none
Faild to recover on 19.2 RRS feed

  • Question

  • I bought a new Azure Sphere MT3620 to evaluate if it is usable for commercial projects.

    I followed the instructions:

    - installed sdk and TAP

    - started device recover

    when I try to recover I alway get the following error.

    I already reinstalled SDK and USB Serial Converters. Still fails.

    Here the output:

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

    Start time (UTC): Tuesday, 19 February 2019 12:51:41
    Starting device recovery. Please note that this may take up to 10 minutes.
    verbose: Reading settings file 'C:\Users\...\AppData\Local\Azure Sphere Tools\settings.json'.
    Downloading recovery images...
    verbose: Downloading https://prod.releases.sphere.azure.net/recovery/mt3620an.zip to C:\Users\...\AppData\Local\Temp\AzureSphereRecoveryImages\...\mt3620an.zip.
    Download complete.
    verbose: Unzipping C:\Users\...\AppData\Local\Temp\AzureSphereRecoveryImages\...\mt3620an.zip to C:\Users\...\AppData\Local\Temp\AzureSphereRecoveryImages\...\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: [device opened by another process]
    verbose: 1: MSFT MT3620 Std Interface B
    verbose: 2: MSFT MT3620 Std Interface C
    verbose: 3: [device opened by another process]
    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:  (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 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
    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:39.8000821.

    - How should the tap configuratuion be? I see 2 tap-windows-adapters: Ethernet3 and Ethernet4. None of them is currently connected or bridged. Some more details about the expected configuration would be helpful.

    - Is there a possibility to downgrade to a previous version say 18.11.2 of the sdk?


    • Edited by mawe81 Tuesday, February 19, 2019 2:02 PM details
    Tuesday, February 19, 2019 1:15 PM

Answers

  • I was able to solve the problem by uninstalling the SDK (repair did not work) and removing al TAP devices.

    It looks like there's a problem if AzureSphere is not on the first TAP device.

    See my blogpost



    • Marked as answer by mawe81 Tuesday, February 19, 2019 3:03 PM
    • Edited by mawe81 Wednesday, March 13, 2019 4:12 PM
    Tuesday, February 19, 2019 3:03 PM