ChibiOS Free Embedded RTOS

chThdExit() is equivalent to return but this does not include finalization code of course.

To me this means they are not equivalent. Equivalent would mean the exact same cpu instructions will be executed, but since destructors will not be called when using chThdExit(), the code with return will ...

If chThdExit() never returns, and the compiler doesn't know this (which it seems like it will not), doesn't this imply that the cleanup code for user defined types (i.e., class destructors) will not be run, since the compiler implicitly places this code at the end the function body? So return ...

If I allocate an instance of a C++ class type on the stack inside of a thread function, it seems like the destructor for this instance will not be executed if the thread function calls chThdExit() instead of actually returning. The compiler won't know that the no instructions will be executed after ...

I have a thread that is running a loop at 200Hz and in that loop it periodically calls f_write(). This is the only thread to use any of the FatFs calls, and this thread has the highest priority. While the thread is running, the system is responsive (the shell works). When I invoke a shell command to ...

I have a Olimex STM32-H407 dev board which has an STM32F407 chip on it. I'm using the SD card and FatFS to write data to the card. I have been search the source tree but am unable to find out what the SDIO clock speed (SDIO_CK in RM0090) is set to by default. My reading of the documentation is that ...

Giovanni,
I doubled my stack size from 2048 to 4096 to 8192, finally to 32768 (riduculous, I know), and this did not fix it. It isn't obvious to me why the stack size would be an issue if the unhandled exception is occuring even with calls to simple things like help or a do nothing command that ...

I am working from one of the demos, modified to add some extra shell commands. One of my shell commands results in a relatively large bit of code (~25kb) getting added to my project. Most of this is from static data associated with a lookup table, all of it statically allocated. Anyway, when I have ...

This fixes the compilation issue. I will test on Monday to make sure it runs fine on my hardware.

Thanks for the fast fix!

Luke

Great, I look forward to testing it out.

Luke

A simpler way to recreate this bug is to do:

in any of the ARMCM4 demos.

Luke