Undefined SYS/BIOS symbol build errors

Is this a project that moved from BIOS 5.x to SYSBIOS 6.x?  I ask because I see that some of the missing functions are legacy APIs.

First, you shoudn't have to update your compiler/linker path's with bios or sysbios because this should be added to the path automatically given that you chosed a particular BIOS version for the build.  So my first recommendation is removed those additional paths that you added to the compiler/linker search paths.

Judah

Thanks for the response.

I got the same errors even if I remove those additional compiler and linker include/search paths (which is why I tried adding those paths).

Yes, this project is being migrated from DSP/BIOS 5.x to SYS/BIOS 6.x. I presume these functions used are backward compatible and should work, correct? I'm referring to Appendix A of SPRAAS7E Migrating a DSP/BIOS 5 Application to SYS/BIOS 6 which contains list of unsupported APIs and these do not seem to appear there.

My source files contain all the new SYS/BIOS 6.x header files followed by the old DSP/BIOs 5.x header files as suggested in section 4 of the SPRAAS7E document.

Any other ideas what I should be looking for?

BRY,

Yes, the functions are backwards compatible.

You should only need SYSBIOS 6.x header files if you are planning on using SYSBIOS 6.x APIs, otherwise, you don't need them.

In your source files, if you did not update the #include <> of the bios header files then you do need to add a path into your compiler settings.

For example: The BIOS 5.x way is something like:

    #include <clk.h>

The BIOS 6.x way is:

    #include <ti/bios/clk.h>

If your #include looks like the BIOS 5.x way then you need to add to the compiler path.  See Section 3.3 of SPRAAS7E for more info.

You should not need to update the linker path as this should be done for you.

Judah

BRY,

Is your *.cfg file still using the BIOS 5.x statements or are you now using BIOS 6.x in the .cfg file?

Can you try adding this to your .cfg file and see if this error  "ti_sysbios_BIOS_start__E" goes away?

     xdc.useModule('ti.sysbios.BIOS');

If it goes away it means that your .cfg file is not including the right modules.

If you were coming from BIOS 5.x and you following the migrating doc, I wouldn't expect you to see these linking errors.

Judah

Yes the problem goes away after adding that line. Thanks Judah!

I could not migrate my tconf file using the xs command line tool (the tconf file was created for ). So the cfg file was created afresh and the platform used is the ti.platforms.evm6678.

However, I am now having a run time problem. It looks like execution stops in the BIOS_start() specifically in the ti_sysbios_knl_Task_startup().

Here is my code snippet:

   Error_init(&eb);

   /* Create 1 task with priority 15 */
   Task_Params_init(&taskParams);
   taskParams.stackSize = sizeof(MyApp_TaskStack);
   taskParams.priority = 14;

   tskHandle = Task_create((Task_FuncPtr)MyApp_MainTask, &taskParams, &eb);
   CSDASSERT(tskHandle != NULL);

   /* Start the BIOS */
   BIOS_start(); /** Code stops executing here **/

The MyApp_MainTask does not get spawned and I am unable to read any DSP variables or core registers or memory via the emulator.
Can someone help? Is there anything I need to look into in the cfg file?

I didn't get the part of your question that went off screen.

A very useful tool for debuggin is ROV.  See Bios_Getting_Started_Guide.pdf section 1.7 Running a SYS/BIOS Project for more information.

So you put a breakpoint in your MyApp_MainTask and you never get there?  Are there any other threads in your system or an ISR that is coming in?

I would also check your stacks (Hwi and Task stacks) to make sure you are not blowing them.  ROV can give details on these.

Judah