none
Failed to upgrade Sphere to 18.11 RRS feed

  • Question

  • I try to upgrade Sphere firmware to 18.11 and it failed.

    SDK already been updated to 18.11

    Running command from PowerShell as admin. Here is the command output

    PS C:\Home> azsphere device recover
    Starting device recovery. Please note that this may take up to 10 minutes.
    Board found. Sending recovery bootloader.
    Erasing flash.
    Sending images.
    Sending image 1 of 16.
    Sending image 2 of 16.
    Sending image 3 of 16.
    Sending image 4 of 16.
    Sending image 5 of 16.
    Sending image 6 of 16.
    Sending image 7 of 16.
    Sending image 8 of 16.
    Sending image 9 of 16.
    Sending image 10 of 16.
    Sending image 11 of 16.
    Sending image 12 of 16.
    Sending image 13 of 16.
    Sending image 14 of 16.
    Sending image 15 of 16.
    Sending image 16 of 16.
    Finished writing images; rebooting board.
    error: Failed to establish communication with device after recovery. Try unplugging the device and plugging it back in, and verifying communication using 'azsphere device show-attached'. If that fails, try recovering the device again.
    error: Failed to establish communication with device after recovery.
    error: Command failed in 00:04:25.8080641.

    PS C:\Home> azsphere device show-attached
    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:14:17.9526124.

    Anybody has idea how to recover this Sphere unit?


    Tuesday, December 4, 2018 11:25 PM

Answers

All replies

  • Hello Shaoshan,

    Was your device already in use before you tried to upgrade?

    If it was did you follow the steps here? And first you assigned your device to a device group that does not deliver over-the-air application updates?

    Also make sure that the board is showing on the Device Manager. Follow the steps here to download the drivers from Future Technology Devices International (FTDI) if it is not showing.

    Thanks


    Thursday, December 6, 2018 7:49 AM
    Moderator
  • Hi again,

    Can you also please repeat these commands with the -v (verbose) option, and send us the output?

    Thanks

    Thursday, December 6, 2018 3:41 PM
    Moderator
  • Yes. The device has been used before upgraded. I forgot step to move device to system software only group.

    But now I am not able to run this command anymore

    azsphere device update-device-group -d cd037ae5-27ca-4a13-9e3b-2a9d87f9d7bd

    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:21.3607590.

    If I run the azsphere device recover -v, it has exactly the same output as w/o -v, just some additional empty lines.

    ---------

    azsphere device recover -v
    Azure Sphere Utility version 18.11.3.23758
    Copyright (C) Microsoft Corporation. All rights reserved.

    Start time (UTC): Thursday, 06 December 2018 23:12:34
    Starting device recovery. Please note that this may take up to 10 minutes.

    ....

    Finished writing images; rebooting board.
    error: Failed to establish communication with device after recovery. Try unplugging the device and plugging it back in, and verifying communication using 'azsphere device show-attached'. If that fails, try recovering the device again.
    error: Failed to establish communication with device after recovery.
    error: Command failed in 00:04:25.9437814.

    Thursday, December 6, 2018 11:22 PM
  • Thanks Shaoshan,

    Can you also let us know the output for azsphere device show-attached -v ?

    Friday, December 7, 2018 1:35 AM
    Moderator
  • Here is the output of azsphere device show-attached -v

    --------------

    Azure Sphere Utility version 18.11.3.23758
    Copyright (C) Microsoft Corporation. All rights reserved.

    Start time (UTC): Friday, 07 December 2018 21:04:26
    error: An unexpected problem occurred. Please try again; if the issue persists, please refer to aka.ms/azurespheresupport for troubleshooting suggestions and support. DeviceUtilitiesLibrary.DeviceConnectionException: Could not connect to
     the device. Check if your device is connected to the PC. The device may be unresponsive if it is applying an Azure Sphere operating system update; please retry in a few minutes. If this issue persists, try uninstalling and reinstalling
    the Azure Sphere SDK. ---> System.Net.Http.HttpRequestException: An error occurred while sending the request. ---> System.Net.WebException: Unable to connect to the remote server ---> System.Net.Sockets.SocketException: A connection atte
    mpt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 192.168.35.2:443
       at System.Net.Sockets.Socket.InternalEndConnect(IAsyncResult asyncResult)
       at System.Net.Sockets.Socket.EndConnect(IAsyncResult asyncResult)
       at System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Socket s4, Socket s6, Socket& socket, IPAddress& address, ConnectSocketState state, IAsyncResult asyncResult, Exception& exception)
       --- End of inner exception stack trace ---
       at System.Net.HttpWebRequest.EndGetResponse(IAsyncResult asyncResult)
       at System.Net.Http.HttpClientHandler.GetResponseCallback(IAsyncResult ar)
       --- End of inner exception stack trace ---
       at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
       at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
       at System.Net.Http.HttpClient.<FinishSendAsyncBuffered>d__58.MoveNext()
    --- End of stack trace from previous location where exception was thrown ---
       at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
       at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
       at DeviceUtilitiesLibrary.DeviceRestHelper.<RestCallNoBodyAsync>d__19`1.MoveNext()
       --- End of inner exception stack trace ---
       at DeviceUtilitiesLibrary.DeviceRestHelper.<RestCallNoBodyAsync>d__19`1.MoveNext()
    --- End of stack trace from previous location where exception was thrown ---
       at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
       at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
       at DeviceUtilitiesLibrary.DeviceRestHelper.<GetAsync>d__9`1.MoveNext()
    --- End of stack trace from previous location where exception was thrown ---
       at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
       at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
       at DeviceUtilitiesLibrary.DeviceRestHelper.Get[SuccessResponseType](String[] restUrlParts)
       at DeviceUtilitiesLibrary.DeviceManagerBase.<>c__DisplayClass10_0.<.ctor>b__1()
       at System.Lazy`1.CreateValue()
       at System.Lazy`1.LazyInitValue()
       at DeviceUtilitiesLibrary.DeviceSideloadManager.ThrowIfApiNotYetSupported(SemanticVersion supportThreshold)
       at DeviceUtilitiesLibrary.DeviceSideloadManager.GetImages()
       at Microsoft.Azure.Sphere.Tools.AzSphere.DeviceImageListInstalledCommand.GetInstalledComponents(Boolean allComponents, IDeviceSideloadManager deviceSideloadManager)
       at Microsoft.Azure.Sphere.Tools.AzSphere.OsVersionChecker.GetDeviceImages(IDeviceSideloadManager deviceSideloadManager)
       at Microsoft.Azure.Sphere.Tools.AzSphere.OsVersionChecker.GetDeviceOsVersion(ILogger logger, Boolean ignoreWarning)
       at Microsoft.Azure.Sphere.Tools.AzSphere.DeviceShowAttachedCommand.Execute()
       at System.Threading.Tasks.Task`1.InnerInvoke()
       at System.Threading.Tasks.Task.Execute()
    --- End of stack trace from previous location where exception was thrown ---
       at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
       at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
       at CommandLine.SuperCommand`1.<ExecuteAsync>d__0.MoveNext()
    --- End of stack trace from previous location where exception was thrown ---
       at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
       at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
       at CommandLine.EntryPoint.<ExecuteAsync>d__1`2.MoveNext()
    error: Command failed in 00:00:21.4721028.

    Friday, December 7, 2018 9:06 PM
  • Hi can you please double check your power supply Jumpers? The board ships with headers on J2 and J3 for more info please read: MT3620 Power Supply

     
    Monday, December 10, 2018 10:22 PM
    Owner
  • Thanks!

    Just notice that my device lost the jumper for J3. After reconnect the jump, everything works fine.

    Friday, December 14, 2018 11:36 PM
  • My J2 and J3 Jumpers are in the right location.

    When I run azsphere device show-attached -v

    I get a similar stack trace as shown above.  

    Also my Windows Laptop has crashed several times during this troubleshooting.  I checked COM Drivers they are up to date as well.


    aksheik

    Wednesday, December 26, 2018 8:01 PM
  • Alberto,

    I looked through this thread and my device is giving exactly the same error messages presented here, but my jumpers are in the correct position and the COM ports show in the device manager when the board is attached. When I try to recover the images are downloaded but an error occurs on reboot, and similar to here when I run many of the device commands (e.g. show-attached, update-device-group, claim etc.) I get the error below (when I run in verbose the output is exactly as shown on the post above).

    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:21.3205123.

    If the jumpers are connected correctly what's the next step in debugging the problem?

    Friday, February 15, 2019 9:22 PM
  • I have exactly the same problem:

    I received two different MT3620 development kits and have not been able to connect any of them to my PC running 'Windows 10 Enterprise', Version 1803, Build 17134.590.

    When attaching the MT3620 to the computer, it does not find/install the serial driver. I went to the FTDI website and downloaded the driver for 'Windows 10 and it appears to have resolved that issue. When then following the instructions,, I opened the 'Azure Sphere Developer Command Prompt Preview' and attempted to show attached devices, it said:

    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:21.3147525.

    I then performed the azuresphere OS update thinking that may resolve the problem:
    **```
    C:\Users\043674\Documents>azsphere device recover
    Starting device recovery. Please note that this may take up to 10 minutes.
    Downloading recovery images...
    Download complete.
    Board found. Sending recovery bootloader.
    Erasing flash.
    Sending images.
    Sending image 1 of 16.
    Sending image 2 of 16.
    Sending image 3 of 16.
    Sending image 4 of 16.
    Sending image 5 of 16.
    Sending image 6 of 16.
    Sending image 7 of 16.
    Sending image 8 of 16.
    Sending image 9 of 16.
    Sending image 10 of 16.
    Sending image 11 of 16.
    Sending image 12 of 16.
    Sending image 13 of 16.
    Sending image 14 of 16.
    Sending image 15 of 16.
    Sending image 16 of 16.
    Finished writing images; rebooting board.
    error: Failed to establish communication with device after recovery. Try unplugging the device and plugging it back in, and verifying communication using 'azsphere device show-attached'. If that fails, try recovering the device again.
    error: Failed to establish communication with device after recovery.
    error: Command failed in 00:04:29.2063041.

    I checked the COM ports in device manager and everything looks correct--shows the 3 com ports, shows a TAP network driver installed. I verified the Jumper settings are installed correctly and even put a coin cell in just to be sure.  It appears the OS will always update, but never connect and this has happened on 3 separate boards now.

    I went in and checked my network connections because it seems that the TAP-Driver is necessary.  When I did, it shows the TAP Network connection as disabled.  Perhaps this is the issue, but I know of no way to install or enabled the TAP driver.  So I uninstalled everything completely, and reinstalled everything again.  Same results.

    How to resolve this issue?

    Tuesday, March 12, 2019 1:14 PM
  • Hi,

    Can you paste here the result of doing the following commands:

    • azsphere device show-ota-status -v
    • azsphere show-version
    • azsphere device recover -v
    • azsphere device wifi show-status -v

    Thanks!

    Wednesday, March 13, 2019 4:39 PM
    Moderator
  • Hi,

    I have the same error and the Jumpers are set correctly. Please find the logs below.

    There are a couple of messages after flashing the device: 'verbose: Unexpected response from device:'

    Regards

    C:\Users\FlorianWagner(박플로)\Documents>azsphere device show-attached -v
    Azure Sphere Utility version 19.2.4.2632
    Copyright (C) Microsoft Corporation. All rights reserved.
    Start time (UTC): Monday, 18 March 2019 06:56:08
    error: An unexpected problem occurred. Please try again; if the issue persists, please refer to aka.ms/azurespheresupport for troubleshooting suggestions and support. DeviceUtilitiesLibrary.DeviceConnectionException: Could not connect to the device. Check if your device is connected to the PC. The device may be unresponsive if it is applying an Azure Sphere operating system update; please retry in a few minutes. If this issue persists, try uninstalling and reinstalling the Azure Sphere SDK. ---> System.Net.Http.HttpRequestException: An error occurred while sending the request. ---> System.Net.WebException: 원격 서버에 연결할 수 없습니다. ---> System.Net.Sockets.SocketException: 연결된 구성원으로부터 응답이 없어 연결하지 못했거나, 호스트로부터 응답이 없어 연결이 끊어졌습니다 192.168.35.2:443
       위치: System.Net.Sockets.Socket.InternalEndConnect(IAsyncResult asyncResult)
       위치: System.Net.Sockets.Socket.EndConnect(IAsyncResult asyncResult)
       위치: System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Socket s4, Socket s6, Socket& socket, IPAddress& address, ConnectSocketState state, IAsyncResult asyncResult, Exception& exception)
       --- 내부 예외 스택 추적의 끝 ---
       위치: System.Net.HttpWebRequest.EndGetResponse(IAsyncResult asyncResult)
       위치: System.Net.Http.HttpClientHandler.GetResponseCallback(IAsyncResult ar)
       --- 내부 예외 스택 추적의 끝 ---
       위치: System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
       위치: System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
       위치: System.Net.Http.HttpClient.<FinishSendAsyncBuffered>d__58.MoveNext()
    --- 예외가 throw된 이전 위치의 스택 추적 끝 ---
       위치: System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
       위치: System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
       위치: DeviceUtilitiesLibrary.DeviceRestHelper.<RestCallNoBodyAsync>d__19`1.MoveNext()
       --- 내부 예외 스택 추적의 끝 ---
       위치: DeviceUtilitiesLibrary.DeviceRestHelper.<RestCallNoBodyAsync>d__19`1.MoveNext()
    --- 예외가 throw된 이전 위치의 스택 추적 끝 ---
       위치: System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
       위치: System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
       위치: DeviceUtilitiesLibrary.DeviceRestHelper.<GetAsync>d__9`1.MoveNext()
    --- 예외가 throw된 이전 위치의 스택 추적 끝 ---
       위치: System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
       위치: System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
       위치: DeviceUtilitiesLibrary.DeviceRestHelper.Get[SuccessResponseType](String[] restUrlParts)
       위치: DeviceUtilitiesLibrary.DeviceManagerBase.<>c__DisplayClass10_0.<.ctor>b__1()
       위치: System.Lazy`1.CreateValue()
       위치: System.Lazy`1.LazyInitValue()
       위치: DeviceUtilitiesLibrary.DeviceSideloadManager.ThrowIfApiNotYetSupported(SemanticVersion supportThreshold)
       위치: DeviceUtilitiesLibrary.DeviceSideloadManager.GetImages()
       위치: Microsoft.Azure.Sphere.Tools.Common.DeprecatedOsChecker.CheckForDeprecatedOs(ILogger logger)
       위치: Microsoft.Azure.Sphere.Tools.AzSphere.DeviceShowAttachedCommand.Execute()
       위치: System.Threading.Tasks.Task`1.InnerInvoke()
       위치: System.Threading.Tasks.Task.Execute()
    --- 예외가 throw된 이전 위치의 스택 추적 끝 ---
       위치: System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
       위치: System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
       위치: CommandLine.SuperCommand`1.<ExecuteAsync>d__0.MoveNext()
    --- 예외가 throw된 이전 위치의 스택 추적 끝 ---
       위치: System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
       위치: System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
       위치: CommandLine.EntryPoint.<ExecuteAsync>d__1`2.MoveNext()
    error: Command failed in 00:00:21.4622437.
    C:\Users\FlorianWagner(박플로)\Documents>azsphere device show-ota-status -v
    Azure Sphere Utility version 19.2.4.2632
    Copyright (C) Microsoft Corporation. All rights reserved.
    Start time (UTC): Monday, 18 March 2019 06:58:59
    verbose: Reading settings file 'C:\Users\user\AppData\Local\Azure Sphere Tools\settings.json'.
    verbose: ==> Using Azure Active Directory tenant ID: '9066feb3-4808-494b-b62e-e143c4cfdf8b'.
    verbose: ==> Using environment: 'prod'.
    verbose: ==> Using Azure Sphere tenant ID: '55c8b721-46a6-497e-8bc1-355bcb6237ad'.
    error: An unexpected problem occurred. Please try again; if the issue persists, please refer to aka.ms/azurespheresupport for troubleshooting suggestions and support. DeviceUtilitiesLibrary.DeviceConnectionException: Could not connect to the device. Check if your device is connected to the PC. The device may be unresponsive if it is applying an Azure Sphere operating system update; please retry in a few minutes. If this issue persists, try uninstalling and reinstalling the Azure Sphere SDK. ---> System.Net.Http.HttpRequestException: An error occurred while sending the request. ---> System.Net.WebException: 원격 서버에 연결할 수 없습니다. ---> System.Net.Sockets.SocketException: 연결된 구성원으로부터 응답이 없어 연결하지 못했거나, 호스트로부터 응답이 없어 연결이 끊어졌습니다 192.168.35.2:443
       위치: System.Net.Sockets.Socket.InternalEndConnect(IAsyncResult asyncResult)
       위치: System.Net.Sockets.Socket.EndConnect(IAsyncResult asyncResult)
       위치: System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Socket s4, Socket s6, Socket& socket, IPAddress& address, ConnectSocketState state, IAsyncResult asyncResult, Exception& exception)
       --- 내부 예외 스택 추적의 끝 ---
       위치: System.Net.HttpWebRequest.EndGetResponse(IAsyncResult asyncResult)
       위치: System.Net.Http.HttpClientHandler.GetResponseCallback(IAsyncResult ar)
       --- 내부 예외 스택 추적의 끝 ---
       위치: System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
       위치: System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
       위치: System.Net.Http.HttpClient.<FinishSendAsyncBuffered>d__58.MoveNext()
    --- 예외가 throw된 이전 위치의 스택 추적 끝 ---
       위치: System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
       위치: System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
       위치: DeviceUtilitiesLibrary.DeviceRestHelper.<RestCallNoBodyAsync>d__19`1.MoveNext()
       --- 내부 예외 스택 추적의 끝 ---
       위치: DeviceUtilitiesLibrary.DeviceRestHelper.<RestCallNoBodyAsync>d__19`1.MoveNext()
    --- 예외가 throw된 이전 위치의 스택 추적 끝 ---
       위치: System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
       위치: System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
       위치: DeviceUtilitiesLibrary.DeviceRestHelper.<GetAsync>d__9`1.MoveNext()
    --- 예외가 throw된 이전 위치의 스택 추적 끝 ---
       위치: System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
       위치: System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
       위치: DeviceUtilitiesLibrary.DeviceRestHelper.Get[SuccessResponseType](String[] restUrlParts)
       위치: DeviceUtilitiesLibrary.DeviceManagerBase.<>c__DisplayClass10_0.<.ctor>b__1()
       위치: System.Lazy`1.CreateValue()
       위치: System.Lazy`1.LazyInitValue()
       위치: DeviceUtilitiesLibrary.DeviceSideloadManager.ThrowIfApiNotYetSupported(SemanticVersion supportThreshold)
       위치: DeviceUtilitiesLibrary.DeviceSideloadManager.GetImages()
       위치: Microsoft.Azure.Sphere.Tools.Common.DeprecatedOsChecker.CheckForDeprecatedOs(ILogger logger)
       위치: Microsoft.Azure.Sphere.Tools.AzSphere.DeviceShowOtaStatusCommand.<ExecuteAsync>d__1.MoveNext()
    --- 예외가 throw된 이전 위치의 스택 추적 끝 ---
       위치: System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
       위치: System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
       위치: Microsoft.Azure.Sphere.Tools.AzSphere.DeviceShowOtaStatusCommand.<ExecuteAsync>d__0.MoveNext()
    --- 예외가 throw된 이전 위치의 스택 추적 끝 ---
       위치: System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
       위치: System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
       위치: CommandLine.SuperCommand`1.<ExecuteAsync>d__0.MoveNext()
    --- 예외가 throw된 이전 위치의 스택 추적 끝 ---
       위치: System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
       위치: System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
       위치: CommandLine.EntryPoint.<ExecuteAsync>d__1`2.MoveNext()
    error: Command failed in 00:00:21.5347545.
    C:\Users\FlorianWagner(박플로)\Documents>azsphere show-version
    19.02
    Command completed successfully in 00:00:00.3029448.
    C:\Users\FlorianWagner(박플로)\Documents>azsphere device recover -v
    Azure Sphere Utility version 19.2.4.2632
    Copyright (C) Microsoft Corporation. All rights reserved.
    Start time (UTC): Monday, 18 March 2019 07:04:13
    Starting device recovery. Please note that this may take up to 10 minutes.
    verbose: Reading settings file 'C:\Users\user\AppData\Local\Azure Sphere Tools\settings.json'.
    Downloading recovery images...
    verbose: Downloading https://prod.releases.sphere.azure.net/recovery/mt3620an.zip to C:\Users\user\AppData\Local\Temp\AzureSphereRecoveryImages\23df3599-897e-42b7-99af-39fe2d6c9270\mt3620an.zip.
    Download complete.
    verbose: Unzipping C:\Users\user\AppData\Local\Temp\AzureSphereRecoveryImages\23df3599-897e-42b7-99af-39fe2d6c9270\mt3620an.zip to C:\Users\user\AppData\Local\Temp\AzureSphereRecoveryImages\23df3599-897e-42b7-99af-39fe2d6c9270\mt3620an.
    verbose: Adding package Trusted Keystore
    verbose: Adding package Pluton Runtime
    verbose: Adding package Security Monitor
    verbose: Adding package Device Capability
    verbose: Adding package N9 Wifi Firmware
    verbose: Adding package A7 NW loader
    verbose: Adding package NW Device Tree
    verbose: Adding package NW Kernel
    verbose: Adding package NW Root Filesystem
    verbose: Adding package update-cert-store
    verbose: Adding package gatewayd
    verbose: Adding package networkd
    verbose: Adding package azured
    verbose: Adding package rng-tools
    verbose: Adding package 1BL
    verbose: Adding package 1BL
    verbose: Looking for board using device locator 'Sopris cDVB 2.x'
    verbose: Enumerating attached FTDI devices:
    verbose: 0: MSFT MT3620 Std Interface A
    verbose: 1: MSFT MT3620 Std Interface B
    verbose: 2: MSFT MT3620 Std Interface C
    verbose: 3: MSFT MT3620 Std Interface D
    verbose: Did not find attached board using device locator 'Sopris cDVB 2.x'
    verbose: Looking for board using device locator 'MT3620 device'
    verbose: Enumerating attached FTDI devices:
    verbose: 0: MSFT MT3620 Std Interface A
    verbose: 1: MSFT MT3620 Std Interface B
    verbose: 2: MSFT MT3620 Std Interface C
    verbose: 3: MSFT MT3620 Std Interface D
    verbose: Located and opened board using device locator 'MT3620 device'
    Board found. Sending recovery bootloader.
    verbose: Unexpected data while waiting for recovery mode: ECOVERY
    0000362000008A01020A00008FC8C833
    C (44 bytes) - will wait for XMODEM
    verbose: XMODEM sent 16384 bytes, with a max 0 retries per packet
    Erasing flash.
    verbose: Contract version is 2
    Sending images.
    verbose: XMODEM sent 1420 bytes, with a max 0 retries per packet
    Sending image 1 of 16.
    verbose: XMODEM sent 1576 bytes, with a max 0 retries per packet
    verbose: Image sent.
    Sending image 2 of 16.
    verbose: XMODEM sent 29300 bytes, with a max 0 retries per packet
    verbose: Image sent.
    Sending image 3 of 16.
    verbose: XMODEM sent 98644 bytes, with a max 0 retries per packet
    verbose: Image sent.
    Sending image 4 of 16.
    verbose: XMODEM sent 392 bytes, with a max 0 retries per packet
    verbose: Image sent.
    Sending image 5 of 16.
    verbose: XMODEM sent 269980 bytes, with a max 0 retries per packet
    verbose: Image sent.
    Sending image 6 of 16.
    verbose: XMODEM sent 16676 bytes, with a max 0 retries per packet
    verbose: Image sent.
    Sending image 7 of 16.
    verbose: XMODEM sent 16228 bytes, with a max 0 retries per packet
    verbose: Image sent.
    Sending image 8 of 16.
    verbose: XMODEM sent 2426428 bytes, with a max 0 retries per packet
    verbose: Image sent.
    Sending image 9 of 16.
    verbose: XMODEM sent 1741036 bytes, with a max 0 retries per packet
    verbose: Image sent.
    Sending image 10 of 16.
    verbose: XMODEM sent 24576 bytes, with a max 0 retries per packet
    verbose: Image sent.
    Sending image 11 of 16.
    verbose: XMODEM sent 90324 bytes, with a max 0 retries per packet
    verbose: Image sent.
    Sending image 12 of 16.
    verbose: XMODEM sent 491740 bytes, with a max 0 retries per packet
    verbose: Image sent.
    Sending image 13 of 16.
    verbose: XMODEM sent 151764 bytes, with a max 0 retries per packet
    verbose: Image sent.
    Sending image 14 of 16.
    verbose: XMODEM sent 32972 bytes, with a max 0 retries per packet
    verbose: Image sent.
    Sending image 15 of 16.
    verbose: XMODEM sent 16384 bytes, with a max 0 retries per packet
    verbose: Image sent.
    Sending image 16 of 16.
    verbose: XMODEM sent 16384 bytes, with a max 0 retries per packet
    verbose: Image sent.
    verbose: Unexpected response from device:
    verbose: [no data]
    verbose: Line status: OverrunError: False, ParityError: False, FramingError: False, BreakInterrupt: False
    verbose: Modem status: ClearToSend: False, DataSetRead: True, RingIndicator: True, DataCarrierDetect: False
    verbose: Unexpected response from device:
    verbose: [no data]
    verbose: Line status: OverrunError: False, ParityError: False, FramingError: False, BreakInterrupt: False
    verbose: Modem status: ClearToSend: False, DataSetRead: True, RingIndicator: True, DataCarrierDetect: False
    verbose: Unexpected response from device:
    verbose: [no data]
    verbose: Line status: OverrunError: False, ParityError: False, FramingError: False, BreakInterrupt: False
    verbose: Modem status: ClearToSend: False, DataSetRead: True, RingIndicator: True, DataCarrierDetect: False
    Finished writing images; rebooting board.
    error: Failed to establish communication with device after recovery. Try unplugging the device and plugging it back in, and verifying communication using 'azsphere device show-attached'. If that fails, try recovering the device again.
    error: Failed to establish communication with device after recovery.
    error: Command failed in 00:04:31.5057993.
    C:\Users\FlorianWagner(박플로)\Documents>azsphere device wifi show-status -v
    Azure Sphere Utility version 19.2.4.2632
    Copyright (C) Microsoft Corporation. All rights reserved.
    Start time (UTC): Monday, 18 March 2019 07:09:07
    error: An unexpected problem occurred. Please try again; if the issue persists, please refer to aka.ms/azurespheresupport for troubleshooting suggestions and support. DeviceUtilitiesLibrary.DeviceConnectionException: Could not connect to the device. Check if your device is connected to the PC. The device may be unresponsive if it is applying an Azure Sphere operating system update; please retry in a few minutes. If this issue persists, try uninstalling and reinstalling the Azure Sphere SDK. ---> System.Net.Http.HttpRequestException: An error occurred while sending the request. ---> System.Net.WebException: 원격 서버에 연결할 수 없습니다. ---> System.Net.Sockets.SocketException: 연결된 구성원으로부터 응답이 없어 연결하지 못했거나, 호스트로부터 응답이 없어 연결이 끊어졌습니다 192.168.35.2:443
       위치: System.Net.Sockets.Socket.InternalEndConnect(IAsyncResult asyncResult)
       위치: System.Net.Sockets.Socket.EndConnect(IAsyncResult asyncResult)
       위치: System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Socket s4, Socket s6, Socket& socket, IPAddress& address, ConnectSocketState state, IAsyncResult asyncResult, Exception& exception)
       --- 내부 예외 스택 추적의 끝 ---
       위치: System.Net.HttpWebRequest.EndGetResponse(IAsyncResult asyncResult)
       위치: System.Net.Http.HttpClientHandler.GetResponseCallback(IAsyncResult ar)
       --- 내부 예외 스택 추적의 끝 ---
       위치: System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
       위치: System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
       위치: System.Net.Http.HttpClient.<FinishSendAsyncBuffered>d__58.MoveNext()
    --- 예외가 throw된 이전 위치의 스택 추적 끝 ---
       위치: System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
       위치: System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
       위치: DeviceUtilitiesLibrary.DeviceRestHelper.<RestCallNoBodyAsync>d__19`1.MoveNext()
       --- 내부 예외 스택 추적의 끝 ---
       위치: DeviceUtilitiesLibrary.DeviceRestHelper.<RestCallNoBodyAsync>d__19`1.MoveNext()
    --- 예외가 throw된 이전 위치의 스택 추적 끝 ---
       위치: System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
       위치: System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
       위치: DeviceUtilitiesLibrary.DeviceRestHelper.<GetAsync>d__9`1.MoveNext()
    --- 예외가 throw된 이전 위치의 스택 추적 끝 ---
       위치: System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
       위치: System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
       위치: DeviceUtilitiesLibrary.DeviceRestHelper.Get[SuccessResponseType](String[] restUrlParts)
       위치: DeviceUtilitiesLibrary.DeviceManagerBase.<>c__DisplayClass10_0.<.ctor>b__1()
       위치: System.Lazy`1.CreateValue()
       위치: System.Lazy`1.LazyInitValue()
       위치: DeviceUtilitiesLibrary.DeviceSideloadManager.ThrowIfApiNotYetSupported(SemanticVersion supportThreshold)
       위치: DeviceUtilitiesLibrary.DeviceSideloadManager.GetImages()
       위치: Microsoft.Azure.Sphere.Tools.Common.DeprecatedOsChecker.CheckForDeprecatedOs(ILogger logger)
       위치: Microsoft.Azure.Sphere.Tools.AzSphere.DeviceWifiShowStatusCommand.Execute()
       위치: System.Threading.Tasks.Task`1.InnerInvoke()
       위치: System.Threading.Tasks.Task.Execute()
    --- 예외가 throw된 이전 위치의 스택 추적 끝 ---
       위치: System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
       위치: System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
       위치: CommandLine.SuperCommand`1.<ExecuteAsync>d__0.MoveNext()
    --- 예외가 throw된 이전 위치의 스택 추적 끝 ---
       위치: System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
       위치: System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
       위치: CommandLine.SuperCommand`1.<ExecuteAsync>d__0.MoveNext()
    --- 예외가 throw된 이전 위치의 스택 추적 끝 ---
       위치: System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
       위치: System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
       위치: CommandLine.EntryPoint.<ExecuteAsync>d__1`2.MoveNext()
    error: Command failed in 00:00:21.5402184.


    Monday, March 18, 2019 7:12 AM
  • As a reference, adding the troubleshooting done by jflynn_129 : https://github.com/MicrosoftDocs/azure-sphere-issues/issues/86

    bespinfw can you please try the following suggested by jlynn_129?

    "I dug into this further. the problem is the TAP Driver configuration. When the SDK was installed, it was installed on a machine that was running on a virtual network (VPN). The TAP driver incorrectly configured the TAP driver. specifically, I had the "Cisco AnyConnect VPN client" installed. The TAP driver had enabled the Cisco anyConnect Network Access Manager Filter Driver. Once this was disabled, the SDK started working correctly. Hopefully, this will help others. It seems like the TAP driver can be the source of considerable interference."


    Also take a look at this thread: https://social.msdn.microsoft.com/Forums/en-US/b0ad96c4-c707-4c9f-93da-d79a738fa585/faild-to-recover-on-192?forum=azuresphere

    Thank you!

    Tuesday, March 19, 2019 5:21 PM
    Moderator
  • Hello bespinfw,

    Can you please confirm if you are now unblocked and what was the solution?

    Thank you!

    Friday, April 12, 2019 2:00 PM
    Moderator
  • I'm experiencing this problem too. No VPNs installed. Windows 10 Home, update 1803, azsphere version 19.02. After unboxing new dev kit, 'azsphere device recover' finished writing images, rebooting board, "Failed to establish communication with device...."

    Checked power jumpers.


    • Edited by eeCharlie Tuesday, April 16, 2019 8:34 AM typo
    Tuesday, April 16, 2019 8:27 AM
  • Hi eeCharlie,

    If you have went through Troubleshooting steps here as well and were not successful, please file a support request @ https://aka.ms/azsupt and reference this issue in the description. If you do not have access to a support plan, please reach out @ AZCommunity @ microsoft.com with a link to this Issue as well as your subscription ID and we can help get the support ticket opened for this issue.

    Thank you!

    Tuesday, April 16, 2019 12:37 PM
    Moderator
  • Hello,

    We have added troubleshooting steps in the following Doc:

    Troubleshooting installation and setup

    If the troubleshooting steps aren't solving your issue please file a new issue under that same doc.

    Thank you!

    Monday, April 29, 2019 11:29 PM
    Moderator