Application Exception when link compile download

I think this a duplicate of previous request,
Could you please share the project and source code for simulating the issue?

Sorry it took so long to reply.

My original account was banned from replying because attaching a  source code link in the reply.

All my source code is in LRtest.c above.

What I want implement is print error message by dlb in schematic.

Thank you .

Hi,

SigmaStudio schematic application will be generated as different DXE which will run on target application allocated memory space and there is no library included in SigmaStudio schematic application to support "printf". So, the "printf" within plugin or internal algorithm not supported and even not recommended due to algorithm performance issues. 

You may use a parameter within algorithm to know about the state of the algorithm and use "Parameter Read" block to know about the state of the plug in using the parameter.
For more information refer Parameter Read [Analog Devices Wiki]                               

Also, you can use SigmaStudio schematic debugging technique to debug your plug in, please refer to section "Debugging Schematics using CCES" in "AE_42_SS4G_QuickStartGuide.pdf" document under SigmaStudio For SHARC installation folder. 

Please refer following link for more information about plug-in debugging technique,
(+) FAQ: ADSP-215xx/ADSP-SC5xx SigmaStudio For SHARC schematic custom plug-in debugging technique - Documents - SigmaStudio for SHARC - EngineerZone (analog.com)

Thanks.

The value of "parameter read" depends on when I click the read button.How can I get the first block output?

And "debuggging in CCES" can not help me when I design a plug-ins tool.

I think "printf" is a easy way to observe the output in every block.But I don't know how to make it work every time.

I will find a suitable method on basis of your suggestion.

Thanks for your reply.

The value of "parameter read" depends on when I click the read button.How can I get the first block output?

And "debuggging in CCES" can not help me when I design a plug-ins tool.

I think "printf" is a easy way to observe the output in every block.But I don't know how to make it work every time.

I will find a suitable method on basis of your suggestion.

Thanks for your reply.