Errors during RESET step about mcumgr-android

[saty9]

fixed by increasing the expected swap time but would be helpful if it gave a clearer/ more consistent error message

[bgiori]

Hi @saty9,

Thanks for submitting this issue.

io.runtime.mcumgr.exception.McuMgrException: io.runtime.mcumgr.ble.callback.TransactionTimeoutException: Transaction 2 timed out without receiving a response

There are some bugs in the 0.12.0-beta versions (assuming you are using one of those for faster DFU) with a new implementation of the BLE transport layer. As of now I am still working them out, so you may want to switch to 0.11.0 until the non-beta release gets tagged. If 0.11.0 doesn't work for you please let me know .

io.runtime.mcumgr.exception.McuMgrException: UNKNOWN(-5)

This seems a bit problematic, as there is no code -5. I would suppose that some non-standard data is getting received and parsed out. Does this happen often?

fixed by increasing the expected swap time but would be helpful if it gave a clearer/ more consistent error message

For sure, this is a good callout. I can wrap any exceptions received during the reset step in an exception with additional info about the amount of time waited and a message suggesting increasing the swap time. Should be less confusing for developers.

[philips77]

-5 error may be coming from here.

[saty9]

@bgiori I encountered these errors in 0.11 and tried 0.12 in the hope it would make them go away but they also appeared then too

[bgiori]

-5 error may be coming from here.

That would make sense. Would be worth cleaning up the error message, via wrapping he exception in a failure rather than using the status as an mcumgr error code.

@bgiori I encountered these errors in 0.11 and tried 0.12 in the hope it would make them go away but they also appeared then too

The TransactionTimeoutException is specific to 0.12.0-beta releases and was caused by a bug in one of the early releases. The bug has since been fixed in the most recent 0.12.0-beta4 release.

---

My conclusion is that we need better and more consistent exceptions for some error cases with regards to resets during DFU.