Does Dowloading a hex file of size >700k using xboot for Atxemaga 256A3 Work

[Anthony]

Hi

I have been working on xmega 128 A1 and Xmega 256A3

We have been using AVR open source Programmer and Xmega Boot laoder
Quick Start Guide fro getting the boot loader functioning

For smaller size hex file the AVR open Source works well both on xmeag
128A1 and for xmega 256 A3

However once the hex file size is larger >700K I always seem to get
and error when writing to Application Flash

When using Xboot with AVR Dude have you had any problems when wrting
700k hex files

Please do let me know

Regards

Anthony

[Bradley Nelson]

The hex file size is not directly useful.  Check the compiler output to find the actual flash code size - you are most likely beyond the programmable size of 256K.  Also check your optimization - you should be using the -s level of optimization.  I haven't pushed XBoot to any extremes yet, but it has programmed large files without any problems for me thus far.

Let me know if you still need help - good luck!

Brad

--
You received this message because you are subscribed to the Google Groups "avr-xboot" group.
To post to this group, send email to avr-...@googlegroups.com.
To unsubscribe from this group, send email to avr-xboot+...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/avr-xboot?hl=en.

[Anthony]

Hello Brad

Thank you for your reply

My mistake i should have been specific sorry for that

Hex file size 700Kb Windows Explorer

Actual Size of the code

112 508 bytes of CODE memory (+ 157 828 range fill )
14 154 bytes of DATA memory

We are able to download this code through the PDI/JTAG Interface using
the JTAGICE MKII so we are not beyond the limits of a 256k Flash
memory for xmega256 A3

But when we load this hex file using the AVROSP it fails to download
the hex file

Another hex file

Hex file size 148KB windows Explorer

Actual Size of the code

53 504 bytes of CODE memory (+ 52 range fill )
5 797 bytes of DATA memory

When we downlaod this file through AVROSP it works perfectly

Clock Frequency is the 2Mhz and Baud 9600

Have you tried the AVROSP programmer or you only used AVR Dude

Please can you send us a link of the AVR DUde that youhave made use
of

Regards

Anthony

> >http://groups.google.com/group/avr-xboot?hl=en.- Hide quoted text -
>
> - Show quoted text -

[Bradley Nelson]

Not sure what's going on.  I've only programmed XBoot using AVRDude on Linux (straight from the repository), as described on my blog.  Currently I'm using AVRDude version 5.10.  I haven't had any problems like what you're describing.  Friends of mine have also programmed to XBoot without too many issues from AVRDude in Windows.

I would recommend trying AVRDude with the "-v -v" options and posting the result.  Maybe Alex can help further debugging.

Brad

[Alex Forencich]

It's possible that the BAUD rate selections in XBoot.h are not quite
ideal. When I calculated the original BAUD rates I was optimizing for
BSCALE to be as close to zero as possible. That may not be completely
ideal. It's possible the error is showing up after long transfers, as
what might be happening in your case. To that end, try the following:

In xboot.h, change the 2 MHz, 9600 bps values as follows:

BSEL: 769
BSCALE: -6

Then try programming your chip via xboot and let us know how it works.

Alex Forencich

> +unsub...@googlegroups.com.

> For more options, visit this group at
> http://groups.google.com/group/avr-xboot?hl=en.
>
>
>
>
>

> --
> You received this message because you are subscribed to the Google
> Groups "avr-xboot" group.
> To post to this group, send email to avr-...@googlegroups.com.
> To unsubscribe from this group, send email to avr-xboot

> +unsub...@googlegroups.com.