• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Answers 1 answer
  • Subscribers 80 subscribers
  • Views 2660 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.

MSP-EXP432P401R: Defective Board? - or in some mysterious recoverable state?

LouEEEE!
Expert 1955 points
Part Number: MSP-EXP432P401R
Other Parts Discussed in Thread: ENERGYTRACE, UNIFLASH

Running experiments on two recently-acquired MSP-EXP432P401R boards. Relatively new to this platform, am seeing some error messages I don't know how to remediate or escape from!

Environment is CCSv7.3 on macOS. As a test, am building outofbox_msp432p401r_MSP_EXP432P401R_tirtos_ccs

On 'Board 1', firmware loads, halts at first breakpoint, EnergyTrace runs - all as expected.

On 'Board 2' - same USB port used, same cable...

CORTEX_M4_0: Can't Run Target CPU: (Error -2134 @ 0x0) Unable to control device execution state. 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 7.0.48.0) 
CORTEX_M4_0: JTAG Communication Error: (Error -615 @ 0x0) The target failed to see a correctly formatted SWD header. The  connection to the target may be unreliable. Try lowering the  TCLK setting before trying again. (Emulation package 7.0.48.0)

JTAG TCLK is at default 2.5MHz. Does this look like something I can fix/reset/other, or do I have a defective board?

The Test Connection function for the XDS110 USB Debug Probe runs with no apparent errors.

Have also tried direct write of finished firmware binaries using UniFlash - with similar results.

  • 0
    TI__Expert 8510 points

    For all Debugger-related problems on TI Launchpads, the first place I'd start is the  Debugging JTAG page here.

    If you search for "SWD header", the first step suggested is to verify that you have the jumpers in place for TMS and TCK on the J101 header row.

  • 0 in reply to Bob Landers
    Expert 1955 points
    Bob - Tks for taking a swing. But all J101 header pins are in place - haven't moved 'em since receiving this board. Haven't touched the TCLK from default setting, either. Weird.
  • 0 in reply to LouEEEE!
    TI__Expert 8510 points

    Did you try the other debugging steps from this page, including the one on XDS110 that mentions re-flashing the firmware for the XDS110 interface on the Launchpad?    Despite the fact that your test worked, I'd still give that a try- the instructions from this section are:

       An attempt to connect to the XDS110 failed.

       The cause may be one or more of: invalid firmware update, invalid

       XDS110 serial number, or faulty USB connection. The firmware and

       serial number may be updated using the xdsdfu utility found in

       the .../ccs_base/common/uscif/xds110 directory of your

       installation. View the ReadMe.txt file there for instructions.

    If, after this, the 2nd board still doesn't work, then I would recommend replacing the board since you've already proven that the SW and other connections aren't the issue since you have another LaunchPad that does work.

    Regards,

      Bob

  • 0 in reply to Bob Landers
    Expert 1955 points

    Thanks, Bob, for your inputs...

    I've tried these tests - and others - repeatedly at this point. Oddly, 'Board 2' ( the offending citizen here ) does accept a re-flash of the XDS110 firmware per those instructions; always has. As a reminder, I'm comparing two MSP-EXP432P401R LaunchPads in these tests. Board 1 works perfectly in all regards.

    In addition, I've tested build/load cycles in several configurations at this point. The test: I've been 'jumpering' the XDS110 from Board 1 to MSP432 section of Board 2, and vice versa. In all cases, results point to a problem in the MSP432 section of Board 2.

    I'm now convinced of this, as Board 2 runs extremely hot - I hadn't had occasion to notice this before. I mean, it's almost too hot to the touch within 30 seconds of connection to my USB port ( which is worrying on another level...! )

    INTERESTINGLY: This power problem seems to be mediated by the 3V3 jumper on J101. The board remains cool with only the 5V jumper in place. Diagnostic, though I'd leave it to you to determine exactly what of!

    Apart from replacing the inexpensive board itself, do I win the Diagnostician of The Month Award, or similar? ;)

    Lou

  • 0 in reply to LouEEEE!
    TI__Expert 8510 points
    OK, that sounds like the chip has taken some EOS (Electrical Overstress) or ESD damage . In such situations the MSP432 device may still function in many ways, but will pull much more current than it would normally, and some pins may not function correctly while many others still perform normally. Either way, it's definitely time to replace that board!

**Attention** This is a public forum