Aircraft Distro MCUs Unresponsive/ Aircraft Does not Turn ON
Background
Section titled “Background”This failure most often occurs after a failed firmware update leaves one or both of the distro MCUs without a main app, and because they control the power state of the rest of the zip this can cause strange behavior.
Firmware Note
Section titled “Firmware Note”Aircraft firmware updates detect distro app states and abort the update[1] if the system cannot safely proceed with at least one distro enabling power to the Aircraft (computes). In most cases, this will prevent the Aircraft from powering down if update errors are encountered. This behavior allows firmware deploy retries without requiring the Aircraft to be removed from the Dock for maintenance.
[1] If neither distro app is detected, the update will proceed as it assumes that the update is running from a smart cart for maintenance or recovery.
Troubleshooting Steps
Section titled “Troubleshooting Steps”graph TD
connect-the-aircraft-to-a-smart-cart-se["<small><b>Step 1</b></small><br/>Action: Connect the Aircraft to a smart cart...."]
attempt-to-power-on-the-aircraft-power{"<small><b>Step 2</b></small><br/>Question: Attempt to power ON the Aircraft Po..."}
are-the-distro-mcus-reachable-use-ping{"<small><b>Step 3</b></small><br/>Question: Are the distro MCU’s reachable Use ..."}
use-rpc-cli-i-fe80-20-enp3s0-casa-gett["<small><b>Step 4</b></small><br/>Action: Use rpc-cli -i fe80::20%enp3s0 casa ..."]
escalate-to-p2-firmware-power-on-call-2{{"<small><b>Step 5</b></small><br/>Escalation: Escalate to P2 Firmware Power On Call."}}
escalate-to-p2-firmware-power-on-call{{"<small><b>Step 6</b></small><br/>Escalation: Escalate to P2 Firmware Power On Call."}}
manually-flash-the-main-app-to-the-dist["<small><b>Step 7</b></small><br/>Action: Manually flash the main app to the di..."]
modify-the-firmware-version-to-the-lates{"<small><b>Step 8</b></small><br/>Question: Modify the firmware version to the la..."}
the-aircraft-may-return-to-service("<small><b>Step 9</b></small><br/>Reference: The Aircraft may return to service.")
escalate-to-p2-firmware-power-on-call-3{{"<small><b>Step 10</b></small><br/>Escalation: Escalate to P2 Firmware Power On Call."}}
connect-the-aircraft-to-a-smart-cart-se --> attempt-to-power-on-the-aircraft-power
attempt-to-power-on-the-aircraft-power -->|Yes| are-the-distro-mcus-reachable-use-ping
attempt-to-power-on-the-aircraft-power -->|No| escalate-to-p2-firmware-power-on-call
are-the-distro-mcus-reachable-use-ping -->|Yes| use-rpc-cli-i-fe80-20-enp3s0-casa-gett
are-the-distro-mcus-reachable-use-ping -->|No| escalate-to-p2-firmware-power-on-call-2
use-rpc-cli-i-fe80-20-enp3s0-casa-gett --> manually-flash-the-main-app-to-the-dist
manually-flash-the-main-app-to-the-dist --> modify-the-firmware-version-to-the-lates
modify-the-firmware-version-to-the-lates -->|Yes| the-aircraft-may-return-to-service
modify-the-firmware-version-to-the-lates -->|No| escalate-to-p2-firmware-power-on-call-3
style connect-the-aircraft-to-a-smart-cart-se fill:#dcfce7,stroke:#22c55e,color:#14532d
style attempt-to-power-on-the-aircraft-power fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style are-the-distro-mcus-reachable-use-ping fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style use-rpc-cli-i-fe80-20-enp3s0-casa-gett fill:#dcfce7,stroke:#22c55e,color:#14532d
style escalate-to-p2-firmware-power-on-call-2 fill:#fef3c7,stroke:#f59e0b,color:#78350f
style escalate-to-p2-firmware-power-on-call fill:#fef3c7,stroke:#f59e0b,color:#78350f
style manually-flash-the-main-app-to-the-dist fill:#dcfce7,stroke:#22c55e,color:#14532d
style modify-the-firmware-version-to-the-lates fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style the-aircraft-may-return-to-service fill:#f3e8ff,stroke:#a855f7,color:#581c87
style escalate-to-p2-firmware-power-on-call-3 fill:#fef3c7,stroke:#f59e0b,color:#78350f Hover or focus a block to preview it. Select the block to keep the preview open.
ping_devices to check)?rpc-cli -i fe80::20%enp3s0 casa GetTargetInfo to verify that distro_a is staying in its bootloader.fw-update -i fe80::20%enp3s0 update -a distro_a -p hw.main -s $FW_VERSION fw-update -i fe80::21%enp3s0 update -a distro_b -p hw.main -s $FW_VERSION Resolution note
This plaintext block is ready to paste into the Resolution Note field on the ZERP issue you're working. The permalink below gives engineering review access to the full step-by-step timeline including any back-navigation; share it if the case needs a deeper look.
Permalink:
Session is too large to fit in a URL. Use Download session JSON to share the timeline out-of-band.
Did this guide help you get unblocked?
Open suggestions
There are no open suggestions.
Open pull requests
There are no open pull requests.