I2C is a two-wire protocol where a master can communicate with several slaves - have a look at Microchip's application node AN982
**broken link removed**
it would work the same with two PICs except that instead of an EEPROM a PIC would be programmed as a slave.That AP is for interfacing an EEPROM IC with a PIC 12F, would it work just the same with two PICs? Isn't I²C a little too complex?
why can't you select pic 16f its has inbuilt eeprom
Humm... Interesting. After some reading I'm pending towards RS485, it seems simpler to implement and the maximum distance of the I²C is below that of my application.RS485 may be an alternative
have a look at Microchip's application note AN774Is there a library or tutorial or something that teaches how to implement the RS485, I'm pretty new to MCU's and every little thing takes me quite some effort.
Also, can I implement RS485 without any other IC's but the MCU's? Space and cost are kind of an issue here...
have a look at Microchip's application note AN774
do you started to communicate?
All the MCU's involved have I2C. What would be ideal to me is a tree-like architecture, where a node is a master to a few others below him, but a slave to a higher node. Is that too hard to implement?I highly suggest moving to a chip with I2C. Microchip has libraries for communicating with it, and it isn't very complicated if you are going to use a single master architecture.
We use cookies and similar technologies for the following purposes:
Do you accept cookies and these technologies?
We use cookies and similar technologies for the following purposes:
Do you accept cookies and these technologies?