• Locked Locked
  • Replies 12 replies
  • Subscribers 58 subscribers
  • Views 2737 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.

Cannot connect MSP-432p up to CCS,

British Lab
Prodigy 50 points
Other Parts Discussed in Thread: ENERGIA, CC2650

Hello,

I am trying connect an MSP432 to CCS but not having any luck,  I have succesfully connected it to a separate machine but its failing on my work machine.

The error msg is :

[Start]

Execute the command:

%ccs_base%/common/uscif/dbgjtag -f %boarddatafile% -rv -o -S integrity

[Result]


-----[Print the board config pathname(s)]------------------------------------

C:\Users\nick\AppData\Local\TEXASI~1\CCS\
ti\1\0\BrdDat\testBoard.dat

-----[Print the reset-command software log-file]-----------------------------

This utility has selected a 100- or 510-class product.
This utility will load the adapter 'jioxds110.dll'.
The library build date was 'Apr 27 2016'.
The library build time was '23:27:56'.
The library package version is '6.0.228.0'.
The library component version is '35.35.0.0'.
The controller does not use a programmable FPGA.

An error occurred while hard opening the controller.

-----[An error has occurred and this utility has aborted]--------------------

This error is generated by TI's USCIF driver or utilities.

The value is '-261' (0xfffffefb).
The title is 'SC_ERR_XDS110_FAIL'.

The explanation is:
Invalid response was received from the XDS110.

[End]

Thanks

Nick

  • TI__Guru**** 464431 points
    Hi Nick,
    Just a few questions:
    -What is the CCS version you are using on both the failing PC and the one where it works? Please provide the full version number
    -Are you using the MSP432 LaunchPad?
    -What is the host OS on the failing machine (what version of Windows)?
    -Have to tried taking all available updates in CCS?

    Thanks
    ki
  • in reply to Ki
    Prodigy 50 points
    Hello Ki,

    -What is the CCS version you are using on both the failing PC and the one where it works? Please provide the full version number
    both Version: 6.1.3.00033

    -Are you using the MSP432 LaunchPad? Yes
    -What is the host OS on the failing machine (what version of Windows)? Both Windows 10
    -Have to tried taking all available updates in CCS? All up to date

    Thanks
    Nick
  • in reply to British Lab
    Prodigy 50 points

    Hello Ki,

    I am using version 6.1.3.00033  on both windows 10 machines

    I am using a launchpad,  

    Both machines are windows 10 and the CCS is up to date

    Thanks

    Nick

  • in reply to British Lab
    TI__Guru**** 464431 points
    Hi Nick,
    Are you using Energia? Can you try doing a complete power cycle of your PC?

    Thanks
    ki
  • in reply to Ki
    Prodigy 50 points

    Hi Ki,

    I'm not using Energia and I have rebooted my machine (many times)

    regards

    Nick

  • in reply to British Lab
    Prodigy 50 points

    Hello Ki,

    Can you help with this please?

    regards

    Nick

  • in reply to British Lab
    TI__Guru**** 464431 points
    Hi Nick,
    Sorry for the delay. I currently don't have any good ideas on how to remedy the issue. The fact that the launchpad works on the other PC means it must be something related to the environment on the other PC. I will pull in some of our emulation experts for more assistance. Thanks for your patience.

    ki
  • in reply to Ki
    TI__Expert 7695 points

    Hi Nick

    The error indicates a hard connect issue, and the software stack is not able to communicate with the XDS110 debug probe. To help troubleshoot further could you try the following on the machine where the connection does not work:

    1. Is the LED on the debug probe side glowing green when you plug in the launchpad?

    2. Can you check if the XDS110 got enumerated on the machine?

    3. Did you try different USB ports on the machine?

    Thanks

    Ashwini

  • in reply to Ki
    TI__Guru**** 171094 points

    Nick,

    This is a very unusual error and was also observed by a fellow on the web (thus Ki's question about Energia).

    It can have two sources:

    1) Timeout. CCS sends a packet to the XDS110 and gets no response in time (usually 4 secs).

    This can potentially be caused by a conflict in libusb libraries - we supply one library with bug fixes that properly address some race conditions, but if a library is loaded previously then CCS will try to use that. That is why Ki suggested rebooting the PC, as it may remove any previous instances. Do you have another IDE and kits connected to the system? This is a long shot, but I recall that in the past when I was switching between WinUSB and libusb (when using OpenOCD and CCS) I was constantly running into strange issues and needed to switch these libraries using the method shown at this link.

    Also, are you connected to a USB3.0 port that uses a Renesas chipset? There are some known issues with libusb and this controller. This is mentioned in the Known issues of our XDS200 page and in the libusb page.

    2) Bad response. CCS sends a packet to the XDS110, it responded but with too many or too few bytes in the return packet.

    This is only possible if somehow there is a firmware mismatch, given that USB is a protocol that has retries and error checking (thus "flipped bits" are very unlikely to occur). Given you are using the latest version of the TI emulators component (6.0.228.0), it already features an automatic firmware update mechanism, therefore minimizing the possibility of this happening.

    Despite this, can you confirm what firmware is loaded to your XDS110 by issuing the command in step 1 of the section "Updating firmware of the XDS110 page?

    Apart from these details I can't really think of anything else to try. If I have some additional ideas I will report back on this thread.

    Hope this helps,

    Rafael

  • in reply to desouza
    TI__Expert 4635 points
    Hi Team,

    I had the opportunity to visit Nick recently and saw this issue on his PC. On connection the LED is always red on his setup. The hardware appears to enumerate OK on Device Manager but will not connect in CCS Debug with the 'Bad Response' issue.

    We plugged the MSP432 Launchpad into my laptop and the firmware auto updated to latest version and connect in CCS 6.1.3.00033 fine but still did not connect on his config. Incidentally we also observed the same with a different CC2650 Launchpad which features the XDS110 debugger.

    In Nick's case this appears to be localized to the XDS110 class emulators and their drivers as a SmartRF06 board with XDS100v3 worked flawlessly with some other EM hardware.

    Do we have any means to check and verify the versions of loaded library / DLL dependencies associated with the XDS110 driver on Win10? I too suspect a dependency mismatch.

    Regards,
    Garry
  • in reply to Garry Clarkson
    Guru 92251 points

    Garry Clarkson said:
    Do we have any means to check and verify the versions of loaded library / DLL dependencies associated with the XDS110 driver on Win10? I too suspect a dependency mismatch.

    Suggest running the 32-bit version of Dependency Walker on <ccs_install_root>\ccsv6\ccs_base\common\uscif\JIOXDS110.DLL and checking that the required MSVCR120.DLL from the Microsoft Visual C++ 2013 Redistributable (x86) can be found.

    Even if the MSVCR120.DLL can be found, it might be worth attempting a repair of the Microsoft Visual C++ 2013 Redistributable (x86), since that fixed a debugger error on a different emulator - see Debugger Initialization Error

  • in reply to Garry Clarkson
    TI__Intellectual 2515 points

    There are two LEDs on the MSP432 LaunchPad.  A green and a red.  When the LaunchPad is first plugged in, the green LED should light indicating power and proper operation.  On connection, the red LED should light and flicker with activity, and the green LED should remain lit.  Are you seeing the green LED go out when the red LED turns on?  That would indicate the firmware has taken a CPU fault interrupt.  Or are both LEDs on?  That would indicate the firmware believes there is a host connection, but the host is telling us it's not seeing proper responses.