Fixed workload / software image / I/O
Validate the board, image and peripherals as one configuration.
Compare compact embedded compute options for fixed software, interface adaptation and video evaluation without assuming universal board or peripheral compatibility.
System role
Camera or peripheral input to compact embedded compute to a customer software image or fixed workload.
The category defines where a module may enter the customer architecture. Exact interfaces, ownership boundaries and validation requirements still change by model.
- 01 Camera / peripheral input Evaluation path
- 02 Embedded compute board Evaluation path
- 03 Customer software image or fixed workload Customer-owned
- 04 Host interfaces and peripherals Evaluation path
- 05 Customer system validation Customer-owned
Two compact compute configurations
Source-listed parameters support comparison. Final selection still requires the exact model, revision, interface and customer test conditions.
These boards are compared as fixed hardware and software-image configurations. Connector presence does not prove universal driver, pinout or peripheral compatibility.
CUSTOMER VERIFICATION REQUIRED
| Model | Processor | Memory | Storage | Video / I/O | Network / radio | Mechanical |
|---|---|---|---|---|---|---|
| ZeroW Alternative Board | H618 quad Cortex-A53, up to 1.5 GHz | LPDDR4, capacity optional | Configuration dependent | Micro HDMI / USB-C power / 40-pin GPIO | 2.4 / 5 GHz Wi-Fi + Bluetooth 5.0 | 65 × 30 mm / approx. 8.5 g |
| 2GB LPDDR4 / 16GB eMMC Board | RK3568 64-bit quad Cortex-A55 | 2GB LPDDR4 | 16GB eMMC | HDMI / Type-C / USB / Gigabit Ethernet / MIPI / 2×20 header | IPEX antenna connector; function to confirm | Board revision and installed envelope to confirm |
- OS image, memory map, storage, camera input, GPIO pinout, drivers, peripherals, power and thermal behavior require exact-board verification.
- These are embedded compute evaluation options, not complete perception or autonomy systems.
What to confirm
Selection questions before a model enters evaluation.
- 01
Which OS image, storage, memory and workload must be fixed for evaluation?
- 02
Which camera, pinout, driver, peripheral and interface dependencies must be confirmed?
- 03
What power, enclosure and thermal conditions define acceptable operation?
Verification gates
A category match is not yet a platform match.
Each evaluation unit must remain tied to its exact model, revision, selected options, source status and customer acceptance criteria.
Electrical and interface
Connector, pinout, direction, voltage level, signaling, protocol, host, driver and firmware.
Mechanical and environmental
Envelope, mounting, optics, cabling, vibration, heat path, installation and operating conditions.
Workflow and acceptance
Video or data path, degraded-state behavior, measurements, thresholds and change triggers.
Next engineering decision
Review Embedded Compute Boards against your platform constraints.
Share the platform context and the engineering constraints already known. Thyraon will use them to frame the next evaluation step.