• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Subscribers 80 subscribers
  • Views 316 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.

MSP-EXP432P401R: Unable to run/upload the code

ArTzy
Mastermind 20150 points

Other Parts Discussed in Thread: MSP-FET

Hi Experts,

This is our problem my client is experiencing:

"We can make some code running on MSP432P401R when we have the debugger connected. When we disconnect the debugger and reset the controller, the code is not running anymore. With the example code (gpio toggle) it works fine. Could you give me a hint what we are missing in our project configurations?"

Any thoughts on these?

Thank you for your support.

Regards,
Archie A.

  • 0
    Guru 43445 points

     Do they do a lot of data initialization?

    Can they set a GPIO right as it starts up to see if it is at least getting to main()?

    Can they pare down their program to a bare bones project that shows the problem and share it with us?

  • 0
    TI__Mastermind 27180 points

    Hi Archie,

    • Do you know when in the code it stops executing? It may be tedious but one way to check is using the GPIO pins to blink the LED in a pattern when you are in a certain section, or you could scope certain pins that are in use.
    • Are you going into any low-power mode and not waking up from there?
    • Is the debugger the debugger mode in CCS and they're using the on board eZ-fet or are they using an external debugger like the MSP-FET?
    • Are they using a Launchpad or do they have their own board?
      • If using a custom board, check that the reset has the proper pull-up resistor and that the MCU gets reset properly.

    There shouldn't be a project configuration they need to select to get it to run.

    Regards,

    Luke

  • +1 in reply to Luke Ledbetter
    TI__Mastermind 20150 points

    Hello Keith/Luke,

    Thanks for your support.

    Fortunately, client were able to solve the problem. Here is the problem again:
    Firmware executed flawlessly with the MSP FET plugged in. Without FET not, no matter after which kind of reset.

    The solution: They have to run the controller with 48MHz, for this they turned up the clock; also, the drive strength of the pin, but the core voltage was probably too low with 1.25V. With AM_LDO_VCORE1 in the CPM register they could solve this. The fact that it still needs a wait-state (flash) also took some time. Problem solved! Firmware is running now.

    Thanks.

    Regards,
    Archie A.

  • 0 in reply to Luke Ledbetter
    TI__Mastermind 20150 points

    Hello Luke,

    Client has last query as follows:

    "We would like to know in detail why the programming of the chip works without wait states and with low core voltage as long as the MSP-FET is connected.
    We also noticed that the chip is very often not recognized. Plugging and unplugging the FET probe is constantly necessary to be able to program the chip, no matter if with the EVM or with our own circuit (Error connecting to the target: Unknown device --> this error message is constantly present, it can sometimes be fixed, sometimes unfortunately not. This is very exhausting in the long run, especially because we don't know the cause in detail).
    The next question we have is what exactly happens when you set the option "On connect, perform factory reset" (Debug configurations --> Target --> Connection options)? With this, bricked chips that were thought dead could be programmed after all."

    Thank you for your support.

    Regards,
    Archie A

  • 0 in reply to ArTzy
    TI__Mastermind 27180 points

    The MSP-FET is probably supplying some power to the system which is why you can work the device with a low core voltage as long as the MSP-FET is connected. Also I'd recommend looking at the recommended operating conditions again as 1.25V seems a bit low. Below is a picture of some recommended operating conditions from the datasheet. The second picture is some of the Vcore recommended conditions

    Is that 1.25 for the Vcore voltage? Or what voltage is the 1.25 representing?

    As for a connection issue, it could potentially be a weak connection through the cables or the pins aren't properly connected, which is why unplugging and re-plugging could help.

    The factory reset would wipe the memory and reset the registers, essentially setting properties to how they were when you first received the device. It won't solve any wear and tear the device has or if you ran the device out of operating conditions and damaged the circuits.

    Regards,

    Luke

**Attention** This is a public forum