ChibiOS Free Embedded RTOS

All but the most recent ST devices use one of two I2C hardware blocks, each with its own driver. (So I2CV1, I2CV2). You can tell which by looking at the device-specific make file - look in the directories under \os\hal\ports\STM32 (for 20.3.4, anyway). Judging by the minimal work involved in porting...

I know this is a very old long thread but would like to ask why this seems not to be making it into upstream?:) I suspect because the code could do with a good cleanup after several people have updated and extended it. I've long felt that the V2 code is over-complicated, but since it works reliably...

I've never used the F103; IIRC I last used I2Cv1 slave code on the F4, which I stopped using a long time ago. AFAIK that should work on F103 as well. I last updated ChibiOS 19.1.3 (not sure how well it was tested), and have attached the updated files from there. The test harnesses I used are posted ...

Two possibilities that I can think of:

1. You can generate an interrupt each time SPI completes. Use that to start off the next transfer.
2. Use a spare hardware timer to generate interrupts at a faster rate.

Giovanni wrote:Could you try the "alternate" Cortex-M port? it is an entirely different approach to the problem, especially interrupts handling.
Giovanni

Looks to be Chibi 21 only. Would it backport to Chibi 20, or do I need to move my software forward? (I've been trying not to change too much!)

No intentionally enabled fast interrupts (I think I might have checked for unintentional ones at some time, but I'll revisit that). And no stack overflows - at least not according to both the ChibiStudio plugin and a cruder check of my own. Its an F767, so I've got the stack guard enabled. I can con...

Finally revisiting this project, to discover that ST have recently released an updated Errata (https://www.st.com/resource/en/errata_sheet/dm00257543-stm32f76xxx-and-stm32f77xxx-device-limitations-stmicroelectronics.pdf). Quite a lot of new stuff, with 2.4.4 having similarities to my problem: Memory...

I think I read somewhere that FreeRTOS has a construct similar to this, where from within an interrupt you could trigger the execution of any routine from within a thread. Not difficult to set up using event flags and a worker thread, but maybe there would be efficiencies derived from a specific con...

Have a look at the attached; think it contains some useful routines for setting single filters.
(Don't adopt it wholesale; it's not been brought up to date with latest Chibi version, and may have other surprises; but it does work)

There's an alternative I2C slave, originally written by genosensor, and modified by me for the later I2C ports, if you search