Sup, leaflabs!
I have the IDE ("LATEST" as of today) running on a copy of XP, with no ability to select serial port. I see the following error when uploading to either RAM or Flash:
"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...
Lost Device after reset, assuming prod_id was incremented by oneNo DFU capable USB device found"
What can I do to attempt to fix this?
poslathian
LeafLabs
Hmm. Check that the device drivers are installed and windows is at least seeing everything in the background. Control Panel -> System -> Devices, look under COM ports, check for Maple COM. If its not there, check under usb devices or unknown devices and see if its there. There are two sets of drivers you need, one for DFU and one for serial, perhaps the serial driver installation went foul at some point?
Assuming that the drivers are all installed, and plugging in maple fails to cause any sort of registration in windows, get back to us and well debug some more!
Hooray, linux FTW!
Which version of windows XP was giving you trouble (32/64, home/pro, recently service packed?), and which of ubuntu did you get working (karmic/lucid)?
poslathian
LeafLabs
awesome! For the record, its not ftdi drivers that you want (we nixed the ftdi chip, using instead using the onboard usb hardware of the stm32). Our serial drivers are actually the standard usbser.sys and an inf file, located in
path-to-maple-ide/Drivers/mapleDrv/serial
the DFU driver is actually just libusb and an inf file found in:
path-to-maple-ide/Drivers/mapleDrv/dfu
but hey, ubuntu is cool too. Better in fact.
Windows XP 32 SP2
is now
Ubuntu 9.04!
Yo -- I know you're going gangbusters making everything work, but maybe throw a note in the installation directions about where you keep your drivers at?
(I spent a ton of hours fiddling with Windows control/dll/blahblahblah because I thought you were still using FTDI =/)
Right now the quickstart page links to the install page which somewhat confusingly references the driver paths... would it have been more helpful to have clearer docs on the website or an INSTALL-WINDOWS.html file in the released archive?
I definitely looked through the README/install how-to docs in the install, as well as on the website though I didn't see the note about driver locations here.
The main thing that confused me was assuming the folder called "drivers" included the driver I was looking for.
You must log in to post.
