Have you tried to add those workers into the application?
I'll try a quick test tomorrow (which is a US holiday).
On 1/17/21 6:16 PM, Walters Dominic A via discuss wrote:
> Classification: UK OFFICIAL
>
>
> Hi Brian,
>
> The ACI can't be used on platform or device worker properties, either to set or get them.
> I raised this on the email list in December 2019: http://lists.opencpi.org/pipermail/discuss_lists.opencpi.org/2019-December/000300.html.
> There is an issue for this: https://gitlab.com/opencpi/opencpi/-/issues/485.
>
> -----Original Message-----
> From: discuss <discuss-bounces_at_lists.opencpi.org> On Behalf Of Brian Padalino
> Sent: 16 January 2021 21:18
> To: discuss_at_lists.opencpi.org
> Subject: [Discuss OpenCPI] Set Platform Properties from Application
>
> The FSK application I am running has to set some platform properties to work correctly. These properties, essentially, are hooked up to different RF switches in the FPGA logic. It was easy to expose them as properties.
>
> With OpenCPI v2.0.1, I am getting an exception stating that there is an unknown application property. Note that these are platform properties, so maybe I am doing something wrong. In my application, I have:
>
> OA::Application app(xml_name.c_str(), NULL) ;
> app.initialize() ;
> app.setProperty( "platform_name", "platform_property", "value" ) ;
>
> I am able to use ocpihdl to query the platform property as expected:
>
> # ocpihdl get platform_name platform_property
> 28 platform_property: 0
>
> I can set and get it as well, and it works just fine. Did the syntax change? Do I need to change how I call this?
>
> Thanks,
> Brian
>
Received on Mon Jan 18 2021 - 03:06:51 CST