Search Results

Hello, There are currently no plans to extend support for NXP's i.MX91. However, you can add functionality for core initialization and reset yourself using a J-Link script file. More information can be found here: J-Link Script Files Knowledge Base If you require a custom flashloader, you will need the J-Link Device Support Kit (DSK): J-Link DSK Product Page Best regards, Simon

Hello, The latest version of ARM Development Studio does not include native J-Link support. However, if ARM Development Studio supports using GDB, you can use the J-Link GDB Server to enable debugging with J-Link. Best regards, Simon

Hello, I just tried to reproduce the issue, but erasing and flashing the R7FA2A2AD using the J-Link OB worked without any problems on my side. While reviewing the user manual for the evaluation board, I noticed that jumper J9 needs to be open when using the J-Link OB. Reference: Users Manual - Evaluation Kit for RA2A2 MCU Group, Section 5.2, Table 4: Jumper Connection Summary for Different Debug Modes Could you please try flashing the device with J9 open and let me know if the issue persists? Be…

Hello, You will likely need to implement the SetupTarget() function in a J-Link script file and manually specify the CTICoreBaseAddr. As a reference, you can use the following example script: Template Example_ConfigTargetSettings_NXP_S32V234.JLinkScript Best regards, Simon

Hello, The reason ForceAttachTarget is not working is because the exec command is being called before the J-Link DLL session has started. To set global DLL variables like ForceAttachTarget, you can add a J-Link script file to your project that includes the ConfigTargetSettings() function. This function is called after the J-Link DLL session starts, but before the target is connected. C Source Code (4 lines)You can find more information on J-Link script files here: kb.segger.com/J-Link_script_fil…

Hello, It looks like the website is outdated. Since J-Link LITE V9, debugging Cortex-M33 targets is supported. For a complete overview of all J-Link models, their features, and supported cores, please refer to the following link: kb.segger.com/J-Link_Model_Overview Best regards, Simon

Hello, There are currently no plans to support the WCH CH32V devices. Best regards, Simon

Hello, The statement that J-Link supports both "debugging and programming" for the ESP32 is incorrect—this was likely a misunderstanding. J-Link support for the ESP32 is limited to debugging only and does not include flash programming. Currently, there are no plans to add flash programming support. Could you provide a link to the announcement mentioning ESP32 support? We would like to review and correct any misleading statements. However, if you need to program the ESP32, this can be done using …

Hello, 1. I just tested our hardware (RSL10 SIP EVB V1.2) and did not encounter this issue. Could you please provide a generic J-Link log file of the failing scenario? How to enable: wiki.segger.com/J-Link_DLL#Enable_J-Link_Log_File 2. The flashloader for the RSL10’s NVR Flash is unique because sector erasure occurs within the program function. When programming the target with two separate files, J-Flash executes multiple program calls, causing the entire sector to be erased each time. This is n…

Hello, Semihosting itself is not limited in path length. However, depending on the tool you are using on the PC side, the path length could be limited to 256 characters (the maximum path length in Windows). May I ask which tool you are using for semihosting? So i can check if there is a limitation in that specific tool. Best regards, Simon

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