Lpc2000

The manual states that for the SSEL0 signal, that when SPI is setup
as a Master, this signal can be used as GPIO.

This statement is not in the description of the SSEL1 signal.  I'm 
configurating the SSP as an SPI port and would like to use SSEL1 as a 
GPIO pin.

Any experience?

   Barry

Barry,

There are already a few postings on this already. SSEL1 needs to be 
pulled up or tied high, and the pin configuration needs to be set as 
SSEL1 function and not a GPIO.

(Otherwise it just won't clock out any data!)

I believe this is going to be fixed on new LPC2000 variants...

Jane

javida13 wrote:

> The manual states that for the SSEL0 signal, that when SPI is setup
> as a Master, this signal can be used as GPIO.
>
> This statement is not in the description of the SSEL1 signal.  I'm
> configurating the SSP as an SPI port and would like to use SSEL1 as a
> GPIO pin.
>
> Any experience?
>
>    Barry
>
>
>
>
>
> ------------------------------------------------------------------------
> *Yahoo! Groups Links*
>
>     * To visit your group on the web, go to:
>       http://groups.yahoo.com/group/lpc2000/
>        
>     * To unsubscribe from this group, send an email to:
>       lpc2000-unsubscribe@yahoogroups.com
>       <mailto:lpc2000-unsubscribe@yahoogroups.com?subject=Unsubscribe>
>        
>     * Your use of Yahoo! Groups is subject to the Yahoo! Terms of
>       Service <http://docs.yahoo.com/info/terms/>.
>
>
>------------------------------------------------------------------------
>
>No virus found in this incoming message.
>Checked by AVG Anti-Virus.
>Version: 7.0.308 / Virus Database: 266.11.7 - Release Date: 09/05/2005
>  
>

I justed tested using the Keil Evaluation board (LPC2138) both the SPI
and the SSP configured as an SPI.  On both ports the SSEL line is set
as GPIO.  I even have the output of the SSEL pins toggling.  Using a
dual channel scope, the MOSI data is correct and within the clock
burst.  So far, I see both Perpherals behaving as specified in the
manual.  At this point, I'm not using interrupts or the FIFO logic in
the SSP.

  Barry


> Barry,
> 
> There are already a few postings on this already. SSEL1 needs to be 
> pulled up or tied high, and the pin configuration needs to be set
as 
> SSEL1 function and not a GPIO.
> 
> (Otherwise it just won't clock out any data!)
> 
> I believe this is going to be fixed on new LPC2000 variants...
> 
> Jane
> 
> javida13 wrote:
> 
> > The manual states that for the SSEL0 signal, that when SPI is
setup
> > as a Master, this signal can be used as GPIO.
> >
> > This statement is not in the description of the SSEL1 signal.  I'm
> > configurating the SSP as an SPI port and would like to use SSEL1
as a
> > GPIO pin.
> >
> > Any experience?
> >
> >    Barry
> >

> >
> >
> >
> >
> >
--------------------------------------------------
----------------------
> > *Yahoo! Groups Links*
> >
> >     * To visit your group on the web, go to:
> >       http://groups.yahoo.com/group/lpc2000/
> >        
> >     * To unsubscribe from this group, send an email to:
> >       lpc2000-unsubscribe@yahoogroups.com
> >       <mailto:lpc2000-unsubscribe@yahoogroups.
com?subject=Unsubscribe>
> >        
> >     * Your use of Yahoo! Groups is subject to the Yahoo! Terms of
> >       Service <http://docs.yahoo.com/info/terms/>.
> >
> >
>
>-------------------------------------------------
-----------------------
> >
> >No virus found in this incoming message.
> >Checked by AVG Anti-Virus.
> >Version: 7.0.308 / Virus Database: 266.11.7 - Release Date:
09/05/2005
> >  
> >