[bug #49387] ATXmega32E5 Flash section address wrong

[avrs-admin]

Georges Palauqui g.palauqui@gptechinno.com
Wed 19 Oct 2016 08:14:01 PM UTC
Device type: x32e5

Current avrdude.conf.in gives for ATxmega32e5 :
memory "apptable"
size = 0x1000;
offset = 0x00807000;
page_size = 0x80;
readsize = 0x100;
;
memory "boot"
size = 0x1000;
offset = 0x00808000;
page_size = 0x80;
readsize = 0x100;
;
But according to datasheet (http://www.atmel.com/Images/Atmel-8153-8-and-16-bit-AVR-Microcontroller-XMEGA-E-ATxmega8E5-ATxmega16E5-ATxmega32E5_Datasheet.pdf page 12 figure 8.1) it should be :
memory "apptable"
size = 0x800;
offset = 0x00803800;
page_size = 0x80;
readsize = 0x80;
;

memory "boot"
size = 0x800;
offset = 0x00804000;
page_size = 0x80;
readsize = 0x80;
;
Both Size and Offset are wrong.

This issue was migrated from https://savannah.nongnu.org/bugs/?49387

[mcuee]

It seems to me there are quite a bit of xmega related issues. Not able to help much as I do not have an xmega board. But I am not so sure if all of them are still relevant or not.

Ref: xmega relared issues

• [bug #27254] Cannot program ATXMega with AVRDUDE using AVR911 AVROSP mode #164
• [bug #29264] avrdude upload to xmega using stk500 protocol using byte addresses rather than word addresses #190
• [bug #29896] Add support for XMEGA specific AVR109 protocol extensions used by XBoot #200
• [bug #33160] JTAGICE mkII in JTAG mode, target not started correctly #226
• [bug #34994] avrdude does not send PDI offsets when erasing XMEGA chip #243
• [bug #39033] Support for ATxmegaXXXA4U devices #289
• [bug #40112] 6.0.1 - 911 flash upload fails #304
• [bug #40518] Using application with AVR109 on Xmega does not work as expected #311
• [bug #40702] fix: enable AVRISPmkII to read prodsig #314
• [bug #41878] AVR Dragon JTAG: ATxmega256A3BU hangs, when programming or reading device signature #337
• [bug #43577] Extended address not sent with avr109 #360
• [bug #43839] unable to verify device signature or program boot memory on xmega16d4 from ELF file #365
• [bug #45826] ATMEL-ICE content mismatch on Linux and OS X #391 (but also affect other AVR chips).
• [bug #46843] avrdude=>6 fails to write from 128k-mark onwards, loops back to 0x0000 #404
• [bug #49387] ATXmega32E5 Flash section address wrong #435
• [bug #51117] Problems with extended address (>128K) and buffer size #454

[MCUdude]

For reference, I've attached the ATxmega32E5.atdf file, which is used by Microchip Studio when working with the 32E5. I can only assume that this file has the correct content. All these files can be downloaded from Microchip Packs Repository.

ATxmega32E5.atdf.zip

From ATxmega32E5.atdf:

<memory-segment start="0x07000" size="0x1000" type="flash" rw="RW" exec="1" name="APPTABLE_SECTION" pagesize="128"/>

<property name="APPTABLE_SECTION_OFFSET" value="0x00807000"/>



<memory-segment start="0x08000" size="0x1000" type="flash" rw="RW" exec="1" name="BOOT_SECTION" pagesize="128"/>

<property name="BOOT_SECTION_OFFSET" value="0x00808000"/>

I'm closing this issue because OP may have read from a datasheet that had the memory addresses incorrectly defined. If this was a real problem, the latest ATxmega32E5.adtf would reflect OP's suggested changes.