v0.0.5
This firmware is based on a slightly older version of TMK, as originally ported by Marfrit, but support for Televideo DEC keyboards has also been backported onto it, integrated with VIAL, and layouts have been made more TMK-like.
converter_ibmpc_usb_atmega32u4_caterina_vial.hex has been tested with handwired pro micro.
converter_ibmpc_usb_atmega32u4_atmel_dfu_vial.hex has been tested with a soarer's converter cable from Orihalcon, and from Tinkerboy.
It is expected to also work with hasu-built tmk converters using atmega32u4/atmega32u2, but this has not yet been tested.
There are two variants for each firmware. The plain "vial" variant, and a "vial_VERY_INSECURE" variant. The vial_VERY_INSECURE variant allows the keyboard to be sent into bootloader mode, and reprogrammed by any application running on the host PC, however it's slightly safer for first users, because it doesn't require a working keyboard to be attached to the converter for it to be sent into bootloader mode from the VIAL app, or from Vial Web. The normal "vial" build is secure, so it requires Escape and Enter to be held for a number of seconds to unlock the keyboard to do some privileged changes to it.
Warning: you can still get your converter in a state in which it can't enter bootloader mode using just software, even if you choose the VERY_INSECURE variant, if you flash a firmware that is for a different chip, or for a different bootloader. Make sure you choose the correct .hex file to flash!
Warning: If you flash this on Soarer's converter hardware, then the "scboot" tool will not continue working to send it into bootloader mode, because it's a Soarer's-specific tool. Instead you will have to use the VIAL app (or Vial Web).
Note:
- Pro Micros use converter_ibmpc_usb_atmega32u4_caterina_vial.hex firmware
- Teensy 2.0 use converter_ibmpc_usb_atmega32u4_halfkay_vial.hex firmware
- Some pro micro compatible dev-boards will NOT use caterina
- for Soarer's converter cables from Orihalcon use converter_ibmpc_usb_atmega32u4_atmel_dfu_vial.hex. The soarer's converter cables this has been tested on come with atmega32u4 chips, and a bootloader compatible with the bootloadHID protocol, HOWEVER, the bootloadhid firmware doesn't correctly enter bootloader mode when triggered from VIAL. Experimentally I have verified that however the atmel_dfu firmware correctly enters bootloader mode, so please use that one. For flashing use either QMK Toolbox, or the bootloadHID command line utility. (Note: when first flashing VIAL firmware you will have to use scboot, to get it into bootloader mode).
- WARNING: if you make a mistake while flashing one of these cables, and flash the wrong firmware that can't enter bootloader mode, then you will have to cut up the USB end of the cable, and short the RESET pin to GND to get it into bootloader mode again.
- See this imgur post if this happens: https://imgur.com/a/HT6RKKI
- WARNING: if you make a mistake while flashing one of these cables, and flash the wrong firmware that can't enter bootloader mode, then you will have to cut up the USB end of the cable, and short the RESET pin to GND to get it into bootloader mode again.
- for Tinkerboy's Soarer's converter cables (specifically the ones with the silkscreen "KBD Converter v1.2" on the bottom of their PCB, others have not been tested), use converter_ibmpc_usb_atmega32u4_atmel_dfu_vial.hex, and flash it normally, using QMK Toolbox, or dfu-programmer.
- WARNING: if you make a mistake while flashing one of these cables, and flash the wrong firmware that can't enter bootloader mode, then you will have to open up the USB end of the cable, and short the RESET pin to GND to get it into bootloader mode again. (This is easier than on the Orihalcon cables, because the different style of connector which is not potted)
- See this imgur post if this happens: https://imgur.com/a/6forxAM
- WARNING: if you make a mistake while flashing one of these cables, and flash the wrong firmware that can't enter bootloader mode, then you will have to open up the USB end of the cable, and short the RESET pin to GND to get it into bootloader mode again. (This is easier than on the Orihalcon cables, because the different style of connector which is not potted)
Make sure to select the most appropriate layout in the Layout tab.
Important changes in this release:
- changed in the default keymap one of the keys from MO(1) to LT(1,KC_APP)