GitXplorerGitXplorer
e

check-avr-bootloader-clears-flash

public
2 stars
0 forks
0 issues

Commits

List of commits on branch master.
Unverified
4873582cb531234182d999a11ab22af1cda83f4c

add funding

eellensp committed 3 years ago
Unverified
dae37296a35331a0a42041a4d8d17f0e164108ff

more typos

eellensp committed 3 years ago
Unverified
fe8f8616183f2136c7ea85e7232f2bc415c029cf

ad node that it is atmega2560 only

eellensp committed 3 years ago
Unverified
83babdb7cf5fdf0231369ca00eaa35a1a1aeb8ba

update readme

eellensp committed 3 years ago
Unverified
e7bfca26fc5c8f559ba84e8bd2b641b9741a357a

Delete un needed template files

eellensp committed 3 years ago
Unverified
ed59d7491e1bde2920b5630bf9cf80dbf4944a6e

fix readme typos

eellensp committed 3 years ago

README

The README file for this repository.

Tests that the end of flash ram on a atmega2560 is cleared by the bootloader on a new firmware upload.

There is a long known bug in a lot of mega2560 boot loaders that does not clear that flash above 0x3C000 This checks if your bootloader is effected by this or not.

AVR Fuse reading based on code found at https://www.avrfreaks.net/forum/read-fuse-bits-runtime by David Prentice

Example output consists of:

information:

"lockb = 0xFF" "ext fuse = 0xFD" "high fuse = 0xD8" "low fuse = 0xFF" "BOOT loader start : 0x3E000"

Now the code check that all high bytes are set to FF begins:

"Checking 0x3C000 through 0x3E000 has been cleared."

If the bytes are cleared you get a positive result

"This bootloader is good!"

If the bytes are not cleared you get, the first address that failed and its contents eg "Addr:3C000[1]" "This bootloader is faulty, it does not clear the full usable flash area"