Andrew, it might help you to use -e instead of -u. E.g., if you want to rewrite all the flash and EEPROM. I had to erase and then load fuse bits, then used CDCBootloader.hex. It looked like this:avrdude -c usbtiny -p at90usb1286 -e -U lfuse:w:0xde:m -U hfuse:w:0xdb:m -U efuse:w:0xf8:m It really helps to clear those lock bits first. remember, the AT90USB1286 comes preloaded with HID bootloader and lock bits set so to not allowed accidental erase or rewrite
At90usb1286 USB Driver
I think I can handle the bootloader recompiling for ATMega1286 and ISP loading to the Teensy2.0++. But I have a question you may be able to answer: where do you think the 1200 baud switch is interpreted for the reset function? I did not see it in the bootloader code and wonder if its embedded in a resident USB driver somewhere. Any insight you could give would be greatly appreciated.Thanks,Bill
The Printrboard electronic set was designed by members of the Printrbot team in order to eliminate the production and functionality shortcomings of older RepRap electronics sets. Printrboard improves upon the previous production-grade electronics set (Gen6) by adding heatbed and SD card support, reverting to 1/16 microstepping Allegro stepper drivers, and improving connectivity reliability and reducing cost by elimination of the FTDI UART chip. Printrboard also has expansion headers supporting I2C, SPI, UART, and ADC pins. All extra I/O ports of the AT90USB have been broken out to headers for prototyping and expansion.
Starting first with the principles of USB, you might be deterred by it's complexity.(The free accessible USB specification, available atUSB Implementers Forum,has 650 pages.)This leads often to the fact that either outdated interfaces are used further, or that the complexityof the USB is covered by the use of blown up software libraries. Such libraries (or example applications)are offered e.g. by the manufacturers of USB chips or together with experimentation boards -- often howeveronly as binary files(DLL)for a specificoperating system,or with a very strictcopyrightlicense, which restricts the distribution of thesoftware.In this case releasing of the developed software together with allsource codeunder theGPLor otherfree softwarelicenses is usually not permitted, so that furtherdevelopment of the software or adaption to different controllers by other developers is practically impossible. Unfortunately for some commercially distributed devices the concrete realization of thefirmware-interfaceis not indicated also, so that these devices can only be used with vendor supplieddevice driverson specificoperating systems.
Since driver programming under Microsoft operating systems is not easy and often is not possiblewithout employment of additional software packages, the HID device class is often used there forcommunication with USB devices. With the employment of this device class no special device drivers arenecessary, however communication may be restricted to USB Low-Speed. At the present time special device classeslike HID are not supported by the firmware, but extension with this functionality is possible.However there exists a special version of the LibUSB library for Microsoft operating systems, which canbe used as an alternative to the HID device class.
I don't have an experimental board since the project needs small device so I only use an adaptor pcb for the TQFP case and that's it. The usb hardware to connect (via breadboard for the beginning) was no real problem but the answer from windows allways is 'unknown device'. If I want to update the driver it allways says that the driver for 'unknown device' is allready up-to-date and stops. In descriptions on how to install in the internet allways the flip program is mentioned. I inbstalled it and then look for the driver installation package which has to be included internet allways claims. But there is no. Only two HTMLs on how to update (not install) drivers for windows2000 and windowsXP and a lot of cats, infs sys's and so on. If I tried to install this inf through 'install' in the windows explorer it tells me that this inf is not able to do so. And through the device manager it stops since it is satisfied with the up-to-date driver for 'unknown device'. If I try to install it through the direct install dialog in device manager it goes this way too. So: how can I install the driver for this devices? Normal arduino drivers do not work since these allways simulates a serial connection. Here it as direct line without serial.
Hello,some add's: I just have tried again to install drivers included to the flip package. Since the was no installation program I installed it through the device manager. With the hade-made-installation I allready came to the correct installation process. The device I want to usewas in the list ... everything fine so far. But short to the end of the installation it gave an error message one section of the '*.inf'-file was not valid. I don't know the details since this were not presented. It was the ...cdc driver as far as I can see the only one able to give a driver for AT90USB162 chips.
Now I'm out of ideas. Any kind of automatic does not work since windows fell in love with the unknown device driver and wants to stay with it. And hand made don't work since there is an error inside the inf-file needed. And all hand-made is not really possible since I don't know all the files needed. These are in the cat-file belonging to the driver but not all there in are needed. I don't know the details how the installation process separates the one needed and the one possibly desturbing. And I don't know how to make windows using the driver if I copied them to the correct locations. The inf-file is part of this and so ....
You can download the source distribution from the project files page. Windows users can download a pre-compiled executable, a set of USB drivers and the HTML help file in a separate zip file from the same page. 2ff7e9595c