element14 Community
element14 Community
    Register Log In
  • Site
  • Search
  • Log In Register
  • About Us
  • Community Hub
    Community Hub
    • What's New on element14
    • Feedback and Support
    • Benefits of Membership
    • Personal Blogs
    • Members Area
    • Achievement Levels
  • Learn
    Learn
    • Ask an Expert
    • eBooks
    • element14 presents
    • Learning Center
    • Tech Spotlight
    • STEM Academy
    • Webinars, Training and Events
    • Learning Groups
  • Technologies
    Technologies
    • 3D Printing
    • FPGA
    • Industrial Automation
    • Internet of Things
    • Power & Energy
    • Sensors
    • Technology Groups
  • Challenges & Projects
    Challenges & Projects
    • Design Challenges
    • element14 presents Projects
    • Project14
    • Arduino Projects
    • Raspberry Pi Projects
    • Project Groups
  • Products
    Products
    • Arduino
    • Avnet Boards Community
    • Dev Tools
    • Manufacturers
    • Multicomp Pro
    • Product Groups
    • Raspberry Pi
    • RoadTests & Reviews
  • Store
    Store
    • Visit Your Store
    • Choose another store...
      • Europe
      •  Austria (German)
      •  Belgium (Dutch, French)
      •  Bulgaria (Bulgarian)
      •  Czech Republic (Czech)
      •  Denmark (Danish)
      •  Estonia (Estonian)
      •  Finland (Finnish)
      •  France (French)
      •  Germany (German)
      •  Hungary (Hungarian)
      •  Ireland
      •  Israel
      •  Italy (Italian)
      •  Latvia (Latvian)
      •  
      •  Lithuania (Lithuanian)
      •  Netherlands (Dutch)
      •  Norway (Norwegian)
      •  Poland (Polish)
      •  Portugal (Portuguese)
      •  Romania (Romanian)
      •  Russia (Russian)
      •  Slovakia (Slovak)
      •  Slovenia (Slovenian)
      •  Spain (Spanish)
      •  Sweden (Swedish)
      •  Switzerland(German, French)
      •  Turkey (Turkish)
      •  United Kingdom
      • Asia Pacific
      •  Australia
      •  China
      •  Hong Kong
      •  India
      •  Korea (Korean)
      •  Malaysia
      •  New Zealand
      •  Philippines
      •  Singapore
      •  Taiwan
      •  Thailand (Thai)
      • Americas
      •  Brazil (Portuguese)
      •  Canada
      •  Mexico (Spanish)
      •  United States
      Can't find the country/region you're looking for? Visit our export site or find a local distributor.
  • Translate
  • Profile
  • Settings
Azure Sphere Guardian 100
  • Products
  • Dev Tools
  • Avnet Boards Community
  • Azure Sphere Guardian 100
  • More
  • Cancel
Azure Sphere Guardian 100
Forum Cannot get the Guardian100 to connect to my PC via USB (suspect driver issue)
  • Forum
  • Documents
  • Files
  • Members
  • Mentions
  • Sub-Groups
  • Tags
  • More
  • Cancel
  • New
Join Azure Sphere Guardian 100 to participate - click to join for free!
Actions
  • Share
  • More
  • Cancel
Forum Thread Details
  • State Verified Answer
  • Replies 5 replies
  • Subscribers 5 subscribers
  • Views 1803 views
  • Users 0 members are here
Related

Cannot get the Guardian100 to connect to my PC via USB (suspect driver issue)

BigG
BigG over 5 years ago

As title suggests, I am having trouble with connecting to Guardian100 via USB cable.

 

Setup so far (as per users guide):

1. Windows10 [tick]

2.Version later than 1607 [tick]

3. Install Azure Sphere SDK [tick]

3.1 The version reported should be 19.09 [tick]

 

Then I had followed this step in the Quick Start Guide:

STEP 3:

Connect the provided cables and power-up Guardian:

- Connect the Ethernet cable from Guardian to the equipment

- Connect USB cable type-A connector to the on-site equipment

- Connect USB cable type-B connector to Guardian

 

Then went onto

STEP 4:

Complete the Microsoft installation instructions to:

- Set up an Azure Sphere account (and subscribe to notifications)

- Claim your device

- Configure Wi-Fi settings of your device

 

I was unable to Claim my device.

 

Within the instructions it informed me that I should have 4 ports showing. I only have 1. I tried installing FTDI drivers directly and tried uninstalling but to no avail. Same thing.

 

Now while writing this query I do note a discrepancy with the Users Guide and the Getting Started guide.

 

I see in the user guide this instruction, which is not in the quick start guide (hence did not follow)

 

8.4     Debug/Programmer FTDI USB Interface Access

 

1) Disconnect all cables from Guardian, unscrew the four screws and remove the enclosure lid 

2) Plug-in a USB cable (type-A to MicroUSB) from the vertically oriented MicroUSB connector on the Guardian PCB, to a spare USB port on the Windows 10 development computer

 

Then in 8.4.1 Windows FTDI USB Driver Installation

 

1) On first-time connection of Guardian to the development computer, the USB drivers should automatically download and install (this can be slow). If drivers do not install automatically,  right-click on the device name in Windows Device Manager and select Update driver. Alternatively, download the drivers from Future Technology Devices International (FTDI), - choose the driver that matches your Windows 10 installation (32- or 64-bit).  Additional assistance on this aspect is available at: https://docs.microsoft.com/en-us/azure-sphere/install/install#connect-the-Secure Edge Module

 

The link above returns page not found (404)

 

 

Finally, 8.4.2 Windows FTDI Interface Verification

 

2) Open Windows Device Manager and confirm the following are listed:  - three new COM ports   (under Ports COM & LPT) - a TAP-Windows Adaptor V9  (under Network Adaptors)

 

image

I am not able to get these 3 showing.

 

Any advice welcomed.

  • Sign in to reply
  • Cancel
  • Fred27
    0 Fred27 over 5 years ago

    Are you familiar with the process of claiming your device when using the Azure Sphere development board? I assume this will be fairly similar. You need to log into Azure and to use the azsphere command line tool.

     

    This is the relevant part of the guide for claiming the development kit: https://docs.microsoft.com/en-us/azure-sphere/install/claim-device

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
  • BigG
    0 BigG over 5 years ago in reply to Fred27

    Yes I am. I cannot get to Step 5 as it fails with a message in the Azure CMD tool telling me that it cannot connect to device as cannot find it.

     

    This is when I am first creating the tenant as per these instructions: https://docs.microsoft.com/en-us/azure-sphere/deployment/create-tenant

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
  • BigG
    0 BigG over 5 years ago

    So, as I suspected (although not initially assumed), the quick start guide is incorrect - I suggest this quick start guide (and probably the user manual too) needs amending

     

    You need to follow these instructions given in the user manual to create a tenant.

     

    As per section 8.4 (Debug/Programmer FTDI USB Interface Access):

     

    1) Disconnect all cables from Guardian, unscrew the four screws and remove the enclosure lid 

    2) Plug-in a USB cable (type-A to MicroUSB) from the vertically oriented MicroUSB connector on the Guardian PCB, to a spare USB port on the Windows 10 development computer

     

    When I followed this step and it gave me the 3 USB ports and allowed me to create my Azure tenant etc.

     

    This all makes sense as you wouldn't normally want this feature accessible from outside the enclosure.

     

    So, it turns out it was not a driver issue, after all.

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Reject Answer
    • Cancel
  • clem57
    0 clem57 over 5 years ago in reply to BigG

    Actually in the MS doc for Azure Sphere they mention a switch that allows creating the tenant without the device. Later the device can update over the air...

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
  • BigG
    0 BigG over 5 years ago in reply to clem57

    I did not pick that up. Nice to know that. Still, you have to be able to communicate with the device via USB in order to upload the WiFi credentials as well. So, not being able to do that was the issue I needed solving.

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
element14 Community

element14 is the first online community specifically for engineers. Connect with your peers and get expert answers to your questions.

  • Members
  • Learn
  • Technologies
  • Challenges & Projects
  • Products
  • Store
  • About Us
  • Feedback & Support
  • FAQs
  • Terms of Use
  • Privacy Policy
  • Legal and Copyright Notices
  • Sitemap
  • Cookies

An Avnet Company © 2025 Premier Farnell Limited. All Rights Reserved.

Premier Farnell Ltd, registered in England and Wales (no 00876412), registered office: Farnell House, Forge Lane, Leeds LS12 2NE.

ICP 备案号 10220084.

Follow element14

  • X
  • Facebook
  • linkedin
  • YouTube