Lpc2000

The problem (annoyance) with the LPC is that if you want to operate the
SPI in Master mode only, the SS pin must still be configured for SPI use
and tied high.  It cannot be configured as a GPIO pin and used for a
different purpose.

Regards
-Bill Knight
http://www.theARMPatch.com



On Tue, 30 Nov 2004 17:43:07 -0000, R M wrote:



You must be new to the low-cost micro controller scene because with
most low-end micros (in my experience) the SS# pin is not normally
driven by the master - it, or any other GPIO for that matter is driven
by software to select a slave. This is not a Philips LPC thing - the
AVR and many other micros act the same way.

If you wanted a hardware controlled SS# peripheral then look at a more
complex/expensive device like the Coldfire 5282 which has a multi
channel SPI peripheral that bangs the SS# pins for you.

However in my opinion, it is better to have software control over the
SS# pin since it would otherwise preclude multiple slaves when only
one SS# pin is provided (as is the case with low-end micros).

As for the ADC on the LPC, I don't have any experience with this
peripheral. However it is not uncommon for the inputs to not be 5V
tolerant (if that what your rant was about) in mixed signal devices,
or at least in peripherals/pins that interface with mixed signal
silicon.

What exactly is wrong with the boot-loader? I like the standard and
easy to use API it provides to the Flash. I also like the ability to
have a fresh part on a PCB programmable without the need for JTAG (as
do my verification and production peers).