Propeller Activity Board I2c bus access is missing?

Zap-o

Did I miss something on the schematic? Why are the i2c pins on the eeprom non accessible or are they?

There should be a header so I can use more on this bus, right? I suppose parallax had good intentions and if so my curiosity insist I ask politely ask why otherwise blessed may your day be.

Thanks

Duane Degn

I think it's to keep it simple. Some devices can keep a Prop from booting correctly if used on the I2C bus.

Of course any two I/O pins can be used as an alternate bus.

I like how the QuickStart board makes all I/O pins available.

msrobots

You basically can use any pins for i2c, but I also stumbled upon this on one of my Parallax Boards.

I have a lot of different boards, so not sure if it was the Activity board. But I could not find I2C pins either on the headers.

Mike

WBA Consulting

Probably a non-value add comment, but I have only used the EEPROM I2C bus for other items during my learning through the Propeller Education Kit. I always dedicate two other pins for my I2C devices because you can.

KMyers

Yes no direct access to the pins. I always extra pins on my activity boards.

bte2

WBA Consulting wrote: »

I always dedicate two other pins for my I2C devices because you can.

I do also, but only so a hardware failure won't prevent the Propeller from booting. You cannot code to catch bad hardware if your MCU won't boot.