You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When firmware accidentally reports 0 bytes available for DFU partition, then nRF connect seems to be simply crashing.
This happens with nRF connect 4.28 and (2.26 as well).
I'm developing a custom Rust-based firmware which is using DFU over BLE.
When testing with nRF connect, and attempting to push out application.zip, it crashed after the download and validation for the .dat file was complete and nRF-Connect requested to start pushing the actual firmware payload.
Log file from firmware side starts just after *.dat file has been uploaded and its CRC is going to be calculated:
We're in XXI century and humanity still can't divide by 0.
Fixing this issue is a bit difficult, as there's no clear solution what to do in such case. Should it select the object again, hoping for non-zero value, or abort? Of course, crashing is the worst option.
Anyway, I hope you can fix it on your side, as I'm quite busy with other tasks and this one will have to wait.
We're in XXI century and humanity still can't divide by 0.
Fixing this issue is a bit difficult, as there's no clear solution what to do in such case. Should it select the object again, hoping for non-zero value, or abort? Of course, crashing is the worst option.
Ideally DFU process is aborted and relevant error is bubbled up to the UI as device seems to be unable to accept the firmware.
Anyway, I hope you can fix it on your side, as I'm quite busy with other tasks and this one will have to wait.
Yeah, I already figured this out and "worked it around" from firmware side where I had a typo in the DFU partition length calculation.
When firmware accidentally reports 0 bytes available for DFU partition, then nRF connect seems to be simply crashing.
This happens with nRF connect 4.28 and (2.26 as well).
I'm developing a custom Rust-based firmware which is using DFU over BLE.
When testing with nRF connect, and attempting to push out application.zip, it crashed after the download and validation for the
.dat
file was complete and nRF-Connect requested to start pushing the actual firmware payload.Log file from firmware side starts just after
*.dat
file has been uploaded and its CRC is going to be calculated:And at this point, nRF connect seems to be crashing due unexpected response where
max_size = 0
.The text was updated successfully, but these errors were encountered: