Yahoo Groups archive

AVR-Chat

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

Message

Re: [AVR-Chat] Re: newbie looking for advice

2008-02-27 by np np

In my experience its best to buy programmers made by the same manufacturer as the chips I am using.

Sorry to mention PIC's but I have heard of lots of problems with none Microchip programmers.
I can only guess the same is true for AVR.







----- Original Message ----
From: Tom <tjkeller1@windstream.net>
To: AVR-Chat@yahoogroups.com
Sent: Wednesday, 27 February, 2008 9:23:55 PM
Subject: Re: [AVR-Chat] Re: newbie looking for advice

John Samperi wrote:
>
> At 06:52 PM 27/02/2008, you wrote:
> > You can use a parallel
> >port (assuming your PC has one), and a 4 wire cable, wired to a piece of
> >perfboard, or to pins that can
> >\be pligged into your solderless breadboard, for programming. Dead 
> simple.
>
> ....which is usually followed by Dead Chip....
>
> Regards
>
> John Samperi
>
With all due respect, John, Horsepuckey! My first AVR project was 
an AT90S8515 based project involving three separate controllers for 
interactive video kiosks (for the KoolAid Museum) and I must have 
programmed those 8515s a hundred times befoe I got the programs working 
properly. All done with nothing more thana length of ribbon cabl;e 
with 4 lines, and a DB25 connector on one endm and db-9 connector ont he 
other end, plugging in to my controllers. Never lost am 8515. Thery 
are still in place, still running great 5 years later.

While expensive programmer hardware can be nice, and offers some 
nice, useful features, the truth is that so long as one is reasonably 
careful, one can get bv dirt cheap with AVRs, without problems.

avrFreak





      __________________________________________________________
Sent from Yahoo! Mail.
A Smarter Inbox. http://uk.docs.yahoo.com/nowyoucan.html

[Non-text portions of this message have been removed]

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.