New firmware breaks one of the USB ports on the CTRL

[vampjaz]

I had my ctrl set up a while ago but i went recently to change one binding using https://drop.com/mechanical-keyboards/configurator , the new firmware breaks the left USB port. plugging into the right one works fine. tried updating mdloader and the applet and it makes no difference. reverted back to the old firmare file i had and it works again.. the new firmware file that the website gave me is 4kb smaller than the old one and has a different name and i suspect that they changed something that broke the dual USB setup

i can't find a project related to the website configurator so let me know if this is the wrong place to report this bug.

[rossgong]

I can confirm this exact issue on my Drop CTRL keyboard

[jldeen]

I can also confirm this issue and I have emailed support about it. I thought I was going crazy! @vampjaz Do you have a link to the previous firmware so others like myself may roll back. I can't seem to find where to download it. Thanks in advance!

[vampjaz]

Do you have a link to the previous firmware

@jldeen unfortunately, my bindings are pretty nonstandard so i don't think it would be useful for most people.

[jldeen]

@vampjaz No worries. Thank you for replying. FWIW, I pulled a copy of the firmware for the CTRL high profile right off a brand new board. I flashed my current keyboard with this uploaded firmware and it resolved my issue. I'm attaching it here for others, though I do so with caution: be careful flashing your keyboard with a file a stranger uploaded. I also compiled my own firmware using the default keymap from the qmk_firmware repo and this also worked fine. I think the configurator tool is just broken and Drop doesn't want to admit it. I contacted support and commented on their forums. Support wanted to replace the keyboard and deleted my comment on their forums about this issue.
drop_ctrl_default_read_firmware.zip

[rossgong]

I can confirm @jldeen 's firmware fixes the problem, even if it removes any custom keymap. Sad to lose one of the bigger advertised features of this board

[just-another-jxliu]

We'll look into this.

[colombod]

Same issue for me.

[just-another-jxliu]

Hi all, we rolled out a fix earlier today. Try compiling again and flashing your keyboard. Some additional information here: https://drop.com/talk/9382/how-to-configure-your-ctrl-keyboard/2884250

[vampjaz]

well now i can't download any new firmwares from the configurator, it just hangs forever on compiling

[just-another-jxliu]

@vampjaz Try again now. We rotated some infrastructure and I missed a server restart.

[vampjaz]

ok so now my left usb port only works about half the time with the new firmware, improvement i guess?

[just-another-jxliu]

@vampjaz We pushed a change to our web configurator to allow for choosing the firmware version to use and to configure how long the microcontroller waits before determining which USB port is connected to the computer. By default, the microcontroller waits 100 ms. Try increasing that to see if the port detection becomes more consistent. Let me know if that improves things for you and what values you try out.

[Tarball]

I'm encountering a similar issue with the "Modern" firmware, except it doesn't seem to matter which USB port I use. The keyboard simply will not boot up (no device in Device Manager, no LEDs on the keyboard) about 75% of the time. The other 25% of the time it takes 15-20 seconds for the keyboard to come to life, then it works fine. I increased the USB port detection delay to 1000ms but didn't see much of a difference.
Reverting to the "Original" firmware resolves the problem, but I'd like to use the Modern firmware since it's supposed to improve the key chatter issue.

Edit: After further testing, it appears the keyboard does eventually come to life, it just can take up to 60 or 70 seconds (though sometimes it is quicker). So maybe this isn't the same issue that others are encountering.