
SEGGER - Simon SuperModerator
- Member since Mar 20th 2024
This site uses cookies. By continuing to browse this site, you are agreeing to our Cookie Policy.
-
SEGGER - Simon -
Replied to the thread Is there any plan for supporting wch CH32V risk V parts?.
PostHello, There are currently no plans to support the WCH CH32V devices. Best regards, Simon -
SEGGER - Simon -
Replied to the thread J-Link flash support for ESP32.
PostHello, 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… -
SEGGER - Simon -
Replied to the thread Problems programming the RSL10.
PostHello, 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… -
SEGGER - Simon -
Replied to the thread J-Link Semihosting: Is There a Limit on Directory Depth for File Open?.
PostHello, 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… -
SEGGER - Simon -
Replied to the thread [SOLVED] How to configure PlatformIO with JLink to execute the initialization script before communicating with target.
PostHello, .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… -
SEGGER - Simon -
Replied to the thread [SOLVED] Trying to understand difference between Jlink Commander and JLINK DLL.
PostHello, 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 -
SEGGER - Simon -
Replied to the thread J-Link Pro Flash Download: Compare very slow.
PostHello, 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 -
SEGGER - Simon -
Replied to the thread JFlashSPI not able to program a SPI-Flash.
PostHello, 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… -
SEGGER - Simon -
Replied to the thread Use JLink Commander to debug Cortex-A35.
PostHello, You can find an example here: Template Example_ConfigTargetSettings_NXP_S32V234.JLinkScript Best regards, Simon