I am making a large number of i2c calls. Sometimes this works okay, but often the bus will hang and the program gets stuck.
There should not be any gaps in the data below. My theory is that some interrupt is occuring, and if the interrupt occurs at some unfortunate moment, the i2c traffic gets messed up:
So I wanted to try protecting the i2c call by disabling unrelated interrupts, then reenabling them.
ENABLE_INTERRUPTS() and DISABLE_INTERRUPTS() set primask, which would not be good because the i2c still needs to function.
Then I thought I could use BASEPRI, but I am not sure how to set this through the SDK (or otherwise).
Related question - I was experimenting with blocking and non-blocking variants of the receive code.
I have blockng and non-blocking versions of both the send and the receive. If I understand correctly, the non-blocking still blocks the program in a sense, but gives you the option to do something inside the {} brackets while you're waiting.
I wonder if there is a safer way to handle this code. If anything happens to the bus, you will get stuck in the while busy loop forever. But if you use the blocking calls, and change the max wait time to something finite, you should return something to the calling function so they know to retry. is there a try/catch way to handle these i2c calls?
Hello,
Instead of the LPI2C_DRV_MasterGetTransferStatus() function, you can use a callback function which is then called from the LPI2C_DRV_MasterIRQHandler().
The callback function takes i2c_master_event_t as an argument.
callbacks.h
If using a higher interrupt level for the LPI2C is not enough, you can use the BASEPRI.
The BASEPRI register is in the same format as the interrupt priority registers.
For example, interrupt priority level 2:
S32_NVIC->IP[xx] = 0x20;
To set BASEPRI to the same level use something like this:
__asm__("MOV R0, 0x20");
__asm__("MSR BASEPRI, R0");
Regards,
Daniel
