Other Parts Discussed in Thread: AWR6443
Tool/software:
Hi TI experts,
When we do PV test on new product for BUSOFF recovery, we found that CAN message can not send out successfully after shorting CANH and GND
The detailed test case is as follows:
1 send diagnostic message request with 100ms cycle
2 short the CANH and GND about 60s
3 check if Application message and diagnostic message is recovered
result: The Application message can recover but the diagnostic message is not.
We use the MCAL and MCAL version is "MCAL_REL_03.00.03.02_ENGINEERING_RELEASE".
We add some prints at Can_Write API and found all API is called rightly when the issue occurs.
Finally, we add prints at end of Can_mcanWriteTxMailbox to check the CAN ID and status of API MCAN_txBufAddReq
And the ID is our diagnostic CAN ID and status is 0 when this issue occurs.
Our diag CAN mailbox configuration is as follows:
Our CAN controller configuration is as follows:
After we change the configure to FULL-CAN, the issue seems disappear.
But there is still some other issues, the diag CAN message need more time to recover to send after remove the short error inject.
So, we want to know if there is some constraints on the CAN Handle type and the reason why the diag CAN message need more time to recover to send after remove the short error inject.