Tool/software:
Hi TI Support Team,
I am encountering an issue while configuring the input range and resolution for the ADS8688. Specifically, the device does not appear to apply the new configuration settings correctly and the response is consistent across all channels (CH0 to CH7). Below are the details of the problem:
-
Goal:
I am attempting to set the Range Select Register for all channels to0101, which corresponds to an input range of 0 to 2.5 x VREF. -
Issue:
- After writing the new input range setting to the Range Select Register for any channel, the register does not reflect the updated value. When I read back the register, it consistently returns
0x00. - To confirm this issue, I read the ADC values for all channels with ~0V input, and they return
0x7FFFinstead of a value close to zero. - This behavior is observed across all channels (CH0 to CH7).
- After writing the new input range setting to the Range Select Register for any channel, the register does not reflect the updated value. When I read back the register, it consistently returns
-
Waveform Confirmation:
I have verified the SPI communication using a logic analyzer and the waveform for writing the new resolution and range settings matches the protocol in the datasheet. But the Range Select Register remains the same. -
Steps Taken for Debugging:
- Verified SPI timing and communication integrity.
- Attempted to write to the Range Select Register for all channels individually and in sequence, with the same result.
- Repeatedly read back the registers after configuration attempts to confirm the behavior.
-
Questions:
- Are there specific initialization steps required before configuring the Range Select Register?
- Is there a required write sequence or delay that I may be missing?
- Could there be a device-level lock or protection that prevents writing to the Range Select Registers?
- Is there a common issue that could explain why all channels behave identically and fail to update?
Any insights on this issue would be greatly appreciated, as I am unable to proceed with testing due to the configuration failure.

