This might shed some light as to what the i2c0 device thinks it can see (and John can look at the bus lines as well). You can also use this to query devices on the bus. You can dump this information out in u-boot ("factoryconfig") as well as use the i2c utilities in u-Boot to forcibly probe i2c0 ("i2c probe") to find local addresses attached to the bus (48-57 show up due to the onboard prom and the on-board power controller). When u-Boot loads up (on power up or on reset), the I2C0 bus is read to get the factory configuration data (serial number, MAC address, etc.) from a small onboard prom. Which Revision of the Industrial I/O are you using? Rev A Industrial I/O boards have the I2C port of the video hooked through the FPGA, not I2C0 on the OMAP, so you won't get a valid response if you are using a Rev A industrial I/O board.
0 Comments
Leave a Reply. |