We have detected your current browser version is not the latest one. Xilinx.com uses the latest web technologies to bring you the best online experience possible. Please upgrade to a Xilinx.com supported browser:Chrome, Firefox, Internet Explorer 11, Safari. Thank you!

Showing results for 
Search instead for 
Did you mean: 
Registered: ‎11-14-2008

ZCU111 TRD 2018.2 - adding AXI-GPIO kills RFTOOL app

I added two AXI-GPIO modules (dual channel) to the ZCU111 v1.0 TRD. I let Vivado auto-assign the address map to 0x8000_0000 and 0x8000_1000.

The project builds without error in Vivado. I opened the TRD PetaLinux BSP in 2018.2 and imported the .HDF and ran petalinux-build. No errors and the ZCU111 boots with no issues.

Autostart.sh kicks off RFTOOL. No errors.

eth0 is up and healthy. I can ping other locations on my network.

The problem comes when I try to connect a TCP client (MATLAB or the Xilinx LabView UI).

At the terminal I see:

Accepted data connection
Accepted command connection
datapath_t: waiting for lock
datapath_t: acquired lock

However, Linux dies here and I never see the final step:

datapath_t: Releasing lock

My best guess is that it's related to the call to init_gpio() in data_interface.c, which if successful will result in "Releasing lock" ... but it seems to choke around this point.

  /* initialise the gpio's for data path */
  ret = init_gpio();
  if (ret) {
    printf("Unable to initialise gpio's\n");
    goto gpio_init_failed;
  printf("%s:Releasing lock\n", __func__);

Any ideas?

The TRD design uses PS GPIO, so I'm not sure there's a conflict with my PL-based AXI-GPIO.



Tags (3)
0 Kudos