AnsweredAssumed Answered

ADSP-SC58x CCES executable name in L2 SRAM

Question asked by pinaz on Nov 30, 2015
Latest reply on Dec 11, 2015 by pinaz

SHARC+ projects created in CCES seem to always store the SHARC+ executable name in L2 SRAM.


It does this even when MCAPI and "Include C++ support" are not enabled in the project.  Note: the memory location of the string changes when "Include C++ support" is not enabled, so I have to wonder if the string's presence is not intended.


Writing unneeded data (C++ data structures and executable name) into L2 SRAM is undesired behavior; what CCES mechanism exists to disable it?