[SOLVED] LPC546xx SPIFI Erase problem

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

  • [SOLVED] LPC546xx SPIFI Erase problem

    Hello,

    I am using the J-Link probe to erase and flash the NXP LPC54608J512 microcontroller.
    The J-Link version I am using is V6.82 and the target I use is LPC54608J512 (allow ECRP).

    I get the message "Error while determining flash info (Bank @ 0x10000000)"

    The problem is in erasing the SPIFI Flash but I have no SPIFI Flash connected to the microcontroller.

    The problem is the same as this post:
    forum.segger.com/index.php/Thr…xx-SPFI-Flashing-Problem/

    Complete output:
    Type "connect" to establish a target connection, '?' for help
    J-Link>connect
    Please specify device / core. <Default>: LPC54608J512
    Type '?' for selection dialog
    Device>?
    Please specify target interface:
    J) JTAG (Default)
    S) SWD
    TIF>S
    Specify target interface speed [kHz]. <Default>: 4000 kHz
    Speed>2000
    Device "LPC54608J512 (ALLOW ECRP)" selected.


    Connecting to target via SWD
    Found SW-DP with ID 0x2BA01477
    Found SW-DP with ID 0x2BA01477
    DPIDR: 0x2BA01477
    Scanning AP map to find all available APs
    AP[1]: Stopped AP scan as end of AP map has been reached
    AP[0]: AHB-AP (IDR: 0x24770011)
    Iterating through AP map to find AHB-AP to use
    AP[0]: Core found
    AP[0]: AHB-AP ROM base: 0xE00FF000
    CPUID register: 0x410FC241. Implementer code: 0x41 (ARM)
    Found Cortex-M4 r0p1, Little endian.
    FPUnit: 6 code (BP) slots and 2 literal slots
    CoreSight components:
    ROMTbl[0] @ E00FF000
    ROMTbl[0][0]: E000E000, CID: B105E00D, PID: 000BB00C SCS-M7
    ROMTbl[0][1]: E0001000, CID: B105E00D, PID: 003BB002 DWT
    ROMTbl[0][2]: E0002000, CID: B105E00D, PID: 002BB003 FPB
    ROMTbl[0][3]: E0000000, CID: B105E00D, PID: 003BB001 ITM
    ROMTbl[0][4]: E0040000, CID: B105900D, PID: 000BB9A1 TPIU
    ROMTbl[0][5]: E0041000, CID: B105900D, PID: 000BB925 ETM
    Cortex-M4 identified.
    J-Link>erase
    Erasing device (LPC54608J512 (allow ECRP))...
    J-Link: Flash download: Total time needed: 1.926s (Prepare: 0.079s, Compare: 0.000s, Erase: 1.840s, Program: 0.000s, Verify: 0.000s, Restore: 0.005s)

    ****** Error: Failed to prepare RAMCode using RAM
    Error while determining flash info (Bank @ 0x10000000)
    ERROR: Erase returned with error code -1.


    Thanks in advance,
  • Hi,
    Thank you for your inquiry.

    We will look into this.If a QSPI is not always present, J-Link should not try to erase it by default.

    For now, you could use the latest beta release in combination with the new erase range command (erase <SAddr>,<EAddr).

    Best regards,
    Fabian
    Please read the forum rules before posting: Forum Rules

    Keep in mind, this is not a support forum. Its main purpose is user to user interaction.
    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.
  • Hi,
    UPDATE:
    The QSPI for this device was falsely marked as "always present".

    A fix will be part of the next patched release, planned for later today.
    It will be available for download here:
    segger.com/downloads/jlink#J-L…twareAndDocumentationPack

    Thank you for making this known to us.
    We are sorry for any inconvenience caused.

    Best regards,
    Fabian
    Please read the forum rules before posting: Forum Rules

    Keep in mind, this is not a support forum. Its main purpose is user to user interaction.
    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.
  • Hi,

    The version is now available.

    Could you please come back to us if this fixed the issue for you?

    Best regards,
    Fabian
    Please read the forum rules before posting: Forum Rules

    Keep in mind, this is not a support forum. Its main purpose is user to user interaction.
    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.