• State TI Thinks Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 55 subscribers
  • Views 715 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.

Original question:

CCS/TMDSEMU110-U: Error in connecting device, while debugging using XDS110 debugger

CCS/TMDSEMU110-U: Error in connecting device, while debugging using XDS110 debugger

Shubham Mittal
Expert 1135 points

Part Number: TMDSEMU110-U
Other Parts Discussed in Thread: UNIFLASH, CC3200

Tool/software: Code Composer Studio

Hello all,

In continuing with my earlier post:-

https://e2e.ti.com/support/development_tools/code_composer_studio/f/81/t/689764

Now, i am facing a strange problem.

I am able to debug the TI examples with the help of debugger but when i try to debug my own firmware it starts giving an error, 

Unable to communicate with the device. Please check your connection.


Any idea about this problem because i believe if it is working for particular firmware then it must also work for other firmware.

Thank You

Shubham

  • 0
    TI__Guru**** 171399 points

    Shubham,

    When the error happens, are you flashing the board (using Uniflash) or simply loading the code to the device via CCS? The difference between the two methods is the SOP jumper placement, which can prevent one or another operation from succeeding. 

    If you are simply loading via CCS, after the problem happens can you power cycle the board and load and debug the TI examples normally? If so, does the error happen immediately after you load your firmware? The thread below shows some tips to debug early stages after the code loading

    https://e2e.ti.com/support/development_tools/code_composer_studio/f/81/t/671504 

    If the issue happens after the main() is reached, my suspicion is that your firmware may be locking you out of the JTAG (by reconfiguring pins for different functions, for example) or causing the device to reset continuously and collapsing its execution. I am notifying the CC3200 experts that may shed some light into what device settings may influence that.  

    Regards,

    Rafael

  • 0 in reply to desouza
    TI__Mastermind 45606 points
    Hi Shubham,

    Rafael has some good initial debug steps to take and I'd be interested in hearing your feedback after checking them.

    Related to the JTAG, the device pins you would not want to reconfigure are 16 (TDI), 17 (TDO), 19 (TCK), and 20 (TMS). Check your firmware and make sure you don't reconfigure these pins dynamically.

    Are you going into any low power modes in your firmware? Going into LPDS, or a lower power state, will cause your JTAG to disconnect and you won't be able to debug within CCS while the device is in the low power state.

    Best,
    Kevin
  • 0 in reply to Kevin Allen18
    Expert 1135 points
    Hi Rafael & Kevin,

    Thanks for your reply.

    I was able to resolve the issue.
    Actually issue was not related to the hardware setings. It was related to the wrong configuration settings. I was changing my connection type in the configuration file under view->target configurations but it was not effective. Then in the project directory i found that there is target config folder and checked the .ccxml file under this folder. I found settings in that config file was different. I changed the settings and its start working.

    Regards
    Shubham