Search Results
Search results 1-4 of 4.
This site uses cookies. By continuing to browse this site, you are agreeing to our Cookie Policy.
-
Quote from SEGGER - Niklas: “ Could please open and make a screenshot of J-Link Commander (JLinkExe)? ” Please find attached a screenshot of JLinkExe; it seems JLinkExe doesn't detect the Raspberry Pi. I am sure the connection are fine because I am able to connect with OpenOCD using the same hardware setup. Is there anything I can try to make the JLinkExe work with the Pi? Thanks for your support. Alex
-
Quote from SEGGER - Niklas: “ the issue regarding OpenOCD + J-Link models with Full Speed USB (V9 and older) has been fixed with the firmware "J-Link V9 compiled Sep 1 2016 18:29:50" or later, which is included in V6.00i or higher” Guys, thanks a lot! I upgraded the J-Link firmware to the latest version and everything is back to normal with OpenOCD!
-
Hi Niklas, as per your suggestion I launched JLinkExe (V6.00g). As soon I connected the J-Link device it upgraded the J-Link firmware (without no possibility to avoid this) Source Code (7 lines) After the upgrade I wasn't able to get the device working 1) JlinkExe doesn't found any chain (HW setup as before with OpenOCD) Source Code (17 lines) How can I specify the JTAG chain? In openOCD I have a working config if that can be helpful. 2) The J-Link device doesn't work with OpenOCD anymore due to…
-
Hi all, I am trying to connect to the RPi2 JTAG. I have the following setup - Raspberry Pi 2 running Raspbian 8.0 (Jessie) - OpenOCD 0.9.0 with a J-Link EDU connected to a Ubuntu system. I setup the GPIO in order to expose the JTAG interface and the JTAG connection works: I can halt/resume processors. The issues start whenever I tried to access the memory (with the CPU halted). For example Source Code (14 lines) Is there anyone aware of this issue? Is there anything I can do to dig into the prob…