CCS/LINUXSDK-OMAPL138: RTSC platform not recognized in SYS-BIOS project

Rushina Trivedi

Intellectual 270 points

Part Number: LINUXSDK-OMAPL138
Other Parts Discussed in Thread: OMAPL138, OMAP-L138

Tool/software: Code Composer Studio

Hi,

I go through the page

https://e2e.ti.com/support/development_tools/code_composer_studio/f/81/p/666156/2454868

as I got warning after compilation as below.

warning #10247-D: creating output section "IRAM" without a SECTIONS specification

As in the above link, it is specified that somewhere #pragma is used for IRAM. Actually I am using #pragma DATA_SECTION ("IRAM"); in my .cpp file for the array which I want to put in IRAM to do faster process compare to the data in DDR. So, I want put some arrays in IRAM section. It is also showing usage of IRAM memory in .map file.Then How could I avoid the warning #10247-D. What should I do for proper use of IRAM for my data arrays?

Thanks,

Rushina.

over 7 years ago

0 ToddMullanix over 7 years ago

TI__Guru* 96960 points

Hi Rushina,

What version of SYS/BIOS are you using? Which core is this happening on? Can you attach your .cfg file?

Todd

0 Rushina Trivedi over 7 years ago in reply to ToddMullanix

Intellectual 270 points

Hi Todd,

Thanks for the reply. Information about my project is as below.

I have a custom board with

1) MityDspl-138F module (with FPGA) which uses OMAPL-138.

2) I have built Virtual machine (Linux) with MityDSP Critical_Link_Unified_VM_14-04_04-2017.ova file from critical link.

3) I have build my project with CCS 6.1.3 in linux virtual machine.

3) I am using platform.tci file from critical link for my DSP6748 project.

4) I am using DSP/BIOS version 5.42.2.10.

I am attaching platform.tci and generated .tcf file for my project for your reference. you need these two files or any other *.cfg file?

Please let me know if you need any other inputs.

Thanks,

Rushina.configuration.rar

0 ToddMullanix over 7 years ago in reply to Rushina Trivedi

TI__Guru* 96960 points

Thanks. Can you attach the mapfile also?

0 Sasha Slijepcevic over 7 years ago

TI__Mastermind 37985 points

Rushina,
the first thing you should do is to rename the section defined in the pragma directives to some other name. It would make it easier to tell apart a section from a memory object. I made the same recommendation in the linked thread so you can look there for an explanation.

So, let say you have
#pragma DATA_SECTION ("IRAM_section")
in your source file.
All you need to do is to add another linker command file to your project, let's call it link.cmd, with a following content:
SECTION { IRAM_section > IRAM }

That should take care of that warning.

0 Rushina Trivedi over 7 years ago in reply to Sasha Slijepcevic

Intellectual 270 points

Thanks for your Reply.

It solved my problem. No more warnings about IRAM.

I have one more query regarding to on chip Shared RAM in OMAPL138. Which is located at 0x80000000 to 0x8001 FFFF. Is it possible to use it for arrays declared in .cpp file like IRAM ? i.e just before the array. If possible then How to use it? I tried to use it same way as IRAM by creating SHARAM_section > L3_CBA_RAM in link.cmd file, it ends up in using IRAM memory instead of shared RAM memory as I can see it in generated .map file. And if not possible that way, How could I make use of shared RAM for my arrays in the program? I am attaching link.cmd and .map file for your reference.

Thanks,

Rushina.

map_and_cmd.rar

0 Sasha Slijepcevic over 7 years ago in reply to Rushina Trivedi

TI__Mastermind 37985 points

Rushina,
I don't know much about memory configuration on OMAP-L138. I would recommend posting that question in the OMAP-L13x forum - e2e.ti.com/.../42

There should be someone there who can answer.

Code Composer Studio™︎

Code Composer Studio forum

CCS/LINUXSDK-OMAPL138: RTSC platform not recognized in SYS-BIOS project