Hello everyone,
I am encountering a strange issue with the USB-8452 I2C/SPI controller. I have used this device in the past without issue, so I have a little bit of experience with it. I am now trying to use the I2C bus to read/write a EEPROM chip. Currently I have no issues reading/writing data. However, the vendor that I am working with is unable to read 0x00 bytes. Currently our theory is that the controller is interpreting this as the ASCII null char and terminating the communication. What makes this difficult to debug is my setup "just works". I use the "General I2C Read" C example that is included in the device driver download. The code example is able to read my EEPROM chip with barely any modifications. However, our vendor's setup is getting stuck on the 0x00 bytes. We have verified that our setups have the same EEPROM chip, 8452 board, code sample, etc. so there are no obvious differences. The nature of the data we need to read/write is such that we cannot guarantee there will never be 0x00 bytes in the data.
Based on my setup, the dll should drive the 8452 to read the specified number of bytes, regardless of what the bytes are. However, our vendor is experiencing premature terminations of the data. Is this behavior something that can be configured for the device? If so, how is this configuration done?
Any suggestions are appreciated!
-BR
