Just as in dynamic signal flow, a flash/file I/O scheme needs to be implemented on the desired target device. Refer to Section “Tuning Sets (SETi) implemented” of this document. The following explains the way dynamic signal flow for control works.
Master Control Design
The control flow is designed in the GTT. Once completed, it is sent through an xTP message to the xAF. Refer to the GTT documentation for more information on how to design the control flow in the SFD.
Saving the master control data on the target device
On the target device, the xTP layer should have a way to use an instance of the InitializationMsgParser class. This class is available in the interface library that is delivered with the xAF. The InitializationMsgParser can be initialized as it is shown in Section “Multiple Instance Multiple Core support for dynamic SFD with GTT” of this document.
Once it is initialized and xTP message, XTP_DEVICE (0x64), is received, it should trigger the parseMessage as shown below:
Instantiating the Control Module Flow from the Control Flow stored on the device
Once the step above is complete, the master control flow can be instantiated by rebooting the system. To do this, the code below should be implemented along with the initialization of the framework. You can use the DeviceParser class, which is also included in the interface library. Below is a brief example on how to load the master module.
Once m_numPins and m_controlMsgMap are populated, they can be used to instantiate the master module:
xAFInitMasterControl(&g_masterControl, m_controlMsgMap, m_numPins, UNUSED_VAR, memAlloc alloc);
Example Implementation
In current release, examples are available for IVP. The control module file, sect131072.flash, is stored in the AudioFrameworkDLLS folder indicated by IVP. You can find a reference implementation on the xAF repo in the VirtualAmpEffect file at the following location: