AnsweredAssumed Answered

Custom LDFs in CCES

Question asked by Rai on Feb 27, 2014
Latest reply on Feb 28, 2014 by CraigG

Hi all,

I've been working on porting a project for the BF561 with a custom LDF from VDSP++ to CCES. Since the import tool was not much help here, I ended up creating a new project and adding the existing code instead of importing.

I have managed to compile the project, but I do get a warning, and I'm not sure I'm doing everything the right way.

 

 

I need ALL the L2 memory available to core A. Is this possible without a custom LDF?

 

I started out with a generated LDF and startup code, and then disabled the LDF/startup code addon, as suggested by the porting FAQ. However, if I remove "app_startup.doj" and "app_cplbtab561a.dj" from  $OBJECTS in the LDF, I get this error:

[Error li1171] "..\system\startup_ldf\app.ldf":226 Failed to find global symbol 'start' needed for absolute placement.

Can anyone explain this to me?

 

If I do not remove the startup files from the LDF, I can compile (after modifying the LDF to include all the  sections I need). However, I get this warning:

[Warning li2131] "..\system\startup_ldf\app.ldf":305 Input section(s) of incompatible init qualifier detected in the output section 'L1_code_cache'

In the "linker_log.xml" file, it says: The following input section(s) have no init qualifier: (list of ALL the object files).

Any help with that please?

 

Thanks in advance.

Outcomes