Hey all, the overall experience with the M60_A has been amazing (Team Lake, represent!) with one exception, running my custom keymap. To save others the trouble, here are some helpful tips for those that aren't using the configurator and instead trying to use QMK from source (most likely because you already have a keymap defined for another keyboard).
If you are using more than four layers you will want to set "
DYNAMIC_KEYMAP_ENABLE=no" in your
rules.mk. You might also be able to increase the number of supported layers, but I'm not sure at which point you start running out of flash. You'll know if you are having this problem if you try to switch to a new layer and the keys do nothing (answers the question as to why my Zeal60 boards stopped working).
Currently (but likely to be fixed soon with the merge of my
PR) the
rama/m60_a keyboard definition doesn't support the
60_hhkb layout. You will want to add it if you use layouts (and, frankly everyone should be using layouts). Once you have it in place you can use "
make rama/m60_a:your_keymap_name:dfu" to build and flash your device.
To put the board into bootloader (programming) mode hold down the top-left key (usually
Escape but I'll not be so presumptuous). This will also clear the EEPROM so if you set backlight colors they will be reset to the default. I recommend putting a
RESET key in your keymap to enter bootloader without clearing the EEPROM or having to unplug/replug the USB cable each time (it can lead to scratching the back plate, to which I can testify).