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.

Compiler/RM48L952: HET Paritycheck freezing issues

Part Number: RM48L952
Other Parts Discussed in Thread: HALCOGEN

Tool/software: TI C/C++ Compiler

Hello TI,

i have a question regarding the provided halcogen lib for the hetparitycheck as there is an bitflip injection in the HETRAM. So far I can see that the ESM group 1 is triggered when I call the API which is what I expect. But somehow the HET program stops working after that call. A simple PWM LED just freezes and stops working. Is there anything I need to consider?

  • Hello,

    This is the intended behavior and is defined as a safe state for the N2HET. See the TRM (spnu503c) section 20.2.2.3 on page 799 titled "Parity Error Detection Actions". The application needs to make sure that the RAM does not have a real fault. If error is injected intentionally the HET can be turned ON again once the parity memory is restored to the correct values.

    Regards, Sunil

  • Hello Sunil,

    thanks for the reply. I have another question connected to this topic. In case of 2 HETprograms are running (het1 & het2) on the system, how can I deal with synchronization issues as the het programs are updated every program resolution tick. I assume there will be a "small" time slice where Het1 will be out of sync with the Het2 as it has been deactivated due to its parity error injection. After I activate HET1 again, what are the measurements to bring both programs into sync again, or does it happen automatically by the MCU.

    Is it possible for the hetparitycheck API usage to not disturb the current het1/2 program flow?

    Thanks

  • Hello,

    You can connect the two HET instances in a master/slave configuration. The connection is done internally. Then one HET generates the loop timing for the second HET. This way the loop time for both HETs are synchronized.

    Also, if a parity error occurs on the master HET, it also shuts off the loop-time synchronization signal, so the second HET will also stop until it sees the master HET generate the loop-time sync signal again.

    You can always check the HET RAM parity error detection logic before enabling the HET. This way the program flow is not disturbed by the parity error injection.

    Regards, Sunil