i have tried to read (flash contents) from Uno r3 by avr-isp programmer
checking file after read but so big file and not usable... (much more FF)
attached 3 file
1- original file from arduino ide (which correct)
2- from avrdude
3- from avr studio
please help what is that problem. and how can i fix it.
br
checking file after read but so big file and not usable... (much more FF)
When the compiler generates a .hex file, the file contains only the code from your program.
When you read a .hex file from a chip, you read the entire flash memory space (32k), including memory that is unused and unprogrammed (which will show up as 0xFF)
westfw:
When the compiler generates a .hex file, the file contains only the code from your program.
When you read a .hex file from a chip, you read the entire flash memory space (32k), including memory that is unused and unprogrammed (which will show up as 0xFF)
So you probably don't have any problem.
Hi westfw
you are right about FF but my files more big then 32K
one of 78kb other one 90K
i don't know what is problem.
that files are for test and blinking pin 13
i tried to flash that bigger files to uno its done. and blinking is OK
you can test it.
thx for help
osezer34:
Hi westfw
you are right about FF but my files more big then 32K
one of 78kb other one 90K
i don't know what is problem.
This is normal - .hex takes 2 characters for every byte, plus the 6 characters (IIRC - something like that) at the start of each line, and the checksum at the end, and the linebreak characters. So the .hex file is 2.something times larger than the data it represents, which is exactly what you're seeing.
DrAzzy:
This is normal - .hex takes 2 characters for every byte, plus the 6 characters (IIRC - something like that) at the start of each line, and the checksum at the end, and the linebreak characters. So the .hex file is 2.something times larger than the data it represents, which is exactly what you're seeing.