vNext1

Bleeding-edge firmware. vNext1 is a prerelease for people who want the newest changes and can recover a board themselves. For everyday use, stay on vLaunch2.

Flashing resets every setting on the board, so back up your layout first.

Before you update

• Update Keybard Host to vLaunch2.3 if you use the overlay. Keybard at keybard.svalboard.com is already vLaunch2.3. Older versions of either can't read a board on vNext1.
• Export your layout (.svil) from Keybard's Layouts panel.

Update

1. Flash svalboard_left_sval_vNext1.uf2 to the left half and svalboard_right_sval_vNext1.uf2 to the right, as before: press RESET twice quickly and copy the file onto the RPI-RP2 drive.
2. Flash both halves. If the halves run different releases, the half without USB stops typing, and nothing warns you.
3. Plug in, connect Keybard, and import your .svil.

If your board has a pointing module, Keybard asks you to choose the board again after this update: the board now uses one USB product ID for every module. On Linux, install the udev rule that covers every Svalboard product ID:

KERNEL=="hidraw*", SUBSYSTEM=="hidraw", ATTRS{idVendor}=="303a", ATTRS{idProduct}=="404[4-9a-d]", MODE="0660", TAG+="uaccess"

New

• One firmware file per half. The board detects its pointing module on each half by itself. After you swap a module, unplug the board and plug it back in.
• Keybard lists each hand's pointing module in the Fragments panel.
• Overlay Shift follows the board. With Keybard Host vLaunch2.3, shifted legends follow Shift, Caps Lock and Caps Word on your Svalboard.
• 5-key finger clusters are the default layout.

The .svup files are for the in-firmware updater, which isn't released yet; use the .uf2 files.