avrdebug.exe binary for Windows - please compile...

General discussions about V-USB, our firmware-only implementation of a low speed USB device on Atmel's AVR microcontrollers
Post Reply
Anon

avrdebug.exe binary for Windows - please compile...

Post by Anon » Tue May 01, 2007 7:57 am

Could someone please compile and provide for downloading the avrdebug.exe (Windows binary) from the avr-doper package? Installing the whole gcc toolchain just for building a single small program is, well, a bit too much for me :-)

Thanks a lot in advance!

christian
Objective Development
Objective Development
Posts: 1443
Joined: Thu Nov 09, 2006 11:46 am

Post by christian » Mon May 07, 2007 11:44 am

Don't know whether avrdebug will run on Windows, since it uses libusb for connecting to a HID compliant device. This could result in a driver conflict.

Any Windows experts out there? We need to attach two applications to the same device, one using the HID interface, the other plain control transfers on endpoint 0 to query the debug data.

Anon

It works ;-)

Post by Anon » Mon May 07, 2007 1:07 pm

I tried it myself. Well, it seems to work. Sorry, I'm in no way a guru (that's why I asked for someone to do that), but here's what I did:

Installed MingW, installed libusb-win32, tried to compile, couldn't determine where to get date- and time-related functions in avrdebug code, commented them out, replaced a call to usleep(100000) by the call to Sleep(100) and it compiled.

It seems to work - I can program and receive debug messages from the same device... If there is a "real guru" who could compile it properly - it would still be great to have a downloadable .EXE from the original code...

Anon

Post by Anon » Mon May 07, 2007 1:08 pm

Sorry, forgot to say that I've only tried it in CDC mode, not HID (but that's good enough already for programming from AVR Studio)...

christian
Objective Development
Objective Development
Posts: 1443
Joined: Thu Nov 09, 2006 11:46 am

Post by christian » Mon May 07, 2007 1:13 pm

CDC or HID, Windows attaches a class driver to the device in both cases. In order to run avrdebug, you would have to attach a second (device specific) driver, in this case the libusb driver. I don't know Windows driver development well enough to tell how this can be done.

I have not tried it, though. Maybe it just works...

Post Reply