• State
  • Locked Locked
  • Replies 5 replies
  • Subscribers 31 subscribers
  • Views 413 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:

MSP432P401R launchpad DOA?

MSP432E401Y: Launchpad enumerates and appears to flash firmware but does not work

Braden Hines
Intellectual 370 points
Part Number: MSP432E401Y


I just received a batch of 3 new MSP432E401Y Launchpads. They are all freshly removed from the packaging, no changes to jumpers or anything.

I plugged in the first two to my Windows PC and went through the process of updating the firmware from within CCS and then downloading my application.  Everything was fine.

The third one, however, failed to be recognized in CCS.  So I uncorked xdsdfu and am trying to use that to update it.  Here's what I get.  First, when I plug the board into the PC, it already comes up in DFU mode, and the serial number is all zeros:

C:\ti\ccs1011\ccs\ccs_base\common\uscif\xds110>xdsdfu -e

USB Device Firmware Upgrade Utility
Copyright (c) 2008-2019 Texas Instruments Incorporated. All rights reserved.

Scanning USB buses for supported XDS110 devices...


<<<< Device 0 >>>>

VID: 0x1cbe PID: 0x00ff
Device Name: Tiva Device Firmware Update
Manufacturer: Texas Instruments Incorporated
Serial Num: 00000000
Mode: DFU

Found 1 device.

C:\ti\ccs1011\ccs\ccs_base\common\uscif\xds110>xdsdfu -m

USB Device Firmware Upgrade Utility
Copyright (c) 2008-2019 Texas Instruments Incorporated. All rights reserved.

Scanning USB buses for supported XDS110 devices...

Device is already in DFU mode. No switch necessary.

From there, it appears to respond normally to commands.  For example, when I go to flash the firmware, it pauses for a while at "Downloading firmware_3.0.0.14.bin to device...", but then nothing changes:

C:\ti\ccs1011\ccs\ccs_base\common\uscif\xds110>xdsdfu -f firmware_3.0.0.14.bin -r

USB Device Firmware Upgrade Utility
Copyright (c) 2008-2019 Texas Instruments Incorporated. All rights reserved.

Scanning USB buses for supported XDS110 devices...

Downloading firmware_3.0.0.14.bin to device...

C:\ti\ccs1011\ccs\ccs_base\common\uscif\xds110>xdsdfu -e

USB Device Firmware Upgrade Utility
Copyright (c) 2008-2019 Texas Instruments Incorporated. All rights reserved.

Scanning USB buses for supported XDS110 devices...


<<<< Device 0 >>>>

VID: 0x1cbe PID: 0x00ff
Device Name: Tiva Device Firmware Update
Manufacturer: Texas Instruments Incorporated
Serial Num: 00000000
Mode: DFU

Found 1 device.

Unplugging from USB and plugging back in also has no effect.  Still just comes up in DFU mode.

Attempting to set the serial number is also a no-op:

C:\ti\ccs1011\ccs\ccs_base\common\uscif\xds110>xdsdfu -s ME40FSim -r

USB Device Firmware Upgrade Utility
Copyright (c) 2008-2019 Texas Instruments Incorporated. All rights reserved.

Scanning USB buses for supported XDS110 devices...

Setting serial number to "ME40FSim"...

C:\ti\ccs1011\ccs\ccs_base\common\uscif\xds110>xdsdfu -e

USB Device Firmware Upgrade Utility
Copyright (c) 2008-2019 Texas Instruments Incorporated. All rights reserved.

Scanning USB buses for supported XDS110 devices...


<<<< Device 0 >>>>

VID: 0x1cbe PID: 0x00ff
Device Name: Tiva Device Firmware Update
Manufacturer: Texas Instruments Incorporated
Serial Num: 00000000
Mode: DFU

Found 1 device.

I also tried the procedure for "Recovering a Bricked XDS110 without JTAG", where you short pin 97 to GND.  I have successfully used this procedure in the past to recover bricked devices, but like everything else, it had no effect on this board.

The only other thing I can report is that the board has no LED's illuminated. 

How can I get this board up and running?

Thanks,
Brad

  • 0
    TI__Mastermind 39855 points

    My advice is that you can use XDS110 to read out the code saved in TIVA MCU on XDS110, and download it into the bad one.

    It may be a choice.

  • 0 in reply to Eason Zhou
    Intellectual 370 points

    Hi Eason,

    Thanks for your reply and advice.

    Are you suggesting to simply read the firmware out of one Launchpad and burn it into another?  If so, I already have a known-good firmware file, that I burned into two other Launchpads at the same time I tried to burn this one.  It's just that this Launchpad doesn't act like it's actually been flashed.

    If you are suggesting something different, can you elaborate on what steps I should take?

    Thanks,
    Brad

  • 0 in reply to Braden Hines
    TI__Mastermind 39855 points

    I advice you to connect our customer support team to replace one board or change a TIVA MCU by yourself: 

  • 0 in reply to Eason Zhou
    Intellectual 370 points

    Hi Eason,

    Thanks for the reply.  I apologize, but I just don't understand your suggestion.  What do you mean by "change a TIVA MCU by yourself"?  It sounds like that would involve desoldering it and soldering a new one? (!)  I'm guessing that you must mean something different.

    I can exchange the board if need be, but would like to salvage it if possible - I've already soldered a 98-pin connector to it, which takes about 20 minutes.  And then given that exchanging a board will take another 20 minutes (and might be difficult - it was provided to me by my customer, so I don't have any sort of invoice), I'd be willing to spend up to 40 minutes trying to get it working.

    Also, can you explain in any more detail what your suggestion in your first reply meant?

    Thanks,
    Brad

  • 0 in reply to Braden Hines
    TI__Mastermind 39855 points

    Hi Brad,

    As you can program the code into TIVA MCU, I think we can't say it is broken.

    As you can't change a launchpad, I think you need to debug the board by yourself. What I mean is that I think the problem mostly caused by TIVA MCU, I advise you to re-solder a new one by yourself. My reply before is too arbitrary. I think you need to debug it first.

    1. Check the signal on XDS_DP and XDS_DM and compared them with other boards. I think you can find some information from this signal. 

    Eason