Hi developpers , Actually I meet a problem with the use of the logic analyzer in myproject ,I can't add any signal in real debug mode ( not simulation) I use the keil ulink ME probe,so I searched in many links to find a solution , but there isnt ,My card is not a dev card ,it is a cortex m3 with many peripheral around like LCD ,DSP ... .
Well my question is how to configure the project (if it is possible ) so I can use the logic analyzer
NB: I can debug of course my card see variable value ,but can't use only the logic analyzer.
I don't think you can use any sw logic analyzer when running on real hardware.
When the simulator is used, the Keil tools can (for supported chips) not only simulate the processor instructions, but can also keep track of the state of the simulated devices like I/O pins, UART, I2C, ...
Some processors contains a trace function, but that is a function where the processor continuously dump information about the instruction execution - not the state of all the individual signals of all GPIO etc. This trace dump can be used to see what the processor did before it suffered an exception.
So can you explain me why we have in the debug two sides : simulation and "using probe" :
Debug=> "use ulink me"==> settings==>trace ,wich mean we can trace in real mode.
??
Well, for processors with trace module, it's possible to sniff the instruction processing.
But much I/O operations aren't even involving any instruction processing - you can use UART, timers, SPI, ... to toggle processor pins without the processor core being involved.
So if I understand if we have an ETM trace cell , we can visualize variables in the logic analyzer and in real mode?
Logic Analyzer can be used also when debugging real HW (Cortex-M) but is limited to monitoring memory locations.
DWT unit in Cortex-M provides trace information also for memory read/write. Therefore it is possible to monitor CPU read/write to any memory location (including peripheral registers).
ETM is not required.
For example: Monitoring analog value can be achieved by defining a memory value which is updated by the A/D converter. Adding this variable to the Logic Analyzer automatically configures the chip trace resource to trace writes to the defined location.
www.keil.com/.../ulinkpro_trace_la_window.htm
Robert,
Can you say something about the sampling rate of the logic analyzer?
Whenever CPU writes to memory it can emit trace information.
Logic Analyzer will therefore capture every write to defined location rather than periodically reading it. Sampling rate is not relevant in this case.
Well I adde a simple global variable that changed value in time ,when I add it to the logical analyzer no problem but when I run debug ,the value doesn't change ,that's why I think I need the ETM cell trace ,cause I don't see why it is not working and changing values in time. NB: I did all steps of configuration ,I don't think I'm missing something.
Initially you said: >In the status bar I don't have the message : Trace:Running .. is it normal? No. This indicates that trace is not captured.
Probably trace is not configured correctly (or not generated by the target or not connected properly ...)
www.keil.com/.../ulink2_trace_status.htm http://www.keil.com/support/man/docs/ulink2/ulink2_ctx_trace.htm
Dear Sir Actually you have right I have this message :
"No Synchronization" wich mean there are no synchronization packets received from the target. This indicates that the Trace hardware is either not connected or improperly configured.
the microcontrollor is STM32F101R8 , it contains the trace cell,can we use logic analyzer with this microcontroller?( I can do the step by step debug in SDW without problems) if not I suppose the thread is closed ,if yes how can I configure it ?
Best Regards
Take a look at Trace Configuration for STM32F10xx to see how to configure: http://www.keil.com/support/man/docs/ulink2/ulink2_STM32F10xxx.htm
I did , now I think that hardware doesn't contain a ETM debug interface, we have just a 10 pin connector debug,so in this case can you confirm please that I must have the right interface , is it the reason why it is not working?