CC3200 Launchpad SWD

Sysprogs forums Forums VisualGDB CC3200 Launchpad SWD

Viewing 5 posts - 1 through 5 (of 5 total)
  • Author
    Posts
  • #8985
    ciaranmaca
    Participant

    Hi,

    I have JTAG connectivity working well with my CC3200 Launchpad (FTDI 2232 based debug connectivity). I want to switch to SWD to save pins. How can I do this?

    I tried adding ‘transport select swd’ to one of my scripts but it also needed me to switch the jtag tap commands to ‘swd’  (and of course set the SOP settings right on my board). But I get errors in openocd. “ession transport is “swd” but your config requires JTAG” etc.

    Any one done this?

    Ciarán

     

    #8993
    support
    Keymaster

    Hi,

    Have you tried explicitly selecting the SWD transport in the VisualGDB Project Properties window?

    #9003
    ciaranmaca
    Participant

    Hi,

    No, that didn’t work either. I get the following error:

    Ciarán

     

    ^error,msg=”-var-assign: Could not assign expression to variable object”
    -exec-continue
    ^error,msg=”Warning:\nCannot insert breakpoint 1.\nCannot access memory at address 0x20004ac8\n”

    — GDBServer output —
    Open On-Chip Debugger 0.9.0 (2016-09-01) [https://github.com/sysprogs/openocd]

    Licensed under GNU GPL v2

    For bug reports, read

    http://openocd.org/doc/doxygen/bugs.html

    adapter speed: 1000 kHz

    jtag

    adapter_nsrst_delay: 100

    jtag_ntrst_delay: 100

    cortex_m reset_config sysresetreq

    VisualGDB_OpenOCD_Ready

    Info : clock speed 1000 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: cc3200.jrc: IR capture error; saw 0x00 not 0x01

    Warn : Bypassing JTAG setup events due to errors

    Info : accepting ‘gdb’ connection on tcp/63987

    undefined debug reason 7 – target needs reset

    Error: Target not examined yet

    Error: Target not examined yet

    Error: Target not examined yet

    Error: Target not examined yet

    Error: Target not examined yet

    Error: JTAG scan chain interrogation failed: all zeroes

    Error: Check JTAG interface, timings, target power, etc.

    Error: Trying to use configured scan chain anyway…

    #9036
    support
    Keymaster

    Hi,

    We have rechecked the OpenOCD support for FTDI and CC3200 and it looks like the current FTDI configuration files do not support the SWD signals yet.

    There are third-party articles describing how to define them, but we have not retested those instructions. We would expect the OpenOCD maintainers to update the configuration files in the next few releases.

    Also if you encounter errors like “The current target requires JTAG”, please try switching OpenOCD to manual configuration mode and replacing the cc3200.cfg script with the cc32xx.cfg.

    If this does not help, please let us know.

    #9038
    ciaranmaca
    Participant

    Hi,

    Thanks for the reply. Yes, I set the target to cc32xx.cfg and that got me partly there. I still hard an error about signal definitions. But taking inspiration from the gcc scripts in the tools folder of the TI SDK for CC3200 I added these two lines to the interface/ftdi/cc3200lp.cfg script:

    # Add for SWD
    ftdi_layout_signal SWD_EN -ndata 0x0080
    ftdi_layout_signal SWDIO_OE -data 0x0008

    And hurray, it works.

    Thanks for your help. I consider the issue resolved.

    Ciarán

Viewing 5 posts - 1 through 5 (of 5 total)
  • You must be logged in to reply to this topic.