-
-
Notifications
You must be signed in to change notification settings - Fork 40.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Feature Request] ESP32 and/or ESP8266 support? #9223
Comments
I remember looking at this a few years back, one of the reasons is because the ESP8266's USB port is actually going through a UART to USB bridge, so you can't use it to enumerate as a HID device and send HID reports. You can, however, implement something like V-USB if you put your mind to it, but that would require using other pins and wiring your own usb cable/port from it. Basically, it's not ideal. They're good IoT boards, but I don't see them being too useful as a USB keyboard. Also regarding the bluetooth stack, I've seen work on a nicer approach to managing the bluetooth stack in QMK. Not sure how things will proceed from there, but that approach might work if that is the case. |
The ESP chips run on the Xtensa architecture, which is completely different to the platforms we currently support (ARM and AVR). It would likely be a significant effort to add this entirely new one given that ChibiOS almost certainly would not accept it. Most importantly though, whoever does this would then be responsible for maintaining it. |
maybe add UART sending of key code, this way any board can simply be used as a bridge |
ESP32-S2 supports USB https://www.espressif.com/en/news/espressif-announces-%E2%80%A8esp32-s2-secure-wi-fi-mcu |
This should cover what's required, specifically the section "Adding support for a new MCU Family": Selecting an Arm MCU |
Could be great use 1 or 2 of these https://heltec.org/project/wifi-kit-32/ adapting ESPUSB library integrated with the custom keyboards.
all of these only ~$10 Or the new ESP32-S2 chipset with USB Console ~ $7 Dev Kit ESP32-S2-SAOLA-1R The best Option, using the chipset ESP32-S2 |
This issue has been automatically marked as stale because it has not had activity in the last 90 days. It will be closed in the next 30 days unless it is tagged properly or other activity occurs. |
I was poking at this a bit today and managed to get something.. well. not working. but at least compiling and linking. You can follow along over at https://hackaday.io/project/178232-lalboard/log/190758-investigating-qmk-on-the-esp32 if you're interested. |
Given that esp32 is supported by RIOT-OS, perhaps that would be worth investigating as a HAL? |
This issue has been automatically marked as stale because it has not had activity in the last 90 days. It will be closed in the next 30 days unless it is tagged properly or other activity occurs. |
Do you have a fork or something? I have the Logitech RF protocol working on the ESP8266 https://github.com/bilogic/logitech-unifying-device |
Yeah, I have a fork that's integrated with esp-idf, not RIOT-OS. But I don't have it published or anything yet. And It's not really an approach that would be acceptable to merge into mainline qmk. It basically builds qmk as a esp-idf module, and uses esp-idf to build the whole project. |
@JesusFreke do you mind sharing your work, i'm currently building dactyl manuform, and thinking about to add a bluetooth support. |
@JesusFreke yea, I'm keen to see what it can do too! |
This issue has been automatically marked as stale because it has not had activity in the last 90 days. It will be closed in the next 30 days unless it is tagged properly or other activity occurs. |
any news about it? |
It's interesting to have alternatives due IC shortage |
Any updates on this? |
zvecr has made significant progress with RIOT support- not with this in mind though. I'd say it's still a good way away from being at the point where you could be considering adding ESP32... |
At this stage asking for status updates is a hindrance rather than a help -- closing this issue until |
I'm wondering how hard it would be to get USB keyboard functionality working on an esp32-s3. That could be a good starting point to start delving deeper into the code. |
I may be wrong, but looking through the RIOT docs, it seems like the ESP32 is supported at this point. https://api.riot-os.org/group__cpu__esp32.html |
Is there any guide how to use RIOT with the QMK? |
Feature Request Type
Description
There are many inexpensive ESP32 and ESP8266 based dev boards with on-board bluetooth, li-po charging, wifi, and sometimes OLED screens. These seem like a great upgrade from our usual Teensy and Pro Micro dev boards given how feature rich they are, and the fact that they are even cheaper in a lot of cases than the Pro Micro.
Example 1
Example 2
Overall, it seems like moving away from the relatively expensive, hard to find, and frequently unavailable community-developed hardware solutions like the BlueNano, and towards the ecosystem of modern dev boards like these might enable significantly more wireless keyboards to start showing up. The missing piece seems to be QMK support
I was pretty surprised to not find any discussion about these dev boards in the keyboard community. Would it be possible to get official QMK support for them Or are there some technical reasons why it would not be possible?
The text was updated successfully, but these errors were encountered: