Ought to work just fine. If they are using the same clock, then if the baud rates are also set to be the same, the baud rates WILL be the same. This should be as close to zero-error async serial as you can get. You can also use any arbitrary baud rate for the micro-micro link as it does not have to fit any standard in order to talk to a desktop host. An external clock source should be good. There should be little or no interaction between the two clocked chips. Jim Wagner On 27 Mar 2007 10:08:56 -0700,Tue, 27 Mar 2007 11:08:49 -0600 "Cat C" <catalin_cluj@hotmail.com> wrote: > Hello, > > I have this idea that I think should work, but might have > some problems... > > The first "A" (Mega8) would do some specialized tasks, > and it currently > talks to a PC through it's serial port. The PC issues > commands, and gets > results. > > I want to replace the PC with a second "B" controller > (I'm thinking Mega324 > so I can connect one serial to "A", and another serial to > a PC if needs be). > > Would I have any problems if I clock both from the same > (external) clock > source? > > I'm also thinking I may need faster speed, so I might > connect one 8 bit port > from "A" to "B" to transmit 8 bits at a time... and maybe > use another 2 bits > (interrupt input?) of another port for "Data Ready" and > "ACK". > > Am I missing something? > > The SPI of "A" is already used and I'd rather not share > it even if it would > be possible. > > If SPI would be much better... I might chose another > controller that has 2 > SPI ports if such a thing exists...? > > Thank you, > > Cat > > _________________________________________________________________ > http://local.live.com/?mkt=en-ca/?v=2&cid=A6D6BDB4586E357F!420 > --------------------------------------------------------------- The Think Different Store http://www.thinkdifferentstore.com/ For All Your Mac Gear ---------------------------------------------------------------
Message
Re: [AVR-Chat] Connecting to microcontrollers to the same clock and between them
2007-03-27 by Jim Wagner
Attachments
- No local attachments were found for this message.