1) Why is there a timeout parameter in master mode of I2C module?
bool EUSCI_B_I2C_masterSendMultiByteStartWithTimeout (uint16_t baseAddress, uint8_t txData, uint32_t timeout);
Isn't sending the data under the control of MSP because it is master?
And also what is the unit of this parameter?
2) Why does non of the master routines check whether the data transmitted is acknowledged by the slave? Suppose the slave address is wrong in production and what will be the behavior of DiriverLib I2C routines?
3) Can TI provide me a reliable I2C routines that uses latest eUSCI capabilities without any interrupts that increase design complexity (pooling is enough in this case) in order to read data from an EEPROM.