Nobody uses a frequency counter any more. Why not set a multifunction counter up for a start/stop period measurement...then if you can talk to it over any interface bus, let that puppy, the microcontroller circuit, run and log the time periods to run the routine. After a while, take an average. If you have an el spiffo counter, you can program that to do the averaging too. REB David VanHorn wrote: >>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. > > [Non-text portions of this message have been removed]
Message
Re: [AVR-Chat] Re: code speed optimization
2007-12-30 by Roy E. Burrage
Attachments
- No local attachments were found for this message.