• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Subscribers 52 subscribers
  • Views 657 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.

CC2640R2F: DevPack XDS110 debugger after migrating to CC2640R2F

Zaffer Merchant
Intellectual 515 points
Part Number: CC2640R2F
Other Parts Discussed in Thread: CC2640,

We have been using CCS and the DevPack XDS110 Debugger to flash our CC2640 device. We have ported and successfully built our code using the R2 SDK but unfortunately we cannot test it since the R2 Launchpad is out of stock. And when we try to flash the new CC2640R2 board we get an error when connecting with the flash programmer (btw we just swapped the cc2640 with the cc2640R2)

Before we spend a lot of time debugging HW, do you know if the DevPack XDS110 will work with the CC2640R2 device? (the R2 Launchpad also has the XDS110)

Thanks, Zaffer

  • 0
    Intellectual 515 points
    We found the problem, HW related. We can now build, flash and run our code on the R2

    Thanks!
  • 0 in reply to Zaffer Merchant
    TI__Guru 55305 points
    Glad you solve the issue!
  • 0 in reply to Zaffer Merchant
    Intellectual 345 points

    Hi Zaffer,

    Edit: Disregard my question, the example projects included in BLE Stack 3.0 use XDS110, but we are actually using XDS100v3's. Once I modified the project to use the correct debugger everything worked.

    If you're able to, and don't mind, could you elaborate on what your issue was? I'm also trying to migrate from the CC2640 to the CC2640R2F but I get the following error when trying to connect the debugger:

    Cortex_M3_0: GEL Output: Memory Map Initialization Complete.
Cortex_M3_0: Failed Board Reset: (Error -260 @ 0x0) An attempt to connect to the XDS110 failed. The cause may be one or more of: no XDS110 is connected, invalid firmware update, invalid XDS110 serial number, or faulty USB cable. The firmware and serial number may be updated using the xdsdfu utility found in the .../ccs_base/common/uscif/xds110 directory of your installation. View the ReadMe.txt file there for instructions. (Emulation package 6.0.504.1) 
IcePick_C: Error connecting to the target: (Error -260 @ 0x0) An attempt to connect to the XDS110 failed. The cause may be one or more of: no XDS110 is connected, invalid firmware update, invalid XDS110 serial number, or faulty USB cable. The firmware and serial number may be updated using the xdsdfu utility found in the .../ccs_base/common/uscif/xds110 directory of your installation. View the ReadMe.txt file there for instructions. (Emulation package 6.0.504.1)

    So far we've tried swapping the parts on two of our production boards, and neither of them will work with our debugger (which I verified still works with the CC2640). What's also strange is that I'm able to program our firmware image using Flash Programmer 2, but not with CCSv7 (I don't think it's a CCSv7 issue since the CC2640 still works).

    Thank You,
    Josh

  • 0 in reply to Josh Lubawy
    Intellectual 515 points

    We had been using the Flash Programmer with DevPack XDS110 to flash our CC2640 target board, but after swapping the R2, the Flash programmer could not detect the CC2640 on the target with either the DevPack or the LaunchPad R2. Turned out one of the power distribution discretes on the board got damaged when the IC was swapped and replacing the component fixed the problem. We are now also able to flash the target using CCSv7. You might want to try a DevPack or Launchpad R2 to flash your target.

    Also to isolate the problem quickly we ported a simple LED test program rather than our entire code. We are in process of porting our code now.

    Zaffer