Synth-DIY Yahoo! Groups Archives

Thread

Re: AVRISP -> AtTiny Communication Problem

2010-01-21 by bit_tricks

--- In AVR-Chat@yahoogroups.com, "Kenny M." <kenny782@...> wrote:
>
> Oh sorry, I got rid of the blinking orange when I did the manual upgrade the other day.

Cool, that's progress.

To be certain that you are selecting the correct device in the correct place, the dialogue box to do this is shown on Page 11 of the User's Guide here:

http://www.atmel.com/dyn/resources/prod_documents/AVRISPmkII_UG.pdf

The location to set the ISP frequency is shown on Page 17 of the same guide.  I'd try a value of 125kHz or less (possibly much less just to try and eliminate this as being your issue).

Hang in there.  It is true, it does get easier with experience.

Rick

Re: [AVR-Chat] Re: AVRISP -> AtTiny Communication Problem

2010-01-21 by Kenny M.

Oh sorry, I got rid of the blinking orange when I did the manual upgrade the other day.
I got back to the green light but it still won't work none the less.

I'll take a look at that Dragon too though, sound like a good deal.

I appreciate all the info on this.

Show quoted textHide quoted text

----- Original Message -----
From: "bit_tricks" <bit.tricks@gmail.com>
To: AVR-Chat@yahoogroups.com
Sent: Wednesday, January 20, 2010 9:13:38 PM GMT -05:00 US/Canada Eastern
Subject: [AVR-Chat] Re: AVRISP -> AtTiny Communication Problem

--- In AVR-Chat@yahoogroups.com , "Kenny M." <kenny782@...> wrote: 
> 
> Yeah I actually ran through the manual upgrade already. 
> 
> The AVRISP2 must be bad, I can't get it to connect to any of these chips and everyone else seems to be out of ideas. 
> If they'll give me my money back I'll just grab a USPS flat rate box and send it back for 5 bucks. 
> 

Well, unfortunately, I don't have any new suggestions to add. 

If you have performed a successful manual upgrade, and are still receiving an orange blinking light, then I suspect a wiring issue. It could be on your reset line and/or the ISP interface. 

If the programmer is happy with the ISP connections, but you can't program the chip, then I suspect either the wrong device is selected or the ISP frequency is set too high in AVR Studio. 

If you would like to try a different programmer, I suggest the Atmel AVR Dragon. It costs $49 from Digikey. It will do everything the AVRISPmkII will do plus it will perform JTAG and debugWire emulation for devices with 32kB of flash or less. I don't believe your ATtiny15L's support JTAG or debugWire, but you might want this capability for a different micro in the future. 

Rick

RE: [AVR-Chat] Re: AVRISP -> AtTiny Communication Problem

2010-01-21 by Ivan Vernot

Hello,
Sorry to jump into the middle of the thread but I just wanted to say that in my experience the AVRISP MkII is quite robust and (knock on wood) I have had no reliability problems with it ever. 

Apologies if this has already been covered but have you checked -
1. Are you certain that your target micro is OK?
2. Check that you ISP Freq is no more the 1/4 of the CPU clock freq
3. Check that you have the connection correct - 
3a. In particular check  MISO and MISO (I still get them the wrong way around!)
3b. Not sure what your target micro is but note that some (eg. atmega128) do not use MISO/MISO pin for programming
4. What exactly is the error message  from AVR studio? I always first try to 'Read Signature' (from the 'Main tab')

HTH
Ivan Vernot

Show quoted textHide quoted text

> -----Original Message-----
> From: AVR-Chat@yahoogroups.com [mailto:AVR-Chat@yahoogroups.com] On
> Behalf Of Kenny M.
> Sent: Thursday, 21 January 2010 1:42 PM
> To: AVR-Chat@yahoogroups.com
> Subject: Re: [AVR-Chat] Re: AVRISP -> AtTiny Communication Problem
> 
> Oh sorry, I got rid of the blinking orange when I did the manual
> upgrade the other day.
> I got back to the green light but it still won't work none the less.
> 
> I'll take a look at that Dragon too though, sound like a good deal.
> 
> I appreciate all the info on this.
> 
> ----- Original Message -----
> From: "bit_tricks" <bit.tricks@gmail.com>
> To: AVR-Chat@yahoogroups.com
> Sent: Wednesday, January 20, 2010 9:13:38 PM GMT -05:00 US/Canada
> Eastern
> Subject: [AVR-Chat] Re: AVRISP -> AtTiny Communication Problem
> 
> --- In AVR-Chat@yahoogroups.com , "Kenny M." <kenny782@...> wrote:
> >
> > Yeah I actually ran through the manual upgrade already.
> >
> > The AVRISP2 must be bad, I can't get it to connect to any of these
> chips and everyone else seems to be out of ideas.
> > If they'll give me my money back I'll just grab a USPS flat rate box
> and send it back for 5 bucks.
> >
> 
> Well, unfortunately, I don't have any new suggestions to add.
> 
> If you have performed a successful manual upgrade, and are still
> receiving an orange blinking light, then I suspect a wiring issue. It
> could be on your reset line and/or the ISP interface.
> 
> If the programmer is happy with the ISP connections, but you can't
> program the chip, then I suspect either the wrong device is selected or
> the ISP frequency is set too high in AVR Studio.
> 
> If you would like to try a different programmer, I suggest the Atmel
> AVR Dragon. It costs $49 from Digikey. It will do everything the
> AVRISPmkII will do plus it will perform JTAG and debugWire emulation
> for devices with 32kB of flash or less. I don't believe your
> ATtiny15L's support JTAG or debugWire, but you might want this
> capability for a different micro in the future.
> 
> Rick
> 
> 
> 
> 
> 
> 
> 
> 
> ------------------------------------
> 
> Yahoo! Groups Links
> 
> 
>

RE: [AVR-Chat] Re: AVRISP -> AtTiny Communication Problem

2010-01-21 by Dave McLaughlin

Hi Ivan,

 

And typing them!!  :o)   Sorry, couldn’t resist!

 

If you remember what they are abbreviations for, it is easier to get them wired up correctly.

 

MISO     Master IN Slave OUT

MOSI     Master OUT Slave IN

 

Cheers,
Dave…

Show quoted textHide quoted text

From: AVR-Chat@yahoogroups.com [mailto:AVR-Chat@yahoogroups.com] On Behalf Of Ivan Vernot
Sent: 21 January 2010 11:01
To: AVR-Chat@yahoogroups.com
Subject: RE: [AVR-Chat] Re: AVRISP -> AtTiny Communication Problem

 

3a. In particular check MISO and MISO (I still get them the wrong way around!)

HTH
Ivan Vernot





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