[SOLVED] Flashing LPC8N04 not working

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

  • [SOLVED] Flashing LPC8N04 not working

    Hello together,

    I want to flash a LPC8N04 device with my J-Link EDU device.
    Unortunately I rarely can even connect to the device.
    If connection works and I try to execute the erase command following error message is shown:

    Source Code

    1. Connecting to target via SWD
    2. Found SW-DP with ID 0x0BC11477
    3. AP map detection skipped. Manually configured AP map found.
    4. AP[0]: AHB-AP (IDR: Not set)
    5. AP[0]: Core found
    6. AP[0]: AHB-AP ROM base: 0xE00FF000
    7. CPUID register: 0x410CC601. Implementer code: 0x41 (ARM)
    8. Found Cortex-M0 r0p1, Little endian.
    9. FPUnit: 4 code (BP) slots and 0 literal slots
    10. CoreSight components:
    11. ROMTbl[0] @ E00FF000
    12. ROMTbl[0][0]: E000E000, CID: B105E00D, PID: 000BB008 SCS
    13. ROMTbl[0][1]: E0001000, CID: B105E00D, PID: 000BB00A DWT
    14. ROMTbl[0][2]: E0002000, CID: B105E00D, PID: 000BB00B FPB
    15. Cortex-M0 identified.
    16. J-Link>erase
    17. **************************
    18. WARNING: T-bit of XPSR is 0 but should be 1. Changed to 1.
    19. **************************
    20. Erasing device (LPC8N04)...
    21. ****** Error: Timeout while erasing sectors, RAMCode did not respond in time. (PC = 0xFFFFFFFF, CPSR = 0xFFFFFFFF, LR = 0x01000003)!
    22. J-Link: Flash download: Total time needed: 10.540s (Prepare: 0.381s, Compare: 0.000s, Erase: 10.056s, Program: 0.000s, Verify: 0.000s, Restore: 0.102s)
    23. ERROR: Erase returned with error code -5.
    24. J-Link>
    Display All


    How can I programm this MCU?

    Additional Information:

    VTref detection works.
    When I press the reset button the LED at J-Link turns orange.
    SWDIO and SWDCLK linkes show activity (checked with oscilloscope)
    -> I assume connection between MCU und J-Link is correct

    Used HW is thisdev-kit. I seperated the boards and I only try to program the LPC8N04 on the right board.
    Information and schematics can be found in the "Software & Tools" category for the dev-kit link.

    Best Regards,
    Timo
  • Hello Timo,

    Thank you for your inquiry.
    Such an issue is not known to us.
    Which J-Link software version are you using?
    Does using the latest version solve the issue?

    Best regards,
    Nino
    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.
  • Hello Nino,

    it looks like bad quality control on NXP side: The chip is not soldered properly on the board!

    I found out could connect more often when touching the chip itself.
    After some retouching with an solder iron I can now reliably connect to the part.

    Erasing still fails with the same error though.
    J-Link SW Version is 6.30i.

    EDIT:
    Feel free to close this thread as the reason for the failure is most likely not caused by SEGGER.
    Thank for your time.

    Best Regards,
    Timo

    The post was edited 1 time, last by tkr ().

  • Hello Timo,

    The erase issue was reproducible. J-Link assumed the target has 32 kB available instead of actually 30 kB (the information that the last 2 kB are not available was placed inconveniently in the manual).
    The issue is fixed now and it will be available with our next J-Link software release.
    Sorry for any inconveniences caused.

    Best regards,
    Nino
    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.
  • Hello,

    The fix is not part of the current beta release V6.31h and will be part of the next official release V6.30k.

    We will consider this case as closed now.

    Best regards,
    Nino
    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.