-
```
The EFUSE byte on m328 and some other chips only has three bits that are
actually used, and there seems to have been some disagreement on how to handle
the unused bits so that "verify" operation…
-
```
The EFUSE byte on m328 and some other chips only has three bits that are
actually used, and there seems to have been some disagreement on how to handle
the unused bits so that "verify" operation…
-
```
The EFUSE byte on m328 and some other chips only has three bits that are
actually used, and there seems to have been some disagreement on how to handle
the unused bits so that "verify" operation…
-
```
The EFUSE byte on m328 and some other chips only has three bits that are
actually used, and there seems to have been some disagreement on how to handle
the unused bits so that "verify" operation…
-
```
The EFUSE byte on m328 and some other chips only has three bits that are
actually used, and there seems to have been some disagreement on how to handle
the unused bits so that "verify" operation…
-
```
The EFUSE byte on m328 and some other chips only has three bits that are
actually used, and there seems to have been some disagreement on how to handle
the unused bits so that "verify" operation…
-
```
I'm trying to compile optiboot with EEPROM support for m328. Enabling BIG_BOOT
results in an error by the linker complaining about a section overlap. Has this
been tested by someone lately?
Wha…
-
```
I'm trying to compile optiboot with EEPROM support for m328. Enabling BIG_BOOT
results in an error by the linker complaining about a section overlap. Has this
been tested by someone lately?
Wha…
-
```
The EFUSE byte on m328 and some other chips only has three bits that are
actually used, and there seems to have been some disagreement on how to handle
the unused bits so that "verify" operation…
-
```
The EFUSE byte on m328 and some other chips only has three bits that are
actually used, and there seems to have been some disagreement on how to handle
the unused bits so that "verify" operation…