I looked again, and noticed this:

  "SMP must be cleared when SPI is used in slave mode"

I wonder, if you were in slave mode, maybe it would keep
you from being able to set it?

I'm surprised someone on this list doesn't know this one.  Must
be spending too much time over on [OT]

I've actually got an 877 board somewhere.  I'd try it myself if
knew where the board was, had the time, was currently up on
coding in PIC.    Let me know how bad it gets...

Have you ruled out the "bad chip" thing?

Barry


At 07:35 AM 9/14/01 +0300, you wrote:
>Barry, is exactly the thing I've done. But SMP bit appears it can't be
>set.
>I have Mplab 4.99.07.
>Vasile
>
>On Thu, 13 Sep 2001, Barry Gershenfeld wrote:
>
>> The data sheet I looked at says you can only write to the
>> top two bits of SSPSTAT.
>>
>> If it were me I might suspect MPLAB was interfering, and I'd
>> arrange to write a routine to let the chip itself test
>> this.   (Set the bit, test the bit, light an LED if it's
>> set, etc.)
>>
>> Barry
>>
>>
>> At 01:47 PM 9/12/01 +0300, you wrote:
>> >Accordingly to Mplab, I can't write the SSPSTAT register in I2C
>> >initialisation sequence.
>> >Bank switching is ok, all SSPCON2 and SSPADD are initialised OK.
>> >What should I do ?
>> >
>> >Vasile
>>
>> --

--
http://www.piclist.com hint: PICList Posts must start with ONE topic:
[PIC]:,[SX]:,[AVR]: ->uP ONLY! [EE]:,[OT]: ->Other [BUY]:,[AD]: ->Ads