debug - save MDK memory content to file

Foreword

In the debugger, ready to analyze some buffer returned from the device.
Only to find, MDK shows the memory contents, but still could not save documents directly into a bin or can be directly copied to the text, do the setback ah ...
check the internet, we usually hex2bin, save the file with the sAVE command to bin + memory data.
That I was able SAVE command to save memory MDK hex. But bin hex turn this problem, find a few versions of the hex2bin not so. It should be MDK5 generated HEX format version of the relatively new bar.

Finally, I use the J-Flash V6.46g + winhex get, wit ah :)
J-Flash is the best hex2bin.

test

MDK save the contents of memory to hex

This step has official information.
http://www.keil.com/support/man/docs/uv3/uv3_cm_save.htm

I began to address this debugging from 0x20005E2c save 303 bytes, then my command as follows:

SAVE d:\USART1_RX_BUF 0x20005E2c, 0x20005F5B

Enter the command place in MDK command line input box.
Here Insert Picture Description
Generate a good look at the document, indeed hex format.

Turn the hex bin

I find a few of hex2bin, can not correct this hex will turn into a bin.
I direct JFALSH, this is installed JLINK that will be installed on the drive.
Load the hex file JFALSH, it is normally open. The debugger that comes with the tool is easy to use.
Here Insert Picture Description
Save JFLASH comes with a feature to save data files into a bin

and then turn a good open bin file winhex, you can use the copy function, copy the contents of the binary out, stick to the project, for analysis by the agreement.

Finally, you get an array of binary content, then you can do a decent living.

unsigned AnsiChar data[304] = {
	0x01, 0x2F, 0x01, 0x01, 0x00, 0x01, 0x26, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 
	0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0xFF, 
	0xFF, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0xFF, 0xFF, 0xFF, 0xFF, 0xFF, 0xFF, 0xFF, 0xFF, 0xFF, 
	0xFF, 0xFF, 0xFF, 0x28, 0xFE, 0xFE, 0xFE, 0xFE, 0xFE, 0xFE, 0xFE, 0xFE, 0xFE, 0xFE, 0xFE, 0xFE, 
	0xFE, 0xFE, 0xFE, 0xFE, 0xFE, 0xFE, 0xFE, 0xFE, 0xFE, 0xFE, 0xFE, 0xFE, 0xFE, 0xFE, 0xFE, 0xFE, 
	0xFE, 0xFE, 0xFE, 0xFE, 0xFE, 0xFE, 0xFE, 0xFE, 0xFE, 0xFE, 0xFE, 0xFE, 0x14, 0xFE, 0xFE, 0xFE, 
	0xFE, 0xFE, 0xFE, 0xFE, 0xFE, 0xFE, 0xFE, 0xFE, 0xFE, 0xFE, 0xFE, 0xFE, 0xFE, 0xFE, 0xFE, 0xFE, 
	0xFE, 0x14, 0xFE, 0xFE, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 
	0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x14, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 
	0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x1E, 0x00, 0x00, 0x00, 0x00, 
	0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 
	0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x0A, 0x00, 0x00, 0x00, 0x00, 0x00, 
	0x00, 0x00, 0x00, 0x00, 0x00, 0x3C, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 
	0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 
	0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 
	0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 
	0x00, 0x00, 0x08, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x04, 0xFE, 0xFE, 0xFE, 0xFE, 
	0x08, 0xFE, 0xFE, 0xFE, 0xFE, 0xFE, 0xFE, 0xFE, 0xFE, 0x08, 0xFE, 0xFE, 0xFE, 0xFE, 0xFE, 0xFE, 
	0xFE, 0xFE, 0x02, 0xFE, 0xFE, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0xF3, 0x3D, 0x00
};

MDK details do not really use, in addition to MDK did not have to use.
Originally from the device memory to copy the contents of the address, this is the IDE should do.

LostSpeed

Published 436 original articles · won praise 126 · Views 1.75 million +

His message board concerns