Hi there,
I have some problems with setting up my development environment consisting of CCS v5.3.0.00090 and MCSDK v2.1.2.5 on my Windows Pro (SP1) 64 Bit system. I use the TMDSEVM6678LE as evaluation platform. The antivirus was always disabled during installaiton procedure of both CCS and MCSDK.
Here some background info’s what I have done so far:
- First, I installed CCS v5.3 followed by the MCSDK v2.1.2 with its default settings (regarding paths, etc.) for C6000 multicore devices. After installation and restarting CCS the IDE discovered all, (it seems so) installed modules from MCSDK without any error messages. Afterwards, I tried to run an example project on my EVM. After hitting the compilation button I immediately got some error messages. These messages said that some products that are utilized by the example project are missing / unrecognized and have to be installed. In addition to those missing products (such as “com.ti.biosmcsdk, com.ti.biosmcsdk.pdk.C6678L and com.ti.rtsc.NDK”) I further had some trouble with the drivers of my Blackhawk (XDS560v2) emulator which were provided with the EVM DVD. Since nothing worked so far (after my try and error installation approach) I started to read the getting started guides. I started with the MCSDK 2.1 getting started guide and found my first mistake. The installation path. The getting started guide recommends to use “C:\Program Files\Texas Instruments” as the installation path and not the default installation path suggested by CCS.
- Secondly, I uninstalled the complete development environment with all LIBs and cleared all registry entries and made my system completely free from TI’s software and started the installation process again. This time I followed the installation instructions, stated in the MCSDK getting started guide, step by step. Following this instructions and reading further articles in the Processors-Wiki I found my second mistake. A little note informed me NOT to use the emulator drivers provided with the EVM-DVD, because they are already integrated in CCS v5.1 and higher. Unfortunately, the “READ_ME_FIRST.txt” (Date: November 13, 2012), which also comes with the EVM-DVD, says (in section IV) I have to install the provided emulation pack. So, I have simply overwritten the already installed emulation drivers (that were actually newer than that provided with the DVD). That was the reason for my emulator connection problems. After finishing the current CCS installation I skipped point 5 and 6 of the READ_ME_FIRST.txt and continued with the MCSDK installation. The path of the MCSDK installation was also redirected to “C:\Program Files\Texas Instruments”, as recommended inside the getting started guide. After finishing and restarting CCS, it, again, discovered the new installed products/modules without any error messages (I thought so far). Unfortunately, I have not realized the little exclamation mark inside the product icon at this time. This warning had informed me, that the product (e.g. PDK, EDMA3, DSPLIB, etc.), which comes with the latest available MCSDKv2.1.2.5 version is not designed for the latest available CCSv5.3 version. (See attached figure). But, as mentioned above, I have not realized this little exclamation mark and continued with importing an example project. This attempt ended with same error message as described above. Namely with the missing products error message.
- Thirdly, I found a getting started of the CCS and started to read. After some lines I found a note that says “It is not recommended to use “C:\Program Files\Texas Instruments” as installation path”. Ok, now I was totally confused. Further reading told me to disable the UAC of Windows 7 to avoid additional permission problems. This sounded plausible to me, so I cleaned up my system again (Uninstall CCS and MCSDK and clean registry) and restarted installation procedure. I think I don’t have to mention that this attempt was comparable unsuccessful as the two mentioned above. So please, could you tell me what installation path to choose for CCSv5.3 and MCSDKv2.1.2.5 on a Windows 7 Pro 64 Bit system, since both getting started guides recommend different paths for different reasons.
- With the third installation approach I started to look more into detail and finally recognized the small exclamation marks in the icons when I checked the RTSC products (Window->Preferences->Code Composer Studio->RTSC->Products). Therefore, I decided to go back from CCSv5.3 to CCSv5.2. My though was, maybe v5.2 is already designed for the latest available MCSDK! So I started my fourth installation approach, but this time with CCSv5.2.1.00018. MCSDK was still the version v2.1.2.5. After finishing installation process CCS was finally able to discover all installed product without any errors and now also without any exclamation marks. Connecting to the emulator was also possible. I continued with the import of the example project. But, after hitting the compile button I got another error messages. This time the used compiler was too old for compiling the example project (see figure). So I started a software update (from Help->Check for Updates menu) and selected the latest provided compiler. After updating the compiler I still received the same error message because the provided compiler form the update menu was version v6.9 and not the required v7.4. I searched again the forums for possible reasons and found that compiler versions v7.xx are only available with CCSv5.3 and above and v6.xx are limited to CCSv5.2 and below. I don’t know whether that is true or not, but also this information was plausible to me and I started updating my CCSv5.2 to CCSv5.3 with Help->Check for Update menu. After finishing the update and restarting CCS it does not discovered new products again (that was plausible to me). But, after opening the RTSC products overview to see the discovered tools, all already discovered product, which were provided with the MCSDKv2.1.2.5, were marked with an red cross icon. In addition to that the product name was like MCSDK or PDK was replaced by the statement “Unknown Product” (Unfortunately, I don’t have a screenshot of that scenario). After pressing the “Restore Defaults” button all unknown product (all provided with MCSDKv2.1.2.5) were deleted form the discovered tools list. The current state is: I do not have any problems with the compiler version (since that is now v7.4.1) anymore but CCS is again unable to compile the example project due to the missing products.
So my question is, are there some knwon compatibility issues with CCSv5.3 and MCSDKv2.1.2.5 in conjunction with Windows7 Pro (SP1) 64 bit systems or the chosen installation path? If there are some, is there a workaround to get the lattest available toolsets (CCS and MCSDK) to work properly together?
Now, I spent nearly 4 days with trouble shooting and getting the IDEs operational and I really do not know what else I could try.
Therefore I urgently need your help to fix this problem.
Kind regards,
Viktor
