ADRV9008-1 + ADRV9008-2 + ZCU102 REFERENCE DESIGN HELP

Hello,

Are you using Linux or No-OS ? 

In my opinion, the two boards can be brought up sequentially, as if they are the only ones on the ZCU102, so the code you've used for a single ADRV9008-2 should work on this project, with the SPI/GPIOs adjusted to reflect the new design. I suppose, you'll need also GPIOs, not only SPI to each board. If the two boards need common clocking, or have other synchronization requirements, things may be more complex.

Regards,

Adrian

Waiting for your reply...

Hello Adrian,

Thanks for the prompt response.

"The problem is that the HPC0 and HPC1 are connected to different transceiver banks, which are not adjoined, so they need their own reference clock. On our ADRV9009-ZU11EG, this is not a problem, as they are connected to adjoined banks."

 So for our custom board,since ADC and DAC are connected to adjacent banks,we should be able to use ADRV9009-ZU11EG HDL reference design but in software we need to take into account of AD9528 in place of HMC7044 and ADRV9008-2 and ADRV9008-1 in place of 2 ADRV9009. We will be needing your help in configuring the same in no-os in near future.

"Regarding SPI, i was thinking to use SPI0 to connect to HPC0 evaluation board ICs and SPI 1 to connect to HPC1 evaluation board ICs(or vice versa), so you should have 3 CS per SPI, but given that you have 6 CS, should be enough."

As of now we would like to configure the way you have described using 2 SPIs.Please guide us what changes needs to be done in no-os software that is available for ADRV9009 so that we can configure ADRV9008-1+ADRV9008-2.

 FYI: Once again mentioning that I tried to independently interface ADRV9008-1 with ZCU102 by using the same code  which is there for ADRV9009 with few changes like we made TX_Enable as OFF and RX_Enable to be ON,we disabled the DAC initilazation part from Transport to PHY layer including clock  also, but its popping the following error: ERROR:247:TALISE_waitArmCmdStatus() failed due to thrown ARM error.ARM time out error:TALISE_waitInitCals() failed.

Regards

Siddharth

Sid@123 said:

So for our custom board,since ADC and DAC are connected to adjacent banks,we should be able to use ADRV9009-ZU11EG HDL reference design but in software we need to take into account of AD9528 in place of HMC7044 and ADRV9008-2 and ADRV9008-1 in place of 2 ADRV9009. We will be needing your help in configuring the same in no-os in near future.

That's correct. You could also probably squeeze both ADRVs in a single transceiver bank, if the application suits that.

Regarding the no-os configuration, I will move the question to the appropriate forum and somebody from that group can give you specific instructions.

Regards,

Adrian

Moved to No-OS forum

Hi Siddharth,

Regarding the SPI question:

devices/adi_hal/parameters.h contains these chip select definitions:

Hello Buha,

Thanks for the detailed reply.

Using 3 Chip Selects on SPI0 is not possible even if its possible in HDL, as there are only 2 CS lines brought out from SoC to each HPC connector in hardware.(Please confirm if i am correct).

We will try to use 2 SPI for ADRV9008-1 and ADRV9008-2 on ZCU102.

But in between we tried to interface only ADRV9008-1_WPCBZ on ZCU102 but its popping up

error: RFPLL not locked.

Following Changes were made in no-os project files of ADRV9009 for ADRV9008-1 as per the sequence of configuration mentioned in headless.c generated from ADRV9009(ADRV9008-1) TES GUI :

In talise_setup function:

uint32_t initCalMask = TAL_ADC_TUNER | TAL_TIA_3DB_CORNER | TAL_DC_OFFSET | TAL_RX_GAIN_DELAY | TAL_FLASH_CAL | TAL_RX_QEC_INIT;

uint32_t trackingCalMask = TAL_TRACK_NONE;

talAction = TALISE_setRxTxEnable(pd, TAL_RX1RX2_EN, TAL_TXOFF);

I have commented the TX and ORX portions in headless.c. I have attached app_talise.c,headless.c and talise_conif.c files

.forum_adrv9008-1.rar

Please help us out on this.

FYI :While interfacing ADRV9008-2 with ZCU102,we used the same code(hdl_2019_r2(Vivado 2019.1)+No-Os software) as it is,,which is there for ADRV9009 and it(ADRV9008-2) is configured successfully.

 Also we have interfaced ADRV9009_WPCBZ successfully.

Regards

Siddharth

Hi Buha

We are waiting for your response

Regards

Siddharth

Hi Siddharth,

Sorry for delay,

The no-OS project under 'projects/adrv9009', as you can see only supports adrv9009 based hardware.

In theory, what you are trying to do should work by only initializing RX-related stuff (for adrv9008-1). I saw that you are disabling TX-related stuff, that is reasonable. You also change initCalMask (probably because that's what TES software output was) and I checked that the linux driver, known to work, actually uses the same initCalMask you use for adrv9008-1 so that's good:

https://github.com/analogdevicesinc/linux/blob/master/drivers/iio/adc/adrv9009.c

I don't see anything obviously wrong. What I would do is draw inspiration from the linux implementation at the above link and try to match it. 

This would be the device tree configuration for zcu102 + adrv9008-1:

https://github.com/analogdevicesinc/linux/blob/master/arch/arm64/boot/dts/xilinx/zynqmp-zcu102-rev10-adrv9008-1.dts

Regards

Hi Siddarth,

I have some good news, someone from the team has created a pull request to add support for adrv9008-1 and adrv9008-2:

https://github.com/analogdevicesinc/no-OS/pull/1018

Please try the code by simply checking out branch dev/adrv9008 and building as usual, making sure to enable the flags in projects/adrv9009/src/app/app_config.h 

Best regards

Thanks Buha for the help.

Actually we were able to configure ADRV9008-1 on ZCU102.Main problem what we observed is

Error"RF PLL Not Locked" is there for some specific profiles generated by TES.

When i changed with other profiles from TES on trial and error basis,it worked for us.

Now what we will do is try using this code and i will run the profile for which error was thrown earlier.

Regards

Siddharth

Hi Adrian,

Now we want to configure "as discussed earlier in this thread" ADRV9008-1 on HPC0 and ADRV9008-2 on HPC1 at a time. As advised by you, we used SPI0 for HPC0 and SPI1 for HPC1.Similarly for gpio lines we mapped to both HPC's. Also pin planning is being done for both HPC corresponding lines towards FPGA. Now regarding JESD lines,since MGT banks corresponding to HPC0 and HPC1 are not adjoined,we need to replicate GTHE4 XCVR block in block design of reference HDL design.Please guide us in, how to add another GTHE4 XCVR block for the other HPC and what all changes needs to be done so that our HDL design for both HPC is ready.

Regards

Siddharth

Hi Adrian,

Now we want to configure "as discussed earlier in this thread" ADRV9008-1 on HPC0 and ADRV9008-2 on HPC1 at a time. As advised by you, we used SPI0 for HPC0 and SPI1 for HPC1.Similarly for gpio lines we mapped to both HPC's. Also pin planning is being done for both HPC corresponding lines towards FPGA. Now regarding JESD lines,since MGT banks corresponding to HPC0 and HPC1 are not adjoined,we need to replicate GTHE4 XCVR block in block design of reference HDL design.Please guide us in, how to add another GTHE4 XCVR block for the other HPC and what all changes needs to be done so that our HDL design for both HPC is ready.

Regards

Siddharth

Hello Siddharth,

Ultimately you'll need two util_adxcvr blocks, one for each HPC, which will either connect one RX (2 RX lanes) or one TX and one ORx( 4 TX lanes and 2 RX lanes) and reconnect the data link layers to the coresponding util_adxcvr. 

As an intermediary step you could copy the whole data path for JESD204 so you'll have support for two ADRV9009s, with the correct pinout and reference clocks (for one path pinout for HPC0 and for the other HPC1) and afterwards remove the pieces that are not needed.

Do you have a github repository with your HDL changes ? I could take a look and give specific pointers.

Regards,

Adrian

Hello Adrian,

I replicated only util_adxcvr part as my requirement is ADRV9008-1 on 1 hpc and ADRV9008-2 on other hpc. Also i cloned spi and gpio connections as advised by you. In implemented design, tx and rx jesd data lines are placed in respective banks corresponding to hpc0 and hpc1.

Before validating whole setup on hardware, with this bitstream what i hv generated now,is it ok to connect only adrv9008-2 on hp1 and check whether its working fine and then similarly for only adrv9008-1 on hp0 and then go for combined setup with changes in no-os code that caters both adrv9008.

Regards

Siddharth

Hello,

Yes, validating independently should be good steps in validating the whole design.

Regards,

Adrian

Hello Adrian,

 I validated independently ADRV9008-2 on hp1 and ADRV9008-1 on hp0 using bitstream(combined logic hp0 and hp1) and in both the cases device is in data mode which means its all fine.

But 1 observations:

I routed spi0 to hp0 in hdl design and in no-os platform, device_id is set to 0 and gpios for adrv9009_resetb and ad9528_resetb has been set with an offset of 78. Next when I checked ADRV9008-2 on hp1,i only changed device id to 1 as spi1 is mapped in hdl but didn't change the gpios value for ADRV9008-2 and AD9528 resets in parameters.h, then it should not have been configured. But its configured successfully with data mode. Also when I gave the required gpio values its working in data mode.

Regards

Siddharth 

Hello Adrian!!

Waiting for your reply...

If this part what I asked is clear,then I can focus on configuring both hp0 and hp1 sequentially in baremetal.

Thanks n regards 

Siddharth

Hello Siddharth,

Do you have a branch with the full design or a block diagram ?

I wasn't sure if it was a question or just an observation, but indeed it seems strange, but I cannot say why it happen from the description above.

Regards,

Adrian

Regarding the software changes you did, maybe somebody from the software group may add additional comments, but I suppose they would also need additional clarifications with the exact changes.

Hello Adrian!!!

Thanks so much for all the guidance regarding HDL. Also i would like to thank buha for helping in getting no-os project with code segregation between ADRV9008-1 and ADRV9008-2. This was really helpful while doing no-os for both ADC and DAC together.

Now i am able to configure both ADRV9008-1+AD9528 on HPC0 and ADRV9008-2+AD9528 on HPC1 simultaneously.

It took much time as i was not continuously working on it.

Also with respect to last question what i asked,i think i got the clarity now. My doubt was, without proper gpio assignment for reset signal in HPC0,still ADC was getting configured. Actually it can be configured what i observed,only problem will be when we want to re run the system debugger for configuration,ADC wont configure.It will fail in Talise_initialize. We have to repower the board in this case. Once i did the proper assignment of gpio,this was solved.

I have to do a RF-loop back test and will ask for your support if required.

Thanks & Regards

Siddharth

Hi Siddharth,

Thanks for letting us know that it works. I will lock this thread now for commenting since too long threads may be hard to read by people looking for solutions on EngineerZone.

As always, feel free to open new threads if you think you need help from ADI engineers.