• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Subscribers 100 subscribers
  • Views 856 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

BIOS6 errors:(e.g. ti.bios.MEM : This module should be used BEFORE ti.sysbios.heaps.HeapMem)

Bin Zhou35352
Prodigy 700 points
Other Parts Discussed in Thread: SYSBIOS

I need to port DSP server from LEO(TNETV107x, with C64+) to Netra/Centaurus (with C674). Tools I'm using for Netra now is:

codec_engine_3_21_00_02_eng

 bios_6_31_00_06_eng

 ipc_1_22_00_10_eng

 xdctools_3_20_05_69_eng

 syslink_02_00_00_65_alpha2

TI_CGT_C6000_7.2.0B1

 

Since We used BIOS5 on LEO before and now BIOS6 on Netra, my server configurations have to be changed a lot, and I used configurations from codec_engine_3_21_00_02_eng\examples\ti\sdo\ce\examples\servers\all_codecs as examples. I'm not a DSP engineer and I'm not familiar with BIOS, so I just copied most things from CE sever example and removed other platforms support.

Now I got following errors and I don't know why. Can somebody help? I have attached my configuration related files to this post.

 

Thanks a lot,

Bin

 

error: ti.bios.MEM: "/vobs/dsps_gtippdk/ti/mas/ippdk/tools/bios_6_31_00_06_eng/packages/ti/bios/MEM.xs", line 271: ti.bios.MEM : This module should be used BEFORE ti.sysbios.heaps.HeapMem
error: ti.bios.TSK: "/vobs/dsps_gtippdk/ti/mas/ippdk/tools/bios_6_31_00_06_eng/packages/ti/bios/TSK.xs", line 60: ti.bios.TSK : This module should be used BEFORE ti.sysbios.knl.Task
error: ti.bios.TSK: "/vobs/dsps_gtippdk/ti/mas/ippdk/tools/bios_6_31_00_06_eng/packages/ti/bios/TSK.xs", line 65: ti.bios.TSK : This module should be used BEFORE ti.sysbios.BIOS
error: ti.bios.CLK: "/vobs/dsps_gtippdk/ti/mas/ippdk/tools/bios_6_31_00_06_eng/packages/ti/bios/CLK.xs", line 94: ti.bios.CLK : This module should be used BEFORE ti.sysbios.knl.Clock
error: ti.bios.CLK: "/vobs/dsps_gtippdk/ti/mas/ippdk/tools/bios_6_31_00_06_eng/packages/ti/bios/CLK.xs", line 99: ti.bios.CLK : This module should be used BEFORE ti.sysbios.BIOS
error: ti.bios.CLK: "/vobs/dsps_gtippdk/ti/mas/ippdk/tools/bios_6_31_00_06_eng/packages/ti/bios/CLK.xs", line 104: ti.bios.CLK : This module should be used BEFORE ti.sysbios.timers.dmtimer.Timer
error: ti.bios.CLK: "/vobs/dsps_gtippdk/ti/mas/ippdk/tools/bios_6_31_00_06_eng/packages/ti/bios/CLK.xs", line 109: ti.bios.CLK : This module should be used BEFORE xdc.runtime.Timestamp
error: ti.bios.CLK: "/vobs/dsps_gtippdk/ti/mas/ippdk/tools/bios_6_31_00_06_eng/packages/ti/bios/CLK.xs", line 114: ti.bios.CLK : This module should be used BEFORE ti.sysbios.family.c64p.TimestampProvider
error: ti.bios.SWI: "/vobs/dsps_gtippdk/ti/mas/ippdk/tools/bios_6_31_00_06_eng/packages/ti/bios/SWI.xs", line 62: ti.bios.SWI : This module should be used BEFORE ti.sysbios.knl.Swi
error: ti.bios.SWI: "/vobs/dsps_gtippdk/ti/mas/ippdk/tools/bios_6_31_00_06_eng/packages/ti/bios/SWI.xs", line 67: ti.bios.SWI : This module should be used BEFORE ti.sysbios.BIOS
error: ti.bios.GBL: "/vobs/dsps_gtippdk/ti/mas/ippdk/tools/bios_6_31_00_06_eng/packages/ti/bios/GBL.xs", line 67: ti.bios.GBL : This module should be used BEFORE ti.sysbios.family.c64p.Cache
error: ti.bios.GBL: "/vobs/dsps_gtippdk/ti/mas/ippdk/tools/bios_6_31_00_06_eng/packages/ti/bios/GBL.xs", line 71: ti.bios.GBL : This module should be used BEFORE ti.sysbios.BIOS
js: "/vobs/dsps_gtippdk/ti/mas/ippdk/tools/xdctools_3_20_05_69_eng/packages/xdc/cfg/Main.xs", line 116: Error: Configuration failed!


 

 

devnodeServer_cfg.zip
  • 0
    TI__Expert 4095 points

    Note sure if this is any help, but ti.bios.MEM is the legacy interface which allows you to use old BIOS 5 MEM API calls in your application and build it against BIOS 6. It maps the old APIs in MEM to the new ones in ti.sysbios.heaps.HeapMem.

    Do you know if you're explicitly using these legacy modules? If you are, then you probably need to pull them in earlier in your configuration.

    If not, then it's probably one of the products you're building against that's pulling them in (probably either syslink or codegen). In that case, you might need to reference those products in the right order in your .cfg script. I'm not familiar with syslink or codec engine, so I can't offer much insight there.

    Chris 

  • 0
    TI__Mastermind 18260 points

    I noticed that your devnodeServer.cfg potentially includes a config file that you haven't included in your .zip attachment:
    var file = new java.io.File("codecs.cfg");
    if (file.exists()) {
      utils.importFile("codecs.cfg");
    }

    Since I can't otherwise see how legacy BIOS 5 is being brought in to your build, I've got to believe it's in there.  Perhaps you need to just import that file earlier (as Chris noted), possibly importing it as the first step in devnodeServer.cfg.

    Regards,

    - Rob

  • 0 in reply to Robert Tivy
    TI__Mastermind 20805 points

    You should include the following line at the top of your .cfg before anything else:

    xdc.loadPackage('ti.bios.tconf');

    You might also find some useful info in the migration app note that describes steps and issues to migrate BIOS 5.x to BIOS 6.x.  This app note can be found via link in the product release notes.

    -Karl-

     

    Normal 0 false false false MicrosoftInternetExplorer4

  • 0 in reply to Karl Wechsler
    TI__Prodigy 700 points

    Thanks to all who answered my questions. I added xdc.loadPackage('ti.bios.tconf'); at the beginning of my devenodeServer.cfg and the errors disappeared. :-)

  • 0
    Prodigy 10 points

    Bin:

    If you are the same Bin Zhou that went to WVU, please drop me a line.

     

    I have been trying to locate you for sometime :-)

     

    Thanks

    Srini