Vdevice

Vdevice is a virtual IO device package for the RT-Thread embedded operating system, providing simulated GPIO, LCD, and touch-input peripherals that let…

  • Development
  • Game Servers
  • Tools & Utilities
Vdevice is a virtual IO device package for the RT-Thread embedded operating system, providing simulated GPIO, LCD, and touch-input peripherals that let embedded developers test and debug application code without physical hardware.

Platform availability

Available on 0 of 10 platforms

  • Unraid (not listed)
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

8/100 Low

Maintained
0last commit 1291 days ago
Popular
61 GitHub stars
Easy to install
250 install platforms, install notes, Docker image
Light to run
No data

Based on 3 of 4 factors.

GitHub stars
1
Open issues
0
Last commit
2023-05-10
Latest release
V1.0.0
License
Apache-2.0
Activity
stale

Checked 16 days ago - source: GitHub (RT-Thread-packages/vdevice)

Resources & Compatibility

ARM (e.g. Raspberry Pi) is not supported.

Checked 54 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Enable vdevice in menuconfig Enable vdevice via menuconfig, then select which virtual devices (GPIO, LCD, or touch) to activate in your RT-Thread build. source
  • Installation After enabling vdevice in menuconfig, select the GPIO, LCD, or touch devices you want to virtualize. source

Fetched 2 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

Does each vComponent in the vDevice Controller have its own control plane socket?

Yes. Each vComponent serves its own control plane socket, and the Controller routes control messages to the appropriate one.

What Hailo-10H information does the Raspberry Pi forum thread provide?

It describes loading multiple Hailo-10H services as available APIs using VDevice inference-context management. It also mentions trouble getting an AI Hat + 2 setup working.

What VDevice initialization pattern is discussed in the Hailo community thread?

A user wants to create a VDevice inside a class initializer and reuse it instead of recreating it for each inference call.

Answers sourced from community.hailo.ai, forums.raspberrypi.com, github.com

Community

Collected 48 days ago - public community threads