• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 51 subscribers
  • Views 663 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.

Unable to start debug session for the stack on CC2640

Nick Alexeev
Intellectual 645 points
Other Parts Discussed in Thread: CCSTUDIO, CC2640

Folks,

This is related to the conversation here.  I've got this wish to run a CCStudio project on a CC2640, but I'm having little luck yet.

I'm starting with simlple_peripheral sample project.  I follow the instructions from SimpleLink Academy to build and debug.  As far as I understand, I have to load the stack first (steps 2 and 3), then I can load and debug the app.  Here's the odd thing.  I can start a debug session from the app just fine.  But I can't start a debug session for the stack.  I get this message.

Error connecting to the target:
(Error -151 @ 0x0)
One of the FTDI driver functions used during the connect
returned bad status or an error. The cause may be one or
more of: no XDS100 is plugged in, invalid XDS100 serial number,
blank XDS100 EEPROM, missing FTDI drivers, faulty USB cable.
Use the xds100serial command-line utility in the 'common/uscif'
folder to verify the XDS100 can be located.
(Emulation package 6.0.407.3)

Why do I get this message?  After all, it's the same debug probe (DevPack rev 1.3.0), the same target board, the same JTAG connection, the same CC2460.

Bonus question.  The CC26xx are multi-core parts.  How does the debugger know which core to run the app on, which core to run the stack on?

Any suggestion, insight or reference is really appreciated!

Cheers,
- Nick

CCStudio 6.1.3, BLE SDK 2.2.0, target is CC2640 inside SaBLE-x module

  • 0
    TI__Mastermind 34660 points
    Hello. You're not running two versions of CCS are you? If you can actually build and debug the application code, then i would recommend copying the debug settings from the application and using them from the stack. Of course, I can't see any reason why this isn't working to begin with so you may be better off just reinstalling the stack.

    Only the low-level PHY code is run on the M0. Any application / stack code that you can debug is on the M3.
  • 0 in reply to Tim C
    Intellectual 645 points

    Tim,

    Thanks for the tip!  I found the difference between the app and stack debug settings.  The app is set for XDS110.  The stacks is set for XDS100v3.  When I have switched the stack to XDS110, I can start a debug session for the stack.

    On a different note.

    Only the low-level PHY code is run on the M0. Any application / stack code that you can debug is on the M3.

    Hmm...  In that case, how do I get the low level M0 code into my CC2640?  Is it a separate CCStudio project (or a binary)?
    Or, does it come pre-programmed from the factory?  If it's pre-programmed at the factory, then I'm concerned about accidentally wiping out the M0 firmware.

    Cheers,
    - Nick

  • 0 in reply to Nick Alexeev
    TI__Mastermind 34660 points
    Well that's good news.

    Basically, you don't need to even think about the M0. It runs off ROM so you don't need to load anything and there is nothing you can do to erase / overwrite it.