I'm using uVision4 on an STM32 platform.
Is it possible to get a dump of memory to file during debug? I can view the memory, yes, but i can't even select the contents of that window to copy-paste.
what i need to accomplish is to compare certain memory locations (large ranges, not feasible to do manually) between function calls. i can not do it programmatically since it might adulterate the memory i'm analyzing.
any ideas?
Per; One technique I have used is to write a printf to the debug command window with a debugger function.ini routine. Then set a breakpoint execute to execute the function. Then go to the debug command line and do a log to file. You can also include this in your debug function. Anything written to the debug command window will be logged to the file. I have used this for all type of data dumps but I have never attempted to dump code space.
Look at the debugger LOG command and 'Creating Functions' in the uVision Debugger's Manual. Remember the printf function in the debugger function is a special printf function that writes only to the command window. This is NOT the same as the 'C' language printf function.
Bradford
Thanks for the reply, Al.
Trying to follow the user manual... I assume i'm supposed to follow the instructions for setting up the 'Debug viewer Window' using the ITM Stimulus Port...
Problem is, when i follow the instructions I run into the error:
"source\main.c(44): error: #734: function "fputc(int, std::FILE *)" conflicts with using-declaration of function "std::fputc(int, std::FILE *) C"
Any idea why this is?
also, i have no idea how to bring up the ITM privileges User interface as they outline it in the manual. Any hints here would be welcome.
Per; I must have a much older version of MDK-ARM. My prior post referenced the PK51 because you did not list a product type.
The Function Editor for MDK-ARM is defined at this link. http://www.keil.com/support/man/docs/uv4/uv4_df_createfunct.htm
I have no idea what your error message is trying to tell you.
My references are for running the Debugger in Simulator mode using the Function Editor in the Debugger. Bradford
Yuo can either use the SAVE command from the command prompt while in debug mode to create a .hex file on your hard drive based on the memory image, or first enable the LOG command and combine that with another one that I forgot right now to generate a non .hex file.
Thanks a ton, Tamir. That was exactly what i needed.