Search Results

Do the Segger software tools support IPv6 addresses for connecting to remote hosts? Are there address format constraints? e.g. leading zeros, double colons, etc. I can't see any mention of ipv6 in the documentation, and it is not currently working for me, but I am not entirely sure if it is a segger tool issue, or a separate network arch issue.

Is is possible to use the plugin or JS scripting engine to send data into the "Timeline" window? The application is for real-time plotting of a signal. In this application, the values of the signal have to go through a hardware FIFO, so they only exist in bursts in an array. Although, in this case, each sample *is* timestamped. So, if I could highjack the drawing in Timeline, and trigger updates on specific PC matches (or some other trigger mechanism), that would work great. It would just be a l…

Can RTT be made to work on an ARM1176 target? Yes, I know it is now ancient silicon. After some tinkering, there seems to be some suggestions that it might be impossible due to no "background memory access"? The control block is definitely linked and sitting at 0x00012940, but there's no RTT output on the terminal, And the Ozone console surfaces that BMA error: ``` 1:04:15.579 090 Edit.SysVar (VAR_ALLOW_BMA_EMULATION, 1); 1:04:17.144 014 System settings were written to the project file. 1:04:22.…

Okey dokey, apparently the problem is the JLink has to be disconnected and then reconnected, too, otherwise it (apparently) can keep the TAP open and bypass RDP, even through the device doing a Flash Option Bytes programming sequence. Resolved now.

@Haddock Also look into RTT. It is a fairly good tech, and it gives you a data in/out pipe. I have used that before to set up a system where a running device listens for "commands" over the input stream, does certain manufacturing/comissioning-time actions, and then locks out any more commands. Also look into pylink-square. They wrapped the Segger DLL in a python library, making it significantly easier to do a lot of the manipulations. afaik the way the pro's do the "production date" thing is th…

This may be an STM32-specific thing, and not related to Segger BUT: I enabled read protection on a STM32L496AG part. When I connect with: Source Code (1 line) And then do "halt", sure enough, I am presented with the dialog about "Active read protected STM32 device detected." But if I select "no", and DON'T trigger a mass erase, it drops to the "J-Link>" prompt, and I can then do: Source Code (1 line) and it reads out the flash memory. SP, vector table, etc. Which is ... surprising?

Quote from SEGGER - Nino: “But if Apple did not change anything major (again). Everything should be working as expected ” Font selection appears to not work in 3.26e in OSX 12.3.1, and defaults to Helvetica.

I need to come up with a solution for setting an external RTC on a board w/ an STM32L4 line mcu. It occurs to me that I could potentially do this via an OpenFlashLoader tool, where I could create a few memory-mapped variables, e.g. 32b epoch time to set, 32b sentinel to start setting, 32b response value to pend on. Can multiple separate OpenFlashLoader ELF's be used for different address spaces on a chip? Or would I have to extend the "main" one that ships for use with QSPI flash? And if I have …

I am also consistently having problems with recent versions of Ozone on OSX. I just tried 3.24b, and these issues persisted. I believe they showed up all through the 3.23 series, so I have been using 3.22a. Behaviors: - Dragging the "FreeRTOS" window from being docked to undocked will usually result in an app hang or immediate app crash - Dragging other windows around sometimes does not cause a crash, but resizes the app window and results in large blank gray spaces in the layout - Font looks od…

Hi. I am using JLink on OSX, targeting an STM32L496AG micro. When connecting via command link JLinkExe, it seems like the RTT control block is not automatically found. Invocation is: JLinkExe -device STM32L496AG -if swd -speed auto -autoconnect 1 While JLinkExe connects and controls the core OK without issue, it does not seem to make RTT output available to the JLinkRTTClient running in another shell. Is this expected behavior? However, when using Ozone for debugging, the RTT block is detected a…

Is there a patch to add SystemView that is avaialable for the FreeRTOS V10.0.1 kernel? There are a few places that are different, and different enough that it is not immediately obvious how to manually patch in the changes. e.g. the changes in `prvAddNewTaskToReadyList`, which appears to have changed significantly between V10.0.0 and V10.0.1.

Is there any existing tool that could be applied to a hardware-in-the-loop QA system to capture information like the stack trace heading into the hardfault? And ideally, the equivalent of the the full output of the FreeRTOS view from Ozone. Beyond that, maybe even the stack unwinding for each of the tasks, too. The application here is that we have a QA agent doing very labor intensive testing, and in the case of hardfaults, it would be great to grab all that information at the time of failure, w…

I am working with a board that is copied partly from the STM32L496G_Disco board as a reference, using that exact micro and SPI flash. The good news is that the bundled OFL loader for this MCU + flash combo works "out of the box" with JLink and Ozone. Wow. The bad news is that it is a bit slow to program even a modest size hex, ~1.7MB takes 30+ seconds. What speed(s) are set up for the MCU and the QSPI clock in the ST_STM32L496G_Disco_QSPI.elf OFL that is bundled in the JLink package? Is the sour…

Will the output from the Ozone code profile listing for the "load" metric be valid for functions that are moved to a run-from-RAM section via a gcc attribute? e.g. __attribute__ ((section (".fast"))) , with the .fast section located in the RAM segment by the linker script . I don't have a minimum working example to reproduce at the moment, I am just observing this in the context of a large/complex program where I am trying to accelerate some crypto functions. When I move some of the functions th…

Adding that watch does not cause a crash in 2.56w . I have had a lot of other problems with versions > 2.60 , hangs and crashes when resetting and reflashing. Looking forward to things getting stabilized.

One follow-on here: If I try to enter in a watch of *(uint32_t*)0x200221D8 , Ozone crashes immediately. Version 2.60e running on OSX 10.14 Mojave.

Alright, for a little more exposition, the error can be captured in a simple printf of the address before and after the function call. e.g.: C Source Code (1 line) Looking at the disassembly, this compiles to: Source Code (4 lines)Where 0x080B0070 is the address of the const string. So it looks like R7+0x10 = 0x2001C090 is storing the address of the variable. In the suspicious function, R7 is getting stacked, but then the incorrect value in unstacked, ergo my suspicious function must be clobberi…

I can't profile the elf, since it would contain our proprietary source. Maybe if we put an NDA in place? But then you would need very specific hardware for the ELF to even run. This issue also happens when using gdbserver + eclipse + GNU Arm Eclipse plugin suite; the behavior is reproduced in the Eclipse watch window. How is Ozone/Jlink even resolving the variable name to a location? There isn't a symbol in the ELF for it, as far as I can see ...

I am debugging a project with Ozone, and I am seeing something that I do not understand the cause of. It may have a clear cause ... or it may be an Ozone bug. I'm unsure. In the code that I debugging, I am setting a watch on a stack variable (a struct), and Ozone reports the location as 0x2001C090. The size is correctly reported as 121 bytes. After a returning from the call to a function that is suspected to contain bugs (by step-over before entering), the location reported by Ozone changes to 0…

Interesting. Will J-Link support OpenFlashLoader loaders, if they are added to the XML file? I remapped the external flash bank to a base of 0xC0000000, which is unused on my micro, in both the FlashDev.c and in the XML file. J-Flash works as expected when operating from these addresses, but J-Link commander only returns "Could not read memory" when trying: mem 0xC0000000,0x1FF