TMS570LS0432: debugger issue

Hi Sachin,

Please first check the reference below that helps thoroughly check the various scenarios where the connection issues can happen:

https://software-dl.ti.com/ccs/esd/documents/ccsv7_debugging_jtag_connectivity_issues.html

Do you have any code running in your TMS570 MCU? 

Hello Qj Wang,

Yes! code is running on MCU. Reprogrmme is not working!

This problems happens only when programme is downloaded & made to run. After applying run, it comes to sort of suspend mode where it does not run application. next step if i terminate & reprogramme then i see above message. 

I think connectivity wise : should not be an issue. with same setup i can run other code on board whci has same MCU.

So, issue- programme is running which is casuing some issue & not letting reprogramme MCU.

Best regards,
Sachin

folowing above procedure; i get following mesage. I also tried on two boards. Any other suggestion?

Its very critical issue. Is it possible if we can do telecon ?

Best regards,
Sahcin

IcePick: Error connecting to the target: (Error -2131 @ 0x0) Unable to access device register. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 9.4.0.00129)
CortexR4: Error connecting to the target: (Error -242 @ 0x0) A router subpath could not be accessed. The board configuration file is probably incorrect. (Emulation package 9.4.0.00129)
IcePick: Error connecting to the target: (Error -2131 @ 0x0) Unable to access device register. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 9.4.0.00129)
IcePick: Error connecting to the target: (Error -2131 @ 0x0) Unable to access device register. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 9.4.0.00129)
CortexR4: GEL Output: Memory Map Setup for Flash @ Address 0x0CortexR4: Failed CPU Reset: (Error -2063 @ 0x0) Unable to reset device. Power-cycle the board. If error persists, confirm configuration and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 9.4.0.00129)
CortexR4: Error: (Error -242 @ 0x0) A router subpath could not be accessed. The board configuration file is probably incorrect. (Emulation package 9.4.0.00129)
CortexR4: Error: (Error -1170 @ 0x0) Unable to access the DAP. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 9.4.0.00129)
CortexR4: Unable to determine target status after 20 attempts
CortexR4: Failed to remove the debug state from the target before disconnecting. There may still be breakpoint op-codes embedded in program memory. It is recommended that you reset the emulator before you connect and reload your program before you continue debugging
CortexR4: GEL: Error while executing GEL_Reset(): Reset failed: retcode=-1
at GEL_Reset()
CortexR4: Error initializing flash programming: Could not read register CPSR: target is not connected
CortexR4: GEL Output: Memory Map Setup for Flash @ Address 0x0CortexR4: Failed CPU Reset: (Error -2063 @ 0x0) Unable to reset device. Power-cycle the board. If error persists, confirm configuration and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 9.4.0.00129)
CortexR4: Error: (Error -242 @ 0x0) A router subpath could not be accessed. The board configuration file is probably incorrect. (Emulation package 9.4.0.00129)
CortexR4: Error: (Error -1170 @ 0x0) Unable to access the DAP. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 9.4.0.00129)
CortexR4: Unable to determine target status after 20 attempts
CortexR4: Failed to remove the debug state from the target before disconnecting. There may still be breakpoint op-codes embedded in program memory. It is recommended that you reset the emulator before you connect and reload your program before you continue debugging
CortexR4: GEL: Error while executing GEL_Reset(): Reset failed: retcode=-1
at GEL_Reset()

HI Sahcin,

The only way to solve this kind of  problem is to repeat the procedure in my last post. nRTS is the system reset pin of MCU.

Can you share the code which is running in your MCU? 

QJ Wang,

Yes, i can share code. How ?

We are in big issue as it not allowing me to develop code. Changing mcu chip is also not an option. So we have got stuck.

Kindly advise!

Best Regardsm
Sachin

Hi Sachin,

You can upload the code to e2e if possible. If not, please send me a private message with the code. Thanks

Adlex_TMS57004_BQ79600_BQ79616_SPIv1.zip

pls check its issue of XDS200 debug probe. Does it work for XDS100v2?

I will check it on TMS570LS043x launchpad with xds100v2.

Hello QJ wang,

Any update on issue ?

best regards,

sachin

After loading your code to my TMS570LS0432x launchpad, the JTAG connect is lost. I am not able to connect JTAG to the device. 

I will investigate the problem today. 

Sorry, I sued a wrong launchpad. The device on my launchpad is TMS570LS0232PZ. 

I tested your project on my LS0432x board, it works OK.

It is running in the while() loop, and printing the message in the console: board 1: 12.499491 ....

Did you also tested using xds200probe?

Hi Sachin,

I am sorry the launchpad doesn't a JTAG header for xds200probe. 

Is the code running on your MCU exactly same as the code you gave me? 

The behavior looks like the CPU enters the exception repeatedly. 

Hello QJ Wang,

I dont find " ICEPick_C". 

I see above situation. i see below resiter view for icepick:

For Dap; this is how resister view looks like:

I am not able to connect DAP.

Pls suggest - what i can try next.

Best Regards,
Sachin

Yes, its same behavior. I am not able programme MCU! Kindly suggest how cna i solve issue?

The value of the most of the core registers in your post are zero, which means the registers are not read or accessed.

The value of the core registers in my test are not zero:

To be honest, I don't know what causes this issue. Don't you have another board?

No, i tried on 3-4 boards & all are in same condition now. all boards mcus have got into this mode & hence i am very afraid for next step. 

I need TI help to solve this issue, otherwise i dont know what option i have! PLs let me know your feedback.

any suggestion- what i can do our work has got stcuk by this issue?

If you use xds200, please lower the JTAG speed, and try again. 

If possible, please probe the JTAG signals (TCK, TMS, TDI, TDO, and nTRST). Is the nERROR pin asserted (LOW)? To be honest, I don't know what happened to your board.