|
Re: how to generate a custom memory map for rtsc based project [message #635141 is a reply to message #635016] |
Mon, 25 October 2010 18:13 |
Sasha Slijepcevic Messages: 115 Registered: July 2009 |
Senior Member |
|
|
Since you are working in CCSv4, you have available two different techniques for defining platform instances. If you are using config.bld, you can use a parameter Build.platformTable ( http://www.sanb.design.ti.com/iliad/webhome/xdoc/xdc/bld/Bui ldEnvironment.html#platform.Table) to specify platform instance parameters. The path to your config.bld is entered in C/C++ Build->Tool Settings->Advanced Options->Build configuration file (-b) in your project build properties.
Here is a short guide how to specify platform parameters in config.bld: http://rtsc.eclipse.org/docs-tip/Using_Targets_and_Platforms #Defining_Platform_Instances_via_config.bld
In your case, Build.platformTable entry for your platform would look like this:
Build.platformTable['ti.platforms.evmDM365'] = {
...
customMemoryMap: [
["RAM1", {
name: "RAM1",
base: 0x8000,
len: 0x1000,
space: "code/data"
}],
["RAM2", {
name: "RAM2",
base: 0x9000,
len: 0x1000,
space: "code/data"
}],
etc,
]
};
In case, you can't use config.bld, there is another way of configuring platform instances described here:
http://rtsc.eclipse.org/docs-tip/Using_Targets_and_Platforms #Defining_Platform_Instances_via_a_RTSC_Module_Configuration _Parameter.
In that case, you would add 'customMemoryMap' specification to a file corresponding to Sim6x.xs in the example in the link.
As mentioned in the docs for customMemoryMap ( http://www.sanb.design.ti.com/iliad/webhome/xdoc/xdc/platfor m/IPlatform.html#custom.Memory.Map), the custom memory map has to fit in the physical memory available on the board.
Also, if you specify a custom memory map for a platform instance, you must specify the parameters 'dataMemory', 'codeMemory' and 'stackMemory'
http://www.sanb.design.ti.com/iliad/webhome/xdoc/xdc/platfor m/IPlatform.html#code.Memory. The purpose of these parameters is to define allocation of standard compiler sections. Since you are effectively deleting default memory object names referred to by these parameters, you have to set new values for them.
[Updated on: Mon, 25 October 2010 18:14] Report message to a moderator
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.09926 seconds