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.

TMS570LS1227: nError pin is high after loading Halcogen generated sample program

Part Number: TMS570LS1227
Other Parts Discussed in Thread: HALCOGEN,

Hi,

We have created a custom board using TMS570LS1227 processor and on a new board when we loaded a halcogen generated program on to board it is giving ESM error and nERROR pin is always high and getting below error when we try to flash any other binary.

How do we recover from this and what might be causing this issue

  • Hello Suresh,

    1. The nERROR is a low active pin. How do you connect the nERROR pin on your board? This is the nERROR connection on launchpad:

    2. An uncorrectable ECC error will unconditionally cause the nERROR pin to toggle low. Please check the ESM status registers to see which channels are set.

  • Hi QJ thanks for response 

    1. Think we have connected the nError pin correctly 

    2. We are not able to connect debugger to the board, how do we verify the ESM status registers ? you mentioned uncorrectable, is that mean that we lost those boards ?

    We flashed simplest example created from Halcogen, and confused what made it to go into that error state.

  • It looks like the code you programmed is making the part enter an exception state repeatedly. This prevents the CPU from entering a debug state, resulting in the behavior you observe. You need to try to erase the part, assert and release nRST to see if the erase command is able to halt the CPU and erase the flash.

    Please try this procedure to let CPU enter a debug state:

    1. 1. Open the target configuration window, and launch the selected the configuration
    2. Switch to debug window
    3. Press the reset (nRST) button and hold it
    4. Click “Connect Target” immediately after you release the nRST button
    5. The board should be connected after couple tries
  • Thanks for the Steps. Issue is resolved now, we were getting failure because of Oscillator failing on board.