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,
what am I doing wrong? Always when I try this
save c:\projekte\read.hex 0x80000000, 0x80010000
uVision is flooding my hard disk with waste data. Are there examples for the correct using?
Best regards Detlef
What do you mean by, "flooding" and "waste" data?
You've asked for a 64K address range, and the size of a corresponding Intel Hex file will be more than two times this; ie, >128K
What size are you actually seeing?
http://www.keil.com/support/man/docs/uv3/uv3_cm_save.htm
The size is growing above 1 Gigabyte within a very short time (approximately within 20 seconds) and uvision is freezing. When this happens you have to kill the uv3 process in the task manager.
Opening the file shows the "waste" data, which may be the first line of a correct file repeated endlessly and "flooding" the hard disk.
The "waste" data:
:0200000480007A :0200000480007A :0200000480007A :0200000480007A :0200000480007A :0200000480007A :0200000480007A and so on...
Well, obviously is the command line errors free and it seems to be a bug in uVision.