Wallace White <[EMAIL PROTECTED]> wrote:
> What setup are folks using to debug bootloaders, specifically with
> the JTAGICE mkII? Or are they?
Debug it as a standalone application (i.e. use a relocated .text
instead of .bootloader section).
Alas, on the ATmega128, you'll run into the additional
See http://gcc.gnu.org/bugs.html> for instructions.
Compiler version:
$ avr-gcc -v
Using built-in specs.
Target: avr
Configured with: ../configure --target=avr --prefix=/home/eisvogel/avr
--enable-languages=c,c++ --disable-nls
Thread model: single
gcc version 4.1.0
What setup are folks using to debug bootloaders, specifically with the
JTAGICE mkII? Or are they?
I've figured out that AVR Studio 4.11 SP2, when in debugging mode with
the JTAGICE mkII, doesn't load the .bootloader or other custom text
sections from the .elf file. (I'm using a bootloader to progr
p://gcc.gnu.org/bugs.html> for instructions.
Compiler version:
$ avr-gcc -v
Using built-in specs.
Target: avr
Configured with: ../configure --target=avr --prefix=/home/eisvogel/avr
--enable-languages=c,c++ --disable-nls
Thread model: single
gcc version 4.1.0 20050422 (experimental)
ttp://gcc.gnu.org/bugs.html> for instructions.
Compiler version:
$ avr-gcc -v
Using built-in specs.
Target: avr
Configured with: ../configure --target=avr --prefix=/home/eisvogel/avr
--enable-languages=c,c++ --disable-nls
Thread model: single
gcc version 4.1.0
