qmk / qmk_configurator

The QMK Configurator
http://config.qmk.fm
689 stars 343 forks source link

[Bug] crkdb_r2g not working with current .hex file #1305

Closed marcin-jakub-sroka closed 1 year ago

marcin-jakub-sroka commented 1 year ago

Describe the Bug

I think something is broken in compiling json layout for crkdb_r2g.

I changed my keyboard configuration in https://config.qmk.fm, compiled there to .hex file, downloaded both .hex and .json files, but after I flashed my keyboard with QMK Toolbox (https://github.com/qmk/qmk_toolbox/releases/tag/0.2.2) it DOES NOT WORK properly. Symptoms:

First I thought that something was wrong with my changed layout (web configurator shouldn't generate wrong layout anyway) but I compiled old .json file and the result was pretty much the same. I tried upgrading QMK Toolbox with pre-release (https://github.com/qmk/qmk_toolbox/releases/tag/beta) with no success. I tried to compile locally my layout with docker image qmkfm/qmk_configurator:latest in Fedora WSL2 but the result is the same - .hex file is exactly the same and so the way my keyboard works after being flashed.

Last time I compiled my configuration on 26 of may. Everything is OK after flashing with .hex file compiled on 26 of may.

Additional Context?

No response

yanfali commented 1 year ago

Did you flash both sides? With enough time flashing just one side results in a broken keyboard.

marcin-jakub-sroka commented 1 year ago

Did you flash both sides? With enough time flashing just one side results in a broken keyboard.

What do you mean? The left side is attached to computer with USB cable, and the right to the left with TRRS cable. I flash the same way with new .hex file, and with old .hex file. The process seams to work properly - there are no warnings or errors. I use the following procedure:

keyboard-magpie commented 1 year ago

Please also flash the right side of the keyboard with the same hex file and report back.

marcin-jakub-sroka commented 1 year ago

Please also flash the right side of the keyboard with the same hex file and report back.

Ha! It's working! Thanks guys!

Something must have changed since flashing separately was not necessary earlier.

So my procedure now is as follows:

keyboard-magpie commented 1 year ago

For future reference:

https://docs.splitkb.com/hc/en-us/articles/360011949679-When-do-I-need-to-flash-my-microcontroller-

You can add to that list: if it has been a significant time since you last flashed.

marcin-jakub-sroka commented 1 year ago

For future reference:

https://docs.splitkb.com/hc/en-us/articles/360011949679-When-do-I-need-to-flash-my-microcontroller-

You can add to that list: if it has been a significant time since you last flashed.

Thanks. I'll remember that. BTW Do you know that "sroka" in Polish is "magpie" in English?

yanfali commented 1 year ago

One way to think about it is a split keyboard is two keyboards that cooperate to act as a single keyboard.

If one keyboard has a newer version of the firmware it can't talk to the other older because the protocol drifts over time as things are added or removed.

If you keep that in mind it makes more sense to flash both sides if it's been a while since you have done either side.

On Wed, Sep 13, 2023, 09:33 marcin-jakub-sroka @.***> wrote:

For future reference:

https://docs.splitkb.com/hc/en-us/articles/360011949679-When-do-I-need-to-flash-my-microcontroller-

You can add to that list: if it has been a significant time since you last flashed.

Thanks. I'll remember that. BTW Do you know that "sroka" in Polish is "magpie" in English?

— Reply to this email directly, view it on GitHub https://github.com/qmk/qmk_configurator/issues/1305#issuecomment-1717960691, or unsubscribe https://github.com/notifications/unsubscribe-auth/AARLSU2NAHDBRZDR4GKAZV3X2HN6DANCNFSM6AAAAAA4WU4YQU . You are receiving this because you commented.Message ID: @.***>