Click to view our Accessibility Statement or contact us with accessibility-related questions
Free Standard Shipping in the US on orders over $99
shopping_cart
arrow_back
Drop CTRL V1 Mechanical Keyboard
Mech Keys
Showing 1 of 1691 conversations about:
Drop CTRL V1 Mechanical Keyboard
marcw
33
Jul 2, 2020
issue flashing CTRL Hi everyone sorry for the wall o' text but i'm going crazy here. I've been using an ALT for a bit here and it has been wonderful. No issues flashing and rearranging my keymap, layers, etc. However I cannot do the same on CTRL. It works ok with the base firmware it shipped with but I got it to customize. I just received my CTRL today and cannot for the life of me get mdloader or qmk_toolbox to flash the thing. MDloader does the search for device for 60 seconds then times out with "Error: Could not find a valid device port!" if i try and force it to port 5 which is what i'm seeing it on as windows i get "Opening port '5'... Failed! (The system cannot find the file specified.)" if i use --verbose i see: .Opening port 'COM1'... Success! Configuring port...  Get config... Success!  Set config... Success!  Set timeouts... Success! Setting normal mode... Error reading 2 bytes! [0][0000](0) Closing port... Success! Opening port 'COM2'... Failed! Opening port 'COM3'... Failed! Opening port 'COM4'... Failed! Opening port 'COM5'... Success! Configuring port...  Get config... Success!  Set config... Success!  Set timeouts... Success! Setting normal mode... Success! Write: [w41002018,#] Closing port... Success! Opening port 'COM6'... Failed! Opening port 'COM7'... Failed! Opening port 'COM8'... Failed! Opening port 'COM9'... Failed! in qmk toolbox I can see the device connecting/disconnecting as i put it in to DFU mode but it fails to flash saying "Error: Could not find matching device ID!" sample below: *** Atmel SAM-BA device disconnected: Arduino Srl (www.arduino.org) Bossa Program Port (COM5) (03EB:6124:0110) *** Atmel SAM-BA device connected: Arduino Srl (www.arduino.org) Bossa Program Port (COM5) (03EB:6124:0110) *** Attempting to flash, please don't remove device >>> mdloader_windows.exe -p COM5 -D "D:\temp\massdrop_ctrl_thel1979.bin" --restart   Massdrop Loader 1.03       Massdrop Loader Copyright (C) 2018 Massdrop Inc.   This program is Free Software and has ABSOLUTELY NO WARRANTY       Opening port 'COM5'... Success!   Error: Could not find matching device ID!   Closing port... Success! Going through either of these same process with my ALT (obviously using a different compiled bin) works just fine. I've tried different usb ports on my PC, different usb ports on the keyboard, a different computer entirely. All work fine with the ALT but the CTRL just won't talk it seems. Any help would be very very appreciated. I was so excited to start messing with this thing.
3
Reply
bookmark_border
more_vert
marcw
33
Jul 2, 2020
marcwthe badasses fauxpark and sigprof in the QMK discord figured this one out. it seems this new CTRL has a different chip ID than previous ones. We updated line 38 in mdloader_common.c to change the Chip ID to 0x60060306 and then i was able to flash. I'm guessing the program is going to need to be updated for this.
7
Reply
bookmark_border
more_vert
zk7_7
0
Jul 9, 2020
marcwIn just using the mdloader_windows.exe and the applet .bin file, how could we make this change?
Vote
Reply
bookmark_border
more_vert
marcw
33
Jul 9, 2020
zk7_7i had to download the full source from git. add the line and recompile using the linux enviro i had already setup for making firmware
Vote
Reply
bookmark_border
more_vert
zk7_7
0
Jul 9, 2020
marcwI was debating trying that on my linux system to send over the compiled folder to my windows PC. I had tried the fix within linux but still had the issue, so we'll see how that works
Vote
Reply
bookmark_border
more_vert
marcw
33
Jul 9, 2020
zk7_7yeah as far as i could tell even though i ran the compiler/make they have built into the code there on my linux environment it created what appeared to be a windows executable inside the "build" subdirectory that it creates. running it in windows worked for me.
Vote
Reply
bookmark_border
more_vert
Rietty
2
Jul 11, 2020
marcwCould you share the updated build exes hopefully?
Vote
Reply
bookmark_border
more_vert
Ciel21
11
Jul 11, 2020
RiettyIm having the same issue and finally found this post about it. does any one have an updated mdloader for windows for this?
Vote
Reply
bookmark_border
more_vert
RyaSad
3
Jul 11, 2020
marcwSame exact issue. I have the ALT and it works fine, my new CTRL just doesnt get recognized by mdloader and just times out. Hopefully we can just get an update exe that works...
Vote
Reply
bookmark_border
more_vert
marcw
33
Jul 11, 2020
Riettyhttps://drive.google.com/file/d/1KvyRvtoVVE3OQdiWAKgj-XZll37Cxy4H/view?usp=sharing i've never tried sharing a file from my google drive so let see if this works hopefully they just put the update into mdloader itself so everyone gets it instead of having to search for this.
17
Reply
bookmark_border
more_vert
RyaSad
3
Jul 11, 2020
marcwthank you!!!!
Vote
Reply
bookmark_border
more_vert
MattEMatt
0
Jul 12, 2020
marcwFound this thread, and marcw, thank you! the exe and associated dll worked perfectly on my windows machine. I'm compliling the tools for linux and I will be looking for that line to modify, thank you all for that!
Vote
Reply
bookmark_border
more_vert
griponreality
190
Jul 15, 2020
marcwYou have also fixed this issue for anyone with the Drop Shift. Many thanks. Am linking to your comment with the link and crediting you for it over on the Shift discussion.
Vote
Reply
bookmark_border
more_vert
daveman1010221
0
Jul 15, 2020
marcwWell, I'm trying to do this on linux, so the exe doesn't work. Any chance you have a fixed.zip for linux? Thanks.
Vote
Reply
bookmark_border
more_vert
daveman1010221
0
Jul 15, 2020
daveman1010221nvm, I got it.
Vote
Reply
bookmark_border
more_vert
marcw
33
Jul 15, 2020
daveman1010221Great because I didn’t have a Linux one. What’s you have to do? Inevitably someone else on Linux is going to come looking :)
1
Reply
bookmark_border
more_vert
daveman1010221
0
Jul 16, 2020
marcwI read the comment above about editing line 38, made that change in my local tree that I pulled from GitHub, re-compiled, and used that binary. :-)
Vote
Reply
bookmark_border
more_vert
watermelonn
9
Jul 16, 2020
marcwYou my friend are an absolute legend!
Vote
Reply
bookmark_border
more_vert
marcw
33
Jul 16, 2020
watermelonnas a further follow up I just received notice from github that the fix has been integrated into the code now. So downloading a fresh copy from github should work now, and eliminate the need for this. I figured I'd put this out there in case anyone runs into this issue because they're still using an old copy they already downloaded previously. Just go hit up the latest copy and you should be good.
Vote
Reply
bookmark_border
more_vert
Sam-tut
0
Aug 1, 2020
marcwI am not sure if the issue is really gone. I tried the github version and the version you shared with the community and i am still having the same problem with two brand new drop Alt keyboards on two different machines running windows 10 :-( At this point i am not sure what to do to get it to work but i am about to move on from trying to get it to work on Windows and i'll be trying to do it on my linux machine.
Vote
Reply
bookmark_border
more_vert
moca
11
Aug 7, 2020
Sam-tutThat's weird 🤔 I just got an new Alt too and I'm on Win10 but the files marcw shared worked for me. Hope you can find a fix.
Vote
Reply
bookmark_border
more_vert
afynyth
10
Aug 26, 2020
Sam-tutDid you ever figure this out? I tried the new 1.04 release and marcw's files as well, and keep getting repeated failed COM port messages. Really out of ideas now.
1
Reply
bookmark_border
more_vert
JASON_LIU
Aug 27, 2020
afynythI'm experiencing the same issue. I tried the 1.04 version mdloader Windows as well as Linux. I built the tool from source in Linux after applying user marcw's suggested fix. I tried the binary marcw compiled for Windows. Nothing works. Still getting "Error: Could not find a valid device port!" on my Drop Alt.
Vote
Reply
bookmark_border
more_vert
JASON_LIU
Aug 27, 2020
marcwI'm experiencing the "Error: Could not find a valid device port!" issue. I tried the latest 1.04 version mdloader on Windows as well as Linux. I built the tool from source in Linux after applying the fix you suggested. I tried the binary you compiled for Windows. Nothing works. Still getting "Error: Could not find a valid device port!" on my Drop Alt. I made sure to use sudo when in Linux.
Vote
Reply
bookmark_border
more_vert
afynyth
10
Aug 27, 2020
JASON_LIUI'm fairly sure it's a new issue, also recompiled the source with @marcw 's edit, same error. Might be a new revision ID with the new batch of Drop ALTs, but if I'm understanding the update of the 1.04 binaries right even if there is a new ID it should work. Honestly have no clue what's wrong.
(Edited)
Vote
Reply
bookmark_border
more_vert
JASON_LIU
Aug 27, 2020
afynythI fixed it. Download the 1.03 source. Change the CHIP ID in line #38 to 0x60060305. Compile. Boom.
2
Reply
bookmark_border
more_vert
afynyth
10
Aug 27, 2020
JASON_LIUHm, it's still not working for me, but atleast it's a different error. It gets to the COM port 6 and errors out. Could you see if I'm doing anything different from you?
  • I compile the mdloader with the changed line #38 using "make -f Makefile" in my terminal
  • It gives me a build folder, I copy the applet and mdloader.exe in that to a separate folder with my config.bin file
  • There's now 3 files in that separate folder
  • In Powershell, I go to that folder
  • I press the reset button on the back of the keyboard
  • I then run the command
Is there something I'm doing wrong? Btw, I get the same result when I press reset after I run the command.
(Edited)
Vote
Reply
bookmark_border
more_vert
JASON_LIU
Aug 27, 2020
marcwThe latest batch of Alt High Profile's Chip ID changed to 0x60060305. And using 1.04 to flash gives the same error as you experienced with your CTRL. I was able to flash by changing the Chip ID to 0x60060305 in mdloader_common.c from 1.03 source code. I found the new Chip ID because the binary you compiled prints the Chip ID when attempt to connect. So big thanks to you!!! You and fauxpark and sigprof are truly heroes!!! I posted the solution in the community. Can you tell me how you made the program print Chip ID? It's a really good feature. Thank you!
1
Reply
bookmark_border
more_vert
JASON_LIU
Aug 27, 2020
afynythI'm not quite sure. I'm working in Linux. I don't know how use "make" in Windows. But first you should try flashing using marcw's binary. It should print out a string of number. Which is the Chip ID. Yours may not be 60060305?
1
Reply
bookmark_border
more_vert
JASON_LIU
Aug 27, 2020
afynythIf you need further help, you can contact me on discord (Hotaru Yanagawa#8302). I'm exhausted after spending hours fixing it. But I'll help you tomorrow.
2
Reply
bookmark_border
more_vert
afynyth
10
Aug 27, 2020
JASON_LIUSUCCESS!! Like an idiot, I was modifying the Chip ID address instead of Chip ID. *facepalm* But your method works!!!! I think you should make an issue in the github to warn that every new batch of Drop alts/ctrls have a new chip id. Thanks so much!
Vote
Reply
bookmark_border
more_vert
JASON_LIU
Aug 27, 2020
afynythBig thanks. Can you share your windows binary? I don't have a mean to compile for Windows, but would like to flash firmware on my windows machine. I tried WSL but it doesn't work.
Vote
Reply
bookmark_border
more_vert
JASON_LIU
Aug 27, 2020
afynythI got the following when trying to use your binary: Device port: COM5 (SAMD51J18A) Opening port 'COM5'... Success! Found MCU: SAMD51J18A Bootloader version: v2.18Sep 4 2018 16:48:28 Applet file: applet-flash-samd51j18a.bin Applet Version: 1 ERROR: Parser: File is empty! Error: Could not parse file! Closing port... Success! So weird. I'll try setting up GNU on my Windows machine and try tomorrow.
Vote
Reply
bookmark_border
more_vert
afynyth
10
Aug 27, 2020
JASON_LIUYeah, not quite sure what's wrong. I reuploaded it though. I used MinGW with make to compile it, maybe try that?
Vote
Reply
bookmark_border
more_vert
hoobie4792
0
Aug 27, 2020
afynythRan across your shared google drive folder and was able to update my Drop ALT successfully. Thank you!!!
(Edited)
Vote
Reply
bookmark_border
more_vert
minituff
2
Sep 1, 2020
marcwI think something is wrong with my CTRL also: Bootloader port listing ----------------------------- Opening port 'COM1'... Failed! Opening port 'COM2'... Failed! Opening port 'COM3'... Success! Configuring port...  Get config... Success!  Set config... Success!  Set timeouts... Success! Setting normal mode... Error writing 2 bytes! [0](0) Closing port... Success!
1
Reply
bookmark_border
more_vert
buttercup7
0
Sep 4, 2020
afynythMassive thanks to you. This worked for me.
Vote
Reply
bookmark_border
more_vert
DrKoopa
0
Sep 9, 2020
afynythI tried the stock loader as well as marcw's (as linked above) and neither worked, throwing the same errors as above. I tried your files, and while the loader seems to have successfully completed the update, the keybind changes I made in the firmware didn't take (still have default controls). I made the firmware via the online configurator on drop's site, so I'm not really sure if this is a problem with the firmware or loader (or user error, though I'm inclined to think it's not my fault). If you have any ideas for me to test out, or any questions I can answer, lemme know! Thanks for your work here, really wish these expensive keebs had functional software =.= I'd rather not learn QMK just yet, though I may anyway if I don't find a solution in the nigh future.
Vote
Reply
bookmark_border
more_vert
Rwarcards762
0
Sep 17, 2020
afynythSavior. I just bought a Drop ALT on September 3rd (I think) and the latest version (as of September 16th, 2020, v1.0.4) in the GitHub does NOT work. This binary works. Thanks again!
Vote
Reply
bookmark_border
more_vert
danielartvia7
0
Sep 30, 2020
Rwarcards762Hello same as you. I got my keyboard a few days ago. Do you have an email to contact you, I don´t understand about binary :( and the new version sucks.
Vote
Reply
bookmark_border
more_vert
glagrien
0
Feb 19, 2021
marcwThis Works like a charm for me, thanks a lot for your work
Vote
Reply
bookmark_border
more_vert
Public_Nuisance
79
Mar 26, 2021
marcwThank you!
Vote
Reply
bookmark_border
more_vert
leannoliquor
0
Jul 20, 2021
marcwThese fixed files worked holy shit thank you!
Vote
Reply
bookmark_border
more_vert
weihyac
0
Feb 12, 2022
marcwthank you so much.
Vote
Reply
bookmark_border
more_vert
lolskilled
1
Jun 8, 2022
marcwHave the same problem, Could not find a valid device port, help :) :(
Vote
Reply
bookmark_border
more_vert
View Full Discussion
PRODUCTS YOU MAY LIKE
Drop CTRL V1 Mechanical Keyboard
Drop + MiTo GMK Laser Custom Keycap Set
$125
Drop + Matt3o MT3 Susuwatari Custom Keycap Set
$130
Drop + biip MT3 Extended 2048 Custom Keycap Set
$52
Drop Holy Panda X Mechanical Switches
$19
Drop Skylight Series Keycap Set
$45
Drop + Oblotzky SA Oblivion V2 Custom Keycap Set
$60
Drop + RedSuns GMK Red Samurai Keycap Set
$85
Drop GMK White-on-Black Custom Keycap Set
$89
Drop + MiTo SA Godspeed Custom Keycap Set
$99
Trending Posts in Mechanical Keyboards
DROWTS
SOLO GOOD ! @_@ Drop CTRL V2 Mechanical Keyboard
Apr 18, 2024
Mech Keys
Photos
Vote
0
lwthunder
Drop CTRL V2 Mechanical Keyboard PCBA
If I want some hot-swap socket for replacement, where I can buy to ensure it fits this PCBA?
Apr 17, 2024
Mech Keys
Questions
Vote
0
ThereminGoatMK
Do I Need to Lube My Keyboard Switches?
Figure 1: Sometime around here is a good time to ask that question... If you’re new to the mechanical keyboard hobby, I have no doubt that planning your first keyboard build is a bit of a daunting task. To be entirely honest with you, it’s only a tiny bit less daunting for your second or even third keyboard builds should you stay around a little while longer. You’ve got the keyboard itself to worry about, stabilizers, keycaps, and even switches on top of all of the intangible marks you want your dream keyboard to hit. Switches are especially daunting right out of the gate as there’s just so many options out there to pick from – each with their own unique specifications, manufacturers, and more. Yet, in spite of all of these differences between switches, time and time again I find people always asking about lubing switches as one of their chief concerns when it comes to picking some up. With countless numbers of content creators talking about lubing switches, its no...
Apr 17, 2024
Mech Keys
Guides
Drop Updates
3
1
Keyboy
Help Momoka zoo 65
Pcb damage is it possible to fix
Apr 16, 2024
Mech Keys
Questions
Vote
0
TiKiToPia
Keyboard & Drink
Playful set
This set goes better for keyboards meant for personal-casual setups as opposed to office-work environments.
Apr 14, 2024
Mech Keys
Keyboard & Drink
2
0
Keyboy
help Momoka zoo 65
What is the diameter and length of the screws for the momoka zoo 65
Apr 14, 2024
Mech Keys
Questions
Vote
0
jtgas23
ALT V2 not detected with Drop Keyboard Configurator
Hi, This is my first non-mac keyboard. I was under the impression that this would work out of box with with mac desktop however I am having issues getting the ALT V2 detected with the keyboard configurator software. The keyboard is plugged in and powered on. Apologies if this is very basic or if I have used incorrect language describing my issue, I don't have experience with this. Thank you
Apr 13, 2024
Mech Keys
Questions
Vote
3
© 2024 Drop
Company
About Drop StudioStudent DiscountPrivacy PolicyTerms of UseCookie Settings
Drop Refurbished
Like-new products you can trust
Drop Rewards
Get $5 for every 500 points you earn! Learn more
Drop Keyboard Club
Become a member and expand your keycap collection
Collaborate With Us
For Brands & Designers
Support
ContactCommunity GuidelinesHelp CenterSitemap
Follow Drop
© 2024 Drop