Hi fernando.barrios@uwaterloo.ca,
Yes I'm using extended CAN as well, I'm working with J1939.
I would recommend you start from a single message and go from there. Since you have your CAN interface working and you are able to transmit messages you know your physical layer is working. I haven't gone deep using the CAN interface as I was doing only testing for evaluating the s32k144, but I would suggest you to do the following:
- Create the RX message for only one ID, let's say CFDD6EB. Do the Init RX and then in the ISR add the blocks for receiving only this message.
- Assuming you're using CANalyzer connect your two buses (CH1 & CH2) together and start transmitting from a IG block in CANalyzer a message with the CFDD6EB, let's say at a rate of 100 ms. Start CANalyzer and you should see the messages being TX on CH1 and RX on CH2. One thing I noticed is that your CAN bus has to be active when you start your S32K144EVB or your CAN interface doesn't work (I haven't figured out why yet, I assume it has a time out and goes to bus off or something similar). That's why you should start CANalyzer first and have activity on the CAN bus. Then power up your S32K144EVB
- If you are using FREEMASTER, you should see the data you are transmitting from CANalyzer.
Best regards,
Gustavo