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.

TMS570LC4357 - FlexRay, POC-State change

Other Parts Discussed in Thread: TMS570LS3137, HALCOGEN

Hi,

I´m working on a FlexRay-driver implementation. My equipment is as follows:

  • Hercules Development Kit: TMDX570LC43 HDK  (Controller: TMX570LC4357)
  • Hercules Development Kit: TMDs570LS31 HDK  (Controller: TMS570LS3137)
  • Two daughter cards with FlexRay-Transceiver

  • Composer Studio Version: 6.0.1.00040
  • HALCoGen Version: 04.03.00

The TMS570LS3137 controller is working properly, but the TMX570LC4357 got a problem I´m not able to solve:

When I try to change the POC-state from DEFAULT_CONFIG to CONFIG with SUCC1.CMD(0-3) = 0001, the SUCC1.PBSY - Bit is set. After that the FlexRay Communication Controller should accept the command and reset the POC busy flag (SUCC1.PBSY) but that never happened.

Even with the TI FlexRay Example code and no additional hardware, the POC busy flag is permanently set.

Do you know what could cause this behaviour? Thanks for every reply.

Best Regards,

Chris

  • Hi Chris,

    I'm not the Fray expert, but from the descriptions of the CONFIG state, PBSY and the CMD I would expect the PBSY bet to be set while in CONFIG mode.

    1 = POC is busy, CMD(3-0) locked

    As CMD is always locked in CONFIG state I would expect this bit to be always set. To leave the CONFIG state the unlock sequence is required.

    However, this is only my interpretation of the spec.

    EDIT:

    Ok, it seems that I'm wrong, according to Bosch Application Note AN002:

        //
        // write Configuration Lock Key
    while ((read32bit(SUCC1) & 0x00000080) != 0);
    write32bit(LCK, 0x000000CE);
    write32bit(LCK, 0x00000031);
        //
        // CHI command READY
    write32bit(SUCC1, 0x0F8FFB02); // SUCC1.TXSY = SUCC1.TXST = 1

    This clearly shows polling the PBSY bit before leaving the CONFIG state.

    Best Regards,
    Christian

  • Hi Chris,

    Ok, second try, now I think I know whats going on.

    I talked to our former FlexRay expert and he told me, that what you are seeing is a typical issue and caused by the clock goint to the FlexRay module not turned on or not configured correctly.

    I quickly checked the default configuration of the TMS507LC4357in HALCoGen and indeed the clock domain for the FlexRay module (VCLKA2) is disabled by default:

    So please enable VCLKA2 and try again.

    BTW according to the datasheet the FlexRay module needs a clock of 80MHz.
    Thus you should use PLL2 as source for VCLKA2 and configure it accordingly.

    Best Regards,
    Christian

  • Hi Christian,

    Indeed, the disabled clock domain caused the problem. Thank you so much!!!

    Best Regards,
    Chris