Hi team,
we are trying to create procedure for custom modules creation and had some questions about the workflow for deploying modules to an embedded target, specifically Analog Devices SHARC.Could you please confirm that my understanding is correct?
Steps 10–15 in Module developmet overview section under Custom Module in Audio weaver documentation , involve taking all the code and files generated by Audio Weaver and MATLAB and integrating them into an executable that runs on an embedded target.
The components include MATLAB‑generated module source code (.c and .h), any C code initializer file, and the Audio Weaver provided TargerInfo.h,AWE runtime files,Platform source files, Audio module.dlb and vectorLib.dlb.
Since our hardware target is a SHARC processor, the final embedded firmware image .dxe file is produced by compiling and linking all of these components together using the SHARC embedded toolchain CrossCore Embedded Studio.
Is this breakdown correct for a SHARC embedded deployment workflow?
4:07pm
Hi Sangeetha,
To summarize, after creating a module that runs natively you will have:
These, along with some other BSP files, need to be imported into your SHARC CCES IDE.
Compile that to an object file. Convert that into a static library.
Take that along with ModuleList.h (which you have edited to add the definition of the new module) and link that into your existing AWECore.
Please see: Deploying Custom Modules to SHARC (ADI-21569-SOM)
for more details.
Thanks,
Gary