Hi Marc,
AVaRICE (v2.8) seems to support the ATtiny167, so you should be able to
debug it from Eclipse. Take a look at the AVR Eclipse Plugin debugging
tutorial ( http://avr-eclipse.sourceforge.net/wiki/index.php/Debugging )
on how to set everything up. With the right setup the debugger will
transfer your application to your ATtiny167 Flash mem. It won't burn
fuses and lockbits and it probably won't program the EEPROM, but maybe
you can live without this.
AVaRICE could also be used to program this MCU (incl. fuses etc.), but
this is not supported by the plugin (yet -- I am working on it :-). In
the meantime you could set up avarice as an 'External Tool' in Eclipse
to use it as a programmer.
brgds,
Thomas
Erwan MARC wrote:
Hello,
I have to use an ATTiny167 for an application and foud out that
avr-gcc tool chain was ready for this part. On an other side, I'd like
to use eclipse for may developments on several targets (Atmel or not)
so I was pleased to find the avr-plugin for eclipse.
The compilation step is perfect, easy to implement but after that for
programming (and debugging) I face a problem:
avrdude is not able to manage this part, nor through avrISP or JTAGICE.
I'm not a specialist of ISP protocol but why is is necessary to make
specific work for such a new part?
Then is it possible to program the chip with .elf file on an other
tool (such as avr studio :-( ) and come back to eclispe with gdb for
debugging purpose?
Do you have tips to remain all time on eclipse environment and avoid,
if possible, to switch to avr studio?
Regards
_______________________________________________
AVR-chat mailing list
[email protected]
http://lists.nongnu.org/mailman/listinfo/avr-chat