letters Posted June 22, 2016 Share Posted June 22, 2016 Hello All, I've continuously racked my brain on this today and repeatedly come up with the same error, perhaps someone can assist. I've tried this on two different Win7 x64 devices. I feel I've done everything mentioned in the tutorials available here but I know I'm missing something as this isn't working. My error occurs, and I've seen it on Darren's Git Page, Flashing Ducky, but the I haven't found the information there to help my case. I error out at the Opening Port stage with a ATLibUsbDfu: 3EB 2FF6 no device present - FAIL Could not open device. I feel some of the guides are incomplete, leaving pieces out that I notice people claim to work in various comments. For instance: Inside the x86 folder of the Atmel Signed Driver is the .sys and .dll, through comments I get the understanding that I'm supposed to rename one of these files then drop them into my syswow64 folder, but the [Tutorial] by Nick mentions none of this. Also, Nick's post and a post by Enjoy0001 slightly contradict themselves in a couple of areas. In Nick's guide, there's no mention at all of dropping the program.bat along with .hex file into the Atmel\Flip 3.4.2\bin folder but it appears that needs to be done to complete the next operation, and per Enjoy0001's he drops the two files into the directory before bin, Atmel\Flip\ 3.4.2. I've tried placing the files in both directories with no luck. I've tried saving the .sys and .dll to both my syswow64 drivers folder and my system32 drivers folder. Do I need to be copying/moving these files at all? Darren's resource explains this is a driver problem and it's resolved by pointing the driver location to the atmel driver folder manually. I believe I've done this but perhaps I'm not doing it correctly as it's not helped yet. In order to download the Atmel driver I had to take this process: I'd like to note that loading the Ducky into my PC while holding the button does not prompt a wizard as some say it does on occasion. My Process on Win7 Ent. x64: Device Manager > Right click at the top > Add legacy Hardware > Show All Devices > Have Disk > Point to Atmel > toggle atmel_flip.inf > toggle AT32UC3B > Install Finishes Is my process of driver pointing incorrect? After performing these steps as instructed in Darren's post, I get the same error: Load Device manager, Find Atmel USB Device(Shows Atmel USB Devices in Device Manager not DFU Device), Update driver, Manual Install, Point windows to Atmel unzipped. C++ Redist and Flip are installed on the devices. Firmware file: c_duck_v2.1.hex Guide in mention by Nick: Guide in mention by Enjoy0001: I feel I did my due diligence of crawling these forums and YT for resolve to this error before posting but I've had no luck. Thanks for any input. If I can provide any additional information, I'll see to it immediately. I'll try this firmware flashing on a Linux device and a Windows 10 device later tonight. I'll report back with the outcome, but either way it'd be nice to solidify this process on a windows device. Quote Link to comment Share on other sites More sharing options...
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.