Hi Team,
Recently, when I used IWR1642, I found that the initialization of CAN would fail under the following conditions. (The program was stuck in CANFD_init(), and the SDK used was mmwave_sdk_03_05_00_04.)
Condition 1. I used the SBL program, initialized the CAN in the SBL program and implemented the following operations before jumping to the APP program.
CANFD_transmitDataCancel(txMsgObjHandle,&errCode1);
CANFD_deinit(canHandle,&errCode1);
Condition 2. I re-initialized CAN in the APP program, but other nodes in the external CAN network had been sending very dense CAN messages during initialization (during fault simulation, they simulated other nodes to send a frame every 1ms. If other nodes sent normally, e.g., once every 50ms, this problem would not occur).
Under the conditions 1&2, the program would be stuck in CANFD_init() about every 10~20 times when the power was turned on again.
However, if condition 1 was excluded (that is, there was no SBL program and only APP program), there would be no problem.
In addition, under the conditions 1&2, the CAN_STB pin was pulled to a high-level electricity before the APP was initialized, and then the program would be stuck in CANFD_init() after each power-on.
What could be the cause of this? What else should I pay attention to when using SBL with CAN communication?
Kind regards,
Katherine
