|
I disagree. The whole concept of NI2C bases on the fact that the messages of a single transmission request are handled as an atomic transmisson and are not interruptible. Therefore it *must* use REPEATED START. Some slaves require combined transmissions, where the master sends some bytes first (e.g. a memory address, a register number or a command byte) and then reads a couple of data bytes. These combined transmissions actually *must* use REPEATED START, but the sequence can only be done in NI2C with two messages in one transmission request.
If single messages with separate STOP and START conditions are needed, the user has to schedule different transmission requests with separate calls to DeviceIoControl(). |