[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [avr-chat] xmega lock bits vs avrdude
From: |
Weddington, Eric |
Subject: |
Re: [avr-chat] xmega lock bits vs avrdude |
Date: |
Thu, 14 Jul 2011 11:29:10 -0600 |
Hi David,
AFAIK, Atmel has not publicly released the xmega programming protocol. You'll
probably have to do this with AVR Studio.
> -----Original Message-----
> From: address@hidden [mailto:avr-
> address@hidden On Behalf Of David
> Martin
> Sent: Wednesday, July 06, 2011 8:47 AM
> To: address@hidden
> Subject: [avr-chat] xmega lock bits vs avrdude
>
> I cannot program the lock bits on an XMEGA128, via avrdude.
> I found this bug: http://savannah.nongnu.org/bugs/?30451
> But it does not seem to have any tracking, over a year old.
>
> Is there a way to program the lockbits, without Studio? I am at a loss.
>
> Log file:
> avrdude: Version 5.10, compiled on Jun 20 2011 at 17:56:07
> Copyright (c) 2000-2005 Brian Dean, http://www.bdmicro.com/
> Copyright (c) 2007-2009 Joerg Wunsch
>
> System wide configuration file is "/usr/local/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
> avrdude: usbdev_open(): using read endpoint 0x82
> 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: erasing chip
> avrdude: reading input file "0x00"
> avrdude: writing lock (1 bytes):
>
> Writing | avrdude: stk600_xprog_write_byte(): unknown memory "lock"
> ***failed;
> ################################################## | 100% 0.00s
>
> avrdude: 1 bytes of lock written
> avrdude: verifying lock memory against 0x00:
> avrdude: load data lock data from input file 0x00:
> avrdude: input file 0x00 contains 1 bytes
> avrdude: reading on-chip lock data:
>
> Reading | avrdude: 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.
>
>
> --
> David L. Martin
> address@hidden
>
> _______________________________________________
> AVR-chat mailing list
> address@hidden
> https://lists.nongnu.org/mailman/listinfo/avr-chat