Hello, I found a strange problem when debugging I2C as a cluster machine on the chip of AM2632. My project will be attached
First of all, I changed it in the official routine, the official routine did not see AM2632 as a cluster machine routine, so I changed it in the original routine as a host. Secondly, since the MCU is a complex machine, then I found an upper computer tool (Aaradvark), as the host to issue IIC read and write commands, in the first acquisition of semaphore, will be stuck there, and then receive the iic command, will trigger the callback function, the semaphore release, so as to continue to run the program. That is to say, MCU received the first IIC command, but when MUC sent data, that is, the second I2C_transfer, it did not trigger the callback function, and the returned state was I2C_STS_SUCCESS, which would get stuck at SemaphoreP_pend. Then the IIC bus will be pulled dead, you can see in the waveform diagram, and can no longer trigger the interrupt callback function, how to deal with this problem?
i2c_read_am263x-cc_r5fss0-0_freertos_ti-arm-clang.zip
