pico HID Flashing Procedure<\/h3>\n\n- Download the Image<\/strong>
The flashing image for Pico, “pico-hid.uf2”, can be downloaded from the GitHub releases page here<\/a>.<\/li>\n- Flashing Steps<\/strong>
Connect the Pico to your PC via USB while holding down its boot button, and it will be recognized as a USB drive.
With the drive mounted, copy the downloaded “pico-hid.uf2” file to the USB drive.
* Since we are not using a PS\/2 keyboard or mouse this time, the flashing is complete with just this step.
\n![\"Flashing](\"https:\/\/donguri3.net\/wp-content\/uploads\/2025\/04\/RPI-RP2-D_-2025_04_03-15_57_26-1024x556.png\")
<\/a><\/li>\n<\/ol>\nFlashing the PiKVM OS Image<\/h2>\nSelecting and Flashing the OS Image<\/h3>\n\n- Flashing Tool<\/strong>
Use Raspberry Pi Imager to flash the PiKVM V1 OS image (for HDMIUSB, RPi3).
* Please note that if you are not using a USB capture board or if you are using a different Raspberry Pi version, the required image will differ.
\n![\"Raspberry](\"https:\/\/donguri3.net\/wp-content\/uploads\/2025\/04\/Raspberry-Pi-Imager-v1.9.0-2025_04_01-15_39_34.png\")
<\/a><\/li>\n- Image Download Source<\/strong>
The OS image can be downloaded from the official website here<\/a>.
Since downloading takes some time, I initially attempted a custom build, but gave up due to numerous errors and patiently waited for the official image to download instead.<\/li>\n- Installing the Image<\/strong>\n
\n- Select Raspberry Pi Device
\nSelect Raspberry Pi 3 for this project
\n![\"Select](\"https:\/\/donguri3.net\/wp-content\/uploads\/2025\/04\/Raspberry-Pi-Imager-v1.9.0-2025_04_01-15_39_29.png\")
<\/a><\/li>\n- Select OS
\nSelect the downloaded custom image
\n![\"Select](\"https:\/\/donguri3.net\/wp-content\/uploads\/2025\/04\/Raspberry-Pi-Imager-v1.9.0-2025_04_01-15_38_35.png\")
<\/a><\/li>\n- Select Storage
\nSelect the SD card to be inserted into the Raspberry Pi
\n![\"Select](\"https:\/\/donguri3.net\/wp-content\/uploads\/2025\/04\/Raspberry-Pi-Imager-v1.9.0-2025_04_01-15_38_25.png\")
<\/a><\/li>\n- Write OS Image
\nClick Next to start writing
\n![\"Raspberry](\"https:\/\/donguri3.net\/wp-content\/uploads\/2025\/04\/Raspberry-Pi-Imager-v1.9.0-2025_04_01-15_48_41.png\")
<\/a><\/li>\n<\/ol>\n<\/li>\n<\/ul>\nInitial Setup After Installation<\/h2>\nBrowser Access<\/h3>\n\n- Once the OS image has been written and PiKVM has booted up, access the PiKVM via a web browser. (Do you need to connect an HDMI cable to the Raspberry Pi to check its assigned IP?)<\/li>\n
- Default login credentials:
User ID:<\/strong> admin
Password:<\/strong> admin<\/li>\n<\/ul>\nTroubleshooting When the Screen Does Not Display<\/h3>\n
If the PiKVM screen does not appear in your browser, modify the settings from the console using the following steps.<\/p>\n
\n- Access the Console<\/strong>
Log in to the console as the root user (initial password: root).<\/li>\n- Editing
\nSwitch Filesystem to RW Mode<\/strong>
\nEdit \/etc\/kvmd\/override.yaml<\/strong>
\nApply Changes<\/strong><\/li>\n<\/ol>\n[root@pikvm ~]# rw\n[root@pikvm ~]# vim \/etc\/kvmd\/override.yaml\nkvmd:\n streamer:\n forever: true\n cmd_append: [--slowdown]\n[root@pikvm ~]# ro\n[root@pikvm ~]# systemctl restart kvmd<\/pre>\nThis should allow the target server’s screen to be displayed correctly.<\/p>\n
Initial Troubleshooting and Lessons Learned<\/h2>\n
In the early stages, I mistakenly connected the wiring between the Pico and Raspberry Pi 3 incorrectly, which caused continuous SPI connection errors. Re-verifying the correct wiring and resetting the HID resolved the issue, but it made me acutely realize how crucial it is to check hardware connections before setting up the software.<\/p>\n
Conclusion<\/h2>\n
In this software setup, we covered flashing pico HID to the Pico compatible board, writing the PiKVM V1 OS image using Raspberry Pi Imager, and troubleshooting initial configurations. By following the official documentation (PiKVM V1<\/a>) and GitHub release information step-by-step, we successfully completed a simple and stable PiKVM system tailored for monitoring the ASRock Beebox.<\/p>\n
The flashing image for Pico, “pico-hid.uf2”, can be downloaded from the GitHub releases page here<\/a>.<\/li>\n
Connect the Pico to your PC via USB while holding down its boot button, and it will be recognized as a USB drive.
With the drive mounted, copy the downloaded “pico-hid.uf2” file to the USB drive.
* Since we are not using a PS\/2 keyboard or mouse this time, the flashing is complete with just this step.
\n
<\/a><\/li>\n<\/ol>\nFlashing the PiKVM OS Image<\/h2>\nSelecting and Flashing the OS Image<\/h3>\n\n- Flashing Tool<\/strong>
Use Raspberry Pi Imager to flash the PiKVM V1 OS image (for HDMIUSB, RPi3).
* Please note that if you are not using a USB capture board or if you are using a different Raspberry Pi version, the required image will differ.
\n<\/a><\/li>\n- Image Download Source<\/strong>
The OS image can be downloaded from the official website here<\/a>.
Since downloading takes some time, I initially attempted a custom build, but gave up due to numerous errors and patiently waited for the official image to download instead.<\/li>\n- Installing the Image<\/strong>\n
\n- Select Raspberry Pi Device
\nSelect Raspberry Pi 3 for this project
\n<\/a><\/li>\n- Select OS
\nSelect the downloaded custom image
\n<\/a><\/li>\n- Select Storage
\nSelect the SD card to be inserted into the Raspberry Pi
\n<\/a><\/li>\n- Write OS Image
\nClick Next to start writing
\n<\/a><\/li>\n<\/ol>\n<\/li>\n<\/ul>\nInitial Setup After Installation<\/h2>\nBrowser Access<\/h3>\n\n- Once the OS image has been written and PiKVM has booted up, access the PiKVM via a web browser. (Do you need to connect an HDMI cable to the Raspberry Pi to check its assigned IP?)<\/li>\n
- Default login credentials:
User ID:<\/strong> admin
Password:<\/strong> admin<\/li>\n<\/ul>\nTroubleshooting When the Screen Does Not Display<\/h3>\n
If the PiKVM screen does not appear in your browser, modify the settings from the console using the following steps.<\/p>\n
\n- Access the Console<\/strong>
Log in to the console as the root user (initial password: root).<\/li>\n- Editing
\nSwitch Filesystem to RW Mode<\/strong>
\nEdit \/etc\/kvmd\/override.yaml<\/strong>
\nApply Changes<\/strong><\/li>\n<\/ol>\n[root@pikvm ~]# rw\n[root@pikvm ~]# vim \/etc\/kvmd\/override.yaml\nkvmd:\n streamer:\n forever: true\n cmd_append: [--slowdown]\n[root@pikvm ~]# ro\n[root@pikvm ~]# systemctl restart kvmd<\/pre>\nThis should allow the target server’s screen to be displayed correctly.<\/p>\n
Initial Troubleshooting and Lessons Learned<\/h2>\n
In the early stages, I mistakenly connected the wiring between the Pico and Raspberry Pi 3 incorrectly, which caused continuous SPI connection errors. Re-verifying the correct wiring and resetting the HID resolved the issue, but it made me acutely realize how crucial it is to check hardware connections before setting up the software.<\/p>\n
Conclusion<\/h2>\n
In this software setup, we covered flashing pico HID to the Pico compatible board, writing the PiKVM V1 OS image using Raspberry Pi Imager, and troubleshooting initial configurations. By following the official documentation (PiKVM V1<\/a>) and GitHub release information step-by-step, we successfully completed a simple and stable PiKVM system tailored for monitoring the ASRock Beebox.<\/p>\n
- \n
- Flashing Tool<\/strong>
Use Raspberry Pi Imager to flash the PiKVM V1 OS image (for HDMIUSB, RPi3).
* Please note that if you are not using a USB capture board or if you are using a different Raspberry Pi version, the required image will differ.
\n<\/a><\/li>\n- Image Download Source<\/strong>
The OS image can be downloaded from the official website here<\/a>.
Since downloading takes some time, I initially attempted a custom build, but gave up due to numerous errors and patiently waited for the official image to download instead.<\/li>\n- Installing the Image<\/strong>\n
- \n
- Select Raspberry Pi Device
\nSelect Raspberry Pi 3 for this project
\n<\/a><\/li>\n- Select OS
\nSelect the downloaded custom image
\n<\/a><\/li>\n- Select Storage
\nSelect the SD card to be inserted into the Raspberry Pi
\n<\/a><\/li>\n- Write OS Image
\nClick Next to start writing
\n<\/a><\/li>\n<\/ol>\n<\/li>\n<\/ul>\nInitial Setup After Installation<\/h2>\n
Browser Access<\/h3>\n
- \n
- Once the OS image has been written and PiKVM has booted up, access the PiKVM via a web browser. (Do you need to connect an HDMI cable to the Raspberry Pi to check its assigned IP?)<\/li>\n
- Default login credentials:
User ID:<\/strong> admin
Password:<\/strong> admin<\/li>\n<\/ul>\nTroubleshooting When the Screen Does Not Display<\/h3>\n
If the PiKVM screen does not appear in your browser, modify the settings from the console using the following steps.<\/p>\n
- \n
- Access the Console<\/strong>
Log in to the console as the root user (initial password: root).<\/li>\n- Editing
\nSwitch Filesystem to RW Mode<\/strong>
\nEdit \/etc\/kvmd\/override.yaml<\/strong>
\nApply Changes<\/strong><\/li>\n<\/ol>\n[root@pikvm ~]# rw\n[root@pikvm ~]# vim \/etc\/kvmd\/override.yaml\nkvmd:\n streamer:\n forever: true\n cmd_append: [--slowdown]\n[root@pikvm ~]# ro\n[root@pikvm ~]# systemctl restart kvmd<\/pre>\n
This should allow the target server’s screen to be displayed correctly.<\/p>\n
Initial Troubleshooting and Lessons Learned<\/h2>\n
In the early stages, I mistakenly connected the wiring between the Pico and Raspberry Pi 3 incorrectly, which caused continuous SPI connection errors. Re-verifying the correct wiring and resetting the HID resolved the issue, but it made me acutely realize how crucial it is to check hardware connections before setting up the software.<\/p>\n
Conclusion<\/h2>\n
In this software setup, we covered flashing pico HID to the Pico compatible board, writing the PiKVM V1 OS image using Raspberry Pi Imager, and troubleshooting initial configurations. By following the official documentation (PiKVM V1<\/a>) and GitHub release information step-by-step, we successfully completed a simple and stable PiKVM system tailored for monitoring the ASRock Beebox.<\/p>\n
- Editing
- Access the Console<\/strong>
- Select OS
- Image Download Source<\/strong>