• State Answer Suggested
  • Locked Locked
  • Replies 6 replies
  • Answers 1 answer
  • Subscribers 56 subscribers
  • Views 526 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/LAUNCHXL-F280049C: error initializing emulator

Viktorija Cecil
Mastermind 18501 points
Part Number: LAUNCHXL-F280049C
Other Parts Discussed in Thread: BOOSTXL-DRV8320RS

Tool/software: Code Composer Studio

Team, 

My customer is having an issue with debugger:

I am having trouble with debugger on LaunchXL-F280049C. It works when BoostXL-DRV8320RS is not plugged in. After I plug in BoostXL-DRV8320RS it doesn’t. I get this error:

My CCS version is 9.3.0.00012. Even if I unplug BoostXL-DRV8320RS I still get this error until I restart CCS.

Your feedback would be greatly appreciated.

Thanks

Viktorija

  • 0
    Intellectual 400 points

    Here is additional information to my problem. I ran the utility:

    C:\ti\ccs_base\common\uscif\xds110>xdsdfu -e

    USB Device Firmware Upgrade Utility
    Copyright (c) 2008-2015 Texas Instruments Incorporated. All rights reserved.

    Scanning USB buses for supported XDS110 devices...


    <<<< Device 0 >>>>

    VID: 0x0451 PID: 0xbef3
    Device Name: XDS110 Embed with CMSIS-DAP
    Version: 3.0.0.11
    Manufacturer: Texas Instruments
    Serial Num: CL491035
    Mode: Runtime

    Found 1 device.

    Also I removed/installed J1-J3 when I install/remove BoostXL-DRV8320RS board.

    Alex

  • 0 in reply to Aleksandr Labunskiy
    TI__Guru**** 171309 points

    Alex, Viktorija, 

    Thanks for the details. Error 260 indicates the host can't communicate with the probe, which is usually caused by many factors, including cables, the USB port, etc. Check the reference below for details (search for the error number). 

    https://software-dl.ti.com/ccs/esd/documents/ccs_debugging_jtag_connectivity_issues.html

    You mentioned you removed JP1~JP3, but perhaps the boosterpack may be providing insufficient power to the processor side of the board? You could try to remove JP9 and apply external power to the board independently. That or put the boosterpack in the lower part of the board (J5~J8) and isolate the power through JP8.  

    I didn't thoroughly check the schematics to see if there may be other issues at hand, but that is my best bet at this time. 

    Hope this helps,

    Rafael

  • 0 in reply to desouza
    Intellectual 400 points

    Dear Rafael,

    Instead of wasting my time you could have asked a simple question: "Di you install JP9 when you removed JP3?" They are mutually exclusive but one of them obviously (now) required because +5V0 is connected pin 96 on the debugger chip. This requirement is not mentioned in any TI documentation/guides. TI should add this to the chapter 3.2 Hardware Setup of BOOSTXL-DRV8320RS EVM User’s Guide. You did help me when you mentioned JP9 but I fixed TI problem myself.

    Alex

  • 0 in reply to Aleksandr Labunskiy
    TI__Guru**** 171309 points

    Alex,

    Hindsight always has a perfect perspective and I don't deliberately make developers like you waste their time with useless reading.

    Whenever replying to a thread, I don't have the developer's system in front of me and need to cover all possible scenarios that may be causing a failure.

    Also, there are many boosterpacks and launchpads available and I don't have access to all the hardware, especially in times of quarantine like these. 

    Rafael

  • 0 in reply to desouza
    Intellectual 400 points

    All I want now is TI to update the document I mentioned in the previous reply so no one else has this problem. This document is not a general document. It is for a particular launchpad and booster pack.

    Thanks

    Alex

  • 0 in reply to Aleksandr Labunskiy
    TI__Guru 66340 points

    Alex,

    I appreciate the feedback and we will be discussing how to improve that area of the documentation.

    Regards,

    -Adam