MSP432P4011: The way of the factory reset for MSP432P4011

Hi,

This link seems to suggest there isn't one. https://e2e.ti.com/support/microcontrollers/msp430/f/166/t/455309?-Factory-Reset-for-MSP430 

However, I have forwarded this query to the team for a confirmation.

Thanks.

Hello FI-san,

Do you have any update on my thread?

Best Regards,
Nomo

Hello Michael-san,

Thank you for your reply.
I'll check your comment.
If I have another question, I'll another post as a related one.

Best Regards,
Nomo

Hi, we still have the same problem with our custom MSP432P4011 board.

1. If we step from main() the first procedure will be Power_init(). If we step over it the connection is lost and we cannot connect to the chip again! Even after new power-up. Are our chips all 'locked' or destroyed! We have probably a software configuration error since core samples like 'cs_hfxt_start_MSP_EXP432P4111'_nortos_ccs' runs fine, build for MSP432P4011.

2. Are the problems with unlocking these particular chips solved? We always receive the following message:

3. This happens with both SWDCLK,SWDIO (2-wire) as well as JTAG-4

We also never get the possibility for a factory reset this way?

We use cccs 9.2.x

regards,
Laurent

Hi Laurent,

Typically error -261 is related to the XDS110 debugger itself, and not the chip it's attached to. For debugging XDS110 issues this is a great resource:

http://software-dl.ti.com/ccs/esd/documents/ccsv7_debugging_jtag_connectivity_issues.html

Some more threads on E2E with information on that error:

https://e2e.ti.com/support/tools/ccs/f/81/t/737649?CCS-MSP432P401R-Error-261-0x0-Invalid-response-was-received-from-the-XDS110-JTAG-comm-error-

https://e2e.ti.com/support/wireless-connectivity/wifi/f/968/t/616940?CC3220SF-LAUNCHXL-Error-XDS110-returned-error-code-261-What-does-this-mean-

Is the XDS110 on your custom board, or do you have a separate XDS110 debugger you are connecting to each board?

Have you tried using a different debugger? Each MSP432 launchpad comes with an XDS110, and you can wire the JTAG header pins to your board to connect the XDS110.

Regards,
Michael 

Hi Michael, thanks for your reply. I used both the MSP-FET+ADPTR as well as the XDS110 of the MSP-EXP432P4111 LaunchPad. We also tried both SWD and 4-JTAG. Both cases result in running perfect on the LaunchPad and endering the custom  MSP432P4011 inaccessible!

Here's a picture of the pcb(2-layers) we use and only components necessary for the MSP432P4011 are placed, including the clocks(48MHz and 32,768kHz)! 

We now tend to get a zif socket and start building up the hardware from scratch! Question: do you have some simple pcb layout specifically for this 64-pin processor we could have made for this purpose?

Regards, Laurent

2M Engineering BV

Hi Laurent,

For PCB layout guidance, our reference design is the MSP432P4xx launchpad designs. You can find their design files on the respective product pages:

http://www.ti.com/tool/MSP-EXP432P401R

http://www.ti.com/tool/MSP-EXP432P4111

I suggest you take a look at those layouts and schematics and compare them against your board. Looking at the design guide in ti.com/lit/slaa770 should also be useful in debugging your JTAG issue.

Regards,

Michael

HI,

I think I solved the issue. It had nothing to do with the cJtag or any of that comminication. It looked like a software failure on one board and a hardware issue on another equal board. I had this code:

main() {

Power_init();

GPIOInit();

....

I could step over "Power_init();" ok but stepping over GPIOInit() hang up everthing with waird results and not being able to connect. Looking in a bundle of literature(TI) I found the answer! It was due to not having the DCDC L1 components placed, setting the CDCD to LDO but not repeating this on all places(power_profiles). We are now busy placing them and see whats happening but, I'm pretty convinced it will solve the issue!

It will take a few days, but I'll let you know by the end of this week!
Thanks for the support anyway.

regards,

Laurent
2M Engineering
the Netherlands