UART and I2C loading issues

25 views
Skip to first unread message

SteveS

unread,
Jun 22, 2011, 6:04:04 PM6/22/11
to avr-xboot
Not sure if this is supported or not... I've configured the latest
xboot to use both UART and I2C for entry and communications
(USE_ENTER_UART, USER_ENTER_I2C, USE_UART, USE_I2C all defined). I can
program xboot (using AVRStudio) without any problems, and it appears
to be working fine.

I then try to load an app using AVRDude - it communicates with xboot,
but then when it tries to read the EEPROM data it fails. Here's the
relevant output from AVRDude:


avrdude: Device signature = 0x1e9541
avrdude: NOTE: FLASH memory has been specified, an erase cycle will be
performed
To disable this feature, specify the -D option.
avrdude: Send: A [41] . [03] . [fc]
avrdude: Recv: . [0d]
avrdude: Send: g [67] . [00] . [01] E [45]
avrdude: Recv: . [ff]
avrdude: Send: A [41] . [03] . [fd]
avrdude: Recv: . [ff]
avrdude: error: programmer did not respond to command: set addr


If I then rebuild xboot without I2C support and reflash; everything
works fine.

Not sure if this is a bug or a feature...

Steve

Alex Forencich

unread,
Jun 22, 2011, 6:17:20 PM6/22/11
to avr-...@googlegroups.com
Probably a bug. I suppose I will have to look into it. What is the
code size of the hex file? Is it actually small enough to fit into the
boot section? After building with 'make', you should get something that
looks like this:

Size after:
xboot.elf :
section size addr
.text 0xcd0 0x4000
.BOOT 0x3a 0x4cd0
.bss 0x1 0x802000
.stab 0x38e8 0x0
.stabstr 0xb646 0x0
Total 0xfc39

.text size + .BOOT size must be less than the boot block size. What
does it look like for your configuration?

Alex Forencich

Steve Soloski

unread,
Jun 23, 2011, 9:27:09 AM6/23/11
to avr-...@googlegroups.com
Here's the size I get with both UART and I2C built in:

Size after:
xboot.elf  :
section      size       addr
.text       0xdf6     0x4000
.BOOT        0x3a     0x4df6
.bss          0x2   0x802000
.stab      0x3438        0x0
.stabstr   0xb630        0x0
Total      0xf89a

Seems like it's small enough... AVRStudio didn't complain when it programmed the chip. I'm also compiling with the -Os flag.

Steve


--
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.


Reply all
Reply to author
Forward
0 new messages