• State Resolved
  • Locked Locked
  • Replies 1 reply
  • Subscribers 96 subscribers
  • Views 1169 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.

Manually define sections for DSP/BIOS

Markus Glasl
Prodigy 140 points


Hello,

I try to manually define the code sections for DSP/BIOS (.bios, .sysinit, .hwi, .rtdx_text, .hwi_vec) in our user linker command script. As I know from post http://e2e.ti.com/support/embedded/f/355/p/94447/328678.aspx#328678 I have to put the include of the generated linker command file after my user defined linker command file and copy the section definitions from generated file to my file. That works great for .bios, .sysinit, .hwi and .rtdx_text but not for .hwi_vec.

.hwi_vec is defined as follows in the generated file:

.hwi_vec: {
                    *(.hwi_vec)
                } align = 0x400, RUN_START(HWI_A_VECS) > IRAM
If I delete the "RUN_START" command (because linker says that redefinition of symbols is not allowed) the following linker warning comes:

"DSPLibcfg.cmd", line 221: warning: section specifier matches no sections;
   potential matches are consumed by section specifier at
   "C:\P4Workspaces\POST\Stromrichterleitgeraet\Basis_ASG_Source\Branch0\DSP\Fi
   rmware\DSPLibTestProject\DSPLib.cmd", line 64
What does that mean?

What I try do do is, find out and define symbols for start address and size of each section. I want to do this with the LOAD_START and LOAD_SIZE commands. It's working for all sections except .hwi_vec.

I'm using DSP/BIOS 5.41.10.36 and CGT v7.2.2 and CCS 3.3

Regards

Christian

  • 0
    TI__Guru**** 251300 points

    Markus Glasl said:
    "DSPLibcfg.cmd", line 221: warning: section specifier matches no sections;
       potential matches are consumed by section specifier at
       "C:\P4Workspaces\POST\Stromrichterleitgeraet\Basis_ASG_Source\Branch0\DSP\Fi
       rmware\DSPLibTestProject\DSPLib.cmd", line 64
    What does that mean?

    It means that the section specifier on line 64 of DSPLib.cmd forms some output section that uses, at a minimum, all of the input sections named .hwi_vec.  Thus, when these lines from DSPLibcfg.cmd come along, there are no .hwi_vec input sections left to do anything with.  Thus, these .hwi_vec lines in DSPLibcfg.cmd have no effect.

    At the level of the linker, this is what is occuring.  I'm sorry, but I don't know BIOS well enough to tell you a good way to fix this issue.

    Thanks and regards,

    -George