• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Subscribers 55 subscribers
  • Views 889 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.

creating output section .bios:.near without SECTIONS specification

Shiras Pallikkara
Intellectual 445 points

I am getting a warning while building my project. The warning is " warning: creating output section .bios:.near without SECTIONS specification". From the map file, this section is as below

.bios:.near

* 0 000db140 000005e0

000db140 00000220 bios.a64 : mem_free.o64 (.bios:.near)

000db360 00000200 : mem_allo.o64 (.bios:.near)

000db560 000000c0 : mem_init.o64 (.bios:.near)

000db620 000000a0 : mem_vall.o64 (.bios:.near)

000db6c0 00000060 : sys_erro.o64 (.bios:.near)

All the object files in this section are from the bios.a64 library. I need these object files to be included under .bios output section. What should i do to include .bios:.near section under .bios section. As .bios is DSP code section and is configured using cbd file, .bios definition is already there in the generated linker command file. If i write

.bios: {} > ISRAM
{
    * (.bios:.near) 

} in my custom linker file, it will throw a warning " multiple definitions of SECTION named '.bios'"

Is there a provision to append .bios:.near section to the already defined .bios definition, instead of redefining, in my custom linker file.?

  • 0
    TI__Mastermind 24340 points

    What version of DSP/BIOS are you using?

    What are your compiler and linker options? (at Build options..)

  • 0 in reply to Mariana
    Intellectual 445 points

    I am building the DSP Application Project for C6415 Processor on CCS Ver.2.20.03. The code gen toolset version used is 4.32 and the DSP BIOS Ver. used is 4.60.50.

    I know that i am working on old versions. The project is currently linked by a Visual Linker rcp file. I have to try out linking the same project using text linker command file, in the same build environment. Once this is done, i am planning to upgrade the build environment and try the build again.

    Compiler Options:

    -qq -o3 -fr"..\..\..\obj\acqlocrfi\tr" -ft"..\..\..\obj\acqlocrfi\tr" -i"../../../include" -i"." -d"CHIP_6415" -d"JUPITER2" -d"_JUPITER_" -d"DUMP" -mi1 -ml3 -mv6400

    Linker Options:

    -q -ar -c -m"shiras.map" -w -x -i"..\..\..\target\lib"

  • 0 in reply to Shiras Pallikkara
    TI__Mastermind 24340 points

     

    This seems like a very old bug related to the use of  -ar and -w options at the linker. The bug is corrected in the newest version of DSP/BIOS, so the solution is to upgrade to 5.x or later. You can try not using -ar if you can, but I'm not sure if the warning will go away.

  • 0 in reply to Mariana
    Intellectual 445 points

    Thanks Mariana..

    If i replace -ar option with just -a, then the warning will go away as well as the .bios:.near will come under .bios.

    But i could get my binary working with -ar option and with the warning persisiting on build.