Flashing bootloader to Mightyboard about sailfish-mightyboardfirmware

[tinder-danielnewman]

Contact @joachim if you have difficulty with optiboot.

As to changing the fuse bits for the ATmegaBOOT_168_atmega1280.hex bootloader, you should have left the fuse bits unchanged. You should reset them to whatever they were before you started. (Sorry, off the top of my head I do not know the correct fuse bit settings on a Mightyboard Rev G board.)

[nicoco007]

I just read them off another board and I get 0xDA for H (which is what I used when burning ATmegaBOOT_168_1280.hex), 0xF4 for E and 0xFF for L (didn't see anything for lock bits). I don't think that's the issue. That board has the standard bootloader on it (no changes were done since we got it).

[nicoco007]

Now that I think about it, I had set the extended fuse to 0xF5 at some point. Could that have bricked the board? Could mismatched lock bits also do this?

My only other hypothesis at this point is that the programmer isn't working properly (for some reason), but that wouldn't really make sense considering it validates what it wrote.

[nicoco007]

Alright, I just tried running avrdude -C /path/to/avrdude.conf -p m1280 -F -P /dev/cu.usbmodem1451 -U flash:w:ATmegaBOOT_168_atmega1280.hex -c avrisp -e -b 19200 (no changes to fuses, just burn the bootloader) and it's doing the same thing. Any ideas?

(sorry about the spam)

[tinder-danielnewman]

Sorry, no ideas. As an aside, I've never had good luck using the /dev/cu.usbmodemNNNN device variant on a Mac. But then, I also always use real AVR ISP programmers and avoid using an Arduino to do ISP programming. (They typically cannot burn more than 64K and the actual firmware is a few bytes shy of 124K.)

[nicoco007]

Ah, okay, that might be the issue. I'll try on Linux first, and if that doesn't work I guess I'll have to invest in an actual ISP and go from there. Thanks for your help!

[sbts]

@nicoco007 would be good if you can report your results with trying Linux and / or a hardware ISP device