Proprietary i2c protocol
I'm working on a project, updating firmware on given HWs: 2 microcontrollers talking i2c (master/slave, of coarse). I know i2c is more complex/slow than SPI, UART, etc., but it's a constrain. The slave will be implementing a file-system, more-or-less, so there will be 50-500 byte read/write operations (both!) - not the standard i2c usage. I can choose how to implement the application-level protocol, over i2c. My question: what are the limitations of i2c, for this usage? Meaning, i2c-master clocks the lines and generates STOP, so must know the length of all responses - is that correct? Can I parse bytes, as they arrive, 1 at a time, run them through a dispatcher? Will that not slow-down communication, which is slow to start with? I know this is not a 'programming' but more of a design question, but I have a feeling that someone out there has done a bit of design in his/her career... Thanks
IC2 SLAVE NOT RESPONDING XC8
Re: I2C, what does “clocked out” mean?
interpreting i2c register map for ISL12022
I2C repeated start
what is better using while loop or if statement when checking status codes of atmega 32?
Atmega64A pins SCL/SDA no respond
atmega64 I2c ds3231 not responding
Sending double through I2C from Arduino Pro Mini to ESP8266
Texas Instruments DS92LX1621/2
How do you adjust an I2C driver to handle smbus specs?
I2C Communication between 2 Beaglebone black
MUX channels not needed, how to wire?
I2C clock stretching details
comunication from stm32 Nucleo L152RE and shield x-nucleo IKS01A1 with protocol I2C and DMA
NACK and ACK responses on I2c bus
SH72867 with I2C