also looking at this
docs: clarify runtime status and the owned Pi setup path
#51
2 files
+19
-2
| @@ -47,8 +47,9 @@ profile remains neutral-only. The owned [sensor pipeline](sensors.md), | ||
| 47 | 47 | [navigation](navigation.md) have separate simulation and hardware acceptance gates. |
| 48 | 48 | |
| 49 | 49 | [Diagnostics and replay](diagnostics.md) retain explicit loss and provenance. |
| 50 | [Runtime trust and image staging](runtime-updates.md) preserves initial trust and authenticates offline candidates; | |
| 51 | persistent trust, boot selection and rollback remain required before installation. | |
| 50 | [Runtime trust and image staging](runtime-updates.md) preserves enrolled trust, | |
| 51 | journals verified metadata and prepares owned image candidates. Physical board | |
| 52 | installation, persistent boot selection and recovery require separate qualification. | |
| 52 | 53 | The [library API](api.md) describes behavior extensions. The |
| 53 | 54 | [shared vehicle contract](vehicles.md) covers quadcopter, fixed-wing, ground, |
| 54 | 55 | surface and subsea profiles. [Optional external drivers](drivers.md) have |
| @@ -14,6 +14,22 @@ Keep propellers removed during bench integration. This release receives physical | ||
| 14 | 14 | 4. Validate the camera independently with Raspberry Pi's [AI Camera guide](https://www.raspberrypi.com/documentation/accessories/ai-camera.html) |
| 15 | 15 | or [camera software guide](https://www.raspberrypi.com/documentation/computers/camera_software.html). |
| 16 | 16 | `rpicam-hello --list-cameras` lists detected cameras. The [camera pipeline](camera-tracking.md) now consumes IMX500 frames/detections; its on-device validation remains pending. |
| 17 | ||
| 18 | ## Owned runtime development | |
| 19 | ||
| 20 | Continue with the [owned runtime bench](runtime.md#run-the-native-host-harness), | |
| 21 | using its CMake, C++17 and CTest prerequisites on a development host. The host | |
| 22 | harness exercises the kernel and Pi protocol with synthetic samples and neutral | |
| 23 | outputs. Follow the separate Pico 2 and [sensor bench](sensors.md) guides when | |
| 24 | adding those boards. Pi camera acquisition and physical board measurements still | |
| 25 | need their own on-device validation. ArduPilot and PX4 are optional drivers. | |
| 26 | ||
| 27 | ## Optional flight-controller telemetry | |
| 28 | ||
| 29 | Use this path when you want receive-only telemetry from an independent flight | |
| 30 | controller. It is separate from developing the owned runtime and does not enable | |
| 31 | physical flight commands. | |
| 32 | ||
| 17 | 33 | 5. Install the supported ArduCopter firmware for Pixhawk 6C using an appropriate ground station. |
| 18 | 34 | Connect the autopilot to the Pi over USB using the exact connector on your board, then identify its |
| 19 | 35 | stable `/dev/serial/by-id/...` device. Grant the service account the OS's serial-device permissions. |