ChibiOS Free Embedded RTOS

Hi Giovanni, I was personally saddened to read that the ChibiOS licensing has changed (from GPL+exception to straight GPLv3) and now requires registration for any commercial use (closed source), and then has limits on number of units produced unless a license is purchased. Just knowing that I can't ...

Hi, You are right, I interpreted wrongly the figure 224 in my reference manual. Thanks. But I have another related question. Can I configure the SPI driver so that I can transmit data on the rising edge, but receive data on the falling edge? This is how SPI always works in modes 1 and 2. (CPOL=0 CP...

This is an example of a situation where Git and GitHub's features that make it easy to share, review, and merge changes would really shine. The author has made some apparently useful changes/fixes to ChibiOS but doesn't have time to formally submit the patches. But it would take only a few seconds t...

Actually it seems like the hypothetical sdcErase() and sdcSecureErase() have contrary characteristics. Suppose, as is generally the case, I don't need secure erase. Then I want to help the SD card controller do wear-leveling and optimize performance by marking unused regions of the flash as erased (...

Occasionally you may encounter a compiler or toolchain bug. But most often when changing the compiler optimization level causes a change in behavior from C or C++ code, it indicates that the code is depending on some undefined behavior in the language. (See also A Guide to Undefined Behavior in C an...

Thargon, is this the code you are talking about? void Mutex::unlock(void) { chMtxUnlock(&mutex); } void Mutex::unlockS(void) { chMtxLockS(&mutex); } This code has been in ChibiOS ch.cpp/ch.hpp since Aug 2014. Yikes, I think this is a bad bug: It seems that Mutex::unlockS() should call chMtx...

Thargon, is this the code you are talking about?



This code has been in ChibiOS ch.cpp/ch.hpp since Aug 2014.

Are there multiple BaseSequentialStream types in that version of ChibiOS? I think at some point there was one in the HAL and one in the RT kernel. Maybe gcc is confused. Also is there more of the error message missing? It says "note:" which usually follows an actual warning or error messag...

Now I am less sure. Something funny is going on: My firmware is stuck, I am pausing and resuming execution. Note how current thread changes, but p_current is always the same? http://i.imgur.com/SvvrUCC.png http://i.imgur.com/C20tIQI.png http://i.imgur.com/HuPW6gP.png #define ON_UNLOCK_HOOK onUnlock...

Personally I would prefer the code to be clean and readable to meeting some draconian rules like "macros must be surrounded by parentheses". It seems like many of the MISRA rules may be more of a burden and cost to readability than is worth the benefit of being "MISRA compliant" ...