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/TMDSEMU200-U: TMDSEMU200-U (J Tag)

Part Number: TMDSEMU200-U
Other Parts Discussed in Thread: CC2640, CC2650

Tool/software: Code Composer Studio

Hi all,

We are using CCS version 6 and Debugger XDS200 for the development of our costume device.

Problem observed# -  Not able to program our board using XDS200/Jtag through Code composer studio

Cortex_M3_0: GEL Output: Memory Map Initialization Complete.

Cortex_M3_0: Failed Board Reset: (Error -180 @ 0x0) Internal error: Invalid error code. Restart the application. If error persists, please report the error. (Emulation package 6.0.407.3) 

IcePick_C: Error connecting to the target: (Error -180 @ 0x0) Internal error: Invalid error code. Restart the application. If error persists, please report the error. (Emulation package 6.0.407.3)

 

Please help us to resolve the problem...

  • Hi,

    This error is not valid for XDS200 JTAG debug probes, therefore I suspect your configuration is wrong. The reason is that you mention MSP432 on the tag, but the error message is talking about a Cortex _M3 core. Also, you have a tag that talks about XDS110.

    Can you double-check your configuration to see if it matches the HW you have?

    Regards,
    Rafael
  • Hi...
    Im sorry MSP432 must have selected by mistake. Sorry for that. i have changed the tag.
    My hardware has CC2640. for this i use XDS200 to Flash...
    We use to do initial tests on SensorTag which is similar to our costume board. To Flash sensortag i use XDS110. So i had mentioned it...

    Could you please tell me what kind of error is this....

    Thanks & Regard,
    Aishwarya
  • Aishwarya,

    Thanks for the clarification. I don't have a CC2640 device/board with me, but I connected my XDS200 to my CC2650 Launchpad and I was successful.

    The configuration file I am using follows attached. 

    The fact your XDS200 is throwing this invalid error may indicate something is not quite right with your Debug Probe. Does it work in another setup or with another board? If not, then I would try to issue the command shown in step 2 of the following reference to verify if the debug probe is active and what version of firmware is installed. 

    http://processors.wiki.ti.com/index.php/XDS200#Updating_the_XDS200_firmware 

    If the command returns errors, there is a high probability the Debug Probe is defective.

    Before you go through that, though, I would try to reinstall the Windows drivers - they may have become corrupted somehow.

    - Open the Windows Control Panel
    - Expand the node Ports (COM & LPT)
    - Right-click on node XDS2xx Emulator CDC Serial Port
    - Select Update Driver SoftwareBrowse my computer for driver software
    - Select Let me pick from a list of device drivers on my computerIf the drivers are already installed, you should see XDS2xx Emulator CDC Serial Port Version: M.m.m.m [mm/dd/yyyy]. Select this one. Otherwise, repeat but skip this step.
    - Click on Browse and select the directory C:\ti\ccsv7\ccs_base\emulation\windows\xds2xx_drivers
    - Repeat for XDS2xx User CDC Serial Port

    That should get you the same driver as installed by CCS.

    If Windows refuses to update the driver, then you will have to remove them. 

    - Right-click on node XDS2xx Emulator CDC Serial Port
    - Select Uninstall...
    - Check the box Delete the driver software for this device and click OK
    - Repeat for XDS2xx User CDC Serial Port
    - Do the procedure above to reinstall the drivers

    If that does not work, then I suspect your Debug Probe may be defective. 

    Hope this helps,

    Rafael