The controller has detected a power loss.

Thanks for the guide, it has put me on the right track.

Using it I have found that the XDS device does not show up under ports in the device manager. However the XDS110 shows up when I use one of my launchpads and the XDS100v2 shows up when I use a Blackhawk debugger. I assume this board uses one of those as the User's Guide calls out XDS100v2. I would attempt to update the driver but that is usually done through the device manager. Is there another way to update it?

Hi John,

There is not another way to update the firmware on the onboard XDS100 if you cannot see it in device manager. I find it interesting that Device Manager doesn't see the debugger, yet CCS gives a low-power message instead of saying that it doesn't see a debugger. Could you go to your target configuration and use the 'Test Connection' option, and could you post the output log? Also, are you able to connect to your Controlcard from the docking board with the XDS110 or the Blackhawk XDS100V2? Make sure to set the switches correctly according to the F28388D ControlCard User's Guide for using an external emulator. 

Best Regards,

Ben Collier

Thanks for responding.

On the switch positions I see no indication on the board or in the document for location of position 1 vs position 2. So not sure how to set them.

I get the same results with or without the docking card.

Hi John,

The two switches important for JTAG connection are circled in the image below. The top one is switch 1, the bottom one is switch 2. Each 'switch' component has two small switches on it. According to Table 1 in the Control Card user's guide, if you want to connect with an external debugger, you need to set both switches in switch 1 to the off position (left). In switch 2, you need to switch the top switch off (left) and the bottom switch on (right).

Once the switches are in the right position, you could try connecting to the device through the JTAG header on the docking card. Could you try to use your Blackhawk XDS100V2? This will confirm that the MCU is still functioning correctly.

Best Regards,

Ben Collier

Thanks for the reply.

I set the switches but still nothing in the device manager.

Sorry I cannot use the Blackhawk. I work remotely and I was only sent a bed of nails connector for our target board.

Hi John,

Unless you think that the firmware on the ControlCard debugger has been modified, I would suspect that the cause of your problem might be hardware damage to the XDS100V2 debugger. It would be good to see if an external debugger can connect to the F28388D, that way we can confirm the problem is only with the MCU063B  debugger. 

Is there any way you could obtain a debugger so that you could try this? Which launchpads do you have? It's possible that you may be able to use the launchpad as a debugger, though I will have to double check that.

Best Regards,

Ben Collier

Hi John,

Which Launchpad do you have with the onboard XDS110 JTAG Debug Probe? After you let me know, I can give you specific instructions on how to test your connection to the F28388D, and you should only need 5 standard jumper wires. If you have the right launchpad, you should be able to test connection to your F28388D on the Controlcard, though you may not be able to actually load code with this setup. This way we could verify that the F28388D microcontroller itself is still able to circulate bits, meaning that your problem is caused by the MCU063B's XDS100V2.

Best Regards,

Ben Collier

Hi Ben,

Thanks for the note. Apologies for late reply but had to break off early Friday.

I have a LAUNCHXL-F280049C. Does this board require or prefer the XDS110?

I should point out that we are using CCS11, not 12 and I cannot get that changed.

John