Hardware Hub¶
Use this page when you already know the SDK workflow and need to decide where it should run.
Choose The Device¶
| If you need... | Best fit | Start with |
|---|---|---|
| a stable live digital-patient demo | Raspberry Pi | Raspberry Pi Digital Patient |
| visible hardware feedback with a small bridge layer | Arduino UNO Q | Arduino UNO Q Setup |
| deterministic hardware-logic verification | FPGA board or mock FPGA flow | FPGA Mode |
| accelerated stress testing or real-duration wall-clock studies | NVIDIA Jetson | Jetson Endurance Mode |
Fastest Safe Start¶
Raspberry Pi:
iints edge quickstart --board raspberry_pi
Arduino UNO Q:
iints edge quickstart --board uno_q
FPGA safety-core lab:
iints fpga doctor
iints fpga setup --output-dir iints_fpga_lab
iints fpga demo --output-dir results/fpga_demo
Jetson:
iints jetson doctor
iints jetson endurance start --duration 7d --profile mixed_adversarial --output-dir results/jetson_7day
For a true 24-hour acquisition study instead of an accelerated stress sweep:
iints jetson endurance start --duration 1d --profile normal --wall-clock --output-dir results/jetson_research_day
Device Routes¶
Raspberry Pi¶
Edge Hardware Matrix
-> Raspberry Pi Digital Patient
-> Remote Deploy & Pi Connect
-> Maker Faire Pi Mode if needed
Arduino UNO Q¶
Edge Hardware Matrix
-> Arduino UNO Q Setup
-> upload bridge sketch once
-> run the Linux-side patient runtime
NVIDIA Jetson¶
Jetson Endurance Mode
-> doctor
-> endurance start in accelerated or wall-clock mode
-> status / monitor / export
FPGA Mode¶
FPGA Mode
-> setup lab scaffold
-> run mock safety-core comparison
-> later connect serial FPGA bridge
-> compare hardware output against SDK reference