• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 30 subscribers
  • Views 185 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

LAUNCHXL2-570LC43: LS3137 FlexRay drivers are compatible with the LC4357

ARUN BADIGER
Prodigy 10 points
Part Number: LAUNCHXL2-570LC43
Other Parts Discussed in Thread: TMS570LC4357, , TMS570LS3137, TMS570LC4357-EP, TMS570LC4357-SEP

Tool/software:

Hi,

We are procuring LAUNCHXL2-570LC43 with micro controller TMS570LC4357, our focus is to bring up flexray interface.

Community discussions indicate that FlexRay drivers and example code exist for the TMS570LS3137.

Whether LS3137 FlexRay drivers are compatible with the LC4357, or any adaptations are required. 

If changes are required, please outline what modifications are needed to port them successfully.

Is it possible to test FlexRay in loopback mode on a single node by transmitting on Channel A and receiving the looped-back data on Channel B?



Regards,
Arun Badiger

  • 0
    TI__Guru 71771 points

    Hi Arun,

    Based on the provided technical documents, the FlexRay drivers for the TMS570LS3137 are not directly compatible with the TMS570LC4357 and will require adaptations. The necessary modifications involve implementing workarounds for several silicon-specific design exceptions (errata) present in the TMS570LC4357.

    Regarding loopback testing, the device's dual-channel architecture makes it possible to perform a loopback test on a single node by transmitting on Channel A and receiving the data on Channel B, provided an external connection is made between the respective pins.

    Driver Compatibility and Required Adaptations

    Both the TMS570LS3137 and TMS570LC4357 microcontrollers feature a dual-channel FlexRay controller with a FlexRay Transfer Unit (FTU), indicating a similar underlying peripheral. However, the document "Known Design Exceptions to Functional Specifications" for the TMS570LC43x microcontroller lists several errata related to the FlexRay (ERAY) and FlexRay Transfer Unit (FTU) modules.

    Drivers written for the TMS570LS3137 would not account for these issues. To successfully port the drivers to the TMS570LC4357, workarounds for the following known design exceptions must be implemented:

    Errata ID Title
    ERAY#52 (FLEXRAY#52) Wakeup Symbol (WUS) Generates Redundant Wakeup Interrupts (SIR.WUPA/B)
    ERAY#58 (FLEXRAY#58) Erroneous Cycle Offset During Startup after abort of startup or normal operation
    ERAY#59 (FLEXRAY#59) First Wakeup Symbol (WUS) Following Received Valid Wakeup Pattern (WUP) May Be Ignored
    ERAY#60 (FLEXRAY#60) READY Command Accepted In READY State
    ERAY#61 (FLEXRAY#61) The Transmission Slot Mode Bit Is Reset Immediately When Entering HALT State
    ERAY#64 (FLEXRAY#64) SBESTAT register is not readable
    ERAY#68 (FLEXRAY#68) Data transfer overrun for message transfers Message RAM to Output Buffer (OBF) or from Input Buffer (IBF) to Message RAM.
    ERAY#69 (FLEXRAY#69) Missing startup frame in cycle 0 at coldstart after FREEZE or READY command
    FTU#08 FlexRay Transfer Unit Not Disabled On Memory Protection Violation (MPV) Error
    FTU#19 TCCOx Flag Clearing Masked

    FlexRay Loopback Test

    The FlexRay module contains two independent channel protocol controllers and two transient buffer RAMs (TBF A and TBF B) to buffer data for each channel. The device provides separate physical pins for each channel's transmit and receive lines. This dual-channel architecture allows for a loopback test on a single node. To perform such a test, the transmitter of one channel (e.g., FRAYTX1) would need to be externally connected to the receiver of the other channel (e.g., FRAYRX2).

    The following table from the TMS570LS3137 datasheet illustrates the dedicated pins for each channel, which is consistent with the dual-channel architecture of the TMS570LC4357.

    Terminal Signal Name Description
    FRAYRX1 FlexRay data receive (channel 1)
    FRAYTX1 FlexRay data transmit (channel 1)
    FRAYTXEN1 FlexRay transmit enable (channel 1)
    FRAYRX2 FlexRay data receive (channel 2)
    FRAYTX2 FlexRay data transmit (channel 2)
    FRAYTXEN2 FlexRay transmit enable (channel 2)

    References

    • TMS570LC4357 SPNS195C-FEBRUARY 2014-REVISED JUNE 2016
    • TMS570LC4357-EP SPNS253A-MAY 2018-REVISED SEPTEMBER 2019
    • FlexRay Module SPNU563A-March 2018
    • TMS570LC4357-SEP SPNS254A – JUNE 2022 - REVISED MARCH 2024
    • TMS570LS3137 SPNS162C-APRIL 2012-REVISED APRIL 2015
    • FlexRay Module SPNU499C-March 2018
    • Basic Steps to Setup an FTU Transfer SPNA145-January 2012
    • Known Design Exceptions to Functional Specifications TMS570LC4357Microcontroller SPNZ180D-June 2013-Revised May 2016

    Source: ['https://www.ti.com/lit/ds/spns195c/spns195c.pdf#page=4', 'https://www.ti.com/lit/ds/spns253a/spns253a.pdf#page=4', 'https://www.ti.com/lit/ds/spns253a/spns253a.pdf#page=117', 'https://www.ti.com/lit/ug/spnu563a/spnu563a.pdf#page=1215', 'https://www.ti.com/lit/ds/spns254a/spns254a.pdf#page=4', 'https://www.ti.com/lit/ds/spns162c/spns162c.pdf#page=134', 'https://www.ti.com/lit/ug/spnu499c/spnu499c.pdf#page=1048', 'https://www.ti.com/lit/ds/spns162c/spns162c.pdf#page=15', 'https://www.ti.com/lit/an/spna145/spna145.pdf#page=4', 'https://www.ti.com/lit/ug/spnu499c/spnu499c.pdf#page=1243', 'https://www.ti.com/lit/ug/spnu563a/spnu563a.pdf#page=1220', 'https://www.ti.com/lit/ug/spnu563a/spnu563a.pdf#page=1257', 'https://www.ti.com/lit/er/spnz180d/spnz180d.pdf#page=6', 'https://www.ti.com/lit/ug/spnu563a/spnu563a.pdf#page=1215', 'https://www.ti.com/lit/ds/spns253a/spns253a.pdf#page=4']

    --
    Thanks & regards,
    Jagadish.

  • +1 in reply to jagadish gundavarapu
    Prodigy 10 points

    Hi Jagadish Gundavarapu,

    Thanks for the detailed description. I’ll go through it in more detail.

    I was able to successfully test the example code, originally developed for the TMS570LS3137, on the TMS570LC4357 board with only minor modifications to the clock configuration. The data transmission between two nodes has also been successfully verified.

    Thanks & Regards,

    Arun Badiger