Hi Brian,
If I understand the problem correctly, the issue is that HDL devices cannot
be instanced in assemblies. They can only be instanced in containers (which
encapsulate assemblies) or platform configurations (which are instanced
alongside assemblies).
An example of a container instance for the e31x platform:
https://gitlab.com/opencpi/osp/ocpi.osp.e3xx/-/blob/develop/hdl/assemblies/empty/cnt_e31x_mimo_xcvr_filter.xml
An example of a platform configuration instance for the e31x platform:
https://gitlab.com/opencpi/osp/ocpi.osp.e3xx/-/blob/develop/hdl/platforms/e31x/cfg_1rx_1tx_mode_2_cmos.xml
Hope this helps.
Thanks,
Brandon
On Wed, Apr 22, 2020 at 6:48 PM Brian Padalino <bpadalino_at_gmail.com> wrote:
> I am making an assembly of an HDL device that I created in my own project
> outside of opencpi.
>
> I am running into a problem that states:
>
> Worker <name> was not found in any of the component libraries built for
> zynq
>
> If I go to the directory (hdl/devices/<name>.hdl), I can build just fine.
> At the end, it says it's creating symbolic links and, indeed, I see links
> in hdl/devices/lib/hdl/zynq pointing to vhd, v, and edf files.
>
> I tried playing around with OCPI_COMPONENT_LIBRARY_PATH, and
> OCPI_PROJECT_PATH environment variables, but to no avail. I also tried
> searching other repositories for doing this, but I couldn't find many other
> people implementing OpenCPI devices/assemblies/projects.
>
> I don't quite understand what needs to be in place for an assembly in the
> same project to be able to use an HDL device in the same project.
>
> Can someone shed some light on this for me? Just a link to an example
> out-of-tree would probably be enough.
>
> Thanks,
> Brian
>
Received on Thu Apr 23 2020 - 14:37:45 CDT