• State
  • Locked Locked
  • Replies 4 replies
  • Subscribers 99 subscribers
  • Views 454 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

TCF file for C6748 on OMAP L-138 EVM

DanB57495
Expert 1340 points

Hi Guys,

I am new to DSP/BIOS. I am using a C6748 SOM  (128Mbyte DDR RAM) on a OMAP L138 EVM evaluation kit from LogicPD. I am trying to port some code that was targeted for a C6713 on a totally different system. The code uses  MEM_alloc, TSK_create  and LOG functions and other DSP/BIOS-related API calls. Is there a TCF file readily available that has the basic configuration already setup for the C6748 SOM that would be suitable for this type of setup or at least as a place to start?

Thanks in advance.

 

Dan.

  • 0
    TI__Expert 4095 points

    Maybe start with one of the BIOS 5 examples? Maybe the 'stairstep' example if you're using LOG?

    Chris

     

  • 0 in reply to Chris McCormick
    Expert 1340 points

    Hi,

    Thanks for the suggestion. There doen't appear to be a platform for L138 or C6748 in the stairstep example, however when I started fresh creating a new TCF-file there was platform called ti.platforms.evm6748 which indicated the right amount of memory so that may be my best bet.

    The only document I have about setting these files up is Bios_Tconf_User_Guide.pdf from May 2006. Is there anything more detailed explaining more about how to use the settings on the interface or how to incorporate linker files etc.?

    For example I  tried a default configuration TCF with the evm6748 platform. The linker file is auto-generated and of course I have a seperate linker file for the actual program's requirements including loading libraries etc. I assume we don't want to edit the auto-generated linker file so is it OK for both these linker files to co-exist assuming they don't step on eachother?

    I also noticed that the auto-generated linker assigns memory segments to itself to a memory secton  that is too small (IRAM). Again I assume we don't want to manually re-assign the section in the auto-generated linker file so how do we change it in the graphical setup program?

    Thanks in advance for any help!

     

    Dan.

     

  • 0 in reply to DanB57495
    TI__Mastermind 45025 points

    Hi Dan,

    Which version of BIOS are you using?

    The evm6748 platform is what you want, so you got that part correct.

    Did you see the document titled

    "TMS320 DSP/BIOS v5.41User’s Guide"?

    In this document, the following section has more info on linker command files:

    5.1.3 Defining Segments in Your Own Linker Command File

    You are also correct in that you don't want to edit the auto generated linker command file; the typical use case is to define your own linker command file with references/includes the auto generated one:

    -l <auto-generated-linker>.cmd

    Regarding memory settings, it's perfectly ok to re-arrange the memory sections into different memory segments.  You can do this in the Gconf GUI that should come up in CCS when you double click the TCF file.  In the GUI, you can navigate to the MEM module:

    system -> global settings -> MEM - Memory Section Manager

    If you right click on MEM and bring up its properties, you'll be able to place the various sections into different MEM segments.

    Steve

     

  • 0 in reply to Steven Connell
    Expert 1340 points

    Hi Steve,

     

    I am using DSP/BIOS 5.33.05.

    The version of TMS320 DSP/BIOS User's guide I had was from 2004. I just grabbed the on you mentioned (2009) which is much more current and far more informative and helpful so far. Thank you!

    At the moment the code I am porting uses a base library that dynamically allocates all memory. On a C6748, it currently needs the L3_CBA_RAM, IRAM and DDR to hold it all (I didn't touch the L1 cache). I am going throught the manual to see how to confgure the memory to allow it to work. Since the DDR RAM needs to be initialized I am trying to figure out how I will accomplish this? Even if I use a GEL initially to get the DDR started this will be OK for debugging, but I 'm wondering how DDR will work when loaded from a NOR-flash? I saw there was an option to "Call User Init Function" which could be used for initialization, but will that be of use when loading from a flash?

    Thanks in advance for your help.

    Dan.