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.

Emergency restore of MSP432 (bricked) emulator

Other Parts Discussed in Thread: TM4C1294NCPDT

Hi,

I'd like to know is it possible to reprogram emulator side (TM4C129) of MSP432 (using maybe another MSP432 board) in case USB connection is lost due to unsuccessful reprogramming of an emulator?

Thank you in advance,

Alexey

  • Hi Alexey,

    Yes this is possible, we have done it before. Please let us know if you run into any issues.

    Best regards,

    David
  • I have a MSP432 board and lost USB connectivity due to unsuccessful reprogramming using the 'ti\ccsv6\ccs_base\common\uscif\xds110\xdsdfu.exe' tool.
    I see some connections for emulator: TP101-110, but of course, don't have any hardware and software tools to make a restore.
    I do not pretend to give such tools to me or make any service, since such actions may lead to leak some intellectual properties in emulator side.
    But CCS recommendations about bad USB connectivity needs to clarify about possible consequences or post it directly in a 'flashing' utility.

    Regards,
    Alexey

  • Oh, David,
    Thank you for your feedback.
    The solution is actually included in Readme.txt file.

    Regards,
    Alexey

  • Hi Alexey,

    Before trying to update the TM4C with the debugger, please try re-programming the bootloader using the xdsdfu.

    1. Flash bootloader: xdsdfu –b boot_loader.bin
    2. Flash firmware: xdsdfu –f firmware.bin

    Regards,

    David
  • Here actually documented process for lost USB recovering:

    1) Ground the JTAG TDO pin of the XDS110's Tiva CPU.  This is pin 97

    on the 128 pin device.  This is a JTAG pin for flashing the XDS110 via

    JTAG; it is not the JTAG TDO pin of the debug target. If the board has

    a JTAG header for flashing the XDS110 you may use that, otherwise you

    can ground the pin on the device. (Check the TM4C1294NCPDT datasheet

    for the pin location; it is located on a corner and easy to access.)

    2) Unplug and re-plug the XDS110 into the host PC while the pin is grounded.

    3) The XDS110 should now be in DFU programming mode and you can flash it

    using the xdsdfu utility as detailed above.

  • No, it doesn't work, - after grounding pin97 and power-cycle, USB connectivity didn't appear to make a connection with an utility.
  • There is a specific note about that:

    This feature is currently only implemented in the XDS110 boot

    loader that was first available in emupack 6.0.15.0. If your XDS110's

    boot loader is an earlier version, this procedure won't work. In the boot

    loaders from emupack 5.1.537.0, the target JTAG TCK pin was used instead.

    If your device used that version of the boot loader, try the procedure

    by grounding the target TCK pin. If your XDS110's boot loader is an even

    earlier version, this procedure won't work at all, and you'll need to use

    JTAG to recover.

     


    Probably my board is even older (BLACK version).

  • OK, is it possible to reprogram 'bricked' board using normal 'RED' board with such utility by JTAG pins connectivity?

  • Hi Alexey,

     The RBIAS (R139) is missing and this resistor is required (pin 59 to GND,  4.87K)  for the DFU to work on a blank part. That might be the reason why the xdsdfu is not working.

    Alexey Bagaev said:
    OK, is it possible to reprogram 'bricked' board using normal 'RED' board with such utility by JTAG pins connectivity?

    Yes this is possible.

      Best regards,

       David

  • I've tried with 4.84k. Didn't work.
  • Never mind,
    After reflashing the 'bootloader' and 'firmware' on the working RED board, my connectivity problems in CCS in debug mode (which many users on E2E told about) disappeared. I haven't done any hardware manipulations in that case except software polling for DFU.

    All works good on it. Connectivity test result:

    "The SWD Mode Integrity test has succeeded."

    Regards,
    Alexey

**Attention** This is a public forum