Table of Contents
Published: 2026-09-16 · Category: RISC-V MCU · Reading time: ~4 min · Status: DRAFT
The interesting part is the SoC they removed
JetKVM Mini, detailed on 14 September 2026, is a smaller and cheaper version of the JetKVM KVM-over-IP device. The headline change is not the size — it is that the previous design's Rockchip RV1106G3 running Linux has been replaced by an Espressif ESP32-P4X RISC-V microcontroller running a FreeRTOS-based ESP-IDF firmware.
That substitution is a clean case study in where RISC-V microcontrollers are actually winning. The stated reason is cost, and the largest single saving is the removal of the external RAM and eMMC flash that Linux requires. Below a certain complexity threshold, a Linux BSP is not a feature — it is a bill of materials line, a boot-time penalty and a security-update obligation. A KVM that streams one encoded video feed, emulates HID and serves a web UI does not need a memory-management unit.
ESP32-P4X: what the silicon brings
The ESP32-P4X designation matters. This is ESP32-P4 revision 3.x and greater, not the original ESP32-P4. Published specifications:
| Block | Specification |
|---|---|
| HP CPU | Dual-core 32-bit RISC-V @ up to 400 MHz, AI instruction extension, single-precision FPU |
| LP CPU | Single RISC-V core @ up to 40 MHz |
| Memory | 768 KB HP L2MEM, 32 KB LP SRAM, 8 KB TCM, 32 MB PSRAM |
| ROM | 128 KB HP, 16 KB LP |
| VPU | H.264 and JPEG codec with Pixel Processing Accelerator and 2D DMA |
| GPU | 2D Pixel Processing Accelerator (PPA) |
| Storage | 16 MB flash, microSD for virtual media |
Why revision 3.x was the enabling change
Earlier community IP-KVM projects built on the original ESP32-P4 — ESP-KVM and P4 KVM — were restricted to MJPEG or very slow H.264, because an extra colour-space conversion step was required in software. The newer ESP32-P4X removes that step.
This is the practical lesson for anyone selecting silicon for an encoder product: the difference between "there is an H.264 block" and "there is a usable H.264 pipeline" is often a data-movement detail that only shows up in a specific silicon revision. Verify the revision, not just the part family.
Video path: 1080p30 in, WebRTC out
Video enters over an HDMI input port supporting up to 720p60 or 1080p30, is H.264-encoded on device, and is streamed over WebRTC to the host browser. The 4K figure quoted in the announcement is not on-device capture: with JetKVM OS Services installed on a Windows, macOS or Linux target, encoding happens on the host, so 4K screen capture, shared clipboard, a guest terminal and file transfer become possible.
Keeping that distinction straight matters. The RISC-V device is a 1080p30 appliance; 4K is a host-side feature.
Two variants, two radios
- JetKVM Mini — 100 Mbps Ethernet RJ45.
- JetKVM Mini W — dual-band WiFi 6, Bluetooth for onboarding, and 802.15.4 for Zigbee and Thread via an ESP32-C5 module.
Both carry USB 2.0 Type-C at 480 Mbps for mouse, keyboard and virtual-media emulation plus power, a second USB 2.0 Type-C at 12 Mbps for auxiliary power and future expansion, and run from 5 V at 500 mA. The enclosure is aluminium at 42 × 42 × 23 mm, with a 240 × 240 non-touch IPS status display.
Firmware, price and availability
Moving from Linux to ESP-IDF required a complete firmware rewrite, though the user-facing protocols, web interface and cloud integration are unchanged. The firmware will be open-sourced on the company's GitHub account closer to release.
Pricing is announced: $39 for the Mini, $33 each in a three-pack; $42 for the Mini W, $36 each in a three-pack. Availability is 26 October 2026.
Engineering takeaway
For embedded teams, JetKVM Mini is a useful reference point on the RISC-V-versus-Linux-SoC decision. If your product is a fixed-function streaming or control appliance, a 400 MHz RISC-V MCU with a hardware codec can remove DRAM, eMMC, a Linux BSP and a meaningful chunk of unit cost. The trade is a full firmware rewrite and the loss of a general-purpose software ecosystem. Price that trade honestly — and check the silicon revision before you commit.
Sources
- CNX Software — "JetKVM Mini – A low-cost, ESP32-P4X-based KVM with Ethernet or WiFi connectivity", 2026-09-14, by Jean-Luc Aufranc — https://www.cnx-software.com/2026/09/14/jetkvm-mini-a-low-cost-esp32-p4x-based-kvm-with-ethernet-or-wifi-connectivity/
- CNX Software — original JetKVM article ($69 KVM over IP), 2025-03-21 — https://www.cnx-software.com/2025/03/21/jetkvm-a-69-kvm-over-ip-solution-with-open-source-software/
- CNX Software — "ESP32-P4 revision 3.0 gains new power rail, requires new PCB design and firmware", 2026-03-23 — https://www.cnx-software.com/2026/03/23/esp32-p4-revision-3-0-gains-new-power-rail-requires-new-pcb-design-and-firmware/
- CNX Software — "ESP-KVM – An open-source IP KVM solution based on ESP32-P4 RISC-V MCU", 2026-07-30 — https://www.cnx-software.com/2026/07/30/esp-kvm-an-open-source-ip-kvm-solution-based-esp32-p4-risc-v-mcu/
Verification notes
- All specifications, prices and the 26 October 2026 availability date are taken verbatim from the CNX Software article dated 14 September 2026. No figures were estimated.
- The 4K capability is explicitly attributed to host-side JetKVM OS Services, not to on-device capture. This distinction is stated in the body because the announcement's own wording could be misread.
- The display size is not confirmed: CNX writes "size not mentioned, but possibly 1.54-inch". The draft states only the confirmed 240 × 240 resolution and describes it as non-touch.
- The claim that ESP32-P4X removes a colour-space conversion step required by the older ESP32-P4 is CNX's explanation, attributed as such.
- Prior coverage of ESP32-P4-based KVM projects exists (ESP-KVM, P4 KVM, 2026-07-30); this draft is scoped to the commercial JetKVM Mini and does not restate that material.
- Single-source limitation: only one substantive source (CNX Software) was found. Espressif's own ESP32-P4X datasheet was not consulted, so the block-level figures should be re-checked against it before publication.