Post Go back to editing

AD9163 NCO Reset

Category: Hardware
Product Number: AD9163

Hi,

I need to reset the NCO of the AD9163. So when the SYSREF is set, the NCO must always start at the phase. The phase value or deterministic delay do not matter, sine the phase is measured and compensated at the beginning of the measurement. 

System:

DAC CLK = 6GHz
Number of Lanes = 4
Subclass 1 (One-Shot Sync Mode)
Unknown DAC CLK to SYSREF phase relationship. 

After powering up, the DAC is synced by SYSREF. In the measurement mode NCO value is written over SPI and reset by SYSREF. That works so far but in some cases the reset of the NCO is not reliable (the phase jumps from SYSREF to SYSREF). I found a correlation between stability and SYSREF_PHASE0 information. When SYSREF_PHASE0 has the value 0xE0 or 0xC0 then the reset is reliable otherwise not. It looks like a timing issues between SYSREF and DAC_CLK / 4. 

Can this problem be caused by a timing problem between SYSREF and DAC_CLK / 4?

Do you have a recommendation on how to solve this problem?

Best Regards

Parents
  • I also encountered a similar problem when debugging AD9163 multi shard synchronization:
    1.DAC CLOCK 6GHz;
    2.4 lane, line rate 7.5Gbit/s, F=1, K=32,;
    How to understand the return values of registers 0x037 and 0x038 mentioned in the manual as 0x0fe0, 0x0fc0, 0x0f80, and 0x0f00?
    4. The manual requires that the sysref time window be greater than at least 4 DAC CLK, which also meets the requirement;
    5.continuous mode
    After turning off NCO, using DDS to generate DAC data is still asynchronous;

    Debugging according to the synchronization steps did not have a significant effect. May I ask if there are any key areas that I missed?

Reply
  • I also encountered a similar problem when debugging AD9163 multi shard synchronization:
    1.DAC CLOCK 6GHz;
    2.4 lane, line rate 7.5Gbit/s, F=1, K=32,;
    How to understand the return values of registers 0x037 and 0x038 mentioned in the manual as 0x0fe0, 0x0fc0, 0x0f80, and 0x0f00?
    4. The manual requires that the sysref time window be greater than at least 4 DAC CLK, which also meets the requirement;
    5.continuous mode
    After turning off NCO, using DDS to generate DAC data is still asynchronous;

    Debugging according to the synchronization steps did not have a significant effect. May I ask if there are any key areas that I missed?

Children
No Data