.o64P (.bios:.near) Should I put these sections in local memory?

William Bagshaw

I noticed lines like...

e01966c0 00000060 : mem_vall.o64P (.bios:.near)

in the map file for a 6457 build.

Is this implying that these sections are better off in local memory? How would I get these into local memory? Slightly confused by the colon. Happy to experiment with TCF changes or adding a custom linker script. I am familiar with both.

Thanks William.

over 10 years ago

Archaeologist over 10 years ago

TI__Guru* 84285 points

I don't have the answer to your larger question, but the colon is used to create subsections. You can think of .bios:.near as a subsection of .bios, or you can think of it as its own independent section. Subsections exist so that you can make fine-grained section placement.

William Bagshaw over 10 years ago in reply to Archaeologist

Prodigy 200 points

Do you know how to control sub sections in a linker script? I think I tried to treat it just as a section name and it did not work for me. For example wild card matching.

Archaeologist over 10 years ago in reply to William Bagshaw

TI__Guru* 84285 points

You should be able to use it either as a normal section name, or with wildcards. Could you show me an example of the linker command file placement specification that does not behave as you expected?

William Bagshaw over 10 years ago in reply to Archaeologist

Prodigy 200 points

I don't have what i tried before, I hope to try with these newly discovered sections. I see no harm in experimenting with moving them to local memory, unless we start to run short.

Code Composer Studio™︎

Code Composer Studio forum

.o64P (.bios:.near) Should I put these sections in local memory?