ChibiOS Free Embedded RTOS

The difference seems to be that using /sys/bus/iio/devices/X sensor results in a GET_REPORT which is a control request and using /dev/hidrawX results in an interrupt read request. For the device to respond to the interrupt read request your software needs to send something on that endpoint (otherwis...

Each thread can listen for up to 32 events or you can register up to 32 event listeners for a particular thread. An unique event listener is required for each event source to which you are registering.

The way to solve this would be a fundamental change to ChibiOS. That said, you could decouple absolute time and interval time. Meaning, you always have a free-running absolute time source (perhaps from a 32kHz clock) and then you have an interval timer for performing the actual delay based on the de...

ST also has an app note for using a timer capture/compare to implement DMA timeout: http://www.st.com/content/st_com/en/products/embedded-software/mcus-embedded-software/stm32-embedded-software/stm32-standard-peripheral-libraries-expansions/stsw-stm32027.html# This would require board changes however.

This sounds like a protocol issue. When sending data of max packet size the host/device need to 'terminate' the request with a short packet (zero-length packet). Without a short packet both the host/device don't know the transfer has ended if the length is equal to the max packet size. To test you c...

osalDbgCheck(chk); osalDbgAssert(i2cp->state == I2C_READY, "not ready"); if(wkup){ chprintf((BaseSequentialStream *)&SERIAL_PORT, "%s: %d\n\r",__func__,i++); chThdSleepMilliseconds(250); } osalSysLock(); i2cp->errors = I2C_NO_ERROR; i2cp->state = I2C_ACTIVE_TX; if(wkup){ chp...

The way I'm understanding the problem is not with the license itself, but rather enforcing it. If you want to earn a reasonable profit for you work, then you are forced to limit what is available for free. However, the point of FOSS, is that it's not meant to earn a reasonable profit. It seems you'r...

Interrupts are re-enabled following the context switch to the next runnable task. In general ChibiOS works like this: 1) Task calls OS wait/pend function 2) OS calls chSysLock() 3) Check if the resource is available (assume it is not) 4) If resource is unavailable, perform context switch to highest ...

Have a problem with sending data through SPI in Virtual Driver header. Symptoms are as same as I had when I just started to work with SPI and used wrong driver. Can't figure out how to solve it. Shortly, what I need. I'm using OLED display in my design and since it has limited time of life, I want ...

You shouldn't be using chprintf within the callback as it's in an interrupt context. When the string is longer than the queue can accept it will block and attempt to context switch from an interrupt context which is not possible.