On Thu, Apr 23, 2020 at 10:47 AM Brian Padalino <bpadalino_at_gmail.com> wrote:
> Hey Brandon,
>
> On Thu, Apr 23, 2020 at 10:37 AM Brandon Luquette <bluquette_at_geontech.com>
> wrote:
>
>> 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.
>>
>
> Yes, thanks. It seems I got confused about devices versus components. I
> am making something that is more like a component (does not connect to
> external pins by itself) and not a device (connects to external pins).
>
> I'm going to refactor and try to make it a component.
>
So I made it a component, but something new is happening. It seems the
names of my EDIF netlists have an '_rv' attached to it. I did a comparison
between the mfsk_mapper.hdl in the opencpi project, and I can't understand
why that worker netlist is called mfsk_mapper.edf when mine is called
<name>_rv.edf.
Has anyone got any information on why it's called _rv instead of just what
hte name of the device is?
Thanks,
Brian
>
Received on Thu Apr 23 2020 - 17:23:11 CDT