1
0
Fork 0
forked from forks/qmk_firmware
qmk_firmware/keyboards/durgod/dgk6x
Ryan 56555c61e1
Migrate LAYOUTS to data driven (#19541)
* Migrate `LAYOUTS` to data driven, 0-9

* Migrate `LAYOUTS` to data driven, A

* Migrate `LAYOUTS` to data driven, B

* Migrate `LAYOUTS` to data driven, C

* Migrate `LAYOUTS` to data driven, D

* Migrate `LAYOUTS` to data driven, E

* Migrate `LAYOUTS` to data driven, F

* Migrate `LAYOUTS` to data driven, G

* Migrate `LAYOUTS` to data driven, H

* Migrate `LAYOUTS` to data driven, handwired

* Migrate `LAYOUTS` to data driven, I

* Migrate `LAYOUTS` to data driven, J

* Migrate `LAYOUTS` to data driven, K

* Migrate `LAYOUTS` to data driven, L

* Migrate `LAYOUTS` to data driven, M

* Migrate `LAYOUTS` to data driven, N

* Migrate `LAYOUTS` to data driven, O

* Migrate `LAYOUTS` to data driven, P

* Migrate `LAYOUTS` to data driven, Q

* Migrate `LAYOUTS` to data driven, R

* Migrate `LAYOUTS` to data driven, S

* Migrate `LAYOUTS` to data driven, T

* Migrate `LAYOUTS` to data driven, U

* Migrate `LAYOUTS` to data driven, V

* Migrate `LAYOUTS` to data driven, W

* Migrate `LAYOUTS` to data driven, X

* Migrate `LAYOUTS` to data driven, Y

* Migrate `LAYOUTS` to data driven, Z
2023-01-10 02:48:20 +00:00
..
galaxy Migrate LAYOUTS to data driven (#19541) 2023-01-10 02:48:20 +00:00
hades Migrate LAYOUTS to data driven (#19541) 2023-01-10 02:48:20 +00:00
venus Migrate LAYOUTS to data driven (#19541) 2023-01-10 02:48:20 +00:00
config.h VIA V3 - The Custom UI Update (#18222) 2022-11-10 07:46:44 +11:00
dgk6x.c Fix Per Key LED Indicator Callbacks (#18450) 2022-10-04 15:24:22 -07:00
dgk6x.h [Keyboard] Add Durgod Hades, Galaxy and Venus Keyboards (#12893) 2021-07-20 09:44:22 -07:00
halconf.h Durgod: Increase scan rate by using wait_us GPT timer (#14091) 2021-12-27 14:04:26 +11:00
mcuconf.h [Keyboard] Add Durgod Hades, Galaxy and Venus Keyboards (#12893) 2021-07-20 09:44:22 -07:00
readme.md [Keyboard] Add Durgod Hades, Galaxy and Venus Keyboards (#12893) 2021-07-20 09:44:22 -07:00
rules.mk Fixes for bootloader refactor build failures (#15638) 2022-01-06 06:55:46 +11:00

DGK6X = Venus, Hades, Galaxy, etc.

This DGK6X code is shared between the ANSI variants of Venus, Hades and Galaxy keyboards.

  • Keyboard Maintainer: J-Sully and dkjer
  • Hardware Supported: Durgod Venus, Hades or Galaxy board with STM32F070RBT6
  • Hardware Availability: Venus, Hades and Galaxy

Instructions

Build

Instructions for building the Venus, Hades and Galaxy firmware can be found here:

Initial Flash

For first Flashing from initial Stock's Firmware

  1. Back up original Firmware Image:
  • Unplug
  • Short Boot0 to Vdd (See below)
  • Plug In USB
  • Make a Flash Image's Backup in case you wanted to restore the Keyboard to Stock's Image:
    • Using dfu-util:

      dfu-util --list
      dfu-util --alt 0 --dfuse-address 0x08000000 --upload ${OLD_STOCK_BIN}
      
  1. Flash the QMK Firmware Image.
  • Put board into Bootloader mode, using the same method as when backing up the original Firmware (above)
  • Here are a few options for performing the initial Flash:
    • Using QMK Toolbox

    • Using dfu-util:

      dfu-util --alt 0 --dfuse-address 0x08000000 --download ${NEW_QMK_BIN}
      

You can short Boot0 to Vdd by shorting R19 to C30 on the sides closest to the processor, as shown:

  • Hades & Venus: Shorting Boot0 to Vdd on Hades or Venus

  • Galaxy 75 Shorting Boot0 to Vdd on Galaxy 75

Subsequent Flashing

For repeating Flashing you can use BootMagic:

  • BootMagic Lite has been enabled with Assigned "Esc" key
  • Unplug USB Cable
  • Holding Esc Button
  • Plug in USB Cable, Keyboard should be in ST-Bootloader state