PY BLOCK

03 / Technology

One open stack.
Three clear layers.

Affordable handheld hardware, capability-secure system software, and Python-authored applications—designed together from silicon to screen.

01 Hardware

Popular silicon,
practical interfaces.

The platform targets affordable, widely available Arm modules. Our current RDK X5 reference combines Cortex-A55 compute and 2 GiB memory with the interfaces a real handheld needs: display, storage, input, networking, and a direct debug path.

  • Arm AArch64 compute with commodity memory
  • HDMI display, USB HID, Ethernet, SD, I²C, and UART
  • Board-specific details isolated behind reusable driver contracts
Reference hardware map
RDK X5 reference hardware diagramAn Arm Cortex-A55 system on module connects to display, USB input, Ethernet, storage, and debug interfaces. RDK X5 MODULE + CARRIER Arm Cortex-A55AArch64 · 2 GiB DDRCOMPUTE CORE DisplayDC8000 · BT1120 · HDMI USB inputUSB3 xHCI · Hub · HID Storage + debugSD · I²C · UART NetworkingEQoS GMAC · RGMII PHY

02 Software

Small trusted core.
with Python Services in user space.

Based on the Hardware architecture, base OS kernel & Python Services provides isolation, scheduling, and capabilities. A narrowly scoped root task creates service threads and grants only the memory, device, and notification capabilities each needs. After boot, policy and drivers remain owned by user-mode services.

  • No Linux kernel guest or fallback path
  • Python-derived policy runs through the Godot-python VM
  • Display, USB, Storage, and networking are user mode services
Software architecture
Software framework architectureThe Godot-Python application layer sits above the Godot-Python runtime framework, user-mode service domains, boot-time authority, the kernel, and the hardware platform. Godot-Python application layeruser applications · system policy Godot-Python runtime frameworklanguage runtime · user interface · rendering · composition PYTHON OSUSER-MODE SERVICES + DRIVERS Display servicecomposition · output Input servicedevices · events Storage servicefilesystem · block I/O Network serviceprotocols · sockets Root authorityboot-time provisioning only Kernelcapabilities · TCBs · VSpace · scheduling Hardware platform

Dashed paths show capabilities provisioned at boot; solid paths show the operating stack.

03 Applications

Python at the top.
Portable output below.

Application logic starts in familiar Python. A compact toolchain converts it into an Object-FCode image for the target runtime, where EFL and software Vulkan render through Wayland to the display. The same composition can expose remote display, input, and debugging services.

  • Readable Python source remains the authoring layer
  • Generated OFC2 images are compact and target-ready
  • One runtime supports native display and remote access
Application path
Python application delivery pathPython source is transpiled into an Object-FCode image, run by a user-mode runtime, rendered using EFL and software Vulkan, and presented locally or remotely. Python sourceapps + policy TranspilerPython AST OFC2 imageportable payload User-modeVM runtime EFL + software VulkanCPU rendering · GPU optional Local screenWayland · framebuffer · HDMI Remote toolsVNC · input · GDB

Explore the implementation

Codes & Docs →