...

The tuning interface is one of the most important parts of the Audio Weaver integration. While there are many ways to connect a target device to PC-based Audio Weaver Server, it is important for system integrators to verify that the tuning interface is properly implemented, stable, and fast.

Required Modules

The tuning interface test procedure requires a certain subset of modules be present on the embedded target to execute. These are:

• Biquad Loading

• Scaler V2

• Periodic Source

• Null Sink

• Type Conversion

Stability test

The Stability test aims to test your target system’s stability in handling tuning messages under high CPU load from audio processing.

1. Create a dummy design with Audio Weaver similar to Figure 1. Correctly configure the input/output of the design as the target system requires. If a passthrough design is already available, that may be used as well.

   Image RemovedImage Added

2. Add “Sine Smoothed Gen” and “Sink Display” modules to the design. Leave the Sink window open to increase data exchange while it runs.

3. Add a “Cycle Burner” module to the design. Set numCyclesPerBlock to 1000 and run the design on the target.

4. Gradually increase numCyclesPerClock while monitoring through the AWE Server. Stop once the CPU load reaches at least 75% (Figure 2).

5. Allow AWE Designer to continue running the design for at least 1 hour.

There should be no crashes or server disconnections during the stability test. If any occur, debugging is needed to address the issue.

...

Speed Test:

The Speed test aims to verify system responsiveness of the tuning commands. It tests the read/write speed for different vector sizes to simulate what an actual running system may encounter, depending on the design and the number of inspector windows opened. Slow response from target can result in a communication timeout and can impact tuning capability.

...