• Locked Locked
  • Replies 16 replies
  • Subscribers 81 subscribers
  • Views 9611 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.

MSP432 LAUNCHPAD doesn't work

Eduardo Jagher
Intellectual 320 points
Other Parts Discussed in Thread: TM4C1294NCPDT

Hello guys,

I bought the MSP432 launchpad a week ago and my unboxing wasn't happy, it didn't even blink the LEDs. Only startup the USB drivers, but no out of box demo, no communication with CCS. I checked the voltages and the weldings with a microscope, but nothing weird. Somebody have the same problem? I'm starting think to buy another one.

Thanks

  • TI__Guru**** 219737 points

    Hello Eduardo,

    What is your XDS110 device enumerating as on your computer? It should come up as two COM ports: XDS110 Class Application/User UART and XDS110 Class Auxiliary Data Port. If not I would reference the FAQ (Section 5) of the MSP‑EXP432P401R LaunchPad Evaluation Kit User's Guide: www.ti.com/.../slau597.pdf

    Here's a link to the necessary XDS drivers: processors.wiki.ti.com/.../XDS_Emulation_Software_Package

    Regards,
    Ryan

  • Guru 74080 points
    Eduardo,

    the LaunchPad comes pre-programmed, so normally the demo program should work even without the drivers. This is the blink example that measures the time between your button presses and adjusts the blink frequency according to this time. Does this work?

    Did you install CCS with the MSP432 LaunchPad or did you install it some time prior to the MSP432? If yes, you maybe might not have the support for the MSP432 installed and therefore no drivers for the XDS as well. You can re-run the installer, adding the MSP432 support in this case.

    Dennis
  • in reply to Dennis Eichmann
    Intellectual 320 points
    Dennis,

    The blink example doesn't work. I added the support for MSP432 to my CCS and I be able to create a project and build it to a MSP432 microcontroller, but when I try to flash the device on Launchpad an error occur, today I don't have my Launchpad to specify the problem, but tomorrow I will try to analise this problem and the USB controller of my computer to give you those informations.

    Eduardo
  • in reply to Eduardo Jagher
    Guru 74080 points
    Does the power LED on the emulator side light up?
  • in reply to Dennis Eichmann
    Intellectual 320 points
    No LEDs turn on, but the power is OK (I measure the voltages).
  • in reply to Eduardo Jagher
    Guru 74080 points
    That is very strange - the green LED should light up when connected to the USB, regardless of the program that is currently running in the MSP. Have you tried to remove the connecting jumpers between emulator and processor side?

    Dennis
  • in reply to Dennis Eichmann
    Intellectual 320 points

    I tried to remove the jumpers, no effect. But the USB controller enumerate the device as a (Stellaris Device Firmware Upgrade).

  • in reply to Eduardo Jagher
    Guru 74080 points

    Look at this thread:

    Is your one getting hot, too?

  • in reply to Dennis Eichmann
    Intellectual 320 points
    No integrated circuit has getting hot, it behavior is like the emulator and the device wasn't programmed.
  • in reply to Eduardo Jagher
    TI__Expert 7125 points

    Eduardo,

    It sounds like the emulator program is not functioning properly. You can reprogram the emulator with the following steps:

    Navigate to the XDS110 folder in your installation of CCS. If installed in the default location you will find it here:

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

    Follow instructions in the ReadMe file  under

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

    to reprogram the XDS110.

  • in reply to MikeS
    Guru 74080 points
    Just had a look into the schematic of the MSP432 LaunchPad - LED102 (the green "power" LED) isn't hardwired to power. Was thinking this all the time...it is controlled by the TM4C. So MikeS' suggestion sounds to be the most probable one. Good to know that.
  • in reply to MikeS
    Intellectual 320 points
    MikeS,

    Thank you for your help, I'm trying to update de firmware but was happened a problem with the xdsdfu.exe, it opens and suddenly close, I will try in my house tha is windows 7. The problem is (ERROR: No file was specified. The file name is required.)

    Thanks,
  • in reply to MikeS
    Prodigy 50 points

    Hi everyone,

    I got some weeks ago an "broken" MSP432LP, too. So I connected the support and got a payback for this broken board.
    (btw. very convenient procedure - 100% satisfying ! - I hope the money will come in the next weeks, hehe 8=) ) 

    Well, as I am some kind of "interested" in solving that kind of errors, I got deeper into it.
    All voltages are ok and no visual defects on the board are found. So I supposed that the XDS110 was delivered with 
    wrong or no software - the usb-port was fine and my pc found an stellaris update device so far... but no green POWER-LED lit on.

    That made me think of my first thought of an incomplete software in the XDS110-part. Then I soldered the debug pins
    for the XDS110 (TM4C1294) and used another MSP430LP (the new one) as an external debugger/programmer.

    Like the procedure to reactivate a "bricked" MSP432LP as described in slau597 (MSP-EXP432P401R_EvalKitDoc.pdf) page 27ff,
    I connected it via CCS6.1. I activated the CS_DAP_0 and included the file "tm4c1294ncpdt.gel". Then I set "show all cores"
    and connected the CS_DAP_0 with the script included. After that I connected to the "main-core" tm4c1294ncpdt,

    With the ability to run and debug the core, I tried again to update the firmware, found at ..\ccsv6\ccs_base\common\uscif\xds110.
    That didn´t work before - the XDS110 was in upload-mode, but I got an "error 4 - usb-update went wrong" (like this)...

    This time I got lucky - firmware update was ok and after that the green Power-LED got lit (bright green !!!) => Hoooray...

    In the end, I was able to build and program the Out-of-the-box-software...

    A bricked Launchpad was reborn again... (but took about 4h of preparation and tryout..)

    If someone got a similiar problem, I could make a detailed howto to solve that problem.

    Greetz.......Detlef

  • in reply to Detlef Lampart
    TI__Expert 7125 points
    Eduardo,

    Any update on your progress? Was the command line DFU tool able to solve your problem?

    Detlef,

    Thanks for the detailed update. Your procedure accomplishes the same as mine posted above. The difference being that yours goes through JTAG to the TM4C129 and mine goes through the DFU (to avoid soldering and/or making custom debug cable). However, your method should be pretty much fool-proof, and my method only works with an updated DFU. If there was truly no programming from the factory (which should NEVER be the case) - your method would work where mine would fail. This is because the DFU tool relies on an updated DFU in the device. However this also means that your method may solve the problem now, and may not be able to update in the future where the DFU is used.

    I would be curious what DFU is in your TM4C device. Are you able to run the command line DFU tool above? Or is the only access through the JTAG connection you made?
  • in reply to MikeS
    Prodigy 50 points

    Mike,

    first I tried to access via the DFU-Mode and appropriate software (xdsdfu.exe) as described. There I got "error 4 - dfu error" - so

    I believe the DFU-Part didn´t work correctly. Then I connected via a homebrew-adapter the two MSP432 - one as programmer

    to the external (and bricked) one. There I "resetted" the ARM-Core similar as the procedure described for a bricked

    MSP432-Main.MCU (not XDS110). After that I did the DFU-update via the known way (switch to up/download.mode - program firmware.bin
    with xdsdfu.exe)

    So as the well-known procedure worked out, I suppose future updates via DFU shall work, too.

     If there exists an "special" firmware for the programmer-part (XDS110), then updating this part with the correct "DFU-firmware" should work, too.
    (and will give a future function for coming updates)...

    Well - an interesting question - is this "DFU-firmware" available and when, where could it be found ? I suppose that the XDS110 is completely

    programmable, as it is "open source" and therefore perhaps the software is available... Or is there some "magic" portion of software in it ?

    PS: I will be thankful for a link - hehe 8=)

    Greetz.......Detlef

  • in reply to MikeS
    Intellectual 320 points
    Hello Mike,

    I'm sorry for the delay. I decide to buy another one and try to programming the old one like Detlef showed to us. Thank you for your help and up to the next problem/discussion.

    Eduardo.

**Attention** This is a public forum