#Can't flash firmware onto nice!nano on MacOS 15.5

1 messages · Page 1 of 1 (latest)

digital eagle
#

I just made a keymap with nickcoutsos.github.io/keymap-editor , and I'm trying to flash it onto my typeractive corne, with the uf2 generated from this repo: haxybaxy/corne-wireless-view-zmk-config

Everytime I try to drag and drop the firmware onto the nice!nano I get this error:

The Finder can’t complete the operation because some data in “corne_left nice_view_adapter nice_view-nice_nano_v2-zmk.uf2” can’t be read or written.(Error code -36)

and the keymap stays the exact same as before, so the reflashing does not work.

When I try with the terminal I get this error:

could not copy extended attributes to /Volumes/NICENANO/corne_left nice_view_adapter nice_view-nice_nano_v2-zmk.uf2: Attribute not found

I tried with different Macbooks running the same version of MacOS, and the issue still persists.

Please let me know if you know anything about this <3

rain sage
digital eagle
#

The keymap does not change from what it was before, so I don't think it is being flashed

uncut falcon
#

Typeractive assumes you will use ZMK Studio to edit your keymap. You might want to read over the Studio feature page, but the short of it is that once it's been enabled your keymap is saved just like your pairing information, and reflashing with new firmware won't update it. If you can get into Studio, you can use "Refresh Stock Settings" from within the Studio UI to update the saved mapping with what you flashed.
If you can't get into Studio or don't want to bother trying, you'll need to build and flash the settings_reset shield to clear out the saved keymap.
If you don't intend to use Studio at all, you should disable it by doing the opposite of the "how to enable it" instructions.

digital eagle
#

when im in a being the goat competition and my opponent is honorless

uncut falcon
#

don't be silly, it's just that you're not the first person this has happened to blobcheeky
I disagree with Typeractive's decision to enable Studio by default (they should at least warn about this side effect) but it's not my call to make...