Search Results
Search results 1-5 of 5.
This site uses cookies. By continuing to browse this site, you are agreeing to our Cookie Policy.
-
I have a question regarding Ozone and the time it takes to load data from an ELF file. We have a fairly large application running on an STM32F processor and during development the time to load the ELF file into Ozone grew from 10 of seconds up to 6-8 minutes. This 6-8 minutes seems very long since running "readelf" takes a small fraction on this time. Also, this 6-8 minutes greatly increases troubleshooting time. Recently, in an attempt to understand what might be causing this delay, I created a…
-
I was able to get Ozone functioning well just this morning. The main change I made was adding in the trace pin configurations similar to the project for the "Cortex-M Trace Reference Board" project that I found on your website. To answer your question below, my project is built in Linux with the "arm-none-eabi-" compiler. We don't use any specific IDE.
-
Hi Nino, Some of the information you asked for: 1) An STM32F429II on a custom board 2) SWD, but I could use either SWD or JTAG (all the pins are there) 3) Ozone = V2.44e, JLINK = V6.18c 4) I will try to make a small simple project which I would feel comfortable sharing. Attach is a jdebug file without connection to an ELF file. 5) I've tried USB and ethernet. I am using a USB hub (StarTech ST7300USB3B) and an Ethernet switch (Netgear GS105) One other potentially odd bit in my configuration is th…
-
I hope this isn't too much of a newbie question, but this is my first attempt at using Ozone (with a J-Trace Pro for Cortex-M) and I'm experiencing an odd issue. We are using the Linux version of Ozone, since Linux is where our code exists, if I create an Ozone project without pointing to my device source code ELF file, Ozone seems to work reasonable. In this case I can see the processor registers, view memory, step through the assembly code, halt and continue execution. The basic stuff works. W…