Search Results
Search results 1-7 of 7.
This site uses cookies. By continuing to browse this site, you are agreeing to our Cookie Policy.
-
No more questions, thanks.
-
My experience is Segger points to Renesas and Renesas points to Segger. The JLink does work fine with arm based renesas cpus. The E1 debugger works without any issues out of the box with e2 studio and HEW.
-
I seem to recall similar experiences when attempting to use a JLink with a non-arm Renesas CPU. I tried for awhile to use a Jlink pro with a RX62N on e2 studio (version 7.0 I think -- maybe 6.2) and gave up and just went back to the Renesas E1. Debugging worked great at first (maybe a few days) and slowly progressed into not working at all. I actually warranty exchanged a JLink pro thinking it was faulty due to the issues I was having debugging the RX62n. The new JLink pro had the same the probl…
-
Quote from SEGGER - Fabian: “Hi, Thank you for your Inquiry. Unfortunately, there is currently no such command-line option. We will put it on our requested features list, but cannot say when it will be implemented. If you require this feature short term, you can also buy and use our J-Link SDK. A part of the SDK is the source code for the J-Link Commander (jlink.exe). It can be modified with an API function to always select a certain ID Code, when the verification window would be called by our D…
-
bash script I used awhile ago to automate flashing an RZT1 device. This requires creating a project in J-Flash.Shell-Script (9 lines)
-
The image below is the pop-up that appears when I launch jlink.exe -- I must enter the ID Code manually.
-
I want to be able to launch jlink.exe with all target settings from the command line. I am able to provide the device, interface, speed, etc without issue. My problem is I do not know how to pass the "ID Code verification" to the jlink.exe. Does anyone know how to pass the ID Code to the jlink.exe via the command line?