Search Results

Hi Alex, thanks for your response. The link provided is quite helpful. To be honest, I still don't know if I have the right requirement for tracing and can't really figure out its usecase. I think I need to inform myself what tracing is and if I can utilize its potential. Coming to ETB, I am afraid my chip doesn't support ETB. (pls see attachment). In this case I guess I need to rely only on software tracing. One of the child links from your link talks about trace with RAM functions. Perhaps thi…

Hi Alex, unfortunately the proposed access via path didn't work. ("Peripherals/GPIO/GPIOA/ODR"). (pls see attachment) Thats why I had to try out the previosly mentioned method. Jfyi. Kind regards

Hi Alex, I meant to say that it is not updating when the CPU is running. In the previous reply I just wanted to let you that it updated only when the CPU got halted. Kind regards

Hi Alex, thanks for your response. Sorry, my question was not clear. From the ozone user guide I got to know that the 'Memory window' updates itself at a fixed rate based on the 'Periodic Refresh' set. (pls find it attached) This is quite a convinient feature that I usually have the habit of looking at the memory window for updated values. Each time I set the Periodic Refresh to certain value (say 500ms), there is no periodic refresh observed in the memory window. And there is no command displye…

Hi Alex, thanks for your response. The proposed solution works like a charm. Please find the attached image. Not very important proposal. In the second attached image we could see that there is only upscale multiplication factor on the signal but no downscaling. It would be quite helpul to have this, to sclae large signals. Thanks for your support. Kimd regards

Hi Alex, thanks for your resplonse. Trying out your proposed soluation gave the idea to try out accessing the the peripheral reg like accessing a structure element. Taget.GetReg("Peripherals.GPIO.GPIOA.ODR"); //this works Attached you will find the console log. There is another way to access it, via Target.ReadU32(<peripheral_reg_address>); This works as well. Target.ReadU32(0x40020014); Thanks again. Kind regards PS: Just a small thought. Not very important though. For Target.GetReg() , the cor…

Hi Alex, thanks for your response. This works like a charm. Just a small observation. Not very important though. You can see that in the 'Data sampling' window I have selected the expression to be displayed in Hex, where as the Timeline data graph by default shown the expression in decimal. I could not find a way to change the display type in the graph. Like said not very important and jfyi. Kind regards

Hello, my memory browser doesn't refresh. Changing the interval in the 'Periodic Refresh' pane has no impact. I am using Segger J-Link EDU probe. Thank you.

Hello, the page for J-trace says the below about Trace Buffer- " Trace Buffer If the target device includes an Embedded Trace Buffer (ETB) or similar, trace can be done with a J-Link. The trace data is then written by the target into the internal trace buffer of usually about a few kilobytes and read by J-Link when the target is halted. With a trace buffer the last few thousand executed instructions can be available, which does not provide full insight, but can be useful to recall the execution …

Hello, is there a possibility to split two signals (basically which are of different singal levels) in the data graph to their indivdual y-axes for better visulization? Thank you.

Hello, from the Ozone user guide I could see that the CPU registers could be accessed via Target.GetReg(" ") from the console; On similiar grounds, what is the command to access the peripheral regsiter's value from the Console? Thank you.

Hello, is it somehow possible to add peripheral registers to the data graph (timeline) window for graphical view. Thank you. [img]https://pbs.twimg.com/media/F39gnTfXIAAQnPE?format=png&name=900x900[/img]