Devices / single-board

Khadas VIM1S

Also known as VIM1S, khadas-vim1s

Open firmwareInstall: mediumImported

A free replacement firmware exists.

Armbian standard configuration (khadas-vim1s.conf). Kernel branches: legacy,edge; board family: meson-s4t7. Availability and working features depend on the selected image and branch; a build configuration is not an OpenDeviceDB hardware test.

Get started

One known way to put open firmware or software on this device, easiest first. Each one links to the project's own instructions.

Before you start
  • Back up your data and settings (and the stock firmware, when the guide says how).
  • Check the exact model, hardware revision and firmware version against the guide: a close model may not work.
  • Charge the battery or use a stable power supply; do not unplug during the install.

Install Armbian

Install: medium

Needs a cable or the command line · Armbian

Device opened
No
Firmware
Use the exact VIM1S board revision and an image for the selected kernel branch (legacy,edge). standard configuration.

Check upstream image availability and the board-specific page. SD, eMMC, SPI and USB installation routes vary by board; no universal media or recovery procedure is implied.

No install report yet. · Report how it went

OpenDeviceDB links to each project's own instructions and tools; nothing is flashed from this site. Flashing is at your own risk and may void the warranty.

ID
khadas/vim1s
Category
single-board
Vendor support
Unknown
Updated
2026-11-16
Curate this record on GitHubJSONClaim this device

Being worked on

No live claim. If you start working on this device, claim it so nobody duplicates your work.

Interfaces

No interface documented yet.

Projects

ProjectKindOriginLicenseFreedom
Armbian (standard configuration; khadas-vim1s.conf)firmwarecommunityGPL-2.0Still non-free: not stated · Cloud: noneArmbian standard configuration (khadas-vim1s.conf). Kernel branches: legacy,edge; board family: meson-s4t7. Availability and working features depend on the selected image and branch; a build configuration is not an OpenDeviceDB hardware test. Bootloader, DDR initialization, trusted firmware and peripheral firmware may use vendor binaries. This entry does not establish a fully free firmware stack.
What "still non-free" and "cloud" mean

What stays proprietary or depends on the vendor's cloud once the project is in use, from the project's own documentation.

vendor blobs
proprietary files extracted from the stock firmware
stock firmware
the stock firmware stays on the device; the project only talks to it
modem
cellular modem firmware
GPU
graphics driver or firmware
Wi-Fi
Wi-Fi driver or firmware
Bluetooth
Bluetooth firmware
camera
camera driver or image processing
sensors
sensor hub or sensor drivers
bootloader
boot firmware
other
another proprietary part
Cloud: none
works fully locally
Cloud: only at setup
a vendor account is needed once, e.g. to obtain a local key
Cloud: optional
cloud features exist but are not needed
Cloud: required
does not work without the vendor's cloud
Cloud: unknown
not known

Verification

Not verified. A "verified on hardware" badge requires a replayable test (hardware-replay) run on a real device with a stated firmware version.

Provenance

AI assistance not stated.

Status and claims as of the build date (2026-11-16). Data licensed CC BY-SA 4.0; imported data keeps its upstream license.