I have resorted to fixing the Microchip bug, once again by using a simple PAL which both qualifies the slave address, and gates the SPI clock to the slave. One would think the designers SO close to Motorola (Who did SPI SS WELL!) would have "inherited" some of the legacy. * | __O Thomas C. Sefranek WA1RHP@ARRL.NET |_-\<,_ Amateur Radio Operator: WA1RHP (*)/ (*) Bicycle mobile on 145.41, PL 74.4 http://hamradio.cmcorp.com/inventory/Inventory.html http://www.harvardrepeater.org > -----Original Message----- > From: pic microcontroller discussion list > [mailto:PICLIST@MITVMA.MIT.EDU]On Behalf Of Ian McLean > Sent: Sunday, January 25, 2004 5:42 PM > To: PICLIST@MITVMA.MIT.EDU > Subject: Re: [PIC:] multiple SPI slaves? > > > Yes ! I have also seen this behaviour when trying to use a slave > PIC and a > Dallas RTC using SPI (DS1305). The Slave Select does NOT work properly. > The slave PIC receives and shifts the buffer even when it is not > 'selected'. > Resorted to bit-bashing between PIC's. > > Rgs > Ian > > > -----Original Message----- > > From: pic microcontroller discussion list > > [mailto:PICLIST@MITVMA.MIT.EDU]On Behalf Of Tom Sefranek > > Sent: Monday, 26 January 2004 8:18 am > > To: PICLIST@MITVMA.MIT.EDU > > Subject: Re: [PIC:] multiple SPI slaves? > > > > > > I have one 18C452 as a master to 27 slaves (also 452s). > > > > Slave select is bogus on the PICs! (Even the F452s!) > > Slave select is an EDGE sync. for input data, and a gate for > > output data > > from the slave. > > > > The slave PICs WILL interrupt even if the SS is NOT active! > > (So your proposal to broadcast may actually ACCIDENTLY work!) > > > > Tom > > > > > > Bill Couture wrote: > > > > >Hi! > > > > > >I'm looking at a design for work where we would have one central PIC > > >playing communications host (probably an 18F452), and 8 > > "satellite" PICs > > >controlling hardware (16F818's), communicating via with the > > host via SPI. > > > > > >I'm worried, however, about "broadcast messages" to the > > satellite PICs. > > >Can the 16F818's listen even if the SS signal is not > > asserted? Or can > > >I assert all of the 16F818's SS lines and have everyone listen? > > > > > >And, what about the reply to the SPI master? Do I have to > > worry about the > > >"wired-OR" nature of the SDO line, or can I keep a 0 in the > > SPI transmit > > >register, and nobody sends a reply? > > > > > >If the question isn't clear enough, please ask for details. > > > > > >Thanks, > > > Bill > > > > > >-- > > >http://www.piclist.com#nomail Going offline? Don't AutoReply us! > > >email listserv@mitvma.mit.edu with SET PICList DIGEST in the body > > > > > > > > > > > > > > > > -- > > http://www.piclist.com#nomail Going offline? Don't AutoReply us! > > email listserv@mitvma.mit.edu with SET PICList DIGEST in the body > > -- > http://www.piclist.com#nomail Going offline? Don't AutoReply us! > email listserv@mitvma.mit.edu with SET PICList DIGEST in the body > > -- http://www.piclist.com#nomail Going offline? Don't AutoReply us! email listserv@mitvma.mit.edu with SET PICList DIGEST in the body