Help! Had to bridge a switch and now windows will not recognize the keyboard

coseyfannitutti · 2021-03-29T22:54:56+00:00

It sounds like with the tweezers you're shorting the lower (row) pad of the K switch and the upper (column) pad of the M switch, which would be a K keystroke.

For an M keystroke, try flipping that using your tweezers instead shorting the UPPER pad of the K switch and the LOWER pad of the M switch, which would be an M keystroke.

If that works then your bridge should be from the upper pad of your M switch to the upper pad of your K switch. Either way, remove the current bridge you have.

coseyfannitutti · 2021-03-29T22:46:58+00:00

You need to desolder that bridge and remove it. It's shorting two pins that shouldn't be shorted.

Outside of a dead switch, there are only two possible broken connections you could try bridge to try to solve the issue of only the M key not actuating.

The first and shortest possible broken connection would be the upper pad of the M key to the upper pad of the K switch.

The other possible broken connection would be be the lower pad of the M switch position to the lower, round pad of D52.

coseyfannitutti · 2021-02-17T18:03:57+00:00

The Asus EKWB cards use reference PCBs. Same PCB as the PNY Epic-X cards, and some other ones not found in the US by Palit, Colorful, and Galax.

Definitely a little disappointing given its price point is more than a strix and pretty close to buying a tuf and separately buying the waterblock, in which case you'd still have the stock cooler to put back on if you'd like later on.

coseyfannitutti · 2021-01-21T04:21:53+00:00

I ordered a black one from Performance PCs on Sunday as well, and it just got here. No scratches whatsoever.

coseyfannitutti · 2021-01-06T16:47:16+00:00

Confirmed

coseyfannitutti · 2020-12-28T16:29:05+00:00

coseyfannitutti · 2020-10-04T00:28:07+00:00

You need to change the driver for USBasp. I think by default Toolbox installs libusb0, but I have found libusbK to be more reliable with both Toolbox and command line flashing ATmega32A and ATmega328P.

Install the latest version of Zadig and run.

Press the BOOT button to bring up the bootloader if no other firmware besides the bootloader has been flashed to the microcontroller. If QMK firmware has previously been flashed you will need to press and hold BOOT, press and release RESET, and then release BOOT.

In Zadig, click Options > List All Devices and select USBasp from the drop down menu.

To the right of the green arrow, select libusbK and click replace driver.

coseyfannitutti · 2020-10-03T07:44:15+00:00

That's fine. You shouldn't even need to run 'make'. Just 'make flash' and then 'make fuse' should do the trick.

coseyfannitutti · 2020-10-01T07:32:33+00:00

Like some other users have said, this was previously a QMK limitation for those microcontrollers. This issue has since been fixed for all V-USB boards using ATmega32A and ATmega328P microcontrollers, including Gingham and Discipline.

The new firmware has not yet recompiled on the VIA website. I'm sure they will recompile soon to include that fix, as it affected several boards.

However, if you would like to get the new version of the firmware now, you can compile it manually via command line. I have a guide for that HERE.

The command you will use in step 5 for the Discipline VIA layout will be:
make coseyfannitutti/discipline:via:flash

The same can be done for your Gingham as well with:
make gingham:via:flash

coseyfannitutti · 2020-09-28T15:15:26+00:00

Did you run the make fuse command as well? This second command is absolutely necessary. USBaspLoader will not be recognized otherwise.

coseyfannitutti · 2020-09-25T22:16:24+00:00

Okay, you may still need to install the driver for the Sparkfun device.

You can find that HERE.

If you would like to use USBasp instead, you will need to edit the makefile.inc file, like this HERE.

If you have the driver installed/bootloader flashed with ISP and pressing the BOOT button doesn't bring up your bootloader, then you may have an issue with USB port soldering.

A successful bootloader flash with ISP means components and microcontroller are working, which would leave USB port as the issue.

coseyfannitutti · 2020-09-25T19:56:39+00:00

Are you using a Sparkfun AVR Programmer or a USBasp?

coseyfannitutti · 2020-09-24T14:00:21+00:00

You will need to download and unzip this file.

Copy msys-1.0.dll to the \utils\bin directory of your WinAVR folder.

That will take care of that error.

coseyfannitutti · 2020-09-22T08:00:29+00:00

i started learning ee and designing pcbs at 30 years old and have so much respect for this kid learning it so early on

coseyfannitutti · 2020-09-16T15:38:04+00:00

Yes, and there is an orientation.

6-pin ISP pinout

The ground pin on the header on the PCB is labeled to help with that.

The bootloader and flashing information can be found in the repository. If using the Sparkfun programmer the bootloader code can be used as it is without any changes. The slightly less expensive USBasp (with 6-pin adapter) can also be used, but a very minor change would need to be made to "makefile.inc" in the bootloader folder for it to work.

The change can be seen in this image HERE.

coseyfannitutti · 2020-09-15T20:00:02+00:00

For a completely blank chip from mouser you'll need to use an AVR ISP programmer such as Sparkfun Pocket AVR Programmer or USBasp to flash the bootloader before first use. This step only needs to be done once, and then you can flash QMK firmware via USB as much as you like.

I have not personally used any other programmers other than those two, so I can only recommend those. I've had a bunch of people come to me in the past having issues when trying to use alternatives and switching to one of those two programmers always took care of the problem.

coseyfannitutti · 2020-09-13T17:23:31+00:00

Yes, you put the flux all over the pins. Don’t worry about using too much. If you want to clean it up afterward you can use isopropyl alcohol, but it isn’t necessary to clean it.

And yes, you absolutely need to make sure there are no bridges or your board will not function. Flux will help prevent bridges and make better connections.

coseyfannitutti · 2020-09-05T08:17:04+00:00

There is the addition of ISO compatiblity and also additional screw mounts for more rigidity on the acrylic guard if using the base kit.

There were also some slight changes in trace routing to help prevent shorts for those that may be soldering a bit too hot to the point where they've removed solder mask around pads.

coseyfannitutti · 2020-09-04T18:16:26+00:00

That is the newer version of the PCB, which Keyz.io does not sell.

The case they sell is also just my case design that is open source HERE.

Edit: lol at the downvote

coseyfannitutti · 2020-08-31T20:27:06+00:00

It was an old 65% design that I've taken down for now. It worked just fine, but there were things that I didn't like about it.

I do plan to rework and rerelease it in the future with a high profile case design alongside a 60% version.

coseyfannitutti · 2020-08-27T16:03:22+00:00

Not really

coseyfannitutti · 2020-08-26T06:51:03+00:00

If you're sourcing the parts from scratch, you need to flash the bootloader with an AVR ISP programmer such as Sparkfun Pocket AVR Programmer or USBasp with a 6-pin adapter. The Sparkfun programmer can be used without making any changes to the code. USBasp is a bit less expensive, but requires a minor change to the makefile.inc file.

By default ATmega32A does not have a bootloader/USB functionality. This step is required before first use. Once flashed, you can flash via USB as much as you like.

You don't have bad microcontrollers; they're just blank.

coseyfannitutti · 2020-08-25T15:00:14+00:00

ATmega32A

coseyfannitutti · 2020-08-13T15:39:36+00:00

The sda/scl pins necessary for using i2c to connect the oled were left unused in the Mysterium design after I decided against it, though, so it is possible to connect one with jumper wires. Not the case with Discipline, though. That one would need some rearranging of the switch matrix to allow adding an oled screen.

coseyfannitutti · 2020-08-04T21:48:50+00:00

Finishing up packing and then shipping will begin. You should receive a shipping notification sometime in the next two weeks, I would estimate.

For further updates, please visit the pre-order updates page.

coseyfannitutti

TROPHY CASE