Skip to content
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

qmk configurator doesn't give a .bin or .hex file #1303

Open
1 task done
CrotoneFC opened this issue Sep 5, 2023 · 36 comments
Open
1 task done

qmk configurator doesn't give a .bin or .hex file #1303

CrotoneFC opened this issue Sep 5, 2023 · 36 comments

Comments

@CrotoneFC
Copy link

Information

  • None of the other issue templates apply

Description

when I try to download my keymap, after having it compiled, the only file I can download is a .uf2, which I can't use and can't convert to anything useful. What do I do?

@noroadsleft
Copy link
Member

What keyboard is this regarding? Saying you only get a .UF2 and not a .BIN or .HEX doesn't tell me anything actionable.

@CrotoneFC
Copy link
Author

What keyboard is this regarding? Saying you only get a .UF2 and not a .BIN or .HEX doesn't tell me anything actionable.

a tofu jr

@noroadsleft
Copy link
Member

If it's actually a Tofu Jr. PCB, .UF2 is the correct file format. It's an RP2040, which should show up like a USB flash drive when you enter Bootloader mode.

If it's a different bootloader, then your PCB isn't actually a Tofu Jr., and you'll need to set a different keyboard for your keymap.

@CrotoneFC
Copy link
Author

If it's actually a Tofu Jr. PCB, .UF2 is the correct file format. It's an RP2040, which should show up like a USB flash drive when you enter Bootloader mode.

If it's a different bootloader, then your PCB isn't actually a Tofu Jr., and you'll need to set a different keyboard for your keymap.

thank you so much for the clarification, i couldn’t find any online just like this one. Do you by any chance know how can i check for sure if my pcb is an RP2040? i bought the entire kit from kbdfans so i think it should be the tofu jr pcb.

@noroadsleft
Copy link
Member

Did you buy the keyboard already assembled? The best way to tell - though not the easiest as far as effort - would be to take it apart and look at the microcontroller.

Have you put your keyboard into bootloader yet? Try unplugging the USB cable, holding the top left key, connecting the cable and then releasing the key. If a new storage drive appears on your PC, that should be the RP2040 bootloader.

There's a short build video for a Tofu Jr on YouTube here. At 4:14 there's a decent shot of the PCB - one of the black squares on the bottom side should look like the image of an RP2040 microcontroller as shown on raspberrypi.com, if indeed your keyboard is a Tofu Jr.

@CrotoneFC
Copy link
Author

ok perfect. i managed to get to the bootloader mode and flash the new keymap but there's a problem. Some time ago I tried to remap the keyboard and I managed to do it on QMK configurator just by compiling it, and now the keys i modified that time won't change binding (e.g. i set the page up key to be an F10, and even if in the new keymap it is a page up again it still works as an F10)

@CrotoneFC
Copy link
Author

I'm pretty confused by the situation and very sorry for bothering yo so much, but you've been already a saviour to me, thank you so much

@noroadsleft
Copy link
Member

Curious: you're now the second person this week who's reported flashing a Configurator firmware to their board and not had the changes go into effect on their board. 🤨

@CrotoneFC
Copy link
Author

i mean it changed the keys that weren't already changed before, so that's puzzling to me

@noroadsleft
Copy link
Member

Do you have a JSON keymap export for your board? If so, could you post it here?

@CrotoneFC
Copy link
Author

CrotoneFC commented Sep 7, 2023

{
  "version": 1,
  "notes": "",
  "documentation": "\"This file is a QMK Configurator export. You can import this at <https://config.qmk.fm>. It can also be used directly with QMK's source code.\n\nTo setup your QMK environment check out the tutorial: <https://docs.qmk.fm/#/newbs>\n\nYou can convert this file to a keymap.c using this command: `qmk json2c {keymap}`\n\nYou can compile this keymap using this command: `qmk compile {keymap}`\"\n",
  "keyboard": "dztech/tofu/jr/v1",
  "keymap": "dztech_tofu_jr_v1_layout_65_ansi_mine",
  "layout": "LAYOUT_65_ansi",
  "layers": [
    [
      "KC_ESC",
      "KC_1",
      "KC_2",
      "KC_3",
      "KC_4",
      "KC_5",
      "KC_6",
      "KC_7",
      "KC_8",
      "KC_9",
      "KC_0",
      "KC_MINS",
      "KC_EQL",
      "KC_BSPC",
      "KC_SLSH",
      "KC_TAB",
      "KC_Q",
      "KC_W",
      "KC_E",
      "KC_R",
      "KC_T",
      "KC_Y",
      "KC_U",
      "KC_I",
      "KC_O",
      "KC_P",
      "KC_LBRC",
      "KC_RBRC",
      "KC_BSLS",
      "KC_PGUP",
      "KC_CAPS",
      "KC_A",
      "KC_S",
      "KC_D",
      "KC_F",
      "KC_G",
      "KC_H",
      "KC_J",
      "KC_K",
      "KC_L",
      "KC_GRV",
      "KC_QUOT",
      "KC_ENT",
      "KC_PGDN",
      "KC_LSFT",
      "KC_Z",
      "KC_X",
      "KC_C",
      "KC_V",
      "KC_B",
      "KC_N",
      "KC_M",
      "KC_COMM",
      "KC_DOT",
      "KC_SCLN",
      "KC_RSFT",
      "KC_UP",
      "KC_END",
      "KC_LCTL",
      "KC_LGUI",
      "KC_LALT",
      "KC_SPC",
      "KC_RALT",
      "KC_RGUI",
      "KC_RCTL",
      "KC_LEFT",
      "KC_DOWN",
      "KC_RGHT"
    ],
    [
      "QK_GESC",
      "KC_F1",
      "KC_F2",
      "KC_F3",
      "KC_F4",
      "KC_F5",
      "KC_F6",
      "KC_F7",
      "KC_F8",
      "KC_F9",
      "KC_F10",
      "KC_F11",
      "KC_F12",
      "KC_DEL",
      "KC_HOME",
      "KC_TRNS",
      "RGB_TOG",
      "RGB_MOD",
      "RGB_HUI",
      "RGB_HUD",
      "RGB_SAI",
      "RGB_SAD",
      "RGB_VAI",
      "RGB_VAD",
      "KC_TRNS",
      "KC_PSCR",
      "KC_SCRL",
      "KC_PAUS",
      "QK_BOOT",
      "KC_PGUP",
      "KC_CAPS",
      "RGB_SPI",
      "RGB_SPD",
      "KC_TRNS",
      "KC_TRNS",
      "KC_TRNS",
      "KC_TRNS",
      "KC_TRNS",
      "KC_TRNS",
      "KC_TRNS",
      "KC_TRNS",
      "KC_TRNS",
      "EE_CLR",
      "KC_PGDN",
      "KC_LSFT",
      "KC_TRNS",
      "KC_TRNS",
      "KC_TRNS",
      "KC_TRNS",
      "KC_TRNS",
      "NK_TOGG",
      "KC_TRNS",
      "KC_TRNS",
      "KC_TRNS",
      "KC_TRNS",
      "KC_TRNS",
      "KC_VOLU",
      "KC_MUTE",
      "KC_TRNS",
      "KC_TRNS",
      "KC_TRNS",
      "KC_TRNS",
      "KC_TRNS",
      "KC_TRNS",
      "KC_TRNS",
      "KC_MPRV",
      "KC_VOLD",
      "KC_MNXT"
    ],
    [
      "KC_TRNS",
      "KC_TRNS",
      "KC_TRNS",
      "KC_TRNS",
      "KC_TRNS",
      "KC_TRNS",
      "KC_TRNS",
      "KC_TRNS",
      "KC_TRNS",
      "KC_TRNS",
      "KC_TRNS",
      "KC_TRNS",
      "KC_TRNS",
      "KC_TRNS",
      "KC_TRNS",
      "KC_TRNS",
      "KC_TRNS",
      "KC_TRNS",
      "KC_TRNS",
      "KC_TRNS",
      "KC_TRNS",
      "KC_TRNS",
      "KC_TRNS",
      "KC_TRNS",
      "KC_TRNS",
      "KC_TRNS",
      "KC_TRNS",
      "KC_TRNS",
      "KC_TRNS",
      "KC_TRNS",
      "KC_TRNS",
      "KC_TRNS",
      "KC_TRNS",
      "KC_TRNS",
      "KC_TRNS",
      "KC_TRNS",
      "KC_TRNS",
      "KC_TRNS",
      "KC_TRNS",
      "KC_TRNS",
      "KC_TRNS",
      "KC_TRNS",
      "KC_TRNS",
      "KC_TRNS",
      "KC_TRNS",
      "KC_TRNS",
      "KC_TRNS",
      "KC_TRNS",
      "KC_TRNS",
      "KC_TRNS",
      "KC_TRNS",
      "KC_TRNS",
      "KC_TRNS",
      "KC_TRNS",
      "KC_TRNS",
      "KC_TRNS",
      "KC_TRNS",
      "KC_TRNS",
      "KC_TRNS",
      "KC_TRNS",
      "KC_TRNS",
      "KC_TRNS",
      "KC_TRNS",
      "KC_TRNS",
      "KC_TRNS",
      "KC_TRNS",
      "KC_TRNS",
      "KC_TRNS"
    ],
    [
      "KC_TRNS",
      "KC_TRNS",
      "KC_TRNS",
      "KC_TRNS",
      "KC_TRNS",
      "KC_TRNS",
      "KC_TRNS",
      "KC_TRNS",
      "KC_TRNS",
      "KC_TRNS",
      "KC_TRNS",
      "KC_TRNS",
      "KC_TRNS",
      "KC_TRNS",
      "KC_TRNS",
      "KC_TRNS",
      "KC_TRNS",
      "KC_TRNS",
      "KC_TRNS",
      "KC_TRNS",
      "KC_TRNS",
      "KC_TRNS",
      "KC_TRNS",
      "KC_TRNS",
      "KC_TRNS",
      "KC_TRNS",
      "KC_TRNS",
      "KC_TRNS",
      "KC_TRNS",
      "KC_TRNS",
      "KC_TRNS",
      "KC_TRNS",
      "KC_TRNS",
      "KC_TRNS",
      "KC_TRNS",
      "KC_TRNS",
      "KC_TRNS",
      "KC_TRNS",
      "KC_TRNS",
      "KC_TRNS",
      "KC_TRNS",
      "KC_TRNS",
      "KC_TRNS",
      "KC_TRNS",
      "KC_TRNS",
      "KC_TRNS",
      "KC_TRNS",
      "KC_TRNS",
      "KC_TRNS",
      "KC_TRNS",
      "KC_TRNS",
      "KC_TRNS",
      "KC_TRNS",
      "KC_TRNS",
      "KC_TRNS",
      "KC_TRNS",
      "KC_TRNS",
      "KC_TRNS",
      "KC_TRNS",
      "KC_TRNS",
      "KC_TRNS",
      "KC_TRNS",
      "KC_TRNS",
      "KC_TRNS",
      "KC_TRNS",
      "KC_TRNS",
      "KC_TRNS",
      "KC_TRNS"
    ]
  ],
  "author": ""
}

@CrotoneFC
Copy link
Author

it wouldn't let me attach the json file so I took down the code from vscode, this would be the keymap I flashed

@noroadsleft
Copy link
Member

image
image

I don't see a way for you to even switch layers in your keymap.

You should perhaps go on QMK Configurator's Key Tester and check that each key you press actually is doing what you expect it to do.

@CrotoneFC
Copy link
Author

i know that there's not a layer switch because I didn't put one, but I already checked on the key tester and by now the minus key works as an accent

@noroadsleft
Copy link
Member

What input language is your PC set to use?

@CrotoneFC
Copy link
Author

i'm really bugged it's like some key are hard wired to do a certain function and can't be changed

@CrotoneFC
Copy link
Author

What input language is your PC set to use?

american english

@noroadsleft
Copy link
Member

I already checked on the key tester and by now the minus key works as an accent

Has it worked like an accent the whole time you've had the board, or only since flashing new firmware? And is it always an accent, or do you sometimes get a minus sign?

@CrotoneFC
Copy link
Author

I already checked on the key tester and by now the minus key works as an accent

Has it worked like an accent the whole time you've had the board, or only since flashing new firmware? And is it always an accent, or do you sometimes get a minus sign?

no when I got the board it was default, but then I compiled the new bindings on qmk configurator and I don't know how it just worked like that. Now the keys that were changed always work like that, never got a minus or anything different

@CrotoneFC
Copy link
Author

maybe if there was a way to completely reset the keyboard and the flash in the new keymap it would work?

@noroadsleft
Copy link
Member

Try flashing the firmware in the attached ZIP file; I just compiled it.

It should be a standard US English QWERTY layout, except for the top two keys on the far-right column, which are QK_BOOT (Jump to Bootloader Mode) and EE_CLR (Clear EEPROM), respectively.

image

dztech_tofu_jr_v1_crotonefc_test.zip

@CrotoneFC
Copy link
Author

CrotoneFC commented Sep 7, 2023

everything works as it should except for the plus that still works as the accent

@CrotoneFC
Copy link
Author

again thank you so much for the effort you're putting in

@noroadsleft
Copy link
Member

Random thought; might be nothing: Tap the EE_CLR key that I placed, wait a bit, and then reboot the board (unplug then replug should be fine).

@CrotoneFC
Copy link
Author

nope, still the accent is there

@CrotoneFC
Copy link
Author

i can't really see a reason why it should be there still

@lesshonor
Copy link
Contributor

What OS are you running?
Can you please take a screenshot of your language settings? On Windows, these settings are under Settings > Language. Mine looks like this:
Windows language settings

@CrotoneFC
Copy link
Author

image

@lesshonor
Copy link
Contributor

Please confirm that the language icon in your taskbar is set to US English for the keyboard layout:
image

@CrotoneFC
Copy link
Author

yes

@lesshonor
Copy link
Contributor

lesshonor commented Sep 7, 2023

Can you take screenshots to make sure?
You will also need to confirm that the layout and language are also US English. There are a lot of ways to get this mixed up now -- Control + Shift, Left Alt + Shift, and Windows + Spacebar will all modify your input keyboard layout and/or language.
https://www.digitalcitizen.life/change-keyboard-language-windows-11/

@CrotoneFC
Copy link
Author

rn i can't take a screen but i can confirm that the language has always been us english

@lesshonor
Copy link
Contributor

If you're only interested in working with US English keyboards, you can uninstall the Italian keyboard layouts:
image

@CrotoneFC
Copy link
Author

i'd leave it for the laptop kayboard which is italin layout

@CrotoneFC
Copy link
Author

i'm pretty sure it's not a problem of the language setting

@CrotoneFC
Copy link
Author

probably the question is senseless but is there a way to completely reset the PCB to factory settings and then flashing it afterwards?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants