• State Resolved
  • Locked Locked
  • Replies 8 replies
  • Subscribers 30 subscribers
  • Views 1211 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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: MSP432 LaunchPad no longer useable

Ted Fryberger
Intellectual 780 points

Part Number: MSP-EXP432P401R

My MSP-EXP432P401R LaunchPad was working fine. Bought a BOOSTXL-SHARP128 boost pack and plugged it into the LP. Now when I try to download a successfully built program I get some combination of the following error messages.

CORTEX_M4_0: * WARNING *: The connected device is not MSP432P401R
CORTEX_M4_0: GEL Output: Memory Map Initialization Complete
CORTEX_M4_0: GEL Output: Halting Watchdog Timer
CORTEX_M4_0: Error initializing flash programming: Your XMS432P401R material is no longer supported. We recommend you moving to production-quality MSP432P401R/M silicon by ordering samples at www.ti.com/product/MSP432P401R.

CORTEX_M4_0: Loader: One or more sections of your program falls into a memory region that is not writable. These regions will not actually be written to the target. Check your linker configuration and/or memory map.

CORTEX_M4_0: File Loader: Verification failed: Values at address 0x00007FF0 do not match Please verify target memory and memory map.
CORTEX_M4_0: GEL: File: D:\Product\DIGS\Code\DC2\MCU2-432\432-uSD\fatsd_MSP_EXP432P401R_nortos_ccs\Debug\fatsd_MSP_EXP432P401R_nortos_ccs.out: a data verification error occurred, file load failed.

Tried this with and without a microSD memory card inserted, then unplugged the Boost pack, then tried a different PC and get the same errors. What's the story with this?

  • 0
    TI__Mastermind 32825 points

    HI,

    You are using the early sample chip XMS432P401R not the production device MSP432P401R. The functions are limited on the early sample chips. You need to get a production one to replace it.

    Best regards,

    Cash Hao

  • 0 in reply to Cash Hao11
    Intellectual 780 points

    Thanks, but I disagree.

    This board was working fine it is the red board, Rev 2.1 which wasn't purchased that long ago. And if I look at the two MCU's on board the labels on top are: MSP432P401R Rev D for the general purpose MCU, and MSP432E401YT Rev B for the FET MCU.

    What is causing these error messages?

  • 0 in reply to Ted Fryberger
    Guru 91610 points

    From your description, the "XMS432" reference is spurious -- the chip is incommunicado, so the (PC) software guesses.

    The usual repair for this kind of thing is the Factory Reset procedure described in the Launchpad UG (SLAU597F) Sec 5. 

    These sorts of lockouts usually result from errant software (e.g. bad clock settings) rather than installing new hardware. Did you download any software just before you installed the booster pack?

  • 0 in reply to Bruce McKenney47378
    Intellectual 780 points

    I'm trying to do a factory reset of the 432 LP based on the LP UG section 5.

    But when I View  >> Target Configurations - I'm not seeing XDS110, I'm seeing MSP432P401R.ccxml

    From here I follow the steps in the UG, but never see a default script for Factory Reset. Many scripts are listed but no Factory Reset.

  • 0 in reply to Bruce McKenney47378
    TI__Mastermind 32825 points

    Hi Bruce，

    For some early sample chips, we actually do have this kind of markers on the chip. This kind of chip should only be used on some early evaluation projects and have limited functions. I am not sure where does this customer get this chip because we do not selling them to the customer.

    Best regards,

    Cash Hao

  • 0 in reply to Ted Fryberger
    Guru 91610 points

    I just went through the procedure, and got the expected results, though I also saw MSP432P401R.ccxml, not xds100v2.ccxml. 

    My only thoughts:

    1) Be sure to "connect to target" CS_DAP_0 (under "Non Debuggable Devices"), not CORTEX_M4_0.

    2) I was using CCSv8. I suppose it's possible things have changed in later versions.

  • 0 in reply to Cash Hao11
    Guru 91610 points

    Hi Cash,

    I have a small collection of XMS432s (Black Launchpads) in a box somewhere. CCS, starting with (I think) v8, refuses to do anything with them, whether they're working or not.

    When the OP mentioned that the Launchpad had been working before the incident, that told me that he had a Red Launchpad (with an MSP432), and the message was bogus. I've also seen that XMS432 message in cases where I had been cruel to a Red Launchpad.

  • +1
    Intellectual 780 points

    Hi Bruce,

     

    Thanks for the info, that was the problem, using CS_DAP I was able to do a factory reset on the board which is now working again. Thanks for your help. The E2E website has been down all day, I will close the issue when it’s back up.

     

    Ted