I have a target system that I am trying to get data out of. I want to use the swo trace output, I can get printf debug out using an ULINK 2 but using the same settings with a ULINK pro I can not get printf debug, just garbage out.
I have tried many settings for core clock but can not find the correct one.
Is there a way to read what the core clock is from the command line? Is there a way to set it from the command line?
I need it to work with both tools.
What speed are you programming the target to run at? Use that setting so the debugger and target have coherent settings. Either via SystemInit() in system_arch.c or in your debug initialization script (.INI)
I don't recall the SWV function to be materially different on the Pro vs conventional pod, but I don't have it with me right now to double check.
OK I got things working a bit better, but still see a difference in the ULINK 2 VS ULINK pro.
The processor is clocked by a 2 mhz clock, which is increased by the pll to 16 MHz. I put the JTag Max clock to 2MHz, and on the trace config I have core clock set to 16 MHz.
I have a single printf that prints This is a test XXX where xxx is an increasing number
ULINK 2
serial Wire output is defaulted to UART/NRZ SWO Clock Prescaler 14 (autodetect) which results in a clock of 1.142857 ITM port zero enabled
output to the display and file and no number ar missing
this is a test 0 this is a test 1 this is a test 2 this is a test 3 this is a test 4 this is a test 5
... this is a test 17 this is a test 18 this is a test 19
ULINK pro
Serial Wire output is defaulted to Manchester SWO clock prescaler 14 (can range 1 -16) ITM port zeron enabled.
Output to the dispaly misses many lines and the file has many control chars. is is a this ishis is this is a test 27 is is a test 32 this is a test 33 s is his is a test thihis is a test his is a test 72
As the ULINK pro is capable of faster sync than the ULINK 2 I would think it would get all the data, but it looks like it is misses quite a bit of the printed lines where the ULINK 2 captures them all.
Any ideas?
I don't think I'm using the same CPU, but my observation with the Pro is that it's very fussy about the USB cable, a cheap USB 1.0 cable that works fine with the ULINK 2 is no good for the ULINK Pro