Search Results

Hello Patryk, Thank you for your inquiry. There are currently no news at that front due to low demand, sorry. Best regards, Nino

Hi, Good to hear that you are up and running again. This thread will be closed now. Best regards, Nino

Hello, Thank you for your inquiry. Generic support for A53 and A57 has been added to our latest J-Link probes including the J-Link Edu. However due to lack of hardware and documentation from silicon vendors only the NXP S32V232 has actually been tested: segger.com/downloads/supported-devices.php Others might work but we can't issue a guarantee at this point. In some cases special handlings might be needed for connection or powering up cores etc. However any of these steps would be achievable usi…

Hello, Thank you for your inquiry. Such an issue is not known to us. Regarding BMI we recommend the following Wiki article: wiki.segger.com/XMC1000 Does it provide the information your are looking for? Best regards, Nino

Hello, Thank you for your inquiry. The current SystemViewV2.52f_Src files from our website are faulty in regards to the RTT files. For now we recommend using the RTT files shipped with the latest J-Link software version. The SystemView shipping files are currently under review and should be updated shorty as well. Sorry for any inconvenience caused. Best regards, Nino

Hello Thomas, Thank you for your inquiry. The issue is related to your other thread so this one will be closed: Recording stops with "Invalid packet received" when using assembly version Best regards, Nino

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

Hello Gawie, Yes IAR will utilize the 64 MB on board buffer so depending of the target speed and created trace data this can be enough to reconstruct the last couple of seconds. Best regards, Nino

Hello Dirk, Great to hear that you are up and running again. As the initial inquiry has been solved this thread will be closed now. 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