none
Over the air provisioning not working, how to troubleshoot? RRS feed

  • Question

  • Hi, I can successfully prep for OTA provisioning using the example app, but the device does not run on reset or reboot.

    How do I troubleshoot?

    Monday, October 29, 2018 4:50 PM

Answers

All replies

  • Besides prep for OTA, did you also follow the steps outlined in Link device to feed ?

    Tuesday, October 30, 2018 1:44 PM
  • I did.

    How can I monitor debug output while in OTA mode?

    What are the network requirements, i.e. my network only allows HTTP/80 and HTTPS/443, no other ports, no other protocols.

    Wednesday, October 31, 2018 6:40 PM
  • Hello, I am also not able to get OTA working on my Azure Sphere development kit. I have tried several ways to link the feed with no success. The latest error I get is: 

    error: An image with the same name ('Mt3620Blink1') or ID ('59846319-09e1-4622-8644-7098b27c6bed') already exists.
    Trace ID: d0dfd3c2-33da-4fac-bec1-9b6f6d550f31
    error: Command failed in 00:00:21.5915114.

    Additionally, when I run - azsphere device image list-installed
    []

    I get no image. Please let me know what I am doing wrong. Thanks,

    Wednesday, October 31, 2018 7:11 PM
  • Hello, I am also not able to get OTA working on my Azure Sphere development kit. I have tried several ways to link the feed with no success. The latest error I get is: 

    error: An image with the same name ('Mt3620Blink1') or ID ('59846319-09e1-4622-8644-7098b27c6bed') already exists.
    Trace ID: d0dfd3c2-33da-4fac-bec1-9b6f6d550f31
    error: Command failed in 00:00:21.5915114.

    Additionally, when I run - azsphere device image list-installed
    []

    I get no image. Please let me know what I am doing wrong. Thanks,

    I had the same problem, you need to edit the app_manifest.json file and assign a new GUID and name.

    That got me to the point of reset and wait for provision, and then nothing happens.

    • Edited by ptr123 Wednesday, October 31, 2018 7:41 PM
    Wednesday, October 31, 2018 7:41 PM
  • Hello ptr123 and Microsoft,

    I am now having the exact same issue as you (prt123). I gotten to the point of setting up my MT3620 for OTA functionality. However, nothing happens on Reset or Restart. I have been through the process several times and still no success. 

    Could the Certified MT3620 board be the problem?

    Should I re-flash the OS?

    I have spent several hours trying to get Azure Sphere to work. So a little assistance would be nice.

    Thanks,

    Thursday, November 1, 2018 3:34 PM
  • Hi Msft, a little help here please?
    Wednesday, November 7, 2018 5:56 PM
  • Hello prt123, 

    It turned out that after executing the >azsphere device link-feed.. command and restarting the MT3620 it can take anywhere from 1 hour to several hours before the OTA update happens - based on my experimentation. 

    I hope this helps.

    Thursday, November 8, 2018 9:47 PM
  • Hi ptr123,

    Can you let us know the output of: azsphere device show-ota-status ?

    Thank you.

    Friday, November 9, 2018 11:13 PM
    Moderator
  • C:\Users\piete\Documents>azsphere device show-ota-status
    The Azure Sphere Security Service is targeting this device with OS version TP4.2.1
    Your device has the expected version of the Azure Sphere OS: TP4.2.1.
    Command completed successfully in 00:00:03.9655957.
    Tuesday, November 13, 2018 5:34 PM
  • Thanks for confirming that you have the correct version TP4.2.1.

    Let me ask some additional info (also applies to Marcus Davis)

    1) I’d like see output of azsphere device image list-targeted.  That shows if OTA is set up correctly to send the app.

    2) If OTA not set up correctly, then I’d also like to see output of  azsphere device show-ota-config.  That shows if the device has a SKU and non-default device group.  If not, perform azsphere device prep-field --newskuname --newdevicegroupname.  Then:

    • Rebuild the app, which creates a new imagepackage with a new image ID, and then (again) perform azsphere device link-feed --newfeedname --dependentfeedid --imagepath.  If you don’t rebuild the app then this retry will fail with ‘image already exists’ error that Marcus reported.
    • Alternatively, if it’s still not working, you can debug via see azsphere device-group feed list -i <device group ID> to show if the device’s device group has a feed, and then azsphere feed list -i <feed id> to show if that feed has an image (set).

    3) If OTA is now/already set up correctly, and you've reset the device afterwards, then it must be problem with wifi/internet access.  Check if azsphere device wifi show-status shows connected.  If so, you should check if wifi actually has access to internet (and not blocked by some proxy).  

    If still struggling, I can suggest further steps on this.

    Thanks!




    Wednesday, November 14, 2018 11:48 AM
    Moderator
  • C:\Users\piete\Documents>azsphere device image list-targeted
    Successfully retrieved the current image set for device with ID '5B7E67444CEDCA5430C20282BB17B1664CBCA9B9CB640ED4A1CEF6B16BACD3DE2E7B72FC47D49E0FB2C12BFE044C9211D06F34699097200911DA70F2606B49E0' from your Azure Sphere tenant:
     --> ID:   [48b245ca-2b23-48ef-b4d2-5638b4606505]
     --> Name: 'ImageSet-Mt3620BlinkPtr1-2018.10.25-13.14.47-07:00'
    Images to be installed:
     --> [ID: 984893e4-2c77-48d3-94a7-c6be867833da]
    Command completed successfully in 00:00:03.6171241.

    C:\Users\piete\Documents>azsphere device show-ota-status
    The Azure Sphere Security Service is targeting this device with OS version TP4.2.1
    Your device has the expected version of the Azure Sphere OS: TP4.2.1.
    Command completed successfully in 00:00:03.7136618.

    C:\Users\piete\Documents>azsphere device show-ota-config
    Retrieved the over-the-air update configuration for device with ID '5B7E67444CEDCA5430C20282BB17B1664CBCA9B9CB640ED4A1CEF6B16BACD3DE2E7B72FC47D49E0FB2C12BFE044C9211D06F34699097200911DA70F2606B49E0':
     --> Device group: 'FieldGroupOTA3' with ID 'ddf856f6-d15c-4740-b831-64d7c9b3fc06'
     --> SKU: '9d606c43-1fad-4990-b207-554a025e0869' of type 'Chip'
     --> SKU: '886fc1bc-363a-4b56-8fba-2ee46f125241' of type 'Product'
    Command completed successfully in 00:00:02.1499722.

    C:\Users\piete\Documents>azsphere device wifi show-status
    SSID                : Draadtang
    Configuration state : enabled
    Connection state    : connected
    Security state      : psk
    Frequency           : 5180
    Mode                : station
    Key management      : WPA2-PSK
    WPA State           : COMPLETED
    IP Address          : 192.168.20.11
    MAC Address         : 2c:f7:f1:08:80:be

    Command completed successfully in 00:00:00.7946581.


    Thursday, November 15, 2018 6:30 PM
  • Hi ptr123,

    Can you upgrade to the latest version 18.11 and try again?

    Thanks!

    Friday, November 16, 2018 5:22 PM
    Moderator
  • I upgraded to 18.11, recompiled per instructions, and still no OTA provisioning.

    How do I debug?

    My network only allows HTTP and HTTPS, no other protocols, what protocol is used for OTA?

    Output:

    C:\Users\piete\Documents>azsphere device image list-targeted
    Successfully retrieved the current image set for device with ID '5B7E67444CEDCA5430C20282BB17B1664CBCA9B9CB640ED4A1CEF6B16BACD3DE2E7B72FC47D49E0FB2C12BFE044C9211D06F34699097200911DA70F2606B49E0' from your Azure Sphere tenant:
     --> Image set ID:   70902f29-c89e-418f-b2eb-43325c6f77b7
     --> Image set name: ImageSet-Mt3620BlinkPtr1-2018.11.19-10.49.03-08:00
    Images to be installed:
     --> Mt3620BlinkPtr1
       --> Image type:   Application
       --> Component ID: d3acaef0-3995-4d63-bfe4-d57739ee7fcb
       --> Image ID:     7339b96a-d47e-40b6-b026-fe154056efc9
    Command completed successfully in 00:00:03.3871336.

    C:\Users\piete\Documents>azsphere device show-ota-status
    Your device is running Azure Sphere OS version 18.11.
    The Azure Sphere Security Service is targeting this device with Azure Sphere OS version 18.11.
    Your device has the expected version of the Azure Sphere OS: 18.11.
    Command completed successfully in 00:00:02.5182244.

    C:\Users\piete\Documents>azsphere device wifi show-status
    SSID                : Draadtang
    Configuration state : enabled
    Connection state    : connected
    Security state      : psk
    Frequency           : 5180
    Mode                : station
    Key management      : WPA2-PSK
    WPA State           : COMPLETED
    IP Address          : 192.168.20.10
    MAC Address         : 2c:f7:f1:08:80:be

    Command completed successfully in 00:00:01.1345188.

    Monday, November 19, 2018 6:54 PM
  • Hi ptr123,

    That detail is important (network only allows HTTP and HTTPS) since update currently runs over Azure Iot Hub which uses the MQTT protocol. Can you please try this on a different network?

    Thank you.

    Wednesday, November 21, 2018 6:53 PM
    Moderator
  • I cannot, having to move to a lab turns this project from an interesting experiment into too much effort.

    When will you support enterprise friendly networks, i.e. HTTPS/443 only, and WPA2 Enterprise / username password?

    Wednesday, November 21, 2018 7:11 PM
  • Hello ptr123,

    May I kindly ask you to a add a new feature request here  and share the link so others can upvote?

    Thank you!

    Monday, December 3, 2018 1:19 PM
    Moderator
  • Done:

    https://feedback.azure.com/forums/915433-azure-sphere/suggestions/36175345-support-for-enterprise-networks-http-s-and-wpa2-e

    • Marked as answer by ptr123 Monday, December 3, 2018 4:23 PM
    Monday, December 3, 2018 4:23 PM
  • Struggling the same way, but I have unrestricted Internet Connection, recreated the feed, rebuild the image...

    azsphere device show-ota-status
    Your device is running Azure Sphere OS version 18.11.
    The Azure Sphere Security Service is targeting this device with Azure Sphere OS version 18.11.
    Your device has the expected version of the Azure Sphere OS: 18.11.
    Command completed successfully in 00:00:03.1985166.

    azsphere device image list-targeted
    Successfully retrieved the current image set for device with ID '0F8ADE345823314A1EE33DBBF6CEC59C6E15B81E5DA8E3ED9AFC05DD9981BA6CD0C9E397E3CC7756B69D456A9EFC9CAEF78BDB915413EDEB07604DDE88CF63BE' from your Azure Sphere tenant:
     --> Image set ID:   c6c29e8b-e7bf-42cc-a01a-35e57abf9b95
     --> Image set name: ImageSet-Mt3620Blink1-2019.01.30-11.08.10+01:00
    Images to be installed:
     --> Mt3620Blink1
       --> Image type:   Application
       --> Component ID: ea976d20-33ad-4453-93fe-7d2af0e0ccc9
       --> Image ID:     eef610fc-d4c6-49b4-a12e-6668b6748490
    Command completed successfully in 00:00:04.0698094.

    azsphere device show-ota-config
    Retrieved the over-the-air update configuration for device with ID '0F8ADE345823314A1EE33DBBF6CEC59C6E15B81E5DA8E3ED9AFC05DD9981BA6CD0C9E397E3CC7756B69D456A9EFC9CAEF78BDB915413EDEB07604DDE88CF63BE':
     --> Device group: 'SDKBoards' with ID 'b0e86b82-b92b-40c7-8c3a-f489cc073155'
     --> SKU: '9d606c43-1fad-4990-b207-554a025e0869' of type 'Chip'
     --> SKU: '30d81df6-7ddd-4220-85cc-54bcf186b204' of type 'Product'
    Command completed successfully in 00:00:02.6360982.

    azsphere device wifi show-status
    SSID                : ----
    Configuration state : enabled
    Connection state    : connected
    Security state      : psk
    Frequency           : 5260
    Mode                : station
    Key management      : WPA2-PSK
    WPA State           : COMPLETED
    IP Address          : ------
    MAC Address         : 2c:f7:f1:08:76:85

    Command completed successfully in 00:00:01.1027637.

    azsphere device image list-installed
    No installed images.
    Command completed successfully in 00:00:01.1950527.


    • Edited by mschl Wednesday, January 30, 2019 11:06 AM
    Wednesday, January 30, 2019 11:04 AM
  • Even after waiting for more than 10 minutes after RESET, does not it change?
    Wednesday, January 30, 2019 12:08 PM
  • Nope, even after several hours

    The only things we see from the device to Internet on the firewall after reset is an HTTP (not S) request to 13.107.4.52 (MSFT)

    • Edited by mschl Wednesday, January 30, 2019 2:04 PM
    Wednesday, January 30, 2019 1:52 PM