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.

CCS/MSP432P401R: Unknown device after upgrade to ccs8 simplelink 2.00

Part Number: MSP432P401R

Tool/software: Code Composer Studio

Hi,

After upgrading to ccs8 and simplelink 2.00 my custom board is not more detected, the error that I get is Unknown device. I use MSP FET.

This is the entire error:

CORTEX_M4_0: Trouble Reading Memory Block at 0x20100c on Page 0 of Length 0x4: Could not read device memory
CORTEX_M4_0: GEL: Error while executing OnTargetConnect(): Target failed to read 0x0020100C
	 at gGEL_DeviceID=*((unsigned int *) 0x0020100C) [msp432p401r.gel:247]
	 at OnTargetConnect()
CORTEX_M4_0: Failed Soft Reset: Could not reset device
CORTEX_M4_0: Trouble Writing Memory Block at 0x0 on Page 0 of Length 0x6c88: Could not erase device memory
CORTEX_M4_0: File Loader: Verification failed: Target failed to write 0x00000000
CORTEX_M4_0: GEL: File: /Users/miha/workspace_200/hello_MSP_EXP432P401R_tirtos_ccs/Debug/hello_MSP_EXP432P401R_tirtos_ccs.out: Load failed.



Can somebody help me?

Until now everything was working fine but now I've locked the second custom board.

Is this a known issue? How to solve?

Thank you

Miha

  • I've tried to program from MSPFlasher the example and this is the output:

    * -----/|-------------------------------------------------------------------- *
    * / |__ *
    * /_ / MSP Flasher v1.3.16 *
    * | / *
    * -----|/-------------------------------------------------------------------- *
    *
    * Evaluating triggers...done
    * Checking for available FET debuggers:
    * Found USB FET @ usbmodem1461 <- Selected
    * Initializing interface @ usbmodem1461...done
    * Checking firmware compatibility:
    * FET firmware is up to date.
    * Reading FW version...done
    * Setting VCC to 3000 mV...done
    * Accessing device...done
    * Reading device information...done
    * Loading file into device...
    # Exit: 59
    # ERROR: Could not erase device memory
    * Starting target code execution...done
    * Disconnecting from device...done
    *
    * ----------------------------------------------------------------------------
    * Driver : closed (Could not reset device)
    * ----------------------------------------------------------------------------
    */

    thank you
  • Can you perform a factory reset of the device?

    Chris
  • Unfortunately No,

    I've tried with JTAG and also with XDS110.

    This is very urgent.. what can I try more?

    Miha
  • If I reconnect the programmer to the PCB the red and the green led light flashes 500ms one 500ms the other not simultaneously.
  • Can you focus on the XDS110?  With the XDS110 applied and power, can you see the tool in the device manager (assuming windows)?

    Do you need to reset the XDS110?  You can use the xdsfu.exe . I do not have CCS8 but you should be able to find the tool here ccsv8\ccs_base\common\uscif\xds110.

    Can you select the XDS110 from CCS?  Download a simple piece of example code from the new SDK?

    Regards,

    Chris

  • Can you program a launchpad or target board? Confirm that the issue is not with the custom hardware?

    Regards,
    Chris
  • I can program a launchpad, the hardware was working for few months without any problems, but after upgrading to CSS8 and the simplelink 2.00 + MSP FET firmware upgrade the problem showed.

    I use os x.

    And if I XDS110 or JTAG is the same. Unable to do the factory reset or upload the program.

    Is this a problem of the new MSP FET firmware maybe?

    Miha
  • It is possible that maybe the PJ port where the programming pins are are locked or something like that?
  • Chris, can I ask you if the simplelink sdk 2.00 supports version D of msp432401R?
    For the version C is explicitly written, the D should also be but Better to ask.

    Thank you
  • Revision D of the silicon should be included in the support. I have submitted a bug and asked this to be updated. I also noticed that the macOS only identifies Sierra and I am investigation that as well.

    Do you have any way to utilize the XDS110 on the launchpad to connect to your custom board? What version of the MSP432-Fet adapter (www.ti.com/.../msp-fet-432adptr ) are you using?

    Chris
  • Hi Miha,

    MSP432P401R RevD was tested with MSP-FET before releasing the silicon.

    As you've mentioned that after upgrading to CCS8.0 and the new SDK the issue shows up. Is the same hardware setup working with the CCS & SDK setup you've used before? MSP-FET will automatically downgrade its firmware.

    Best regards,
    Bob Heilmaier

  • Hi Chris,

    I'm attaching a photo of my Hardware(sorry for the quality but my phone camera is not working as it should)

    As you can see my msp fet is attached with a short cable,
    I'm working with the device like 2 months everyday without any problem.
    The working environment is CCS8 + Simplelink SDK 1.40.. 
    With the upgrade to simplelink SDK 2.00 (and CCS8) I've locket two MSP432P401R. Now I don't know exactly if the problem is a combination of CCS8 + SDK 2.0 or just the SDK. The problem is that I'm about to go to production with this hardware and right now I cannot afford to lock my HW. 

    My idea was to upgrade to SDK 2.00 to improve the code usability in the future and improve power consumption.

    If you need I can send you the SN of the msp-fet but I as I can see it works nicely. If I try to program with CCS7 the firmware downgrades, with CCS8 the firmware upgrades.. 

    Miha 

  • Does the hardware setup work with your CCS7 installation?
    Best regards,
    Bob
  • Yes,

    CCS7 + SDK 1.40 Works
    CCS8 + SDK 1.40 Works
    CCS8 + SDK 2.00 Locks

    Regards
    Miha
  • Miha,

    to make sure I get the problem correctly, please do correct me if anything below is not true:

    1. You are working on macOS, CCSv8.0 and MSP432 SDK 2.10?
    2. You are using pre-production harware with MSP-FET which worked before upgrading to the new SDK version?
    3. You also own a XDS110 which is also not capable to get a connection to the hardware after it got locked?

    If all above is true (especially the 3. item), please try to connect your XDS110 to the hardware using the 10pin connector from your picture and follow the steps from SLAU575 (Chapter 8.1 "Factory Reset Without Password")

    Best regards,
    Bob

  • Miha,

        Thank you for sending the picture - it is clear enough.  Per Bob's request, can you use the XDS110 from the launchpad instead?

    Regards,

    Chris

  • Hi Cris/Bob,

    I've tried with the black xds110 but unfortunately I cannot reset the device.
    Should it work with the black board or only with the red one?

    P.S. I'm having problems finding the rev C(red board in the EU) farnell ships only the old ones.

    Thank you
  • Hi Miha,

    there should be no difference between using the XDS110 of the black or the red LaunchPad.

    You're saying that you cannot reset the device. Have you tried the steps from my comment above? At which step are you failing?

    Thanks,

    Bob

  • Hi Bob,

    I'm working on macOS, CCSv8.0 with SDK 1.40 right now.

    The hardware that I'm working right now is a custom made PCB with a MSP432P401 rev D.

    With the setup(look at the attached photo) I'm getting stack at connecting to the device following the chapter "Factory Reset..."

    Is there something other that I can try?

    thank you

    Miha

  • According to the chapter, you don't need to connect to the device but to the Debug Access Port (DAP).
    Have you performed the steps exactly according to the manual? If yes, please post at which step you are failing.
    Bob
  • Hi,

    One detail regarding the Black Launchpad. Its connector is not the output of the embedded XDS110 probe but instead the JTAG input of the built-in MSP432. The connection shown in the last photograph will never work.

    Check section 2.3.3 of the SLAU597A

    Regards,

    Rafael

  • Hi Rafael/Bob,

    I thought that the 10pin connector is for this, now I've tried like you suggested me and it worked!
    I've unlocked my two boards :D

    Thank you so much!

    Miha