Search Results

Hi, The action "Reset" implicitly does a halt. This is the only way to make sure that the device is in a defined state when programming the flash. The "Reset" action is by default selected in the Init steps on project creation, and can be removed by the user if required. If you set RDP level 1 in the exit steps, I do not think you actually need to issue a go, as OBL_LAUNCH will trigger a system reset anyway, so the device should be running afterwards. BR Fabian

Hi Swamirajan, Thank you for your inquiry. This seems to be an SPI NOR flash, correct? In this case, the flash can be simply added by the user themselves: wiki.segger.com/CFI_Flash BR Fabian

Hi Alex, I assume you are using J-Flash for programming? In this case, you can use the Exit steps in the J-Flash project options. The GD32F1 devices have mostly the same option byte programming procedure as the STM32F1 do. There is a J-Flash project in the SEGGER wiki that sets RDP for the STM32F1 via the exit steps. After some small adjustments, it should also work for the GD32F1 devices. Does this answer your question? BR Fabian

Hi, I can confirm that this is a bug in our software. A fix will be part of the patched release, planned for later today. BR Fabian

Hi, The only thing required for Ozone is to update the J-Link DLL in it. If you are on Windows, you can use the J-Link DLL Updater for this purpose. It is part of the J-Link Software Pack: segger.com/downloads/jlink#J-L…twareAndDocumentationPack If you are on Linux/Mac, you can either update the J-Link DLL manually, or wait for the next Ozone update, which will be shipped with the latest version of it. BR Fabian

Hi, Thank you for your inqiury. Quote from fraengers: “It happens very often, that I disconnect the power of my microcontroller board while a debug session is still running. ” It is not recommended to cut the debug connection behind the back of a debug probe, while the debug session is running. It usually does not hurt, but it is like killing a part of the debug process. The recommended way would be to stop the debug session first and then to cut the power afterwards. Quote from fraengers: “Is t…

Hi, Thank you for your inquiry. J-Flash executes a reset & halt after reset by default as first step of the production programming action (-auto/"F7"). You should be fine flashing the usual way, as the core is not started before programming is finished. Did you experience any issues so far? BR Fabian

Hi, I am sorry if my words are raising a condescending impression. It was not meant that way and I will try to prevent this from happening in my future messages. BR Fabian

Hi, Do not worry, you did not abuse anything or break the rules. You are welcome to ask questions here. BR Fabian

Hi, That is exactly what I already did. The last link is the link to the SEGGER shop with the license you want to acquire: forum.segger.com/index.php/Att…e10c3c884bcdbfa39277cd50e BR Fabian

Hi, Thank you for your inquiry. Quote from Eqqman: “as an aside, I don't understand why Segger's own tool won't use their own ELF format ” I do not understand what you mean with "own ELF format". The Executable and Linkable Format (ELF) is a standardized format for executable files. en.wikipedia.org/wiki/Executable_and_Linkable_Format ELF There are many IDEs/Toolchains that use this format as it provides a good way to integrate debug information via the DWARF standard. Why reinvent the wheel whe…

Hi, Good to hear that the problem could be resolved. We will close this thread now. BR Fabian

Hi, Thank you for your inquiry. - Information about SystemView licensing - Information about J-Link locked licenses - SystemView SEGGER shop page After purchase, you will receive the license and information about how to add the license to the J-Link. Does this answer your question? BR Fabian

Hi, For debug support requests, please use our support ticket system (link in my signature, below this message). BR Fabian

Hi Denis, this is a bug that was already fixed internally. The fix will be part of the next patched release, planned for later today (V7.68b). segger.com/downloads/jlink#J-L…twareAndDocumentationPack If you want to be notified when the patched version goes live, you can subscribe to our release newsletter: segger.com/notification/subscribe.php?prodid=7,94 We are sorry for any inconvenience caused. BR Fabian

Hi, The J-Link does not try to understand the J-Link chain. As you can see in the log you posted yourself, the device (name) you are trying to select is not supported by J-Link: Quote from emrainey: “No valid device has been selected. ” Usually, the device selection dialog would open to let you choose the correct device from a list of device, but your linux does not have all required libs installed: Quote from emrainey: “/opt/SEGGER/JLink_V766g/JLinkGUIServerExe: error while loading shared libra…

Hi, Thank you for your inquiry. There are multiple ways to do this, but the simplest would probably to use the J-Link Commander: wiki.segger.com/J-Link_Commander#Mem32 BR Fabian

Hi, the J-Link you are using is a clone and not a genuine J-Link. Please note that it is illegal to use our tools in combination with a clone. I assume that you were not aware of this. As you are a student and are planning to use the J-Link in a non-commercial context, I would suggest to acquire one of our J-Link EDU models: - J-Link EDU - J-Link EDU mini And install the latest J-Link Software version: segger.com/downloads/jlink#J-L…twareAndDocumentationPack We will close this thread now. BR Fab…

Hi, Good to hear that the latest version resolved the issue. We will close this thread now. BR Fabian

Hi Josu, Good to hear that you were able to solve this problem. Thank you for sharing your solution. BR Fabian