- Ask a related questionWhat is a related question?A related question is a question created from another question. When the related question is created, it will be automatically linked to the original question.
Original question:
TMS320F28377D: DCSM change from EMUBOOT flash boot to wait boot
Hello,
I am having issue connecting JTAG XDS110 to the F280049 MCU after burning OTP:
The application I wrote runs, but I can no longer access it with the debugger. I need to change the application and I cannot do anything. Error message: `Error connecting to the target: (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.9.0.00040)`
I can say that the power supply is quite good and there are no problems with real power.
Thus, I cannot even unlock the MCU using the correct password (when I write a proper password and click Unlock button in the UniFlash, it gives me the same error).
It seems I have a similar problem described in TRM:
When initially debugging a device with the password locations in OTP programmed (secured), the emulator takes some time to take control of the CPU. During this time, the CPU will start running and may execute an
instruction that performs an access to a protected ECSL area and if the CPU is halted when the program counter (PC) is pointing to a secure location, the ECSL will trip and cause the emulator connection to be broken.
The solution to this problem is:
• Use the Wait Boot Mode boot option. In this mode, the CPU will be in a loop and hence will not jump to the user application code. Using this BOOTMODE, the user can connect to CCS and debug the code.
There are 2 questions:
