none
Failed to upgrade Sphere to 18.11

    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

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
    Owner
  • 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
    Owner
  • 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
    Owner
  • 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