Question 1

Do you need access to our source code?

Accepted Answer

No. Polaris runs on its own server, deploys its own client to the target, and validates the board through Polaris OS and Polaris HAL. No source-code access, no changes to your build, CI, or version control. Your IP stays with your team.

Question 2

Will this interfere with our development workflow?

Accepted Answer

No. The stack runs on its own server, against its own target client on the DUT, on its own cadence. It does not share a build system, CI pipeline, or version control history with your development. Both run concurrently against the same board.

Question 3

Which target operating systems are supported?

Accepted Answer

FreeRTOS for bare-metal and RTOS targets; Yocto-based Linux for embedded Linux targets. Transport matches the target: FlatBuffers on FreeRTOS bare-metal, gRPC on Yocto Linux. Porting to a new SoC means writing the HAL — everything above carries forward.

Question 4

How does environmental testing work?

Accepted Answer

Environmental conditions are authored as test parameters and dispatched to the server, which coordinates the run against the device. Monitoring mode streams telemetry as conditions ramp. Event-based mode fires when a configured threshold is crossed. Every condition, reading, and trigger event is persisted to the records store.

Question 5

What does the audit trail look like?

Accepted Answer

Every run record includes operator identity and timestamps on every state change, firmware and schema versions snapshotted at run start, three-stamp timing on every cross-boundary measurement, and explicit drop counts. The store is append-only — invalidations are recorded with a reason, never silent deletes. Records are reviewable in the Web UI and exportable as machine-readable JSON or PDF.

Question 6

How do the records map to ISO 26262, DO-178C, IEC 62304, and IEC 61508?

Accepted Answer

ISO 26262: fault-injection results, coverage records, and test-to-requirement linkage. DO-178C / DO-254: structural test artifacts and repeatable build-and-run records. IEC 62304: lifecycle-aligned logs and SOUP mitigation records. IEC 61508: functional-safety integrity records and environmental-stress test records.

Question 7

Our board is not one of your six in-house platforms. Can you still help?

Accepted Answer

Yes. The HAL is the only platform-specific piece. We port it to your part — typically a short step from one of the six families, which together cover roughly 90% of embedded silicon. Everything above the HAL carries forward unchanged.

Hardware, validated independently.

Polaris — Independent Validation & Verification (IV&V)

Orion — Hardware-in-the-Loop (HIL)

Vela — Field Datalogger