none
Device recover failure - MT3620 RRS feed

  • Question

  • I am unable to recover an MT3620, which does not respond to any commands.

        C:\Users\\Documents>azsphere dev recover -v
        Azure Sphere Utility version 19.5.4.53731
        Copyright (C) Microsoft Corporation. All rights reserved.

    Start time (UTC): Wednesday, 09 October 2019 17:49:02 Starting device recovery. Please note that this may take up to 10 minutes. Downloading recovery images... verbose: Downloading https://prod.releases.sphere.azure.net/recovery/mt3620an.zip to C:\Users\mabeltma.REDMOND\AppData\Local\Temp\AzureSphereRecoveryImages\c2b9fa40-6b8c-4bf1-a2a5-8faeee69cd89\mt3620an.zip. Download complete. verbose: Unzipping C:\Users\mabeltma.REDMOND\AppData\Local\Temp\AzureSphereRecoveryImages\c2b9fa40-6b8c-4bf1-a2a5-8faeee69cd89\mt3620an.zip to C:\Users\mabeltma.REDMOND\AppData\Local\Temp\AzureSphereRecoveryImages\c2b9fa40-6b8c-4bf1-a2a5-8faeee69cd89\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: No SerialSlipToTunService port is set in the registry; defaulting to 56665. verbose: Looking for board using device locator 'MT3620 device' verbose: Located board(s) using device locator 'MT3620 device' Board found. Sending recovery bootloader. verbose: Unexpected data while waiting for recovery mode: (0 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 1976 bytes, with a max 0 retries per packet verbose: Image sent. Sending image 2 of 16. verbose: XMODEM sent 29948 bytes, with a max 0 retries per packet verbose: Image sent. Sending image 3 of 16. verbose: XMODEM sent 102740 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 16740 bytes, with a max 0 retries per packet verbose: Image sent. Sending image 7 of 16. verbose: XMODEM sent 17444 bytes, with a max 0 retries per packet verbose: Image sent. Sending image 8 of 16. verbose: XMODEM sent 2477744 bytes, with a max 0 retries per packet verbose: Image sent. Sending image 9 of 16. verbose: XMODEM sent 1839340 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 98516 bytes, with a max 0 retries per packet verbose: Image sent. Sending image 12 of 16. verbose: XMODEM sent 573660 bytes, with a max 0 retries per packet verbose: Image sent. Sending image 13 of 16. verbose: XMODEM sent 73940 bytes, with a max 0 retries per packet verbose: Image sent. Sending image 14 of 16. verbose: XMODEM sent 37068 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:06:36.4646103.

    I have tried:
     - Uninstalling / reinstalling SDK.
     - Verifying Azure Sphere is the only TAP device on my system.
     - No firewalls are interfering.
     - Another dev box.

    Attaching wireshark to the TAP device, I see no traffic coming from the device.

    Is my device bricked?

    • Edited by Marcus Beltman Wednesday, October 9, 2019 6:13 PM More log.
    Wednesday, October 9, 2019 6:11 PM

All replies