If this would be our situation, it would be a firmware update for our smart outlets in the field. You definitely want to make sure that updates are backwards c

If this would be our situation, it would be a firmware update for our smart outlets in the field. You definitely want to make sure that updates are backwards compatible. We use a mesh and once there was an incompatibility on the mesh protocol. You want to make sure this will never cause trouble. We decided to use another channel all together. Our next update will update the bootloader and radio stack as well. Scary! This is an update that uses multiple intermediate bootloaders so we fall back to a working system at each step. We definitely do not want to have bricked devices out there. https://github.com/naveenspace7/bluenet-bootloader/blob/intermediate-bl-2/intermediate/docs/flowchart.pdf https://github.com/naveenspace7/bluenet-bootloader/blob/inte... We almost didn't find a bug nevertheless. In our older devices there were some programmed with a binary generated by objcopy without the --gap-fill 0xFF flag. It lead to an hardfault in initialization of the new file system. Brrr. https://github.com/crownstone/bluenet/issues/73 https://github.com/crownstone/bluenet/issues/73