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.

nERROR pin not activated for EFUSE stuck at 0 test in TMS570LS3137

Other Parts Discussed in Thread: TMS570LS3137

Hello everyone,

I am testing the EFUSE self test flow with TMS570LS3137. According to the TRM, the stuck at 0 test should triger ESM3.1 and ESM1.41. I can see these error flags are set. But the error pin in not activated, the register ESMEPSR is 0x1. Does someone also see the same behavior? Or the error pin is only activated for real EFUSE error? I have some other test which activate the error pin. So I am sure the error pin works (the LED at the HDK is on).

Any advice?

Thank you!

Libo

  • Hello Libo,

    I will try and recreate your test to see if I can figure out what might be causing the issue. Is possible for you to provide me the code you are using to generate the issue?

  • Hi Chuck,

    thanks for the quick response. I just did a few tests. First I turned off the power for the HDK board. Then I restarted the test in CCS. Before my EFUSE test, I wrote 0x003FC000 into EFUSE boundary register. In other words, I started teh stuck at 0 test manually. Then I saw the error pin was 0 and the LED at HDK was on. Then I restarted the software, and run my EFUSE test. Now I see the error pin is activated as expected. I repeated the test a few times, and the error pin is always activated. I can no more re-generate the error I saw yesterday. So I will close this thread. Thanks for the help.

    Libo

  • Hi Chuck,

    I have found the error in our code. The error handler of ESM1.41 also clears the error pin. Yesterday I didn't set break point  in ESM1.41 error handler, so the error pin was cleared without being seen.

    Thanks!

    Libo

  • Hello Libo,

    I am glad you were able to get past the issue. Please let us know if you have any additional needs for support.