MSP432 Factory Reset Causing Error

Hi Robert,

Thanks for sharing the details about your software versions. Referring to the XMS432 Support wiki page, they seem to be ok.

I have two initial questions. Are you power cycling between performing the Factory Reset and trying to load your custom code onto the board? Have you enabled password protection for the Factory Reset?

Regards,

James

MSP Customer Applications

Hi James,

Thank you for your prompt response.  We are power cycling between Factory Resets. (chronological order of events: launched target configuration (brand new empty project chosen for target config), connected to target, factory reset performed, terminated debug session (clicked stop button in CCS), powered off launchpad, powered off custom board, wait 10 seconds, powered up custom board, powered up launchpad, tried uploading code to the launchpad with debug, and then we received the error listed in my first post.

We have also not enabled password protection for the Factory Reset.

Best,

Robert

Hi Robert,

Thanks for the details about your programming method - it's very helpful for effective debugging.

I'm wondering if there's an issue caused by the custom board (target) powering up before the LaunchPad (debugger). Could you try keeping power supplied to the LaunchPad while power cycling the custom board? Also, are you powering these from the same PC via USB?

Using CCS v6.1.3, I took two red (XMS432 RevC) MSP432 LaunchPads and tried to duplicate your issue. For the debugger LaunchPad (board on the left), I powered it from my PC via USB and removed all jumpers from J101. For the target LaunchPad (board on the right), I powered it from a separate external power supply (two AA batteries) and removed all jumpers from J101. Next, I used a 10-pin ribbon cable to connect the two boards: XDS110 Out ----> MSP432 In

In CCS, I opened the "msp432p401x_1" Toggle P1.0 code example project from MSP432Ware v3.50.00.02. First, I programmed the target board with this code example. After stopping the debug session, I went through the Factory Reset procedure. After stopping the debug session and removing the external power supply from the target board, I powered it back up and reprogrammed the Toggle P1.0 code example without encountering any errors. Try this approach and let me know if the error still occurs, and we can dig deeper.

I've included my installation details for your reference.

Regards,

James

MSP Customer Applications

Hi James,

I just tried keeping the power supplied to the LaunchPad while power cycling the custom board with no luck.  I am powering the custom board from an external DC power supply and powering the Launchpad from a PC via USB.

I tried your exact setup shown above with two REV C launchpads and it works without a problem.  I am starting to wonder if it has anything to do with our programming connection (even though I am able to Factory Reset the board..). Here (https://e2e.ti.com/support/microcontrollers/msp430/f/166/p/1978984/reply?ReplyToContentTypeID=1 ) it mentions that pull-down resistors are required for JTAG.  Currently we have pull-down resistors on all 4 lines (TCK,TDI,TDO,TMS) and we have been programming like this for quite some time without any issue, however it may be an issue for factory reset. With the first revision of the Launchpad (black) we found that we could not program our custom boards (SWD interface) without a pull-down on the SWCLK line.  From the launchpad schematic available online, it does not seem that these lines have any resistors but maybe you can confirm? Otherwise any other ideas?

I have also attached my installation details below. Seems like the only difference is that you have a newer MSP432 target content 3.50.0.02. I assume this is not available to the public yet, since I tried to update it and it says no updates were found.

Hi Robert,

Thanks for trying these recommendations. Regarding the pull-down resistors on the JTAG signals, could you provide the link again? Unfortunately, I wasn't able to access it. I noticed that these resistors aren't used on the LaunchPad, so I'm curious to see what this link says.

Can you try changing the JTAG / SWD / cJTAG Mode Settings to "SWD Mode - Aux COM port is target TDO pin" under "Connection Properties"? When the settings of Port J are changed, full JTAG access is prevented on these pins. Using SWD allows access through the dedicated debug pins.

Regards,

James

MSP Customer Applications

Hi Robert,

Thanks for confirming your Mode Settings. Would you be able to share the debug portion of your custom board schematic? Send me a private message if you're not able to. What specific connector/pins are you using on the LaunchPad debugger for the JTAG/SWD interface?

Regards,

James

MSP Customer Applications

Hi James,

Although we cannot share our official schematic on this forum, I can describe the debug portion of the schematic to you since it is very simple.  I went ahead and just now removed all of the pull down resistors on our custom board and we are still able to Factory Reset the boards with the previous procedure.  So the debug connection is as follows:

We are directly connected from the launchpad's XDS110 debug pins to our custom board's JTAG pins.

Best,

Robert

Hi Robert,

The debug connection diagram is helpful. How are you implementing your RESET circuit? For proper JTAG operation, the datasheet specifies a 47kOhm pull-up resistor and a 1.1nF pull-down capacitor, as shown below.

This may be causing the issue. Let's keep the other pull-down resistors that you removed off for now.

Regards,

James

MSP Customer Applications

Hi James,

Does this reset circuit have anything to do with the nReset connection (pin 10) on the 10pin cortex debug connector? (nReset pin shown in my last post or on page 2 of http://infocenter.arm.com/help/topic/com.arm.doc.faqs/attached/13634/cortex_debug_connectors.pdf Or is this just an additional circuit needed on our board aside from the programming cable?  At the moment, I do not have the nReset pin connected to anything, which I am not quite sure is correct.

Thank you,

Robert

Hi Robert,

Yes, the RSTn pin of the MSP432 should be pulled up to VCC using a 47kOhm resistor and pulled down to GND using a 1.1nF capacitor, as shown in my post above (which came from the MSP432 LaunchPad User's Guide) and discussed in Table 4-4 on page 27 of the MSP432 datasheet.

Then, the RSTn pin of the MSP432 should be connected to the nRESET pin of the Cortex debug connector on your board to ensure proper JTAG/SWD operation.

Regards,

James

MSP Customer Applications

Hi James,

We added the 47kohm pull-up with 1.0nF pulldown to the RSTn pin of the MSP432 and then connected the nRESET pin of the Cortex debug connector to our board with no luck.  We are still able to factory reset the boards but unable to program.

What do you recommend trying next?

Best,

Robert

Hi Robert,

Thanks for trying this. Let's keep the reset circuit implemented moving forward. Since we're able to perform the Factory Reset and then program code on the target LaunchPad, the debugger LaunchPad seems to be fine. However, missing connections, wrong capacitance values, etc. could be causing the issue on the custom boards.

I'd recommend comparing the schematic of your custom board to the schematic of the LaunchPad. It may be helpful to view the design files in Eagle. Another good reference would be the schematic of the MSP-TS432PZ100 target development board, which has a 10-pin Cortex debug connector and all connections/components for programming/debugging through JTAG interface or the Serial Wire Debug (SWD 2-wire JTAG) protocol. See Section 1.2 in the MSP432 Hardware Tools User's Guide for the proper jumper configurations.

Regards,

James

MSP Customer Applications