>
>My first thought was yes. I understood that 8 bites of data can be
>transmitted synchronously with clock pulses.
>
>
>I'm trying to initiate a communication using master1 mode, the
>sspstat = 0b_0000_0000 and sspcon = 0b_0010_0010 are set appropiate
>for fosc/64. The pins used are rc3 ( spi-clk ) and rc4 ( spi-data in )
>and an extra pin for chip select, all direction are set correct in
>TRIS register.
>

>( I don't want to use
>slave mode ). And I don't saw any damn clock on to my scope...
>
>Thank you in advance,
>Vasile
>
>--
>http://www.piclist.com hint: To leave the PICList
>piclist-unsubscribe-requestKILLspammitvma.mit.edu
>
>
>

>
> Sorry for bothering you, but I'm feeling so annoyed !
> I don't understood from pic archive examples and data sheet if
> master clock is generated automaticaly by the MSSP module or not.
> My first thought was yes. I understood that 8 bites of data can be
> transmitted synchronously with clock pulses.
> I'm trying to initiate a communication using master1 mode, the
> sspstat = 0b_0000_0000 and sspcon = 0b_0010_0010 are set appropiate
> for fosc/64. The pins used are rc3 ( spi-clk ) and rc4 ( spi-data in )
> and an extra pin for chip select, all direction are set correct in
> TRIS register.
>
> According to data sheet:
> " In master mode the data is transmitted/received as soon as the
> SSPBUF register is written to " and:
> "The master can initiate the data transfer at any time because it
> controls the SCK "
>
> My device ( MAX121 ) is connected to receive clocks from PIC and to
> deliver data's as soon as the chip select ( or convst ) is tied to gnd.
> But how can be determined MSSP to send clocks ? The only way I saw is

> Hello,
>
>     the usual way of having a sendSPI() function is something like:
>
> #asm
>        MOVF   SSPBUF,W        // Discard received data in buffer and
>                                //    clear SSPSTAT_BF
>        MOVFF  spiData,SSPBUF  // Put data to send on buffer
>                                //    and start sending
>        loopssp:
>        BTFSS  SSPSTAT_BF      // If there's not received byte
>                                //     in buffer (transmit completed)
>        BRA    loopssp         // loop
> #endasm
>
>     This is working perfectly as it should, but my data sending routine
> does this:
>
>     calculateByteToSend()
>     sendSPI()
>     calculateByteToSend()
>     sendSPI()
>     calculateByteToSend()
>     sendSPI()
>     calculateByteToSend()
>     sendSPI()
>     etc...
>
>     Of course, this isn't very efficient because the PIC waits to send
> the data when it would be calculating the next byte, so I tried:
>
>
> #asm
>        loopssp:
>        BTFSS  SSPSTAT_BF      // If there's not received byte
>                                //     in buffer (transmit completed)
>        BRA    loopssp         // loop
>
>        MOVF   SSPBUF,W        // Discard received data in buffer and
>                                //    clear SSPSTAT_BF
>
>        MOVFF  spiData,SSPBUF  // Put data to send on buffer
>                                //    and start sending
> #endasm
>
>     But, the PIC hands after some transmits. Can anyone tell me what
> I'm doing wrong?
>
>     Best regards,
>
>     Brusque
>
> --
> ---------------------------------------------------------------------
> Edson Brusque                    Stagetronics Eletro Eletrônicos Ltda
> Research and Development                   Blumenau  -  SC  -  Brazil
> http://www.ryan.com.br/netiqueta.htm             http://www.citronics.com.br
> ---------------------------------------------------------------------

> >From what little I understand so far, I2C and SPI are standards for
> programming microcontrollers IN their target circuits.  For obvious
> reasons, avoiding the need to swap the microcontroller back and forth
> between the target circuit and a programmer like the PICSTART PLUS is
> essential for surface mount microcontrollers.
>
> Is there a list of all of these in-circuit programming/emulating
> methods used for surface mount microcontrollers?  How do you decide
> which standard to use?  What type of connector/cable do you normally
> use to connect the computer to the embedded circuit?  How do you
> recommend getting started?  (So far, all of my experience has been
> with through hole microcontrollers programmed with the PICSTART PLUS.)
>
> --
> Jason Hsu
> http://www.jasonhsu.com/swrwatt.html
> http://www.jasonhsu.com/swrwatt-c.txt
> http://www.jasonhsu.com/swrwatt-asm.txt