From d54168317a6600825c51389190de487f6a3f1731 Mon Sep 17 00:00:00 2001 From: Ondrej Stanek Date: Mon, 4 Apr 2022 13:27:05 +0200 Subject: [PATCH] Fix lock fuse verification step in the ISP target The fuse bits value has to be prefixed with `0x`, otherwise, avrdude treats it as a filename and the lock fuse write fails. --- optiboot/bootloaders/optiboot/Makefile.isp | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/optiboot/bootloaders/optiboot/Makefile.isp b/optiboot/bootloaders/optiboot/Makefile.isp index 1d792b0..84a3b4e 100644 --- a/optiboot/bootloaders/optiboot/Makefile.isp +++ b/optiboot/bootloaders/optiboot/Makefile.isp @@ -72,7 +72,7 @@ ISPFUSES = -e -u -U lock:w:0x$(LOCKFUSE):m $(EFUSE_CMD) \ # space from accidental SPM writes. Note: "2f" allows boot section to be read # by the application, which is different than the arduino default. # -ISPFLASH = -U flash:w:$(FILENAME) -U lock:w:$(LOCKFUSE):m +ISPFLASH = -U flash:w:$(FILENAME) -U lock:w:0x$(LOCKFUSE):m # There are certain complicated caused by the fact that the default state # of a fuse is a "1" rather than a "0", especially with respect to fuse bits