It appears TI has a misprint on page 14 of the spec sheet regarding the address selection input lines... The I2C2 and I2C0 labels in the address selection table need to be reversed (ie pulling up I2C2 and leaving I2C1 and I2C0 tied to ground gives the device an address of 0x04 not 0x01 as documented)....
According to page 15 of the spec sheet, the device should give me a NACK after the 7th byte has been written to the E3, E4, or E5 'registers' --- it does not !
When I do a read operation on 'register' E1 and vary the voltage on the AVOUT and align the 10 bit values to integers... I see that the VIN value changes while the VOUT value does not ! (had scoped out voltage levels on pins 15 (AVIN) and 17 (AVOUT) just to make sure - and tied AVIN to ground... same problem...
The reserved bits in 'registers', E0, E1, E3, and E5 --- consistently have their first bytes set to 0x56, 0x7F, 0xE0 and, 0x18 (not the default 0x00 value outlined in the spec sheet).... only register E4 register has the reserved bits set to 0 (as documented)...
Writing values to "register' E3 are read back correctly with the exception of byte 7 which always comes back as 0x00 --- byte 7 is not NACKED by the SM72445 as I explained above... and the write operation on bits 7 to 0 of the E3 Register do not alter the SM72445's operation (for example outputting the PLL clock on pin 5 by setting bit 1 does not output the clock on pin 5 !
Now... the board is a custom board, there were other devices on the I2C bus (all worked fine)... that I had removed just to make sure there were no conflicting issues... the only device communicating with the SM72445 is the micro (running its I2C subsystem at about 50 KHz which is well within the 100 Khz I2C specification by Philips... both the clock and data lines are pulled up via 2.2 K ohm resistors... the digital and analog power contains less than 0.005 volts of noise --- ringing and ground bounce are less than 0.025 volts... of course the board has a solid ground plane...
Any detailed timing specs or additional information regarding the I2C operations of this chip would be much appreciated...