Re: [avr-gcc-list] Debugging a bootloader with JTAGICE mkII

[Ben L. Titzer]

Which microcontroller are you using? You might be interested in 
checking out Avrora; I've added support for flash updates recently, and 
some people at UCLA using the ATMega128 on Berkeley motes are doing 
over-the-air programming of the flash. There are still some bugs to 
work out tho.

This functionality is not yet in the release code, but is available in 
the latest CVS code.

http://compilers.cs.ucla.edu/avrora

On Apr 22, 2005, at 4:18 PM, Wallace White wrote:

> 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 program a
> lookup table in flash.) I see that this is a known bug of AVR Studio
> (see 
> http://lists.gnu.org/archive/html/avr-libc-dev/2005-04/msg00020.html).
> You can debug from the .hex file, but you lose source-level info.
>
> I got the same result with extcoff into AVR Studio.
>
> I would try gdb and avarice, but I read in the WinAVR manual that
> avarice doesn't yet support the JTAGICE mkII.
>
> It's looking like there's no way to do source-level debug with a
> bootloader with the mkII? I'm gonna get real familiar with
> disassembled code, then, or find an ur-JTAGICE...
>
> Thanks,
> Wallace
>
>
> _______________________________________________
> AVR-GCC-list mailing list
> address@hidden
> http://lists.nongnu.org/mailman/listinfo/avr-gcc-list
========================================================
Before we work on artificial intelligence, why don't we do something 
about natural stupidity?
--Steve Polyak