In the spru007h.pdf document. at the page of 48.
"If you want to change the memory configuration, you should do it in the
Platform.tci file you use, not in the application’s TCF script or with the
DSP/BIOS Configuration Tool"
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.
In the spru007h.pdf document. at the page of 48.
"If you want to change the memory configuration, you should do it in the
Platform.tci file you use, not in the application’s TCF script or with the
DSP/BIOS Configuration Tool"
KuangRen said:"If you want to change the memory configuration, you should do it in the
Platform.tci file you use, not in the application’s TCF script or with the
DSP/BIOS Configuration Tool"
What does it mean the sentence above?
What this is suggesting is that if you want to change the memory map of a particular platform, where a platform is considered to be a particular board (for example evmDM6446), that you change it at the platform level. This is more convention than anything else, it would allow you to use the same Platform.tci file in other projects for the same board, than they would also have the proper memory map for that particular board.
KuangRen said:what's the difference of the platform.tci and application's TCF?
The Platform.tci file is defining settings that are specific to the board, whereas the application's tcf file is defining settings that are specific to the application. You can think of the tci file as the BIOS equivalent of a configuration header file (similar to a C header file), it contains generic definitions and settings you can include in various projects. If you look in your tcf file, you should actually see it referencing the tci file, when this is done it inherits the properties of the tci file (just like a .h file included in a .c file would do).