locating STS objects in L3 memory

  GROUP:
  {
    host_accessed_data_sect
  } > HOST_ACCESSED_RAM

  GROUP:
  {
    .log_output_section: 
    {
      .\Debug\wally2_appcfg.obj(.LOG_status$buf)
    }
    .sts_output_section: 
    {
      .\Debug\wally2_appcfg.obj(.sts)
    }
    tx_fir_data_sect
  } > L3_CBA_RAM

HOST_ACCESSED_RAM = L2; L3_CBA_RAM = L3
I confirmed again this morning that with this setting, CCS IDE will not get the STS stats.  The LOG seems to work - 
messages are output to the message log, but on the statistics view, nothing updates.

Now, after more investigation, I can get it to work.  The issue seems to be whether it's relocated in the linker file
or the tcf file. In the tcf file, I have to use this command: 

bios.STS.OBJMEMSEG = prog.get("L3_CBA_RAM");

And I cannot do anything in the linker file.  It seems to be the only way it works.  How come the STS memory 
section cannot be relocated via a linker file?  For LOG objects it seems to work fine.

Also, I can't use both the tcf command and linker command.  What I want is to be able to place STS objects in L3
and use the linker file to place this section relative to other memory sections I'm putting in
L3 (hence the need for the GROUP directive).
So in the above linker file snippet, I need to remove the .sts_output_section.  This creates kind of another problem.  
I don't know how to direct the build where to place the STS code in L3.  It seems to place it at the end of used L3,
but what if I want to place it elsewhere?

LOG objects seem to have so such restrictions.  I can use the .log_output_sect and it will work.  
I don't even need a corresponding line in the tcf file:

/*bios.LOG.instance("LOG_status").bufSeg = prog.get("HOST_ACCESSED_RAM");*/