Hi Robert,

Did you also try reflashing the bootloader?

See the "flashing the bootloader" section of: https://dev.ti.com/tirex/explore/node?node=A__ALFqIj4dX6S.TZRERoSphA__xdsdebugprobes__FUz-xrs__LATEST

Thanks

ki

Hi ki, 

Flashing the bootloader didn't help. I tried several times the "xdsdfu -b boot_loader.bin -r" step, but it finished immediatly. Not sure if something was flashed:

C:\ti\ccs2000\ccs\ccs_base\common\uscif\xds110>xdsdfu -b boot_loader.bin -r

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

Replacing the bootloader may render the XDS110 unusable.
Do you want to continue (Y/N) ? Y
Scanning USB buses for supported XDS110 devices...

Downloading boot_loader.bin to device...

Now, after several tries and tests, the XDS110 does not go into DFU mode anymore when I pull pin 97 to GND during power-up. And connecting a debugger to the MSP432 is nearly impossible, as I'd need to solder wires to the JTAG pins. 

Thanks,
  Robert

I have been experimenting with my F280039C controlCard. It also has an MSP432E401Y for the XDS110 device. I had no problems updating the firmware and bootloader using CCS 20. After power cycle, the device is still detected and I can use it for debug

I will order the LanchPad to see if the issue is specific to the LaunchPad.

Hi Robert .....sorry I was out of action yesterday ....I tried the same routine and made the mods to pin97 and attached the CRO to see the mods were operable BUT the USB still did NOT connect to the MSoft PC Host. Sigh. No happy tingles ....so I cannot take the next step reloading the Flash. The -e attribute to xdsdfu.exe gave "Unable to load Libusb" same as before.

I think I will resort to the control card assy and test this today ... while poor old Ki does his magic with Ti and figures whats wrong ?

I wonder how many users of LaunchXL F280039C have reported disconnection of USB after downloading CCS20 ? There seems no forum title for XDS110 problems ? It seems difficult to circumvent  this problem ....what can we do if we lose programmatic attachment to the launchPad ? Its gone .... unless there is a field practical H/W mod to re-establish USB connection .... ????

Why was the XDS110 upgrade needed anyway ?

Rgds

DonW

Ki & Robert....is THIS the problem ?

I am sure I had my LaunchXLF280039C fired up and running my application while I downloaded the CCS20 IDE ....See this from the XDS110 install instructions !

"Installation Instructions

• Make sure XDS110 is not plugged in
• Install Code Composer Studio version 6.1.0 or later if using an embedded XDS110, install 7.0.0 or later if using a standalone XDS110.
  • If installing CCS in Linux, make sure to follow the installation instructions at the Linux Host support page.
• Plug in the XDS110. It should be properly recognized by the system."

The consequence of NOT having the XDS110 was not mentioned.

Don Williams said:

Ki & Robert....is THIS the problem ?

Highly unlikely. Especially if you already had a prior CCS version installed.

I plugged my control card in and emptied all previous work/projects ...first thing that happened was the "start debug" fail because the Launch.json file was an empty shell. I plugged in my standby txt ...next

The project built fine .... but starting debug I got the following : 

...My team will run out of dev PCB if we lose another L'Pad or Control Card .

NOTE the instruction to NOT unplug the debug probe (C'Card or L'pad ) which solves my question about the contradictory Installation instructions above.

I attach the above to provide the revision level information - ie between which revision levels the update is happening...it might be useful info.

So ... do I load the update or not ? And in reference to Ki's advice above somewhere, the appropriate launch.json file is NOT being loaded from the explorer example file ????

Last I mentioned I would look at the makefile and see where the .json file is being looked for - and not found. But when I plug the json file guts in the project save keeps it.....???

OK Ki & Robert ... my TMDSCNCD280039C control card plugged into my baseboard works fine after the XDS110 f/w update - and the filling the Launch.json shell ...?? But I can live with that ...and I am back on the road !!!

Tested successful enumeration a number of times under C'Card USB power...so was power cycling. Works just like a bought one !

We need another stand of dev PCBs and we might stay with the CCards ...

Cant say this has resolved my Issue ?

Glad to hear the controlcards are working. I should be getting a LaunchPad soon and will see if there are any issues there.

Ki said:

I should be getting a LaunchPad soon and will see if there are any issues there.

I got my new LAUNCHXL-F280039C. I plug it in to my PC and it was detected fine. I then created a target configuration in CCS 20 for it and launched a debug session. CCS detected it and said I needed to update the firmware. It said OK and it updated the firmware successfully (so it seemed). Then it successfully started the debug session and I could connect to the target! Then I shut down the debug session and started another one. Still good. I terminated the session and ran xdsdfu -e. It found the XDS110 and had the updated firmware version. Good! Then I power cycled the launchpad (unplugged it and the plugged it back in). xdsdfu -e reported nothing found. I tried launching a debug session and of course that failed. 

So.... I can reproduce this issue. It seems specific to the LAUNCHXL-F280039C. We have had similar issues in the past with other launchpads/EVM due to issues during the manufacturing process at the factory:

https://e2e.ti.com/support/microcontrollers/arm-based-microcontrollers-group/arm-based-microcontrollers/f/arm-based-microcontrollers-forum/1374638/lp-am263p-xds-110-firmware-update-failure/5282507#5282507

https://e2e.ti.com/support/processors-group/processors/f/processors-forum/1385763/j722sxh01evm-unable-to-connect-to-xds110-in-ccs/5296661#5296661

I'm wondering if this may be another case.

I will continue investigation.

Ki said:

I will continue investigation.

Besides the tedious workaround of grounding TDO every time on powerup, another (easier) workaround is to hold down button S1 on the LaunchPad while connecting the USB cable. This will also allow the XDS110 to be detected.

Ki .... some alligators in this swamp .... this issue persists and may be the cause of the problem ?

The L'Pad 280039C enumerated and for all indications seems to be debugging ...but will check further tho registers panel seems updating...

I get this on "Test Connection" button ccmxl editor screen.

Side issues L'Pad enumerates and "active" ... ??