Search Results

Search results 1-20 of 31.

This site uses cookies. By continuing to browse this site, you are agreeing to our Cookie Policy.

  • We are still experiencing this problem. Do you have any update? Best regards, Thomas

  • Hi Nino! I just found out that it was my fault. Ozone shows the data and function entries as expected! Sorry for the noise best regards, Thomas

  • Hi! Quote from SEGGER - Fabian: “Therefore we suggest that you correct the HAL-init to use the right address space (see above). ” I think you may have posted the wrong screenshot. Perhaps you meant chapter 59.5.8. ? But, unfortunately, 0xE00E1000 also reads as zero. You should be able to reproduce that result on your side. Quote from SEGGER - Fabian: “The work-around/hack is not recommended. ” I was not yet able to find a work-around.. Of course, I could fake the HAL_GetREVID function, but we ha…

  • Do you have any update on this topic?

  • Ozone 3.10d In C, it's possible to have two distinct global static variables or functions with the same name in different source files. For example: a.c static int foo; static void bar(void) { } b.c static int foo; static void bar(void) { } In this case, the "Global Data" and "Functions" View lists only one of them (depending on the order in the linked .elf file). I would expect that all variables and functions are shown with their according source file in the "Scope" column.

  • Do you have any update on this topic? Or do you have an example work-around script? It's not entirely clear how I could write one myself..

  • Hi! I haven't checked on 2) yet. But regarding ETF-Trace: forum.segger.com/index.php/Att…69efc1e8839d9ed091912b903 Does that mean, that the Timestamps checkbox does not work for ETF? Then I think that the combined Data sampling/Instruction trace window is a little bit misleading.. I was confused for a few hours, until I connected a scope and noticed the bogus time measurements. If it's not on the same timeline, data samples and trace really should not be shown to be correlated.

  • Googling for 0x5C001000 turns up some interesting results.. This might be relevant to you: xor-gate.org/post/stlink-arm-ap-access/ "On the STM32H743 there is an APB-AP on APSEL 2 which I suppose may be present on other STM32's as well. Through this AP you can access the DBGMCU at its documented address 0xE00E1000. However, if you use the standard ST-Link memory access commands they will clobber AP2's CSW.DbSwEnable bit. This then prevents accesses to the DBGMCU via AP0 (and presumably the CPU) a…

  • Hi! Setup: I am using Ozone 3.10b and a STM32H743 @ 480MHz. I've set up ETF trace according to wiki.segger.com/STM32H7#Tracing_on_ST_STM32H743 In the trace settings dialog, I set the source to Trace Buffer, and CPU Frequency to 480000000. I'm using the .pex file from wiki.segger.com/images/b/b8/ST…43_400MHz_TraceBuffer.zip Problem: After the OnTraceStart() hook of the pex-File is run, the DBGMCU->IDCODE register at 0x5C001000 reads 0x00000000 instead of the expected 0x20036450. This can also be …

  • Hi! I am using Ozone 3.10b and a STM32H743 @ 480MHz. 1) I've set up ETF trace according to wiki.segger.com/STM32H7#Tracing_on_ST_STM32H743 In the trace settings dialog, I set the source to Trace Buffer, and CPU Frequency to 480000000. When I do a for()-loop based delay of 4.54 microseconds (measured with an Oscilloscope), the timeline shows this as only 2 us. When I hover over the delay function, it says "991 Instructions executed, 2064 ns". 2) When I repeat the same test with my J-Trace and 4-B…

  • Can do! Here's an empty CubeMX5 project for a Nucleo-H743 board. forum.segger.com/index.php/Att…69efc1e8839d9ed091912b903 FEB87B47 is decoded as "?" in the Disassembly window. Source view is even more confused and shows only the "7B47" part of the instruction forum.segger.com/index.php/Att…69efc1e8839d9ed091912b903

  • Hi! I'm using Ozone 3.10b (linux) with an STM32H7. The Disassembly window can't decode the following double-precision FPU instructions: FEB8 7B47 Ozone: ?, gcc listing says: vrinta.f64 d7, d7 FEB8 6B45 Ozone: ?, gcc listing says: vrinta.f64 d6, d5 (And possibly other vrintX.f64 variants. These are just the ones I've seen in my program) best regards, Thomas

  • "I am a bit confused here. What are you refering to exactly here? Is ETF trace not working with the example project from the Wiki out of the box?" The trace itself works fine. Only the Trace Settings GUI Dialog misses a field to set the CPU frequency. Without setting VAR_TRACE_CORE_CLOCK, the time stamps in the Timeline are wrong. (I'm not using the example project, but integrated the .pex into my own .jdebug file)

  • Hi! I've just discovered, that you've implemented ETF Trace Buffer on the STM32H7! (See discussion here and here, also this Wiki page) Some minor points: - The Trace Settings Dialog misses a CPU frequency input field - If I do "Edit.SysVar (VAR_TRACE_CORE_CLOCK, 400000000);" manually, everything works as expected - Ozone 3.10a for Linux does not yet include the required JLinkARM v6.60 Libraries - Is there a way to update the libraries manually, like in the Windows version? - Otherwise, I'll just…

  • Here's the user manual: st.com/content/ccc/resource/te…lations/en.DM00493601.pdf There is no 10 pin connector for the target processor. Of course, all STM32 pins are available on pin headers, so you could use jumper wires to connect an external J-Link to PA13/PA14. The embedded ST-Link goes into three-state, so you can do it in principle. But that's no substitute for the Reflash-Utility, which was the killer feature for Ozone evaluation. It will be dearly missed by students. BTW: The manual ment…

  • Sad to hear that. The small NUCLEO-32 boards do not have the MIPI-10 connector. Also, I think the Reflash-Utility was a great marketing tool for both Segger and ST.. at least that's how I tested Ozone/SystemView and convinced my company to buy some JLink debuggers!

  • Will there be a ST-Link Reflash Utility for the new ST NUCLEO boards?

  • Bonus question: When you say "telnet", do you really mean TELNET according to RFC 854? Raw TCP sockets would be far better for binary data (no telnet IAC escape character handling, etc.). If it really is RFC 854, an option to turn that off would be nice.

  • Ozone 2.7.0a on Linux x64 My STM32 application uses RTT to print debug messages on RTT channel 0. Additionally, I want to use RTT channel 1 to output real-time current and voltage samples from a control loop. It would be nice, if Ozone could just open additional telnet ports for these RTT channels, for example on port 19021 + Channel-ID Ozone already seems to fetch the additional channels.. at least the RdOff value is updated constantly. Or is there any other way to get data from additional chan…

  • Ozone 2.7.0a on Linux x64 My STM32 application uses RTT to print debug messages. When the "Terminal" window is open, and also a telnet client is connected to localhost:19021, RTT messages are sent to either the Terminal window, or the telnet client (seemingly at random). I would expect that all messages are sent to both the terminal window and the telnet server reliably. Alternatively, the Terminal Window should be grayed out when another client is connected. The current behavior breaks both fea…