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.

MSP432P411V: Can't read the memory [CPU core halt sequence problem]

Part Number: MSP432P411V
Other Parts Discussed in Thread: UNIFLASH

Hi,

My customers made a product using MSP430P411V. They want to check the checksum after writing the firmware to the chip. However, we can't access the MSP432P411V.

We also can't access using XDS200 and Uniflash. Therefore, factory reset cannot be used.
Written area: 0x0000 0000 ~ 0x0007 FFFF

When they wrote to the chip using XDS110 or I-jet, it worked fine. However, if they write it using third-party tool or MSPGANG, they will not be able to read the memory.

Question 1:
What does the error message mean?

/////
Checking device ID…
EC: FB / FB / FB / FB / FB / FB / FB / FB / 5
CPU Core halt sequence problem
////

Question 2:
How do we reset the chip?

Best regards,
Rei

  • Hi Rei,

    I can't find the information on "CPU core halt sequence problem" on MSP Gang Programmer (MSP-GANG) User's Guide (Rev. Q)

    I guess this issue is related with JTAG hardware connection on the board and MSPGANG. May I know which board user using?

    if user can program the MSP432P411V using XDS110 and I-jet, please continue using them instead of MSPGANG.

    Thanks!

  • Hi Xiaodong,

    Sorry, I don't know what board the customer is using. When customers access the chip using XDS200 and Uniflash, they get the following error code:

    Error connecting to the target:
    (Error -1141 @ 0x0)
    Device is not responding to the request. Reset the device, and retry the operation.
    If error persists, confirm configuration, power-cycle the board, and/or try more reliable
    JTAG settings(e.g. lower TCLK).
    (Emulation package 8.3.0.00003)

    They are in the same state with CCS. We're in trouble because we can't factory reset this.

    Would you tell me how to recover this chip? I also suspect HW.. but I want to know the information from the error code.

    Regards,

    Rei