Recent Activities
This site uses cookies. By continuing to browse this site, you are agreeing to our Cookie Policy.
-
eggplant886 -
Posted the thread GDB client issue in SES.
ThreadHello 1. When using SES with GDB server for debugging, SES would send packages like '$vCont;s:0#22' '$vCont;c:0#12'. It uses thread id 0 here which means 'an arbitrary thread' according to GDB protocol. Some GDB server does not accept such an ambiguous… -
deqing -
Posted the thread Security JTAG not worked with Jlink-Plus and i.mxrt1050.
ThreadHi, I use Jlink-plus to connect to the Security-jtag enabled device (i.mx rt1050), however, it failed. Attached is the script and running result. Can you help to give how to solve it? Thanks -
StefanSchmidt -
Replied to the thread [SOLVED] J-Link GDB Server erases flash sectors used for storing persistent data when downloading a firmware image.
PostI close this thread as I found a solution for the issue. I am using the Cortex-M plugin in a docker container to connect to the GDB server running natively on my host. In order to "keep" the settings in the device I added the following to the launch.json… -
Steven Bos -
Posted the thread J-Link OB Firmware for Micro:Bit v2.2x.
ThreadAt my university we use the Micro:Bit v2 in various courses at various levels. Unfortunately the Micro:Bit Educational Foundation changed the interface chip in 2022, rendering the current J-Link OB v2 firmware for v2.00 unusable. This has also been… -
bipbeepbip -
Posted the thread Flash programming on Renesas DA14706 seems to leave the flash controller in an invalid state.
ThreadHello, When I use J-Link commander to write a binary to the flash using the J-Link OB on the evaluation board, the SoC will then not boot and following the execution in Ozone shows that it stays in the boot ROM for a while and then reset. I noticed… -
StefanSchmidt -
Replied to the thread [SOLVED] J-Link GDB Server erases flash sectors used for storing persistent data when downloading a firmware image.
PostOk, I am not getting it: According to the log in localhost:19080/flash.htm the area with persistent data is not touched at all... Where the heck is the stored data? -
StefanSchmidt -
Replied to the thread RTT 50ms timeout is too short for linux container pass-through.
PostIt might not be the solution for your setup, but I am using JLink GDB Server and RTT Viewer on the host and connect to the GDB Server on the host from within the docker container. The marked line in the launch.json shows the connection to the GDB server… -
SEGGER - Alex -
Replied to the thread Differences in Flasher/J-Link performance.
PostHi, Does not sound familiar. In general, Flashers do neither support RTT nor HSS (both J-Scope modes) so it is simulated on the PC side. As you observed: With much less throughput I do not see why timestamps and values should get corrupted if the TIF… -
fraengers -
Posted the thread live tracing - timeline.
ThreadHello, I'm curently testing J-Trace with Ozone. As I already found out, there is only a limited amount of traced data visible in the timeline. And while the MCU is running, no data is visible at all. Can (a limited amount of) data be shown while the… -
zamniah -
Posted the thread Flasher Secure + Server - support for STM32U5 locking with RDP2.
ThreadHi, we are wondering about Flasher Secure support for STM32U5, since your wiki page wiki.segger.com/ST_STM32 notes that "native lock support" is not present (SFI is not meant here, just RDP2 and option bytes). Though there are JFlash/JLink files as… -
cinderblock -
Posted the thread Differences in Flasher/J-Link performance.
ThreadI have an older ARM Flasher debugger. Using it, I have reliable RTT/JScope plotting over a 4MHz SWD connection. I also have a new J-link PLUS Compact. It seems to be capable of much more throughput with an identical setup. However, I seem to get a lot… -
friesen -
Replied to the thread Jlink pro reg not reset.
PostI can confirm that "r" resets the register. Some testing notes: PLLCFGR reset value is 0x00001000 PLLCFGR address is 0x4002100C Following JLINK commander "erase", PLLCFGR value is 0x01001412 "r" resets this to 0x00001000 I've attached the jlink… -
cinderblock -
Posted the thread Better handling of data channels in JScope.
ThreadI'm using JScope heavily for some debugging in RTT mode. I would like to rename/configure traces more permanently/programmatically. If I rename them in the XML config, it works when I load the project, but the names get lost when I connect to a… -
SEGGER - Alex -
Replied to the thread Jlink pro reg not reset.
PostDoes it also happen when issuing the reset via J-Link Commander? Use „r“ to reset Use „mem32 <Addr>“ to read the PLLCFGR -
RTTseemsOK -
Replied to the thread RTT 50ms timeout is too short for linux container pass-through.
PostI could still use help on this. Ideally there would be a way to adjust the timeout, otherwise, if someone could adjust in it a new build that would be good too. Or even more ideally... Maybe this project is updated as a Tabby plug in or something a… -
JayTT -
Replied to the thread JLink flash failure when using Ozone: Timeout while erasing sectors, RAMCode did not respond in time!.
PostFYI, after trying many things to find the difference, the one that worked in the end is going into the source tree and running: Source Code (1 line)to completely purge the build output directory and rebuild. -
cinderblock -
Posted the thread [Feature Request] Colors in RTT Viewer All Terminals.
ThreadI recently learned that RTT Viewer Terminals support colors (and a couple other control codes) segger.com/products/debug-prob…#using-text-control-codes I'd seen that Terminal 1 showed up in Red in the All Terminals tab. I was confused to find out that… -
JayTT -
Posted the thread JLink flash failure when using Ozone: Timeout while erasing sectors, RAMCode did not respond in time!.
ThreadI have a new failure when using 'Reprogramming Flash' from Ozone with my STM32 app. This started occurring about two weeks ago for me, was not an issue prior. Does not reproduce with same JLink, same STM32 device, same code, same process when connected…