[REOPENED] Can't connect to a CC2650 using a J-Trace

  • [REOPENED] Can't connect to a CC2650 using a J-Trace

    Hi, I'm trying to use a J-Trace to load code and debug a TI CC2650. I am getting a similar error message to the one listed in this thread:

    [SOLVED] CC2650 JLinkExe connection issue

    That issue was fixed with the Sep 8, 2015 release. However, the J-Trace I'm using, after updating the firmware, has firmware dated Sep 4:

    Source Code

    1. Firmware: J-Trace Cortex-M Rev.3 compiled Sep 4 2015 18:16:12
    2. Hardware version: V3.10


    Is having that firmware date expected? I have tried both using IAR and using J-Link Commander without success. Here's the error with J-Link Commander:

    Source Code

    1. Device "CC2650F128" selected.
    3. ****** Error: CC2538 (connect):Can not find ICE-Pick (IDCODE mismatch). Expected 0x0B00002F, found: 0xFFFFFFFF
    5. ****** Error: CC2538 (connect):Can not find ICE-Pick (IDCODE mismatch). Expected 0x0B00002F, found: 0xFFFFFFFF
    7. ****** Error: CC2538 (connect):Can not find ICE-Pick (IDCODE mismatch). Expected 0x0B00002F, found: 0xFFFFFFFF
    9. ****** Error: CC2538 (connect):Can not find ICE-Pick (IDCODE mismatch). Expected 0x0B00002F, found: 0xFFFFFFFF
    10. Can not connect to target.


    I tried using a coworker's I-jet in IAR, and it worked fine. Any suggestions?

  • Hi,

    Is having that firmware date expected

    Correct, Firmware: J-Trace Cortex-M Rev.3 compiled Sep 4 2015 18:16:12 is the most recent firmware for J-Trace Cortex-M Rev 3.
    The issue was located in the J-Link PC Software, not the firmware.

    Could you provide us with a J-Link logfile?
    Log output can be enabled like as follows:
    • Open a connection to J-Link, e.g start J-Link Commander
    • In J-Link Control Panel: (Click the J-Link symbol located in the notification / tray area in order to open J-Link Control panel)
    • Open the tab "Settings"
    • Next to the field "Log file" check "Override" and click "..." in order to choose a log file path.

    This is also described in UM8001 Chapter 5 "Working with J-Link and J-Trace", Section 5.7 "J-Link control panel" .

    Best regards,
    Niklas
    Please read the forum rules before posting.

    Keep in mind, this is *not* a support forum.
    Our engineers will try to answer your questions between their projects if possible but this can be delayed by longer periods of time.
    Should you be entitled to support you can contact us via our support system: segger.com/ticket/
    Or you can contact us via e-mail.

  • The issue was located in the J-Link PC Software, not the firmware.
    That's what I was wondering. Thanks.

    I tried to connect using JTAG instead of SWD in J-Link Commander, and now it worked (I think I tried before and it didn't). However, the first time after I plug the J-Trace in, it still fails to connect using IAR. After the first try, I can download code and debug. Previously, I tried over and over, and I know it wouldn't work in IAR. I don't know why it will work except for the first time now. I am fine if it doesn't work the first try, but I've attached a log in case you want to see it.
    FailedFirstTry.txt

    I still have another problem. When I click "Break" in IAR, I get an error that the "CPU could not be halted" and then debugging ends. I have attached a log of when I tried.
    HaltAttempt.txt

  • Hi,


    sorry for the delay in response.
    Could you please download & install the latest version of the J-Link software & documentation pack (V5.10q) and use the integrated DLL Updater in order to update the DLL used by IAR EWARM?

    You can check the version IAR EWARM is using by taking a look at the Debug Log:


    Best regards,
    Niklas
    Please read the forum rules before posting.

    Keep in mind, this is *not* a support forum.
    Our engineers will try to answer your questions between their projects if possible but this can be delayed by longer periods of time.
    Should you be entitled to support you can contact us via our support system: segger.com/ticket/
    Or you can contact us via e-mail.

  • A coworker was doing most of the work on our project using the CC2650, so it wasn't as important that I get the J-Trace working great. However, he is no longer working on it, so I'm back to using the J-Trace and still having problems (although J-Trace works great with the ST processors I usually use it with).

    Today I have been trying, but I have not managed download code onto the chip once. I updated to the newest J-Link software pack and updated the firmware on the J-Trace, and I still can't download code. I can use an I-jet fine, so I'm reasonably sure the connection is good. A dialog asks 4 times whether it should unlock/unsecure the device, and I've tried both ways without success. Here's the IAR log:

    Source Code

    1. Mon Oct 17, 2016 22:58:38: Loaded macro file: D:\Programs\IAR Systems\Embedded Workbench 7.4\arm\config\debugger\TexasInstruments\CC26xx.dmac
    2. Mon Oct 17, 2016 22:58:38: Loaded macro file: D:\Programs\IAR Systems\Embedded Workbench 7.4\arm\config\flashloader\TexasInstruments\FlashCC26xx.mac
    3. Mon Oct 17, 2016 22:58:38: JLINK command: ProjectFile = D:\Projects\Removed\Firmware\trunk\settings\Removed_Debug.jlink, return = 0
    4. Mon Oct 17, 2016 22:58:38: Device "CC2650F128" selected.
    5. Mon Oct 17, 2016 22:58:38: DLL version: V6.10f, compiled Oct 17 2016 17:41:18
    6. Mon Oct 17, 2016 22:58:38: Firmware: J-Trace Cortex-M Rev.3 compiled Sep 1 2016 18:34:36
    7. Mon Oct 17, 2016 22:58:38: JTAG speed is initially set to: 1000 kHz
    8. Mon Oct 17, 2016 22:58:38: Performing HIB
    9. Mon Oct 17, 2016 22:58:40: Performing HIB
    10. Mon Oct 17, 2016 22:58:41: Performing HIB
    11. Mon Oct 17, 2016 22:58:42: Performing HIB
    12. Mon Oct 17, 2016 22:58:44: Fatal error: Device specific connect: Can not find CPU TAP (IDCODE mismatch) Session aborted!
    13. Mon Oct 17, 2016 22:58:44: Unloaded macro file: D:\Programs\IAR Systems\Embedded Workbench 7.4\arm\config\flashloader\TexasInstruments\FlashCC26xx.mac
    Display All


    It also fails to connect when I try J-Link Commander. Here is a log from it:

    FailureToConnect.txt

    Any help is appreciated.

  • Hi,

    according to the Log file, SWD is selected as interface in IAR:

    C Source Code

    1. T1AA4 023:017 JLINK_TIF_Select(JLINKARM_TIF_SWD) returns 0x00 (0003ms, 0021ms total)

    Could you please select JTAG and give it a try?

    Best regards,
    Niklas
    Please read the forum rules before posting.

    Keep in mind, this is *not* a support forum.
    Our engineers will try to answer your questions between their projects if possible but this can be delayed by longer periods of time.
    Should you be entitled to support you can contact us via our support system: segger.com/ticket/
    Or you can contact us via e-mail.

  • Unfortunately, as you can see below, that option is disabled in the settings, and I don't know why. I have tried changing a couple other settings to see if the option would get enabled, but without success. I'm using IAR 7.60.1.



    EDIT: In case you want me to try JTAG in J-Link Commander, here's a log (I tried both SWD and JTAG earlier, but only posted the SWD log):

    FailureToConnectJTAG.txt

    The post was edited 1 time, last by jminer ().