The device received improper data for a supported command.
Possible Causes:
- Attempted to write an unsupported value to a register using I2C
- A configuration stored in the EEPROM has an invalid combination of configuration values (i.e. VOUT higher than range allows)
Remedies and Workarounds
Here are some experiments you can try to narrow things down:
- Read the configuration into LTpowerPlay and click the "DRC" button in the toolbar to check for problems
- Power Cycle the device and see if the problem returns,
- If so, the unsupported data is programmed into NVM
- If not, the unsupported data is programmed in to RAM only
- Further Isolate which register(s) are causing the problem
- Issue a CLEAR_FAULTS
- Select registers one at a time in the 'All Global' and 'All Paged' (be sure to go through each page), and write the individual register (F12)
- Look for the CML_INVALID_DATA fault to re-apper, indicating the offending command
- Debug with Scope
- Trigger a scope on the falling edge of ALERTB while probing SCL/SDA
- Go Offline and then back Online in LTpowerPlay (forces a refresh of GUI cache values)
- Click Write All in LTpowerPlay
- Observe the command that was written to the device immediately preceding the falling ALERTB signal.