onUpgradFailed gets called but update continues

[lambo81]

The callback:

public void onUpgradeFailed(FirmwareUpgradeManager.State state, McuMgrException error);

gets called. state.toString() is "VALIDATE" and error.getMessage() is "Payload (10 bytes) too long for MTU: 0"

However, the device keeps going through the update process. The next state is "UPLOAD"

[philips77]

Hello,
We also encountered the issue and are looking for a solution. Please, check out https://github.com/NordicSemiconductor/Android-nRF-Connect-Device-Manager for more updates, as this repo has been deprecated.

[philips77]

OK, we pinpointed the issue.
It's the issue in BLE library 2.3. This happens when you are already connected to the device using another client (BluetoothGatt or BleManager), which has requested MTU change. Then, when you connect using McuMgrBleTransport, the onMtuChanged(..) callback gets fired automatically even before the service discovery begins and, as initialization queue has not yet been initialized, if reports the device as ready here: https://github.com/NordicSemiconductor/Android-BLE-Library/blob/1c8339013e678a864302209618435de5707207dd/ble/src/main/java/no/nordicsemi/android/ble/BleManagerHandler.java#L2357

[lambo81]

Wow thank you for your help. I will try this. Incidentally, I looked at the Nordic library but was confused as to whether it supports Zephyr, which is what I’m using. Do you know about that?

…

On Thu, Sep 23, 2021 at 2:42 AM Aleksander Nowakowski < ***@***.***> wrote: OK, we pinpointed the issue. It's the issue in BLE library 2.3. This happens when you are already connected to the device using another client (BluetoothGatt or BleManager), which has requested MTU change. Then, when you connect using McuMgrBleTransport, the onMtuChanged(..) callback gets fired automatically even before the service discovery begins and, as initialization queue has not yet been initialized, if reports the device as ready here: https://github.com/NordicSemiconductor/Android-BLE-Library/blob/1c8339013e678a864302209618435de5707207dd/ble/src/main/java/no/nordicsemi/android/ble/BleManagerHandler.java#L2357 — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#93 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AUWKQ4SKWD3K6H3IAE62BEDUDLY7LANCNFSM5ESYB4UQ> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.

[lambo81]

Oh never mind the last email. I was looking at a different Nordic dfu library than the one you listed.

…

On Thu, Sep 23, 2021 at 6:54 AM Chris Lam ***@***.***> wrote: Wow thank you for your help. I will try this. Incidentally, I looked at the Nordic library but was confused as to whether it supports Zephyr, which is what I’m using. Do you know about that? On Thu, Sep 23, 2021 at 2:42 AM Aleksander Nowakowski < ***@***.***> wrote: > OK, we pinpointed the issue. > It's the issue in BLE library 2.3. This happens when you are already > connected to the device using another client (BluetoothGatt or BleManager), > which has requested MTU change. Then, when you connect using > McuMgrBleTransport, the onMtuChanged(..) callback gets fired > automatically even before the service discovery begins and, as > initialization queue has not yet been initialized, if reports the device as > ready here: > https://github.com/NordicSemiconductor/Android-BLE-Library/blob/1c8339013e678a864302209618435de5707207dd/ble/src/main/java/no/nordicsemi/android/ble/BleManagerHandler.java#L2357 > > — > You are receiving this because you authored the thread. > Reply to this email directly, view it on GitHub > <#93 (comment)>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AUWKQ4SKWD3K6H3IAE62BEDUDLY7LANCNFSM5ESYB4UQ> > . > Triage notifications on the go with GitHub Mobile for iOS > <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> > or Android > <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. > >

[philips77]

Version 0.13.0-beta06 should have this issue fixed. It's now available on Maven Central.