All,

A recent push to the repo enabled the following improvements:

The "bias_xml" example now works correctly, see the tools/cdk/examples/bias_xml/Makefile for comments etc. This required some changes in the metadata for building hdl "applications"/bitstreams. see hdl/applications/testbias/*.xml. So you can run the same app, and the hdl-vs-rcc choice is either explicit or implicit based on OCPI_LIBRARY_PATH.

The newish xml applications have two new features:

1. The xml app can specify a "done" attribute which is the name of the instance that, when "done" indicates that the app is done, so that "wait" returns. And "wait" returns true if it timed out (when a timeout value is supplied). This "done" feature is useful when all workers in the app do not necessarily know when they are "done", so you can't wait for all to be "done".

2. The OCPI::API::Application class now has a setProperty method: setProperty("instance", "propname", "value");

Containers expose their "name()" method in the API now.

Files in the OCPI_LIBRARY_PATH that are not real artifacts are tolerated and printed in the log, but do not stop anything.

Protocol xml files can now have a top level "datavaluewidth" attribute to force the message granularity to a smaller value than is implied by the payloads in the operations. I.e. when you want byte granularity for future flexibility even though
there are no operations that need it now.

The OCPI_PAR_SEED allows setting different place-and-route seeds for xilinx bitsteram builds.

opcode symbols are automatically generated in the verilog worker skeletons.

OCPI_LOG_LEVEL works properly - set to 10 for max, 0 for silence

Hopefully a doc update will come soon that includes most of this.

Cheers,

Jim



_______________________________________________
opencpi_dev mailing list
[email protected]
http://lists.opencpi.org/listinfo.cgi/opencpi_dev-opencpi.org

Reply via email to