ADC is stable in operation. However, if work is performed at SPI with other consumers (CS = 1 for ADC), then ADC stops working - it is not possible to read registers, data is also incorrect.
If you have encountering an SPI communication issues, it might be worth reading this thread which includes most of the frequently asked questions regarding sigma delta products.
Digital Interface FAQ - Sigma Delta ADC
If you have further questions, please let us know.
Thank you for the information. I'll get to explore her.
But what about the mutually exclusive:
"The SCLK can continue to run between data transfers, provided the timing numbers are obeyed"
"it is recommended that SCLK idles high between data transfers"
Does the ADC sense the SPI signals with the inactive CS?
When /CS is inactive, any activities on SPI lines will be ignored since the bus will be disabled. When /CS is held low or active, the ADC will then have access to the data bus between itself and the microprocessor. It is important that you provide the correct number of clock cycles when reading from or writing to the control registers. If you provide one extra clock cycle and then write to the part, you will put the part into an unexpected state. A user can transmit the data as a continuous stream or the data can be split into bytes. For example, if writing 24 bits to the ADC, all 24 bits can be transmitted continuously or the data can be divided into 8-bit words. However, if the data is divided into bytes, /CS must be held low until all bytes are transmitted. Thus, "it is recommended that SCLK idles high between data transfers" means that SCLK should be idle high between the 8 bit reads. However, when using the /CS line as a Frame Sync, The SCLK can continue to run between data transfers, provided the timing numbers are obeyed meaning that this line is brought high at the correct time. Check that you have allowed the correct number of clock pulses to occur before /CS is brough high.
You described the expected behavior of the SPI. Nevertheless, I have problems. I will investigate the problem further.
I would also like to understand what kind of problem you are encountering. Can you provide us a scope shot of your digital interface? Can you also provide us additional details of what's happening to your digital interface?
I made an unacceptable mistake for the researcher - I replaced the part and rewrote the firmware. What has helped now is unclear. But it worked.
Good to hear that you have solved the issue. If you have any other concerns, just let us know.
Retrieving data ...