[ABANDONED] Unable to debug LPC1549 using Jlink

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

  • [ABANDONED] Unable to debug LPC1549 using Jlink

    Hi,

    I recently got LPC1549 microcontroller for my project activities and installed IAR to work on it. To debug the software I am using JLINK V5.12 from segger.com/jlink-software.html

    When I try to debug, Jlink is connected and SWD is recognized. But, later I am getting error stating that "Unable to read CPUID" and then the session aborts after 4 retries.
    I have attached the log file for your verification.


    Kindly help me resolve this issue.

    Thanks and Regards,
    Venkat
    Files

    • cspycomm1.txt

      (164.97 kB, downloaded 508 times, last: )

  • Hi Venkat,

    could you please give J-Link Commander a try? ( in order to see if it works in general)
    J-Link commander is part of the J-Link software package, which is available free of charge here . (You should already have it installed as you mentioned)

    • Start J-Link Commander (jlink.exe)
    • Type "connect" in order to start a debug session
    • Type in the target device name if asked (Or type "?" for a target selection Dialog)
    • Choose the correct target interface (JTAG/SWD/etc..)
    • Use a valid speed (Default: 4000kHz, try 100-500 if default does not work)
    • [JTAG only]JTAG conf can be default(most of the times)
    • You should now be successfully connected.
    If anything fails, could you post a screenshot of the complete session?

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

  • Hi Niklas,

    I tried with the Jlink Commander. But, still I have the same problem. I have attached the screenshot of Jlink Commander and the log file.

    In the log file, I could see the warning "SYSRESETREQ has confused core. Trying to reconnect and use VECTRESET" only after which the debugger exits giving the error "Error: Could not start CPU core."

    Is there any problem with the RESET configuration in JLINK. I have set the Reset option in JLINK to "NORMAL" mode?
    Kindly clarify.


    Thanks in advance!!

    Regards,
    Venkat
    Images

    • Error1.png

      43.35 kB, 1,103×907, viewed 489 times
    Files

    • log.txt

      (5.11 kB, downloaded 585 times, last: )

    The post was edited 2 times, last by venkatareddy ().

  • Hi Venkat,

    could please try again and pass the device name (LPC1549) and not the core name (M3)?

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

  • Hi Niklas,

    I changed the device name to LPC1549 and tried to connect JLINK to target. But, it is not successful.

    I have attached the screen shot. Is there any other solution that I can try?

    Regards,
    Venkat
    Images

    • DeviceName.png

      29.73 kB, 1,100×907, viewed 475 times

  • Hi,

    i will try to reproduce this issue.
    Unfortunately, i do have a LPC1549 eval board with LPC-expresso V2, but the current version of LPCScrypt seems to break the process of flashing the J-Link firmware.
    Therefore, I will have to fix this first...

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

  • Hi Niklas,

    Good day..

    Is there any other workaround to solve this issue?
    If the latest version of LPCScrypt creates this problem, is there any possibility that this error will not occur with the previous version of LPCSrypt?


    Thanks and Regards,
    Ezhil S

  • Hi Venkat,

    sorry for the delay in response.
    I gave it a try and could not reproduce the issue. (see J-Link Commander log below)
    Could you provide us with instruction on how to reproduce the issue?

    C Source Code

    1. SEGGER J-Link Commander V5.41d (Compiled May 20 2016 17:33:35)
    2. DLL version V5.41d, compiled May 20 2016 17:33:01
    4. Connecting to J-Link via USB...O.K.
    5. Firmware: J-Link LPCXpresso V2 compiled May 30 2016 16:14:13
    6. Hardware version: V1.00
    7. S/N: 720000000
    8. VTref = 3.300V
    11. Type "connect" to establish a target connection, '?' for help
    12. J-Link>con
    13. Please specify device / core. <Default>: TM4C129XNCZAD
    14. Type '?' for selection dialog
    15. Device>lpc1549
    16. Please specify target interface:
    17. J) JTAG (Default)
    18. S) SWD
    19. TIF>s
    20. Specify target interface speed [kHz]. <Default>: 4000 kHz
    21. Speed>
    22. Device "LPC1549" selected.
    25. Found SWD-DP with ID 0x2BA01477
    26. Found Cortex-M3 r2p1, Little endian.
    27. FPUnit: 6 code (BP) slots and 2 literal slots
    28. CoreSight components:
    29. ROMTbl 0 @ E00FF000
    30. ROMTbl 0 [0]: FFF0F000, CID: B105E00D, PID: 000BB000 SCS
    31. ROMTbl 0 [1]: FFF02000, CID: B105E00D, PID: 003BB002 DWT
    32. ROMTbl 0 [2]: FFF03000, CID: B105E00D, PID: 002BB003 FPB
    33. ROMTbl 0 [3]: FFF01000, CID: B105E00D, PID: 003BB001 ITM
    34. ROMTbl 0 [4]: FFF41000, CID: B105900D, PID: 003BB923 TPIU-Lite
    35. ROMTbl 0 [5]: FFF42000, CID: B105900D, PID: 003BB924 ETM-M3
    36. Cortex-M3 identified.
    37. J-Link>
    Display All


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