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-F28379D: Using debug probe with external power supply

Part Number: LAUNCHXL-F28379D


Tool/software: Code Composer Studio

Hi everybody!

I need to know if it is possible to use the embedded xds probe on the LAUNCHXL board while the MCU is being powered by an external 3.3 V supply. I need to use the debug probe via USB to load and run programs on the MCU, while the latter has its own isolated power supply. Is it possible? If so, please explain how to do it.

Cheers

Francesco

  • Hi Francesco,

    Yes! we purposefully designed all C2000 LaunchPads to support this configuration. You will See JP1, JP2, and JP3 near the top of the LAUNCHXL-F28379D. When shorted, these will connect 5 V, 3.3 V and Gnd to the MCU side of the board which is supplied through the USB on the debugger side. When you remove these jumpers, the Debug probe is still powered and can operate. The MCU needs 3.3V supplied through any of the available connections (BoosterPack Connectors, or auxiliary power jumpers). 5V on the MCU side is optional, but can also be boosted from the 3.3 V supply.

    Refer to the User Guide and Schematic for the specific pins, and jumpers.

    -Mark
  • Hi Mark,

    I already knew the documentation, and now I managed to make it working fine. Problem solved! But let me explain the issue I had. I had managed to power the Lauchxl as explained in the documentation. 3.3V and 5V were supplied from an external power source, the XDS probe was completely isolated. I tried to load and run the blinky led example using code composer studio. There was a strange problem: immediately after a hardware reset (or power switched on), it was possible to load the program, but it wasn't running. Stopping the debug mode and loading again, then the program ran without any problem. This happened every time after hardware reset. I was confused and thought I was missing something in the configuration, and tried and tried again without success. Then I just used a different Launchxl board, and it immediately worked perfectly. I concluded the first board was damaged, but I can't figure out what kind of fault could explain the observed behavior. Is it a known problem?

    Francesco