attiny40 on avrdude

classic Classic list List threaded Threaded
8 messages Options
Reply | Threaded
Open this post in threaded view
|

attiny40 on avrdude

justin cooke-2
Hi,
Is it possible to program the attiny40 with avrdude in ponyser mode? I understand there is no config entry in avrdude.conf, is it just a simple case of adding a new entry and supplying the correct details or is it just impossible for whatever reason?
Regards
Justin
_______________________________________________
avrdude-dev mailing list
[hidden email]
https://lists.nongnu.org/mailman/listinfo/avrdude-dev
Reply | Threaded
Open this post in threaded view
|

Re: attiny40 on avrdude

Joerg Wunsch
As justin cooke wrote:

> Is it possible to program the attiny40 with avrdude in ponyser mode?

I don't think it's possible at all, due to the timing constraints
implied by the TPI protocol.  I think this requires some kind of
controller support.

At the very least, even if it were possible, nobody contributed
TPI bit-bang code so far for use with these direct bit-bang
programmers, so it's not sufficient to just add a few lines of
config file, and be done with it.

(Better subscribe to the list if you want to participate in
communication.)
--
cheers, J"org               .-.-.   --... ...--   -.. .  DL8DTL

http://www.sax.de/~joerg/                        NIC: JW11-RIPE
Never trust an operating system you don't have sources for. ;-)

_______________________________________________
avrdude-dev mailing list
[hidden email]
https://lists.nongnu.org/mailman/listinfo/avrdude-dev
Reply | Threaded
Open this post in threaded view
|

Re: attiny40 on avrdude

René Liebscher
What about the patch #7724 "Add TPI support for Bus Pirate using bitbang
mode"?

I did not try it, but it claims to use TPI with bitbang mode. So maybe this
could be used for some further work on this topic.

Kind regards

René

>             -------- Original-Nachricht --------
> Datum: Tue, 5 Jun 2012 14:19:19 +0200
> Von: Joerg Wunsch <[hidden email]>
> An: "[hidden email]" <[hidden email]>
> CC: justin cooke <[hidden email]>
> Betreff: Re: [avrdude-dev] attiny40 on avrdude
>
>             As justin cooke wrote:
>
> > Is it possible to program the attiny40 with avrdude in ponyser mode?
>
> I don't think it's possible at all, due to the timing constraints
> implied by the TPI protocol.  I think this requires some kind of
> controller support.
>
> At the very least, even if it were possible, nobody contributed
> TPI bit-bang code so far for use with these direct bit-bang
> programmers, so it's not sufficient to just add a few lines of
> config file, and be done with it.
>
> (Better subscribe to the list if you want to participate in
> communication.)
> --
> cheers, J"org               .-.-.   --... ...--   -.. .  DL8DTL
>
> http://www.sax.de/~joerg/                        NIC: JW11-RIPE
> Never trust an operating system you don't have sources for. ;-)
>
> _______________________________________________
> avrdude-dev mailing list
> [hidden email]
> https://lists.nongnu.org/mailman/listinfo/avrdude-dev
>
       
--
Empfehlen Sie GMX DSL Ihren Freunden und Bekannten und wir
belohnen Sie mit bis zu 50,- Euro! https://freundschaftswerbung.gmx.de
_______________________________________________
avrdude-dev mailing list
[hidden email]
https://lists.nongnu.org/mailman/listinfo/avrdude-dev
Reply | Threaded
Open this post in threaded view
|

ATXMEGA128A1 lock byte

David L. Martin-2
In reply to this post by justin cooke-2
Has anyone successfully programed the ATXMEGA128A1 lock byte?

I appears I can program any of the Memory blocks except the lock byte.

Here is what I see:
avrdude -c avrispmkII -P usb -p atxmega128a1 -Ulock:w:0xFF:m -v

avrdude: Version 5.10, compiled on Mar 23 2010 at 15:05:31
          Copyright (c) 2000-2005 Brian Dean, http://www.bdmicro.com/
          Copyright (c) 2007-2009 Joerg Wunsch

          System wide configuration file is "/etc/avrdude.conf"
          User configuration file is "/home/dlmarti/.avrduderc"
          User configuration file does not exist or is not a regular
file, skipping

          Using Port                    : usb
          Using Programmer              : avrispmkII
avrdude: usbdev_open(): Found AVRISP mkII, serno: 000200055222
          AVR Part                      : ATXMEGA128A1
          Chip Erase delay              : 0 us
          PAGEL                         : P00
          BS2                           : P00
          RESET disposition             : dedicated
          RETRY pulse                   : SCK
          serial program mode           : yes
          parallel program mode         : yes
          Timeout                       : 0
          StabDelay                     : 0
          CmdexeDelay                   : 0
          SyncLoops                     : 0
          ByteDelay                     : 0
          PollIndex                     : 0
          PollValue                     : 0x00
          Memory Detail                 :

                                   Block Poll              
Page                       Polled
            Memory Type Mode Delay Size  Indx Paged  Size   Size #Pages
MinW  MaxW   ReadBack
            ----------- ---- ----- ----- ---- ------ ------ ---- ------
----- ----- ---------
            eeprom         0     0     0    0 no       2048   32      
0     0     0 0x00 0x00
            application    0     0     0    0 no     131072  256      
0     0     0 0x00 0x00
            apptable       0     0     0    0 no       8192  256      
0     0     0 0x00 0x00
            boot           0     0     0    0 no       8192  256      
0     0     0 0x00 0x00
            flash          0     0     0    0 no     139264  256      
0     0     0 0x00 0x00
            prodsig        0     0     0    0 no        512  256      
0     0     0 0x00 0x00
            usersig        0     0     0    0 no        512  256      
0     0     0 0x00 0x00
            signature      0     0     0    0 no          3    0      
0     0     0 0x00 0x00
            fuse0          0     0     0    0 no          1    0      
0     0     0 0x00 0x00
            fuse1          0     0     0    0 no          1    0      
0     0     0 0x00 0x00
            fuse2          0     0     0    0 no          1    0      
0     0     0 0x00 0x00
            fuse4          0     0     0    0 no          1    0      
0     0     0 0x00 0x00
            fuse5          0     0     0    0 no          1    0      
0     0     0 0x00 0x00
            lock           0     0     0    0 no          1    0      
0     0     0 0x00 0x00

          Programmer Type : STK500V2
          Description     : Atmel AVR ISP mkII
          Programmer Model: AVRISP mkII
          Hardware Version: 1
          Firmware Version Master : 1.13
          Vtarget         : 3.3 V
          SCK period      : 8.00 us

avrdude: AVR device initialized and ready to accept instructions

Reading | ################################################## | 100% 0.00s

avrdude: Device signature = 0x1e974c
avrdude: reading input file "0xFF"
avrdude: writing lock (1 bytes):

Writing |                                                    | 0%
0.00savrdude: stk600_xprog_write_byte(): unknown memory "lock"
  ***failed;
Writing | ################################################## | 100% 0.00s

avrdude: 1 bytes of lock written
avrdude: verifying lock memory against 0xFF:
avrdude: load data lock data from input file 0xFF:
avrdude: input file 0xFF contains 1 bytes
avrdude: reading on-chip lock data:

Reading |                                                    | 0%
0.00savrdude: stk600_xprog_read_byte(): unknown memory "lock"
avr_read(): error reading address 0x0000
     read operation not supported for memory "lock"
avrdude: failed to read all of lock memory, rc=-2

avrdude done.  Thank you.


_______________________________________________
avrdude-dev mailing list
[hidden email]
https://lists.nongnu.org/mailman/listinfo/avrdude-dev
Reply | Threaded
Open this post in threaded view
|

Re: ATXMEGA128A1 lock byte

Joerg Wunsch
As David L. Martin wrote:

> 0.00savrdude: stk600_xprog_write_byte(): unknown memory "lock"
>   ***failed;

That should be fixed in the SVN version.  Give it a try if you can.

Btw., trying to program the lock byte to 0xff is not useful.
Returning lock bits to `1' state can only be reached by means of a
chip erase.

--
cheers, J"org               .-.-.   --... ...--   -.. .  DL8DTL

http://www.sax.de/~joerg/                        NIC: JW11-RIPE
Never trust an operating system you don't have sources for. ;-)

_______________________________________________
avrdude-dev mailing list
[hidden email]
https://lists.nongnu.org/mailman/listinfo/avrdude-dev
Reply | Threaded
Open this post in threaded view
|

Re: ATXMEGA128A1 lock byte

David L. Martin-2
I understand that 0xff is not a useful value, it was just to dramatize
the error.  So even if the write failed, the read should pass, but
neither did.

Yes, I will try the svn version, thanks.

On 06/05/2012 03:30 PM, Joerg Wunsch wrote:

> As David L. Martin wrote:
>
>> 0.00savrdude: stk600_xprog_write_byte(): unknown memory "lock"
>>    ***failed;
> That should be fixed in the SVN version.  Give it a try if you can.
>
> Btw., trying to program the lock byte to 0xff is not useful.
> Returning lock bits to `1' state can only be reached by means of a
> chip erase.
>


_______________________________________________
avrdude-dev mailing list
[hidden email]
https://lists.nongnu.org/mailman/listinfo/avrdude-dev
Reply | Threaded
Open this post in threaded view
|

Re: attiny40 on avrdude

Darell Tan
In reply to this post by Joerg Wunsch
Hi Justin and Joerg,

It should actually be possible to use the ponyser programmer,
since the bitbang code is all the same.

All you need to do is to add the part definition for the attiny40
to avrdude.conf so it knows what the signature is, and its memory
locations, and you should be good to go.

Please add a 1K resistor from the ponyser MOSI pin before it
connects to TPIDATA pin on the attiny40.

If you do try it out, please keep us updated.

--
Regards,
Darell Tan



On Tue, Jun 5, 2012 at 8:19 PM, Joerg Wunsch <[hidden email]> wrote:

>
> As justin cooke wrote:
>
> > Is it possible to program the attiny40 with avrdude in ponyser mode?
>
> I don't think it's possible at all, due to the timing constraints
> implied by the TPI protocol.  I think this requires some kind of
> controller support.
>
> At the very least, even if it were possible, nobody contributed
> TPI bit-bang code so far for use with these direct bit-bang
> programmers, so it's not sufficient to just add a few lines of
> config file, and be done with it.
>
> (Better subscribe to the list if you want to participate in
> communication.)
> --
> cheers, J"org               .-.-.   --... ...--   -.. .  DL8DTL
>
> http://www.sax.de/~joerg/                        NIC: JW11-RIPE
> Never trust an operating system you don't have sources for. ;-)
>
> _______________________________________________
> avrdude-dev mailing list
> [hidden email]
> https://lists.nongnu.org/mailman/listinfo/avrdude-dev

_______________________________________________
avrdude-dev mailing list
[hidden email]
https://lists.nongnu.org/mailman/listinfo/avrdude-dev
Reply | Threaded
Open this post in threaded view
|

Re: attiny40 on avrdude

justin cooke-2
Thanks Darell, I'll try that out in the next few days and let you guys know.
Cheers
Justin

On 08/06/2012, at 12:53 AM, Darell Tan <[hidden email]> wrote:

> Hi Justin and Joerg,
>
> It should actually be possible to use the ponyser programmer,
> since the bitbang code is all the same.
>
> All you need to do is to add the part definition for the attiny40
> to avrdude.conf so it knows what the signature is, and its memory
> locations, and you should be good to go.
>
> Please add a 1K resistor from the ponyser MOSI pin before it
> connects to TPIDATA pin on the attiny40.
>
> If you do try it out, please keep us updated.
>
> --
> Regards,
> Darell Tan
>
>
>
> On Tue, Jun 5, 2012 at 8:19 PM, Joerg Wunsch <[hidden email]> wrote:
>>
>> As justin cooke wrote:
>>
>>> Is it possible to program the attiny40 with avrdude in ponyser mode?
>>
>> I don't think it's possible at all, due to the timing constraints
>> implied by the TPI protocol.  I think this requires some kind of
>> controller support.
>>
>> At the very least, even if it were possible, nobody contributed
>> TPI bit-bang code so far for use with these direct bit-bang
>> programmers, so it's not sufficient to just add a few lines of
>> config file, and be done with it.
>>
>> (Better subscribe to the list if you want to participate in
>> communication.)
>> --
>> cheers, J"org               .-.-.   --... ...--   -.. .  DL8DTL
>>
>> http://www.sax.de/~joerg/                        NIC: JW11-RIPE
>> Never trust an operating system you don't have sources for. ;-)
>>
>> _______________________________________________
>> avrdude-dev mailing list
>> [hidden email]
>> https://lists.nongnu.org/mailman/listinfo/avrdude-dev

_______________________________________________
avrdude-dev mailing list
[hidden email]
https://lists.nongnu.org/mailman/listinfo/avrdude-dev