[SOLVED] NXP S32K144 will not program anymore.

This site uses cookies. By continuing to browse this site, you are agreeing to our Cookie Policy.

  • [SOLVED] NXP S32K144 will not program anymore.

    I think that I somehow set the flash protection bits. Is there a way to recover, or is my board now a paperweight?

    Running Jflash when I connect I get a dialog "Protection bytes in flash at addr 0x400-0x40F indicate that the readout protection is set"
    However when I tell it to go ahead and mass erase it doesn't clear the issue.

    Running J-Link's "unlock Kinetis" command results in "Unlocking device...Timeout while unlocking device."

    When I attempted to connect to my device I got the following output:

    Connecting to target via JTAG
    InitTarget() start
    InitTarget()
    Device will be unsecured now.
    Timeout while unsecuring device. Erase never stops.
    InitTarget() end
    TotalIRLen = 4, IRPrint = 0x01
    JTAG chain detection found 1 devices:
    #0 Id: 0x1993D01D, IRLen: 04, JTAG-DP
    DPv0 detected
    Scanning AP map to find all available APs
    AP[2]: Stopped AP scan as end of AP map has been reached
    AP[0]: AHB-AP (IDR: 0x24770011)
    AP[1]: JTAG-AP (IDR: 0x001C0000)
    Iterating through AP map to find AHB-AP to use
    AP[0]: Skipped. Invalid implementer code read from CPUIDVal[31:24] = 0x00
    AP[1]: Skipped. Not an AHB-AP
    DPv0 detected
    Scanning AP map to find all available APs
    AP[2]: Stopped AP scan as end of AP map has been reached
    AP[0]: AHB-AP (IDR: 0x24770011)
    AP[1]: JTAG-AP (IDR: 0x001C0000)
    Iterating through AP map to find AHB-AP to use
    AP[0]: Skipped. Invalid implementer code read from CPUIDVal[31:24] = 0x00
    AP[1]: Skipped. Not an AHB-AP
    InitTarget() start
    InitTarget()
  • Hi,
    Thank you for your inquiry and sorry for the delay in response.

    This depends on what you wrote to these registers.
    It appears that you locked the device for good.
    In that case, I do not see a way how to recover it.

    If there still is a way to unlock your device, the NXP support will
    most likely be able to point you to it.

    Best regards,
    Fabian
    Please read the forum rules before posting.

    Keep in mind, this is *not* a support forum.
    Our engineers will try to answer your questions between their projects if possible but this can be delayed by longer periods of time.
    Should you be entitled to support you can contact us via our support system: segger.com/ticket/

    Or you can contact us via e-mail.