X60 CONFIGURATOR / 01
Not connected
MAKE IT YOURS

A familiar keyboard.
Your way.

Key mappings, TrackPoint feel, and power settings.
One place. Straight to your X60.

Connect your keyboard

Use a USB data cable, or your paired Bluetooth profile.

Connect to read live keyboard data

INPUT OUTPUT
—

Connect to read the active route

BATTERY
—

Battery voltage and charge status

POWER STATE
—

Your configured sleep policy

Choose where you type.

Configuration and input are separate. You can edit over USB while typing over Bluetooth.

Profile changes may disconnect Bluetooth. Output/profile changes save after five seconds.

Keep a copy.

Export settings and both keymap layers to a file. Restore a backup to a compatible X60 v0.3.

Backups contain mappings, timeouts, battery settings, and TrackPoint tuning. Bluetooth pairings and firmware are kept separately.

EVERY KEY, CONSIDERED

Make yourself at home.

Select a physical key, then choose what it does.

X60 / PHYSICAL KEYS TrackPoint

Connect to load this layer’s bindings.

Additional physical keys

Labels identify physical keys. The base firmware swaps Left Alt and Windows/Command. Fn and Power, plus essential Fn recovery shortcuts, are reserved.

Choose a key above

Connect to read its current binding.

Release every keyboard key before saving. Changes save immediately.

A LITTLE RED DOT. A LOT OF CONTROL.

Find your feel.

Read and adjust the TrackPoint’s tuning registers.

TrackPoint tuning

Each value ranges from 0 to 255. Start with small changes and test the pointer between adjustments.

Saved after five seconds. Changes take effect immediately. TrackPoint must be awake and initialized.

READY WHEN YOU ARE

Work. Rest. Repeat.

Set your timeouts and check the battery.

A rest between sessions.

Keyboard and TrackPoint activity reset the timer. Any key wakes timed sleep. Hold Power for 1.5 seconds and release to turn off; Power or a new USB insertion wakes it.

Know where you stand.

Battery divider hardware

Match the resistors actually fitted to your board. Our tested pair is 470 kΩ / 470 kΩ with C16 100 nF.

R24 shares the voltage input with charger status. While charging, voltage is unavailable. Percentage is a voltage estimate; this board cannot detect an absent battery reliably.

<20% 20–59% ≥60%

Fn+B shows LED1 for one second at 5% channel brightness. Charging holds red and disables Fn+B.

KEEP A GOOD THING GOING

Firmware, refreshed.

Signed wireless updates, with a trial and automatic rollback.

Update without a cable.

Connect over Bluetooth in desktop Chrome or Edge. Select a signed X60 v0.3 OTA .bin. The signature is checked here and by the bootloader. Settings and pairings are preserved.

Connect to check OTA support. Older boards need a one-time bootloader installation using J-Link.

Keep power connected and stay near the keyboard. Input pauses during upload. After reboot, reconnect and test typing and the TrackPoint, then confirm within three minutes of startup. An unconfirmed trial rolls back on restart. An interrupted upload leaves the installed firmware available; select the same file to resume.

Connect to read

X60 v0.3 · nRF52840
  1. 01

    Choose your X60 firmware

    Select an X60 v0.3 application UF2 matching your installed layout. OTA boards require a signed primary-slot recovery UF2; legacy boards use the original application UF2.

  2. 02

    Enter USB update mode

    Use a USB data cable. Release every key, then enter the bootloader below or press Fn+Page Up.

  3. 03

    Copy, reconnect, verify

    Copy the selected file to the keyboard’s mounted UF2 drive (usually DoerX60Kbd). It restarts automatically. Reconnect USB here to verify the installed build.

Firmware files stay in your browser and transfer directly to the keyboard. Standard nice!nano images are incompatible. After OTA migration, never copy an old 0x1000 application UF2: it would overwrite MCUboot. Keep the matching signed recovery UF2 and use stable USB power for recovery.

UNDER THE KEYCAPS

A closer look.

Read the board’s state without changing its settings.

Connect a keyboard to read diagnostics.

LED states mean the last MCU-completed frame, not physical readback. No supply-current measurement is available. Close Python/other serial tools before connecting over USB.