• State
  • Locked Locked
  • Replies 3 replies
  • Subscribers 30 subscribers
  • Views 2462 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

Original question:

TMS570LS3137: Using XDS110 with gdb/openocd

TMS570LS3137: OpenOCD fails to halt the MCU when connecting

Ricardo Alejos
Prodigy 20 points
Part Number: TMS570LS3137

Hi,

I am trying to connect with the TMS570LS3137 MCU using OpenOCD. I've seen that some of the configuration files do not work "out-of-the-box" and have to be modified. Combining the advice from different related sources (including the past query: https://e2e.ti.com/support/tools/ccs/f/81/t/630450?TMS570LS3137-Using-XDS110-with-gdb-openocd

adapter_khz 1500

source [find interface/ftdi/xds100v2.cfg]
transport select jtag
source [find target/ti_tms570ls3137.cfg]

reset_config trst_only
init
ftdi_set_signal PWR_RST 1
jtag arp_init

But when I start OpenOCD, I get some errors suggesting that the JTAG chain is not healthy (IR value is not the expected one). 

$ openocd -f ./board/ti_tmdx570ls31usb.cfg
Open On-Chip Debugger 0.10.0
Licensed under GNU GPL v2
For bug reports, read
openocd.org/.../bugs.html
adapter speed: 1500 kHz

Info : to use this adapter you MUST add ``init; ftdi_set_signal PWR_RST 1; jtag arp_init'' to the end of your config file!

adapter speed: 1500 kHz
TI BE-32 quirks mode enabled
trst_only separate trst_push_pull
Info : clock speed 1500 kHz
Error: JTAG scan chain interrogation failed: all zeroes
Error: Check JTAG interface, timings, target power, etc.
Error: Trying to use configured scan chain anyway...
Error: tms570.jrc: IR capture error; saw 0x00 not 0x01
Warn : Bypassing JTAG setup events due to errors
Info : JTAG tap: tms570.jrc tap/device found: 0x3b8a002f (mfg: 0x017 (Texas Instruments), part: 0xb8a0, ver: 0x3)
Info : JTAG tap: tms570.dap enabled
Info : tms570.cpu: hardware has 6 breakpoints, 2 watchpoints
1

...

Moreover, if I start the GDB session then OpenOCD says it cannot halt the processor:

...

Info : accepting 'gdb' connection on tcp/3333
Error: Timeout waiting for halt


Error: Register map is not available yet, the target is not fully initialised
Error: Register map is not available yet, the target is not fully initialised
Error: Register map is not available yet, the target is not fully initialised

I am using the XDS100V2 adapter to make the connection. Do you have any advice?

Thanks in advance,

Ricardo A.

  • 0
    TI__Guru**** 464431 points

    Hi Ricardo,

    I can reproduce the issue. I'm still investigating and will keep you posted of any progress.

    Thanks

    ki

  • 0 in reply to Ki
    TI__Guru**** 464431 points

    Hi Ricardo,

    Sorry for the delay. This is a bit beyond my area of expertise so I had to do some digging. As mentioned I can reproduce the issue regarding the "unable to halt" error and the register map errors. I don't get your JTAG scan errors however. That is a bit concerning.

    I have escalated this issue to someone more knowledgeable. As I get updates, I'll be sure to update this thread.

    ki 

  • 0 in reply to Ki
    TI__Guru**** 464431 points

    Hi Ricardo,

    Both myself and a colleague have been trying to get this environment to work. We have been unsuccessful. We are getting the same register map error that you are getting. Basically after GDB establishes connection, it cannot halt the core. It is running free and hence the registers cannot be read. We are not sure how to resolve this as this is not a supported configuration by TI and is beyond our scope of expertise.

    There is a wiki with some information for openOCD on LS3137:

    https://rtime.felk.cvut.cz/hw/index.php/TMS570LS3137#OpenOCD_setup_and_Flashing

    Hopefully it can be useful.

    ki