Search Results
Search results 41-60 of 1,000. There are more results available, please enhance your search parameters.
This site uses cookies. By continuing to browse this site, you are agreeing to our Cookie Policy.
-
Hi, J-Link V8 does not support Cortex-M7. Support for Cortex-M7 was added in 10/2014. Please refer to this article for an overview about the different features of each hardware version. Most new features are not backported to older J-Link Models after they reach end-of-life. J-Link V8 has been superseded by J-Link V9 in 11/2012, followed by J-Link V10 in 10/2015. In case you want to use the features available for current models, we recommend to use our Trade-In Program. Best regards, Niklas
-
Hi, Quote: “when debugging, disconnecting power from target caused the jlink connection to be dropped, as expected. After updating to 6.20d a warning that new firmware is available popped up. After allowing it to update, now when program execution stops, eg power removed from target, the JLink stays happily connectected and I have to manually halt the debugging..” This is not a J-Link feature. The J-Link software does not end the debug session if VCC is lost. It seems like this a Crossworks feat…
-
Hi Ed, Quote: “As long as I selected Target MK02FN128VLF10 and I don't select MK02FN128VLF10( allow security), I believe the bits should stay in the default state, and I will be able to reconnect debugger after erase/program cycle (as long as my program doesn't change them).” Yes and no. It only checks for the Flash Security bits. Since the Mass Erase Enable Bits do not have any effect if the Flash security bits are set to unsecure. Therefore, it should not be possible to enable security when do…
-
Hi, Quote: “Ok, I was taking it as risky in case update goes wrong & fries J-Link box.” Well, that is what the boot loader is therefore. The bootloader is not updated during fw updates and therefore should always be available as a fallback. Best regards, Niklas
-
Hi, Quote: “On Linux:This is second time now I notice that after upgrading J-Link installation and running J-Link, it does not ask like on Windows, but proceeds to update the firmware.” This is the intended behavior. We currently do not ask on Linux / macOS, because we do not support GUI interactions in the command line tools on Linux / macOS. I do not know if there are plans to ask on Linux / macOS, in the future, since updating the firmware when using a new J-Link software, which is manually(!…
-
Hi, VTREF = 0V indicates a wiring issue. The Pinout of J-Link can be found here on the website and in UM08001 VTREF = 0V indicates that Pin 1 and / or none of the GND Pins are connected to the target. Are you using an evaluation board or custom hardware? How do you connect the J-Link to the target? Best regards, Niklas
-
Hi Jimmie, good to hear that you are up and running again. Quote: “I found the following workaround for me:[...]” I am sorry, but there has to be some difference in the setup. e.g. the application reached another state or maybe SWD instead of JTAG was used. If TDO is constant high, no communication will work- neither a connect, nor a halt. If you disagree, could please provide us with a reproduction scenario (binary + instructions)? Best regards, Niklas
-
Hi, Quote: “How do I hold the CPU in reset for the connect? ” by driving nReset low. Some board have a push button for this purpose. You can also give "r0" in J-Link Commander a try. Quote: “ Can I somehow use a custom J-Link script file to reset the CPU (by driving the JTAG Pins manually) and then erase the SPI Flash? ” It is totally possible to drive the JTAG Pins manually using a J-Link script file (override the InitTarget() function in your use case). Best regards, Niklas
-
Hi, sound like the application in the flash is disturbing the debug connection. Does it work when holding the CPU in reset? Does it work when using a low speed (4 - 50 kHz)? Is there maybe a jumper to disconnect the flash or to change to boot memory location? Best regards, Niklas
-
Hi, Quote: “Please explain a bit more here what you mean.” Sorry, I edited this sentence multiple times and in the end I did not check it and it made less sense than intended. Let me rephrase it: This setup works: C Source Code (2 lines) and this as well: C Source Code (2 lines) So you have been able to reproduce a working Remote Server in tunneling mode(!), correct? This does not work for you: C Source Code (2 lines) or did you try it like this? C Source Code (2 lines) Please note that the J-Li…
-
Hi, Quote: “What about the actions by the DLL or the caller of the customized J-Link scripts when return status is error? Will they (or should ..) abort process, or not?” I need to check with engineering on this. Some should definitely fail, like InitTarget(). I am not sure about ResetTarget(), on some target devices, the reset does not work reliably, therefore aborting after one fail would not be good. Needs to be discussed if ResetTarget() aborts after multiple fails or not at all. Quote: “ (w…
-
Hi, Unfortunately, J-Link EDU Mini does not support VCOM: wiki.segger.com/Software_and_H…_Overview#J-Link_EDU_Mini Best regards, Niklas