Yahoo Groups archive

AVR-Chat

Index last updated: 2026-04-28 22:41 UTC

Message

RE: [AVR-Chat] RS-232 Butterfly connection

2006-03-14 by Chuck Hackett

> From: Daniel Boyer
> 
> >By the silence on the list, I assume no-one has ever received data from the
> >RS-232 interface on a Butterfly?
> 
> I have done it many times, an I have never had a single problem. ....

Armed with this information I went back to square one and started over again.  I
now have it working at 9,600 baud with the ~+2.7v to ~-2.7v signal swing.

I think that the original problem was that I had only connected up the Butterfly
TX and Gnd pins (because, at the time, I didn't need RX).  Looking at the
Butterfly schematic makes it clear that they use the RX pin (thru a diode and a
cap) to supply the negative side of the TX signal.  After correcting that it
still didn't work but I think I had disturbed other settings (like baud rate,
etc.) in my previous attempts to get things working.  After I started from
square one again all is now well.

I apologize to the list for wasting bandwidth on a "my bad".  Lesson, always go
back to square one and verify everything! :-)

As partial compensation for my transgressions I offer:

For those looking for a WinAVR (gcc) version of the Butterfly Demo application,
I found one by Martin Thomas at:

http://www.siwawi.arubi.uni-kl.de/avr_projects/#bf_app 

I'm using it to become familiar with declaring and using flash resident data in
WinAVR.


> From: Daniel Boyer
> ....
> 	As it is, how are you programming it without being able to receive
> data from it? (not using the bootloader?)

I'm loading the Butterfly with AVRStudio via the JTAG interface using an ECROS
Tech. AVR Ice-Cube interface.

Cheers,

Chuck Hackett
"Good judgment comes from experience, experience comes from bad judgment"
7.5" gauge Union Pacific Northern (4-8-4) 844
http://www.whitetrout.net/Chuck

Attachments

Move to quarantaine

This moves the raw source file on disk only. The archive index is not changed automatically, so you still need to run a manual refresh afterward.