-
Notifications
You must be signed in to change notification settings - Fork 41
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Question: In the context of file-uploading and file-downloading what is the enum type of HasReturnCode.GroupReturnCode.group and .rc? #201
Comments
The Android-nRF-Connect-Device-Manager/mcumgr-core/src/main/java/io/runtime/mcumgr/McuManager.java Lines 60 to 76 in 389c600
The |
If the device doesn't support SMP v. 2, the Android-nRF-Connect-Device-Manager/mcumgr-core/src/main/java/io/runtime/mcumgr/McuMgrErrorCode.java Line 24 in 389c600
|
Appreciate the prompt response. Now it all makes sense. Just a quick follow up question or two:
Appreciate any insights! |
Hi, The other group you mentioned aren't supported on Zephyr, thus weren't migrated to SMP V2, so they don't support group errors. |
Cool. By the way what is the group-id of the basic-group ("zephyr-group"). Can I find it somewhere? (pardon me if I'm missing something obvious while reading between the lines) |
https://github.com/NordicSemiconductor/Android-nRF-Connect-Device-Manager/blob/main/mcumgr-core/src/main/java/io/runtime/mcumgr/response/HasReturnCode.java
In our Laerdal.McuMgr bindings-library we need to perform exception-mapping and error-mapping between the Java world and the C# world whenever an error occurs during file-downloading or file-uploading (for example "file not found", "corrupted", etc).
Is it correct to say that in the context of file-uploading and file-downloading any McuMgrErrorException adheres to the following statements?
Likewise in the case of firmware-installation we have the following callbacks-proxy:
Is it correct to say that in the context of firmware-installation any McuMgrErrorException adheres to the following statements?
( I just want to be sure that there isn't some corner case where these integer fields are adhering to some other enums because if this happens our error-mapping and exception-mapping will end up mapping and reporting the wrong kind of error over to the C# world misleading the host-application! )
The text was updated successfully, but these errors were encountered: