Azure Sphere Demo Build Error

When I follow the example:

<LINK_TEXT text=“http://wiki.seeedstudio.com/Azure_Spher … phere-demo”>http://wiki.seeedstudio.com/Azure_Sphere_MT3620_Development_Kit/#azure-sphere-demo</LINK_TEXT>



to build the following example from Visual Studio 2017:

<LINK_TEXT text=“https://github.com/Seeed-Studio/Azure_S … _Smart_Fan”>https://github.com/Seeed-Studio/Azure_Sphere_Sample_Smart_Fan</LINK_TEXT>



I got the following error:



1>------ Rebuild All started: Project: AzureSphereDemo2, Configuration: Debug ARM ------

1>arm-poky-linux-musleabi-gcc.exe : error : crypt32.lib: No such file or directory

1>arm-poky-linux-musleabi-gcc.exe : error : winhttp.lib: No such file or directory

1>arm-poky-linux-musleabi-gcc.exe : error : Secur32.lib: No such file or directory

1>arm-poky-linux-musleabi-gcc.exe : error : ncrypt.lib: No such file or directory

1>arm-poky-linux-musleabi-gcc.exe : error : Ws2_32.lib: No such file or directory

1>arm-poky-linux-musleabi-gcc.exe : error : Rpcrt4.lib: No such file or directory

1>Done building project “AzureSphereDemo2.vcxproj” – FAILED.

========== Rebuild All: 0 succeeded, 1 failed, 0 skipped ==========



Please advise what I am missing.

Hi, garymok.



Can you build and run the Azure IoT Hub Sample for MT3620 RDB project in Azure Sphere Preview SDK?

<LINK_TEXT text=“https://docs.microsoft.com/en-us/azure- … iot-sample”>https://docs.microsoft.com/en-us/azure-sphere/app-development/azure-iot-sample</LINK_TEXT>

I had success earlier this week (v18.11, I believe). Would you like me to send you screen shots?



Regards.

Hi @garymok, how are you?



Look, that appears that you had not setup properly your environment.

Have you installed the latest Azure Sphere SDK?

And… Have you upgraded your board to the Firmware 18.11?



Mine is working here in the following setup:

  • Visual Studio 2017
  • Azure Sphere SDK 18.11
  • Azure Sphere Kit upgraded to 18.11



    If you have any problem, post it here and I’ll try to help you.



    Best,

    Andre Curvello

Hello Gary,



My two bits, if you please, on a similar issue. My Visual Studio Extensions had not been installed properly when I encountered a set of similar messages.



My fix (since it was a crash-and-burn desktop) was to uninstall the extensions and Visual Studio, reboot and then start the pre-requisite steps in a more deliberate manner as outlined at <LINK_TEXT text=“https://docs.microsoft.com/en-us/azure- … nvironment”>https://docs.microsoft.com/en-us/azure-sphere/app-development/development-environment</LINK_TEXT>



Hope this helps. I would recommend that you use the Azure command line operations to validate your environment because after attaining success there, the samples worked flawlessly for me.



Regards.

Can you build and run the Azure IoT Hub Sample for MT3620 RDB project in Azure Sphere Preview SDK?

Have you ever tried cartoon movie and TV shows in your Android Mobile phone?

You can easily give access to Cartoon HD for free and enjoy all the latest movies and TV shows for free

I have this same issue. Did you ever find a resolution?

:slight_smile: Can you build and run the Azure IoT Hub Sample for MT3620 RDB project in Azure Sphere Preview SDK?

thanx for share

I would recommend that you use the Azure command line operations to validate your environment because after attaining success there, the samples worked flawlessly for me.

Solution
Follow these steps to manually revert the driver for any non-Azure Sphere devices to its previous version:

In Device Manager, select the non-Azure Sphere device (Another FTDI Quad GZ in the example), then right-click and select Update driver.

In Update Drivers, select Browse my computer for driver software.

browse my computer for drivers

Select Let me pick from a list of available drivers on my computer.

let me pick

Select USB Serial Converter B driver from the list, then click Next.

usb serial converter b

Click Close in the confirmation window.

Device Manager should show Port B for the other FTDI device as USB Serial Converter B, which indicates that it uses the official FTDI driver. The driver for the MT3620 remains MSFT MT3620 Std Interface.

Regards,
Rachel Gomez