Hello,
- When I'm trying to Initialize AD9528 using the function call AD9528_initialize() and getting a warning.
- Below is the warning:
WARNING: AD9528_initialize() issues. Possible cause: REF_CLK not connected.
- We are giveing REFA clock freuency (RefA input) is 30.72 MHz
- I attached the myk_ad9528init.txt file for the AD9528 settings. Please check the settings of clockPLL1, clockPLL2, clockSysref, and clock output.
static spiSettings_t clockSpiSettings = { 1, //chip select Index 0, //Write bit polarity 1, //16bit instruction word 1, //MSB first 0, //Clock phase 0, //Clock polarity 0,//uint8_t enSpiStreaming; 1,//uint8_t autoIncAddrUp; 1 //uint8_t fourWireMode; }; ad9528pll1Settings_t clockPll1Settings = { 30720000, 1, 3, 0, 1, 0, 122880000, 2, 4 }; ad9528pll2Settings_t clockPll2Settings = { 3, 30 }; ad9528outputSettings_t clockOutputSettings = { 53237, {0,0,0,2,0,0,0,0,0,0,0,0,2,0}, {0,0,0,0,0,0,0,0,0,0,0,0,0,0}, {0,0,0,0,0,0,0,0,0,0,0,0,0,0}, {0,0,0,0,0,0,0,0,0,0,0,0,0,0}, {10,10,10,10,10,10,10,10,10,10,10,10,10,10}, {122880000, 122880000, 122880000, 122880000, 122880000, 122880000, 122880000, 122880000, 122880000, 122880000, 122880000, 122880000, 122880000, 122880000} }; ad9528sysrefSettings_t clockSysrefSettings = { 0, 2, 0, 0, 0, 0, 512 };
- While debugging AD9528, we observed that in one of the registers returning the unexpected value
- The expected value is 0x27 but we got 0xF2 and As per the AD9528 datasheet oxF2 means PLL1 is not locked
- Please see the below screenshots(AD9528 Page No: 66).


- while checking the jesd204 interface status by the function axi_jesd204_rx_laneinfo_read( ) sometimes get "error: 1" should I care about the errors? I attached a file
-
Please wait... IF : AD9528_ADDR_STATUS_READBACK0(Reg508) : f2 WARNING: AD9528_initialize() issues. Possible cause: REF_CLK not connected. rx_clkgen: MMCM-PLL locked (122880000 Hz) tx_clkgen: MMCM-PLL locked (122880000 Hz) rx_os_clkgen: MMCM-PLL locked (122880000 Hz) MCS successful CLKPLL locked AD9371 ARM version 5.2.2 PLLs locked Calibrations completed successfully tx_adxcvr: OK (4915200 kHz) rx_adxcvr: OK (4915200 kHz) rx_os_adxcvr: OK (4915200 kHz) rx_jesd status: Link is enabled Measured Link Clock: 122.874 MHz Reported Link Clock: 122.880 MHz Lane rate: 4915.200 MHz Lane rate / 40: 122.880 MHz LMFC rate: 3.840 MHz Link status: DATA SYSREF captured: Yes SYSREF alignment error: No rx_jesd lane 0 status: Errors: 0 CGS state: DATA Initial Frame Synchronization: Yes Lane Latency: 1 Multi-frames and 73 Octets Initial Lane Alignment Sequence: Yes DID: 0, BID: 0, LID: 0, L: 2, SCR: 1, F: 4 K: 32, M: 4, N: 16, CS: 0, N': 16, S: 1, HD: 0 FCHK: 0x47, CF: 0 ADJCNT: 0, PHADJ: 0, ADJDIR: 0, JESDV: 1, SUBCLASS: 1 FC: 4915200 kHz rx_jesd lane 1 status: Errors: 1 CGS state: DATA Initial Frame Synchronization: Yes Lane Latency: 1 Multi-frames and 73 Octets Initial Lane Alignment Sequence: Yes DID: 0, BID: 0, LID: 1, L: 2, SCR: 1, F: 4 K: 32, M: 4, N: 16, CS: 0, N': 16, S: 1, HD: 0 FCHK: 0x48, CF: 0 ADJCNT: 0, PHADJ: 0, ADJDIR: 0, JESDV: 1, SUBCLASS: 1 FC: 4915200 kHz tx_jesd status: Link is enabled Measured Link Clock: 122.876 MHz Reported Link Clock: 122.880 MHz Lane rate: 4915.200 MHz Lane rate / 40: 122.880 MHz LMFC rate: 7.680 MHz SYNC~: deasserted Link status: DATA SYSREF captured: Yes SYSREF alignment error: No rx_os_jesd status: Link is enabled Measured Link Clock: 122.874 MHz Reported Link Clock: 122.880 MHz Lane rate: 4915.200 MHz Lane rate / 40: 122.880 MHz LMFC rate: 7.680 MHz Link status: DATA SYSREF captured: Yes SYSREF alignment error: No rx_os_jesd lane 0 status: Errors: 0 CGS state: DATA Initial Frame Synchronization: Yes Lane Latency: 2 Multi-frames and 5 Octets Initial Lane Alignment Sequence: Yes DID: 0, BID: 0, LID: 0, L: 2, SCR: 1, F: 2 K: 32, M: 2, N: 16, CS: 0, N': 16, S: 1, HD: 0 FCHK: 0x43, CF: 0 ADJCNT: 0, PHADJ: 0, ADJDIR: 0, JESDV: 1, SUBCLASS: 1 FC: 4915200 kHz rx_os_jesd lane 1 status: Errors: 0 CGS state: DATA Initial Frame Synchronization: Yes Lane Latency: 2 Multi-frames and 6 Octets Initial Lane Alignment Sequence: Yes DID: 0, BID: 0, LID: 1, L: 2, SCR: 1, F: 2 K: 32, M: 2, N: 16, CS: 0, N': 16, S: 1, HD: 0 FCHK: 0x44, CF: 0 ADJCNT: 0, PHADJ: 0, ADJDIR: 0, JESDV: 1, SUBCLASS: 1 FC: 4915200 kHz tx_dac: Successfully initialized (245751953 Hz) rx_adc: Successfully initialized (122874450 Hz) rx_obs_adc: Successfully initialized (245748901 Hz) Done
- I checked the Framer Status = 0x3E and deframer Status = 0x28, and
- when I executed the function MYKONOS_jesd204bIlasCheck() I got mismatch value is 0x0 So, this is expected or not ?
uint16_t mismatch;mykError = MYKONOS_jesd204bIlasCheck(&mykDevice, &mismatch);if (mykError == MYKONOS_ERR_OK)printf("mismatch = 0x%x\n", mismatch);
- While running the code AD9375 and observing that clock mismatch, means that the AD9375 clock and FPGA-related clock are different. So this is expected or not?
- AD9375:
- tx_clkgen: MMCM-PLL locked (122880000 Hz)
- rx_clkgen: MMCM-PLL locked (122880000 Hz)
- rx_os_clkgen: MMCM-PLL locked (122880000 Hz)
- FPGA:
- tx_dac: Successfully initialized (245751953 Hz)
- rx_adc: Successfully initialized (122874450 Hz)
- rx_obs_adc: Successfully initialized (245748901 Hz)