Perhaps we should email? mik.ka...@gmail.com Am 04.11.2015 10:42 schrieb "Hannu Vuolasaho" <vuo...@msn.com>:
> > > Michael wrote: > > > > ; Were'synced > > ; calculate output part 1 > > ; wait 2300 cycles > > ; Read inputs > > ; Choose output port > > ; calculate output part 2 > > ; 170 cycles after read write output > > > > This same routine runs parallel in 3 different MCUs? > > So they have to be hardware synced. > > > > Make MCU0 the master, slaves are MCU1 and MCU2 then. > > > > MCU0 needs 2 sync-signal input port pins. > > > > MCU1+2 need 1 sync-signal output port pin. > > > > MCU1 and MCU2 need a ready input pin. > > > > When R is done, MCU1+2 set their sync signal port bit. > > > > Connect MCU2-sync-out --> MCU0-sync2-in > > Connect MCU1-sync-out --> MCU0-sync1-in > > Connect MCU0-ready-out --> MCU1+2-ready-in > > > > When Master MCU0 is ready, it pulls those incomming sync-bits until all > > are set. Now master sets his ready port pin for MCU2 and MCU3. Now you > > are synced again. Proceed... > > > > Is that what was on your mind? > > That was my first idea. There are two problems, mechanical space and > isolation. > The clock signal is optocoupler isolated and using more pins doesn't fit > and > decoupling more signals would also use too much space. > > However I'm trying to tackle this problem with simavr. > > If that doesn't help I'll wirite something which calculates time for me > from source files. > > Hannu Vuolasaho > > > ------------------------------------------------------------------------------ > _______________________________________________ > Amforth-devel mailing list for http://amforth.sf.net/ > Amforth-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/amforth-devel > ------------------------------------------------------------------------------ _______________________________________________ Amforth-devel mailing list for http://amforth.sf.net/ Amforth-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amforth-devel
