Yahoo Groups archive

Lpc2000

Index last updated: 2026-04-28 23:31 UTC

Message

Re: LPC2138: Strange SSP Behavior

2005-01-11 by tah2k

It is pulled high, but the issue I am having is the memory locations 
themselves.

--- In lpc2000@yahoogroups.com, "Charles R. Grenz" 
<charles.grenz@s...> wrote:
> Hi,
> 
> 	Do you have the slave select pin pull high?
> 
> 
> Charles
> 
> 
> 
> -----Original Message-----
> From: tah2k [mailto:tah2k@y...] 
> Sent: Tuesday, January 11, 2005 9:59 AM
> To: lpc2000@yahoogroups.com
> Subject: [lpc2000] Re: LPC2138: Strange SSP Behavior
> 
> 
> 
> 
> Yes, but it doesn't seem to matter.
> 
> --- In lpc2000@yahoogroups.com, "johnnorgaard2003" 
<john_2005@c...> 
> wrote:
> > 
> > Hi
> > 
> > Have you selected the SSP function in PINSEL0 or PINSEL1 ?
> > 
> > 
> > best regards
> > 
> > John
> > 
> > --- In lpc2000@yahoogroups.com, "tah2k" <tah2k@y...> wrote:
> > > 
> > > I'm writing the driver for the LPC2138 SSP block and I am
> > > encountering some strange behavior:
> > > 
> > > First of all, the user manual states SSPCR1, SSPCPSR, and
> SSPIMSC 
> > > are all reset to 0x0 upon powerup.
> > > 
> > > I am finding the following values in these registers after 
reset: 
> > > SSPCR1 (0xE005C004): 0xF8 SSPCPSR (0xE005C010): 0x04
> > > SSPIMSC (0xE005C014): 0x04
> > > 
> > > The processor ignores any writes of any data value to these
> > > locations.
> > > 
> > > Any ideas?
> > > 
> > > -Tim
> 
> 
> 
> 
> 
>  
> Yahoo! Groups Links

Attachments

Move to quarantaine

This moves the raw source file on disk only. The archive index is not changed automatically, so you still need to run a manual refresh afterward.