As sq5rix wrote: > Hmm, I know that - that's why I load code to processor before > debugging - then I manually change debugWire fuse. I miss something > here....
But it seems your Eclipse always wants to (re-)load it anyway: (From the avrfreaks thread:) > buffering data, 48 bytes @ 0x19e0 > buffering data, 48 bytes @ 0x1a10 > buffering data, 48 bytes @ 0x1a40 > buffering data, 48 bytes @ 0x1a70 > buffering data, 24 bytes @ 0x1aa0 > committing to flash > Failed to write target memory space: debugWIRE failed > When I start avr-dbg manually like > > avr-dbg Enkoder.elf > > I see the source code in list command and I can debug. OK, that's expected. ;-) It might even work from inside Eclipse, provided you can tell it to not reload the flash first. 73 es 55! -- cheers, Joerg .-.-. --... ...-- -.. . DL8DTL http://www.sax.de/~joerg/ Never trust an operating system you don't have sources for. ;-) ------------------------------------------------------------------------------ Transform Data into Opportunity. Accelerate data analysis in your applications with Intel Data Analytics Acceleration Library. Click to learn more. http://makebettercode.com/inteldaal-eval _______________________________________________ avarice-user mailing list avarice-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/avarice-user
