CCSv6 unable to create a custom RTSC platform

here is the snapshot of the issue.

Regards,

Nitish

Nitish,
I can't see the pictures you posted. Do you see them when looking at your posts? I'll see if I can replicate the problem in the meantime.

Sorry for the previous post here is the picture which i posted.

Regards,

Nitish

Nitish,
I reproduced the problem and found a bug in the PlatformWizard - https://bugs.eclipse.org/bugs/show_bug.cgi?id=433961. Unfortunately, there is no easy workaround the changes are spread among multiple files.
Sometimes next week we'll have the fix available, but I don't know yet in which form. I'll post more in this thread as soon as I know.

Here is how to install a new version of XDCtools that contains the fix for the Platform Wizard bug. The new version is an engineering release, and in a month or so there should be an "official" release of XDCtools 3.30.02, which will contain this same fix for the bug.

Go to Help->Install New Software... Choose the repository displayed in the Work With dropdown list. If you don't have that repository in the list, add it using the Add... button. After you select that repository, you'll see two versions of XDCtools Core and Grace. Unless you work with MSP430 devices, leave the Grace check box unchecked. One version of XDCtools is for Linux and one is for Windows. Select each of them and click on More... to find out which one is for your OS. A new window will open and the title of that new window will contain either 'linux' or 'win32'.

Check the box for the version that works on your OS and click Next, and Next again. Accept the license agreement and click on Finish, and then restart CCS after the installation.

After the restart, go to Window->Preferences->Code Composer Studio->RTSC and select SYS/BIOS 6.40, or TI_RTOS for C6000, whichever you are using.

Now, when you try using the Platform Wizard, it should work as before.

Hello Sasha

You are correct in that the create platform wizard  now runs and allows selection of a family and device on the first screen and also allows importing an existing platform on the second screen.  However after making the necessary changes and clicking finish the wizard crashes while trying to generate the binary files from the created text (xml, etc) files.  The error message is "can't create session manager: can't find a JVM; the environment variable XDCTOOLS_JAVA_HOME is set but does not seem to be a directory containing a valid 32 bit Java runtime environment."

This error message is misleading in that XDCTOOLS_JAVA_HOME is definitely set correctly (its value is "C:\Program Fiiles\Java\jre7", this is the default Java install folder on Windows and Java is there) and, in any case, the platform wizard always seems to generate this message for any fault.  For example the CCS v5.4 platform wizard always crashed with this same error message if you clicked finish without importing, and then modifying, an existing platform.

In fact this does not really matter too much any more.  I am using CCS v6 because I have a product to develop which needs to actually ship at some stage.  After struggling with CCS v6 for over a week now I have decided that TI have shipped it well before it was finished.  Although the introduction of TI RTOS has caused a major change in the layout of SYS/BIOS and how parts of it, particularly instrumentation but also the network development kit, work none of the documentation or examples have been updated to match.  In fact none of the examples really seem to work, paticularly since most of them demonstration SYS/BIOS functionality that has changed yet the examples have not been updated.  This is especially frustrating since at this time TI RTOS has no relevance to the 5000 or 6000 family DSP processors that I wish to develop for.  Until TI have actually finished CCS v6 I will switch back to CCS v5, at least I know I will be able to finish my firmware with that version.

Regards

Phil Grasso

Hello Sasha

Thank you for your reply.  The requirement to restart CCS after setting the environment variable is definitely correct although this was not the cause of the my problem since the error message included the correctly set value for XDCTOOLS_JAVA_HOME.  However I do notice a difference in your set up and how I had my system configured.  On my computer the environment variable was already set to the operating system Java installation under the "C:\Program Files" folder (possible by the earlier install of CCS v5.4, I am not really sure) so I just left it there.  On the other hand you are using the version of Java installed as part of Eclipse under the CCS install.  I doubt if the actual Java version is the problem but I suspect that the space in the path "C:\Program Files\Java\jre" is causing the problem.  I have noticed that a lot of open source tools, particularly those targetting Linux as well as Windows, do not really support spaces in file and path names properly.

As for the version of CCS I will stay with 5.5 until after I have completed my current project.  I can't have problems with the tools delaying things any further.

Thanks

Phil

Philip Grasso said:

fter struggling with CCS v6 for over a week now I have decided that TI have shipped it well before it was finished.

I totally agree. Even with the newest versions I'm running below, I've spent two weeks and it still doesn't work,..... and yet I'm trying this a month later than Philip.  :o(

CCSv6.0.0.00190, C6472, XDC 3.30.1.25_core, IPC 3.20.0.06, NDK 2.23.2.03, SYSBIOS 6.40.1.15, UIA 2.0.0.28 and XDAIS 7.10.0.06, CGT 7.4.8

Cheers

I performed the steps to make the Platform Wizard able to access what it needs to populate the entries in Create New Platform dialog, but once done, that platform is inaccessible by editing the platform. So are all my other platforms. That dialog is blank where it's supposed to list available platforms.

Just a simple issue with paths? Almost certainly. Knowing that doesn't do me any good, though.

I'm currently editing my platform on CCSv5.5 to fine-tune my memory section assignments and building on CCSv6. I'd rather not have to do that, and given the other problems people are reporting w/v6, maybe I should just plan on letting other customers iron out the bugs and use v5.5 for now.

William,
What's the version of XDCtools you are using? When you edit your platforms, what's the path shown for "Platform Package Repository" and what's the name of the platform you are editing?
I have a platform package tisb.my28335 located in C:/temp/platforms/tisb/my28335. My Platform Package Repository is C:/temp/platforms, and that path and the platform name (with '.' replaced by '/') form the path to the platform location. When any other path is specified for Platform Package Repository, that platform is not visible.

Right now, I have to use XDCTools 3.25.3.72, because selecting 3.30.2.35_core_eng in the Project CCS General RTSC tab generates an error "None of the currently selected products supplied the Target...." and none of my platforms appear.

The target is ti.targets.elf.C66.

The platform is a C6678 platform of my own design called "M2HF". Surprisingly, the platform does appear here and I can use it with XDC 3.25.3.72, so editing the platform on v5.5 and using it here appears to work.

My browse path for the Edit Platform dialog is D:\vws\bz_ccsv6_20140514\spDsp\6678\M2HF_Platform_Configuration\RTSC Platform

... which is the same path that works correctly on v5.5. There are two projects there. Well, there are supposed to be 3, if I include the project I tried and failed to create under v6. I know that dialog is fussy on which directory needs to be specified. Has is gotten even fussier in v6?

What changed is that XDCtools 3.30 does not deliver device files that are used in platforms. The error message that you are seeing is basically asking you to select a SYS/BIOS version in your list of products. There is a screenshot in one of my previous posts in this thread where SYS/BIOS 6.40 is selected. You should do the same, and that should take care of that error message assuming you are using SYS/BIOS 6.40.

To temporarily work arround with this bug,just switch CCS perspective from "CCS Edit" to "CCS Debug".

Maybe it can help you temporarily, and wish TI to post a completely solution for it.