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. When an Ozone project is created which does point to my device source code ELF file, Ozone does just doesn't work. The registers and memory windows never shows any values, I can halt the processor but not step through the code or continue execution. I do see the source code and function names, and when I attempt to step I see the "Debug.StepOver()" call in the console, but basically no other reaction.

Any thoughts as to what I might be doing incorrectly?

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 that Ubuntu is running in a VMWare virtual machine within my Windows 7 PC, so there are those drivers in the mix as well. My VMWare version is 12.5.6 build-5528349.

I will work on a ELF I can share.

Thanks,

Steve.

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.