Author Topic: [GB] Golbat Round 2 (Final Round) - SHIPPING SOON  (Read 12576 times)

0 Members and 1 Guest are viewing this topic.

Offline tobsn

  • Posts: 205
Re: [GB] Golbat Round 2 (Final Round) - SHIPPING SOON
« Reply #100 on: Fri, 25 August 2017, 18:55:21 »
I shipped out all the orders that were paid for as of yesterday!

I have 2 left with shipping unpaid but I think they actually messaged me at some point for a quote so I have to go find those.

That be me, you said you will mail once you're in Miami.

Offline Grimspoon

  • Posts: 49
  • Location: Windsor, ON
    • Reddit
Re: [GB] Golbat Round 2 (Final Round) - SHIPPING SOON
« Reply #101 on: Fri, 25 August 2017, 19:43:30 »
Did the Canadian orders get sent out though?

Never got confirmation or tracking for mine.
Ducky Shine 3, Plank, JD40, JD45

Offline GL1TCH3D

  • Thread Starter
  • Posts: 1112
  • Location: Quebec, Canada
  • Audiophile, tea lover and now keyboard hugger!
Re: [GB] Golbat Round 2 (Final Round) - SHIPPING SOON
« Reply #102 on: Sat, 26 August 2017, 01:20:45 »
Yea the Canadian orders were included in yesterday's bundle. And that was exactly 1 Canadian order :c

Offline ctzn_voyager

  • Posts: 61
  • Location: Detroit
Re: [GB] Golbat Round 2 (Final Round) - SHIPPING SOON
« Reply #103 on: Sun, 27 August 2017, 10:27:54 »
I tried programming this thing again today so my son could use it, and after installing zadig drives my mouse/bluetooth devices aren't working. Anyone else experience this issue? Why is this such a PITA to program?

Edit: Rolled back the driver and got my mouse working. Of course, flashing the PCB still doesn't work. Is there any way to incorporate this keyboard into something like easykeymap tool that I use for the GH60, or using Flip to flash a .hex? I tried building firmware using http://kb.sized.io/ and then flashing the .hex with Flip (which is how I've done my handwire builds in the past) but that didn't work. Are the Rd 1 flashing instructions still recommended for Rd 2 boards?
« Last Edit: Sun, 27 August 2017, 12:00:04 by ctzn_voyager »

Offline Phinnegan

  • Posts: 28
  • I have a new addiction.
Re: [GB] Golbat Round 2 (Final Round) - SHIPPING SOON
« Reply #104 on: Mon, 28 August 2017, 19:09:32 »
I tried programming this thing again today so my son could use it, and after installing zadig drives my mouse/bluetooth devices aren't working. Anyone else experience this issue? Why is this such a PITA to program?

Edit: Rolled back the driver and got my mouse working. Of course, flashing the PCB still doesn't work. Is there any way to incorporate this keyboard into something like easykeymap tool that I use for the GH60, or using Flip to flash a .hex? I tried building firmware using http://kb.sized.io/ and then flashing the .hex with Flip (which is how I've done my handwire builds in the past) but that didn't work. Are the Rd 1 flashing instructions still recommended for Rd 2 boards?

Once I installed the driver using zadig (after putting the keyboard in reflash mode and selecting the atm32yadda per the instructions, did you do this?  you probably replaced the wrong driver which hosed your usb/bluetooth - make sure you're replacing the driver for the keyboard bootloader (the atm32udfu device), which will only appear with the keyboard in flash mode).

I was able to use https://tkg.io/ (after installing the chrome plugin) by selecting  keyboard->kimera, config->golbatv2, and pasting in maps for each layer from the keyboard layout editor (and finally setting led number 3 to 8 rgb leds per the post above). 

The keyboard (in flash mode) shows up in the burn drop down and flashes directly from the browser.

Offline ctzn_voyager

  • Posts: 61
  • Location: Detroit
Re: [GB] Golbat Round 2 (Final Round) - SHIPPING SOON
« Reply #105 on: Mon, 28 August 2017, 20:07:11 »
I tried programming this thing again today so my son could use it, and after installing zadig drives my mouse/bluetooth devices aren't working. Anyone else experience this issue? Why is this such a PITA to program?

Edit: Rolled back the driver and got my mouse working. Of course, flashing the PCB still doesn't work. Is there any way to incorporate this keyboard into something like easykeymap tool that I use for the GH60, or using Flip to flash a .hex? I tried building firmware using http://kb.sized.io/ and then flashing the .hex with Flip (which is how I've done my handwire builds in the past) but that didn't work. Are the Rd 1 flashing instructions still recommended for Rd 2 boards?

Once I installed the driver using zadig (after putting the keyboard in reflash mode and selecting the atm32yadda per the instructions, did you do this?  you probably replaced the wrong driver which hosed your usb/bluetooth - make sure you're replacing the driver for the keyboard bootloader (the atm32udfu device), which will only appear with the keyboard in flash mode).

I was able to use https://tkg.io/ (after installing the chrome plugin) by selecting  keyboard->kimera, config->golbatv2, and pasting in maps for each layer from the keyboard layout editor (and finally setting led number 3 to 8 rgb leds per the post above). 

The keyboard (in flash mode) shows up in the burn drop down and flashes directly from the browser.

Interesting. I'll give it another crack with the link you provided. I've been a little gun shy since my first try. Thanks for the suggestions!

Edit: Tried all that, followed the instructions to the letter, have the driver installed correctly (when I try the set up again it tells me the driver is already installed), the zadig driver is there and installed (it says "reinstall" when I open it now). But the burn button is still greyed out. Additionally, when I drag the eep file to "reflash" I get the set up window prompt that seems to recognize everything correctly, it even seems to flash successfully (at least that's what it says) but nothing works. I know the PCB works and that I built it correctly because when I first built it the default firmware was working.

The only deviation from the instructions are thus: I'm using a more current version of zadig (2.3) and the board is listed as atm32ud4fu.

Edit #2: I'll leave all of the above there in case it can help anyone else, but I've figured out the problem. The USB slot I had the thing plugged into in the front of my computer wasn't recognizing the presses for some reason? I plugged it into one in the back and sure enough it fired right up.
« Last Edit: Mon, 28 August 2017, 20:45:01 by ctzn_voyager »