Closed mcuee closed 1 year ago
issues from the hex files generated by ATtinyCore
hexls is predominantly meant to work for urclock bootloaders (and soe "classic" optiboot bootloaders). It's likely hexls misreads the top byte in this particular bootloader and thinks it's an urboot 7.3 bootloader. Notwithstanding this issue also found a string concatenation error. hexls mistakenly used +=
instead of .=
Just pushed a commit for the latter.
It is okay now. I think it serves my purposes already even though it may mistakenly show the hex as urboot 7.3, at least there are no error messages already.
mcuee@UbuntuSwift3:~/arduino-1.0.6/hardware/arduino/bootloaders/optiboot_attinycore/hex$
./hexls optiboot_attiny88_8000000UL.hex
594 640 u7.3 ----h---- optiboot_attiny88_8000000UL.hex
I will close this issue now.
Today I encountered some issues from the hex files generated by ATtinyCore. I have no issues with other optiboot bootloaders so far, like those from optiboot_x (MegaCoreX and megaTinyCore) and DxCore.
https://github.com/SpenceKonde/ATTinyCore/tree/v2.0.0-devThis-is-the-head-submit-PRs-against-this/avr/bootloaders/optiboot/source
Just an example: