• State Resolved
  • Locked Locked
  • Replies 8 replies
  • Answers 2 answers
  • Subscribers 82 subscribers
  • Views 1058 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

TMS320F280049: Trouble Halting Target CPU: (Error -1156 @ 0x0) Device may be operating in low-power mode

Shaoxing Ke
Expert 3580 points
Part Number: TMS320F280049

Hi Teams,

I am asking for customer here. And customer is using F280049M for mass production.

They are flashing their device with the same software. But they will face below problem in some of the device(about 1%). If the device is  a bare chip (no program), and this phenomenon does not occur.

They found that the chip was powered off during the CAN upgrade process, and the code in the chip was incomplete. At this time, the following error will occur when connecting to the target board/F280049M.

This is console as below:

[ERROR] C28xx_CPU1: Trouble Halting Target CPU: (Error -1156 @ 0x0) Device may be operating in low-power mode. Do you want to bring it out of this mode? Choose 'Yes' to force the device to wake up and retry the operation. Choose 'No' to retry the operation without waking the device. (Emulation package 9.7.0.00213)

By clicking OK, the problem repeat. And we change pull GPIO24 low to set in wait mode, we are able to connect target, erase the flash and program the correct software.

But when we pull GPIO24 high, Power up again, we are still unable to program the software, encounter the same issue.

1.Check the schematic diagram/wiring/whether the pull-up resistor meets the specification requirements according to TI's EVM board.

Because we test connection success, only connect the target board/F280049M, it fails to report the issue about 1156 low-power mode.

2.Check that the F280049M XRSn and the clock is normal, and the power supply 3.3V is also normal.

3.We checked and found that when the target board is connected, TRSTn- will be set high, then there will be a low level for 200us, and then a high level, followed by a low level for 300us, and then it will always be a high level. Not sure that TRSTn status bit prevents emulator from exiting low-power mode？

4.Replaced an emulator again, the problem still exists.

5.Check that EMU 0 & EMU1 in 14-Pin also have pull-up resistors, which are 5.1K and 6.2K respectively.

Can you give troubleshooting suggestions? Or where is the problem? The initial inspection determined that the hardware is normal, but I don't know what caused the failure to exit low-power mode, Thanks.

  • 0
    TI__Guru* 95315 points
    Shaoxing Ke said:
    They found that the chip was powered off during the CAN upgrade process, and the code in the chip was incomplete.

    If the chip was powered off during the CAN upgrade process, no code update would have taken place.

    On a fresh device (i.e. the flash is blank), since there is no code, the watchdog would repeatedly keep timing out and resetting the device. If you attempt to connect to the device while it is being reset, you will see the error shown. This is why you are able to connect to the device in WAIT mode.

  • 0 in reply to Hareesh Janakiraman
    TI__Expert 3580 points

    Hi Experts,

    Customer has their own Bootloader in Flash-A, and Bootloader has disable the watchdog. Actually we test the XRSn Pin is always high level.

    But we found that add CSM_unlock() in the Bootloader, The BOOTLOADER code and the user APP coed will run normally. And then artificial suspension of the CAN upgrade process, the lower power mode 1156 issue would not happen. If we delete the CSM_unlock(), same operation the 1156 issue would happen.

    So here are doubt that when we connect to the target board/C28x, no matter whether the chip is locked or not, the connection should work. That's a bit hard to make sense. Could you give me one picture to understand this? Thanks.

  • +1 in reply to Shaoxing Ke
    TI__Guru* 95315 points

    It is likely the ECSL kick in and breaks the emulator connection. Please refer to 3.13.1.2 Emulation Code Security Logic (ECSL) in page 137 of www.ti.com/lit/SPRUI33. 

    Shaoxing Ke said:
    3.We checked and found that when the target board is connected, TRSTn- will be set high, then there will be a low level for 200us, and then a high level, followed by a low level for 300us, and then it will always be a high level. Not sure that TRSTn status bit prevents emulator from exiting low-power mode？

    This is normal and expected behavior.

  • 0 in reply to Hareesh Janakiraman
    TI__Expert 3580 points

    Hi Experts,

    Very thanks for your answer.

    But compared with the same S/W code, this phenomenon did not occur on the previous generation platform F2803x. Without adding CSM_Unlock, the connection of the emulator 1156 error will not happen. The customer questioned why F280049 has this phenomenon?

    I also refer the F2803x TRM, it also have ECSL as below figure.

  • 0 in reply to Shaoxing Ke
    TI__Guru* 95315 points

    Does customer code have passwords? Have the passwords been programmed in the OTP already? If so, the need to add CSM_unlock() in the Bootloader makes sense. It is hard to predict the behavior of the device that is partially programmed.

    The code security module is significantly different between the 2803x and 280049 device. 

  • 0 in reply to Hareesh Janakiraman
    TI__Expert 3580 points

    Hi Experts,

    Yes, customer code have passwords. and the passwords has been programmed in the OTP.

    Customer expect that the detailed significantly different between the 2803x and 280049 device? Do we have detailed document to help customer close this thread? Thanks.

  • 0 in reply to Shaoxing Ke
    TI__Guru* 95315 points
    Shaoxing Ke said:
    Yes, customer code have passwords. and the passwords has been programmed in the OTP.

    As mentioned earlier, if passwords have been programmed, the need to unlock makes sense.

    Shaoxing Ke said:
    Do we have detailed document to help customer close this thread?

    I don't understand your question. What kind of document are you expecting? We currently have the DCSM chapter in TRM and also the topic in C2000 Academy. We are planning a series of videos to make it easier to understand code security. These videos will be released over the course of next few months.

  • 0 in reply to Hareesh Janakiraman
    TI__Expert 3580 points

    Hi Experts,

    Got it, thanks for your answer!