Other Parts Discussed in Thread: CDCI6214
We're currently developing w/ the CDCI6214 for our solution. As we'll need to generate a requested frequency "on the fly", we can't use TICS to reprogram, so we need the I2C communications up and running. We are currently attempting to connect the I2C ports (GPIO2 & 3) to an external processor for testing. We're trying to do this with minimal soldering changes to the board, so that if needed we can quickly revert back to a setup that works w/ USB so we can use TICS as a development aid.
Unfortunately the user manual doesn't have a great guide as to the process to do this, and we are currently stuck with the CDCI holding the data line low, so we can't even look and see what's going on. We've performed the I2C disable test indicated in the FAQ (REFSEL = L, EEPROMSEL = H/L, RESETN = H, powercycle and check I2C status) and it did not result in a change, so based on that I don't think it is a EEPROM disable problem. We've also removed the MSP430's I2C communication lines (R165 & R166) so that it doesn't interfere with our master. We've also tried setting the LDO jumper for 1.8V and turning off the switch in case that the MSP430 was messing around with power settings, and that hasn't helped things either. We have another device on the I2C bus we're using to test, so we know that it is configured correctly, and the oscilloscope shows the CDCI is holding the data line firmly low.
Is there some obvious procedure available/that I'm missing to convert the eval kit from running off USB/PC to running of External Power/ external processor via I2C? We haven't removed the regulators from EEPROMEL & others, but we aren't sure they are necessary to remove, and we are trying to minimize the amount of bridges to undo in order to bring the system back to a TICS approved state.