Re: [INFO] ChibiOS 3.0 Status
Posted: Wed Dec 18, 2013 8:22 pm
Giovanni wrote:Sure, 2014
So much better than 2015!
I will let the others push you further
So much better than 2015!
I will let the others push you further
Page 2 of 2
So much better than 2015!
I will let the others push you further
Re: [INFO] ChibiOS 3.0 Status
Posted: Sun Dec 22, 2013 7:58 pm
I downloaded ChibiOS 3.0 from GitHub yesterday. I really like how nil is now integrated.
I found a possible problem with serial in the NIL-STM32F051-DISCOVERY demo. I modified this line to write more text.
If I write more than 17 bytes, the example freezes after writing the first two bytes. The blink threads also stop.
I think the problem is in hal_queues.c - oqWriteTimeout().
If I replace the osalThreadEnqueueTimeoutS() with an unlock and return, the program no longer freezes. The message is truncated but the first 18 bytes print.
I also have a problem building the RT-STM32F051-DISCOVERY demo with the latest version of Sourcery CodeBench Lite. I get the following:
If I use this make call it builds.
I have not tried an older version of Sourcery CodeBench Lite to see if Link Time Optimization works.
I found a possible problem with serial in the NIL-STM32F051-DISCOVERY demo. I modified this line to write more text.
Code: Select all
chnWrite(&SD1, (const uint8_t *)"Hello World!\r\n", 14);If I write more than 17 bytes, the example freezes after writing the first two bytes. The blink threads also stop.
I think the problem is in hal_queues.c - oqWriteTimeout().
If I replace the osalThreadEnqueueTimeoutS() with an unlock and return, the program no longer freezes. The message is truncated but the first 18 bytes print.
Code: Select all
while (oqIsFullI(oqp)) {
osalSysUnlock();////////////////////////////////////////////////////////
return w;///////////////////////////////////////////////////////////////
if (osalThreadEnqueueTimeoutS(&oqp->q_waiting, time) != Q_OK) {
osalSysUnlock();
return w;
}
}
I also have a problem building the RT-STM32F051-DISCOVERY demo with the latest version of Sourcery CodeBench Lite. I get the following:
Linking build/ch.elf
main.c: In function 'main':
main.c:58:5: internal compiler error: Segmentation fault
int main(void) {
^
libbacktrace could not find executable to open
Please submit a full bug report,
with preprocessed source if appropriate.
See <https://sourcery.mentor.com/GNUToolchain/> for instructions.
lto-wrapper: arm-none-eabi-gcc returned 1 exit status
c:/users/bill/mentorgraphics/sourcery_codebench_lite_for_arm_eabi/bin/../lib/gcc
/arm-none-eabi/4.8.1/../../../../arm-none-eabi/bin/ld.exe: lto-wrapper failed
collect2.exe: error: ld returned 1 exit status
cs-make: *** [build/ch.elf] Error 1
If I use this make call it builds.
cs-make USE_LTO=no
I have not tried an older version of Sourcery CodeBench Lite to see if Link Time Optimization works.
Re: [INFO] ChibiOS 3.0 Status
Posted: Sun Dec 22, 2013 8:30 pm
Hi,
LTO is known to work using this toolchain: https://launchpad.net/gcc-arm-embedded
About the issue with queues, I will look into it, thanks for finding.
Giovanni
LTO is known to work using this toolchain: https://launchpad.net/gcc-arm-embedded
About the issue with queues, I will look into it, thanks for finding.
Giovanni
Re: [INFO] ChibiOS 3.0 Status
Posted: Mon Dec 23, 2013 8:21 pm
Thanks for the link to the GCC ARM toolchain.
Their just released 4.8 version has a problem with lto but the 2013-09-26 version of 4.7 works.
Their just released 4.8 version has a problem with lto but the 2013-09-26 version of 4.7 works.
Re: [INFO] ChibiOS 3.0 Status
Posted: Sun Dec 29, 2013 11:01 am
Hi,
I finally found the root cause, it was a bug in chSemSignalI() in Nil. Now the queues work as expected.
Next for the 3.0 branch, the AVR and MSP430 ports, this should not take long.
Giovanni
I finally found the root cause, it was a bug in chSemSignalI() in Nil. Now the queues work as expected.
Next for the 3.0 branch, the AVR and MSP430 ports, this should not take long.
Giovanni
Re: [INFO] ChibiOS 3.0 Status
Posted: Fri Jun 13, 2014 12:29 am
Got the same problem with segfault, I use Launchpad's arm-none-eabi-gcc:
Fresh ChibiOS/RT, just trying to compile a supplied demo. What should I do?
[03:27:45] che@quad:~/mcu/chibios-stm32f103/ChibiOS-RT/demos/STM32/RT-STM32F103-OLIMEX_STM32_P103$ make
Linking build/ch.elf
main.c: In function 'main':
main.c:41:5: internal compiler error: Segmentation fault
int main(void) {
^
Please submit a full bug report,
with preprocessed source if appropriate.
See <http://gcc.gnu.org/bugs.html> for instructions.
lto-wrapper: arm-none-eabi-gcc returned 1 exit status
/usr/bin/../lib/gcc/arm-none-eabi/4.8.3/../../../../arm-none-eabi/bin/ld: lto-wrapper failed
collect2: error: ld returned 1 exit status
make: *** [build/ch.elf] Error 1
Fresh ChibiOS/RT, just trying to compile a supplied demo. What should I do?
Re: [INFO] ChibiOS 3.0 Status
Posted: Fri Jun 13, 2014 1:09 am
Have a look at this thread viewtopic.php?f=2&t=1900
The short answer is that with gcc 4.8 LTO is a problem.
The most reliable results are achieved when LTO is set to no in Makefile.
saraben
The short answer is that with gcc 4.8 LTO is a problem.
The most reliable results are achieved when LTO is set to no in Makefile.
saraben
Re: [INFO] ChibiOS 3.0 Status
Posted: Fri Jun 13, 2014 8:50 am
Correct, I recommend staying with 4.7.3 which is very reliable. You may give a try to the Bleeding Edge Toolchain 4.8.x, I am not sure it shares this problem. Both compilers are included in ChibiStudio 6.
Giovanni
Giovanni
Re: [INFO] ChibiOS 3.0 Status
Posted: Tue Apr 14, 2015 2:53 pm
Looks like the release is getting closer, but not yet?
Re: [INFO] ChibiOS 3.0 Status
Posted: Tue Apr 14, 2015 3:24 pm
The "preview 3" has been released yesterday.
Giovanni
Giovanni