I2CWRITE problem

[Art]

Hi Gusse,
Your code does not loop, I am sitting here wondering if there is some latency in your hardware, causing your code to run ahead of the eeprom, so the code is finished before the eeprom has finished waking up . . . Maybe in Art's too . . BTW ART, I liked your talking clock, esp when it encounters an error

Thanks for the comments , but I don't know what you mean by the code running ahead of the EEPROM.
The code is posted above. Writing a bunch of zeros is not exactly what I want to
achieve, but the code exhibits the problem I'm describing.

I suppose at some point I'll run the same code on a breadboard and try adjusting things like clock speed, pull up resistor values, and see if that helps.
PBP should compensate for clock speed though.

[MR2010]

HI art IM JUST TESTING IT ON AN OLD PIC F84A WITH 24C08 ITS WORKING WELL
THIS MY CODE MODIFIED GUSSE CODE

PORTB = 0
TRISB = 0
X       VAR BYTE
Y       VAR BYTE
SCL     VAR PortB.0 
SDA     VAR PortB.1   
LED     VAR PortB.3

I2CDeviceEEprom     VAR BYTE   
I2CAddressEEprom    VAR WORD 
I2CDeviceEEprom=$A0

X=0    'OK if EEPROM content is 00h and X = 0, if X > 0 then fails
MAIN:
FOR I2CAddressEEprom = 0 TO 1024
    I2CWRITE SDA, SCL, I2CDeviceEEprom, I2CAddressEEprom,[ X ], Error			
    PAUSE 10
    I2CREAD SDA, SCL, I2CDeviceEEprom, I2CAddressEEprom,[ Y ], Error
    IF Y <> X THEN GOTO Error
    IF I2CAddressEEprom = 1024 AND X = Y THEN BLINK
NEXT I2CAddressEEprom
GOTO MAIN
Blink:
HIGH LED
PAUSE 1000
LOW LED
PAUSE 1000
GOTO Blink

Error:
HIGH LED
PAUSE 200
LOW LED
PAUSE 200
GOTO error

END

YOU HAVE TO MAKE SURE ABOUT EEPROM PULLUPS AND TRIS AND PORT SET THEM TO 0 OUTPUT
JUST LOOK TO THIS CODE TO GET SOME IDEAS OR POST UR WHOLE CODE SO EVERYONES CAN HELP .
REGARDS

[Archangel]

Thanks for the comments , but I don't know what you mean by the code running ahead of the EEPROM.
The code is posted above. Writing a bunch of zeros is not exactly what I want to
achieve, but the code exhibits the problem I'm describing.

I suppose at some point I'll run the same code on a breadboard and try adjusting things like clock speed, pull up resistor values, and see if that helps.
PBP should compensate for clock speed though.

Hi Art,
I was thinking, in Gusse's case, the pic might blather out a bunch of commands before his eprom was awake, since he is using an OFF PIC eprom, and maybe the eprom just missed it due to the difference in boot rates. I was thinking a short pause during initialization might allow eprom to catch up . . . as I said, I was just thinking.