...
Start the AWE Server on your Target. This can either be a local AWE Server on another PC or something like AWE_command_line. Make sure you know the IP or hostname of your target that’s running the server.
Open the Global Preferences window from the file dropdown menu
Switch the “Connection Type” dropdown from Local Server to Remote Server.
Enter the IP or hostname of your remote target. The click “Reconnect to Server”
If a successful connection is made, you will see a “Connected” string appear under your remote connection string. You will also notice that the default Audio File path has changed to your target’s filesystem.
Now you can run your Designer layout on your remote target as if you were connected to a local target.
...
Note: Build configuration only affects the layout at the PC level. AWE uses a Designer->AWE Core dynamic instantiation model, so the Debug modules are simply not instantiated on the target layout. Overflow Detection.
Overflow Detection
...
Flash Manager Tool
The Flash Manager tool, which is delivered as part of the AWE Server, enables users to easily add and remove Audio Weaver Binary files (*.awb) on targets that support flash file systems. Once added to flash, the .awb file will be loaded by the AWE Core at boot-time and the target can run in stand-alone operation. See the next section ‘Using the Flash Manager’ for instructions on how to do this.
Note that another alternative for stand-alone operation is to store the .awb contents in a C array and compile it into an application directly. This method can be used on targets with or without a flash file system. For more information on this, see section 2.3.2 of the ‘AWE Core – Integration Guide.pdf’ available at https://dspconcepts.com/support .
Using the Flash Manager Tool
Generate an .awb file for your desired Audio Weaver design (.awd) in Designer by going to ‘Tools -> Generate Target Files’.
Select ‘AWB’ target file type and choose the directory to which the .awb file will be saved. Change the ‘Save Basename’ field to a name that is less the 16 characters, then hit the “Generate” button. It will then start compiling the system for creation of the .awb file.
Once the .awb file has been successfully generated, the following window will appear:
In AWE Server, select ‘Target -> Change Connection’ and connect to your target with the appropriate option.
In AWE Server, select ‘Flash -> Flash Manager’. Then press “Add File” button.
Browse to the previously-created .awb file and select it as the input file. Ensure that the file type is “Compiled Script” and check the box next to “Boot file” to designate this file to be used at boot-up (attribute = 26). Click the “Add” button to load the file into memory.
Once the progress completes, click “OK”.
After the file has been added, it will show up in the list “Flash file system on target” in the Flash Manager window. When you reset your target hardware and reconnect AWE Server to it, you should see a non-zero CPU % and heap allocated in the AWE Server, which indicates that the layout is indeed running.
Overflow Detection
On certain targets, AWE Core will detect any overflow conditions while a layout is running and present this information in AWE Server. An “overflow” occurs when the previous pump is not completed before attempting to schedule the next pump. The overflow logic is capable of detecting overflows in any of the sublayouts in a multi-rate layout.
...