edpell
Member
When installing the driver (I am using windows vista 64 bit) I get the complaint that the driver is not digitally signed
Driver: LibUSB-Win32 - Kernel Driver
Service: LibUsb-Win32 - Kernel Driver
07/07/2009, 0.1.12.2
Publisher: http://libusb-win32.sourceforge.net
Location: C:\Windows\System32...\libusb0.sys
1) is there a way around this?
2) should I be concerned about 32 versus 64 bit?
Thanks.
Chorca
Member
Driver signing is a complex process that requires work by both Microsoft and the manufacturer, and typically takes a period of time. It's much easier/quicker for the leaflabs people to just release a driver and have you click the "Continue anyway" button instead of going through a complex and drawn-out signing process through Microsoft.
poslathian
LeafLabs
Hey guys,
Windows vista is not officially supported by us for partially this reason. On windows 7, weve gotten reports of success via entering the boot menu for windows and disabling driver signing. I dont know the exact details, so If you dont know what im talking about off the bat, let me know and ill try and dig up the requisite explanation links. Also in vista/7 windows handles the control lines DTR and RTS in the virtual com driver (usbser.sys) differently. We depend on these signals working a certain way, and there have been bugs related to this issue. Were working on a fix, for now be aware that:
The DTR/RTS problem does not afflict the libraries in our 0.0.4 ide, but that ide is inferior for other reasons. You can copy the hardware/leaflabs/cores/maple directory from 0.0.4 into 0.0.5 to use the good ide with the old library
You may see things like - program halts when serial port is closed, SerialUsb.print doesnt seem to print. This is due to those finicky DTR/RTS lines behaving unsupportedly. Try using hyperterminal instead of the built in arduino terminal. Sorry about those issues, were working on fixes in 0.1.0
siyuz
Member
I've gotten Maple IDE 0.0.5 to work on Win7 x64. Selecting the boot option to override driver signature enforcement works, but you have to do it every time. Instead you can use a program called DSEO (driver signature enforcement override), which can sign the drivers with a dummy certificate.
For a less hacky workaround, use xp 32bit or linux in a VM. I tried virtualbox and it seemed to work.
@Chorca Unfortunately you can't just click "Continue anyways" on x64 systems, they won't accept the driver.
Feyr
Member
for anyone installing on Win7 X64, you should not install the driver from the maple package.
rather, you should head to http://sourceforge.net/apps/trac/libusb-win32/wiki and grab the latest version which contains a digital signature that windows will accept (note: it will still say it's not verified but windows accepts it)
they have a wizard to generate the right inf file for the maple but it's a bit tricky to use: you need to reset/program your maple while having the device manager open. quickly click on the wizard when the 'maple m3' appears (NOT the com port, there's a second one) and use the resulting inf
Wow that's awesome, looks like it was just released last week. We'll update the install docs once we get a chance to test it out.
edpell
Member
The drivers pointed to by Feyr work fine in Windows Vista 64 bit. The only issue I have left is it can not find the DFU device when I upload. The message reads
Couldn't find the DFU device: [1EAF:0003]
I have tried pressing the reset button and then releasing the reset button and then pressing and holding the bar-but button until it gets to slow blinks. This does not fix the issue. It does produce a second message at the "Resetting to bootloader via DTR pulse that says Reset via USB Serial Failed! Did you select the serial right serial port? Assuming the board is in perpetual bootloader mode and continuing to attempt dfu programming..."
Then it gives the couldn't find dfu mesage
Which buttons should I press and or hold in what order until what event? Thanks.
Hey edpell, we don't have a windows 7 or Vista 64 computer set up so we haven't played with this method yet.
My first guess would be that the drivers/.inf were configured for the CDC_ACM (virtual com) configuration of the Maple, not for the DFU (bootloader) configuration. Feyr recommends trying to click through the wizard with careful timing while the Maple is in the quick bootloader mode after reset; it might be easier to put the Maple in perpetual bootloader /before/ configuring the driver?
If that doesn't work you could try hunting down the dfu-util.exe executable and running that from the command line with the '-l' argument to see if any DFU devices are detected at all while in perpetual bootloader mode.
On our todo list is to change the USB device name to be more descriptive so that debugging this entire process is less confusing!
Feyr
Member
i get the "cannot find DFU" on a pretty regular basis too. especially if you have another application opening the serial port. windows gets confused and will break.
you can USUALLY make it work by going to device manager and disabling the "Maple M3" device and reenabling it (control panel, system, device manager). but after 5-6 times you have to reboot.
the serial console doesn't work at all in the IDE so you have to use something else for connecting to your maple, which might be the problem. i installed hyperterminal
if you can't get programming going at all uninstall the two drivers (com port and the other one) and retry. you'll figure out the right sequence that work for you.
i could also upload the inf file i generated if anyone is interested... i think i still have it
Bionic-Badger
Member
After getting pissed with this board not working correctly in Windows 7 64-bit with the default drivers, and then problems with a Windows XP 32-bit VM (VMWare) on Windows 7 64-bit (because it kept enumerating the device in the host machine), I tried Feyr's method. It works great!
Step-by-step instructions:
- Download the binary libUSB package (http://sourceforge.net/projects/libusb-win32/files/), extract somewhere (we'll call it c:\LIBUSB)
- Plug the Maple board into the computer
- Open Device Manager
- Switch Maple board into continuous Bootloader mode (hit reset until you get the fast blinks followed by slower blinks; reset again and immediately hit and hold the boot "BUT" button until it changes into slow blink mode, release).
- It should show some broken USB device in your Devices, not a com-port
- Run the libusb INF wizard (c:\LIBUSB\bin\x86\inf-wizard.exe)
- Click through the dialogs, the default values should be fine, or you can fill in some descriptive info
- Save the INF and have it install. It'll produce a big red prompt about the driver being unsigned and problematic; however, it will still work.
- "Update" the MAPLE 003 device in your device manager and select the INF file you generated.
To load any program:
Run the Maple IDE, when you hit the Upload, hit your Reset button on your Maple Board. It should detect and load the data on it. If your compile takes too long, try hitting the reset later in the upload. I used an alternating interval blink to prove it was working to me instead of the straight blink code.
The serial drivers that came with the Maple IDE package do work fine, so you can use those drivers for the COM port directly.
can bionic's above post be added to the docs at http://leaflabs.com/docs/maple-ide/installation/ ? or at least a link to his above post?
i just got things up and running on win7 thanks to bionic and feyr, but i got a bit frustrated that the provided instructions were not accurate, and while i'm glad i didn't have to ask the question and then wait for a response, it peeved me that the solution was known yet still not in plain sight. future win7 users will certainly appreciate accurate installation instructions in places where accurate installation instructions are supposed to be!
in other news, hooray buttonyblinky!!
You must log in to post.
