• State Resolved
  • Locked Locked
  • Replies 7 replies
  • Answers 1 answer
  • Subscribers 16 subscribers
  • Views 3355 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

SmartRF Flash Programmer 2 fail to read target memory

Dorian Levy
Intellectual 610 points
Other Parts Discussed in Thread: UNIFLASH

We have made a custom board using a 2640 MCU. I am using the XDS110 out from a 2650 Launchpad to connect to the board. SmartRF recognizes the chip as a 2640, but gives "Debug interface locked" message and suggests a Forced Mass Erase. Here is the output from the mass erase:

>Initiate access to target: XDS-L1000334.

>Failed to read target memory.

>Error while reading memory range. Address 0x40091090.

>Start flash erase ...

>Erase finished successfully.

Trying to read after that gives:

>Reset target ...

>Reset of target successfull.

>Initiate access to target: XDS-L1000334.

>Failed to read target memory.

>Error while reading memory range. Address 0x40091090.

>Debug interface is locked. Aborting action. Only forced mass erase is possible.

>Reset target ...

>Reset of target successful.

>failed to get serial number

The mass erase does not seem to be executing properly. I saw in another thread to check the current draw and VDDR and Decouple voltages. VDDR was 1.68V, DEcouple was 1.28V and current was 5.7mA.

  • 0
    TI__Mastermind 20480 points
    Just for my sanity:
    Are you cross-connecting from your custom board to the LP's debugger?
    What pins are you connecting? Can you verify that you are connecting all the pins referenced by the LP's schematics?

    Tom
  • 0 in reply to Tom Kopriva
    Intellectual 610 points

    Yes I am cross connecting to the LP debugger. I Have disconnected all the jumpers that connect the debugger to the chip on the LP and am connecting to the following pins. GND, 3V3, TXD, RESET, TMS, TCK.

  • 0 in reply to Dorian Levy
    TI__Mastermind 20480 points

    Dorian,

    I just tried Flash Programmer 2 while only connecting the pins you listed (on the Launchpad).

    The Launchpad uses an XDS110 debugger. To me, it looks like Flash Programmer 2 is only using the 4-wire JTAG interface with the Launchpad; not the 2-wire cJTAG. And from what I can see, Flash Programmer 2 doesn't support 2-wire cJTAG with the XDS110 (or at least doesn't give that option).

    When using the Launchpad, I was only able to connect to the target when also making the TDI and TDO connections. Is that something you can try on your custom board?

    With that said, I am able to connect with CCS (or IAR) in 2-wire cJTAG mode via the Launchpad without the need of the TDI or TDO pins. If the goal is to debug the device, you should be able to continue w/ CCS (or IAR). If the goal is to simply program the device, using the pins you've listed in your previous post, you may want to look into the Uniflash tool instead of Flash Programmer 2.

    Shown below is a screenshot on how to set to 2-wire cJTAG in a CCS .ccxml target configuration file. The .ccxml file is used in both CCS and Uniflash.

  • 0 in reply to Tom Kopriva
    Intellectual 610 points

    I am able use the XDS110 on the Launchpad with just the two wire. I followed these steps from a different post

    It actually does support 2-pin cJTAG, but you will need to tweak a file in the installation (we haven't enabled a GUI option to select this, unfortunately). Here's what you need to do:

    1. Exit SmartRF Flash Programmer 2

    1. Go to C:\Program Files (x86)\Texas Instruments\SmartRF Tools\Flash Programmer 2\config\xds\board_config

    2. Rename xds110.dat to e.g. xds110.dat.bak (to keep a backup)

    3. Copy the attached file (link below) into the directory (xds110c2.dat)

    4. Rename xds110c2.dat to xds110.dat.

    5. Restart Flash Programmer.

    It will now operate in 2-pin cJTAG mode.

    xds110c2.dat

  • 0 in reply to Tom Kopriva
    Intellectual 610 points
    I tried using Uniflash and got the following:
    [9/14/2016, 10:51:28 AM] GEL: Cortex_M3_0: GEL Output: Memory Map Initialization Complete.
    [9/14/2016, 10:51:37 AM] GEL: Cortex_M3_0: MassErase(): Initializing.
    [9/14/2016, 10:51:37 AM] GEL: Cortex_M3_0: MassErase(): Issuing Board Reset.
    [9/14/2016, 10:51:38 AM] GEL: Cortex_M3_0: MassErase(): Mass erase complete.
    [9/14/2016, 10:51:43 AM] GEL: Cortex_M3_0: GEL Output: Memory Map Initialization Complete.
    [9/14/2016, 10:51:45 AM] Status: CS_DAP_0: Error connecting to the target: (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 6.0.407.3)
  • 0 in reply to Dorian Levy
    TI__Mastermind 20480 points
    Dorian,

    I've moved this thread to the tools forum where you will find folks with more expertise on this subject matter.
  • 0
    Intellectual 610 points
    I found the mistake. I didn't have the VSENSE connected on the Launchpad.