[SOLVED] I can not work with J-Link for a long time.

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

  • [SOLVED] I can not work with J-Link for a long time.

    Hello.
    There are two debuggers - Base and devboard ST-Link-> J-Link. All the defects are approximately the same, I did not notice a difference in behavior.
    There are two problems.
    Problem number 1.
    If you start debugging, open the Control Panel J-Link, then after ~ 20 minutes the debugged processor falls off in J-Link.
    How to repeat the test? Start debugging, open the Control Panel and go to dinner. When you come, you will be waiting for a surprise.
    The defect is stable.
    Problem number 2.
    Debugging is started and is left in this form. After a while (the figure will be lower) everything stops. In Control Panel J-Link there are no errors, everything is just worth it. The JLinkLog.txt file has a length of 134 MB (62 GB on the disk). At the end of the file the following text:


    T18E4 18971:753 JLINK_IsHalted() returns FALSE (0000ms, 426641ms total)
    T18E4 18971:854 JLINK_ReadMemU32(0xE0001004, 0x0001 Items, ...) - Data: CA F3 2A 02 returns 0x01 (0000ms, 426641ms t
    T0C40 18971:854 JLINK_ReadMem (0x00000000, 0x0001 Bytes, ...) -- CPU_ReadMem(1 bytes @ 0x08000000) - Data: 40 return
    T0C40 18971:854 JLINK_ReadMem (0x20000110, 0x0001 Bytes, ...) -- CPU_ReadMem(1 bytes @ 0x20000110) - Data: A6 return
    T0C40 18971:855 JLINK_ReadMem (0x00000000, 0x0004 Bytes, ...) -- CPU_ReadMem(4 bytes @ 0x08000000) - Data: 40 09 00 2
    T0C40 18971:856 JLINK_ReadMem (0x20000140, 0x0020 Bytes, ...) -- CPU_ReadMem(32 bytes @ 0x20000140) - Data: 00 00 00
    T0C40 18971:856 JLINK_ReadMem (0x20000120, 0x0004 Bytes, ...) -- CPU_ReadMem(4 bytes @ 0x20000120) - Data: 01 00 00 0
    T0C40 18971:857 JLINK_ReadMem (0x2000011C, 0x0004 Bytes, ...) -- CPU_ReadMem(4 bytes @ 0x2000011C) - Data: 01 00 00 0
    T0C40 18971:857 JLINK_ReadMem (0x2000023F, 0x0020 Bytes, ...) -- CPU_ReadMem(32 bytes @ 0x2000023F) - Data: 00 00 00
    T0C40 18971:858 JLINK_ReadMem (0x00000000, 0x0001 Bytes, ...) -- CPU_ReadMem(1 bytes @ 0x08000000) - Data: 40 return
    T0C40 18971:859 JLINK_ReadMem (0x20000112, 0x0002 Bytes, ...) -- CPU_ReadMem(2 bytes @ 0x20000112) - Data: 20 02 ret
    T0C40 18971:861 JLINK_ReadMem (0x20000114, 0x0002 Bytes, ...) -- CPU_ReadMem(2 bytes @ 0x20000114) - Data: A4 F4 ret
    T0C40 18971:862 JLINK_ReadMem (0x20000116, 0x0002 Bytes, ...) -- CPU_ReadMem(2 bytes @ 0x20000116) - Data: 28 3C ret
    T0C40 18971:864 JLINK_ReadMem (0x20000144, 0x0002 Bytes, ...) -- CPU_ReadMem(2 bytes @ 0x20000144) - Data: 00 00 ret
    T0C40 18971:864 JLINK_ReadMem (0x20000124, 0x0004 Bytes, ...) -- CPU_ReadMem(4 bytes @ 0x20000124) - Data: 00 00 00 0
    T0C40 18971:865 JLINK_ReadMem (0x20000128, 0x0004 Bytes, ...) -- CPU_ReadMem(4 bytes @ 0x20000128) - Data: 00 00 00 0
    T0C40 18971:865 JLINK_ReadMem (0x2000043D, 0x0020 Bytes, ...) -- CPU_ReadMem(32 bytes @ 0x2000043D) - Data: 02 48 F4
    T0C40 18971:868 JLINK_ReadMem (0x20000118, 0x0002 Bytes, ...) -- CPU_ReadMem(2 bytes @ 0x20000118) - Data: 00 00 ret
    T0C40 18971:868 JLINK_ReadMem (0x00000000, 0x0004 Bytes, ...) -- CPU_ReadMem(4 bytes @ 0x08000000) - Data: 40 09 00 2
    T0C40 18971:869 JLINK_ReadMem (0x00000000, 0x0004 Bytes, ...) -- CPU_ReadMem(4 bytes @ 0x08000000) - Data: 40 09 00 2
    T0C40 18971:869 JLINK_ReadMem (0x00000000, 0x0004 Bytes, ...) -- CPU_ReadMem(4 bytes @ 0x08000000) - Data: 40 09 00 2
    T0C40 18971:870 JLINK_ReadMem (0x2000013D, 0x0001 Bytes, ...) -- CPU_ReadMem(1 bytes @ 0x2000013D) - Data: 00 return
    T0C40 18971:870 JLINK_ReadMem (0x2000013C, 0x0001 Bytes, ...) -- CPU_ReadMem(1 bytes @ 0x2000013C) - Data: 00 return
    T18E4 18971:871 JLINK_IsHalted() returns FALSE (0001ms, 426654ms total)
    T18E4 18971:974 JLINK_IsHalted() returns FALSE (0000ms, 426653ms total)
    T18E4 18972:074 JLINK_IsHalted() returns FALSE (0000ms, 426653ms total)
    T18E4 18972:176 JLINK_IsHalted() returns FALSE (0000ms, 426653ms total)
    T18E4 18972:277 JLINK_IsHalted() returns FALSE (0000ms, 426653ms total)
    T18E4 18972:377 JLINK_ReadMemU32(0xE0001004, 0x0001 Items, ...) - Data: CA F3 2A 02 returns 0x01 (0000ms, 426653ms t
    T0C40 18972:377 JLINK_ReadMem (0x00000000, 0x0001 Bytes, ...) -- CPU_ReadMem(1 bytes @ 0x08000000) - Data: 40 return
    T0C40 18972:377 JLINK_ReadMem (0x20000110, 0x0001 Bytes, ...) -- CPU_ReadMem(1 bytes @ 0x20000110) - Data: A6
    *** Max log file size reached, file closed. ***
    Images
    • jl02.png

      94.12 kB, 843×798, viewed 608 times
  • Re: I can not work with J-Link for a long time.

    Hi,

    then after ~ 20 minutes the debugged processor falls off in J-Link.

    Do we understand you correctly?:
    It looks like J-Link loses connection to the target MCU and further debugging is not possible.

    When you are returning from "dinner":
    Is your PC in a stand-by, hibernate etc. mode so you need to login again etc, or is it just as you left it (maybe the display as been turned off etc.)?

    Would it be possible to provide us a reference project that allows you to reproduce the issue on an eval board?
    We are asking for the project to make sure that it is not something specific to the project / application that causes this behavior.
    The longer you run the session, the higher the chance to run into a timing critical issue, you won't encounter when only having a short debug session.
    We would like to reproduce the problem here.

    Reg. problem 2:
    There is currently a max. log file specified inside the J-Link SW, to make sure it does not pollute the SSD/HDD in and endless way when running a debug session multiple days.
    We will check regarding specifying a higher logfile size etc.
    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, Leon.
    If you are interested in testing the problem, then I did the following test - I blocked working with the JLinkLog.txt file (the error of creating a file in the dll was simulated). Now the debugger works without a problem with the time, the photo is attached.
    Increase the limit of 100000000 is not necessary. Please, remove the log file altogether.
    Images
    • jl03.png

      37.72 kB, 566×381, viewed 406 times
  • In error with Control Panel - I changed the log settings and more. Now this defect is not manifested.
    Let's assume that the "I" was mistaken. When I can clearly determine the conditions of occurrence, I'll write separately.
    Thank you.
  • Hi,

    Thanks for your feedback.
    Increase the limit of 100000000 is not necessary. Please, remove the log file altogether.

    No, we are definitely not doing that.
    The log file is the basis for every support case.

    Let's assume that the "I" was mistaken. When I can clearly determine the conditions of occurrence, I'll write separately.

    O.K., please feel free to open another thread for this. This one will be closed as the issue is assumed to be solved for now, based on the posts.
    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.