Lpc2000

Bruce,

Two days ago I was dealing with the same problem. Then I had to tie the pin 
to VCC and define it as SSEL and had the SPI working as master.

If you define the port as output the SPI continues to get "slave abort". 
Also the LPC2214 user manual states the following in bold in page 163 
"...configured to operate as SPI master MUST select SSEL functionality on an 
appropriate pin...". Which means you have to make the pin a SSEL pin as it 
says "select SSEL functionality".

Anyways the pin is wasted like I'm unable to use PWM outputs as the same 
pins share serial port I/O while some of the pins only have one function.

Kerem


----- Original Message ----- 
From: "Bill Knight" <BillK@...>
To: <lpc2000@yahoogroups.com>
Sent: Thursday, January 13, 2005 1:39 PM
Subject: Re: [lpc2000] Re: SPI usage


>
> On Thu, 13 Jan 2005 13:22:31 +1100, Bruce Paterson wrote:
>
>
> Bruce Paterson wrote:
>
>>
>> Hi,
>>
>> I've written an interrupt based SPI driver to fit into the newlib
>> structure (ioctl, read, write).
>
> A hardware question (it seems to be my day for questions!).
> If you have SPI port enabled, used as a Master, do you have to tie the
> SSEL0 pin high, or can you program that pin as a GPIO (and somehow the
> SPI core gets a permanent high supplied to it internally) ?
>
> Seems a waste of an I/O pin to have to tie it high where most SPI
> applications would be SPI master
> ------------------------------------------------------------------
> Bruce
>  I believe the answer is yes, you must tie the SSEL0 pin high even
> when operating in Master mode and yes, it seems a waste.
>
> -Bill Knight
> http://www.theARMPatch.com
>
>
>
>
>
> Yahoo! Groups Links
>
>
>
>
>
>
>
>