Thanks to Larry and Bruce I have the bootloader source code, however I would
like to integrate it into my main application. That is rather than flashing
the micro with the bootloader and then loading the application I would like
to combine the bootloader with my application. I am still trying to
I took Jason Kyle's boot-loader and reworked it to fit in 512 words. A
version that should be relatively easy to modify for your needs can be found
in the files section of Yahoogroups avrrobotcontrol You will need to sign
up for Yahoogroups to see it download. it is a stand-alone program using
Larry Barello wrote:
--
I took Jason Kyle's boot-loader and reworked it to fit in 512 words.
A version that should be relatively easy to modify for your needs can
be found in the files section of Yahoogroups avrrobotcontrol You
will need to sign up for Yahoogroups to see it download. it
Thanks!
IIRC you can cut out the EEPROM support and the boot loader fits into 256
words.
While paring down the size I cut out the C startup (there is no main())
runtime support and moved statics/globals into automatics assuming they
would go onto the stack. However that clever
. Lightner'
Cc: 'Trampas'; 'AVR GCC List'
Subject: RE: [avr-gcc-list] AT90CAN128 bootloader
Thanks!
IIRC you can cut out the EEPROM support and the boot loader fits into 256
words.
While paring down the size I cut out the C startup (there is no main())
runtime support and moved statics
GCC List'
Subject: RE: [avr-gcc-list] AT90CAN128 bootloader
Larry,
I have some stupid questions. Does the AVRDUDE and/or AVR Studio send out 0
to start programming? Is there some specification somewhere? What happens
if user does hit 0 by accident?
I would very much like to do two
gprand [EMAIL PROTECTED] wrote:
IMHO this is a bug in boot.h.
There are defined this conditions: #elif (FLASHEND USHRT_MAX)
(__USING_MINT8)
Already fixed in CVS (quite some time ago).
--
cheers, Jorg .-.-. --... ...-- -.. . DL8DTL
http://www.sax.de/~joerg/
IMHO this is a bug in boot.h.
There are defined this conditions: #elif (FLASHEND USHRT_MAX)
(__USING_MINT8)
I have no idea for wheach reason mint8 is bound there, but if you remove
this term then the xxx_extended macros will be used and they deal correct
with RAMPZ.
Gottfried
--
View this
1: The flash addressing most significant bit
AT90CAN128 has more than 64Kb of memory so you have a bit to say if
you are acessing the most significant part or the memory address. Pay
attention to this
The RAMPZ register needs to be set accordingly to determine which 64K
page of flash memory