RTOS/TMS320F28075: Linker error: #10008-D cannot find file

You can explicitly place items (wild cards work also). For example (I split FLASH into FLASH and FLASH2)

.text:_ti_sysbios_family_c28_Hwi_* : > FLASH2 PAGE = 0
.text : > FLASH PAGE = 0

There might be a slicker way to send the whole obj somewhere, but we'd need to check with the compiler folks for that. I'll ask one of them to chime in on this thread.

Todd

I have some suggestions on how you can get greater control of input sections coming from libraries, and direct them to specific memory ranges.

For my suggestions to make sense, you need a little background.  Please read the first part of the wiki article Linker Command File Primer about input sections and output sections.

You also need to be familiar with how to name input sections from libraries like  sysbios.a64FP.  For that, please see the section titled Specifying Library or Archive Members as Input to Output Sections in the C28x assembly language tools manual.  

I use the library sysbios.a64FP as an example.  The one you see in these examples may not be identical to the one you have.

To see what files are in the library, use the library archiver command with the option -t ...

$ ar2000 -t sysbios.a28FP

      SIZE   DATE                        FILE NAME
  --------   ------------------------    -----------------
    691945   Mon Sep 19 07:37:51 2016    mangled_ti.sysbios.family.c28.Hwi_config_lib.obj
     11317   Mon Sep 19 07:37:45 2016    family_c28_Hwi_asm_lib.obj
     11617   Mon Sep 19 07:37:45 2016    family_c28_Hwi_disp_asm_lib.obj
      1832   Mon Sep 19 07:37:45 2016    family_c28_IntrinsicsSupport_asm_lib.obj
      3031   Mon Sep 19 07:37:46 2016    family_c28_TaskSupport_asm_lib.obj

Based on that, you could create an output section like this ...

sysbios_text 
{
   --library=sysbios.a28FP<family_c28_Hwi_asm_lib.obj family_c28_Hwi_disp_asm_lib.obj>(.text)
} > FLASH2 PAGE=0

You can see the names of the input sections in the library with the object file display utility ofd2000, like this ...

$ ofd2000 -v --obj_display=none,sections sysbios.a28FP | grep text
    <2> ".text"
    <6> ".text:_ti_sysbios_knl_Task_yield__E__mangled__"
    <7> ".text:_ti_sysbios_knl_Task_unlockSched__E__mangled__"
    <8> ".text:_ti_sysbios_knl_Task_unblock__E__mangled__"
    <9> ".text:_ti_sysbios_knl_Task_unblockI__E__mangled__"
    <10> ".text:_ti_sysbios_knl_Task_stat__E__mangled__"
    <11> ".text:_ti_sysbios_knl_Task_startup__E__mangled__"
... and so on ...

With this information, you might decide to take advantage of the patterns in the input section names ...

sysbios_text 
{
   *(.text:_ti_sysbios_knl_Task_*)
   *(.text:_ti_sysbios_knl_Swi_*)
   /* and so on */
} > FLASH2 PAGE=0

For any one library, use one technique or the other.  Using both on the same library would quickly get confusing.

Thanks and regards,

-George