Search Results

Hi Brandon, This is not forgotten. We are planning to do this at some point in the future. Please understand that the Micro:bit ports are pure charity projects and thus mean zero business for SEGGER. Therefore we have to prioritize paid projects, which we are currently fully booked with. These ports are a considerable amount of work we do not have the resources for right now, as the current project/order situation simply does not allow it. Unfortunately, this also means that we can not provide a…

Hi, We are still not able to reproduce this issue. Could you please provide step-by-step instructions of what you do to produce this issue? Could you please also also send us a J-Link log file? How to enable: wiki.segger.com/J-Link_DLL#Enable_J-Link_Log_File BR Fabian

Hi Grant, Could you please answer the following questions, so we can have a quick look? How exactly are you calling the J-Link commander? What commands are you executing and how do you execute them exactly? Could you please provide 1) a J-Link Log file? How to enable: wiki.segger.com/J-Link_DLL#Enable_J-Link_Log_File 2) the full output of the commander session? BR Fabian

Hi toba, Update: We will add background mode compatibility to the J-Link RTT Logger short term (within the next couple of weeks). Stay up-to-date regarding J-Link: segger.com/notification/subscribe.php?prodid=7,94 BR Fabian

Hi toba, Quote from toba: “How can I use the J-Link RTT Logger in background mode? ” The J-Link RTT Logger is not designed to be used in background mode. As far as I know, there is no way to make it work in background mode. BR Fabian

Hi, sorry for the delay in response. For feature requests of this kind, please open a ticket in our support ticket system (link in my signature, below this post). BR Fabian

Hi, The documentation of InitEmu explicitly says that the only allowed command string is "SetHostIf": wiki.segger.com/J-Link_script_files#InitEMU.28.29 ConfigTargetSettings() or SetupTarget() would be the correct functions to pass "EnableLowPowerHandlingMode" to the DLL. BR Fabian

Hi, Thank you for your inquiry. Did you implement the read function in your flashloader? wiki.segger.com/SEGGER_Flash_Loader#SEGGER_FL_Read BR Fabian

Hi gaston, Quote from gschelotto: “How can I complete uninstall of jlink in a Linux (deb) machine? ” The same way any deb package is uninstalled. This article might help you out: askubuntu.com/questions/22200/how-to-uninstall-a-deb-package Quote from gschelotto: “Can live together 2 jlink versions in opt/SEGGER/ directory? i.e. v6.40 and v7.80 If so, how can I install the v6.40 without downgrading and loosing the v7.80? ” It is not possible in general to have multiple versions of the same applic…

Hi, This should help you out: wiki.segger.com/Read-Modify-Write_Flash BR Fabian

Hi, As mentioned in the support request you opened in our support ticket system: The interface of J-Link and the 6-Pin needle adapter specifies pad no 3 as nRESET, so the J-Link is behaving correctly: segger.com/products/debug-prob…eedle-adapter/#schematics It expects an active low nRESET (#RESET / not RESET), which is in accordance with the specification. Thus, as the DA14531 has a RESET pin instead of nRESET pin, the board design would have to make sure that the signal is negated to apply to d…

Hi, Yes there is: wiki.segger.com/J-Link_script_files Best regards, Fabian

Update: The RTT TELNET port was indeed only available for localhost, even when Localhost only was not selected. This will be fixed with the next J-Link version (V7.80c) planned for the 27th of September. BR Fabian

Hi, The RTT tab in the J-Link web control panel did not replace the RTT Viewer. It is just some additional feature for the web control panel and in no means designed to come close to the J-Link RTT Viewer. The J-Link RTT Viewer is still available as application for Windows, Linux and MacOS: wiki.segger.com/J-Link_RTT_Viewer It is part of the J-Link Software Pack (JLinkRTTViewer.exe / JLinkRTTViewerExe): segger.com/downloads/jlink#J-L…twareAndDocumentationPack Could you please check? Best regards…

Hi, Did you add the required rules file to allow J-Links to be discovered via USB? If you have not added the 99-jlink.rules file (part of the J-Link Software Pack) to your linux system, you would have to call any application using the J-Link DLL (e.g. nrfjprog) as with sudo (as super user). J-Link Software Pack: segger.com/downloads/jlink#J-L…twareAndDocumentationPack Could you please check this? On a side note: nrfjprog is not a SEGGER application but developed and maintained by Nordic Semicond…

Hi, Thank you for your inquiry. Hardware breakpoints (HW BP) on embedded devices are very limited. Thus, by default, the flash breakpoint (Flash BP) feature is enabled. From your description I would assume that you have set more BPs than HW BPs are available, so a Flash BP is set. When setting a Flash BP, a flash download has to be executed and for this the target is halted. To disable Flash BPs, please refer to: - wiki.segger.com/J-Link_Command_Strings#DisableFlashBPs - wiki.segger.com/J-Link_-…

Hi, Good to hear that you are up and running again. BR Fabian

Hi, There are two issues with the code you linked, one which is causing the crash and the other, will result in behavior that you might not intent. 1) Reason for the crash: The language of the J-Link Script files is not 100% compatible to C, but only "C like". Passing pointers of an array to a function does not work the way you do it. Pointers of arrays have to be passed as follows: C Source Code (1 line) Could you please check if this works in your case? We will adjust the documentation so that…

Hi, There are no issues known to us regarding nRF52832 and J-Link. 1) Could you please follow the troubleshooting article on the page linked below and send us a screenshot of the entire J-Link Commander output? wiki.segger.com/J-Link_cannot_…the_CPU#Target_connection 2) Could you please send us a J-Link log file? How to enable: wiki.segger.com/J-Link_DLL#Enable_J-Link_Log_File BR Fabian

Hi, We have not yet heard of such an issue yet. It is good to hear that you were able to resolve it. As it was resolved by resetting the PC, I assume that the PC was in some weird state that caused the issue. Should this issue reappear, we would be very interested in a way to reliably reproduce this, so we can look into it. BR Fabian