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.

TIDA-00002: MCU has locked out, cannot erase chip or download to flash

Part Number: TIDA-00002
Other Parts Discussed in Thread: SEGGER

Hello,

I am receiving an error code -1 on the J-Link Commander when I try an erase chip command. 

I cannot connect to the target using J-Link Flash as the clock frequency can't be detected.

I am generating the clock signal using a function generator at 5MHz 1.8V. 

Any ideas how I can gain control again?

Many thanks

  • Any ideas how I can gain control again?

    Hi,

      Your post was initially posted to the simulation forum and just got re-routed to us. However, I'm also not familiar with this device myself. Your comment seems to suggest that you were able to access the target at one point of time and somehow failed to do so later on. Is this a correct understanding? 

      Can you lower the TCK speed? Which debugger are you using? In CCS, you should be able to lower the TCK frequency. Will that make a difference?

      I will also suggest you contact Segger for support on the Jlink error code -1. I'm also not familiar with the error code. 

  • Hi Charles,

    Correct, the MCU currently has the last program that I downloaded to the flash and it still runs. However the device can no longer be downloaded to.

    I am not using CCS as it is not possible to debug this MCU with CCS, I am using IAR can you provide any more details on how to lower the TCK frequency with this?   

  • Hi Martin,

      How long ago was the last program downloaded? Was it a long time ago (.e.g. months or years) and you are now trying to reprogram again? Or it was working until you programmed something into the flash and afterward you cannot connect/program anymore? I just wanted to know if this something that was programmed to the MCU that caused the problem. I have seen cases (for different MCUs) where a program that requests MCU to go into sleep without a mechanism to wakeup. Once the MCU is in sleep, the debugger can no longer connect to the target via JTAG interface. Hopefully, this is the not the case for your problem. 

      I have no experience with this board and neither IAR toolchain. If you use CCS and depend on which debug probe you use to connect to the target, there is option to change the TCK speed. See below for CCS on a different device where you can change the TCK frequency. The CCS also has utility to test the JTAG scan chain. I tend to believe IAR will have similar capabilities. However, you really need to reach out to IAR for this. 

    Although I have no knowledge about this board, I can recommend you to check if all the voltages are proper on the board and if you see any activities on TCK, TDI and TDO interface? Another thing to check  is if you have another J-LINK debug probe that you can try? Will both debug probes have the same problem?