Search Results
Search results 1-10 of 10.
This site uses cookies. By continuing to browse this site, you are agreeing to our Cookie Policy.
-
Hi, We are very happy that the JLink V7 support CMSIS-DAP probes. But it is not good the serial number of CMSIS-DAP are converted to short id by JLink. So I cannot get correct SN for specific board when there are multiple CMSIS-DAP devices. Like below picture. So is possible to use origin SN as the USB identification in JLink?
-
jlink-firmware on board version: J-Link LPCXpresso V2. J-Link version: V6.44d arm-none-eabi-gdb.exe version: 7-2018-q2 host os: windows 7 We useJ-Link GDB server and GDB to load applications to LPC54S018, sometimes gdbserver cannot startup due to cannot halt CPU. In this situation, open jlink commander, and it could connect to board successful, but run command "halt" it also failed to halt CPU. We have to replugin usb to fix this problem. Need to note, if we use IAR + J-Link, it works very stabl…
-
This should be a critical issue, also exists on other NXP boards. We will also delivery this issue by my colleagues who are responsible for third-party tools.
-
JLinkGDBServerCL.exe console output Source Code (38 lines)
-
Hello sirs, I use JLinkGDBServerCL.exe and arm-none-eabi-gdb.exe to debugging the my LPC boards, but the gdb cannot connect to the gdbserver due to "Reply contains invalid hex digit 32". The boards both used the JLink CDC firmware. I tried the old versions no such issue. Looks like this is a bug. JLink version: 6.34 OS: windows10 & windows 7 1. Start GDBServer Shell-Script (1 line) 2. Start GDB Source Code (19 lines) Best regards haley
-
Hi sirs, As i know, jlink have supported the lpc54018, but i used the gdb-server and gdb to download program to ram. Is there a way to download to external flash. Best regards
-
JLinkSWOViewer.exe work normal, and everything is perfect. I want to do some automation test, so i used the commad line interface JlinkSWOViewerCL.exe and run with bellow commands: JLinkSWOViewerCL.exe -device LPC54608J512 The output: Brainfuck Source Code (3 lines) No matter how i pass the option "-swofreq", the "Receiving SWO data @ 0 kHz." not changed. I I used jlink 6.30f beta version, and also used the stable version. all not working. Bug? Does anybody know about this??? Thanks