S32KのトピックRe: CAN FD and CAN(not Working)

CAN FD and CAN(not Working)

GaneshBhagwat — Fri, 25 Jul 2025 15:33:41 GMT

Hello NXP Community,

I'm currently facing an issue with my CAN configuration. I'm using a basic setup for CAN communication, and it only works when I use CAN-FD mode with PEAK CAN Viewer. However, when I try standard Classical CAN (non-FD), I do not receive any response.

I've attached my project for reference. Could someone kindly review it and let me know if there might be any missing configuration or setting that I’ve overlooked?

To summarize:

CAN-FD + PEAK CAN Viewer: Working as expected
Standard CAN + PEAK CAN Viewer: No response from the board

Any suggestions or guidance would be greatly appreciated.

Thank you in advance!

Best regards,
Ganesh Bhagwat

Re: CAN FD and CAN(not Working)

Julián_AragónM — Tue, 29 Jul 2025 18:32:01 GMT

Hi @GaneshBhagwat

Is the PCAN-View tool configured correctly for the mode, baud rate and sampling point?

Is it possible to share what do you see on the bus? (By using a logic analyzer or oscilloscope) just to confirm if the frame is being sent correctly. Also, please elaborate on what "not working" implies; are you able to enter callback upon reception? Is it only transmissions you are having issues with?

I can see in your CANInit function, ID 0x80000 is being set for acceptance, confirm if this is also set in the CAN analyzer.

You can use this community post as guidance for CAN configuration: Example S32K358 FlexCAN TXRX ISR S32DS35 RTD400/500 - NXP Community.

Best regards,
Julián

Re: CAN FD and CAN(not Working)

GaneshBhagwat — Tue, 05 Aug 2025 16:36:05 GMT

Hi Julián,

Thank you for your response.

I initially suspected a software configuration issue, which is why I posted here. However, it turned out to be a hardware-related problem with the TJA1443 transceiver connection. Due to a floating pin, I was unable to receive or transmit any CAN messages in normal CAN but I don't know why it was working in FD.

After resolving the hardware issue, everything is now working as expected.

Thanks again for taking the time to respond and for pointing me toward the helpful community post.

Best regards,
Ganesh