@sergio-rius Yes, if I find time I'll compile a 16Mhz version

@sergio-rius Today is (if it works) your lucky day

MYSBootloader_1_3_0rc1_8Mhz_CE4_CSN10.hex

@sergio-rius Is there a particular reason why you are using pin 4 for CE - if you can change it back to CE=9 w/o much effort I'd go for that before trying to recompile mysbootloader. The fuses also define the bootloader section size: If the stock bootloader is optiboot the BL section size will be 512 bytes - mysbootloader uses 2048 bytes, hence different fuse settings. More on AVR fuses here: http://www.engbedded.com/fusecalc/

@sergio-rius see the correct fuse settings in the included boards.txt file

@sergio-rius By default CE=9, CSN=10

@phil2020 That's correct - the purpose of this field is to uniquely identify ID requests when several nodes are requesting an ID at the same time (and thus, preventing nodes with same ID assignments). Nodes accept I_ID_RESPONSE messages with either 255 (for backwards compatibility) or the random "token" sent with the I_ID_REQUEST message.

@alexsh1 Yup

@alexsh1 Looks like an RFM69 link issue: a missed ACK from the node after requesting FW block 14000100EB06. Since you are on 2.3.0-alpha it's worthwile testing with 2.2.0 (as we have some ongoing work on the RFMxx drivers). Also, what HW are you using on the gateway?

@alexsh1 Please post your sketch and a full node log to understand what is going on.

@soloam well done! Yes, please go ahead and submit a PR with the necessary changes. I will review it later this week.