To future-proof BCMP/comms layer protocol update incompatibility, we are adding a NVM Config force flag to enable users to set dfu_confirm to 0, which will allow the DFU client to autoconfirm the update without the need for an ACK back to it's DFU host.
Tested on BM SOFT:
Downgrade bridge + mote to v0.9.1
Set the "dfu_confirm" sys config on the mote to 0
update mote to new firmware
See that the nodes can't quite communicate properly (on soft the pubsub still works for some reason??)
But the heartbeat and topo is breaking
update bridge to new firmware
profit
Tested that in the case dfu_confirm is absent, the image reverts.
Remember to reset the
dfu_confirm config between attempts
A side effect of disabling confirm that when the update completes, the host will get timeout error on it's end, even though the update was successfull
To future-proof BCMP/comms layer protocol update incompatibility, we are adding a NVM Config force flag to enable users to set
dfu_confirmto0, which will allow the DFU client to autoconfirm the update without the need for an ACK back to it's DFU host.Tested on BM SOFT:
Tested that in the case
dfu_confirmis absent, the image reverts.Remember to reset the
dfu_confirmconfig between attemptsA side effect of disabling confirm that when the update completes, the host will get timeout error on it's end, even though the update was successfull