We are running a survey to help us improve the experience for all of our members. If you see the survey appear, please take the time to tell us about your experience if you can.
Hi all,
I am still new to the embeded system and currently start self-learning through the example provided in MDK.
Having problem in Debug(print) Viewer because It print ASCII code instead of text even it is in Terminal Mode.
Target HW: SAME70 Debbuger: ULINK2
Max clock: 1MHz Coreclock: 168.000000MHz Trace is Enabled ITM Stimulus Ports 0 and 31 are checked
After searching through the necessary information I am still unable to print the text.
Below are the documents that I refered to: www.keil.com/.../fs_examples.html www.keil.com/.../uv4_db_dbg_printf_viewer.htm http://www.keil.com/support/man/docs/ulink2/ulink2_ctx_trace.htm
What could be the problem? Is it becuase of the incorrect setup for my debugger?
But when I start debugging mode, Trace Record windows show ITM range from 0-31, is it the incorrect core clock cause this problem? if yes, how can know the core clock?
Hopefully anyone could give me some idea or share any related link to me.
Thank you.
The best way to handle this, I think, is just to convert everything to Unicode and stay away from extended ASCII except where it is absolutely necessary for legacy reasons.
Dim enc1252 As Encoding = Encoding.GetEncoding(1252) Dim bArr(0) As Byte bArr(0) = CByte(131)
forum.centos-webpanel.com/.../
Hi Robert,
Thanks for reply! However, I found that the problem is cause by the incorrect core clock vlaue in the trace debbuger setting.
After I open the file system_SAME70.c, the clock setting should be 150MHz for MCK(Master clock).
After changing the value of core clock in debugger trace setting, then the correct text is displyed in Debug (printf) viewer.
Again thanks for the sharing.