Fixing this issue is complicated by the unfortunate update of the pi/18 gadget for armhf to 256MB boot partition. Some devices in the field have 128MB partitions, other have 256MB, depending on just when the particular image was built.
This prevents us from updating the gadget / bootloader as the sanity check logic will refuse this update.
The second issue is that updating kernel and gadget separately is impossible. Updating the boot assets manually shows that the old kernel (revision 44) cannot boot correctly with gadget 74 (current stable). This requires the ability to update those in sync.
Fixing this issue is complicated by the unfortunate update of the pi/18 gadget for armhf to 256MB boot partition. Some devices in the field have 128MB partitions, other have 256MB, depending on just when the particular image was built.
This prevents us from updating the gadget / bootloader as the sanity check logic will refuse this update.
The second issue is that updating kernel and gadget separately is impossible. Updating the boot assets manually shows that the old kernel (revision 44) cannot boot correctly with gadget 74 (current stable). This requires the ability to update those in sync.