Thanks, and the Dragon *definitely* conforms to this specification?
On Jul 20, 2007, at 7:33 PM, Shaun Jackman wrote:
> The `AVR069: AVRISP mkII Communication Protocol' document is
available
> from Atmel:
> http://www.atmel.com/dyn/products/tools_card.asp?tool_id=3808
>
> It's a big help when doing low-level debugging. It defines the
> protocol between the computer and the mkII, not between the mkII
and
> the target device.
>
> Cheers,
> Shaun
>
> On 7/20/07, Brian Shire <address@hidden> wrote:
>>
>> Hello. I'm trying to get the AVR Dragon to work under OS X using
>> avrdude. I've read this thread regarding the topic:
>> http://www.nabble.com/AVR-Dragon-with-OS-X-Intel-Machine-
>> t3621118.html
>>
>> But the referenced argument (-B) doesn't help in my specific
case at
>> all. After following up with the original poster, they replied
that
>> they where in fact still having difficulties despite their last
post
>> of reporting success.
>>
>> Looking into the source code a bit, if I send the sign-on message
>> twice it will report a success, but of course this messes up
the rest
>> of the protocol. I'm curious if you think this might be a buffer
>> flushing issue between libusb and the device or perhaps if
there is a
>> protocol difference between the mkIII board that this code
seems to
>> be based off of? I don't see the official specifications for
>> communication with the device in specific (I'm using ISP), is that
>> published somewhere?
>>
>> The device will hang forever, when enabling extra logging I can
see
>> that the code is reporting a timeout while waiting for the sign-on
>> response from the Dragon board. Happy to help debug at a low
level
>> if someone can help me along a bit, appreciate any help/
suggestions.
>>
>> Thanks!
>>
>> -shire