external eeprom

[Darrel Taylor]

Like Alain was saying ...

You CAN use I2CWRITE/READ statements with a 12F675.
<br>

[ruijc]

Thanks Alain and Darrel Taylor,



my previous question is due to the fact that in the 12F675 datasheet it doesnt says that it's compatible like other pics do.

Maybe pbp gets arround that !?

This means i can use the same pbp expressions and the hardware connections the same also, right ?

Thanks

[Darrel Taylor]

The I2CWRITE/READ statements don't use any Hardware I2C modules.
So you can use any pins you want.

The only limitation is on devices with 12-bit cores.
Just because there is a 12 in the part number (12F675), Does Not mean it's a 12-bit core.
<br>

[tenaja]

Thanks Alain and Darrel Taylor,



my previous question is due to the fact that in the 12F675 datasheet it doesnt says that it's compatible like other pics do.

Maybe pbp gets arround that !?

This means i can use the same pbp expressions and the hardware connections the same also, right ?

Thanks

You are confusing hardware features with compiler capability.

Some PIC's have an MSSP or SSP built in to them. The MSSP allows them to be a master i2c through hardware. Doing it through hardware allows the PIC to "multitask" by giving you processor time while the hardware does the work. The SSP only allows slave i2c, which I learned the hard way, and it's basically useless for communicating with eeprom.

The compiler has a command that performs i2c tasks in software. By doing it in software, that gives you the flexibility to do functions with PIC's that don't have the hardware to do it. However, the trade-off is that during the sending time, it consumes 100% of the processing time. (This is what I ended up doing with my PIC that had the SSP.)

[ruijc]

Hi tenaja,

That's exactly what i was looking for

now i fully undestand

Thanks all and happy new year !!!!

.