[bug #43577] Extended address not sent with avr109 #360

avrs-admin · 2021-12-10T22:36:56Z

Arne Rossius arossius@ias.rwth-aachen.de
Tue 11 Nov 2014 02:14:43 PM UTC

When programming the ATxmega256a3 with avrdude 6.1 (windows version), the extended address is not sent when jumping across a 128 KiB boundary. I have created a text hexfile which only contains data for flash pages 0 (word address 0x00000) and 511 (word address 0x1FF00). However as can be seen from the attached log, after programming the first page only a 16-bit address command ('A') is sent instead of the 24-bit address command ('H'), resulting in an address of 0x0FF00 instead of 0x1FF00. Verify doesn't fail because the same happens when reading, but does fail when programming an actual application (without a gap) larger than 128 KiB.

The programmer is the "xboot" bootloader <https://github.com/alexforencich/xboot/wiki>. The avrdude.conf is unchanged.

Programming the attached hex file does work with the older avrdude 5.11 because this version programs pages 1 to 510 with 0xFF, only sending the address once before the first page and then relying on the bootloader's auto-increment to reach the high addresses. As can be expected, it takes a very long time though.

Also, as can be seen from the xboot source, it resets the extended address byte to zero when receiving an 'A' command. I'm not sure if this behaviour is correct, but if it is, this means that avrdude must send an 'H' command for all flash pages above 128 KiB (unless no address is sent at all between adjacent pages).

file #32418: napftest.hex
file #32419: avrdude-error.txt

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

avrs-admin · 2021-12-10T22:37:57Z

Joerg Wunsch <joerg_wunsch>
Tue 11 Nov 2014 04:48:58 PM UTC

The "extended address" is not part of the original AVR109
appnote.

bug #29896 has already been filed to request adding this
protocol extension, but has not been handled so far. (Sorry
for that.)

avrs-admin · 2021-12-10T22:37:58Z

Arne Rossius
Tue 11 Nov 2014 06:23:38 PM UTC

AFAICS, bug #29896 calls for additional memory types, while this bug is about accessing the area above 128 KiB of the regular flash memory (not bootloader area which is above 256 KiB for xmega256a3), so IMHO it's not a duplicate.

There is already a function in butterfly.c to send the 'H' command (butterfly_set_extaddr()), but it seems that the old butterfly_set_addr() is called instead. Surely this can't be right?

avrs-admin · 2021-12-10T22:38:00Z

Joerg Wunsch <joerg_wunsch>
Tue 11 Nov 2014 07:41:51 PM UTC

OK, sorry, then I misunderstood it. Reopening it, so I can
handle that (hopefully) alltogether.

mcuee · 2022-06-11T12:56:47Z

Hopefully #454 patch can fix this issue.

[bug #51117] Problems with extended address (>128K) and buffer size #454

mcuee · 2022-06-22T00:27:40Z

Ref: xmega relared open issues (Updated on 24-September-2022)
Unconfirmed issues

Confirmed as bug

[bug #43839] unable to verify device signature or program boot memory on xmega16d4 from ELF file #365
flip2: ATxmega32A4U DFU bootloader does not work even though Atmel FLIP 3.47 works fine. #1082 (on 21-Aug-2022)

Enhancement request:

[bug #29896] Add support for XMEGA specific AVR109 protocol extensions used by XBoot #200 (enhancement)
[patch #9563] New feature: ability to reset FLIPv2 targets #733 (enhancement request, with patch)

Recently closed issues:

mcuee · 2022-08-07T10:32:27Z

The test results in #454 show that no issues with ATmega2560 with xboot. But that is based on ATmega2560 with xboot, not ATxmega256a3. Need to get some one to help testing here as I do not have ATxmega256a3. Hopefully Hans can get a hold of the board soon.

[bug #51117] Problems with extended address (>128K) and buffer size #454

mcuee · 2022-08-08T03:44:45Z

https://savannah.nongnu.org/bugs/?29896 is now #200, which is an enhancement request.

[bug #29896] Add support for XMEGA specific AVR109 protocol extensions used by XBoot #200

The issue here in #360 (or #454) is different. By right, avrdude already supports ATmega256x long ago with the following commit on 30-Jan-2007.
6fc6e9b

This issue here is saying that it somehow does not work with ATxmega2560A3. This needs to be confirmed. So I will change the label.

mcuee · 2022-09-24T00:23:29Z

@MCUdude

Now that you have access to the ATxmega256A3BU Xplained board, please take a look at this one and #404 when you got a chance. Thanks.

MCUdude · 2022-09-24T17:36:53Z

I compiled xboot for ATxmega256A3BU, and I'm able to communicate with Avrdude using the bootloader:

$ ./avrdude -cavr109 -p atxmega256a3bu -b 115200 -P /dev/cu.usbserial-1410 

Connecting to programmer: .
Found programmer: Id = "XBoot++"; type = S
    Software Version = 1.7; No Hardware Version given.
Programmer supports auto addr increment.
Programmer supports buffered memory access with buffersize=512 bytes.

Programmer supports the following devices:
    Device code: 0x7b

avrdude: AVR device initialized and ready to accept instructions

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

avrdude: Device signature = 0x1e9843 (probably x256a3bu)

avrdude done.  Thank you.

I can also read from flash:

$ ./avrdude -cavr109 -p atxmega256a3bu -b 115200 -P /dev/cu.usbserial-1410 -Uflash:r:-:I

Connecting to programmer: .
Found programmer: Id = "XBoot++"; type = S
    Software Version = 1.7; No Hardware Version given.
Programmer supports auto addr increment.
Programmer supports buffered memory access with buffersize=512 bytes.

Programmer supports the following devices:
    Device code: 0x7b

avrdude: AVR device initialized and ready to accept instructions

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

avrdude: Device signature = 0x1e9843 (probably x256a3bu)
avrdude: NOTE: Programmer supports page erase for Xmega devices.
         Each page will be erased before programming it, but no chip erase is performed.
         To disable page erases, specify the -D option; for a chip-erase, use the -e option.
avrdude: reading flash memory ...

Reading | ################################################## | 100% 26.46s

avrdude: flash is empty, resulting file has no contents
avrdude: writing output file <stdout>
:00000001FF

avrdude done.  Thank you.

However, I'm not able to write:

$ ./avrdude -cavr109 -p atxmega256a3bu -b 115200 -P /dev/cu.usbserial-1410 -Uflash:w:/Users/hans/Downloads/XMEGA_A3BU_XPLAINED_DEMO1.hex:i

Connecting to programmer: .
Found programmer: Id = "XBoot++"; type = S
    Software Version = 1.7; No Hardware Version given.
Programmer supports auto addr increment.
Programmer supports buffered memory access with buffersize=512 bytes.

Programmer supports the following devices:
    Device code: 0x7b

avrdude: AVR device initialized and ready to accept instructions

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

avrdude: Device signature = 0x1e9843 (probably x256a3bu)
avrdude: NOTE: Programmer supports page erase for Xmega devices.
         Each page will be erased before programming it, but no chip erase is performed.
         To disable page erases, specify the -D option; for a chip-erase, use the -e option.
avrdude: reading input file /Users/hans/Downloads/XMEGA_A3BU_XPLAINED_DEMO1.hex for flash
avrdude: writing 35062 bytes flash ...

Writing | #                                                  | 1% 0.00s ***failed;  
 ***failed;  
 ***failed;  
 ***failed;  
 ***failed;  
 ***failed;  
 ***failed;  
 ***failed;  
 ***failed;  
 ***failed;  
 ***failed;  
 ***failed;  
 ***failed;  
 ***failed;  

...

 ***failed;  
 ***failed;  
 ***failed;  
 ***failed;  
 ***failed;  
 ***failed;  
 ***failed;  
 ***failed;  
 ***failed;  
Writing | ################################################## | 100% 0.10s

avrdude: 35062 bytes of flash written
avrdude: verifying flash memory against /Users/hans/Downloads/XMEGA_A3BU_XPLAINED_DEMO1.hex

Reading | ################################################## | 100% 3.46s

avrdude: verification error, first mismatch at byte 0x0000
         0xff != 0xec
avrdude: verification error; content mismatch

avrdude done.  Thank you.

MCUdude · 2022-09-24T17:51:46Z

It turns out that I forgot to add the -e flag. Now I can get the bootloader to work. I'll try with a bigger file soon.

$ ./avrdude -cavr109 -p atxmega256a3bu -b 115200 -P /dev/cu.usbserial-1410 -e -Uflash:w:/Users/hans/Downloads/XMEGA_A3BU_XPLAINED_DEMO1.hex:i

Connecting to programmer: .
Found programmer: Id = "XBoot++"; type = S
    Software Version = 1.7; No Hardware Version given.
Programmer supports auto addr increment.
Programmer supports buffered memory access with buffersize=512 bytes.

Programmer supports the following devices:
    Device code: 0x7b

avrdude: AVR device initialized and ready to accept instructions

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

avrdude: Device signature = 0x1e9843 (probably x256a3bu)
avrdude: erasing chip
avrdude: reading input file /Users/hans/Downloads/XMEGA_A3BU_XPLAINED_DEMO1.hex for flash
avrdude: writing 35062 bytes flash ...

Writing | ################################################## | 100% 4.29s

avrdude: 35062 bytes of flash written
avrdude: verifying flash memory against /Users/hans/Downloads/XMEGA_A3BU_XPLAINED_DEMO1.hex

Reading | ################################################## | 100% 3.46s

avrdude: 35062 bytes of flash verified

avrdude done.  Thank you.

MCUdude · 2022-09-24T17:57:27Z

@mcuee I can confirm that there's an issue writing to addresses above 128kiB.

$ ./avrdude -cavr109 -p atxmega256a3bu -b 115200 -P /dev/cu.usbserial-1410 -e -Uflash:w:0x55_256kib.hex 

Connecting to programmer: .
Found programmer: Id = "XBoot++"; type = S
    Software Version = 1.7; No Hardware Version given.
Programmer supports auto addr increment.
Programmer supports buffered memory access with buffersize=512 bytes.

Programmer supports the following devices:
    Device code: 0x7b

avrdude: AVR device initialized and ready to accept instructions

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

avrdude: Device signature = 0x1e9843 (probably x256a3bu)
avrdude: erasing chip
avrdude: reading input file 0x55_256kib.hex for flash
avrdude: writing 262143 bytes flash ...

Writing | ################################################## | 100% 31.83s

avrdude: 262143 bytes of flash written
avrdude: verifying flash memory against 0x55_256kib.hex

Reading | ################################################## | 100% 25.66s

avrdude: verification error, first mismatch at byte 0x1ffff
         0xff != 0x55
avrdude: verification error; content mismatch

avrdude done.  Thank you.

mcuee mentioned this issue May 30, 2022

[bug #49387] ATXmega32E5 Flash section address wrong #435

Closed

mcuee mentioned this issue Jun 11, 2022

[bug #51117] Problems with extended address (>128K) and buffer size #454

Closed

mcuee added the bug Something isn't working label Jun 19, 2022

mcuee mentioned this issue Jun 20, 2022

[bug #46843] avrdude=>6 fails to write from 128k-mark onwards, loops back to 0x0000 #404

Closed

dl8dtl added enhancement New feature or request and removed bug Something isn't working labels Jun 23, 2022

mcuee mentioned this issue Jul 22, 2022

[bug #39033] Support for ATxmegaXXXA4U devices #289

Closed

This was referenced Aug 6, 2022

[bug #40518] Using application with AVR109 on Xmega does not work as expected #311

Closed

[bug #40112] 6.0.1 - 911 flash upload fails #304

Closed

mcuee added unconfirmed Maybe a bug, needs to be reproduced by someone else and removed enhancement New feature or request labels Aug 8, 2022

MCUdude mentioned this issue Sep 24, 2022

Fix avr109 extended address #1101

Merged

mcuee added bug Something isn't working and removed unconfirmed Maybe a bug, needs to be reproduced by someone else labels Sep 25, 2022

stefanrueger closed this as completed in 62aa480 Oct 5, 2022

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

[bug #43577] Extended address not sent with avr109 #360

[bug #43577] Extended address not sent with avr109 #360

avrs-admin commented Dec 10, 2021

avrs-admin commented Dec 10, 2021

avrs-admin commented Dec 10, 2021

avrs-admin commented Dec 10, 2021

mcuee commented Jun 11, 2022

mcuee commented Jun 22, 2022 •

edited

Loading

mcuee commented Aug 7, 2022 •

edited

Loading

mcuee commented Aug 8, 2022 •

edited

Loading

mcuee commented Sep 24, 2022

MCUdude commented Sep 24, 2022

MCUdude commented Sep 24, 2022

MCUdude commented Sep 24, 2022

[bug #43577] Extended address not sent with avr109 #360

[bug #43577] Extended address not sent with avr109 #360

Comments

avrs-admin commented Dec 10, 2021

avrs-admin commented Dec 10, 2021

avrs-admin commented Dec 10, 2021

avrs-admin commented Dec 10, 2021

mcuee commented Jun 11, 2022

mcuee commented Jun 22, 2022 • edited Loading

mcuee commented Aug 7, 2022 • edited Loading

mcuee commented Aug 8, 2022 • edited Loading

mcuee commented Sep 24, 2022

MCUdude commented Sep 24, 2022

MCUdude commented Sep 24, 2022

MCUdude commented Sep 24, 2022

mcuee commented Jun 22, 2022 •

edited

Loading

mcuee commented Aug 7, 2022 •

edited

Loading

mcuee commented Aug 8, 2022 •

edited

Loading