[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [avr-gcc-list] AVR-GCC-list Digest, Vol 97, Issue 2
|
From: |
Gerrit Bosch |
|
Subject: |
Re: [avr-gcc-list] AVR-GCC-list Digest, Vol 97, Issue 2 |
|
Date: |
Sun, 10 Feb 2013 00:36:49 +0100 |
Dear Joerg,
Thank you for your explanation. When trying to apply your suggestions it
appears that the device started to work without any delay. Btw the device is
mounted through routing card STK600-RC008T-2 in a socket card STK600-DIP.
I did succeed to program a small trial program. It made some leds flashing. For
the first time I connected the leds through a flatribbon cable. What stunned me
is that led0 glowed a bit though it was not included in the program. Led0 is
connected to PB0 wich is the MOSI line! I removed the tiny from the socket
card, the led still glowed.
It appears that there is an issue in the routing card half grounding the MOSI
line. A routing card for a tiny4313 did not have this behavior with the same
socket card. I think we solved the problem here.
Thanks for your input!
Last question, can VTG be set only from AVR Studio, not with Avrdude or
something else running on a Mac?
Beste groeten, Gerrit.
Op 9 feb. 2013 om 18:00 heeft address@hidden het volgende geschreven:
> Send AVR-GCC-list mailing list submissions to
> address@hidden
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://lists.nongnu.org/mailman/listinfo/avr-gcc-list
> or, via email, send a message with subject or body 'help' to
> address@hidden
>
> You can reach the person managing the list at
> address@hidden
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of AVR-GCC-list digest..."
>
>
> Today's Topics:
>
> 1. Re: AVR-GCC-list Digest, Vol 97, Issue 1 (Gerrit Bosch)
> 2. Re: AVR-GCC-list Digest, Vol 97, Issue 1 (Joerg Wunsch)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Fri, 8 Feb 2013 20:10:36 +0100
> From: Gerrit Bosch <address@hidden>
> To: address@hidden
> Subject: Re: [avr-gcc-list] AVR-GCC-list Digest, Vol 97, Issue 1
> Message-ID: <address@hidden>
> Content-Type: text/plain; charset=us-ascii
>
> Dear Joerg,
>
> Thanks for your mail. I have been working on this a few hours today. There
> are a few things I forgot tov put in my email. Sorry.
> First is that the mega2560 socketcard that came with the STK600 works well.
> So it has to do with the tiny85.
> A logic analyser showed that the signals from the m2560 and the tiny85 were
> different. The tiny85 produced something like spikes.
> Not being an expert I read at the AVRDUDE man-page about the -B parameter. A
> value of 0.1e-120 solved the problem.
> I have no idea why. Is there some literature about this?
>
> Thanks again,
> Gerrit Bosch.
>
>
> Op 8 feb. 2013, om 18:00 heeft address@hidden het volgende geschreven:
>
>> Send AVR-GCC-list mailing list submissions to
>> address@hidden
>>
>> To subscribe or unsubscribe via the World Wide Web, visit
>> https://lists.nongnu.org/mailman/listinfo/avr-gcc-list
>> or, via email, send a message with subject or body 'help' to
>> address@hidden
>>
>> You can reach the person managing the list at
>> address@hidden
>>
>> When replying, please edit your Subject line so it is more specific
>> than "Re: Contents of AVR-GCC-list digest..."
>>
>>
>> Today's Topics:
>>
>> 1. stk600 (Gerrit Bosch)
>> 2. Re: stk600 (Joerg Wunsch)
>>
>>
>> ----------------------------------------------------------------------
>>
>> Message: 1
>> Date: Thu, 7 Feb 2013 22:09:08 +0100
>> From: Gerrit Bosch <address@hidden>
>> To: address@hidden
>> Subject: [avr-gcc-list] stk600
>> Message-ID: <address@hidden>
>> Content-Type: text/plain; charset=us-ascii
>>
>> Hello,
>>
>> Sorry I bother you all with a -for me- confusing but probably simple
>> problem. I am trying to use a STK600 to program a tiny85. Connecting to the
>> device fails, see below. What should I do??
>>
>> Using Mac OSX 10.7.5 with Crosspack AVR 20121207. This is from Terminal:
>>
>> iibmac:~ gbosch$ avrdude -c stk600 -p t85 -P usb:7A:5B -v
>>
>> avrdude: Version 5.11.1, compiled on Dec 6 2012 at 23:54:36
>> Copyright (c) 2000-2005 Brian Dean, http://www.bdmicro.com/
>> Copyright (c) 2007-2009 Joerg Wunsch
>>
>> System wide configuration file is
>> "/usr/local/CrossPack-AVR-20121207/etc/avrdude.conf"
>> User configuration file is "/Users/gbosch/.avrduderc"
>> User configuration file does not exist or is not a regular file,
>> skipping
>>
>> Using Port : usb:7A:5B
>> Using Programmer : stk600
>> avrdude: usbdev_open(): Found STK600, serno: 0048395C7A5B
>> AVR Part : ATtiny85
>> Chip Erase delay : 4500 us
>> PAGEL : P00
>> BS2 : P00
>> RESET disposition : possible i/o
>> RETRY pulse : SCK
>> serial program mode : yes
>> parallel program mode : yes
>> Timeout : 200
>> StabDelay : 100
>> CmdexeDelay : 25
>> SyncLoops : 32
>> ByteDelay : 0
>> PollIndex : 3
>> PollValue : 0x53
>> Memory Detail :
>>
>> Block Poll Page
>> Polled
>> Memory Type Mode Delay Size Indx Paged Size Size #Pages MinW
>> MaxW ReadBack
>> ----------- ---- ----- ----- ---- ------ ------ ---- ------ -----
>> ----- ---------
>> eeprom 65 6 4 0 no 512 4 0 4000
>> 4500 0xff 0xff
>> flash 65 6 32 0 yes 8192 64 128 4500
>> 4500 0xff 0xff
>> signature 0 0 0 0 no 3 0 0 0
>> 0 0x00 0x00
>> lock 0 0 0 0 no 1 0 0 9000
>> 9000 0x00 0x00
>> lfuse 0 0 0 0 no 1 0 0 9000
>> 9000 0x00 0x00
>> hfuse 0 0 0 0 no 1 0 0 9000
>> 9000 0x00 0x00
>> efuse 0 0 0 0 no 1 0 0 9000
>> 9000 0x00 0x00
>> calibration 0 0 0 0 no 2 0 0 0
>> 0 0x00 0x00
>>
>> Programmer Type : STK600
>> Description : Atmel STK600
>> Programmer Model: STK600
>> Hardware Version: 3
>> Firmware Version Master : 2.20
>> Firmware Version Slave 1: 2.01
>> Firmware Version Slave 2: 2.02
>> Routing card : STK600-RC008T-2
>> Socket card : STK600-DIP
>> RC_ID table rev : 47
>> EC_ID table rev : 1
>> Vtarget : 4.8 V
>> Varef 0 : 1.10 V
>> Varef 1 : 0.00 V
>> SCK period : 8.00 us
>> Oscillator : 16.007 MHz
>>
>> avrdude: stk500v2_command(): command failed
>> avrdude: stk500v2_program_enable(): bad AVRISPmkII connection status: MOSI
>> fail
>> avrdude: initialization failed, rc=-1
>> Double check connections and try again, or use -F to override
>> this check.
>>
>>
>> avrdude done. Thank you.
>>
>>
>> Anyone who can help?
>> Thanks, Gerrit.
>>
>>
>> ------------------------------
>>
>> Message: 2
>> Date: Fri, 8 Feb 2013 09:04:38 +0100 (MET)
>> From: address@hidden (Joerg Wunsch)
>> To: address@hidden
>> Subject: Re: [avr-gcc-list] stk600
>> Message-ID: <address@hidden>
>> Content-Type: text/plain; charset=us-ascii
>>
>> Gerrit Bosch <address@hidden> wrote:
>>
>>> Connecting to the device fails, see below. What should I do??
>>
>> Connect it correctly. ;-)
>>
>>> avrdude: stk500v2_program_enable(): bad AVRISPmkII connection status: MOSI
>>> fail
>>
>> This "MOSI fail" comes directly from the STK600's firmware, so you
>> have to convince the STK600. Do you have anything else attached to
>> the SPI lines, or are they only used for programming?
>>
>> --
>> cheers, J"org .-.-. --... ...-- -.. . DL8DTL
>>
>> http://www.sax.de/~joerg/ NIC: JW11-RIPE
>> Never trust an operating system you don't have sources for. ;-)
>>
>>
>>
>> ------------------------------
>>
>> _______________________________________________
>> AVR-GCC-list mailing list
>> address@hidden
>> https://lists.nongnu.org/mailman/listinfo/avr-gcc-list
>>
>>
>> End of AVR-GCC-list Digest, Vol 97, Issue 1
>> *******************************************
>
>
>
>
> ------------------------------
>
> Message: 2
> Date: Fri, 8 Feb 2013 21:07:58 +0100 (MET)
> From: address@hidden (Joerg Wunsch)
> To: address@hidden
> Subject: Re: [avr-gcc-list] AVR-GCC-list Digest, Vol 97, Issue 1
> Message-ID: <address@hidden>
> Content-Type: text/plain; charset=us-ascii
>
> Gerrit Bosch <address@hidden> wrote:
>
>> A logic analyser showed that the signals from the m2560 and the
>> tiny85 were different. The tiny85 produced something like spikes.
>
> Is the ATtiny85 located in an STK600 socket board, or off-board?
>
> If the latter, perhaps your ISP lines are too long, or perhaps you
> forgot to add bypass capacitors to the Vcc line?
>
>> Not being an expert I read at the AVRDUDE man-page about the -B
>> parameter. A value of 0.1e-120 solved the problem.
>
> Really 0.1E-120? That would be strange. :)
>
> For a standard 1-MHz-clocked AVR, -B10 normally ought to be a fairly
> conservative setting. For historical reasons, the ISP clock is given
> as the period time in microseconds, so -B10 corresponds to 100 kHz.
> The requirement is to be below 1/4 of the CPU clock, so for a default
> CPU clock of 1 MHz, your ISP frequency must be below 250 kHz
> (including all possible tolerances). -B4 might be at risk, but -B5 is
> guaranteed to satisfy this condition. -B10 has shown to improve the
> tolerance against all kind of poor cabling etc., at the cost of some
> programming speed of course.
>
> --
> cheers, J"org .-.-. --... ...-- -.. . DL8DTL
>
> http://www.sax.de/~joerg/ NIC: JW11-RIPE
> Never trust an operating system you don't have sources for. ;-)
>
>
>
> ------------------------------
>
> _______________________________________________
> AVR-GCC-list mailing list
> address@hidden
> https://lists.nongnu.org/mailman/listinfo/avr-gcc-list
>
>
> End of AVR-GCC-list Digest, Vol 97, Issue 2
> *******************************************
>
- Re: [avr-gcc-list] AVR-GCC-list Digest, Vol 97, Issue 2,
Gerrit Bosch <=