This thread has been locked.
If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.
Tool/software:
Hi,
We are using AM2634 with custom designed hardware which contains CAN Transceiver "ISO1042-Q1 " along with CCS Version 12.7.0.00007 and XDS110 Debugger.
We are Facing an issue with CAN when we are communicating with two nodes using CAN FD mode while the first node is configured for Tx ID 4, Rx ID 1 and the second node is configured for Tx msg ID 1, Rx msg ID 4. The first node is transmitting a packet for every 3 seconds and the second node is transmitting for every 1 second. Initially the transmission and reception on both nodes is being done successfully but after some time one of the nodes is getting the interrupt status as RX FIFO1 Element lost but in my configuration that FIFO 1 is not even configured instead dedicated message buffer configuration was utilized. In TRM it was mentioned that a write attempt to RX FIFO of size zero will cause this RX FIFO 1 Element lost Error. But as mentioned above RX FIFO1 is not configured but in global filter configuration it was configured as accept nonmatching frames to RX FIFO1 but there is no such nonmatching frame transmitting into the bus.
What could be the actual issue?
Hello,
Apologies for the delayed response here.
1) Could you provide screenshots of the CAN_H/CAN_L/CANTX/CANRX during the initial successful operation and similar for the eventual failing operation?
2) Can you provide code snippets of your RX/TX Buffer/FIFO[0:1] configuration code?
Thanks and regards,
Zackary Fleenor
we were able to resolve this issue but we are facing another issue where we are getting the receiving interrupt as rx message is copied into respective buffer but in NDAT1 and NDAT2 registers no bit is set. we are only facing this issue when 4 nodes have been configured of which 3 are transmitting at different time intervals and one node is only recieving.
Understood.
Can we mark this thread as closed?
Will continue additional debug in the new thread:
Best Regards,
Zackary Fleenor