[SOLVED] J-Link Dave 4 Win 10 crashed Driver

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

  • [SOLVED] J-Link Dave 4 Win 10 crashed Driver

    Hello, I am sorry in advance for my poor skills, I just started programming microcontroller for university matter. In fact I am about to ride a paper for an example experiment within a course. Therefore I need to (already prepared hardware by my supervisor) use an XMC 4500 Relax (Lite) Kit of Infineon and I am using also DAVE 4 V6 with J-Link on Win 10 Pro N 64-Bit.

    As I said I dont know much about yet, but thats why I choose this topic. However I dont want to get just a solution, but also an understanding why my problem is appearing, if possible.

    The Debugger wont work properly (according to my supervisor), but he is convinced, the problem is upt to my OS. So he suggested using another Os (such as Win 7 with Virtual Box for example). Anyhow I tried this and it actually did work. But it would be easier to use the Debugger on my primary OS so I thought somebody is able to help me or give some advise where/how to look for solutions.

    The PNG shows what exactly is happening when debug project for the first time. I also qouted the Console output.

    <terminated, exit value: -1>JLinkGDBServerCL.exe
    SEGGER J-Link GDB Server V6.00d Command Line Version
    JLinkARM.dll V6.00d (DLL compiled Jul 29 2016 19:07:54)

    -----GDB Server start settings-----
    GDBInit file: none
    GDB Server Listening port: 2331
    SWO raw output listening port: 2332
    Terminal I/O port: 2333
    Accept remote connection: localhost only
    Generate logfile: off
    Verify download: on
    Init regs on start: on
    Silent mode: off
    Single run mode: on
    Target connection timeout: 0 ms
    ------J-Link related settings------
    J-Link Host interface: USB
    J-Link script: none
    J-Link settings file: none
    ------Target related settings------
    Target device: XMC4500-F100x1024
    Target interface: SWD
    Target interface speed: 1000kHz
    Target endian: little

    Connecting to J-Link...
    J-Link is connected.
    Firmware: J-Link Lite-XMC4000 Rev.1 compiled Apr 2 2015 18:25:20
    Hardware: V1.00
    S/N: 551010176
    Checking target voltage...
    Target voltage: 3.30 V
    Listening on TCP/IP port 2331
    Connecting to target...Connected to target
    Waiting for GDB connection...Connected to 127.0.0.1
    Reading all registers
    Read 4 bytes @ address 0x00000000 (Data = 0x2000FF3C)
    Read 2 bytes @ address 0x00000000 (Data = 0xFF3C)
    Target interface speed set to 1000 kHz
    Resetting target
    Halting target CPU...
    ...Target halted (PC = 0x08000200)
    R0 = E000ED08, R1 = 00000263, R2 = 02000080, R3 = C8000201
    R4 = 00000536, R5 = 00000000, R6 = 00000000, R7 = 00000000
    R8 = 00000000, R9 = 0C000004, R10= 00000000, R11= 00000000
    R12= 00000000, R13= 10000800, MSP= 10000800, PSP= 00000000
    R14(LR) = 000000ED, R15(PC) = 08000200
    XPSR 01000000, APSR 00000000, EPSR 01000000, IPSR 00000000
    CFBP 00000000, CONTROL 00, FAULTMASK 00, BASEPRI 00, PRIMASK 00
    Reading all registers
    Read 4 bytes @ address 0x08000200 (Data = 0xD08CF8DF)
    Read 2 bytes @ address 0x08000200 (Data = 0xF8DF)
    Select auto target interface speed (1539 kHz)
    Flash breakpoints enabled
    Read 4 bytes @ address 0x08000200 (Data = 0xD08CF8DF)
    Downloading 4096 bytes @ address 0x0C000000 - Verified OK
    Downloading 4096 bytes @ address 0x0C001000 - Verified OK
    Downloading 4096 bytes @ address 0x0C002000 - Verified OK
    Downloading 4096 bytes @ address 0x0C003000 - Verified OK
    Downloading 4096 bytes @ address 0x0C004000 - Verified OK
    Downloading 4096 bytes @ address 0x0C005000 - Verified OK
    Downloading 788 bytes @ address 0x0C006000 - Verified OK
    Downloading 272 bytes @ address 0x0C006314 - Verified OK
    Read 4 bytes @ address 0x08000200 (Data = 0xD08CF8DF)
    Resetting target
    Halting target CPU...
    ...Target halted (PC = 0x08000200)
    Starting target CPU...
    GDB closed TCP/IP connection
    Restoring target state and closing J-Link connection...

    <terminated, exit value: 0>arm-none-eabi-gdb
    GNU gdb (GNU Tools for ARM Embedded Processors) 7.10.1.20160210-cvs
    Copyright (C) 2015 Free Software Foundation, Inc.
    License GPLv3+: GNU GPL version 3 or later
    <http://gnu.org/licenses/gpl.html>
    This is free software: you are free to change and redistribute it.
    There is NO WARRANTY, to the extent permitted by law. Type "show
    copying"
    and "show warranty" for details.
    This GDB was configured as "--host=i686-w64-mingw32
    --target=arm-none-eabi".
    Type "show configuration" for configuration details.
    For bug reporting instructions, please see:
    <http://www.gnu.org/software/gdb/bugs/>.
    Find the GDB manual and other documentation resources online at:
    <http://www.gnu.org/software/gdb/documentation/>.
    For help, type "help".
    Type "apropos word" to search for commands related to "word".
    Warning: the current language does not match this frame.
    <terminated, exit value: 0>Semihosting and SWV
    SEGGER J-Link GDB Server V6.00d - Terminal output channel
    Connection closed by the GDB server.
    Thanks in advance.

    PS: In addition I may say, that the microcontroller itself does work properly, as well as a comport connection from matlab itself.
    Images

    • debug_fehler.PNG

      69.15 kB, 1,776×1,065, viewed 1,395 times

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

  • Hi,

    first of all: In order to get you up and running asap, I would recommend to give Ozone a try. Its a standalone debugger which just needs an ELF file in order to setup a debug session with J-Link.

    Regarding W10 not working and W7 working:
    My first guess is that the W7 machine is running an up-to-date version of the J-Link software & documentation pack , which fixes some bugs in J-Link GDB Server.

    If the issue persists when using the most recent version of the J-Link software, could you please provide us with J-Link logfiles from both a failed and a working debugging session?
    (Please attach the unedited logs as a textfile to a post)
    Log output can be enabled like as follows:
    • Open a connection to J-Link, e.g start J-Link Commander
    • In J-Link Control Panel: (Click the J-Link symbol located in the notification / tray area in order to open J-Link Control panel)
    • Open the tab "Settings"
    • Next to the field "Log file" check "Override" and click "..." in order to choose a log file path.

    This is also described in UM8001 Chapter 5 "Working with J-Link and J-Trace", Section 5.7 "J-Link control panel" .

    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,


    sorry, but I do not understand these log files.
    1) The Windows 7 log just says that it could not connect to a J-Link via USB (mostly likely due to that none is connected to the PC). I thought that it supposed to work in Win 7?
    2) The Windows 10 log looks fine but than immediately stops all of the sudden as if the caller crashed or sth. like that.


    In order to narrow down the list of possible causes of this issue:
    Could you please give J-Link Commander a try?

    • 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.
    • It is now possible to program a binary file(.bin/.mot/.srec/.hex etc.) via the >loadfile< command
    • The commands >r<, >g<, >h<, >s< can be used for reset, go, halt and step.
    • Breakpoints can be set by using the >setbp< command.
    If anything fails, could you please post a screenshot and a logfile 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.

  • Hello Again. My bad...dont know what went wrong with the win7-logfile...

    There are to different now (both worked I guess, I even could control the LED via hterm as plannend), i created just now. And also another WIN 10 logfile, if necessary (but it looks like the same, should i worry about the "old firmware"?)

    I will try to do what you asked for...even i am not sure, what exactly you mean by complete session.
    Files

    • win7_2.txt

      (183.67 kB, downloaded 544 times, last: )

    • win7_3.txt

      (146.95 kB, downloaded 515 times, last: )

    • win10_2.txt

      (24.66 kB, downloaded 556 times, last: )

  • Hi,

    I will try to do what you asked for

    Thanks! It sounds like more work than it is, should be doable in <5 minutes.
    even i am not sure, what exactly you mean by complete session.

    J-Link Commander is a console application. Therefore, by complete session I mean everything that has been printed into the console window since the start of the 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.

  • I am propably doing something wrong (not a 100 percent sure, what i am doing exactly, but

    J-Link>loadfile 04_brightness.hex C:\Users\...\04_brightness\Debug
    Downloading file [04_brightness.hex]...
    Failed to open file.
    J-Link>
    does not work. Properly an syntax error or I am using the wrong adress...

    But I have to go on now, so I wil try it again later.

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

  • Hi,


    the syntax for loadfile is "loadfile <path> [<address>]", where address is only used for .bin files, as they do not include location information.

    For hexfiles, the path is sufficient, as in "loadfile C:\Temp\app.hex" .

    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.

  • Hello.
    Sorry, was quite busy yesterday.

    It seems to work with J-link...at least I can connect, set breakpoints, go, halt, reset. I did this first with the commander in win7 (see first png for complete session and first txt for logfile) and after with win10 (see 3rd txt).
    Unfortunately I am not quite able to fully understand how to read this.
    Images

    • jlink_win7_session1.PNG

      45.08 kB, 638×794, viewed 725 times
    Files

  • Hi,


    sorry for the delay in response.
    First of all, it shows that debugging with J-Link works on both systems.

    The text shown after each step is the disassembly of the executed step.
    We also ship a sophisticated Debugger with GUI, Ozone.

    If the issue with Dave 4 still persists, could you please provide us with the GDB version used on each system?
    If they differ, does it work when using the working version instead on the noon-working setup?


    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.

  • O.K. ...

    From what I have seen, GDBServer never crashed but it was always GDB that closed the connection (maybe due to crashing).
    As both are independent processes, it cannot be a problem in GDBServer (which is the SEGGER component)

    My guess:
    There was some internal problem in DAVE that caused GDB to crash when evaluating a specific part of debug information in the ELF file etc.
    However, it is just a guess.

    Let's close this case for now.

    - Alex
    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.