What boards should espkvm support next? 🤔

[dexif]

Hey everyone!

I've been thinking about expanding the list of supported boards in espkvm - and figured it’s better to ask than to guess 🙂

What boards would you like to see supported? What are you currently using or planning to use?

Also, if there happen to be any manufacturers around (or just kind people with spare boards 😄), having actual hardware makes adding support a lot faster. Just a very subtle hint 😉

Might be interesting for you as well: @espressif @m5stack @LilyGO

Anyway - feel free to drop your ideas, wishes, or any thoughts!

[DaveDavenport]

I am currently using Guition ESP32-P4-M3-Dev.

My plan is to use the ESP32-P4-NANO with POE board.
The usb-a port is OTG, so should work?

[dexif]

I've added draft targets for both - the Guition ESP32-P4-M3-Dev and the Waveshare ESP32-P4-NANO. They reuse the Function EV's C6 + IP101 Ethernet setup, so in theory they should just work, but I've configured them purely from datasheets - nobody's actually run ESP-KVM on either yet. A handful of pins are still guesses (RMII data, microSD, BOOT, chip rev), marked CONFIRM in the overlays.

You've got the Guition - can you check it?

idf.py -B build.guition -D SDKCONFIG=build.guition/sdkconfig \
  -D SDKCONFIG_DEFAULTS="sdkconfig.defaults;boards/guition_p4.defaults" build

(or in the browser flasher, tagged "configured, untested".)

Mainly I'd love to know: does capture + USB + Ethernet come up, and did you have to change any pins?

[DaveDavenport]

Guition ESP32-P4-M3-Dev worked out of the box for me.. capture, ethernet, usb worked fine. (the 3rd usb port from the ethernet is the emulated mouse/keyboard/etc. ). Cannot remember if I changed pins?

It does 'power' itself over the USB-c port, I did not like it, but might be preferable as some machines have a powered usb-port when off (and you can use it to power the kvm).

If I have some time later, I will try your config.

[DaveDavenport]

The guition board I have is a pre 3.0 revision board.

I changed the following:

diff --git a/boards/guition_p4.defaults b/boards/guition_p4.defaults
index 2a92418..42729f3 100644
--- a/boards/guition_p4.defaults
+++ b/boards/guition_p4.defaults
@@ -26,8 +26,8 @@
 # likely rev v3.x - keep the two lines below if so (they also compile esp_h264's
 # faster RGB/YUV422-direct path). If it is actually a rev <3.0 part, DELETE both
 # lines so it builds against the pre-3.0 family like Waveshare.
-CONFIG_ESP32P4_SELECTS_REV_LESS_V3=n
-CONFIG_ESP32P4_REV_MIN_300=y
+CONFIG_ESP32P4_SELECTS_REV_LESS_V3=y
+CONFIG_ESP32P4_REV_MIN_300=n

It works fine with this and the guiton provided config.
Tested:

• Ethernet
• USB mouse/keyboard emulation
• Capturing FHD

Thanks!

[DaveDavenport]

The waveshare nano p4 board I have is also a pre 3.0 revision board.

I changed the following:

diff --git a/boards/nano_p4.defaults b/boards/nano_p4.defaults
index 1a56ce7..6b57e06 100644
--- a/boards/nano_p4.defaults
+++ b/boards/nano_p4.defaults
@@ -21,8 +21,8 @@
 # boards ship rev v3.x; if this board is one, keep the two lines below (they also
 # compile esp_h264's faster RGB/YUV422-direct path). If it is actually a rev <3.0
 # part, DELETE both lines so it builds against the pre-3.0 family like Waveshare.
-CONFIG_ESP32P4_SELECTS_REV_LESS_V3=n
-CONFIG_ESP32P4_REV_MIN_300=y
+CONFIG_ESP32P4_SELECTS_REV_LESS_V3=y
+CONFIG_ESP32P4_REV_MIN_300=n

It works fine with this and the nano p4 provided config.
Tested:

• Ethernet
• USB mouse/keyboard emulation
• Capturing FHD

Thanks!

[dexif]

Thanks. Will apply your changes.

[dexif]

I'll try to add support for m5staсk: #35

[DaveDavenport]

interesting combi.