You must pull up the SSEL of the SCI that you are using. Seem be that
the SCI in master mode need that the SSELx must be connected and
pulled up externally for correct work.
--- In lpc2000@yahoogroups.com, "Mark Crow" <mcrow@p...> wrote:
> Is SSEL1 pulled up?
> -----Original Message-----
> From: Jeetendra Singh [mailto:jeet77_7@y...]
> Sent: Friday, April 08, 2005 9:44 AM
> To: lpc2000@yahoogroups.com
> Subject: [lpc2000] spi in lpc2106
>
>
>
> Hi friends
>
> i am working in Lpc2106 and facing problem in spi mdule.
> Actualy i am using spi module in master mode. i checked my code
in
> jtag debugger(wiggler in CrossStudio)and found that when writing
data
> to the SPDR register then SPif bit in SPSR also sets showing that
> data is transmitted.
>
> But the problem is that nither data nor clocks in the MOSI & SCK
pins.
>
>
> If some body can help me i will be very thank ful to him.
>
> jeetendra
>
> My source code attached
> int main (void){
>
>
> IOSET=0x80;
> IODIR=0x00;
>
> PINSEL0 = 0x00005500;
>
> //Config over
> init_spi();
>
> IOSET = MMC_CS; // Chip select High
> MmCardSendByte(0xAA);
> IOCLR = MMC_CS; // Chip select Low
>
> while (1);
> }
>
> void init_spi(){
> unsigned char ch;
>
>
> IODIR |= MMC_CS; // io direction of mc chip select
> IOSET = MMC_CS; // Chip select High
>
> SPCCR = 0xfe; // clock counter
> SPCR = 0x20; // spi master mode,
>
> // ch = SPDR;// data read
>
> }
>
> BYTE MmCardSendByte(BYTE bt)
> {
> BYTE input;
> SPDR = bt;
> while (!(SPSR & 0x80));
> input = SPDR;
>
> return input;
> }
>
>
>
>
>
>
> --------------------------------------------------------------------
--------
> --
> Yahoo! Groups Links
>
> a.. To visit your group on the web, go to:
> http://groups.yahoo.com/group/lpc2000/
>
> b.. To unsubscribe from this group, send an email to:
> lpc2000-unsubscribe@yahoogroups.com
>
> c.. Your use of Yahoo! Groups is subject to the Yahoo! Terms of
Service.
>
>
>
> [Non-text portions of this message have been removed]Message
Re: spi in lpc2106
2005-04-08 by aumat123
Attachments
- No local attachments were found for this message.