Search Results

Hi Michael, Hi David, Thank you for your inquiry. Could you please provide us with a sample project (including .elf-file) this issue is reproducible with? Ideally via our Support Ticket System (link below this post, in my signature). Please do also refer to this forum post in it (link). Best regards, Fabian

Hi, Thank you for your inquiry. Yes, this post is visible. The command line only provides a limited (usually sufficient) setup of the project. All other settings have to be selected manually, from within the project itself. Best regards, Fabian

Hi, Thank you for your inquiry. This issue was already addressed and fixed internally. The fix will be part of V3.22f (next upcoming version). It will be available for download here: segger.com/downloads/jlink#Ozone Best regards, Fabian

Hi, Thank you for your inquiry. Also, thank you for your feedback and the detailed report. This is very valuable for us. I forwarded this as a bug report to the Ozone department. We will resolve this as soon as possible. Best regards, Fabian

Hi, Thank you for your inquiry. There were a couple of these issues fixed in the last version. Could you please check if the issue persists in the latest version? You can download it here: segger.com/downloads/jlink#SystemView Best regards, Fabian

Hi, Thank you for your inquiry. Could you please try to install the latest version of SystemView? The required libs should be part of the package since V3.12. You can find the latest version here: segger.com/downloads/jlink#SystemView Best regards, Fabian

Hi Remco, Thank you for your inquiry. I forwarded this matter to the related department. We will come back to you as soon as possible. Best regards, Fabian

Hi, Thank you for your inquiry. It seems like something went wrong with the image upload. Could you please re-upload the image? Best regards, Fabian

Hi, Thank you for your inquiry. Your question is answered in the SystemView User Manual (UM08027): segger.com/downloads/jlink/UM08027 Chapter 3.12.5 Export recordings: forum.segger.com/index.php/Att…7bdd3c5e5994fc2f40b8afd7d Best regards, Fabian

Hi Christian, Regarding the 3rd party idea: Alternatively you could buy the J-Link SDK. It also comes with the samples and the source code of the J-Link Commander. The SDK comes with a function to check the available licenses of a probe. Regarding J-Flash in batch processing: The following article should answer your question. wiki.segger.com/UM08003_JFlash#Batch_processing Just so I understand your setup correctly: You use the J-Link OBs on the nrf52840 evaluation boards to develop your code and…

Hi Christian, Thank you for your inquiry. You can pass a command script to the J-Link Commander: wiki.segger.com/J-Link_Commander#-CommandFile The command script could look like this: Source Code (2 lines)Does this work for you? Best regards, Fabian

Hi, Thank you for your inquiry. Currently, this is not possible. In general, text files and similar do not come with text color information. Probably the easiest way would be for you to work with identifiers and indentation to make the calls more visible. Example: Source Code (7 lines)I will check if we can somehow improve our handling for colored texts. Keep you posted. Best regards, Fabian

Hi, Thank you for your inquiry. Usually, failed firmware updates do not brick a J-Link. It should still be recoverable in nearly all cases. In general: When using the J-Link it is important to have a stable USB connection. Please make sure, that the J-Link is directly connected to your PC via a solid USB cable. If you must use a USB-Hub, please make sure that it is externally powered. If this does not help: Could you please follow the troubleshooting article on the page linked below and send us …

Hi, Sorry for the delay. We added the following features to our ToDo list: 1) When opening the J-Link RTT Viewer, the last used Terminal will be opened by default. 2) A command line option to select a specific terminal on startup. Unfortunately, we cannot give a specific timeline for this yet, as we are currently very busy with multiple projects. Stay up-to-date regarding J-Link: segger.com/notification/subscribe.php?prodid=7,94 Best regards, Fabian

Hi, Thank you for your inquiry. SPC560B64 is supported by Flasher only. List of supported devices J-Link: segger.com/downloads/supported-devices.php List of supported devices Flasher: segger.com/downloads/supported-devices.php?model=flasher Best regards, Fabian

Hi, Sorry for the delay in response. This is odd. Could you please provide us with a sample .hex file and a J-Flash project for reproduction purposes? Best regards, Fabian

Hi, As you also contacted us via the Support System, we will close this thread here. Best regards, Fabian

Hi, Unfortunately, we had to delay this. We are planning to add this within the next two weeks for both: - STM32H72xx_73xx - STM32H75xx I will keep you posted. Best regards, Fabian

Hi, Good to hear that you found the source of the issue. I will check internally what could have cause the described damage. Best regards, Fabian

Hi Christian, Thank you for pointing this out to us. As soon as this feature is available we will mention it in our release notes. Stay up-to-date regarding J-Link: segger.com/notification/subscribe.php?prodid=7,94 As the inquiry was answered, we will close this thread now. Best regards, Fabian