• State Not Answered
  • Replies 19 replies
  • Subscribers 70 subscribers
  • Views 1774 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 319473
Options

NEED HELP WITH FOTA VIA DEVICE PROVISIONING ON MY NRF7002DK - AZURE FOTA - IOT HUB

overflow

Hello, I'm trying to do the fota via azure IoT hub, except I can't, I don't know if I'm doing it wrong because I followed the doc   Azure FOTA  https://shorturl.at/fsAJ1 ainsi que  Azure IoT Hub https://shorturl.at/eoT57 , maybe I missed something.

sdk 2.5.99-dev1

I would like to add this, when try to download the zephyr.bin on my azure

<err> download_client: Unable to connect, errno 113
[00:00:44.678,955] <err> fota_download: Download client error
[00:00:44.689,544] <err> azure_fota: FOTA download failed

If you need more information, I'm open, thank you, I hope to find a solution :)

  • 0

    At actif we are also experiencing this problem with the Nordic documentation not being very clear about how to use the FOTA with azure IoT hub.

    We also have a working DPS & Telemetry with IoT Hub. But when we want to add the FOTA, the information provided seem unclear to us and we seem to be bounced between the library and the sample for more information, but none have that helped us understand what we need to do.

  • 0

    Hi,

    When you repeatedly edit the ticket, it makes it hard for us to follow the history and development of the issue.

    In one of your previous images, it looked like you were able to download the new image. Has that changed, or do I remember the old image incorrectly?

    113 is ECONNABORTED, with the explanation "Software caused connection abort". My first guess is that something is wrong with the credentials you have written to the device.

    Best regards,

    Didrik

  • 0 in reply to Didrik Rokhaug

    Hello, thank you for your follow-up and your advice, I'm sorry for that.

    I made a mistake in my analysis, until now I can't download the .bin from my blobstorage.

    I'm still exploring different avenues, exactly I've been thinking about the certificate,

    I got the error ECONNABORTED 113.
    I saw its correspondence in the errno.h "/* Software caused connection abort */",
    I modified my CONFIG_AZURE_FOTA_SEC_TAG which was 11, now I set it to 1, because despite the fact that it was 11, in my terminal I saw [00:00:35.305,633] <inf> download_client: Setting up TLS credentials, sec tag count 1.

    After setting my CONFIG_AZURE_FOTA_SEC_TAG=1, I get a new error which is:
    [ 00:00:35.374,603] <err> download_client: Unable to connect, errno 2.

    in the errno.h it's defined as  #define ENOENT 2 /* No such file or directory */

  • 0 in reply to Didrik Rokhaug

    Hi Didrik,

    I hope this message finds you well. I'm reaching out to discuss the Azure IoT Hub + DPS + FOTA sample that your team provided. We appreciate your efforts in sharing this resource. However, we're encountering some challenges in implementing it effectively.

    Our team has been diligently working to follow the sample, particularly regarding the use of DPS as the provisioning point and the FOTA for firmware updates. Unfortunately, the current documentation doesn't seem to provide the level of detail necessary for us to replicate the process successfully.

    To enhance our understanding and expedite the deployment, it would be immensely helpful if you could confirm that someone from your team has successfully tested this sample. Could you try it yourself? Moreover, could you provide a step-by-step guide detailing the Azure configurations and processes your team followed? Specific areas where we require further clarity include:

    1. The Kconfig settings necessary for integrating with DPS and FOTA.
    2. The exact Azure certificates used in the setup, what certificate and rootCA were used where.
    3. The configurations related to CONFIG_FOTA_SEC_TAG, CONFIG_MQTT_HELPER_SEC_TAG, and CONFIG_MQTT_HELPER_SECONDARY_SEC_TAG.

    Given the current state of the documentation, I'm concerned that others attempting to use your sample might face similar roadblocks. Comprehensive guidance would not only benefit our team but also enhance the overall utility of the sample for everyone involved.

    If providing such detailed information is not feasible, we might consider developing a custom wrapper around the Azure library to meet our needs. However, I'm optimistic that with your team's expertise and support, we can effectively utilize the existing resources.

    Thank you in advance for your attention to this matter. I look forward to your response and any additional insights your team can offer to facilitate a smoother implementation process on our end.

    Best regards,
    Actif

  • 0 in reply to overflow

    Finally I put back the CONFIG_AZURE_FOTA_SEC_TAG=11 or 10, cause thats what my cert are link to.  I still have the error ECONNABORTED 113. These are the tags I use to communicate with my dps and they work fine, but why don't they work when I want to do the fota? any ideas?

Related