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.

C6747: CCS v3.3 and v4.0 compatibility issues

Other Parts Discussed in Thread: TMS320C6747, OMAP-L137

Hi,

I am porting a legacy code for C6747. First I worked with CCS v4. The code built correctly, and I could run it in the C6747 Device Cycle Accurate Simulator. Now I have the OMAP-L137/TMS320C6747 Starter Kit, and am trying to run the code on the board.

Unfortunately, the Starter Kit comes with CCS v3.3, and that has prevented me from running the code on the board. I have tried two approaches; neither has worked so far.

Approach 1:

I tried to re-build the code with CCS v3.3, but the compiler complained about "unrecognized cregister name 'TSCL'". I specified the option as -mv6740, replaced the c6x.h with that in CCS v4, and defined the symbol _TMS320C6740, but I still have the same compiler error. Should I specify the target as C64xx?

Approach 2:

I built the code with CCS v4, then used CCS v3.3 to download the executable onto the board. That didn't succeed. CCS v3.3 popped up an error message: "File: ccs4_build.out does not match the target type, not loaded." This is a little surprising, as both CCS versions are configured to build and run as C674x platform.

I'll appreciate any ideas, suggestions, or insights that help me solve this problem.

 

Thanks,

-Robby

 

  • Robby,

    My recommendation is to download the latest CCSv4 and use it for your C6747 Starter Kit. As long as you are using the on-board emulator or any XDS100 emulator, you will not have to pay for a CCSv4 license. Since you already had the code built and working with the simulator, perhaps you can just use the same version of CCSv4 that you already have, but if it is CCSv4.0.x, I still recommend moving to CCSv4.1.x or the new CCSv4.2 RC1 (Release Candidate).

    Your build problems probably come from using different compiler versions, and going back to CCSv4 will let you get past that problem. You may have to re-install some libraries or just link to them from your CCSv4 workspace or project.

     

    If this answers your question, please click the  Verify Answer  button below. If not, please reply back with more information, such as CCS version numbers, compiler tools versions, and such.

  • Hi Randy,

    Thanks for your quick response.

    I'm using the evaluation CCS v4.1.3. I tried to make it talk to the board, no luck so far. Below is a description of what I did:

    1. Start a new target configuration, choose "XDS100v1 USB Emulator" and "TMS320C6747", and make the configuration active.

    2. Launch TI debugger. When it complained about a missing GEL file, copied the GEL file from CCS v3.3 into the CCS 4.1 folder. The debugger was launched successfully.

    3. Choose "Connect target", an error message popped up: "Error connecting to the target: Error 0x80002240/-600. Fatal Error during: Initialization, OCS, Control,"

    I guess that I'd need to install some USB JTAG driver into CCS v4, and looked it up at Spectrumdigital's website, but didn't find any. How can I solve this problem? 

     

    Thanks again,

    -Robby

  • Please check out the TI Wiki page on Common target configurations here. In the outline box, click on "Boards with XDS510USB Plus onboard emulator" or search for OMAPL137. This is the emulator you want to choose in your target configuration.

    Also, you want to choose the EVMC6747 so you get a GEL file associated with the DSP core. Choosing the TMS320C6747 does not give you the GEL file.

    See if this helps, and let us know either way, please.

  • Hi Randy, your suggestion really helped. Now I can run the code on the board from CCS v4.1.3.

    In retrospect, it shouldn't have been so difficult. The problem was, when I first installed CCS v4.1.3, I did a custom installation and deselected many components, including the XDS510 USB Emulator. Thus I didn't have many choices when I tried to configure a new target. Your suggestion reminded me of my short-cutting. I un-installed CCS v4.1.3,  then did a full re-installation, and everything was straightforward after that.

    Cheers,

    -Robby