This option enables automatic allocation of sections to areas split by the memory area shared with the FLEXIBLE APPLICATION ACCELERATOR (FAA).
Automatic allocation of sections is not split by the memory area shared with the FLEXIBLE APPLICATION ACCELERATOR (FAA).
With STRIDE_DSP_MEMORY_AREA specified, sections are allocated in sequence up to just before the FLEXIBLE APPLICATION ACCELERATOR (FAA) memory area, and the remaining sections are allocated as another section from after the FLEXIBLE APPLICATION ACCELERATOR (FAA) memory area. |
Suppose that file1.obj, file2.obj, file3.obj, and file4.obj each contain data_section, as shown below.
When the device is configured with RAM-A size 2.5 K and RAM-B size 2.5 K, automatic allocation of sections by using the auto_section_layout option is as follows.
The RAM is split to RAM-A (size 2.5 K) and RAM-B (size 2.5 K), and data_section (size 4 K) of the combined file1.obj, file2.obj, file3.obj, and file4.obj cannot be allocated as shown below.
When STRIDE_DSP_MEMORY_AREA is specified, data_section (size 2 K) of file1.obj and file2.obj is allocated to RAM-A (size 2.5 K), and then data_section (size 2 K) of file3.obj and file4.obj is allocated to RAM-B (size 2.5 K), as shown below.
At this time, the other section allocated after the split has the following section name.
sss : Section name before the split
To allocate sections to areas split by the FLEXIBLE APPLICATION ACCELERATOR (FAA) memory area, describe as: |
> rlink a.obj b.obj -device=dr5f10y14.dvf -auto_section_layout -dsp_memory_area -stride_dsp_memory_area |
When auto_section_layout is not specified, a warning will be output and the specification will be ignored. |