Search Results

Hello, We are aware of this issue and are actively working on a fix. Since it impacts the core handling of symbols, the resolution is more complex and may take some time. However, we are aiming to have the fix ready within the next few weeks. Best regards, Simon

Hello, The following links might be helpful: forum.segger.com/index.php/Thr…-SOLVED-RTT-and-FreeRTOS/ wiki.segger.com/RTT#Troubleshooting Best regards, Simon

Hello, You can disable the automatic firmware updates with the DisableAutoUpdateFW command string. wiki.segger.com/J-Link_Command_Strings#DisableAutoUpdateFW Best regards, Simon

Hello, Yes, we plan to support this chip and are looking to implement it in the next few weeks. Stay up-to-date regarding J-Link: segger.com/notification/subscribe.php?prodid=7,94 Best regards, Simon

Hello, The ShowHWStatus command displays the current state of the pins, indicating whether they are high (1) or low (0). For SWD, the following pins are used: - TDI = SWDIO - TCK = SWCLK - TDO = SWO Best regards, Simon

Hello, The fix for this issue will be included in the next version, scheduled for later today. Stay up-to-date regarding J-Link: segger.com/notification/subscribe.php?prodid=7,94 Best regards, Simon

Hello, Currently, there is no option to change the RTT channel in the RTT Client, as it is hardcoded to channel 0. Best regards, Simon

Hello, We have expanded our J-Scope documentation with an example on how to use J-Scope with RTT and timestamps: Example Project Best regards, Simon

Hello, The logs appear to be fine. It's possible that the port (19021) is being blocked by your firewall, or that the RemoteServerCL application does not have the necessary permissions to access your local network. Best regards, Simon

Hello, Supported operating systems for J-Link are: - Microsoft Windows 10 - Microsoft Windows 11 - Linux (Tested distributions) - macOS 10.5 and higher While I'm quite confident that it will run on Windows 7, please note that it is not officially tested or supported, so we cannot guarantee its functionality on that platform. Best regards, Simon

Hello, Thank you for reaching out. The timestamp value in J-Scope is interpreted in microseconds (µs). To display the correct timestamps with J-Scope, you should start with a timestamp of 0 and increase it by 2000 (2ms) each time you send data. Best regards, Simon

Hello, For the Traveo 2 family, we do not support Dual Bank mode. You could write your own Flash Loader if needed using the J-Link DSK. For more information, refer to: wiki.segger.com/J-Link_Device_Support_Kit segger.com/products/debug-probes/j-link/tools/j-link-dsk/ Best regards, Simon

Hello, You could try to read the registers one by one using the "reg" command: wiki.segger.com/J-Link_GDB_Server#reg Best regards, Simon

Hello, You can only choose out of the available pin configurations that are available the MCU and cant adjust it yourself. You can find the available pin configurations for the STM32U599 here: wiki.segger.com/ST_STM32U5#QSPI_Flash If your Pin configuration differs from the ones available, please get in touch with us directly via our support system: segger.com/ticket/ Best regards, Simon

Hello, You can override the reset functionality by passing a JLink script file to the JLink Commander that implements the ResetTarget() function. This will ensure JLink calls your custom reset function instead of the default target reset. Here is an example of how to override JLink functions: Overriding device specific connect To pass the script file to the JLink Commander, you can use the following command line option: J-Link Commander Command Line Options Best regards, Simon

Hello, Programming the OTP of this chip is not supported by J-Link, and we do not have any plans to do so in the near future because our schedule is quite booked at this time. You may want to add support yourself with the JLink DSK using the high-performance SEGGER Flashloader. More information can be found here: segger.com/products/debug-probes/j-link/tools/j-link-dsk/ wiki.segger.com/J-Link_Device_Support_Kit Best regards, Simon

Hello, Could you please send us a J-Link log file of the failing scenario? How to enable: wiki.segger.com/J-Link_DLL#Enable_J-Link_Log_File The S/N you have sent is from a unit from 2019 which is out of support and warranty. We recommend to make use of our trade-in program: segger.com/purchase/trade-in-program/ In the J-Link Commander, you need to select a device in order to connect to your core. In your case, select "CORTEX-M7". Best regards, Simon

Hello, It seems like you are using just the default settings of the remote server, so no additional command line options should be needed. Could you please provide one log of the failing scenario and one of the successful one? The log can be enabled with "-Log <LogFilePath>". Best regards, Simon

Hello, You seem to be using a version which is not up to date. Does the issue also occur with the current release version? https://www.segger.com/downloads/jlink Could you please send us a J-Link log file of the failing scenario? How to enable: wiki.segger.com/J-Link_DLL#Enable_J-Link_Log_File Best regards, Simon

Hello, The resolution that J-Link can measure is approximately 12mA, so the measurement may vary significantly when the target consumption is below that. Best regards, Simon