2406368_en-US

[#1]

How to implement freely variable payload length for FlexRay dynamic frames on MPC5604P

Hello everyone,

I am currently developing FlexRay communication using the MPC5604P MCU, and I need to implement frame-by-frame transmission of different payload lengths in the Dynamic Segment.

I noticed that in NXP's official FlexRay Unified Driver example, the configuration of the Dynamic Segment involves parameters such as G_NUMBER_OF_MINISLOTS, GD_MINISLOT, and P_PAYLOAD_LENGTH_DYN_MAX. However, these parameters appear to be global configuration settings rather than frame-by-frame configurable options. Is there any solution to achieve this functionality?

I would greatly appreciate any insights or suggestions. Thank you very much!

Re: How to implement freely variable payload length for FlexRay dynamic frames on MPC5604PI get it, thank you very matchRe: How to implement freely variable payload length for FlexRay dynamic frames on MPC5604P

Hello,

The FlexRay cluster parameters G_NUMBER_OF_MINISLOTS, GD_MINISLOT, and P_PAYLOAD_LENGTH_DYN_MAX are global timing parameters and must remain consistent across the cluster. P_PAYLOAD_LENGTH_DYN_MAX defines the maximum payload length that any dynamic frame may use; it does not force every dynamic frame to have that length.

Dynamic-segment frames may carry different payload lengths. The actual length is specified in the payload-length field of the individual frame header and is expressed in 16-bit words. Therefore, configure P_PAYLOAD_LENGTH_DYN_MAX for the largest required frame, and update the transmit message-buffer payload-length field before each transmission. Odd byte lengths require padding to the next even number of bytes.

If the FlexRay Unified Driver version being used fixes the payload length during LPDU configuration and does not expose this field through its transmit API, then freely changing the length for one configured LPDU is not supported directly by that driver interface. In that case, either configure multiple dynamic LPDUs with different lengths or modify/use the low-level message-buffer handling to update the frame header while observing the MPC5604P message-buffer locking procedure.

Best regards,

Peter