Hello, Thank you for your inquiry. Such an issue is not known to us. Could you provide us with the .svd file for reference? Does this issue happen only if certain peripherals are active or with all of them?` Bestr regards, Nino

Hello, Thank you for your inquiry. The automatic search range for RTT control block for STM32H7 starts at 0x24... as this RAM is always available. If another memory location is used it has to be set manually by the user. Best regards, Nino

Hello, If autodetection does not work you can update manually by going into your Keil install directory to Keil/ARM/Segger and replace the JlinkARM.dll with the new one from the latest installed J-Link software package. Best regards, Nino

Hello, Thank you for your inquiry. For the S3C2 series only CFIc ompliant NOR Flash is supported. segger.com/downloads/supported-devices.php If you use such Flash make sure it is initialized. How to is explained in the J-Link user guide UM08001 in section 7.5 Setup for various debuggers (CFI flash). Best regards, Nino

Hello, When trying to erase with J-Link Commander you should get the message showed in the attached picture. Do you get the same message when typing erase? If yes, could you execute the exec command EnableEraseAllFlashBanks? This should enable you to erase external memory as well. Best regards, Nino

Hello, Thank you for your feedback. To investigate this further we would need a reproduction scenario. Could you provide us with an example project for some Cortex-M eval board? Easiest for us would be for Embedded Studio, but if you use another IDE the output elf file would be sufficient. Best regards, Nino

Hello, Thank you for your inquiry. Such an issue is not known to us. Generally our software stays backwards compatible so if you use the exact same settings in both versions it should keep working. You seem to be working for a silicon vendor, in this case could you open a support ticket through our official support channels? More information can be found in my signature. Best regards, Nino

Hello DG12, Thank you for your feedback. We will discuss internally if this could be implemented in future. However currently we see the issue that it could break backwards compatibility to customers using commands scripts which could result to unexpected behaviour. Should you be looking into writing your own custom version of J-Link Commander we also offer the J-Link SDK which comes with the J-Link Commander source as an example so you can modify it as you see fit. segger.com/products/debug-pro…

Hello, Did you try to open the mentioned web control link in your folder? Quote from Wiki: “A web version is also available via localhost:19080/ on all platforms. ” Which J-Link software version are you using? Could you try the latest one? Best regards, Nino

Hello, Quote from cvicens: “The problem is that I don't have an .elf loader file. Where would I get the appropriate file for my device? ” You need to write your own. How is explained here: wiki.segger.com/Adding_Support…ng_SEGGER_Embedded_Studio There is no precompiled flash loader for this device yet as the target device is unknown to us. Best regards, Nino

Hello, Thank you for your inquiry. The LH75401 is an ARM7 which have some specialties when it comes to connection speeds. Setting it to automatic speed will not work as the automatic speed will most likely be to fast. We recommend using a connections speed of <100 kHz for that target device. Does connection work reliably then? Could you provide a screenshot of an J-Link Commander session with the slowed down speed? wiki.segger.com/J-Link_cannot_…ty_using_J-Link_Commander Best regards, Nino

Hi Russ, Oh OK, I assumed you already gave our sales team the MAC addresses, sorry for the confusion. When choosing the "right" MAC address we recommend choosing a physical one which is build into your PC, like the Ethernet controller or build in Wifi. If you are not sure which to choose simply provide our sales team with all devices available under ES->Tools->License Manager->Diagnose Problems. They will then figure out the right MAC addresses for you. Best regards, Nino

Hello, Thank you for your inquiry. We received your inquiry via e-mail in parallel. For future inquiries please try to use only one contacting channel, otherwise it can happen that information gets lost between channels which can lead to unnecessarily delayed responses. To answer your question in short (for other forum users too). You should also have received an answer vai e-mail. Downloading multiple files in one session: yes Downloading debug information from multiple elf files at once:no, th…

Hello, Thank you for your inquiry. IAR unfortunately does not support any streaming trace features. For the best trace experience we recommend using Ozone the J-Link debugger. It can be used for free with a J-Trace PRO and works with IAR output formats. So you can compile your application with your current IDE and debug it in Ozone with all J-Trace PRO features active. segger.com/products/development-tools/ozone-j-link-debugger/ A List with Tested Devices for tracing can be found here: segger.co…

Hello, Thank you for your inquiry. Native J-Link support in GHS debugger has been removed by Greenhills a while ago. So at this current point in time we can't give any assistance with Greenhills setups as they are no longer supported. For any setup related issues we suggest contacting Greenhills support. Best regards, Nino

Hello, Thank you for your inquiry. Quote from Mron: “I've seen this as an old issue that was fixed about 4 years ago with nRF51 Dongles. Any help is appreciated. ” If that is the case then it should work with nRF52 as all eval boards known to us with nRF and J-Link OB use the exactly same J-link OB. Looking at the referenced dongle it seems like there is not J-link OB at all: nordicsemi.com/Software-and-To…ment-Kits/nRF52840-Dongle Quote from Nordic: “The dongle has been designed to be used as a…

Hello, Thank you for your inquiry. We can't find any information about the ZGM130S037HGN. Could you provide a reference link? What Coretype is it? Currently supported devices can be found here: segger.com/products/debug-prob…pported-cpus-and-devices/ Should your Core type be listed you can also add support yourself: wiki.segger.com/Adding_Support_for_New_Devices Best regards, Nino

Hello, Thank you for your inquiry. This sounds like an incompatibility of the elf file with current standards. Could you provide us with the elf file so we could check if there is a generic issue with Ozone interpreter? Best regards, Nino