I'm having trouble installing the driver from Windows 10 device manager. It doesn't show up has LUFA DFU, just as two HID devices/keyboards. The buttons return a-g on press, so the device works. Configurator won't see the device yet. Any advice?
paintwallsThanks for the reply, yes. I've hit reset many times. I haven't been able to install the drivers from the link yet. But it only shows up in Windows Dev manager as a HID keyboard. The visual device list says M10. I'll keep experimenting today.
QphilkvThis is the same thing thats happening to me. On Windows I can't get it to detect besides being HID Keyboard and on OS X I get the following "+-o M10-A@14100000 <class AppleUSBDevice, id 0x100000b65, registered, matched, active, busy 0 (5 ms". This is even after the reset button is pressed. So looks like the DFU mode is never showing up as a different driver, always M10-A.
I was able to configure my whitefox on OS X really easily and if I can get access to the M10's DFU mode and use dfu-util, i'll be happy.
Sikh Yes, frustrating eh?
My problem seems to be that Windows automatically installs PnP keyboard drivers every time you hit the reset button. Then, Device Manager doens't allow the option to install the driver or properly disable the HID device.
I've also tried installing the driver on a right click to the file atmel_usb_dfu.inf, but that's also not successful.
QphilkvRight click was the first thing I did to install the driver. I am trying to find a way disable windows 10 from automatically installing the generic driver but I've been unsuccessful in finding anything. There has to be a registry key somewhere.
QphilkvHere is a screenshot of the problem I have.
I've repeatedly deleted HID drivers and removed/reset the device. Every time it automatically installs HID drivers and doesn't appear as a ATm32U4DFU. So far all I have is an expensive keyboard that types this: "abcdefghij"
Hopefully RAMA can help at some point. I'm going to switch back to doing taxes, that was a lot more fun.
QphilkvAt one point I saw this exact scenario on my screen because I ran into an issue at some point. I think it wouldn't connect at one point or wouldn't flash my setup. But I remember I easily resolved it with either Reset or just reopening the config or something. So saying that probably isn't gonna be helpful or relevant.
But anyway, I have another stupid, and probably irrelevant, question/idea...Did you wait to install the Configurator till after you tried installing the drivers? I don't know if it might be necessary, for some reason, to get the driver installed prior to running the Configurator Installer.
I'm just trying to help :(
SikhI do remember having an issue initially with it only showing up as a generic keyboard, with a few USB disconnects & reset button presses it showed what I stated in an earlier conversation... I kept the device manager open during this.
Just out of curiosity attempt it in safe mode.
For others that read this:
Device manager is accessible by right clicking the windows icon on your task bar.
In windows 10 it's recognized as ATm32U4DFU after reset is pressed, after drivers are installed it's listed as ATmega32U4
QphilkvOk, I tried the following order on two separate Windows 10 machines and still no success:
1. Uninstall Configurator
2. Plug in RAMA 10A
3. Reset RAMA 10A
Device connects then Windows auto installs a PNP HID driver as pictured above.
Then I took the following steps:
4. Uninstall HID Device from Device Manager
5. Remove Device M-10A from Control Panel Devices and Printers
6. Reset button on RAMA
Still, the RAMA M10A never appears as ATm32U4DFU in Device Manager. Always as HID Keyboard which consistently returns "abcdefghij" (typed from my RAMA M10a, lol ;).
I have logitech devices plugged into both machines. I tried unplugging these and using a Windows Laptop, same result.
Thanks paintwalls for your help and suggestions. Sikh, let me know if you find a solution. I'm looking forward to hearing from RAMA and getting the device functioning correctly.
QphilkvI read your first reply and got so excited...then I scrolled on down :/
We did good work here. Hopefully we get some more suggestions or a fix from Rama or Josh. It's unfortunate that this isn't something you can just bring back to the store and exchange it for another one to see if it works. How glorious would that be...a KingRama store in every major city!
SikhTried Safe Mode and an OS X machine, still only an a-j keyboard and no luck with configurator.
Will return to Massdrop unless I hear a solution from the dev and manufacturer.