Analog Devices VisualDSP++ 5.0 Service Manual page 115

According to Appendix A of the VisualDSP++ 5.0 C/C++ Compiler and
Library Manual for Blackfin Processors, there are two possible approaches
for building applications that run across both cores.
• One application per core, where executables are built for each core
using two passes of the linker
• One application across both cores, where a five-project group is
used and a single linker pass builds executables for both processors
The latter approach maps the lock variable to L2 memory shared by both
processors without any user intervention. The "one application per core"
approach requires user intervention to ensure that the lock variable is
mapped to the same address in L2 memory in each of the executables.
This is achieved by using the
can be used to resolve a symbol to its memory location assigned in the exe-
cutable for the other core.
The default and generated
/* $VDSG<customise-shared-symbols>
/* This code is preserved if the LDF is re-generated.
/////////////////////////////////////////////////////////////
// ldf_shared_symbols
/* Issue resolve statement for shared symbols mapped in CoreA.
** Below is an example of how to do that.
*/
#if defined(OTHERCORE)
# include <shared_symbols.h> /* C runtime library
VisualDSP++ 5.0 Device Drivers and System
Services Manual for Blackfin Processors
Power Management Module
statement in the
RESOLVE
files for core B contain the following:
.ldf
/* OTHERCORE is a macro defined to name
of the CoreA DXE */
shared symbols,
** uses macro OTHERCORE.
*/
file, which
.ldf
*/
*/
3-11