This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

OMAP-L137, MBX, Linker cmd

I'm trying to get my CCS project transferred over to a codec server build.

in a .cmd file on the Windows box, there is a line "_MBX_collect = MBX_collect;"

Since I'm linking two projects (a library and a regular project), I need the name with the _MBX prefix. If I copy the .cmd file into the directory, will the make use it?

If not, how do I get the equivalent info into the codec build?

Similarly, I have several libraries I'll need to include. Do I just put the files in the lib directory? or in the top level directory? Will they automatically be included in the build? Finally, I'm not sure I need them yet, but I have lots of .h62 and .s62. Do I copy those over? will they be auto-included or do I need to change the Makefile?

 

  • Okay, so no reply to that. Here's something else. There is a main.c created after the server package wizard runs. I've edited it to add my globals that are used by some background tasks and the codec. I've also added the files that contain the task functions for the new background tasks. I've found a ".cdb" file that seems to have been created by the wizard or possibly some make. (I didn't create it or copy it from my Windows' box.) It has TSK_idle stuff in it. I'd like to add my TSK_collect and TSK_process_data to it, but I suspect that I shouldn't edit it directly. What do I edit to add tasks to it? That is, what file is the input to  the .cdb creation?

  • The BIOS .tcf script is the source file (that ultimately generates the .cdb).  You can add static TSK's to that, or just TSK_create() them in your main() fxn if that's easier.

    Chris