Hi DSP Team,
I am looking for guidance on the officially recommended process for converting Audio Weaver layout files through MATLAB scripting APIs without using the GUI-based “Generate Target Files” option.
Is there any official MATLAB scripting/API method available to generate:
-
.awsfiles from.awd -
.awbfiles from.awd
I would also like to understand the intended use cases and differences between .aws and .awb files.
Additionally, is AWB loading supported through MATLAB scripting APIs, or is AWB intended only for target-side/runtime loading workflows?
My goal is to automate layout generation and deployment entirely through MATLAB scripting.
Thanks & Regards,
Monika
7:11am
Hi Monika,
This is described in a version of our doc not yet published. Attached is a copy of the relevant section, (First a description of the Designer GUI Generate Target Files and then a description of how to duplicate the same functionality with Matlab scripts.)
Best,
Rob
7:36am
Regarding AWB loading:
AWB commands can be streamed to a running target:
i.)awe_diary('play', 'file.awb') — plays back a .awb (or .aws) through Server, equivalent to Server's File → Execute Script
ii.)awe_server_command('script,file.awb') — same effect, issued as a raw Server command
Store the .awb in the target's flash file system (for boot/standalone load)
target_flash_add(FILENAME, ATTRIB, coreID) — writes the .awb to the target's flash. Use ATTRIB = 24 (compiled, non-bootable) or 26 (compiled, bootable)
Caveats:
These all assume AWE Server is the runtime broker on the target. On a target where the BSP loads the AWB directly from firmware (e.g., via the generated XXX_initAWB.c/h arrays), there is no Matlab-driven load step — the .awb is compiled in. The Matlab API only loads .awb at runtime via Server.