• State TI Thinks Resolved
  • Locked Locked
  • Replies 5 replies
  • Answers 1 answer
  • Subscribers 56 subscribers
  • Views 1349 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.

CCS/CC2640R2F: Trouble connecting putty to output

Olive Garst
Prodigy 30 points
Part Number: CC2640R2F


Tool/software: Code Composer Studio

I'm new to CCS and this board. I recently changed around my files on my computer which I believe is the problem here. I used to be able to load simple peripheral or project zero onto the board and turn the LEDs on and off from different apps (nRF Connect, TI sensortag, etc). I also used to be able to see connection data on putty. I rearranged my files, but recopied my workspace files where they were before. Now I can flash the board, but no data is written to putty and I can no longer change the LED values or register button pushes. When the board flashes the CCS output is:

Cortex_M3_0: GEL Output: Memory Map Initialization Complete.

Cortex_M3_0: GEL Output: Board Reset Complete

Any help would be appreciated!

  • 0
    Guru 42195 points

    Are you sure you are telling putty the correct serial port?

    Does the terminal work inside CCS?

  • 0 in reply to Keith Barkley
    Prodigy 30 points

    Keith - Thanks for your reply. The terminal is not showing anything inside CCS and I also cannot discover the device via bluetooth on my phone or tablet as it was before.

  • 0 in reply to Olive Garst
    TI__Mastermind 40600 points

    Hi Olive,

    I'm assigning your post to an expert to assist. 

    It may be good to mass erase your device and then flash it again with the prebuilt Project 0 hex and retest though. If this isn't successful, i think you would need to load the project and use the debugger to assess if the device is in a spin lock or something. 

  • 0 in reply to Evan W
    Prodigy 30 points

    Hi Evan -

    Thanks. I did that and it seems as if Project 0 works fine and what I'm attempting to do (add a characteristic to a service for BLE applications) is causing the problem and sending this error:

    Error initializing emulator:
    (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 XDS110SupportReadMe.pdf
    file there for instructions.
    (Emulation package 9.2.0.00002)

  • 0 in reply to Olive Garst
    TI__Genius 17265 points

    Hi Olive,

    You can find some information about this error on the TI Resource Explorer located at Dev.ti.com if you go to Development Tools->Debug Probes->XDS->Documents->JTAG_Debugger Connectivity Issues. If you then look for the error you have (-260) we can see that this issue is likely caused by a faulty USB connection. In order to isolate where the issue is, I've listed a few steps below that you can try. I've ordered them from least-complex to most-complex to make it easier for you. 

    1. Try a different USB port on the host computer. This is pretty unlikely to be the issue, but it's worth a try due to how simple it is.

    2. Try a different cable to connect your computer to the board.

    3. Try a different board/launchpad, if you have one. This will help determine whether the board was damaged.

    4. Open the document named "XDS110SupportReadMe.pdf" located at **Your CCS Install location**\ccs\ccs_base\common\uscif\xds110 . In this document there is a section titled "Recovering a Bricked XDS110 without JTAG". Try following these steps to try to recover the XDS110 device located on your board.

    Best Regards,
    Alec M