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.

MSP432P401R: MSP Flasher not attempting to program

Part Number: MSP432P401R
Other Parts Discussed in Thread: MSP-FET

I'm attempting to flash an MSP432P401R using MSP Flasher and get different results on two different PCs. The left image shows it working correctly on one PC while the right image shows the other PC doesn't even attempt to flash the device. The commands are essentially identical aside from the "-s" flags which I also tried removing afterwards for completeness sake. I ran the command line in administrator mode to ensure that wasn't the issue. Any ideas?

  • On the PC that doesn't work, it looks like if I add the -z flag to it, I do see errors. Why is that? Also, I've read the documentation but still don't understand what -z [VCC] is actually supposed to do. I thought it may try to power the Microcontroller through the MSP-FET, but it doesn't seem to work?

    C:\ti\MSPFlasher_1.3.20\MSP430Flasher.exe -i COM8 -n MSP432P401R -e ERASE_MAIN -w "C:\firmware.hex" -z [VCC, RESET]

    * -----/|-------------------------------------------------------------------- *
    * / |__ *
    * /_ / MSP Flasher v1.3.20 *
    * | / *
    * -----|/-------------------------------------------------------------------- *
    *
    * Evaluating triggers...done
    * Checking for available FET debuggers:
    * Found USB FET @ COM8 <- Selected
    * Initializing interface @ COM8...done
    * Checking firmware compatibility:
    * FET firmware is up to date.
    * Reading FW version...done
    * Setting VCC to 3000 mV...done
    * Accessing device...done
    * Resetting device (RST/NMI)...done
    * Starting target code execution...
    # Exit: 10
    # ERROR: Internal error
    * Resetting device (RST/NMI)...done
    * Starting target code execution...
    # Exit: 10
    # ERROR: Internal error
    * Resetting device (RST/NMI)...done
    * Starting target code execution...
    # Exit: 10
    # ERROR: Internal error
    * Resetting device (RST/NMI)...done
    * Starting target code execution...
    # Exit: 10
    # ERROR: Internal error

  • Hi Derrick,

    I just wanted to check if you are trying this with the same MSP432P401R board from 2 different PCs or if you are testing with 2 different MSP432P401R boards.

    Srinivas

  • I'm using the same boards on both PCs. At this point, I'm assuming there's an issue with the physical setup on the PC that is failing to program the boards. It's using a custom-built fixture and I'm in the process of verifying that the debug pins are routing correctly from the MSP-FET to the target boards and that they're powered correctly.

    My questions at this point are with the MSP Flasher software. What is the purpose of the -z [VCC] flag since it doesn't seem to provide the target board power? Why is it that when I omit the -z flag, the software doesn't even ATTEMPT to flash firmware on the target board? It doesn't give an error. It just exits without doing anything.

  • HI Derrick,

    I think the FET drives the power pin whether it is used by the target board or not. I think the -z is used to provide the exit specifications. From the User's guide (https://www.ti.com/lit/pdf/slau654), the error code 10 says "Could not set device Vcc". It is not clear when the MSP Flasher just exits without doing anything. I am assuming you already tried rebooting the PC.

    Srinivas

  • Srinivas,

    We figured out the wiring issue on our setup and can flash firmware to our boards now.

    I still don't understand what the purpose of the -z [VCC] flag is. If I flash firmware with this flag set, the target board resets properly and I'm able to communicate with one of the application UARTs on the board without power cycling.

    If I use -z [RESET], the target board DOES NOT reset properly. I'm unable to communicate with the application UART on the board. I have to power cycle the board first, and then the application UART starts functioning.

    Neither flag appears to do what I'd expect. Is there any clarification for what is really going on here? Our solution for now is to simply use -z [VCC] since it works, but it doesn't make any sense.

  • HI Derrick,

    Your description seems to match this table below from that User's guide  (https://www.ti.com/lit/pdf/slau654):

    Derrick said:
    I still don't understand what the purpose of the -z [VCC] flag is. If I flash firmware with this flag set, the target board resets properly and I'm able to communicate with one of the application UARTs on the board without power cycling.

    With -z [VCC], the target execution starts as mentioned in the Table, and so you are able to communicate without power cycling.

    Derrick said:
    If I use -z [RESET], the target board DOES NOT reset properly. I'm unable to communicate with the application UART on the board. I have to power cycle the board first, and then the application UART starts functioning.

    With -z [RESET], the table says, the target board is powered down and hence you are not able to communicate.

    If your intent is for it to reset but be ready to communicate, you might need to use both options which is the last entry in the table. -z [RESET, VCC] which will provide the reset but then the target execution also starts.

    At least, that is what I understand the symptoms you are describing. Hope that helps.

    Srinivas