Hi,

I did exact this job 3 month ago. As I see you are using TRIS as a command.
This is not supported from the C76. You should switch to bank 1 and do a
bsf.

   bsf  STATUS,RP0
   bsf  TRISB,3
   bcf  STATUS,RP0


The command
   movlw .8
works in any case. But what are you going to achieve with it?

In master mode you have to program the whole protocol. The use of the I2C
peripheral
is not suggested. But there are new PIC's who have an I2C Master (MI2C).

PIC16F876

PIC16F873
PIC16C773

Greetings

Martin

;**********************************************
;**   name:      Martin Schaefer             **
;**   company:   elektronik 21 GmbH, Germany **
;**   e-mail:    schaefer@elektronik21.de    **
;**********************************************


-----Original Message-----
From: s. rao [mailto:shrirao@blue.weeg.uiowa.edu]
Sent: Monday, April 10, 2000 8:16 AM
To: PICLIST@MITVMA.MIT.EDU
Subject: Q: 16C76 as I2C bus master


Greetz.

I'm trying to come up with code for implementing an I2C bus master
using a 16C76 chip as master with a 24LC32 EEPROM as the only slave.
Code from Roger Stevens's book and website that claims to be able to
achieve this doesn't seem to work; the problems are:

--> The assembler does not like TRIS portb, etc., and it has been
suggested to me that `TRIS' is not an opcode at all.

--> The assembler also does not like MOVLW d'8' et cetera to move a
required number of bits; what is the correct syntax?

--> If Port B is entirely off limits for some reason (because other
applications than the master are using it, such as a motor controller
for instance), then is it possible to use Port C instead?

Sorry if these are elementary questions, but I couldn't find anything
in the FAQ, archives, or literature that directly addressed them.

Rgds,

SR


Content-Type: application/octet-stream;
        name="Martin SchŠfer.vcf"
Content-Disposition: attachment;
        filename="Martin SchŠfer.vcf"

Attachment converted: definition:Martin Sch=fer.vcf (????/----) (0000E325)