SEGGER - Fabian Administrator

Hi Peter, We are not aware of any such issue. I just gave it a quick try and it works without issues on my side, using an STM32F407VE: Source Code (2 lines)Resulted in the lines: Some 123 Test 456. Some 456 Test 123. Could you please provide a working…

Hi Torsten, this depends on how you reset the device and what exactly happens when you do so. From the description I would guess that the debug interface is reset, so a reconnect is required to establish it again. As an active debug interface is a…

Hi Kaushalya, It sounds like you are using Nordic Tools for handling RTT on PC side, correct? If so, please understand that we cannot provide help for applications which are not supported by SEGGER. If not: Which application are you using? Could you…

Hi, We added option byte programming via .hex-file to our feature request list. We will try to squeeze this in within the next couple of weeks. Stay up-to-date regarding J-Link: segger.com/notification/subscribe.php?prodid=7,94 BR Fabian

Hi, Both at once: Executed via cross trigger. Not supported yet. It's on our list but without a fixed schedule at the moment. M7 only: You should be able to halt the M7 in the M7 debug session. If this does not work, could you please share a J-Link…

Hi, You can look them up in the release notes. You can search for the term: "RISC-V: Firmware module version" for differences and compare them. segger.com/downloads/jlink/ReleaseNotes_JLink.html Please note that the list will grow further with time, as…

Hi, Currently, option byte programming via .hex file is not supported for the STM32C0 device with J-Link. I will check internally if there are any plans regarding this. Best regards, Fabian

Hi, Sorry for the delay in response. We are not aware of any such issue. Are you using the latest version of the software? segger.com/downloads/jlink#J-L…twareAndDocumentationPack If so: Could you please provide a sample data file (e.g. .hex) this issue…

Hi, sorry for the delay in response. 0x0800_0000 and 0x0C00_0000 describe the same physical flash area. The first is cached the latter is uncached. When programming data to 0x0800_0000, it is remapped internally to 0x0C00_0000 by J-Link, which was…

Hi, sorry for the delay in response. Even though it is probably not required anymore, please find the answer below: In general we recommend to make use of our trade-in program in such a case: segger.com/purchase/trade-in-program/ The damaged part is an…

Hi, Even though the thread is quite old, an answer to the question can be found here: wiki.segger.com/S32Kxxx#Readout_protection_of_internal_flash BR Fabian

Hi, We updated the wiki-page. The "Force go on connect" option is now explained: wiki.segger.com/J-Link_RTT_Viewer#Force_Go_on_Connect Does this answer your question? BR Fabian

Hi tsche, Unfortunately, we had to postpone the implementation of PIC32MK support.It is still on our list of feature requests, but without definitive timeline. MIPS is not our core business, so we cannot prioritize this, unfortunately. Best…

Hi Peter, No worries! Best regards Fabian

Hi Peter, Quote from hotbrix: “As far I understand you, there is no way around this. I need the perma connection to stay open in order to be able to connect to the server. ” This is correct. As long as you want to use RTT, you will have to have an…