[ABANDONED] JLINK Unspecified Error -1

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

  • [ABANDONED] JLINK Unspecified Error -1


    I'm getting the following error after flashing from a commander script Unspecified error -1 and was wondering if there is an issue with my commander script?

    When I keep re-running the commander script I always get the same error, until I open up MCUxpresso and running it from the play button there.

    Here is my commanderscript:

    Source Code

    1. device LPC54102J256_M4
    2. si 1
    3. speed 2000
    4. erase
    5. loadfile test.hex
    6. sleep 100
    7. r
    8. g
    9. exit

    and here is the full output error log:

    Source Code

    1. SEGGER J-Link Commander V6.56b (Compiled Dec 6 2019 15:02:40)
    2. DLL version V6.56b, compiled Dec 6 2019 15:02:24
    3. J-Link Command File read successfully.
    4. Processing script file...
    5. J-Link connection not established yet but required for command.
    6. Connecting to J-Link via USB...O.K.
    7. Firmware: J-Link V10 compiled Nov 8 2019 16:40:12
    8. Hardware version: V10.10
    9. S/N: 50109947
    10. License(s): GDB
    11. VTref=3.341V
    12. Selecting SWD as current target interface.
    13. Selecting 2000 kHz as target interface speed
    14. Target connection not established yet but required for command.
    15. Device "LPC54102J256_M4" selected.
    16. Connecting to target via SWD
    17. Found SW-DP with ID 0x2BA01477
    18. Scanning AP map to find all available APs
    19. AP[1]: Stopped AP scan as end of AP map has been reached
    20. AP[0]: AHB-AP (IDR: 0x24770011)
    21. Iterating through AP map to find AHB-AP to use
    22. AP[0]: Core found
    23. AP[0]: AHB-AP ROM base: 0xE00FF000
    24. CPUID register: 0x410FC241. Implementer code: 0x41 (ARM)
    25. Found Cortex-M4 r0p1, Little endian.
    26. FPUnit: 6 code (BP) slots and 2 literal slots
    27. CoreSight components:
    28. ROMTbl[0] @ E00FF000
    29. ROMTbl[0][0]: E000E000, CID: B105E00D, PID: 000BB00C SCS-M7
    30. ROMTbl[0][1]: E0001000, CID: B105E00D, PID: 003BB002 DWT
    31. ROMTbl[0][2]: E0002000, CID: B105E00D, PID: 002BB003 FPB
    32. ROMTbl[0][3]: E0000000, CID: B105E00D, PID: 003BB001 ITM
    33. ROMTbl[0][4]: E0040000, CID: B105900D, PID: 000BB9A1 TPIU
    34. ROMTbl[0][5]: E0041000, CID: B105900D, PID: 000BB925 ETM
    35. Cortex-M4 identified.
    36. Erasing device...
    37. Comparing flash [000%]100%] Done.
    38. Erasing flash [000%]000%]010%]010%]025%]025%]035%]035%]050%]050%]060%]060%]075%]075%]085%]085%]100%] Done.
    39. J-Link: Flash download: Total time needed: 0.956s (Prepare: 0.062s, Compare: 0.000s, Erase: 0.890s, Program: 0.000s, Verify: 0.000s, Restore: 0.004s)
    40. Erasing done.
    41. Downloading file [test.hex]...
    42. Comparing flash [000%]000%]040%]040%]050%]100%] Done.
    43. Erasing flash [000%]100%] Done.
    44. Programming flash [000%]000%]000%]000%]000%]000%]000%]000%]005%]005%]005%]005%]005%]005%]005%]005%]010%]010%]010%]010%]010%]010%]010%]010%]015%]015%]015%]015%]015%]015%]015%]015%]020%]020%]020%]020%]020%]020%]020%]020%]025%]025%]025%]025%]025%]025%]025%]025%]030%]030%]030%]030%]030%]030%]030%]030%]035%]035%]035%]035%]035%]035%]035%]035%]040%]040%]040%]040%]040%]040%]040%]040%]045%]045%]045%]045%]045%]045%]045%]045%]050%]050%]050%]050%]050%]050%]050%]050%]055%]055%]055%]055%]055%]055%]055%]055%]060%]060%]060%]060%]060%]060%]060%]060%]065%]065%]065%]065%]065%]065%]065%]065%]070%]070%]070%]070%]070%]070%]070%]070%]075%]075%]075%]075%]075%]075%]075%]075%]080%]080%]080%]080%]080%]080%]080%]080%]085%]085%]085%]085%]085%]085%]085%]085%]090%]090%]090%]090%]090%]090%]090%]090%]095%]095%]095%]095%]095%]100%] Done.
    45. Verifying flash [000%]000%]080%]080%]100%] Done.
    46. J-Link: Flash download: Bank 0 @ 0x00000000: 1 range affected (163840 bytes)
    47. J-Link: Flash download: Total time needed: 1.266s (Prepare: 0.097s, Compare: 0.022s, Erase: 0.000s, Program: 1.090s, Verify: 0.014s, Restore: 0.042s)
    48. Unspecified error -1
    49. Reset delay: 0 ms
    50. Reset type NORMAL: Resets core & peripherals via SYSRESETREQ & VECTRESET bit.
    51. Reset: Halt core after reset via DEMCR.VC_CORERESET.
    52. Reset: Reset device via AIRCR.SYSRESETREQ.
    53. Script processing completed.
    Display All
    Any ideas of what I am doing wrong would be greatly appreciated!

    Thanks in advance
  • Hi,
    Thank you for your inquiry.
    Such an issue is not known to us.

    Does this behavior also appear when using the newest J-Link Software and Documentation Pack version?
    You can download it here:
    If so, could you please verify if the target was successfully programmed and running after executing the script?

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