Posted on 5 Comments

Updating the Soarer’s Converter(ATMEGA32U4) to QMK Firmware with VIAL support

I get a lot of emails requesting me to do a tutorial on how to replace/update the old Soarer’s Converter to use the modern QMK Firmware with VIAL support so here’s your lucky day. 🙂

Get Started

Step 1:

First, plug in your Soarer’s Converter adapter to a Windows PC and put it into bootloader mode so you can flash it with the new QMK Firmware by running a command line software called scboot. Download this zip file which contains two files, extract, and run scboot.exe from the command line.

Running scboot will put the adapter to bootloader mode. Make sure your Soarer’s Converter adapter is indeed using the ATMEGA32U4 chip by looking at your Control Panel devices. You should see a device called ATm32U4DFU.

Step 2:

Now that your adapter is in bootloader mode, you’re ready to flash it with QMK Firmware. Download the Atmel Flip software and my custom QMK firmware. Install and run Atmel Flip. Select ATmega32U4 from the target device selection, Press CTRL + U and click Open to connect to the adapter, and Load HEX File from from the File menu and browse for the custom QMK firmware you downloaded. Click Run and that should update the adapter to the new QMK firmware.

Unplug the adapter and plug it back with a keyboard. Now enjoy your adapter with the awesome QMK firmware! 🙂

5 thoughts on “Updating the Soarer’s Converter(ATMEGA32U4) to QMK Firmware with VIAL support

  1. How do you put the converter into bootloader mode?

    1. While unplugged, press the key B and plug in the adapter to your Windows computer. Wait for a few seconds until it reboot to bootloader mode.

  2. Can you release the sources/configurations for your QMK build? I want to build my own .hex file.

  3. Hello,

    It looks like some features of QMK like Oneshot Keys are not working, can you please provide guidance? Tested with Shift on both side, on Windows, Linux with Vial and REMAP

  4. I have successfully updated my DIY Soarer converter to use the new firmware and initial testing showed it was okay. (even got to configure a few things in VIAL)

    However, after a few days of light usage, I noticed the keyboard frequently (every 30-60 seconds) becomes unresponsive for a second or two, after which it flashes the Num Lock LED and then starts operating normally again.

    I have reverted to Soarer’s firmware and it works fine, so there appears to be no hardware issues (Arduino Pro Micro USB-C – ATMEGA32U4 )

    The only thing done differently is that I used the windows command line to do flash the firmware:

    & “C:\Users\myuser\AppData\Local\Arduino15\packages\arduino\tools\avrdude\6.3.0-arduino17/bin/avrdude” -C”C:\Users\myuser\AppData\Local\Arduino15\packages\arduino\tools\avrdude\6.3.0-arduino17/etc/avrdude.conf” -v -patmega32u4 -cavr109 -PCOM5 -b57600 -D -Uflash:w:D:\converter_tinkerboy_ibmpc_usb_atmega32u4_atmel_dfu_vial.hex:i

    Have any idea what could be going wrong?
    Should I try the method above instead?

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.