In the AWE Core Integration Guide, Section 2.6.1 (Basic Threading Model) says:
Background Processing – In the background / main() thread, non-real-time tasks are
processed. The AWE Core has a single function that must be called from this context:
awe_fwTick(); This function handles all background tasks in AWE Core, including,
among other things, the processing of tuning commands.
Later, in Section 3.2 on integrating the tuning interface, Step 7 contradicts this by saying:
In the background thread, add repeated calls awe_fwTuningTick() to continually process
data as it arrives. This function will execute commands (once they’re fully received), and
will return REPLY_READY when a reply packet has been generated.
Which of these is actually correct? Are there actually two APIs to call from the background thread? Is there a different thread from which awe_fwTuningTick() needs to be called?