Search Results

Hello Nino Thanks a lot for this. Yes it works in both the Ozone terminal and the standalone viewer. After trying this I found I had my system clock wrong. I think that it worked in the standalone SWO viewer made me think the STM32 settings were o.k. This should be very helpful in the future. Thanks again Nino.

They are not active at the same time and the SWO box is ticked. I am using a STM32F103C8 (blue pill) With PB3 wired to SWO and PB4 wired to NRST of the JLink plug. I have not done enough research on this last problem to waste any of your time on this, I was just asking in case it was a known fault or the should be something easy to explain. I can start a new thread if I am stuck after further research. Thanks again for your valuable help.

Great thanks Nino that stopped the segfault. If I can find out how I'll mark as solved. One point though, if I use JLinkSWOViewer I can see my ITM_Print(0,"hello") but although the terminal now has 'SWO Active' I do not see anything when the processor is running. (All it is doing is sending ITM print messages every second) Is there something else I have to activate? Thanks

I am running Ozone 2.60 on Debian Buster with a JLink EDU It works great and very happy with it. I tried to go further and use the SWO o the cortex processor I am working with. So I click Tools Trace Settings and I get a segfault straight away. I check for updates, then install the V2.62e deb. This also segfaults on Trace settings. I will not state anything about processor etc as it segfaults on an empty project. I think that the deb file is lacking a dependancy. This is the last lines of strace…