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.

many problems with CCS4

Hi,

 

I am trying to start using ccs4+dsp/bios 6 instead of ccs3+dsp/bios5.33. Right now, nothing seems to make sense:

 

- I created a test project for F28335, and used the Memory example. Also selected the ezdsp28335 platform and C28_float target. I did not touch anything, but it will not even link properly. It complains that most memory ranges are overlapping with existing ranges. And looking into the files, I see a "linker.cmd", and the 28335_RAM_lnk.cmd.  After deleting the 28335_RAM_lnk.cmd, it finally linked.

- I want to run from flash. this requires custom cmd files with different load and run locations. How can I achieve this? For example. the .vecs section is defined in the linker.cmd. How can I overwrite this?

  • Hello,

    Regarding the first issue: It is a common issue when importing CCS 3.3 BIOS projects into CCSv4. CCS now automatically handles generated files during project-build. This wasn't always the case in CCS 3.3, so you needed to explicitly include them. In v4, if you still explicitly include them, you'll get such errors as you described.

    For the second question, see section 7.10 of: http://focus.ti.com/lit/ug/spru186q/spru186q.pdf

    Thanks

    ki

  • Sorry, I meant section 7.9.

    ki

  • This guide is probably more useful since it is for C28x: http://focus.ti.com/lit/ug/spru513c/spru513c.pdf

    However the content is still the same as for the other guide. And it is still section 7.9.

    Thanks

    ki

  • For the first issue, I did not import from a 3.3 project. It was a completely new project, using the new CCS project wizard... I keeps adding the 28335_RAM_lnk.cmd

    I did as described in section 7.9. I created a cmd file in the main project. But the problem is that the linker still takes the information from the linker.cmd generated in the rtsc configuration project. So for example:

    - the linker.cmd contains the automatically generated line: .vecs: load >> PIEVECT PAGE 1

    -I add in my flash.cmd file: .vecs: load = FLASH, run = PIEVECT, LOAD_START(_hwi_vec_loadstart), LOAD_END(_hwi_vec_loadend), LOAD_SIZE(_hwi_vec_loadsize), RUN_START(_hwi_vec_runstart)  

    The linker ends up with 2 .vecs sections, none of them doing the right thing (load address in flash, and run at the regular pievect address)

  • Ah right. Instead of creating your own cmd file, I think you need to specify it in your tcf file under the MEM object properties. Just a guess. You may want to look at the DSP/BIOS documentation for confirmation and more information.

    For C2000 a cmd file is automatically specified for you. But perhaps we should not pull one in if a DSP/BIOS project is specified... I will note this issue.

    Thanks

    ki

  • My above comment was in regards to BIOS 5. In BIOS 6 it is a cfg file I believe. Otherwise I'm not too familiar with BIOS 6. Sorry.

  • I was able to do everything easily in bios 5/ccs3.3 for a long time. My problem is with ccs4 and it is very hard to find any specific documentation.

    I think my question can be summarized as: How can I set up my project parameters to run a program from flash with ccs4 and dsp/bios6 using the rtsc tools?

  • I stumbled in the rtsc docs on something that led me to add the following lines in my .cfg file:

     

    var sectionVecs = new Program.SectionSpec;
    sectionVecs.runSegment="PIEVECT";
    sectionVecs.loadSegment="FLASH";
    Program.sectMap[".vecs"]=sectionVecs;

     

    Seems that it finally worked and generated a proper linker.cmd file. However, i still do not know how to get the load address from my UserInit function.Am I on the right track?

     

  • Have you visited the main RTSC wiki page? It is the main source of RTSC related material. There is also a forum dedicated to RTSC there which RTSC experts monitor. I'd suggest posting any RTSC related questions there.

    Thanks

    ki