Platform inheritance in new platform wizard

Victor Kazmirenko

Hello!

In my company we are developing custom board with C6670. It is different from EVM at least in having just single DDR3 memory chip. So to proceed with further development I guess I have to define my own platform package. I am using the most recent tools so far. These are CCS 5.4 and XDCtools 3.25.00.48. Demo provided in help refers to CCS 4, so my steps are somewhat different.

I invoke new platform wizard from File/New/Other menu. Then I follow steps in demo, give a name to the package, select folder, family and device itself.

At step 2 the demo suggest to import closest possible platform. The wizard offers me just single choice: ti.platforms.evm6614. As far as I can see from product folder, 6614 though shares many features of 6670 is quite different from it. So I'd rather import settings for 6670 evaluation module. However, as I mentioned, I have just singe option. Should I worry about that? Is there any method to refer evm6670 instead?

over 12 years ago

0 Sasha Slijepcevic over 12 years ago

TI__Mastermind 37985 points

I replicated the problem, and while I don't know the cause yet it seems that the difference in the memory map between these two platforms is very minimal. When you import evm6614, you only need to adjust the base address of DDR3 from 0xA000000 to 0x8000000, and you will get the same settings as if you imported evm6670.

0 Victor Kazmirenko over 12 years ago in reply to Sasha Slijepcevic

Guru 13202 points

Hello, Sasha,

Thank you for your suggestion. I will try this way first. Don't you think, that limiting choice of platforms to inherit to just one is a bug? What is interesting, when I tried to create yet another platform for c6670, I saw my previously created custom platform among choices for import.

0 Sasha Slijepcevic over 12 years ago in reply to Victor Kazmirenko

TI__Mastermind 37985 points

If you try to create a new platform based on the 6670 device, you should definitely be able to import evm6670. It is a bug and I filed it here:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=409620

0 Victor Kazmirenko over 12 years ago in reply to Sasha Slijepcevic

Guru 13202 points

Hello,

Thank you for support. Will monitor when solution becomes available.

0 Sasha Slijepcevic over 12 years ago in reply to Victor Kazmirenko

TI__Mastermind 37985 points

A heavy handed workaround would be to remove the platforms ti.platforms.arm, ti.platforms.arp32 and ti.platforms.c6000 from xdctools/packages, unless of course you are using any of these platforms.

0 Victor Kazmirenko over 12 years ago in reply to Sasha Slijepcevic

Guru 13202 points

Hello,

Thank you for suggestion. As to my environment, we will use DM8147 and C6670. They do not fall in mentioned categories. We also have some legacy on C6414/C6416, but that would not use SYS/BIOS, so it seams safe to me to delete those folders until better solution comes.

However, I do not confirm it helps. I have deleted 3 mentioned folders, started new CCS session. When I run new platform wizard, still I see only 6614 and my custom platform as possible parents.

0 Sasha Slijepcevic over 12 years ago in reply to Victor Kazmirenko

TI__Mastermind 37985 points

I am sorry, I was working in a different debugging environment where the workaround I posted fixes the problem. A workaround that worked for me in a standard CCS environment is little bit more involved and it includes manually changing files in your CCS installation. I haven't tested the workaround much, but I'll post it here anyway just in case you still want to try it.
1. open the file plugin.xml in the directory eclipse\plugins\org.eclipse.rtsc.xdctools.product_3.25.00.48, and delete 'rtscPlatform' XML elements for the three invalid platforms.
2. close CCS
3. open the command window and cd into the directory eclipse of your CCS installation
4. type 'eclipse.exe -clean'. This will start CCS and remove cached versions of plugins.xml files.
5. close CCS opened from the command line in step 4.
6. start CCS normally and try the Platform Wizard again.

0 Victor Kazmirenko over 12 years ago in reply to Sasha Slijepcevic

Guru 13202 points

Hello!

Thank you for your time.

I do confirm that above recipe does work around the issue. Now ti.platforms.evm6670 is suggested in the first place.

Rather than delete entries in XML one may comment them out with "" sequences.

Processors

Processors forum

Platform inheritance in new platform wizard