> In the book Excel by Example, it teaches you how to create a sheat > to calculate the MCU cycles based on assembly file. > This will be more acurate than using an Osciloscope, but not easier. I agree in principle, but in practice, with non-trivial routines, it becomes unwieldy to calculate every possibility. Much easier to scope it, throw real data in, and measure min and max. Besides, simulated results are just that. Simulated. You might miss a path, but the running code won't.
Message
Re: [AVR-Chat] Re: code speed optimization
2007-12-29 by David VanHorn