Hello Johannes,
The load on the MCU may be heavily dependent on interrupt activity, particularly peripheral interrupts that are activated by external events, and over which you have no control. If it is possible for certain interrupts to occur very frequently due to the presence of noise, these may occupy a large portion of the available time.
In general, interrupt processing should be kept as short as possible, but if there can be wide variability in an ISR processing time, with the more lengthy periods occurring very infrequently, you will need to be aware of this, to allow for a worst case scenario that may be difficult to measure, or otherwise predict.
Assuming you are able to operate close to the maximum allowable bus frequency for the device, it should not matter which HCS08 derivative you choose, providing it has the resources that you need for the project. To substantially increase the throughput rate, you would need to choose a more powerful MCU family, such as ColdFire.
However, before considering such a step, you may find that you can reduce the loading on the MCU with code changes that control the frequency and/or duration of the interrupts.
A very simple method to see whether interrupt processing represents a significant load might be to toggle a pin at a single point within your main loop. If you get wide variability of the period between successive toggles, this probably indicates substantial ISR loading.
Incidently, a .S19 file size of 20k would probably represent code size of less than 8k.
Regards,
Mac
Message Edited by bigmac on
2008-05-01 01:42 PM