Hello!
Recently while performing a BLE firmware update using the mcuMgr Library, the stages of the firmware update are as follows VALIDATE, RESET, and fail on UPLOAD. When I believe the order should be VALIDATE UPLOAD CONFIRM RESET. This has happened both within my project and within the nRF deivce manager test app. In addition to this, I usually receive the no_entry(5) error. I've additionally tried to use the logger suggested by the library, however it isn't compatible with the version of flipper I am using in my mobile project. Are there any known issues that would cause the reset to happen so early into the cycle, causing a failure in the update process?
Thanks in advance!
