Possible faulty Azure Sphere device

peterfenn

bwilless

Hi folks, any insights regarding this problem?

Creating a tenant is something done in Azure rather than on the device. Are you sure it's the hardware that's the problem?

In my recent roadtest I tried to describe some of the issues that can crop up when getting started with the device and how to work around them.

AVNET Azure Sphere MT3620 Starter Kit - Review

Hi Peter,

Can you give us more details on the problem you're seeing?  It sounds like maybe your PC is not able to communicate with your device.  Is that what you're encountering?

Have you reviewed and worked through the troubleshooting guide here:http://avnet.me/Azure_Sphere_Install_Troubleshooting.  If not, that's a good place to start. 

Let us know what you find,

Brian

I had a bad cable and got hung up. When I replaced the cable, all the commands work. BTW, are the lights showing up, for instance the blue one?

Glad you found the issue!  The LEDs will not all light up by default.  If you work through the IoT Central Example, blog #3 you can use the IoT Central Settings Tab to toggle all the LEDs. 

Blog #3: http://avnet.me/mt3620-kit-OOB-ref-design-blog-p3

Brian

Thanks for all the suggestions.

I have been through the documentation and the troubleshooting guide suggested by Brian and the guide suggested by Fred but all is setup as suggested.

The issue I have is that the device is now out of the box.

I have setup my AAD properly and also created an account to use with the Global Admin role applied.

When I issue the azsphere login command with that account I get the following which is expected as I haven't created the tenant yet but proves the account is working:

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

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

Command completed successfully in 00:00:10.6725886.

Next I do the logical thing and try to create my tenant but this is what is returned:

error: Failed to create an Azure Sphere tenant with name 'AzureSphere'.

Trace ID: acc4be19-6a9f-4133-9fde-073e92f6100b

error: An unexpected problem occurred. Please try again; if the issue persists, please refer to aka.ms/azurespheresupport for troubleshooting suggestions and support.

error: Command failed in 00:00:19.5623966.

I have tried using names with spaces, without spaces, with quotes and without and tried random names in case I have hit some reserved term.

I have also tried using the force option and added verbose to see if the logging tells me anything.

Nothing results in a different outcome and the logging just gives me a very long winded "400 Bad Request" result.

I can run the command "azsphere dev show-attached" and get a result describing the device ID and its IP so the comms to the device seems good.

If I log into a different Azure account that I know does already have a tenant created and run the following command I have seen Microsoft suggesting tells us if the device has been pre claimed all seems good.

azsphere dev show-ota-status

Your device is running Azure Sphere OS version 19.07.

error: An unexpected problem occurred. Please try again; if the issue persists, please refer to aka.ms/azurespheresupport for troubleshooting suggestions and support.

error: Command failed in 00:00:03.1368024.

Based on Microsofts suggestions it seems this confirms its not claimed.

So what next?

You can only claim a device once and I haven't claimed it anywhere and it seems the above confirms that.

You can only use the device to create one tenant, I haven't created a tenant yet. The account where I had access to a tenant was seeing a tenant created by someone else.

The account with access to a tenant is in a completely different AAD than the one where I'm unable to create a tenant, so different AADs and different accounts.

The reason I suspected hardware is due to MS saying that you can only create a tenant with a device attached and you can only use a device to create a single tenant.

That to me means that something in the devices identity is used to create that tenant and if the device isn't responding properly then that's going to cause a Bad Request response, all supposition but the best I have right now.

I have already run an "azsphere dev recover" to ensure the OS version on the device is up to date and that seems to succeed.

I have checked my AAD config and can see that the 2 Azure Sphere Applications (API and Utility) are listed.

In short I have now run out of places to look and wonder if anyone else can suggest anything or if we think it is a hardware issue does anyone know how Azure Sphere returns work?

Thanks for the detailed response.

Firstly, while logged into each id you used or created, issue:

• azsphere tenant list
• azsphere tenant selected

Then drop in the results here. What we need is the Guid's and names associated with them

Thanks,

Clem

BTW, I worked with multiple devices and learned the hard way how to deal with issues.

For the account with a tenant I get the following:

azsphere tenant list

ID                                   Name

--                                   ----

821b1fe3-aaf7-41bb-9816-ef5b7430124f Emily Sphere 1

azsphere tenant show-selected
Default Azure Sphere tenant ID is '821b1fe3-aaf7-41bb-9816-ef5b7430124f'.

For the account without a tenant I get the following:

azsphere tenant list
warn: No Azure Sphere tenants found under the selected AAD user.
warn: Use 'azsphere login' to change AAD user, or create a new Azure Sphere tenant using 'azsphere tenant create'.
error: You do not have access to any Azure Sphere tenants.
error: Command failed in 00:00:01.3978586.

azsphere tenant show-selected
No default Azure Sphere tenant is selected. If only one Azure Sphere tenant is available
using your current AAD login, it will automatically be used. Otherwise, use this command
to select a default Azure Sphere tenant: 'azsphere tenant select --tenantid <tenant ID>'
Command completed successfully in 00:00:00.3617572.

I would love to get my hands on a few more devices and work through how this all hangs together but when you get a failure to launch on your first device it doesn't inspire you to invest further.

Hopefully we can get over this hurdle and I will procure more devices.

OK, login to the one with the tenant and device attached.

Run this:

azsphere get-support-data --output logs.zip

The log will have debugging information which can show what is true. Post it here and I can interpret it.