rt101-rk3568
RT101
Rockchip RK3568
Tablet-format kiosk with a built-in LTE modem, a battery, and a touch display.
- strux.cellular
- strux.battery
- strux.network
Hardware
Strux 0.4 ships with board support packages for the devices Medeiros IT deploys itself. Each one implements the runtime capabilities its hardware can back, and each is a worked example for bringing up your own board.
rt101-rk3568
Rockchip RK3568
Tablet-format kiosk with a built-in LTE modem, a battery, and a touch display.
hd215-rk3576
Rockchip RK3576
Display kiosk with a USB LTE adapter. The full board bring-up in the Strux documentation.
ht109-rk3576s
Rockchip RK3576S
Tablet-format kiosk with a battery, on the same SoC family as the HD215.
The capabilities listed on each device are the runtime namespaces its board support package provides. Everything built in, from the display API to signed updates and fleet enrollment, works on all three.
A board support package is a folder in your project. The documentation walks from a minimal package that boots in QEMU to a real board with its own kernel, bootloader, device tree, and flash script, and the reference packages in the repository are the worked examples.
| Reference BSP | What it shows |
|---|---|
| qemu | The minimal reference. Every project ships with it and dev mode runs on it. |
| hd215-rk3576 | The full bring-up: custom kernel, U-Boot, device tree, flash scripts, and runtime extensions. |
| hd215-rk3288 | The older 32-bit board, showing an ARMhf build of the same product. |
From a minimal bsp.yaml to a boot in QEMU, then to the real board.
Sources, defconfigs, fragments, patches, device trees, U-Boot and GRUB.
Go providers for the capabilities your hardware can back.
The host-side script that puts the image on the board.
Medeiros IT brings up boards for Strux as an engagement: kernel and bootloader, device tree, runtime extensions for the hardware, the flash path, and an image that enrolls in your Fleet.