ChibiOS Free Embedded RTOS

Any updates on the official support for the slave driver? Would make the chibiOS HAL only excellent for small slave devices. I created a patch for the SPIv2 and the newest chibos 191. Does that seem right? Index: os/hal/include/hal_spi.h ==============================================================...

Are you referring to testhal\STM32\multi\SPI? Just discovered that instead of having STMxx_SPI they where now grouped under "multi" (sneaky :)). Tried to compile the "build for STM32H743", chose the ch.elf in the debug config manually and flashed it. Correction: I get some output...

I'm also dealing with issues with the H743 and SPI. With ChibiOS 19.1.3 there was no output at all and the spi_send was stuck after 3 or 4 iterations. I updated to the latest trunk (from github), fixed my mcuconf and chconf and now I get an output but it looks very weird: h743_weird_spi.png I attach...

Seems to fix it thanks!

I downloaded ChibiStudio around two weeks ago and I'm using the included ChibiOS 19.1.1 stable.

After some digging:

Adding #define STM32_EXTI_ENHANCED to mcuconf.h fixes the issues. Unsure if thats the right place to go. ArduPilot does it the same way.
https://github.com/ArduPilot/ardupilot/ ... _mcuconf.h

The STM32H743 seems to have an issue with the PAL WAIT Drivers. To reproduce go to: chibios191/demos/STM32/RT-STM32H743I-NUCLEO144 set /** * @brief Enables synchronous APIs. * @note Disabling this option saves both code and data space. */ #if !defined(PAL_USE_CALLBACKS) || defined(__DOXYGEN__) #defi...

Understood. Seems like a bunch overhead for my "init" thread though. Meaning I have to actively keep sending semaphores/events in order for the threads to keep running, that takes computing. What I'm looking for is more of an enable/disable flag. Using a regular global boolean flag set by ...

I have a system where I have a bunch of threads that are running when i'm in steady state operation. However when the device is started I don't want them to be running, I would have an init thread that checks a bunch of things on periphery and then starts up the other tasks/threads. I also want to b...

We seem to be talking about different things :) I am aware that one SPI instance (e.g. SPI1) can't be used at the same time, however SPI1 and SPI2 can run very close to each other (see the image below). So my use case is: High Priority Path: GPIO Interrupt -> SPI5 Exchange -> SPI1/2/3 send (<---- as...