Can I split my .bss section into two different memories while building a library so that I can keep the non-time critical code on external memory?
You can use linker tricks to segregate critical code from libraries into separate sections so you can link them to internal memory instead of external memory. In terms of swapping code back and forth that is certainly doable. If you are intending to do overlays then the linker supports the UNION directive which allows you to have two different pieces of code execute from same address (at different times) while being loaded to distinct addresses. You can also use the table feature of the linker to generate copy tables that can then be used by a C program to access the start and sizes of the different sections to swap them in and out of internal memory. The latest run time support library even has a copy table routine that supports this. There is a secondary bootloading application note on C6000 devices that has example code and discussion of many of these topics.
Related Questions
- My organization does not have federal exemption (or is exempt under a different Internal Revenue Code section). How do I obtain tax-exempt status for California?
- Since all homes must meet the requirements of the Manitoba Building Code, what makes an R-2000 Home different?
- When did section 511.1.2 of the Florida building code become effective statewide?
