Question on TICS pro.
Anyway to verify the I2C address (Set the I2C address by clicking “Set I2C Address” on TICS pro) by using TCS pro?
Yong,
Once I2C address is set, you can navigate to the Raw Registers page, find a register with read-only values in it, and click the "Read Register" button.
TICS Pro's Raw Registers page holds a set of all bit values the GUI can program to, or read from, the device. These register maps are typically pre-loaded with some default values that make evaluation with an EVM easier, so that users can write all registers using one of the available methods ("Write All Registers" button in register map, command in the USB communications top menu, or global hotkey Ctrl+L).
Depending on the I2C address given to TICS Pro, you may see success and readback XOR of software, or an error on readback (implying an incorrect I2C address). Images below show an example for successful and failed readback of R2.
Success:
Fail:
It occurs to me that we document R9 in the register map, but TICS Pro does not include this field in the available registers for writing or reading. So my advice about R9[7:1] is inapplicable in TICS Pro. Please disregard.
Regards,
Derek Payne
Yong,
For the "Read Register" question: no difference means the readback value from the device is the same as the value already in TICS Pro's register map.
According to the register documentation, R0 through R3 are read-only constants in this device. The LMK05318B profile loads with these addresses in the software register map pre-defined to the same values as stated in the documentation.
If you click "Read Register" while one of these addresses is selected in the register map, and the readback is successful (because you have the correct I2C address for the device), the status bar will be updated with confirmation readback has been performed, the address of the register that was read, and the contents of that register on the device, XOR'd with the previous contents stored in TICS Pro's software register map. Since TICS Pro pre-loads the software register map with the same values that are in the device, this XOR should be 0x000000, as shown in the success image.
If the readback fails instead (because you do not have the correct I2C address for the device), the status bar will indicate an error trying to read that register, as shown in the failure image.
Technically the readback could also succeed, but return a value that differs from the pre-loaded constants for that device. This would indicate the I2C address on the bus is valid, but does not belong to the LMK05318B.
---
For your second question:
TICS Pro has the above indirect mechanism of checking the I2C address is valid for the device. I think we could design a more direct way to check the full I2C address space and list every device found by trying to read some of these read-only constants and matching to a lookup table of TI devices, but that capability is not supported today.
If LMK05318B is the only device on the I2C bus, you can click the "Scan I2C Bus" function, and the I2C address used by TICS Pro will automatically be updated with the first address that responds. But there is no "validation" performed - if there are two devices, and one of them is at an address that is less than LMK05318B address, this function would pick the wrong device.
or
Regards,
Derek Payne
Yong,
Yes, if you read R2 of LMK05318B and you have the correct address, you should see 0x35 data returned. It might report this as 0x000235, since the address is included with the data during transactions.
The I2C address selected for "Read Register" will be whichever address is in the box in the "USB Communication -> Interface" dialog, next to the "Set I2C Address" button.
