Clarification Needed: J1939 Configuration

[krupan]

We are working on a new implementation using S32K118 coupled with an existing Tresos license (EB Tresos 24.0.1) and MCAL(S32K1XX_MCAL_4.3_RTM_1.0.4)

Our project requires to support for J1939 on top of the standard CAN functionality. Could you please clarify whether this setup supports the J1939 protocol natively, or if there are any additional configuration steps, hardware considerations, or license updates needed to enable this feature?

[Julián_AragónM]

Hi @krupan

Unfortunately, NXP does not provide J1939 library. SAE J1939 is higher-layer protocol, so you will need to ask third-party companies for the stack, such as:

• CANopen Master/Slave - new platforms supported
• J1939 Stack | J1939-FD Protocol Source Code - Simma Software
• SAE J1939 Know-how | Vector

Best regards,
Julián

[krupan]

Hi @Julián_AragónM 

We understand now that NXP does not provide a J1939 library and a third-party J1939 stack is required.

Can you please confirm whether the CAN MCAL generated via EB Tresos (v24.0.1) with S32K1XX_MCAL (v4.3_RTM_1.0.4) is fully compatible with a third-party J1939 stack “as-is”? Are there any modifications, configurations, or additional layers needed on the CAN driver side to support SAE J1939 on the S32K118 platform?

[Julián_AragónM]

Hi @krupan,

Yes, there should be no problem, as the stack is high level. However, please confirm this with the third-party, as this may not apply to every implementation.

Best regards,
Julián