I am trying to implement the Xilinx iBERT IP to accept PRBS data from the Talise (ADVR9008) chip and enable me to look at the eye diagram.
Initially I tried taking the ZCU102 reference design and deleting the talise_tmc block and all associated IP; replacing it with the Xilinx JESD_PHY and iBERT IP. The idea was, with a bit of editing of the device tree in peta-linux environment, I would be able to remove keep just the SPI driver to set-up the Talise chip and I could use iio to set the BIST PRBS mode or the framer. Unfortunately I encountered the knock on effect of losing comms with the device over SPI and not having the iio commands available.
My next thought was to go back to the original reference design and see if I could just instantiate the iBERT IP and plumb it into the existing ADI IP. It looks like most of the ports required come up to the top of the util_adxcvr block as the "up_*" signals, then go off to the axi_adxcvr IP block. I am reluctant to blindly try reconnecting and editing this design as I suspect it will all stop working again!
Any suggestions on the best way for me to proceed to try and get the eye diagram working to test the link from the Talise to the FPGA transceiver (uni-directional no loopback)?
As part of our default reference design we have: https://wiki.analog.com/resources/tools-software/linux-software/jesd_eye_scan
Have you tried using it ?
Thanks for your reply.
I have seen this page but not tried using the reference design because I didn't think it sounded like it could do what I required; please correct me if I'm wrong.
Does it allow me to run the eye scan for one way traffic using PRBS or similar from the ADRV9008 to the FPGA transceiver?
Which release are you using? Just tested with 2019_r1 and it works for me.
How to build Linux image and device tree:
Update: the 2018_r2 release is working as well. Did you make any modifications to the reference design?
We downloaded 2018_R2-2019_05_23.img.xz and put on an SD card without making any changes.
What do you think the cause of of my 'failed to read' error may be? I assume the ADRV9008 does not need a valid signal source as the JESD link will still be up and sending empty packets?
When I built the eye scan software I had warnings about deprecated functions, And when I run the gui there are GTK ciritcal warnings about gtk_widget_hide and gtk_toggle_button_set_active commands that have failed. Should I be concerned?
Why do you need to build the eye scan software? It should be on the image, by default. Try to connect a monitor to the display port, the tool should run right after bootup.
You don't really need a valid signal source for the device, but you should have an active JESD204 link.
Your error indicates that the Eye scan module does not respond to a DRP read request, which is quite strange taking the fact that you did not do any modification in the reference design.
I built the eye scan software as I wanted to run it remotely from my ubuntu VM.
I shall see if I can run it from the dev board image. FYI. I am using the image from the zynqmp-zcu102-rev10-adrv9008-1 directory.
I'll update you once I have had a chance to do this test.
I have ran the reference design with a monitor, kb and mouse connected. As you said, the eye scan software automatically starts and works correctly :-)
I then closed the app and tried relaunching -> jesd_eye_scan
The behavior I get now is the same as when I try and remotely run the app from my VM, whereby it connects and sees the JESD links, but fails to get data for the eye diagram.
However if I put "sudo" in front of "jesd_eye_scan" as per the autostart script, then all is OK.
So, it looks as though my remote connection has a permission issue. Do you know what I can do to overcome this?
In order to access the sysfs files you need root privileges. When you run remote using sshfs you need to login as root.
I have followed the instructions at: https://wiki.analog.com/resources/tools-software/linux-software/jesd_eye_scan#source
I am using the following sshfs command:
sudo sshfs -o allow_other -o sync_read -o connect -C -o workaround=all email@example.com:/ /home/osboxes/eyescan/mnt/zcu/
Some extra options suggested by a forum I read because it was having difficulty connecting.
Has anyone been able to give my problem some thought. Have you been able to install the eyescan software on a remote linux box and get it to run?
We can replicate your issue at our end, someone will start working on it next week. We will come back to you as soon as we have a fix.
Brilliant - thank you.