...
> You're perhaps confusing that with debugWIRE.  As debugWIRE is a
> one-wire protocol, it has to live with delays, caused by RC time
> constants of the circuitry.
...
> ISP is basically the SPI engine of the controller, running in slave
> mode.  As the entire SPI engine is a synchronous system clocked by the
> IO clock of the AVR, the IO clock must be quite a bit faster than the
> ISP clock (the ISP clock line itself is sampled within the SPI engine,
> and ISP clock edges are detected during that sampling).

I have a question related to debugWIRE vs SPI internal to a Tiny88.
A colleague of mine, new to AVRs, tried to use debugWIRE to step
through some code that I gave him.  In my code I turned off the SPI
port through the Power Reduction Register.

Once he hit that point, the part died.  Anyway to recover them?
I did not expect to see any interaction of the SPI and debugWIRE
myself?



-- 
http://www.wearablesmartsensors.com/
http://www.softwaresafety.net/
http://www.designer-iii.com/
http://www.unusualresearch.com/


_______________________________________________
AVR-chat mailing list
[email protected]
http://lists.nongnu.org/mailman/listinfo/avr-chat

Reply via email to