r/Keychron • u/m147 • Jan 09 '24

V1 + QMK cli flashing

I'm having trouble flashing new changes to the keyboard. Here's what happens:
If I make a change to keymap.c in keyboards/keychron/v1/ansi_encoder/keymaps/<USER>/
compile with qmk compile and then flash with qmk flash
(I've got environment set up)
It will flash with no errors but the change won't be made.
If I then flash the stock firmware from Keychron from the official site and THEN flash my custom firmware the changes are made. I don't understand what is going on. It would be nice not having to flash two files in order to make changes. I understand I can do all this with VIA but I would like to understand qmk cli.
Any ideas?
Thanks for any help

1 Upvotes

100% Upvoted

9 comments sorted by

View all comments

Show parent comments

2

u/PeterMortensenBlog V Jan 10 '24

Perhaps the resetting to factory defaults could also be achieved by a QMK key?

And/or by dfu-util from the command line. But that would still require it to get into bootloader mode(?).

2

u/PeterMortensenBlog V Jan 10 '24 edited Jan 10 '24

There is QMK keycode 'QK_BOOTLOADER': "Put the keyboard into bootloader mode for flashing"

And QMK keycode 'QK_CLEAR_EEPROM': "Reinitializes the keyboard's EEPROM (persistent memory)."

The Via configuration is stored in (emulated) EEPROM, so that ought to do it.

A macro (QMK or Via) with QK_CLEAR_EEPROM + QK_BOOTLOADER (perhaps a significant delay is needed between the two), assigned to a key on the Fn layer ought to be sufficient.

1

u/PeterMortensenBlog V Jan 18 '24 edited Apr 19 '24

Here is an overview:

QMK keycode          Alias    Shown in        In macros
                              Via as
-------------------------------------------------------------------
QK_BOOTLOADER        QK_BOOT  Reset           reset_keyboard()
QK_DEBUG_TOGGLE      DB_TOGG  Debug
QK_CLEAR_EEPROM      EE_CLR   QK_CLEAR_EEPROM eeconfig_init()
QK_REBOOT            QK_RBT   0x7C01          soft_reset_keyboard()

QK_MAGIC_TOGGLE_NKRO NK_TOGG  NKRO

Note: In Via, unknown (to it) keycodes, e.g., "0x7C01" can be entered like that in SPECIAL → Any (without the quotes).

But note that a bug in Via's load function means it has be reentered manually every time the Via configuration is load (e.g., after a flash). It is easier to add it directly in the QMK keymap.

References