This project forked from smplman/qmk_firmware
Open-source keyboard firmware for Atmel AVR and Arm USB families
Home Page: https://qmk.fm
License: GNU General Public License v2.0
This keyboard is very similar to the K552, which is very likely just a tenkeyless version of the K551 under the hood (unless not). Should be easy to implement. Also, I have it, and it isn't supported, so that's the main reason I'm pitching this suggestion here. :-)
Not sure if this might be of any use, but the vendor ID is 0C45 and the device ID is 5004.
I'm wondering what is the greatest barrier to implement bluetooth support for Sonix boards. Is it a limitation of current software design, lack of knowledge on hardware at hand or something other. Also I'm curious how can we help to implement bluetooth support for a wider range of keyboards. I created this issue with the intent to start a discussion about this. The best would be if someone could please explain what's missing to make this happen.
This is what I can provide for this keyboard:
lsusb result:
ID 0c45:8006 Microdia Dual Mode Camera (8006 VGA)
Chip: HFD2201KBA
Board: GK4105M-RGB-HFD (switches are soldered directly on board so i can't take pictures of the front board right now)
Brand: Aukey KM-G12 (according to this OpenRGB issue it may to be an OEM clone of "Sandberg Firestorm Mech Keyboard")
Layout: 100%
You can enter bootloader by connecting boot pin to a ground source.
In bootloader vid and pid is: 0c45:7040.
If you press a key combination with 3 or 4 keys hold down, the keyboard either locks up or spams bbbbb or 3b3b3b3b. The bug is not 100% consistently reproducible. The most reliable method I've found to reproduce is to simply mash a lot of butons on the keyboard rapidly.
If you use sn32 branch instead of sn32_master branch, the bug goes away.
Currently the 'Compile Firmware' check will not fail if there are boards that don't build.
So it is possible to merge code that doesn't even compile.
It would be nice if the check gave real feedback if a PR is save to merge.
For example #154 would have been caught a month earlier.
The red Caps lock indicator LED does not work on the Keychron K3 (v1, Optical RGB). Instead of turning on/off when capslock is pressed, it is always dimly on.
The build for the RGB Keychron K3 with optical switches works if the OPTICAL_MATRIX macro is defined, but the Caps lock indicator feature does not seem to be working. The LED is expected to turn on if Caps lock is enabled and off if Caps lock is disabled. Instead, the LED is always in a dim-on state, which could indicate a floating gate condition.
PCB version: Ver 1.4/20201030
Built from 03c781d with arm-none-eabi-gcc version 10.1.0 on Windows 10 with QMK MSYS 1.5.2.
I'm new to mechanical keyboard and recently got Keychron K14 (White backlit). Seems like sm32_master repo contains only code for RGB version of this keyboard.
Am I missing something? Can I help to implement/port RGB firmware to White version?
What are the issues with it (I've heard that Keychron business model is somehow related with using simpler chips on White backlit keyboards which have lesser amount of memory - is it true)?
Thanks!
In my opinion, I think it is a very useful function. but I don't know why it's not implemented in this fork yet
more information about the function here
Declaring an RGB matrix with columns pins with shared PWM results in the A pins being omitted from the RGB matrix.
Example from my particular board (SN32F248B) :
#define LED_MATRIX_COL_PINS { A8, A9, C0, C1 (...rest omitted) }
Being that A8 and C0 shares PWM08 (A and B respectively) and A9 and C1 shares PWM09 (A and B respectively)
[del]
After we have many changes of PWM, but we still missing an LED flush function. Since most keyboard doesn't have LED indicator for Capslock. So rgb_matrix_indicators_user on keymap really helped for that, but we missing LED flush so it make a flickering led color when toggle it.
An error occurred while flashing the keyboard.
I used an auto-compiled firmware #562 from a branch "k87_backlight_test".
Used program XONiX USB MCU ISP Tool version 2.3.2.1 with parameters VID = 320F and PID = 502A.
The firmware ends with an "Protocol Handshake Error!" in the log:
Load File...
---------------------------------------
Bin File Check Sum : DB60
Open USB HID Device...
----VID: 320F PID: 502A----- No. 001
Command Header :Get Firmware Version (0x01) Failed!!
Hey, what is the state of this Project? The last activity is 1,5 months ago and there are 37 MRs piling up. I know this is solely a fun project, but is there any way it can be supported, to free resources or improve motivation? I can offer review and some development resources, but I need something, too (too many projects that got abandoned despite people putting efforts into it). ;) Maybe a roadmap?
Recently I bought a SPC Gear GK630 and I'm wondering how much work is needed to use this firmware with this keyboard. I see that other models from the same vendor are already supported (GK530/GK540 but they're using a slightly different MCU).
I have some basic knowledge about QMK and electronics and I'd like to add support for this keyboard but I'm not sure where to start :)
I believe that this great firmware was started on the work of reverse engineering the Dierya now the Kemove DK63... I wonder why the name change!
This keyboard is stated as supported in the Keyboard database but I cannot find its configuration in the source tree.
Could this keyboard be easily integrated ?
Thank you
The gmmk has a few shortcut keys to use with the fn key and i would like to see them comeback (media and volume controls mainly). I also noticed that the n key rollover isnt working anymore and it now registers only 6 keys at once, there was a shortcut with the stock firmware to switch between 6 key and n-key rollover
The documentation in the "Compatible Keyboards" section states the Keychron K3 is supported, but doesn't specify if the K3 Version 2 is also supported. If is already supported please add it to the documentation.
Default RGB animation is rainbow
However, when the usb driver kicks in, it switches to red breathing. You can observe this behavior by unplugging the keyboard and switching to battery ( bluetooth) mode.
Need to figure out this inconsistency and see if it is our code, or QMK upstream behavior
I'm trying to make an ISO firmware for my Keychron K8.
This is all new to me, but is the K8 ISO folder not missing an info.json file?
Kind regards
Michael Tandrup
Denmark
Keychron K* will break the CI status until the migration to this folder structure is complete. Any resulting artifacts from CI are fine and safe to flash in the meantime.
Maintainers please give us a hand to update all devices so this can go away.
You can ref the K8 and K12 for implementation examples
Current sn32_master, despite of supporting the keychron K7, is not working on my brand new keyboard.
After probin the key matrix and the led matrix pins to microcontroller, I managed to start using it as a keyboard.
What should I do to properly add this code to the repository ( my understanding i that current changes should only apply to the non-optical version of the K7 keyboard)
pr #268 has the changes that make my device work as a keyboard:
anywone having same issue ?
I'd like to see a full and in some ways improved support for Redragon Brahma, the stock software only allows to add something on G keys through the keyboard itself, not by windows software, that's generally the main issue I have with stock firmware, it's a bit clunky, but otherwise functional, cooler RGB features might be welcome, but IMHO, not a priority in any way, personally, I'm fine with 1-2 colors addressable through the keyboard.
Anyways in hopes that someone picks it up,
Sincerely Xlen.
The current pre-compiled firmware for the Keychron C1 with white backlight version causes the keyboard to be unresponsive and the backlights to stop working.
After flashing the current pre-compiled firmware for the Keychron C1 white backlight version, the keyboard does not register input and the backlight does not work.
Keyboard: Keychron C1 White backlight version
Operating system: Mac OS Big Sur
Any keyboard related software installed?
The bin files for the Keychron C1 plain default version does partially restore functionality but with no backlight support.
Title describes all)
I'm trying to build firmware for a Redragon K580 and get the error message above.
Status LEDs are unresponsive if firmware is built with VIA/OpenRGB support. The cause of this issue is the ASUS USB Charger Plus, there are two workarounds. Either change your VID or you uninstall ASUS USB Charger Plus.
Hi, I noticed you have support for both the keychron c1 rgb and the keychron c2 wih white leds. I was wondering if there was a way you could add support for the keychron c2 rgb edition, since this is a combination of these 2 boards.
I just bought a GamaKay K77 with the hopes of rebinding the numpad to the F keys. Unfortunately, there aren't any drivers available for this keyboard besides an "updating" (?) software provided on the Banggood page (it also detects the VID and PID, which are 0x0C45 and 0x7698 respectively). It would also be nice to see some more RGB configurations for this board, since it also has lights around the border that are separately controlled from the lights under the keys! Found this repo today looking around for ways to customize this board and this community seems so talented and helpful. Hoping someone smarter than me can figure this one out! :)
We have keyboards with many revisions. That means multiple duplicate keymaps and layouts. That also means headache to anyone maintaining them.
Plan of attack:
keychron/k*/*/keymaps should move up to keychron/k*/keymapslayout for keymaps and in rules.mk to use. See here.via directory with an appropriate rules.mk enabling via flag and the json can simply be in the keyboard directory. No need for another via keymap. Example of this hereFlashed QMK onto K7 with 0x00 offset, after flashed everything seems OK, but when I plug out and plug in again, my K7 become unresponsiable for computer, only backlight can work. (Only on AMD CPUs, Intel's can work normally)
In device manager:
ROW2COL (Redragons) have an RGB glitch on R5 ( 6 row boards) and F key bug has been observed in neighboring keys in R0.
F key bug is related to fast switching. Introducing delays like this qmk@82aa9ad will fix it.
RGB glitch is weird. Might be related, but needs more investigation. COL2ROW keyboards are not affected
I would really like official support for the Redragon K553 keyboard, since i have tried flashing K552 Rev 2 firmware onto a K553, and that doesn't work - the keyboard is not responding, no backlight, doesn't show up in lsusb unless I put it into Bootloader mode by shorting BOOT pin to ground.
Hi,
I have just setup the environment for compiling a custom K552 firmware. I'am using the branch named sn32_master_openrgb.
Compiling with the command "qmk compile -kb redragon/k552/rev2 -km default", the following error appears:
Compiling: quantum/rgb_matrix/rgb_matrix.c : In function 'eeconfig_update_rgb_matrix_default':
quantum/rgb_matrix/rgb_matrix.c:91:45: error: 'RGB_MATRIX_CYCLE_LEFT_RIGHT' undeclared (first use in this function); did you mean 'RGB_MATRIX_LED_FLUSH_LIMIT'?
I have check that the following branches compile properly with the same command:
Am I doing something wrong?
Best Regards,
Víctor
My current dev setup is through CI. That means downloading autogenerated .zip files.
This is how the directory looks like.
Having the build script append the current HEAD in some format would make easier to identify what's what when testing multiple setups
Would really love support for Royal Kludge RK84, it's a pretty popular budget option
https://www.techpowerup.com/review/royal-kludge-rk84-keyboard/4.html
here's a disassembly, might help
Trying to suspend the RGB on PC sleep/shutdown and resume on wake/boot.
This part works. It turns off the RGB
void suspend_power_down_user(void) {
rgb_matrix_set_suspend_state(true);
}
This part does not work. It is supposed to turn the RGB back on.
void suspend_wakeup_init_user(void) {
rgb_matrix_set_suspend_state(false);
}
#define RGB_DISABLE_WHEN_USB_SUSPENDED true
is set in config.h
The indicator LEDs (Num Lock, Caps Lock, Scroll Lock) are not working. Figure it out.
I flashed the latest firmware available and I found various bugs. This is a documentations of them.
1. The NKRO no longer works and you only get 5-kro.
2. The alt-gr does not work.
3. It does not work with via (But i suppose that that is deactivated on purpose as is a specific build flag)
4. The scroll lock led does not work on Linux (more in the next comment). Tested in Fedora, Arch (KDE) and Linux Mint.
My model is the ISO version and it could cause key-map related bugs.
All the issues have been fixed!
Reports as VID = 0C45, PID = 5004. I believe these to be the same as the Redragon K556 (source: https://youtu.be/2MHtLEiXaXg?t=1195). This is my first time taking a keyboard apart, but managed to take some pictures of the inside, and what I believe to be the chip running everything (apologies for the quality). As I'm new to this kind of stuff, I doubt I can solder anything onto the board (I don't even have a soldering iron), would love to hear if there's any way around this.
I'd like full support for Redragon K587 as Evision software is sh**.
I've been able to flash the QMK firmware and everything works for my Keychron K6 but I cannot load the layout in VIA.
VIA will recognize the keyboard and seems like it connects to it, but the layout is never loaded and as such I can't make any changes
PFPA is not declared for boards requiring PWM B side control.
That results in affected columns missing rgb control and staying off
Models affected: keychron k4,c1 and possibly k8
// PWM0-2 is B for the k4
SN_PFPA->CT16B1 = 0x00000007;
this is the old way of tackling this. It might be worth seeing if we can handle that in chibios level instead of setting the registers directly in matrix code.
This is causing a mess and potential legal issues.
TODO: fix the ID's by Model/Layout following this convention
| VID | PID | Model | Layout | PID | Model | Layout |
|---|---|---|---|---|---|---|
| 0x3434 | 0xFE00 | K1 | ANSI | 0xFE20 | C1 | ANSI |
| 0x3434 | 0xFE01 | ISO | 0xFE21 | ISO | ||
| 0x3434 | 0xFE02 | K2 | ANSI | 0xFE22 | C2 | ANSI |
| 0x3434 | 0xFE03 | ISO | 0xFE23 | ISO | ||
| 0x3434 | 0xFE04 | K3 | ANSI | 0xFE24 | C3 | ANSI |
| 0x3434 | 0xFE05 | ISO | 0xFE25 | ISO | ||
| 0x3434 | 0xFE06 | K4 | ANSI | 0xFE26 | C4 | ANSI |
| 0x3434 | 0xFE07 | ISO | 0xFE27 | ISO | ||
| 0x3434 | 0xFE08 | K5 | ANSI | 0xFE28 | C5 | ANSI |
| 0x3434 | 0xFE09 | ISO | 0xFE29 | ISO | ||
| 0x3434 | 0xFE0A | K6 | ANSI | 0xFE2A | C6 | ANSI |
| 0x3434 | 0xFE0B | ISO | 0xFE2B | ISO | ||
| 0x3434 | 0xFE0C | K7 | ANSI | 0xFE2C | C7 | ANSI |
| 0x3434 | 0xFE0D | ISO | 0xFE2D | ISO | ||
| 0x3434 | 0xFE0E | K8 | ANSI | 0xFE2E | C8 | ANSI |
| 0x3434 | 0xFE0F | ISO | 0xFE2F | ISO | ||
| 0x3434 | 0xFE10 | K9 | ANSI | 0xFE30 | C9 | ANSI |
| 0x3434 | 0xFE11 | ISO | 0xFE31 | ISO | ||
| 0x3434 | 0xFE12 | K10 | ANSI | 0xFE32 | C10 | ANSI |
| 0x3434 | 0xFE13 | ISO | 0xFE33 | ISO | ||
| 0x3434 | 0xFE14 | K11 | ANSI | 0xFE34 | C11 | ANSI |
| 0x3434 | 0xFE15 | ISO | 0xFE35 | ISO | ||
| 0x3434 | 0xFE16 | K12 | ANSI | 0xFE36 | C12 | ANSI |
| 0x3434 | 0xFE17 | ISO | 0xFE37 | ISO | ||
| 0x3434 | 0xFE18 | K13 | ANSI | 0xFE38 | C13 | ANSI |
| 0x3434 | 0xFE19 | ISO | 0xFE39 | ISO | ||
| 0x3434 | 0xFE1A | K14 | ANSI | 0xFE3A | C14 | ANSI |
| 0x3434 | 0xFE1B | ISO | 0xFE3B | ISO | ||
| 0x3434 | 0xFE1C | K15 | ANSI | 0xFE3C | C15 | ANSI |
| 0x3434 | 0xFE1D | ISO | 0xFE3D | ISO | ||
| 0x3434 | 0xFE1E | K16 | ANSI | 0xFE3E | C16 | ANSI |
| 0x3434 | 0xFE1F | ISO | 0xFE3F | ISO |
K556 should be K530.
There is no jump loader for K530, the K556 worked.
I added this as extra information.
Johns
A patch to fix it, I you prefer a pull request let me know.
diff --git a/keyboards/redragon/k530/readme.md b/keyboards/redragon/k530/readme.md
index 987b24fc1..28655ef8d 100644
--- a/keyboards/redragon/k530/readme.md
+++ b/keyboards/redragon/k530/readme.md
@@ -1,6 +1,6 @@
-# Redragon K556 Devarajas
+# Redragon K530 Devarajas
-K556
+K530
Keyboard Maintainer: [Adam Honse](https://github.com/CalcProgrammer1)
Based on Kemove DK63 by: [Stephen Peery](https://github.com/smp4488)
@@ -8,6 +8,8 @@ Hardware Supported: SN32F248BF
Make example for this keyboard (after setting up your build environment):
- make redragon/k556:default
+ make redragon/k530:default
+
+Flash `jumploader-redragon_k556.bin` first and only once.
See the [build environment setup](https://docs.qmk.fm/#/getting_started_build_tools) and the [make instructions](https://docs.qmk.fm/#/getting_started_make_guide) for more information. Brand new to QMK? Start with our [Complete Newbs Guide](https://docs.qmk.fm/#/newbs).
With firmware built from the latest sn32_master branch, the Keychron C1 (white backlight version) can't wake my computer from a suspended state. The keyboard's backlight and LEDs also don't turn off like they should when the computer is suspended. Neither of these problems happens with precompiled firmware from here, based on an older revision, so it seems to be a regression. I can't bisect it, though, due to problems building working firmware from any git revisions older than a certain point.
When the LEDs are set to off (0, 0, 0) on these keyboards, the LEDs are actually very dimly lit. I'm guessing this has to do with the PWM mode, where the first cycle of PWM doesn't keep the output low when the match register is 0. We may need code to initialize the PWM channels to their off state if the value is zero since we only run the PWM in one-shot mode (resetting it each cycle).
Compiling using the instructions does compile successfully but the result is glitchy(double keypresses)
Hi there, i had a problem when i try to compile Keychron K8 firmware using QMK_MSYS, the error says that "SN32F248B is not a valid matrix type" after i run make command, does anyone know what's wrong with this or is this a bug? thanks
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
Django
The Web framework for perfectionists with deadlines.
Laravel
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
Microsoft
Open source projects and samples from Microsoft.
Google
Google ❤️ Open Source for everyone.
Alibaba
Alibaba Open Source for everyone
D3
Data-Driven Documents codes.
Tencent
China tencent open source team.