ChibiOS Free Embedded RTOS

Giovanni wrote:Oh wow, they now pay you to cross the black gates of Mordor?

Giovanni

Hahah, yep! This certainly isn't the Microsoft that I grew up with. Satya is bringing with him a huge culture shift.

Giovanni, does this nudge you at all in hosting ChibiOS on github ?

https://github.com/sponsors

I'm sure there are people out there who would contribute something.

Have you had a chance to look into the various code style enforcement tools I emailed you about?

If you make it a buffered driver, you can use the hal_serial.h abstraction, as it uses virtual method tables for the implementation. If you need per character interrupts, that would be more like hal_uart - and that is tied to a specific lld file.

Now that the latest kernels and HAL are released, I suggest starting a new thread with ideas for the next significant releases.

Hi, When CH_CFG_NO_IDLE_THREAD is enabled then the main() function is the idle thread, you must never try to sleep in there. Doing so causes the problems you are describing. Giovanni Is this still the case? If so, there should be an assert somewhere to catch this. I think chSchGoSleepS is the right...

I'm working on a CAN driver for the MCP2515, making it look like a standard hal_can_lld . When I get that working, I'll play with some ideas we're talking about here. Now let's see who gets some code out there first lol .

So, what do you think - should we make something like a BaseCanLLD (following the style of the other single inheritance Base* 'classes') which hal_can would then use?

If you're taking suggestions for the order of including device support, consider the stm32F72x next

Thanks for turning your attention to the internal flash driver. We may have some test/example code to contribute for testhal as well. I'll look into it if it would help.

Perhaps HAL should go full C++ but I don't know if the world is ready for this :) Giovanni Definitely not ready yet :) ... I'm guessing the VMT should just be part of the driver object. In hal_<device>.c, calls to LLD could be done thru a macro - which either uses the hal_<device>_lld calls directl...