avr/bootloader
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

test: the walk fixture states the board's fuses, not an approximation of them

Browse Source 
The profile called the ssd1306 board's own read ff ff ff dc; the part reads
ff ff fd dc - an Atmel-ICE and the loader agree on that byte. Only the high
fuse decides the walk region, so nothing about the refusal changes; the
fixture now names a configuration that was read off hardware.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This commit is contained in:
BlackMark
2026-08-16 04:49:51 +02:00
parent 37f9747e26
commit 1541818254
1 changed files with 4 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

7
test/pbwalk.py
View File

@@ -50,9 +50,10 @@ def main():
os.makedirs(workdir, exist_ok=True) os.makedirs(workdir, exist_ok=True)
dump = os.path.join(workdir, "dump.bin") dump = os.path.join(workdir, "dump.bin")
# The ssd1306 board's own fuses, and the same boot section with reset left # The ssd1306 board's own fuses, as an Atmel-ICE reads them off the part,
# on the application - the one difference that decides the refusal. # and the same boot section with reset left on the application - the one
bricking, harmless = "ffffffdc", "ffffffdd" # difference that decides the refusal.
bricking, harmless = "fffffddc", "fffffddd"
def session(fuses): def session(fuses):
return pbsim.Device(device_bin, elf, mcu, hz, base_hex, page, baud, dump, fuses=fuses) return pbsim.Device(device_bin, elf, mcu, hz, base_hex, page, baud, dump, fuses=fuses)