Search Results

Search results 1-20 of 653.

This site uses cookies. By continuing to browse this site, you are agreeing to our Cookie Policy.

  • Hi Guillaume, Could you please provide us with a reproducer for this? Best regards, Fabian

  • Hi, Thank you for your inquiry. There is no such issue known to us. At first glance, this does not necessarily look like a J-Link related issue. What Device are you trying to debug exactly? Could you please send us a J-Link log file? How to enable: wiki.segger.com/J-Link_DLL#Enable_J-Link_Log_File Could you please provide us with step-by-step instructions on how to reproduce this issue? Best regards, Fabian

  • Hi, Thank you for your inquiry. We are not aware of any issues related to the STM32F1 series and JTAG. I just gave this a quick try and it seems to be working without any issues on an STM32F10X-128K-EVAL board (STM32F103V8): forum.segger.com/index.php/Att…3e68ca57f5494458a3b973a7c Do you experience the same issue on an evaluation board? Could you please send us a J-Link log file? How to enable: wiki.segger.com/J-Link_DLL#Enable_J-Link_Log_File Best regards, Fabian

  • Hi Priya, Thank you for your inquiry. I am sorry, but I do not quite understand what you are trying to achieve. Could you please explain in more detail? In general: 1) .bin files do not contain any address information, so when opening them in J-Flash you have to provide a start address. Otherwise, J-Flash cannot know where it is supposed to download the data to. 2) The screenshot you provided shows that your project currently only allows to flash data to 0x0-0x3FFF. To flash data to 0x4000 - ...…

  • Hi, Good to hear that you were able to resolve the issue. We will close this thread now. Best regards, Fabian

  • Hi, We are not aware of such an issue. You can find an example blinky project for the RP2040 here: wiki.segger.com/Raspberry_Pi_Pico#Example_Projects It should be working out of the box for Ozone / Embedded Studio. Could you please give that one a try? Best regards, Fabian

  • Hi, As this inquiry is resolved, we will close this thread now. Best regards, Fabian

  • Hi, Thank you for your inquiry. Yes this is possible by using a J-Link Command string: wiki.segger.com/J-Link_Command_Strings#SetCompareMode How you can use them is also explained in the same article: wiki.segger.com/J-Link_Command…ng_J-Link_Command_Strings I will also mention this in our next internal meeting. Maybe we can add an option to enable that some settings are remembered when changed in the control panel. Best regards, Fabian

  • Hi, Sorry for the delay in response. If everything is working correctly, flash can be written with the w* commands. As Alex already said however, this might not be the case for your device, as it is not officially supported and might be different regarding flash programming. Best regards, Fabian

  • Hi, Sorry for the delay in response. We are able to reproduce this behavior. We will look into this as soon as possible. Unfortunately, we are currently very busy with multiple pressing projects, so it might take a while until we are able to resolve this. Best regards, Fabian

  • Hi, Sorry for the delay in response. Somehow this slipped under the table. If we understand you correctly the SWDIO GPIO lane was damaged/destroyed. This should not be possible by simply connecting it to ground. Possible causes could be: - 5V+ current connected to the pin - negative current connected to the pin - ESD Best regards, Fabian

  • Hi, Sorry for the delay in response. We have not forgotten about this. Unfortunately, we do not have any resources available to look into this, but we will do so as soon as possible. We have some high priority projects with upcoming deadlines we have to get out of the way first. We are sorry for any inconvenience caused. Best regards Fabian

  • Hi, Unfortunately, not. The J-Trace would be listed otherwise. As this inquiry is solved now, I will close this thread. Best regards, Fabian

  • Hi everyone, You would need a J-Link of the latest generation to make use of this feature. I forwarded this to our web team so they add this information to the website. The models with CMSIS support are: - J-Link EDU/BASE/PLUS V11 - J-Link ULTRA+ V5 - J-Link PRO V5 - J-Link WiFi V1 If you require this feature you could make use of our Trade in program: segger.com/purchase/trade-in-program/ The trade in also comes with 1 year of support. Best regards, Fabian

  • Hi Lubomir, Thank you for your inquiry. With the latest version of the Software and Documentation pack, you can find the option here: Right-click the J-Link > Select "Configure" > Select "CMSIS-DAP" as boot mode. forum.segger.com/index.php/Att…3e68ca57f5494458a3b973a7c Best regards, Fabian

  • Hi, Update: We implemented the aforementioned features in the latest beta-release V7.11a (segger.com/downloads/jlink#J-L…ndDocumentationPackBeta): 1) The currently opened terminal tab is now remembered after closing the application and will be opened automatically on the next application start. 2) Added command line option "-ti" / "--terminalindex" (see: wiki.segger.com/J-Link_RTT_Viewer#--terminalindex ). Could you please give this version a try and come back to us if it works as expected? Best…

  • Hi, Thank you for your inquiry. We are not aware of any issue with the STM32G0 devices. According to the information of the log file, the J-Link is not able to connect to the device. Did you make sure that the reset pin is connected on your hardware?Did this work on the same hardware before? Does this issue also appear when connecting to the device via J-Link Commander (JLink.exe)? Do you use custom hardware or an evaluation board? In the latter case which one? If custom hardware, do you experie…

  • Hi, Good to hear that it now works as expected. We will close this thread now. We are sorry for any inconvenience caused. Best regards, Fabian

  • Hi, Thank you for your inquiry. Quote from dsc: “Is that how it's intended to work? ” Yes and no. The J-Link RTT Client requires an active J-Link debug connection, e.g. via an IDE, J-Link Commander, ... In your case, the J-Link RTT Viewer opens a debug connection to the device, which the RTT Client then hooks up to. As RTT Viewer and RTT Client are not supposed to be used at the same time, this choice is not optimal though. The simplest option here would be to connect to the device via the J-Lin…

  • Hi, Good to hear that you are up and running again. As the issue was resolved, we will close this thread now. Best regards, Fabian