• State Resolved
  • Locked Locked
  • Replies 6 replies
  • Subscribers 57 subscribers
  • Views 1654 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.

LAUNCHXL-CC1312R1: Can't connect using OpenOCD

Jose Simoes
Intellectual 460 points
Part Number: LAUNCHXL-CC1312R1

Hi,

I'm trying to connect to a LAUNCHXL-CC1312R1 using OpenOCD.

The cmd line I'm using is "openocd -f board/ti_cc13x2_launchpad.cfg"

This is the output I get from OpenOCD:

GNU MCU Eclipse 64-bit Open On-Chip Debugger 0.10.0+dev-00462-gdd1d90111 (2019-01-18-11:42)
Licensed under GNU GPL v2
For bug reports, read
        openocd.org/.../bugs.html
adapter speed: 2500 kHz
srst_only separate srst_gates_jtag srst_open_drain connect_deassert_srst
adapter_nsrst_delay: 100
Info : Listening on port 6666 for tcl connections
Info : Listening on port 4444 for telnet connections
Info : XDS110: connected
Info : XDS110: firmware version = 3.0.0.2
Info : XDS110: hardware version = 0x0023
Info : XDS110: connected to target via JTAG
Info : XDS110: TCK set to 2500 kHz
Info : clock speed 2500 kHz
Info : JTAG tap: cc13x2.jrc tap/device found: 0x5768205f (mfg: 0x02f (ACTEL), part: 0x7682, ver: 0x5)
Warn : JTAG tap: cc13x2.jrc       UNEXPECTED: 0x5768205f (mfg: 0x02f (ACTEL), part: 0x7682, ver: 0x5)
Error: JTAG tap: cc13x2.jrc  expected 1 of 1: 0x0bb4102f (mfg: 0x017 (Texas Instruments), part: 0xbb41, ver: 0x0)
Info : TAP auto0.tap does not have IDCODE
Error: Trying to use configured scan chain anyway...
Error: cc13x2.jrc: IR capture error; saw 0x03 not 0x01
Warn : Bypassing JTAG setup events due to errors
Info : Listening on port 3333 for gdb connections

When connecting from gdb it fails because the connection is refused.

Any ideas?

Thanks!

  • 0
    TI__Mastermind 27145 points

    Hi,

    I sent it to a concerned engineer. We will get back to you ASAP. Please bear with us.

    Thanks,

    PM

  • 0
    Prodigy 110 points

    I was having the same problem and manged to solve it by doing the following:

    - first mounted the XDS jumpers

    - then I flashed an example application on it using Code Composer Studio, where it asked to do an update on the firmware

    After that I went back to using OpenOCD and it was working.  My guess is that the fw update did the trick but I am

    not really sure. Not an expert... still hope that helps you.

    IAr

  • 0 in reply to IAr
    Intellectual 460 points

    thanks for your suggestions!

    A couple of questions, please:

    - Where are the XDS jumpers on this board? Can only find the JTAG and power ones...

    - What is the XDS firmware version that you have now your board?

  • 0 in reply to Jose Simoes
    Prodigy 110 points

    no problem.

    - About the firmware version, it is the following:  "XDS110: firmware version = 2.3.0.14"

    - The XDS jumper block is the one that runs horizontal and indeed it has the JTAG signals on it, TDO, TDI, TMS and TCK.

    Maybe the following link can show you which one I mean better  (check the section called  "Advanced use of the LaunchPad hardware" )

  • 0 in reply to IAr
    Intellectual 460 points

    thanks again! You've put me on the right track.

    FYI, my board now has:

    XDS110: firmware version = 3.0.0.5

    After updating the board XDS probe firmware the issue kept showing.

    I did some more research and after some trial and error, found out that the root cause was with the JTAG clock speed.

    Seem that 2500kHz is too much for the CC13x2 boards. I had to slow it down.

    My OpenOCD command now look like this:

    openocd.exe -f board/ti_cc13x2_launchpad.cfg -c "adapter_khz 2000"
    DGB can now happily connect to the board, flash and run a debug session.
    Maybe this is something that should be addressed by TI OpenOCD team possibly by tweaking the relevant config files for these targets...
    Anyways, thank you very much again! :) 
  • 0 in reply to Jose Simoes
    TI__Intellectual 2515 points

    I am working on updating our OpenOCD support to correct this issue.  Here's a bit more information about what happened:

    The previous firmware for the XDS110 only supported a max TCK frequency of 2500 kHz. We recently updated the low level scan routines beginning with firmware version 3.0.0.x, and we can now drive TCK at up to 14000 kHz.  The host side code to set the rate also needs an update to understand the new range, and using the current setting of 2500 kHz is actually giving the maximum rate.  The value of 2000 kHz is selecting about 8500 kHz in the new firmware.

    So OpenOCD will be getting an update to understand how to correctly set the frequency requested, and the workaround will no longer be necessary.