MSP432P401R launchpad DOA?

Hi Julian,

What -e option in the xdsdfu are you referring to? Refer to the ReadMe.txt inside the xds110 folder on instructions to update the probe.

How to update the firmware and change the serial number.

*** Updating the Firmware Using xdsdfu. ***

You can update the XDS110 firmware using the xdsdfu program included
in this directory over the USB connection.

To program the firmware, follow these steps:

1) Plug the XDS110 debug probe into your computer. Make sure that you
only have one XDS110 class debug probe plugged in. The xdsdfu program
will attempt to flash the first XDS110 debug probe it finds.

2) Run the following two commands from this directory:

xdsdfu -m
xdsdfu -f firmware.bin -r

You may need to pause after the first command to give the OS time to
recognize that the XDS110 has reconfigured as a different USB device.

Once the second command completes, the firmware is updated, and the
debug probe should be ready to use.


Sincerely,
Sean

Hi Sean,

Thanks for your response. 

the -e option is an option to scan and list any enumerated devices on the computer - it's listed in the command line help response of the program. 

But yes, when I run xdsdfu -m I also get a report that no devices are found.... Same goes for the firmware flash command...

MSP432 bboard is plugged in and still flashing away from when I ran the out of box experience GUI and played with the flashing LED... Devices still showing in windows device manager as in screenshot in OP...

So.. do I have a dead unit?? 

 

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

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

Scanning USB buses for supported XDS110 devices...


Found 0 devices.

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

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

Scanning USB buses for supported XDS110 devices...

The requested device was not found on the bus.

C:\ti\ccsv6\ccs_base\common\uscif\xds110>

Hi Julian,

During the installation of CCS, did you install the MSP432 drivers as well? Also, could you check CCS for any available updates? 

It is possible that the debugger is nonfunctional.

Just to verify, could you try running the commands again and waiting for a while before the second command? Let me know if the same issue persists.

xdsdfu -m

xdsdfu -f firmware.bin -r

Sincerely,

Sean

When I installed CCS 2 or so weeks ago, I installed basically just for CC3200.

Then I wanted to play with the edu boosterpack MK2, and while it seems mostly compatible with the CC3200 launchpad I have, I thought it would be best to start using it with the proper MSP432 board... so I ordered that too... 

When the new stuff arrived last week, I first went to try and use CCS cloud for something interesting to try - but I didn't really feel it was useful for what I want to do, so I ignored it.

Then I went into CCS and got it to download the 432 stuff, and the example projects stuff, (MSPware??) and the TI arm compiler, plus arm GCC.. nowhere I saw anything about needing extra drivers, and the fact that the thing shows up in my devices panel (and nobody has picked the screenshot I showed as having an issue) then I should expect the drivers to be there?? 

I guess I could always nuke my CCS install and start again, but really prefer not to as I have spent so long download/installing everything I use when I wiped my PC the other week... 

Just tried playing with xdsdfu again... (xdsdfu -m) still no board found. can still see it in my system panel as before... 

So: 

1) given the screenshot in my OP, is my driver installed right, or not?? 

2) is there any way in CCS that I can look for what drivers are installed? 

3) what do you consider a minimum verifiable test to determine if this board is actually busted or if software is wrong? I can't find it with xdsdfu but it shows up in system panel as shown in the picture in my first post here... 

thanks!

so.....................

?

Hi Julian,

Sorry for the late reply, I am in training all of this week. The issue is that the debugger hardware is recognized, however, a firmware update cannot be completed for the debugger. To make sure MSP432 drivers are installed in CCS, go to Help->Installation Details. The below screenshot should help verify driver installation. 

The launchpad is working since the startup program can boot on the Launchpad, the issue is the debugger connection. The hardware is recognized, however, the firmware update utility cannot connect. A probable cause after verifying drivers and assuming the debugger is functional, may be a faulty USB connection, so could you try to connect via another USB port? 

Sincerely,

Sean

Hi Sean,

I went to have a look and all of those were installed.

but before going to try one last time with a new USB port (had already tried more than one) , I noticed a new download had become available - for the MSP432 emulator?? anyway - I downloaded and installed that, then plugged in my MSP432 board and hit debug - it came up with a different issue (emulator needed update) so I let it do that, and now I'm in debug!! thanks so much for your help. It looks like this latest update fixed my particular issue... 

Now, to get the boosterpack XL stuff up and running!

thanks again!

so much for getting excited things were working.

After being able to import and run a couple of the demo projects (accelerometer, audio FFT) I went to play with the joystick demo, and during download, I got some dialog box talking about the debugger process failing, and recommending I should retry at a lower speed setting.... then anything I have tried after that (including full PC reboot) looks like either the target processor is now cactus, or the debug probe or its driver is now failed in a different way to before.

Does anyone reading this forum have an actual success story with their MSP432P401R launchpad board, where it actually worked out of the box for more than just 2 demo projects?? 

ok... DONE! and working again...
thank you.

This has been an awful lot of fiddling to get some demo projects up and running on this eval board.. I take it this MSP432 thing is pretty new, eh? haven't seen anything like this on the CC3200s I've had for a while now, and they're cortex M4 cores, too...

Anyway - does this kind of reset need to happen more often?
Should I consider slowing down debug link speed for anything I do with the MSP432 eval board, in order to make it more reliable?

thanks again!

Julian

Hi Julian,

Glad to hear the launchpad is now working for you. The reset shouldn't be required often, I think this is only an issue with the initial use of the debugger. But if you run into any more troubles, feel free to reach out to E2E for trouleshooting.

Sincerely,
Sean

exactly the same error, but cant do factory reset, the error is shown belwo

MSP432_Factory_Reset() cannot be evaluated.
Could not write register DP_RESET: target is not connected
at DP_RESET=1 [msp432_factory_reset.gel:44]
at MSP432_Factory_Reset()

Hi Jun,

Your particular error has been posted in a prior E2E thread, I've linked it below for your reference.

e2e.ti.com/.../481815

Sincerely,
Sean