The file_read is being run on the embedded device which doesn't have access to the input file. If running in remote mode (ocpiremote) try forcing file_read and file_write to run on your host system.  

ocpirun -v -d -x -m bias=hdl -p bias=biasvalue=0  -P file_read=ubuntu18_04 -P file_write=ubuntu18_04 testbias.xml

On Wed, May 5, 2021 at 3:27 PM <jpalmer@geontech.com> wrote:

After performing the steps again on the zcu104 the following log file was generated in the sandbox directory.

Discovery options: discoverable: 0, loopback: 0, onlyloopback: 0

Container server at <ANY>:12345

Available TCP server addresses are:

On interface eth0: 192.168.0.10:12345

Artifacts stored/cached in the directory "artifacts", which will be retained on exit.

Containers offered to clients are:

0: PL:0, model: hdl, os: , osVersion: , platform: zcu104

1: rcc0, model: rcc, os: linux, osVersion: 19_2, platform: xilinx19_2_aarch64

New client is "192.168.0.100:51782".

Shutting down client "192.168.0.100:51782" due to error: Code 0x17, level 0, error: 'Worker "file_read" produced an error during the "start" control operation: error opening file

Its also worth noting that this was presented once [$ ocpiremote start -b] was performed.

root@xilinx-zcu104-2019_2:~# [ 72.971915] opencpi: dma_set_coherent_mask failed for device ffffffc027f77400

[ 72.979120] opencpi: get_dma_memory failed in opencpi_init, trying fallback

[ 72.986108] NET: Registered protocol family 12

I have performed the exact set of commands and flow on the Zedboard and have been able to successfully run testbias. Can you confirm that testbias has worked on the zcu104 during regression testing of version v2.1.0 in any of the three modes (standalone, network, server)?

Thanks,

Joel Palmer

_______________________________________________
discuss mailing list -- discuss@lists.opencpi.org
To unsubscribe send an email to discuss-leave@lists.opencpi.org