[root_at_asdr-24 opencpi]# file /mnt/card/opencpi/brik2/lib/libocpi_rcc_s.so
/mnt/card/opencpi/brik2/lib/libocpi_rcc_s.so: ELF 32-bit LSB shared object, ARM, EABI5 version 1 (SYSV), dynamically linked, not stripped
'system.xml' is basically the same as the ZedBoard default. It looks like this on my system:
<opencpi>
<container>
<rcc load='1'/>
<hdl load='1'/>
</container>
<transfer smbsize='128K'>
<pio load='1' smbsize='10M'/>
<socket load='1'/>
<dma load='1'/>
</transfer>
</opencpi>
________________________________
From: Chris Hinkey <chinkey_at_geontech.onmicrosoft.com>
Sent: Tuesday, May 7, 2019 10:56:27 AM
To: Paulz, Eric; discuss_at_lists.opencpi.org
Subject: Re: New RCC platform issues (no available containers)
that container "driver" getting loaded is what allows ocpirun to use the rcc container. by commenting those lines out of the system xml you are essentially saying you don't have a rcc container. this is why when you comment them out you are seeing that error.
You may want to comment out the hdl container in the system xml for test purposes here to just work on the rcc side of things. The first problem you saw is the one that we need to solve.
What happens if you run "file /mnt/card/opencpi/brik2/lib/libocpi_rcc_s.so" on your platform?
Also what is your system.xml with teh rcc container in it?
________________________________
From: discuss <discuss-bounces_at_lists.opencpi.org> on behalf of Paulz, Eric <epaulz_at_vt.edu>
Sent: Tuesday, May 7, 2019 10:47 AM
To: discuss_at_lists.opencpi.org
Subject: [Discuss OpenCPI] New RCC platform issues (no available containers)
Hello,
A week or two ago you guys were helping me get an SD card created using a new RCC platform spec. That has been successful, and it seems that cross-compilation etc. worked correctly as I am now running commands on my board and getting OpenCPI output (errors/logs). I am now running into a couple more errors.
First I will note that I am not booting my board from the SD card. I am just using the opencpi file tree created by the 'make deploy' command.
When I run the setup script on my board, I get the following error message:
[root_at_asdr-24 opencpi]# . ./default_mysetup.sh
Discovering available containers...
Exiting for exception: Error processing system configuration file "/mnt/card/opencpi/system.xml": error loading the "rcc" "container" dri
ver from "/mnt/card/opencpi/brik2/lib/libocpi_rcc_s.so": error loading "/mnt/card/opencpi/brik2/lib/libocpi_rcc_s.so": /mnt/card/opencpi/
brik2/lib/libocpi_rcc_s.so: internal error
%
'libocpi_rcc_s.so' exists in the location specified. Perhaps someone could elaborate on what 'internal error' might mean?
I noticed that if I edit 'system.xml' and comment out everything between the <opencpi></opencpi> tags, I seem to get a step further but then it fails because it can't find any containers. Here is the message I get when I try that:
% . ./default_mysetup.sh
Discovering available containers...
Available containers:
# Model Platform OS OS-Version Arch Name
% cd ../brik2/bin/
% ls
busybox gdb ocpidriver ocpiocltest ocpiserve ocpizynq
ctests loadFlash ocpihdl ocpiremote ocpitest probeJtag
cxxtests ocfrp_check ocpiocl ocpirun ocpixml rsync
% ./ocpirun -v -l8 ../../applications/copy.xml
OCPI( 8: 13.0632): Processing XML system configuration file: "/mnt/card/opencpi/system.xml"
OCPI( 8: 13.0633): Performing discovery for all transfer drivers
OCPI( 8: 13.0633): Performing discovery for all library drivers
OCPI( 8: 13.0633): Searching directory /mnt/card/opencpi/brik2/ recursively, from OCPI_LIBRARY_PATH
OCPI( 8: 14.0149): Performing discovery for all container drivers
OCPI( 8: 14.0149): Component: file_read name: file_read impl: spec: ocpi.core.file_read selection:
OCPI( 8: 14.0149): Component: file_write name: file_write impl: spec: ocpi.core.file_write selection:
OCPI( 8: 14.0149): Considering implementation for instance "file_read" with spec "ocpi.core.file_read": "file_read" from artifact "/mnt/c
ard/opencpi/brik2//artifacts/ocpi.core.file_read.rcc.0.brik2.so"
OCPI( 8: 14.0149): Accepted implementation before connectivity checks with score 1
OCPI( 8: 14.0150): Considering implementation for instance "file_write" with spec "ocpi.core.file_write": "file_write" from artifact "/mn
t/card/opencpi/brik2//artifacts/ocpi.core.file_write.rcc.0.brik2.so"
OCPI( 8: 14.0150): Accepted implementation before connectivity checks with score 1
OCPI( 8: 14.0150): For instance file_read there were 1 candidates. These had potential containers:
OCPI( 8: 14.0150): Checking implementation file_read model rcc os linux version b2 arch arm platform brik2 dynamic 0 opencpi version 1.5
OCPI( 8: 14.0150): Candidate 0 /mnt/card/opencpi/brik2//artifacts/ocpi.core.file_read.rcc.0.brik2.so is ok for no containers
No containers were found for deploying instance 'file_read' (spec 'ocpi.core.file_read').
The implementations found were:
Name: file_read, Model: rcc, Arch: arm, Platform: brik2, OpenCPI Version: 1.5, File: /mnt/card/opencpi/brik2//artifacts/ocpi.core.file_
read.rcc.0.brik2.so
OCPI( 8: 14.0150): Error Exception: For instance "file_read" for spec "ocpi.core.file_read": no feasible containers found for the 1 imple
mentation found.
Exiting for exception: For instance "file_read" for spec "ocpi.core.file_read": no feasible containers found for the 1 implementation fou
nd.
%
The 'system.xml' I'm using is the same one produced when building an SD card for a ZedBoard (as my board is very similar). I'm just not sure what I need to do to make a container available so I can run a test application.
Thanks in advance,
-
Eric C. Paulz
Computer Engineer
Hume Center for National Security & Technology
epaulz_at_vt.edu<mailto:epaulz_at_vt.edu>
Office: 540-231-6180
Cell: 864-243-6767
Received on Tue May 07 2019 - 15:02:28 CDT