Clarification on CAN0 pin combinations in S32K311

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Clarification on CAN0 pin combinations in S32K311

337 Views
yusupkhan241
Contributor II

Hi NXP Team,

I am working on the NXP S32K311 and need clarification regarding CAN0 pin multiplexing. From the reference manual and pin configuration tools, I understand that CAN0 can be routed through specific pin pairs such as:

  • PTB0 (CAN0_RX) and PTB1 (CAN0_TX)
  • PTC2 (CAN0_RX) and PTC3 (CAN0_TX)

In our current hardware design, CAN0 is connected using:

  • PTB0 as CAN0_RX
  • PTC3 as CAN0_TX

Observation:

  • CAN communication works intermittently
  • Errors (CRC/ACK/bit errors) are observed under certain conditions
  • Behaviour varies across boards

Questions:

  1. Is mixing CAN0 RX and TX pins across different groups (e.g., PTB0 + PTC3) a supported configuration on S32K311?
  2. If not supported, could you confirm that this may lead to intermittent or undefined CAN behaviour?
  3. Are there any internal routing or SIUL2 limitations that require RX/TX to be selected strictly from the same pin pair?

We require above information from you to validate this as the root cause of the observed issue.

Thanks in advance for your support S32DS-ARM S32K31XEVB-Q100

0 Kudos
Reply
3 Replies

206 Views
PetrS
NXP TechSupport
NXP TechSupport

Hi,

1. Is mixing CAN0 RX and TX pins across different groups (e.g., PTB0 + PTC3) a supported configuration on S32K311?
A: yes, this is possible. Those pins are different pad types, but it should not be an issue, considering pin rates etc

2. If not supported, could you confirm that this may lead to intermittent or undefined CAN behaviour?

3. Are there any internal routing or SIUL2 limitations that require RX/TX to be selected strictly from the same pin pair?
A: you should properly set the MSCR and IMCR registers to select desired functionality on used pin
TX on PTC3: set MSCR67 OBE=1, SSS=3
RX on PTB0: set MSCR32 IBE=1 and IMCR0.SSS=3 

BR, Petr

0 Kudos
Reply

312 Views
db16122
Contributor III
0 Kudos
Reply

308 Views
yusupkhan241
Contributor II

We observe that CAN0 is currently configured using PTB0 (RX) and PTC3 (TX), i.e., signals are selected from different pin groups.

Based on observed intermittent communication errors (CRC, ACK, bit errors), we suspect that mixing RX/TX across different pin groups may not be a validated or recommended configuration on NXP S32K311.

Could you please confirm whether CAN RX and TX must be selected strictly from the same predefined pin pair (e.g., PTB0/PTB1 or PTC2/PTC3) due to SIUL2/internal routing constraints?

Tags (1)
0 Kudos
Reply
%3CLINGO-SUB%20id%3D%22lingo-sub-2354064%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%3EClarification%20on%20CAN0%20pin%20combinations%20in%20S32K311%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2354064%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%3E%3CP%3EHi%20NXP%20Team%2C%3C%2FP%3E%3CP%3EI%20am%20working%20on%20the%20NXP%20S32K311%20and%20need%20clarification%20regarding%20CAN0%20pin%20multiplexing.%20From%20the%20reference%20manual%20and%20pin%20configuration%20tools%2C%20I%20understand%20that%20CAN0%20can%20be%20routed%20through%20specific%20pin%20pairs%20such%20as%3A%3C%2FP%3E%3CUL%3E%3CLI%3EPTB0%20(CAN0_RX)%20and%20PTB1%20(CAN0_TX)%3C%2FLI%3E%3CLI%3EPTC2%20(CAN0_RX)%20and%20PTC3%20(CAN0_TX)%3C%2FLI%3E%3C%2FUL%3E%3CP%3EIn%20our%20current%20hardware%20design%2C%20CAN0%20is%20connected%20using%3A%3C%2FP%3E%3CUL%3E%3CLI%3EPTB0%20as%20CAN0_RX%3C%2FLI%3E%3CLI%3EPTC3%20as%20CAN0_TX%3C%2FLI%3E%3C%2FUL%3E%3CP%3E%3CSTRONG%3EObservation%3A%3C%2FSTRONG%3E%3C%2FP%3E%3CUL%3E%3CLI%3ECAN%20communication%20works%20intermittently%3C%2FLI%3E%3CLI%3EErrors%20(CRC%2FACK%2Fbit%20errors)%20are%20observed%20under%20certain%20conditions%3C%2FLI%3E%3CLI%3EBehaviour%20varies%20across%20boards%3C%2FLI%3E%3C%2FUL%3E%3CP%3E%3CSTRONG%3EQuestions%3A%3C%2FSTRONG%3E%3C%2FP%3E%3COL%3E%3CLI%3EIs%20mixing%20CAN0%20RX%20and%20TX%20pins%20across%20different%20groups%20(e.g.%2C%20PTB0%20%2B%20PTC3)%20a%20supported%20configuration%20on%20S32K311%3F%3C%2FLI%3E%3CLI%3EIf%20not%20supported%2C%20could%20you%20confirm%20that%20this%20may%20lead%20to%20intermittent%20or%20undefined%20CAN%20behaviour%3F%3C%2FLI%3E%3CLI%3EAre%20there%20any%20internal%20routing%20or%20SIUL2%20limitations%20that%20require%20RX%2FTX%20to%20be%20selected%20strictly%20from%20the%20same%20pin%20pair%3F%3C%2FLI%3E%3C%2FOL%3E%3CP%3EWe%20require%20above%20information%20from%20you%20to%20validate%20this%20as%20the%20root%20cause%20of%20the%20observed%20issue.%3C%2FP%3E%3CP%3EThanks%20in%20advance%20for%20your%20support%20%3CA%20href%3D%22https%3A%2F%2Fcommunity.nxp.com%2Ft5%2Fc-pwmxy87654%2FS32DS-ARM%2Fpd-p%2FS32DS-ARM%22%20class%3D%22lia-product-mention%22%20data-product%3D%223477-1%22%20target%3D%22_blank%22%3ES32DS-ARM%3C%2FA%3E%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fcommunity.nxp.com%2Ft5%2Fc-pwmxy87654%2FS32K31XEVB-Q100%2Fpd-p%2FS32K31XEVB-Q100%22%20class%3D%22lia-product-mention%22%20data-product%3D%223490-1%22%20target%3D%22_blank%22%3ES32K31XEVB-Q100%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2355233%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%20translate%3D%22no%22%3ERe%3A%20Clarification%20on%20CAN0%20pin%20combinations%20in%20S32K311%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2355233%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%3E%3CP%3EHi%2C%3C%2FP%3E%0A%3CP%3E1.%20Is%20mixing%20CAN0%20RX%20and%20TX%20pins%20across%20different%20groups%20(e.g.%2C%20PTB0%20%2B%20PTC3)%20a%20supported%20configuration%20on%20S32K311%3F%3CBR%20%2F%3EA%3A%20yes%2C%20this%20is%20possible.%20Those%20pins%20are%20different%20pad%20types%2C%20but%20it%20should%20not%20be%20an%20issue%2C%20considering%20pin%20rates%20etc%3CBR%20%2F%3E%3CBR%20%2F%3E2.%20If%20not%20supported%2C%20could%20you%20confirm%20that%20this%20may%20lead%20to%20intermittent%20or%20undefined%20CAN%20behaviour%3F%3CBR%20%2F%3E%3CBR%20%2F%3E3.%20Are%20there%20any%20internal%20routing%20or%20SIUL2%20limitations%20that%20require%20RX%2FTX%20to%20be%20selected%20strictly%20from%20the%20same%20pin%20pair%3F%3CBR%20%2F%3EA%3A%20you%20should%20properly%20set%20the%20MSCR%20and%20IMCR%20registers%20to%20select%20desired%20functionality%20on%20used%20pin%3CBR%20%2F%3ETX%20on%20PTC3%3A%20set%20MSCR67%20OBE%3D1%2C%20SSS%3D3%3CBR%20%2F%3ERX%20on%20PTB0%3A%20set%20MSCR32%20IBE%3D1%20and%20IMCR0.SSS%3D3%26nbsp%3B%3C%2FP%3E%0A%3CP%3EBR%2C%20Petr%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2354224%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%20translate%3D%22no%22%3ERe%3A%20Clarification%20on%20CAN0%20pin%20combinations%20in%20S32K311%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2354224%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%3E%3CP%3EWe%20observe%20that%20CAN0%20is%20currently%20configured%20using%20PTB0%20(RX)%20and%20PTC3%20(TX)%2C%20i.e.%2C%20signals%20are%20selected%20from%20different%20pin%20groups.%3C%2FP%3E%3CP%3EBased%20on%20observed%20intermittent%20communication%20errors%20(CRC%2C%20ACK%2C%20bit%20errors)%2C%20we%20suspect%20that%20mixing%20RX%2FTX%20across%20different%20pin%20groups%20may%20not%20be%20a%20validated%20or%20recommended%20configuration%20on%20NXP%20S32K311.%3C%2FP%3E%3CP%3ECould%20you%20please%20confirm%20whether%20CAN%20RX%20and%20TX%20must%20be%20selected%20strictly%20from%20the%20same%20predefined%20pin%20pair%20(e.g.%2C%20PTB0%2FPTB1%20or%20PTC2%2FPTC3)%20due%20to%20SIUL2%2Finternal%20routing%20constraints%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E