• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 99 subscribers
  • Views 598 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.

Custom RTSC Definition for C28335

Jan Stefan
Intellectual 275 points

I am new to BIOS 6 and using CCS 4.2, XDCTools 3.20.05.76, and BIOS 6.31.00.18  to program a F28335 DSP on an eZdsp28335 evaluation board. I am dealing primarily with TI documentation rather than open source docs. (I previously used the DSP/BIOS 2 for another TI Chip)

I selected the built-in ti.platform.ezdsp28335 definition in CCS as my platform and can build and run BIOS demo programs. The definition has the code running from RAM.

I need to make more RTSC definitions for an ezdsp FLASH based usage, as well as my custom hardware board in both a RAM and FLASH based models. I also did not want to modify and perhaps corrupt the existing definition.

As a first baby step, I wanted to make a new RTSC definition that is equivalent to the built-in ezdsp28335 definition. I made a custom repository for my definitions. Using the CCS Wizard, I created a new  RTSC definition, imported the existing ezdsp28335 definition, and saved the result in my custom repository.  

After building with the new definition, I could not run the BIOS demo! The link map was different between the new and existing definitions. The existing definition link map had a .bootCodeSection while the new definition link map did not.

Subsequent investigation showed that while the import did copy the memory map from the existing definition, there was additional script information that was not imported.

My next attempt was to manually copy the existing definition from the XDCTools repository to my repository in the hope that I could then modify it with the Wizard. That did not work either, the path information (ti.platforms.ezdsp28335) seems to be deeply embedded in the file names and data.

My main questions are:

1. Do I need to know all the custom low level detail that seems to have been put into the existing ezdsp definition?

2. Is there a better tool than the CCS Wizard to duplicate a definition?

Any additional advice would be useful.

TIA

Jan

.

  • 0
    TI__Expert 3550 points

    Hello Jan,

    This problem arises because the ti.platforms.ezdsp28335 platform defines some specific boot sections that is not comprehended by the Platform Wizard. We are investigating means for resolving this problem. Meanwhile you can be unblocked by adding the following code to your RTSC configuration script file (*.cfg) of your project.

    var    Boot = xdc.useModule('ti.catalog.c2800.init.Boot');

    Boot.disableWatchdog = true;

    Boot.configurePll = true;

    Boot.pllcrDIV = 10;

    Boot.pllstsDIVSEL = 2;

    Boot.enableEzdspXintfConfig = true;

    Program.sectMap[Boot.bootCodeSection] = new Program.SectionSpec();

    Program.sectMap[Boot.bootCodeSection].loadSegment = "L47SARAM";

    Now you should be able to use the platform generated by the wizard to create a program that is equivalent to the one created with the  ti.platforms.ezdsp28335 platform. You can now define your own  memory sections  (for flash on your board) using the wizard. You may also want to review http://rtsc.eclipse.org/docs-tip/Memory_Management for an overview of memory management in RTSC.

     

    Regards

    Amit

  • 0 in reply to AmitMookerjee
    Intellectual 275 points

    Thank You Amit !!

    I feel like I have been reading Quick Start documents for a month, Your prompt and accurate information gave me some hope that I will eventually learn this system.

    Thanks again.

    Jan