KO
|
EN
gitlite — search
Search
#typescript
#ai-agents
#ai
#dsh-plugin
#deepseek-harness
#open-source
#cli
#claude-code
#codex
#developer-tools
#react
#windows
esparrier
★ 38
Open GitHub ↗
Barrier/Deskflow client for ESP32S3
Download README (.md)
Explore Similar Repositories
repository-synergy
:
The code and data for the SEKE 2021 paper
synergy-serial
:
Generate a Synergy serial code.
TADAM
:
Implementation of the CVPR 2021 paper "Online Multiple Object Tracking with Cross-Task Synergy"
synergy
:
No description available.
DeRIS
:
[ICCV2025] DeRIS: Decoupling Perception and Cognition for Enhanced Referring Image Segmentation through Loopback Synergy
// repository documentation
Was this content helpful?
★ 0
(0 ratings)
Select Rating:
★
★
★
★
★
Submit Feedback
Recent Feedback
×
Download README
Do you want to download the
README.md
file for
esparrier
?
Download (.md)
Esparrier ========= [](https://github.com/windoze/esparrier/blob/main/README.md)  [](https://github.com/windoze/esparrier/releases) [](https://deepwiki.com/windoze/esparrier) Esparrier is a [Barrier](https://github.com/debauchee/barrier)/[Deskflow](https://deskflow.org/) client for ESP32S3. This is a re-write of the original [Esparrier-IDF project](https://github.com/windoze/esparrier-idf), moving from `esp-idf-hal` to `esp-hal` baremetal infrastructure. ## Before you start Make sure your ESP32-S3 board meets following requirements: * It has native USB OTG port. Be aware that some boards have USB-Serial chip instead of native USB OTG port, they won't work. Check the manufacturer's documentation to be sure. * It has 520KB of built-in SRAM, all retail packages should meet this requirement, but you should check the datasheet to be sure. * It has at least 1MB of flash, 4MB or larger flash is required if you want to use OTA update feature. Be aware that some packages don't have built-in flash, such as ESP32S3R2/ESP32S3R8, they require external flash chip to work. The safest option is to get an official development board from Espressif, such as ESP32-S3-DevKitC-1 v1.0 or v1.1. Also because [Espressif has acquired a majority stake in M5Stack](https://www.espressif.com/en/news/Espressif_Acquires_M5Stack), the M5Atom S3 Lite and M5Atom S3 should be good choices as well. ## How to build * The release page provides pre-built binaries for some ESP32S3 boards, you can use them directly if your board is listed. * Generic ESP32S3 boards with native USB-OTG port, the indicator feature is unavailable, OTA and the clipboard feature are disabled as well. * [M5Atom S3 Lite](https://docs.m5stack.com/en/core/AtomS3%20Lite) and [M5AtomS3U](https://docs.m5stack.com/en/core/AtomS3U), the SmartLED feature, the clipboard feature and the OTA feature are enabled. * [M5Atom S3](https://docs.m5stack.com/en/core/AtomS3), the clipboard feature and the OTA feature are enabled, and the indicator shows emoji animations on the built-in LCD screen. * [M5Atom S3R](https://docs.m5stack.com/en/core/AtomS3R), the clipboard feature and the OTA feature are enabled, and the indicator shows emoji animations on the built-in LCD screen. * [Seeed Studio XIAO ESP32S3](https://wiki.seeedstudio.com/xiao_esp32s3_getting_started/), the led is used as the indicator, OTA feature is enabled, and the clipboard feature is disabled due to the lack of a user button. * [Espressif ESP32-S3-DevKitC-1 v1.0](https://docs.espressif.com/projects/esp-dev-kits/en/latest/esp32s3/esp32-s3-devkitc-1/user_guide_v1.0.html), the SmartLED feature and the OTA feature are enabled, and the clipboard feature is disabled due to the lack of a user button. * (Untested) [Espressif ESP32-S3-DevKitC-1 v1.1](https://docs.espressif.com/projects/esp-dev-kits/en/latest/esp32s3/esp32-s3-devkitc-1/user_guide.html), the SmartLED feature and the OTA feature are enabled, and the clipboard feature is disabled due to the lack of a user button. * [Waveshare ESP32-S3-ETH](https://www.waveshare.com/wiki/ESP32-S3-ETH), the SmartLED feature and the OTA feature are enabled, and the clipboard feature is disabled due to the lack of a user button, and the W5500 Ethernet chip is used for the network connection instead of Wi-Fi. 1. Install Rust toolchain. 2. Install Rust ESP32 tools: * `espup` - https://github.com/esp-rs/espup * `cargo-espflash` - https://github.com/esp-rs/espflash * `espmonitor` - https://github.com/esp-rs/espmonitor * Install Rust ESP toolchain with `espup install` 3. Set environment variable for Rust ESP toolchain: * `source $HOME/export-esp.sh` 4. Build and flash: 1. (Optional) Set following environment variables: * `export WIFI_SSID="YOUR_WIFI_SSID"` * `export WIFI_PASSWORD="YOUR_WIFI_PASSWORD"` * `export BARRIER_SERVER="BARRIER_SERVER_IP:PORT"` * `export SCREEN_NAME="SCREEN_NAME"` 2. Put your board in the download mode, then build and flash with `cargo run --release --features <FEATURES> -- --partition-table <PARTITION_TABLE>`. * `<FEATURES>` options: * `smartled` - Enable SmartLED feature (if the board has RGB LED), you need to set the environment variable `SMART_LED_PIN` to the correct pin number. Cannot be enabled together with `led` feature. * `led` - Enable ordinary LED indicator feature (if the board has ordinary LED), you need to set the environment variable `LED_PIN` to the correct pin number. Cannot be enabled together with `smartled` feature. * `clipboard` - Enable clipboard feature (if the board has a user button), you need to set the environment variable `PASTE_BUTTON_PIN` to the correct pin number. * `ota` - Enable OTA update feature (requires 4MB or larger flash) * `<PARTITION_TABLE>` options: * `partitions_single_app.csv` - Use default partition table (1MB flash) * `partitions_ota.csv` - Use OTA partition table (4MB or larger flash) 3. If you skip the first step, the program will use default configurations, and it won't be able to connect to WiFi and Barrier/Deskflow server, you need to [update the configurations](#update-configurations) to make it work. ## Run 1. Configure Barrier or Deskflow server to accept the screen name you set in the environment variable `SCREEN_NAME`, and make sure you turn off the TLS. 2. Plug the board into the USB port. 3. The LED should be red on start, then turn blue when the board is connected to the WiFi, and finally turn dim yellow when the board is connected to the Barrier/Deskflow server. 4. When Barrier/Deskflow enters the screen, the LED turns bright green, and when Barrier/Deskflow leaves the screen, the LED turns dim yellow. 5. The board emulates a standard keyboard and an absolute mouse, it should work in any OS. 6. USB HID boot protocol is used, so you should be able to use the board as a USB keyboard/mouse in BIOS/EFI or even if the OS doesn't have a driver for it. ## Update Configurations There are multiple ways to update the device configuration: ### Web-based Configuration Tool (Recommended) The easiest way to configure your device is using the **web-based configuration tool** at [https://0d0a.com/esparrier/](https://0d0a.com/esparrier/). This tool uses WebUSB to communicate with the device directly from your browser - no installation required. Simply connect your device via USB, open the page in a Chromium-based browser (Chrome, Edge, Opera, Brave), and click "Connect Device". ### CLI Configuration Tool A CLI configuration tool is available at [esparrier-config](https://github.com/windoze/esparrier-config). Checkout the repo and follow the instructions to build and run the tool. ### Manual Configuration (Legacy) Below is the old way to update configurations, it's still valid but not recommended. First, you need to install `esptool.py`, which can be installed with `pip install esptool`. Refer to the [official documentation](https://docs.espressif.com/projects/esptool/en/latest/esp32/installation.html) for more information. ### Prepare and Update Configurations 1. Create a JSON file, refer to [config.json.example](config.json.example) for the format. 2. Put the board into the download mode, then use `esptool.py` to flash the NVS partition. ```bash # Erase the NVS partition esptool.py --chip esp32s3 --port /dev/ttyACM0 write_flash 0x9000 zero.bin # Write the configurations esptool.py --chip esp32s3 --port /dev/ttyACM0 write_flash 0x9000 /path/to/config.json ``` 3. Exit the download mode and reset the board, the new configurations should be applied. ## Clipboard The program now has limited support of the clipboard when the feature `clipboard` is enabled. This feature requires your board to have an user button, and the button should be connected to the GPIO pin defined in the environment variable `PASTE_BUTTON_PIN`, on M5AtomS3 Lite, it is PIN 41. The button should be active low, i.e. the pin should be pulled up to high level, and the button should pull down the pin to low level when pressed. First you need to activate other screen and copy something into the clipboard, then switch to the screen connected to the board. When the screen is activated, the board receives the clipboard content sent by the Barrier/Deskflow server, **keeps the first 1024 characters of the plain text format and discard everything else**. Then you can "paste" the text by pressing the button on the board, the board will convert the text into a sequence of keystrokes, and send them to the computer. All characters except the visible ASCII codes will be discarded as they cannot be directly mapped to USB HID key codes, or they may have special meaning that can mess up things. The program cannot "copy" content to the clipboard. NOTE: When you copied a large amount of text or big image from other screen then moved into the screen connected to the board, the board may stuck for a while, this is because the board is trying to discard the clipboard content. Even it will not parse and hold the whole content, still it needs to receive the whole content from the Barrier/Deskflow server as there is no way to skip a chunk in the middle of a TCP stream without actually reading it. The server sends the content synchronously so the keyboard and mouse will be completely unresponsive until the content has been fully transferred. Due to the low WiFi bandwidth of the ESP32-S3, the transferred could take several seconds or even minutes. [The Deskflow has a `clipboardSharingSize = N` option](https://github.com/deskflow/deskflow/wiki/Text-Config#list-of-options) which can limit the clipboard size to be shared, but this option is unavailable in Barrier. ## Build for other ESP32S3 boards * It's recommended to erase the flash before the first time flashing the binary to the board, you can do this with `esptool.py` or `cargo-espflash`: ```bash # With cargo-espflash cargo espflash erase-flash --chip esp32s3 --port /dev/ttyACM0 # With esptool.py esptool.py --chip esp32s3 --port /dev/ttyACM0 erase_flash ``` * If there is a RGB LED (WS2812B) on the board, you can use `smartled` feature to enable the LED, and you need to set the environment `SMART_LED_PIN` to the correct pin number, on M5AtomS3/Lite, it's 35, on M5StampS3, it's 21. * E.g. to build and flash the binary for ESP32-S3-DevKitC-1 v1.0: ```bash SMART_LED_PIN=38 cargo run --release --features smartled ``` * If there is an ordinary LED on the board, you can use `led` feature to enable it, and you need to set the environment `LED_PIN` to the correct pin number. * Do not enable more than one of above features, the program won't compile. * If none of above features is enabled, the indicator function is disabled. * If there is a user button on the board, you can use `clipboard` feature to enable the clipboard support, and you need to set the environment `PASTE_BUTTON_PIN` to the correct pin number. * E.g. to build and flash the binary for [M5StampS3](https://docs.m5stack.com/en/core/StampS3): ```bash SMART_LED_PIN=21 PASTE_BUTTON_PIN=0 cargo run --release --features smartled,clipboard ``` * The program will output log to the UART0 by default, you can use `espmonitor` to monitor the log. If your board doesn't have separated UART0 port, you can disable the default features, this will disable the USB HID function, and you'll be able to see logs from USB OTG/J-TAG port. This is useful for debugging codes not related to USB HID. ## Use pre-built binaries **NOTE**: Use pre-built binaries only when you have exactly the same board as the binary is built for, or you know what you are doing. Flashing a wrong binary to the board may cause the board to not work properly. 1. Install `esptool.py` as described in the previous section. You don't need to install Rust toolchain and any other ESP32 tools. 2. Download the binary from the [releases page](https://github.com/windoze/esparrier/releases). 3. Extract the binary from the archive. There are few pre-built binaries in the archive for specific boards, choose the one that fits your board. * `merged-esparrier-generic.bin` - For generic ESP32S3 boards with native USB-OTG port, the indicator and clipboard features are unavailable. * `merged-esparrier-m5atoms3-lite.bin` - For [M5Atom S3 Lite](https://docs.m5stack.com/en/core/AtomS3%20Lite) and [M5AtomS3U](https://docs.m5stack.com/en/core/AtomS3U). * `merged-esparrier-m5atoms3.bin` - For [M5Atom S3](https://docs.m5stack.com/en/core/AtomS3). * `merged-esparrier-m5atoms3r.bin` - For [M5Atom S3R](https://docs.m5stack.com/en/core/AtomS3R). * `merged-esparrier-xiao-esp32s3.bin` - For [Seeed Studio XIAO ESP32S3](https://wiki.seeedstudio.com/xiao_esp32s3_getting_started/). * `merged-esparrier-esp32s3-devkitc-1-v1_0.bin` - For [ESP32-S3-DevKitC-1 v1.0](https://docs.espressif.com/projects/esp-dev-kits/en/latest/esp32s3/esp32-s3-devkitc-1/user_guide_v1.0.html). * `merged-esparrier-esp32s3-devkitc-1-v1_1.bin` - For [ESP32-S3-DevKitC-1 v1.1](https://docs.espressif.com/projects/esp-dev-kits/en/latest/esp32s3/esp32-s3-devkitc-1/user_guide.html). * `merged-esparrier-esp32-s3-eth.bin` - For [Waveshare ESP32-S3-ETH](https://www.waveshare.com/wiki/ESP32-S3-ETH). 4. Prepare the `config.json` file as described in the previous section. 5. Put the board into the download mode, then flash the binary and config to the board. Note the USB device name may vary, you may need to change it to the correct one. On most Linux systems, the device name is `/dev/ttyACMx`, where `x` is a number, you can find the correct device name by running `ls /dev/ttyACM*`. * Use `esptool.py`: ```bash # Erase the whole flash esptool.py --chip esp32s3 --port /dev/ttyACM0 erase_flash # Write the binary and config esptool.py --chip esp32s3 --port /dev/ttyACM0 write_flash 0x0000 /path/to/merged-esparrier-generic.bin ``` * Or use `espflash`: ```bash # Erase the whole flash espflash erase-flash --chip esp32s3 --port /dev/ttyACM0 # Write the binary and config espflash write-bin --chip esp32s3 --port /dev/ttyACM0 0x0000 /path/to/merged-esparrier-generic.bin ``` 6. Exit the download mode and reset the board, you should see the new USB HID device on your host. Now the board is ready to be configured using the [web-based configuration tool](https://0d0a.com/esparrier/), the [esparrier-config-cli](https://github.com/windoze/esparrier-config), or by the [manual update configuration](#manual-configuration-legacy) method. ## Troubleshooting If the board stops working after flashing and/or upgrading the program, you may need to: 1. Erase the flash with `esptool.py --chip esp32s3 --port /dev/ttyACM0 erase_flash`. 2. Flash the binary and config again. 3. Windows has a USB device driver cache and it may not recognize the board after flashing, you may need to uninstall the driver in the device manager and re-plug the board. Or you can change the USB VID/PID in the config file and re-flash it, then Windows will recognize it as a new device. 4. If above steps don't work, you can try a different flash command: ```bash # Erase the whole flash esptool.py --chip esp32s3 --port /dev/ttyACM0 erase_flash # Write the binary, please note the firmware used here without 'merged-' prefix. esptool.py --chip esp32s3 --port /dev/ttyACM1 write_flash \ 0x0000 esp32s3-bootloader.bin \ 0x8000 partition_table.bin \ 0x10000 esparrier-generic.bin ``` The root cause of the problem is still not clear, but it seems to be related to the partition table, and the above command will write bootloader, partition table, and the application binary to the flash separately. ## NOTES: **WARNING**: This program is only for testing purpose. It is not a complete implementation of Barrier/Deskflow client. There could be a lot of bugs and missing features. It has no concept of security, neither on the WiFi nor on the USB. It is not recommended to use it in anywhere but a private environment. * This code is developed and tested on [M5Atom S3 Lite](https://docs.m5stack.com/en/core/AtomS3%20Lite), other ESP32S3 boards may not work, or you need to change the code to fit your board. * A board with external antenna is strongly recommended, the ESP32S3 supports 2.4G WiFi only and this band is really crowded, you may experience jittering and lagging if the wireless connection is not stable. * The code doesn't work on ESP8266/ESP32/ESP32C3 because they don't have required USB features, ESP32S2 may work with adaptation but it's not tested. * It doesn't support TLS, so you must run Barrier/Deskflow server without TLS. * When using with Deskflow, you need to make sure the Deskflow server is using "Barrier" protocol, not "Synergy" protocol. * Clipboard, file transfer, and cross-screen drag and drop are not supported due to the technical limitation, there is no way a standard USB HID device can do that, maybe an auxiliary app running on the host can help but I still don't have clear idea. * The mouse function doesn't work properly unless you set the screen size correctly, it may move too fast/slow or even jumpy. Usually the screen size should be the same as the host screen resolution. * Frequently connect/disconnect may cause the board fail to connect to the WiFi and/or Barrier/Deskflow server, you may need to power off the board and wait for a while before trying again. * The USB VID/PID are randomly picked and not registered, you are not authorized to produce and sell USB devices using these VID/PID, so you may need to change the code to use your own VID/PID if you have any business purpose. * The USB remote wakeup may not work because the standard forbids a suspended device consume too much current but this program needs much more than the standard says to keep Wi-Fi connected. I still haven't figured out how to keep the program running with the current <2.5mA. Of course you can choose a board with external power source such as a battery, but it seems to be an overkill. * The program can accept inputs only **after** the board successfully connects to the WiFi and Barrier/Deskflow server, it may be too late to use the board as a USB keyboard/mouse in BIOS/EFI, some main board that has always-on USB ports may work, but I haven't tested it, or you can use a USB hub that can supply power even if the host is off. * The program is compatible with Windows, macOs, and Linux. The keyboard function should work on any OS that supports USB HID devices, but the mouse function may have issues as it's in the absolute mode, not relative mode, which is known not to work on Android and iOS/iPadOS. * The built-in clipboard sharing function is incomplete, but it can be achieved with the [Clipper app](https://clipper.unwritten.codes), or the OS's built-in clipboard sharing function, such as [Clip Sync on Windows](https://support.microsoft.com/en-us/windows/about-the-clipboard-in-windows-c436501e-985d-1c8d-97ea-fe46ddf338c6) or [Universal Clipboard on macOs](https://support.apple.com/guide/mac-help/copy-and-paste-between-devices-mchl70368996/mac). ## TODO: - [x] Support media keys - [x] Re-configure without rebuilding - [x] Support other ESP32S3 boards - [x] Partially support clipboard, now plain ASCII text can be pasted. - [x] OTA update (via USB) - [ ] Support Mac special keys - [ ] Support TLS - [ ] NVS encryption - [ ] BLE HID support, and then support ESP32 and ESP32C3/C6 ## Licenses and Copyrights * This project is released under [MIT license](LICENSE). * The `esp_hal_smartled.rs` file is taken from [esp-hal-community repo](https://github.com/esp-rs/esp-hal-community), which is licensed under [MIT License](https://github.com/esp-rs/esp-hal-community/blob/main/LICENSE-MIT) and [Apache License, version 2.0](https://github.com/esp-rs/esp-hal-community/blob/main/LICENSE-APACHE). * Some code snippets in the `gentable.c` were taken from [Barrier repo](https://github.com/debauchee/barrier) and licensed under [GPLv2](https://github.com/debauchee/barrier/blob/master/LICENSE). The main project only utilizes the output of these snippets, not the code itself, and therefore is not subject to the GPL license. * Animated emoji images are taken from [Google Font Project](https://googlefonts.github.io/noto-emoji-animation/), which is licensed under [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/). * Any other third-party libraries or tools used in this project are subject to their own licenses and copyrights.
