- Forums
- Product Forums
- General Purpose MicrocontrollersGeneral Purpose Microcontrollers
- i.MX Forumsi.MX Forums
- QorIQ Processing PlatformsQorIQ Processing Platforms
- Identification and SecurityIdentification and Security
- Power ManagementPower Management
- Wireless ConnectivityWireless Connectivity
- RFID / NFCRFID / NFC
- Advanced AnalogAdvanced Analog
- Neural Processing UnitsNeural Processing Units
- MCX Microcontrollers
- S32G
- S32K
- S32V
- MPC5xxx
- Other NXP Products
- S12 / MagniV Microcontrollers
- Powertrain and Electrification Analog Drivers
- Sensors
- Vybrid Processors
- Digital Signal Controllers
- 8-bit Microcontrollers
- ColdFire/68K Microcontrollers and Processors
- PowerQUICC Processors
- OSBDM and TBDML
- S32M
- S32Z/E
-
- Solution Forums
- Software Forums
- MCUXpresso Software and ToolsMCUXpresso Software and Tools
- CodeWarriorCodeWarrior
- MQX Software SolutionsMQX Software Solutions
- Model-Based Design Toolbox (MBDT)Model-Based Design Toolbox (MBDT)
- FreeMASTER
- eIQ Machine Learning Software
- Embedded Software and Tools Clinic
- S32 SDK
- S32 Design Studio
- GUI Guider
- Zephyr Project
- Voice Technology
- Application Software Packs
- Secure Provisioning SDK (SPSDK)
- Processor Expert Software
- Generative AI & LLMs
-
- Topics
- Mobile Robotics - Drones and RoversMobile Robotics - Drones and Rovers
- NXP Training ContentNXP Training Content
- University ProgramsUniversity Programs
- Rapid IoT
- NXP Designs
- SafeAssure-Community
- OSS Security & Maintenance
- Using Our Community
-
- Cloud Lab Forums
-
- Knowledge Bases
- ARM Microcontrollers
- i.MX Processors
- Identification and Security
- Model-Based Design Toolbox (MBDT)
- QorIQ Processing Platforms
- S32 Automotive Processing Platform
- Wireless Connectivity
- CodeWarrior
- MCUXpresso Suite of Software and Tools
- MQX Software Solutions
- RFID / NFC
- Advanced Analog
- Neural Processing Units
-
- NXP Tech Blogs
- Home
- :
- Product Forums
- :
- MPC5xxx
- :
- Re: How to implement freely variable payload length for FlexRay dynamic frames on MPC5604P
How to implement freely variable payload length for FlexRay dynamic frames on MPC5604P
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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!
Solved! Go to Solution.
petervlna
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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
petervlna
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
