SOFTWARE_CONFIGURATION_BOOTLOADER_UNFLYABLE
Applicable alarms (1)
Likely outcomes — click to expand
Based on 1 missions where this alarm fired in the last 90 days as of 2026-10-13
Aggregated from fleet operations and refreshed daily. Individual outcomes may vary by site and configuration.
Background
Section titled “Background”This alarm is set because the vehicle went through a Jetpack 6 Ziplinux upgrade. The alarm indicates that the OTA failed partially and left the vehicle in a bad state.
The Aircraft must not be cleared to fly under any circumstances while this alarm is present or after it has been observed for this event.
Troubleshooting Steps
Section titled “Troubleshooting Steps”graph TD
do-not-clear-the-aircraft-to-fly["<small><b>Step 1</b></small><br/>Action: Do not clear the Aircraft to fly unde..."]
escalate-to-p2-embedded-linux-on-call{{"<small><b>Step 2</b></small><br/>Escalation: Immediately escalate to P2 Embedded L..."}}
do-not-clear-the-aircraft-to-fly --> escalate-to-p2-embedded-linux-on-call
style do-not-clear-the-aircraft-to-fly fill:#dcfce7,stroke:#22c55e,color:#14532d
style escalate-to-p2-embedded-linux-on-call fill:#fef3c7,stroke:#f59e0b,color:#78350f Hover or focus a block to preview it. Select the block to keep the preview open.
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.