question

JamesHiggins-7505 avatar image
0 Votes"
JamesHiggins-7505 asked ·

Azure Sphere module stops responding to CLI and fails recovery when switching from "development" to "cloud test" mode.

I have encountered this issue with two Azure Sphere modules.

Both units entered a state where they would not respond to most CLI commands and would return the message "The device is not responding. The device may be unresponsive if it is applying an Azure Sphere operating system update; please retry in a few minutes."

Waiting and power cycling did not help.

They did respond to the "azsphere device recovery..." command, fully downloading the images, but then would fail on the final "reboot".

Both units got into this state when switching from "development" mode to "cloud test" mode.

The first unit was recovered to a functioning state by running a recovery command and specifying an appdev capability file, then running a subsequent
recovery command without the capability file specified.

However, the second unit is unrecoverable even with the technique used for the first unit.

Here is the last bit of output from the unit that is still stuck:

C:> azsphere device recover --capability appdevelopment-82C3B2AA.cap --debug --verbose
...
Received RecoveryComplete
Finished writing images; rebooting board.
Entering state: RebootToNormalMode
Read from Pluton UART:
[1BL] BOOT: 380af000/00000001/02000000
G=a7e86668355ba4d115165ea00e8c66794450cb5a538f28c931f763e6354deeaa30478f9c27397e73a5acbaf48b6c58193c92c217e7c0752ae596645ee0c87012
[1BL] WARNING: Hash boot man: backup
[1BL] WARNING: Hash boot man: backup
D=82c3b2aaf53b6aabbdf33cb33f074dd363c26ff6f509c385a04f7aae15017c81b0a87ad684a6d90cc46a0430482d48ba9659c32b34bbc086547bdc9b995ba3a6,N=f919a598c8941b1451440221a28daeaf630aa55dc748ed58c8c251c1e3793333
[PLUTON] Logging initialized
[PLUTON] Booting HLOS core

505 bytes:
0000 : 5B 31 42 4C 5D 20 42 4F 4F 54 3A 20 33 38 30 61
0010 : 66 30 30 30 2F 30 30 30 30 30 30 30 31 2F 30 32
0020 : 30 30 30 30 30 30 0D 0A 47 3D 61 37 65 38 36 36
0030 : 36 38 33 35 35 62 61 34 64 31 31 35 31 36 35 65
0040 : 61 30 30 65 38 63 36 36 37 39 34 34 35 30 63 62
0050 : 35 61 35 33 38 66 32 38 63 39 33 31 66 37 36 33
0060 : 65 36 33 35 34 64 65 65 61 61 33 30 34 37 38 66
0070 : 39 63 32 37 33 39 37 65 37 33 61 35 61 63 62 61
0080 : 66 34 38 62 36 63 35 38 31 39 33 63 39 32 63 32
0090 : 31 37 65 37 63 30 37 35 32 61 65 35 39 36 36 34
00A0 : 35 65 65 30 63 38 37 30 31 32 0D 0A 5B 31 42 4C
00B0 : 5D 20 57 41 52 4E 49 4E 47 3A 20 48 61 73 68 20
00C0 : 62 6F 6F 74 20 6D 61 6E 3A 20 62 61 63 6B 75 70
00D0 : 0D 0A 5B 31 42 4C 5D 20 57 41 52 4E 49 4E 47 3A
00E0 : 20 48 61 73 68 20 62 6F 6F 74 20 6D 61 6E 3A 20
00F0 : 62 61 63 6B 75 70 0D 0A 44 3D 38 32 63 33 62 32
0100 : 61 61 66 35 33 62 36 61 61 62 62 64 66 33 33 63
0110 : 62 33 33 66 30 37 34 64 64 33 36 33 63 32 36 66
0120 : 66 36 66 35 30 39 63 33 38 35 61 30 34 66 37 61
0130 : 61 65 31 35 30 31 37 63 38 31 62 30 61 38 37 61
0140 : 64 36 38 34 61 36 64 39 30 63 63 34 36 61 30 34
0150 : 33 30 34 38 32 64 34 38 62 61 39 36 35 39 63 33
0160 : 32 62 33 34 62 62 63 30 38 36 35 34 37 62 64 63
0170 : 39 62 39 39 35 62 61 33 61 36 2C 4E 3D 66 39 31
0180 : 39 61 35 39 38 63 38 39 34 31 62 31 34 35 31 34
0190 : 34 30 32 32 31 61 32 38 64 61 65 61 66 36 33 30
01A0 : 61 61 35 35 64 63 37 34 38 65 64 35 38 63 38 63
01B0 : 32 35 31 63 31 65 33 37 39 33 33 33 33 0D 0A 5B
01C0 : 50 4C 55 54 4F 4E 5D 20 4C 6F 67 67 69 6E 67 20
01D0 : 69 6E 69 74 69 61 6C 69 7A 65 64 0D 0A 5B 50 4C
01E0 : 55 54 4F 4E 5D 20 42 6F 6F 74 69 6E 67 20 48 4C
01F0 : 4F 53 20 63 6F 72 65 0D 0A

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.
Failed to establish communication with device after recovery.
Entering state: FailedToRebootToNormalMode
Command completed in 00:05:26.3826146.
cli.azure.cli.core.util :

Event: Cli.PostExecute [<function AzCliLogging.deinit_cmd_metadata_logging at 0x03BD4C00>, <function CompleterCache.invalidate_cache at 0x041D1468>]
az_command_data_logger : exit code: 2
Azure Sphere Utility version 21.2.1.28749
Command ran in 326.805 seconds (init: 0.241, invoke: 326.565)

I have run the recovery command 15-20 times without success.

The CLI is able to successfully communicate to other Azure Sphere modules using the same exact hardware setup. So it is not my PC, drivers, cables, etc.

Q: Is this a known issue?
Q: Is there another recovery sequence that might be more successful?

azure-sphere
· 1
10 |1000 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

We are looking into this issue and update the status as earliest.

0 Votes 0 ·

0 Answers