I am now running DMA-mode. The data is received correctly and put into the rx-buffer.
Unfortunately the messageProcessor is never called so I cannot handle the data.
debugging codes are: 0x82, 0x80, | : 0x04, 0x13, 0x14, 0x05 : |
I understand:
82&80 init transfer
04 address match
13 address match ...
Search found 3 matches
- Thu Sep 03, 2020 1:56 pm
- Forum: General Support
- Topic: I2C Slave mode support?
- Replies: 116
- Views: 138557
- Wed Aug 26, 2020 8:22 am
- Forum: General Support
- Topic: I2C Slave mode support?
- Replies: 116
- Views: 138557
Re: I2C Slave mode support?
Hej steved,
thanks for answering.
Indeed I overlooked i2cMatchAddress(). Beside that I was struggeling with some inconveniences in my test setup. Meanwhile I managed to get something working.
As I don't have any experience with DMA, I disabled DMA. i2c should now run in interrupt mode.
I can see ...
thanks for answering.
Indeed I overlooked i2cMatchAddress(). Beside that I was struggeling with some inconveniences in my test setup. Meanwhile I managed to get something working.
As I don't have any experience with DMA, I disabled DMA. i2c should now run in interrupt mode.
I can see ...
- Thu Aug 20, 2020 2:03 pm
- Forum: General Support
- Topic: I2C Slave mode support?
- Replies: 116
- Views: 138557
Re: I2C Slave mode support?
Hi folks.
I am really happy, that there is code for i2c slave mode available (thanks for that), but i do have some little problem, getting it to work properly. Maybe someone can give me a hint?
I am using the NUCLEO-F767ZI, OS is 20.3.1 and code compiles without any error.
DMA disabled.
From the ...
I am really happy, that there is code for i2c slave mode available (thanks for that), but i do have some little problem, getting it to work properly. Maybe someone can give me a hint?
I am using the NUCLEO-F767ZI, OS is 20.3.1 and code compiles without any error.
DMA disabled.
From the ...