Actions
Forum Thread Details
  • Replies 4 replies
  • Subscribers 45 subscribers
  • Views 421 views
  • Users 0 members are here
Related

Unable to initiate First Step with Azure Sphere

qualial

Hello

 

I have got an Avnet Azure sphere device and i got a azure account with AD user

 

I am able to login but not able to create a Tenant even using force option

i tired "show ota status" and even a "device recover" command but am not able to proceed further

 

here is the output from debug port

 

[1BL] BOOT: 70e00000/00000000/01000000

G=469CAB3244F6502949BD44D34684FFF0DF44D404A61CA5651D2555369FBDC6FE3C01F72E385F1A8FBB83D1DDD70D647055447725CC7722AE4D203F4733E6AD9B

[1BL] !! ERROR: capability image is not for this device

D=0ccb5cc0a1ad2c809ddc8fb2ab599db9634b03a6d83d247acdf2613d58387f7675bd5b13260125e3c9c85f8dcf647bbb549df16d2dd7ef6e3f96ce44557089f4,N=d92ccdfb97490ad53d353013607756afc1a1d3378868a89b8f2ce17880c88ce7

[PLUTON] Logging initialized

[PLUTON] Booting application core

 

Please help

  • More details

    >azsphere tenant create -v -f -n  test

    Azure Sphere Utility version 19.5.4.53731

    Copyright (C) Microsoft Corporation. All rights reserved.

     

     

    Start time (UTC): Saturday, 21 September 2019 12:15:19

    verbose: Creating new Azure Sphere tenant with name 'test'.

    verbose: No Azure Sphere tenants found under the selected AAD user.

    verbose: Successfully logged in with the selected AAD user. This authentication will be used for subsequent commands.

    error: The device is not responding. The device may be unresponsive if it is applying an Azure Sphere operating system update; please retry in a few minutes.

    error: Command failed in 00:04:14.7024121.

  • in reply to qualial

    Make sure that you login to your Microsoft AAD account

    azsphere login

    - Are any tenants listed in the response below this command?

     

    Note the following restrictions:

    1) You can create only one tenant per device

    2) Your device can only be claimed once (and this to to a single tenant)

     

    Additional insights on this topic are available via the Microsoft documentation and in the MSDN technical forums, eg.
    https://social.msdn.microsoft.com/Forums/en-US/caea57b7-9f9d-45c6-841b-8a2e718393aa/changing-directory-and-tenant-before…

  • Hello thanks for prompt reply ,

     

    Noting down things i did which finally worked as i noticed there's no guide which lists all these steps in detail

     

    1)Create a New Active Directory User

    2)Provide Global Management Rights to that user and login using azsphere login 

    3)Downloaded Drivers ftd2xx.dll from FTDI website and copy pasted both X86 and X64 dll files to "C:\Program Files (x86)\Azure Sphere Device Communication Service"

    4)Restart Service "Azure Sphere Device Communication Service"

    5)Ensure that Cable i ran on is USB 2.1 and not USB 3.1 port (Not sure why but in spite of board getting detected maybe it has problem with extension cable or USB 3.1 or both .)

    4)Created Tenant and claimed device

    5)Connect to wifi and did device recover to update firmware

    6)Unlocked debug mode using command "azsphere device prep-debug"

    7)Ran the first 3 Avnet Samples (this was helpful as i understood that Board has Problem with WIFI network wpa2 psk maybe ,it does not have problem when i connect it to mobile hotspot)anyways Please run sample and check network connectivity

     

    That's all Folks :-)