??? 08/21/06 04:31 Read: times |
#122672 - If you want to know what's going on in each MCU Responding to: ???'s previous message |
then you have to consider how it uses the clock. In "the bible" there's a description, for example, of how the MCU interacts with the serial port and the timers, etc. If you want everything tightly coupled, which would be the only reason for using the same oscillator, then you'd want to study that out very carefully.
If you're using loosely coupled communications, then there's no real need for precisely synchronized oscillators. If you don't need the syncrhonization, then your next concern should be the effects of having that 12 MHz or faster clock running around the board. It's much easier on the signal-quality guy's nerves if you distribute a slow clock and sunchronize with that, if it's at all necessary. Think required rather than desired. Never put in any feature you don't absolutely require. If you leave a feature out, it's for sure that it won't cause trouble. RE |
Topic | Author | Date |
Mulitple 8051 from a single clock source. | 01/01/70 00:00 | |
buffers and so on | 01/01/70 00:00 | |
A definite "maybe" | 01/01/70 00:00 | |
Thanks. | 01/01/70 00:00 | |
How many and how far apart? | 01/01/70 00:00 | |
As many as possible I guess. | 01/01/70 00:00 | |
As many as possible I guess. | 01/01/70 00:00 | |
Yes, but is it a million or a dozen? | 01/01/70 00:00 | |
Can not relay on timing. | 01/01/70 00:00 | |
If you want to know what's going on in each MCU | 01/01/70 00:00 | |
Possibilities | 01/01/70 00:00 | |
what's the problem? | 01/01/70 00:00 | |
systolic networks![]() | 01/01/70 00:00 |