-
Notifications
You must be signed in to change notification settings - Fork 214
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
Obtain device hardware and firmware versions in DFU mode #462
Comments
Hi, |
I'll mark your issue as a feature request. We'll try to add it, but I can't promise any dates. |
@philips77 that sounds great! thanks for the prompt feedback and adding this as a feature request. Is there a way I could get notified if/when that feature is implemented? no rush, just to be aware of it. |
You will be by being subscribed to this issue. |
Has this feature been implemented now? |
Hello, I'm afraid this taks will have to wait much longer, as we are busy with lots of other projects. |
Anyway, thank you for your reply. Wish you a happy life |
DFU Bootloader version (please complete the following information):
Device information (please complete the following information):
Your question
we have an iOS app based on Nordic's nRF Toolbox project (and hence using this library). We were able to:
../nRF5_SDK/nRF5_SDK_17.0.2_d674dde/examples/dfu/secure_bootloader/pca10040_s132_ble/
Question:
We would like to obtain the device hardware and firmware revision to obtain the latest .zip firmware package from the backend.
Is it possible to do that in DFU mode (no buttonless) from the iOS application? and if so, how do we get that information?
ADDITIONAL NOTES:
I've tried exposing the required data by setting this:
#define NRF_DFU_PROTOCOL_REDUCED 0
in:
.../nRF5_SDK_17.0.2_d674dde/examples/dfu/secure_bootloader/pca10040_s132_ble/config/sdk_config.h(1252
which in turn enables a couple of methods (that afaik may be part of the solution to expose the required data):
in:
...nRF5_SDK_17.0.2_d674dde/components/libraries/bootloader/dfu/nrf_dfu_req_handler.c(107)
The text was updated successfully, but these errors were encountered: