Search Results

Hi, SEGGER does not maintain the Eclipse plugins/add-ons or provide support for them. We are not aware of any issues, so the best option would be to have a look at the documentation/forums of the plugin or contact the developers. Best regards Johannes

Hi Alberto, Thank you for pointing this out. We will change the RTT Viewer to show warnings in a non-intrusive way. The Telnet connection option is generally meant to attach to a running debug session and get the RTT output from it instead of opening a second connection to J-Link / target. For Telnet you can use any Telnet client of your choice and even create your own application. To be able to use RTT via Telnet it would be sufficient to start J-Link Commander and specify the target device (e.…

Hello, To view multiple threads and their information the debug server (GDB Server / OpenOCD) requires information about which OS is running and how it is handled. For J-Link GDB Server, there is currently no OS Awareness available, so it is not possible to view multiple threads. This is on our long-term todo, but with no fixed schedule, yet. Best regards Johannes

Hi, Currently J-Link can only be used with the 32-bit version of DS-5. Support for the 54 bit version is planned for the future, but with no current schedule. Selecting GDB Server in the Debug Configuration is intended to be used to do remote application debugging, so debugging an application created with DS-5 running on an embedded Linux on the target hardware. J-Link GDB Server is used for bare-metal/kernel debugging. In fact it does not matter which target processor to chose when selecting GD…

Hi, Could you provide screenshots of your Debug Configuration? Normally GDB Server does not reset the target itself on disconnect. Best regards Johannes

Hi Mark, Has been fixed in V4.96l, available for download at segger.com/jlink-software.html Regards Johannes

Hi Mark, Thank you for your report. We were able to reproduce the problem here, too, and already found a solution. It will probably be included in the next patched release version. Although it might not cause problems if you are not using it, if you are running multiple instances of GDB Server you should consider setting -swoport and -telnetport as well. Best regards Johannes

The screenshot shows you are starting GDB Server without configuration. I am not sure what target device you are using, but it is mandatory to tell GDB Server. Could you try starting GDB Server the following way: jlinkgdbservercl.exe -device <YourDeviceName> -if JTAG -speed 1000 (e.g. jlinkgdbservercl.exe -device STM32F407IE -if JTAG -speed 1000) Regards Johannes

Quote: “So is it correct to use "monitor halt" instead of issuing a "ctrl+c" from gdb as currently if I issue a ctrl+c command I get an error on jlinkgdbserver saying that could not halt the core, but doing monitor halt seems to work fine.... ” Sounds strange. Issuing Ctrl-C should work, too. Which version of GDB and GDB Server are you using and which target device? Normally monitor halt should not be used. Quote: “ "GDB receives only a string response like "Writing register (PC = 0x...)" In my …

Hello, Using the monitor commands will not do any update in GDB. The command is simply passed to GDB Server and GDB receives only a string response like "Writing register (PC = 0x...)". Therefore monitor commands which interferer with the debug debugging behavior (breakpoints, go, halt) and require some state update in GDB should only be used when this cannot be issued with a native GDB command. So instead of "monitor go" "countinue" should be used, "break" instead of "monitor setbp" and "set $p…

Hello Matjaz, Thank you for sharing your results with PuTTY. You are right, this information can sometimes be very valuable. We will add timestamps to RTT Viewer in a future version, too. Best regards Johannes

Hello, Quote: “ If I change the PC register to point to the entry point of the flash code and resume execution, the breakpoint at main() is hit. (I then resume execution again and it eventually ends up back to running code from ROM again. I don't believe that the processor is in the correct state when I force it to jump to my code.) It is clear that the J-Link debugger is not configuring the processor to boot from flash. ” Normally, after loading the application, GDB sets the PC to the entry poi…

Hi, The interface library required to use J-Link with DS-5 is only available for Windows 32-bit systems. Support for DS-5 on Linux might be added, but there is currently no time frame for this. Regards Johannes

Hi, There is currently no Linux version of RTT Logger or RTT Viewer. Do you want to use RTT on the Terminal Channel (Channel 0)? RTT Logger is built to log data sent on Channel 1. The current solution on Linux would be to start J-Link Commander (JLinkExe), set device, interface and speed (i.e.via command line options: JLinkexe -device <DeviceName> -speed <SpeedInkHz> -if <SWD|JTAG>) and then start the RTT Client or connect via a Telnet Client to localhost:19021 A client which attaches directly t…

Hello, Quote: “After launching app in debugger and connecting to Jlink RTT Client I can set correct address in the Jlink Controll panel but by then the output is "stale" -- i.e. not exactly real-time. ” What target device are you using? RTT can only be used with targets which allows background memory access while running, which are Cortex-M devices. Quote: “I think the __jlinkExecCommand ("SetRTTAddr 0x20000000") is the right answer but how do I get it compiled into the application? There may be…

Hello Ankur, In general yes, the external RAM needs to be accessible and initialized before loading to it. This can be done with GDB and GDB Server with monitor memU8/16/32 commands as described in Chapter 3.3.3 in the J-Link User Manual (UM08001). Other special handling to debug the kernel should not be necessary. Best regards Johannes

Hi, As already written in the thread, multiple instances of GDB Server / multiple connections to J-Link are not supported on Linux / OS X and there is currently no specific schedule when this will be available. To receive information as soon as it is available we recommend subscribing to the J-Link Notification List (segger.com/notification/subscribe.php?prodid=7). We are also trying to update all relevant threads when specific features are available. Best regards Johannes

Hi, What JTAG speeds are you using in the J-Flash project? Maybe they are really too high as indicated by the error message. Could you provide your J-Flash project file? Best regards Johannes

The main differences between J-Link BASE and J-Link ULTRA+ are the interface speeds. J-Link BASE: - Full-Speed USB 2.0 - Up to 1MByte/Sec download speed into RAM - Maximum JTAG/SWD interface speed 15 MHz - Maximum SWO sampling frequency 7.5 MHz J-Link ULTRA+: - Hi-Speed USB 2.0 - Up to 3 MByte/Sec download speed into RAM - Maximum JTAG/SWD interface speed 50 MHz - Maximum SWO sampling frequency 100 MHz Additionally J-Link ULTRA+ includes licenses for "Unlimited Flash Breakpoints", J-Flash, RDI a…

Hello, Could you give the current version (V4.92) of the J-Link Software a try and check if the update works with this version? Best regards Johannes