[Discuss OpenCPI] Fwd: Fwd: Fwd: Fwd: Multiple AD9361 Devices Cause Multiple Connections Error

From: Davis Hoover <dhoover_at_geontech.com>
Date: Thu, 23 Jan 20 11:42:09 -0500

Brian, I am actively working on this when I find the time. The
hdl-config.cxx fix gets past the code generation step, but there are HDL
build errors I'm still investigating.

---------- Forwarded message ---------
From: Brian Padalino <bpadalino_at_gmail.com>
Date: Thu, Jan 23, 2020 at 11:22 AM
Subject: Re: [Discuss OpenCPI] Fwd: Fwd: Fwd: Multiple AD9361 Devices Cause
Multiple Connections Error
To: Davis Hoover <dhoover_at_geontech.com>
Cc: <discuss_at_lists.opencpi.org>


On Fri, Jan 17, 2020 at 4:58 PM Davis Hoover <dhoover_at_geontech.com> wrote:

> Some debugging help: I often use make -n in these scenarios, which will
> print to the screen the ocpigen commands being run - except in this case
> where -n doesn't work, so I mod'd ocpigen to print out its arguments - then
> stepped through the ocpigen command with gdb. The ocpigen command can also
> be called w/ OCPI_LOG_LEVEL set to 8 or 10, which gives useful logging
> info.
>
> There are lots of ordinals being handled here, in part to facilitate the
> multi device<->subdevice worker scenario. One problem I have identified is
> an incorrect ordinal inspection - I *think* this is the fix:
>
> diff --git a/tools/ocpigen/src/hdl-config.cxx
> b/tools/ocpigen/src/hdl-config.cxx
> index bc0cfa5..d3412ff 100644
> --- a/tools/ocpigen/src/hdl-config.cxx
> +++ b/tools/ocpigen/src/hdl-config.cxx
> _at_@ -327,7 +327,8 @@ emitSubdeviceConnections(std::string &assy,
> DevInstances *baseInstances) {
> // If there are no mapping entries, then we use the implicit
> ordinal of the
> // supports element among supports elements for that device type
> if (s.m_supportsMap.empty()) {
> - if (si->m_ordinal != d.m_ordinal)
> + //if (si->m_ordinal != d.m_ordinal)
> + if (s.m_ordinal != d.m_ordinal)
> continue;
> } else {
> auto it =
>
> This suspected fix causes other problems that I'm still looking into.
>

Just curious if you've been able to look into the other issues mentioned
here from this fix?

Thanks,
Brian


Received on Thu Jan 23 2020 - 16:42:09 CST