| Author |
Message |
|
|
 Posted: Jan 03, 2012 - 02:56 PM |
|
Joined: Dec 10, 2009
Posts: 3
|
|
| AVR Dragon has HV_PROG 20 pin connector, which has XTAL1 output clock signal on 17. pin of it. I used it sucesfuly to make alive my atmega128. |
|
|
| |
|
|
|
|
|
|
Posted: Mar 03, 2012 - 05:47 AM |
|
Joined: Mar 03, 2012
Posts: 2
|
|
Thanks clawson,
From an new-bee like me to AVRs this is a "must read".
I could not find any authoritive fixes for this problem until I came across this forum. spent a couple of days stuffing around! It is like everything that is new - once you know how, it is easy - the hardest thing is knowing where to look to find out how.
Make it a "sticky" to help dummies like me can find it easily.
Thank you  |
|
|
| |
|
|
|
|
|
|
Posted: Mar 03, 2012 - 09:47 AM |
|
Joined: Jul 18, 2005
Posts: 62220
Location: (using avr-gcc in) Finchingfield, Essex, England
|
|
|
Quote:
Make it a "sticky" to help dummies like me can find it easily.
I think you'll find that every article here in Tutorial is equally valid/useful and all would warrant being "sticky" in that sense 
(the evidence here tends to show that most newbies ignore anything that is sticky anyway  ) |
_________________
|
| |
|
|
|
|
|
|
Posted: Mar 03, 2012 - 11:39 AM |
|
Joined: Mar 03, 2012
Posts: 2
|
|
Your probably right, The whole sit could be a sticky
Thanks again,
now that I have found where to look I will be more thourough in my investigations. |
|
|
| |
|
|
|
|
|
|
Posted: Apr 19, 2012 - 09:59 AM |
|
Joined: Apr 16, 2012
Posts: 6
|
|
| Hi Clawson, Thanks for the useful guide. You might wish to add to it that programming with a Vcc on the Tiny 13 of < than 4.5 volts can lead to problems with the reported fuse settings when using AVR studio 4 and an AVRISP2. Whilst I have successfully programmed hundreds of Tiny13s with a target board powered with 2 x AAA cells there have always been a few failures due to screwed clock fuse settings. However increasing the Vcc from an nominal 3 volts to 4.5 volts (by adding another battery) seems to have cured the and I can recover some of the chips with the screwed fuses. Hope this helps. |
|
|
| |
|
|
|
|
|
|
Posted: Apr 19, 2012 - 11:09 AM |
|
Joined: Jul 18, 2005
Posts: 62220
Location: (using avr-gcc in) Finchingfield, Essex, England
|
|
That's not real a general issue but a question chip specification. The Tiny13 datasheet says:
Quote:
ATtiny13: 0 - 10 MHz @ 2.7 - 5.5V, 0 - 20 MHz @ 4.5 - 5.5V
So I assume you were clocking the 3V powere chip above 10MHz. As such you got what the datasheet predicted. If, on the other hand, you are saying you were running at below 10MHz and this occurred then that is an issue you should take up with Atmel to either determine whether they are producing chips out of spec. or whether there is an error in the datasheet that should be amended. |
_________________
|
| |
|
|
|
|
|
|
Posted: May 30, 2012 - 10:05 PM |
|
Joined: May 30, 2012
Posts: 4
|
|
Can you fill me in a bit more on using the stk500's internal clock to rescue my AVR? (I.e. what physical connections need to be made between programmer and AVR? Any flags I need to change on my command line?)
I fell into this pit, setting the fuse for oscillating clock, when I should have set it for crystal. I'm using an Arduino UNO as my AVR programmer (in the Makefile, it's specified as stk500v1, so I hope that counts) for an ATtiny85 AVR. (I have another Arduino, in case one is needed for the clock and one needed for the programmer.)
My Makefile specified (when I bricked my ATtiny85):
Code:
F_CPU = 16000000L
AVRDUDE_PROGRAMMER = stk500v1
AVRDUDE_BITS_PER_SEC = -b 19200 // already a factor of 3.6864MHz, right?
|
|
|
| |
|
|
|
|
|
|
Posted: May 31, 2012 - 09:46 AM |
|
Joined: Jul 18, 2005
Posts: 62220
Location: (using avr-gcc in) Finchingfield, Essex, England
|
|
|
Quote:
Can you fill me in a bit more on using the stk500's internal clock to rescue my AVR? (I.e. what physical connections need to be made between programmer and AVR? Any flags I need to change on my command line?)
STK500 manual is online here:
http://www.atmel.no/webdoc/stk500/stk50 ... znj_jwk_yb |
_________________
|
| |
|
|
|
|
|
|
Posted: Jun 07, 2012 - 08:38 PM |
|
Joined: May 27, 2002
Posts: 737
Location: Alabama USA
|
|
http://www.robotroom.com/Atmel-ATtiny-STK500-Programming-4.html
I found the above link helpful in visualizing the STK-500 jumper settings
as relates to the ATtiny devices.
It is easier to read than the STK-500 manual/help file.
High resolution graphics remove any
ambiguity in how the jumpers are implemented. Covers both the ISP and
HVSP modes and jumper settings.
Hope this is some help. |
_________________
I'll believe corporations
are people when Texas executes one.
|
| |
|
|
|
|
|
|
Posted: Jun 09, 2012 - 12:49 AM |
|
Joined: May 30, 2012
Posts: 4
|
|
|
|
|
|
|
|
Posted: Mar 02, 2013 - 12:15 PM |
|
Joined: Oct 05, 2006
Posts: 2240
Location: Poland
|
|
I would like to point out that this frequently visited tutorial lacks the (important) information that communication via JTAG does not require any valid clock source.
Even when external crystal is selected and physically removed, or when invalid clock setting is made - JTAG still works fine. The chip can be read, programmed or erased then (as long as JTAGEN is programmed).
What is more, also NRESET is of no use with JTAG as for JTAG dongle this pin acts only as input (although some dongles can assert it on demand).
I do not own a JTAGed RSTDISBL chip (like m169pa) but if anyone has such chip along with HVPP standing by, I encourage to try playing with it via JTAG and report.
Remember: "No RSTDISBL - no fun." |
|
|
| |
|
|
|
|
|
|
Posted: Mar 28, 2013 - 12:10 PM |
|
Joined: Mar 27, 2013
Posts: 7
|
|
|
|
|
|
|
FAQ
Search
Register
Log in to check your private messages
Log in
Maximize
RSS
