[En-Nut-Discussion] Ethernut 3.0 limits
supertxaby at gmail.com
Wed Jan 27 13:55:27 CET 2010
Yeah! My infected PC is a good boy now!. I'll beat up the opportunity to
clean my USB drivers (I had 159).
In the new and clean PC in the new clean and polish PC I've not installed
ethernut yet, just the Turtelizer as a desperate and succesfull test.
Moreover, may be important, there appear 3 installation wizards o whatever
(I've the spanish version) when I connect the turtelizer and it appears a
warning each one I select the folder in which I've unpacked your last
drivers... something about the logo and the "official" compatibility with
2010/1/27 Harald Kipp <harald.kipp at egnite.de>
> Hi Javier,
> Javier Longares wrote:
> > Since I had a lot of different boards connected to my PC with different
> > drivers each one, I've tried to test your downloads in other "clean" PC
> > it seems to work. Finally I've noted that in the old PC the system works
> > with your download, but I need to copy all the files and directories
> > included in the turtelizer2 folder to the win32 one. So, after 3 days of
> > hard work I can start now.
> You mean, that the start menu didn't work without copying the files?
> On that new machine, did you install Nut/OS before or after installing
> the Turtelizer tools?
> > 2010/1/27 Harald Kipp <harald.kipp at egnite.de>
> >> 1. Download and install USBDeview from http://www.nirsoft.net (or any
> >> other USB driver uninstaller of your choice).
> >> 2. Make sure that the Turtelizer is *not* connected.
> >> 3. Run USBDeview and uninstall *every* Turtelizer driver listed.
> >> 4. Quit USBDeview.
> >> 5. Unpack ftdi-turtelizer2.zip.
> >> 6. Connect the Turtelizer to the PC. The "New Hardware found" wizard
> >> should pop up. On the second page select "from a user specified source"
> >> or something like that (I have the German version). On the next page
> >> select the directory where you unpacked ftdi-turtelizer2.
> >> 7. Repeat step 6 for the second driver. One is for JTAG, the other for
> >> the USB/Serial bridge.
> >> 8. When done, try to run "Connect Ethernut 3.1" from the start menu
> I'd be interested to know, if this procedure also fixes the problem on
> your first "infected" PC.
More information about the En-Nut-Discussion