Which version of MCSDK is compatible with CCSv5.1?

Actually, when you install MCSDK, it will install the required CCS version. Having said that any new release of MCSDK will work for CCSv5.1.

Thanks,

Arun.

Arun, If I understand you correctly you're recommending to install a specific MCSDK and go with the CCS version included rather than trying to figure out a good combination of these two?

Regards, Marten

Arun, it seems like we're not understanding eachother. Next to the "download MCSDK installation" button (on http://software-dl.ti.com/sdoemb/sdoemb_public_sw/bios_mcsdk/latest/index_FDS.html) it says: Note: Please install Code Composer Studio before installing BIOS-MCSDK package. Plus, the first thing the installer queries is where the CCS installation directory is located.

?

Regards, Marten

Hello Arun

I am having the same problem. I need to establish a tool-chain baseline. All development is done on a restricted network with no internet connection, so I need to find a combination of install-files that work together.

I tried your suggested method and only installed  bios_mcsdk_02_00_03_15_setupwin32.exe on a clean system. The installation program failed with the following message:

---------------------------

Error in startup script

---------------------------

Error in action ExecuteScript: no files matched glob pattern "ccs_base*"

    while executing

"$obj execute"

    (procedure "::InstallJammer::ExecuteActions" line 65)

    invoked from within

"::InstallJammer::ExecuteActions "Setup Actions""

    (procedure "::InstallJammer::ParseCommandLineArguments" line 138)

    invoked from within

"::InstallJammer::ParseCommandLineArguments $::argv"

    (procedure "::InstallJammer::InitInstall" line 60)

    invoked from within

"::InstallJammer::InitInstall"

    (file "/installkitvfs/main.tcl" line 28821)

No version of CCS was installed.

Hi Ham,

The CCS is not installed by installing the MCSDK by itself, you must also install CCS separately.  I think Arun was saying that if you install from the CD that came with the EVM, it will install both components.  Having said that, we are still on CCSv5.3 since CCS5.1 production has not been released yet.  I know that there are some folks using CCS5.1RC, but it is safer to wait if you can.  The CCS can be downloaded at:

http://processors.wiki.ti.com/index.php/Download_CCS

And licenses that allow use with the EVMs and install instructions are at:

http://processors.wiki.ti.com/index.php/C66x

look under Keystone EVM Info section.

Regards,

Travis

BTW,  the latest MCSDK can be installed at:

http://software-dl.ti.com/sdoemb/sdoemb_public_sw/bios_mcsdk/latest/index_FDS.html

It is separate, as are all the SDK from the different product groups, because they are developed and maintained by separate groups and have different maintenance schedules.   The MCSDK2.x is only for the high performance multicore products.  MCSDK will install some components that may already exist.  The key is to use the components tested with the MCSDK examples listed in the release notes.  C66x only supports BIOS6, BIOS5 is installed by CCS to support legacy devices.

Regards,

Travis

As Travis mentioned, I meant the link below.

http://software-dl.ti.com/sdoemb/sdoemb_public_sw/bios_mcsdk/latest/index_FDS.html

It specifies which CCS to be compatible with the release.

Thanks,

Arun.

Hello!

The versions on the disk that was in the EVM6678LE box are Bios_mcsdk_02_00_00 Beta2 (Build 2.0.0.9), and CCS 5.03.00023. We can’t use that beta version of the sdk because of problems with the implementation. Another problem is that the online documentation is not in sync with that version. We updated to MCSDK 2.00.01.12 and that solved our initial problems. (Later we have updated MCSDK to version 2.00.03.15 as well).

So why bother about CCS then?

There are some bugs that we are hoping to get rid of, for example the ability to link source files via drag and drop into the project (not working in 5.0.3 but works in 5.1). When the Release Candidate version of 5.1 turned up we decided to give it a try. But it is causing us a lot of problems, the worst thing is;

If the build fails during the xdc-tool phase the build dialog never goes away and the cancel button has no effect. The only option is to use the task manager (twice) and kill CCS and the build dialog. That might be a good motivator for the developers to write code that compiles on the first try, but maybe not….

This is the reason for asking for a “good” combination of tools. I understand that 5.1 is in pre production status right now, but I am only asking for advice on what versions I should try.

Hi Ham,

Try the latest MCSDK version, it should work with the CCSv5.1

Thanks,

Arun.