i2c PBP questions

[TimV]

Thanks Steve:

I will change ADDR to be "Word". Is it acceptable to just say $07 as the address I want to write to?

The data sheet for the EEPROM states that it is expecting the Address High after it acknowledges the Start condition.

It is written as "high-order byte of the word address and will be written into the Address Pointer" Is the address pointer the location that I intend to write to? It then says that the next byte (2nd half of address word) is the least significant address byte. It does not say what this represents.

The EEPROM has memory addressing from $0000 - $FFFF. Should my $07 as a target address go in as $0700 and then 0000 as the second half of the word?

Confused,

Tim

[mister_e]

When you write ADDR=$07 or ADDR=$7, it store $0007 to the word variable in one shot...If you prefer in the MSB and LSB. have Look to your EEPROM datasheet...
http://ww1.microchip.com/downloads/e...doc/21754E.pdf

Look Figure 6-1. What happen if your address variable is a byte? Yes it miss the LowByte of the address. Using a word sized variable, nothing is missing.

Nothing else to worry about, I2CREAD/WRITE will do the job for you.

P.S. : Welcome on the forum Yet another Canadian Woohoo !!!

[TimV]

Hi Steve:

Thanks for the response. Happy to strengthen the Canadian contingent

I am sitting here watching the program run on the ICD. I wish they went faster.

I will confirm that the address stuff is exactly as you said. I watched 8 0s get fed before it put in my address and I am now watching shift my address across.

From what I can see, everything is working properly.

When I let it run, I am expecting to see the number contained in the [] brackets on the write statement returned in my byte i2c_Data which is in the [] brackets in my read statement.

If this correct?

The read statement does not hit the "Fail" after the [] so that would imply that the program is "running".

Tim

[mister_e]

Running or at least it says that there's something on the I2C lines.

If you really want to know if it's working, you could still write to the EEPROM, then read back the data, if both are the same... it confirm it's working.. just fine.

[TimV]

Hi Steve:

Well that is my big question in my previous response. If this was doing what it is supposed to be doing, would I not see the result in my i2c_Data variable?

ADDR var word
ADDR = $07
PAUSE 10
I2CWRITE PORTC.4,PORTC.3,$A0,ADDR,[1]
PAUSE 10

I2CREAD PORTC.4,PORTC.3,$A0,ADDR,[i2c_Data],Fail
PAUSE 10

GOTO MAIN

Fail:
PORTC.5 = 1
GOTO MAIN

I would expect i2c_Data to contain "1"

It does not.

Am I giving everything enough time?

Thanks

Tim

[mister_e]

Try this one, it's working here

define LOADER_USED 1
disable debug
Data_READ   var byte
Data_Write  var byte
Bad         var bit
ADDR        var word
SDA         var PORTC.4
SCL         var PORTC.3
Control     con $A0

Bad = 0

Start:
    For addr=0 to $FFFF
        
        data_write=addr.lowbyte
        bad = 0
        I2CWRITE sda,scl,control,ADDR,[data_write]
        PAUSE 10 

        I2CREAD sda,scl,control,ADDR,[Data_read]
        enable debug
            data_read=data_read ' refresh ICD display
        disable debug
        if data_read != data_write then bad=bad +1

        next
    GOTO Start

[TimV]

Hi Steve:

Thanks for posting the code. How long should this take to complete? I can see that it is cycling through addresses 0 to $FFFF. I put in a line between the next and GOTO Start to light up one of the status LEDs I have on the board.

It is not lighting up. In the watch window, Data_READ is blank. When I pause the program, I am in the library PBPPIC14.LIB stuck in the PAUSE routine waiting for the carry bit to be cleared. This bit does not get cleared.

I just thought of something. I have no includes in my program as I normally did with assembler. I am just starting out with PBP.

Am I perhaps not adding some includes that I need?

I didn't see a list in the manual anywhere of any special requirements that have to be in the code. I don't have a device include either.

Please advise


Thanks

Tim