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

How to customize the sysBios

Andy Yin
Genius 9390 points
Other Parts Discussed in Thread: SYSBIOS

Hi Experts,

Below are some questions on how to reduce the sysBios size and improve the performance. Besides the user guide, could u pls feel free to give any more suggestions? Thank u so much.

1. it seems a lot of library we need include if we have a *.cfg file, are these library are all necessary or we can remove some of these? 

2. how to make the BIOS more efficient? I mean maybe some code and data can be moved into DDR because it runs infrequently, and some critical code and data we can put it into L2. But the problem is we don’t know how to distinguish code and data in the BIOS.

3. about the code size and data size of BIOS6, do we have some ideal to reduce the whole size of BIOS?

 Many Thanks & Best Regards,

Andy

  • 0
    TI__Mastermind 20805 points

    Andy Yin said:

    1. it seems a lot of library we need include if we have a *.cfg file, are these library are all necessary or we can remove some of these? 

    No.  But you should not need to.  Only the libraries that are needed are added to the generated linker .cmd file.  And the linker only links the required functions into the final executable.  We use compiler option to put every function into a separate subsection of .text which allows the linker to only pull in the minimum set of functions.  Functions and code that is not referenced by your app (or indirectly by another function that is referenced by your app) will not be linked in.

    Andy Yin said:

    2. how to make the BIOS more efficient? I mean maybe some code and data can be moved into DDR because it runs infrequently, and some critical code and data we can put it into L2. But the problem is we don’t know how to distinguish code and data in the BIOS.

    See http://processors.wiki.ti.com/index.php/SYS/BIOS_FAQs#3_Placing_SYS.2FBIOS_code_in_different_memory_segments

    Andy Yin said:

    3. about the code size and data size of BIOS6, do we have some ideal to reduce the whole size of BIOS?

    Check appendix D of the SYS/BIOS User's Guide and also the size benchmarks as provided via link in the release notes.   Which device are you using?  What is your size goal?