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.
Part Number: MSP432P401R
Hi,
As stated in my previous post, I'm currently designing hardware and am trying to integrate parts of the MSP432 Launchpad schematic into my circuit.
On sheet 3, I see that the signal "XDSET_VCCTARGET" on the XDS110 side is the signal that ends up become the 3.3 V on the MSP432 side. However, it seems that XDSET_VCCTARGET is generated using some power switch, TPS2102DBV, and two signals XDSET_VCC and XDSET_VCCOUT.
I know XDSET_VCC is generated using the 3.3 V LDO, but what is XDSET_VCCOUT's purpose? If I'm not interested in EnergyTrace functionality, is it OK to just completely bypass TPS2102DBV and effectively short XDSET_VCCTARGET to XDSET_VCC?
Regards,
Michael
If you don't need EnergyTrace functionality, suggest you instead copy the XDS110 circuit from a different launch pad which doesn't feature EnergyTrace, such as that for a LAUNCHXL-CC2650.michaelwu said:If I'm not interested in EnergyTrace functionality, is it OK to just completely bypass TPS2102DBV and effectively short XDSET_VCCTARGET to XDSET_VCC?
I think the emulator software which runs inside the TM4C1294NCPDT of the XDS110 determines which type of XDS110 it is running in, e.g. if EnergyTrace is fitted, by sampling the values on the PK4..PK7 pins.
If you bypass part of the EnergyTrace circuity on the MSP-EXP432P401R that may cause issues with the XDS110 emulator when trying to debug.
Hey Chester,
Thanks for the reply. This is really helpful insight -- I'll take a look at the schematic of the LAUNCHXL-CC2650. As someone who's new to MCU's, what's the purpose of the XDS110?
Michael
For the official TI documentation see:michaelwu said:As someone who's new to MCU's, what's the purpose of the XDS110?
As for the purpose my view is that the XDS110 allows for:
a. Programming of the flash of a target MCU, either via the CCS debugger or standalone programs such as UniFlash.
b. Debugging a MCU program using the CCS debugger (or other debuggers).
c. For Cortex-M MCUs such as a MSP432P401R support for trace capture through ARM serial wire output (SWO) – UART mode only.
d. Support for UART communications to and from the target MCU.
e. Support for powering the target MCU. The XDS110 built-in to launchpads supply a fixed voltage, whereas the standalone TMDSEMU110-U allows the voltage to be adjusted.
f. EnergyTrace functionality, not available on all versions of the XDS110 on launchpads.
You could simplify your circuit by just having a connector to connect an an external TMDSEMU110-U (or different debug probe) for programming / debugging.michaelwu said:As stated in my previous post, I'm currently designing hardware and am trying to integrate parts of the MSP432 Launchpad schematic into my circuit.
Hey Chester,
Thanks for all the help! This discussion has been really helpful for me.
I have a question for you (or anyone who may see this): On sheet 6 of the schematic, it looks like only 2 of the 6 SHIELD pins of the micro-USB connector are shorted together and then pulled down via the 33 ohm resistor. In making my own schematic, should all 6 pins be connected to each other and then pulled down together?
Michael
This depends on the symbol and the physical design of the USB connector you are using. The shield of the connector should be connected to ground via a resistor. If the connector you are using have 6 physical pins connected to the shield, all 6 should be shorted and connected to the resistor. If it has two, these two pins should be shorted.
The only reason I ask is because the USB connector on the BOM has 6 shield pins but the schematic only shows 2 connected. Either way, I'll pull all 6 down to ground, thanks!
**Attention** This is a public forum