Forum Menu




 


Log in Problems?
New User? Sign Up!
AVR Freaks Forum Index

Post new topic   Reply to topic
View previous topic Printable version Log in to check your private messages View next topic
Author Message
ganzziani
PostPosted: Sep 13, 2010 - 04:32 AM
Resident


Joined: Jun 16, 2006
Posts: 616
Location: Sarasota, FL

1) Yes, of course. I am using a PDI programmer to initially program xboot on the XMEGA (AVRISP mkii). You can see that the device is programmed because on the avrdude output, the xmega sends the correct device Id:
Found programmer: Id = "XBoot++"; type = S

The xboot-read.hex I included on the zip, is the hex file read out from the xmega after it was programmed (not the one generated from the source code).

2) This is how I call avrdude from the console:
avrdude -v -v -p atxmega32a4 -P com1 -c avr109 -b 19200 -U flash:w:xminilab.hex

_________________
www.gabotronics.com
 
 View user's profile Send private message Visit poster's website 
Reply with quote Back to top
radbrad
PostPosted: Sep 13, 2010 - 05:16 AM
Rookie


Joined: Mar 31, 2006
Posts: 48
Location: Corvallis, Oregon

Yeah, wish I could be of more help. Like I said, I've seen this error before when programming XBoot with the AVRISP mkII, and I should have documented it but didn't.

Did you use the given Makefile when blowing the bootloader in with the AVRISP mkII? I couldn't get the bootloader in properly until I used the Makefile.

Haven't thoroughly examined the HEX file, but it appears the program starts in about the right spot for your ATXMega32. That doesn't mean much though - I've been there and had it fail still. Again, the Makefile works properly for this.

Your avrdude command is equivalent to what I use - I don't see a problem there.

_________________
_________________
Brad Nelson
http://bradsprojects.wordpress.com
 
 View user's profile Send private message Visit poster's website 
Reply with quote Back to top
ganzziani
PostPosted: Sep 13, 2010 - 06:03 PM
Resident


Joined: Jun 16, 2006
Posts: 616
Location: Sarasota, FL

I'm still struggling... I've tried several settings with no success. I have used the provided Makefile and I also have let AVRStudio handle the build, specifying the address: -Wl,--section-start=.text=8000

To rule out I don't have a bad avrdude, can someone please send me the latest avrdude Windows executable and .conf file?

_________________
www.gabotronics.com
 
 View user's profile Send private message Visit poster's website 
Reply with quote Back to top
clawson
PostPosted: Sep 13, 2010 - 06:09 PM
10k+ Postman


Joined: Jul 18, 2005
Posts: 62227
Location: (using avr-gcc in) Finchingfield, Essex, England

If you can't get Xboot to work why battle on? - it's not as if there aren't tens of different bootloaders you could adapt - many of them using AVR109 (though it's a kind of out-dated protocol for X use)

_________________
 
 View user's profile Send private message  
Reply with quote Back to top
ganzziani
PostPosted: Sep 13, 2010 - 07:27 PM
Resident


Joined: Jun 16, 2006
Posts: 616
Location: Sarasota, FL

I tried damien_d's bootloader (gcc port of AVR1605):

a) I get the same verification error with avrdude.
b) I tried with AVROSP (the one provided with AVR1605), the bootloader is recognized and the signature bytes match, but I get this error:
[Programmer pagesize is not set!]

Attached are my projects in case someone has time to check them.

Thanks

_________________
www.gabotronics.com
 
 View user's profile Send private message Visit poster's website 
Reply with quote Back to top
Display posts from previous:     
Jump to:  
All times are GMT + 1 Hour
Post new topic   Reply to topic
View previous topic Printable version Log in to check your private messages View next topic
Powered by PNphpBB2 © 2003-2006 The PNphpBB Group
Credits