Actions
Forum Thread Details
  • Replies 29 replies
  • Subscribers 48 subscribers
  • Views 2251 views
  • Users 0 members are here
Related

Possible faulty Azure Sphere device

pjestico

I have recently received an Avnet Azure Sphere device and it appears to be faulty.

It has not been claimed or used to create a tenant by me previously however I am unable to create my first tenant

I know the commands are good and have posted the issue with Microsoft but support is slow.

 

Is there a way to determine the cause of the issue and either resolve or replace the device?

Parents

  • After a few email with the hardware vendor and Microsoft I think we have a conclusion.

     

    Microsoft confirmed that the device was not claimed and therefore that ruled that our definitively as the cause of any issues.

    The hardware vendor shipped a new device which arrived today

    I have just tried creating a tenant with that device and it was successful

     

    Therefore it seems it is possible for a device to have some kind of issue that prevents it from creating a tenant.

    How common this could be I have no information on but the suggested approach would be to raise with Microsoft at AzCommunity@microsoft.com and have them confirm the device is not claimed.

    Assuming that's the case go back to the hardware vendor with that confirmation and obtain a replacement.

     

    Hope all of this helps others.

  • in reply to pjestico

    Hi Peter,

     

    It's great to hear that you're finally up and running.  Thank you for posting the final solution and a contact to ask about the device claim status, and thank you for sticking with it.

     

    This is really interesting.  The way I think this all works is that the azsphere utility reads the device ID from the device and uses that for all interactions with the Azure Sphere Security Service (AS3).  I remember that you could read the device ID from your initial device.  I wonder if the device ID was corrupt somehow.

     

    When the Azure Sphere devices are produced at the silicon factory, the private/public keys are generated, by the Pluton subsystem, and the public key (which is also the device ID) is sent to AS3 so it knows that this Azure Sphere device exists.  I wonder if either the manufacturing step corrupted the device ID, or maybe the device ID being read from the device is corrupt so AS3 does not find a match in it's database and errors out.

     

    If you still have the original device I would love to get my hands on it to do some more investigation.  Let me know if you still have it and I can send you a shipping label.

     

    Brian

Reply
  • in reply to pjestico

    Hi Peter,

     

    It's great to hear that you're finally up and running.  Thank you for posting the final solution and a contact to ask about the device claim status, and thank you for sticking with it.

     

    This is really interesting.  The way I think this all works is that the azsphere utility reads the device ID from the device and uses that for all interactions with the Azure Sphere Security Service (AS3).  I remember that you could read the device ID from your initial device.  I wonder if the device ID was corrupt somehow.

     

    When the Azure Sphere devices are produced at the silicon factory, the private/public keys are generated, by the Pluton subsystem, and the public key (which is also the device ID) is sent to AS3 so it knows that this Azure Sphere device exists.  I wonder if either the manufacturing step corrupted the device ID, or maybe the device ID being read from the device is corrupt so AS3 does not find a match in it's database and errors out.

     

    If you still have the original device I would love to get my hands on it to do some more investigation.  Let me know if you still have it and I can send you a shipping label.

     

    Brian

Children