• State Resolved
  • Locked Locked
  • Replies 8 replies
  • Subscribers 31 subscribers
  • Views 486 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

Original question:

MSP432E401Y: Help with flashing MCU on custom board salvaged from Launchpad

MSP432E401Y: Error wile trying to Factory Reset MSP432E401YT REV B (Launchpad) or flash new code on a custom board

Utkarsh Gupta
Prodigy 60 points
Part Number: MSP432E401Y
Other Parts Discussed in Thread: UNIFLASH

I used MSP432E401YT REV B from Launchpad instead of MSP432E401Y as they were out of stock and I am having trouble factory resetting it.

The msp432_factory_reset is not available so I manually load the .GEL file from ccs_base > emulation > gel > msp432_factory_reset

 

Target Congif:

XDS110 USB debugger on another launchpad connected to MSP432E4YT REV B on custom board using:

  • TDI, TDO, TCK, RST, 3.3 & GND

I keep seeing this error:

CS_DAP_0: Trouble Writing Register DP_RESET: (Error -1013 @ 0x2) Unable to access device register. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 9.4.0.00129) 

MSP432_Factory_Reset() cannot be evaluated.

Target failed to write register DP_RESET

at DP_RESET=1 [msp432_factory_reset.gel:44]

at MSP432_Factory_Reset()

  • Is the pinout of MSP432E401YT REV B even the same as of  MSP432E401YTPDT?
  • How can I try to factory reset my custom board so that I can run new firmware?
  • I tried to factory reset because I am unable to program the controller over jtag, not sure why it works fine on the launchpad but not on my board
  • I can flash the .out file with uniflash but the controller does not toggle gpio at all.
  • 0
    TI__Guru 71216 points

    Hi Utkarsh,

    I see you have started another post on the same topic.  I apologize for not getting you an answer sooner on your other post.  I have escalated both postings internally to see if someone can address your issue.

  • 0 in reply to Dennis Lehman
    Prodigy 60 points

    Thanks for the help, yea we need this urgently resolved for a demo! Hope you understand, we just trying to debug the issue asap.

  • 0
    TI__Mastermind 23105 points

    Hi Utkarsh

    I'd like to share the Troubleshooting section of https://software-dl.ti.com/ccs/esd/documents/xdsdebugprobes/emu_xds110.html

    Hope this page is helpful on the XDS110 issue.

    Thanks!

  • 0 in reply to Xiaodong LI
    Prodigy 60 points

    it's not a XDS110 issue, i think the DAP reset is not accessible through JTAG for this chip

  • 0 in reply to Dennis Lehman
    Prodigy 60 points
    • We have a custom board with  MSP432E401YT REV B (Let’s Call it Board 2) (Error)
    • We also have a working board MSP432E401YT REV B (Let’s Call it Board 1)

    • We cannot program Board 2 from CCS 
    • I can flash Board 2 Uniflash but the MCU does not run after the flash 

    • CCS gives ERROR: CS_DAP_0: Error connecting to the target ( Error -1170 @ 0x0)
    • This error never goes away
    • If I erase the board 2 with uniflash and try to program with ccs again, I can see that memory initialization is complete but after writing 50% in the progress window I start seeing the Error: ( Error -1170 @ 0x0) again and on further efforts to program it the progress bar never appears unless I erase the MCU with uniflash

    • I exported the binary memory content with uniflash from 0x0 for 1000000 Bytes from Board 1 and board 2 and compared the binary files and found them to be an exact match 
    • For Board 2 sometimes we see uniflash error: Hard Fault or NMI error but goes away after I disconnect and connect couple of times or error -613 target is busy 

    • We checked all the voltage levels and ohmed out JTAG pins and they all ohm out 
    • It's not the MCU from launchpad issue because the same MCU works on a different board when swapped 
  • 0 in reply to Utkarsh Gupta
    TI__Guru 71216 points

    Hi Utkarsh,

    If board 1 and board 2 are exact same board, and board 1 works, while board 2 does not, independent of which MCU you have installed, then there must be something wrong with board 2.  Do you have more than these two boards and have you tried to program them?

    Can you share your schematic or at least the portion that shows the MSP432 and all its connections?

  • 0 in reply to Dennis Lehman
    TI__Guru 71216 points

    Hi Utkarsh,

    Never mind about the schematic.  I found your other posting and took a second look. I did notice the capacitors you have for VDDC (1.2v core LDO output) requires a minimum of 2.5 uF.  You might try tacking on another 1uF to see if that might be the issue.

  • 0 in reply to Dennis Lehman
    Prodigy 60 points

    Hello Dennis, thanks for the feedback and I tried that. 

    The issue was that the fab house put 47pf caps by mistake instead of 12pf caps on the 25MHz and 32MHz clock, which pulled the peak-peak on the 25MHz clock too low (about 40% of the pk-pk compared to the launchpad).

    We stripped the board of everything except the MCU and required peripherals and compared to 432 Launchpad and noticed that the clock signal looked great but the amplitude was vastly different compared to the reference (40% reduction compared to Launchpad)

    I was not able to test the 32MHz crystal, maybe I overloaded it with the scope (10x probe) but 25 MHz was easy to test.

    It's hard to test those 201 Caps, but I just took a chance and swapped all the caps on the clock with the 402 caps on Launchpad and it worked. 

    Thanks for all the support!