avrdude-dev
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [avrdude-dev] Problem with AVR Dragon and ATmega324p on OSX


From: Joerg Wunsch
Subject: Re: [avrdude-dev] Problem with AVR Dragon and ATmega324p on OSX
Date: Sat, 15 Nov 2008 09:26:11 +0100
User-agent: Mutt/1.5.11

As Armin Stranjak wrote:

> avrdude: jtagmkII_send(): sending 1 bytes
> avrdude: Sent: . [1b] . [00] . [00] . [01] . [00] . [00] . [00] .  
> [0e] . [01] . [f3] . [97]
> avrdude: jtagmkII_recv():
> 
> and it just hangs there.

That smells like problems on the lowest layer, the USB transport.
This layer is provided by the operating system, together with libusb,
and beyond AVRDUDE's direct control.  The -B option comes into the
game /much/ later.

What I'm noticing:

> avrdude: Version 5.5, compiled on Jul 21 2008 at 19:43:37
>              Copyright (c) 2000-2005 Brian Dean, http://www.bdmicro.com/

> avrdude: Version 5.3.1.osxintelhack, compiled on Feb  1 2007 at 22:30:12
>                Copyright (c) 2000-2005 Brian Dean, http://www.bdmicro.com/

Could that be the "osxintelhack" there?

Are both versions working with the same libusb version?

You could use a debugger, and set the (libusb-internal) variable
usb_debug to a high value, like 100, right at program startup.  That
will make libusb print out some debugging messages.  By comparing both
versions, perhaps we can get an idea what might happen down there.

-- 
cheers, J"org               .-.-.   --... ...--   -.. .  DL8DTL

http://www.sax.de/~joerg/                        NIC: JW11-RIPE
Never trust an operating system you don't have sources for. ;-)




reply via email to

[Prev in Thread] Current Thread [Next in Thread]