tokyo60 json file

tokyo60_custom.json

{"keyboard":"tokyo60","keymap":"tokyo60_custom","layout":
"LAYOUT_60_hhkb","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_GRV","KC_BSPC",
"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_CAPS","KC_A","KC_S","KC_D","KC_F","KC_G","KC_H","KC_J","KC_K","KC_L","KC_SCLN","KC_QUOT","KC_ENT",
"KC_LSFT","KC_Z","KC_X","KC_C","KC_V","KC_B","KC_N","KC_M","KC_COMM","KC_DOT","KC_SLSH","KC_LSFT","MO(1)",
"KC_LCTL","KC_LALT","KC_SPC","KC_RALT","KC_RGUI"],
["KC_PWR","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_INS","KC_DEL","KC_TRNS","RGB_TOG","RGB_MOD","RGB_RMOD","BL_TOGG","BL_STEP","KC_TRNS","KC_TRNS","KC_PSCR","KC_SLCK","KC_PAUS","KC_UP","KC_TRNS","RESET",
"KC_TRNS","KC_VOLD","KC_VOLU","KC_MUTE","KC_MSTP","KC_TRNS","KC_HOME","KC_TRNS","KC_TRNS","KC_PGUP","KC_LEFT","KC_RGHT","KC_TRNS",
"KC_TRNS","KC_TRNS","KC_TRNS","KC_TRNS","KC_TRNS","KC_TRNS","KC_END","KC_TRNS","KC_TRNS","KC_PGDN","KC_DOWN","KC_TRNS","KC_TRNS",
"KC_TRNS","KC_TRNS","KC_TRNS","KC_TRNS","KC_TRNS"]]}

my tokyo60 json file.

got it, the link @ massdrop was alittle borked but I got here.

Nice. thanks.

One minor difference: I didn't define any of the keys in my layer 1 map as transparent. It doesn't seem like that should cause a problem, but that's the only significant difference I can see between mine that worked and yours that isn't. I'll keep looking at it.

could you try generating the hex file for me and post it here? I am not sure if it is my browser or PC that's causing the problem with the compile process.

do you have discord?

my discord tag is schlep

I'm working, no discord behind a corporate firewall

So I created firmware with your JSON and successfully flashed it onto my Tokyo60. The bad news is now I can't flash mine back! Something is up with the mapping for FN I think which is keeping the PAUSE from being recognized. The further bad news is my preferred map is much different than yours :)

Good news. The purple reset button on the bottom of the PCB will put the keyboard in to DFU mode.

Better news, I figured out why L_SHIFT+R_SHIFT+PAUSE fails to put the board into boot loader mode. Your base layer map has two L_SHIFTs and no R_SHIFT. Adding a R_SHIFT made things work again.

As far as it not taking your keymap, I couldn't recreate that.

My keymap: https://gist.github.com/JnyJny/14da6be5dfb9f856efa927dfbdfb982c