ZCU208 image - RFDC driver not found

Hello

I successfuly generate an image for the ZCU208
Jupyter is up when open it
But when I am tring to call the xRFDC xRFCLK and drivers seems not to be present

The content of the .spec file for this board is :

     ARCH_ZCU208 := aarch64
     BSP_ZCU208 := xilinx-zcu208-v2020.2-final.bsp
     STAGE4_PACKAGES_ZCU208 := ethernet

Maybe I need to add explicitly the packages on the .spec file ?
Will appreciate for any help , is there any others ways to do that ?

Thank you !
Shalom

Hi there,

Yes those packages need to be added to the spec if you want them included in your image. E.g. the zcu111 .spec

Another example of PYNQ ported to a ZCU216 is here that you could follow as a reference.

Thanks
Shawn

1 Like

Right thank you very much @skalade !

Hello

One fact that I missed is that I am using a VM with vivado2020.1 and petalinux2020.1 installed
and using the xilinx-zcu208-v2020.2-final.bsp . is there any chance it would work ?

Is this mismatch critical ?

Thanks !

Hi there,

If you managed to build it before with that bsp it might all just work. Can’t say with certainty.

Would recommend using latest tools and latest image if possible.

Thanks
Shawn

Hi @skalade

Yes I as you guessed it works , but as you said also , seems better to have last tools

Lot of thanks

1 Like

Hi @shalom,

Were you able to get PYNQ up and running on the ZCU208?

Thank you.

Hello John

Pynq is running on board
But i didnt found the xrfdc and xrfclk for the board

Shalom

1 Like

Hi @shalom

Do you think starting with the ZCU216 build might be easier to get a fully working ZCU208 build?

Hi John , I go now through #method2 from here: GitHub - sarafs1926/ZCU216-PYNQ: Board repo for the ZCU216 RFSOC
for the zcu208 board … will check if its working

Shalom

@Shalom

Hi Shalom. Were you able to build the SCU216 code from the link you posted, and does it work on the ZCU208 board? Thank you.

John

Hello

It seems not to be same clocks on the 2 boards
There is an error when calling the function that configure the clock
I dont remember whats the error exactly
So we put that in standby for now …

Shalom