In an earlier post I indicated that I was using a TI USB Interface Adapter to check out an SMBus module that I am writing. I mentioned that the "Process Call" section of the SMBus/I2C/SAA GUI tool from the Fusion power design suite was being used to drive the adapter. I mentioned that I was not seeing the Read command from the host after a 'Restart' was issued during a "Process Call". That the bus was reporting the reissuance of the slave address followed by a the RnW bit set low.
What makes this more interesting is that "BLOCK Process Call" seems to work correctly. It does turn the bus around as one would expect. The RnW bit is high after a 'Restart' and the transaction seems to work properly.
I also noticed another problem with the "Process Call" section: "Process Call" however, doesn't seem to work right in another respoect. If I enter ABCD hex for the data payload, monitoring the bus I notice that it ships out and reports ABAB hex. This is true for any entry I try. It just ships out the first byte twice instead of one followed by the other.
If worse comes to worse I guess I can use a Block Process Call that ships and receives only two bytes each way, but I am curious if anyone else has seen this problem.