Search Results

Hello, .jdebug files are only used when debugging with Ozone. When working with J-Link in general, you need to create a JLinkScriptFile that includes the InitTarget() function. For more information, please refer to: J-Link Script Files This file must then be passed to the JLinkDLL instance, which varies depending on the J-Link tool being used. Using J-Link Script Files Unfortunately, we do not have experience using J-Link with PlatformIO. However, if PlatformIO is using the J-Link GDB Server for…

Hello, The J-Link Commander indeed uses only the JLINKARMDLL for communication with J-Link. To erase a range of addresses using the J-Link DLL, you can use the following approach: C Source Code (4 lines)Best regards, Simon

Hello, The limiting factor here is the speed of the target MCU. Since the target needs to calculate the CRC over the entire 2MB flash, this process naturally takes some time. Best regards, Simon

Hello, The AT45DB321E can be configured with two different page sizes: 512 bytes and 528 bytes. J-Flash SPI only supports page sizes that are powers of 2. It is likely that your flash is configured with a 528-byte page size, which would explain why programming is not working. In J-Flash SPI, you can configure init steps (Project Settings -> Setup -> Init Steps) that are executed when connecting to the flash. I have attached a J-Flash SPI project that uses the init steps to change the page size t…

Hello, You can find an example here: Template Example_ConfigTargetSettings_NXP_S32V234.JLinkScript Best regards, Simon

Hello, Could you please send me a private message with the SN of your Flasher? Best regards, Simon

Hello, I just checked, but I was unable to reproduce the issue. I used the example code specified in the README file of the Pylink project, as well as the DSK example code from our knowledge base: Adding a new device (Knowledge Base) Here is the Python source code I used: Python Source Code (13 lines) When I executed this Python code, the J-Link DLL was able to detect the device and successfully connect to it. Could you please share the Python code you are using? Best regards, Simon

Hello, 1. If your Flash base address differs from the one specified in the J-Link software, you can change it using a command-line parameter. For more information, please refer to: kb.segger.com/J-Link_Multiple_…er#Command_line_parameter For Ozone, you may need to specify the flash loader in your project file. For further details, refer to section 7.9.15.2, Project.SetFlashLoader (page 333): segger.com/downloads/jlink/UM08025_Ozone.pdf 2. It is possible that a device-specific reset is executed w…

Hello, Could you please provide a J-link Log file for both cases? How to enable: wiki.segger.com/J-Link_DLL#Enable_J-Link_Log_File Did you make sure that the same programming procedure was used in both cases? Best regards, Simon

Hello, As you have also opened an official support ticket for this issue, we will investigate the matter through the support ticket system. Once a solution is available, we will update this forum thread accordingly. Best regards, Simon

Hello, 1. The J-Link currently does not support debugging or programming the Parade Tech TT21100. You may consider adding support yourself using the J-Link Device Support Kit (DSK) or contact SEGGER to implement the support for you. 2. The STM32F2 series from ST is supported by J-Link, but I could not find any documentation on the STM32F28033. Could you provide a link to such documentation? This would allow me to verify if the STM32F28033 belongs to the STM32F2 series from ST and if it is suppor…

Hello, The JLinkGUIServer is generally responsible for hosting GUI pop-ups to interact with the J-Link, such as warnings, errors, or dialogs for inputting authentication when the target is protected. We are aware of the issue you reported and have already implemented a fix. The fix will be included in the next version, scheduled for release in the middle of next week. Best regards, Simon

Hello, Your assumption that the RTT issue is related to the size of the RTT buffer appears to be correct. I was able to reproduce the issue where J-Scope draws unexpected lines after a short period of time when the RTT buffer size is approximately 30 kB. We will investigate this further and get back to you with updates. Regarding the HSS issue, I was unable to reproduce the behavior using the HSS sample project with a sample rate greater than 100 Hz. Could you please provide the following for fu…

Hello, Switching the interface to JTAG in dormant mode is already supported however the corresponding command was previously undocumented. I have added the documentation for this command to our knowledge base. For more information, please refer to: kb.segger.com/J-Link_Command_Strings#SetDormantModeHandling Best regards, Simon

Hello, To use RTT on external memory with Cortex-R devices, please refer to the following resources: 1. Information on RTT with RZ/T2L: kb.segger.com/index.php?title=Renesas_RZ/T2L#RTT 2. Cortex-R specific RTT details: kb.segger.com/RTT#Cortex-R_specifics 3. CPU caching and RTT: kb.segger.com/RTT#Cortex-M_specifics Quote: “If the curve is a little bit more complex and the time axis sacle is a little bit more large，the j-scope gui will freeze. ” We will investigate this issue and get back to you …

Hello, J-Scope is actively maintained and updated, so please feel free to request any features you find missing in J-Scope. Currently, the only solution to work with the data stream in J-Scope is to record the variables and then export the data either as a CSV file or as a RAW data stream. Other applications that support the CSV format can then be used to analyze the data. For more information on exporting sampled data, please refer to: kb.segger.com/UM08028_J-Scope#Exporting_Sampled_Data Best r…

Hello, Flash Lite only erases sectors that are included in the data file being programmed. If you have enabled config flash but it is not included in your .hex file, Flash Lite will not erase or program this flash when you press the Programming button. However, if you click "Erase Chip," the config flash will be completely erased regardless of whether it is included in your .hex file. >> would J-Flash Lite have erased this area and left it at all-1s, or would it have written all-0s? I ask When t…

Hello, Thank you for your inquiry. 1 / 2 We are not aware of these issues. Is the issue also reproducible with the example code in the J-Scope documentation? kb.segger.com/UM08028_J-Scope#Example_code Would you be able to provide the ELF file and J-Scope project for further investigation? 3 We are aware of this issue, and a fix will be available in the next version. Best regards, Simon

Hello, You can configure the J-Link DLL to avoid reading specific areas from the cache using the ExcludeFlashCacheRange exec command. For more information, please refer to: kb.segger.com/J-Link_Command_Strings#ExcludeFlashCacheRange EDIT: Additional options that helped in fjouen's case was setting SetEnableMemCache=0 and SetAllowFlashCache=0. Best regards, Simon

Hello Benedict, It depends on the device you want to program. You can find a list of all supported devices here: segger.com/supported-devices/jlink/ Best regards, Simon