Another attempt for I2C eeprom, this time - 25C256.

[CuriousOne]

Hello.
I decided to give it another try, now with this module.

https://www.elecrow.com/i2c-eeprom-m...256-p-736.html

Pull up resistors installed, and following code configured.
when properly working, it should produce chirp up, chirp down sound. But it does not
of course, chirp up - write, works fine, because here it chirps directly, but in read routine
I'm getting zeros.

Only what I've found out, that if I set read address to 160 (A0) it returns 255, for any other address, it returns 0.
So somehow, chip responds, right? but not completely.
What I'm missing?

x var byte
y var byte
z var byte
sda var portb.1
scl var portb.0


ehmo:
for X=0 to 12 
I2CWrite sda, scl, 160, x, [x]
hpwm 1,127,1000+x*10
pause 1
next
hpwm 1,0,1000 'mute
pause 500


for x=12 to 0 step -1
i2cread sda, scl, 160,x,[y]
hpwm 1,127,1000+Y*10
pause 1
next
hpwm 1,0,1000
pause 500
goto ehmo

[aerostar]

For read try 161 address

[CuriousOne]

No difference - already tried all combos like 159+160, 160+161 and so on....

[HenrikOlsson]

The 25C265 as mentioned in the title is a SPI EEPROM. That won't ever work with the I2C command.
If, on the other hand, it's the 24C256 then the state of the A0-A2 pins will have an effect on the address. Anyway, looking at the 24C256 datasheet:

In Byte Write mode the Master sends a START, followed
by Slave address, two byte address and data to be written
(Figure 6).

And then your code:

I2CWrite sda, scl, 160, x, [x]

You're using the x-variable as the address (and data) but have it defined as a byte.

With that said, I have not ever used I2C so I'm certainly no expert.

[CuriousOne]

Yes I made an error in tittle, chip is certainly 24C256.

[richard]

you need to do it properly

[mpgmike]

C1, if you have the spare cash, I would recommend a cheap logic analyzer. Saelig sells one for (I think I paid) around $80 US. I haven't used mine in several years, as I now have a Pico Scope that does much more, and better. I am in the northeast US. If you're willing to cover shipping, you can have my old Saelig. It will help you to verify communication protocols and baud rates for situations like this. If interested, PM me & we can take it from there. You might be able to find one on eBay, Amazon, or Craigslist (or whatever local online sellers site you have) for next to nothing, and with cheaper or even no shipping.

[CuriousOne]

So what's wrong with 160? it is chip address, A0, and isn't that fixed?

Regarding the logic analyzer. I have that saelae thing.
I can't get it work as I understand it should work - run continuously, monitor bytes, like scope does. it only has "run", it runs, fills up buffer in couple of seconds and stops - that's all. For that purposes, I bought a scope with built-in logic analyzer, which can run infinitely - Hantek DSO2D10 - but was able it to work only very low speeds, for protocol decoding.

[richard]

it a constant , pbp constants are 16 bits , i2c address are 8 bit
use your logic analyzer

[CuriousOne]

So what should I write instead of 160?

I've searched this forum, and people do use plain numbers in I2C eeprom write/read?