• State Resolved
  • Locked Locked
  • Replies 8 replies
  • Subscribers 101 subscribers
  • Views 1092 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

Creating a custom platform without the Wizard

Clement FR
Genius 4750 points


Hello everyone,

Even though the Platform Wizard is a great tool, we'd like to not use it in our workflow (to not let the end developper modify too much things he shouldn't)

How do you build/modify/create platforms without the wizard ?

Thank you
Regards,
Clément

  • 0
    TI__Mastermind 37985 points

    Clément,
    I would recommend finding a TI platform package that is the most similar to your platform, copying that platform package, renaming it, and then adding the changes you need. After that, you'll have to rebuild the platform package using 'xdc' command. I can give you more details along the way.

    What's your board and the device?

    Also, I don't really understand why would the end developer see any difference between a platform created by the Wizard, and a manually created platform.

  • 0 in reply to Sasha Slijepcevic
    Guru 13202 points

    I do agree with Sasha's comment: how does your end developer see the difference between wizard generated platform and hacked one?

    In any case, platform is set of text files, so whenever you give your partner that package, still he can hack inside. If you'd like to make his life harder, just do not share .project/.cproject you used to build your platform. This way your package would be same hard to hack as TI's ones.

  • 0 in reply to Victor Kazmirenko
    Genius 4750 points

    Thanks,

    I'll try with a colleague what you said Sasha, after I come back from vacation.

    We may put our own graphical interface between the files and the developper. He still could let's say define the size of DDR3 memory but not change where the code is placed for example.

    The end developper wouldn't see the files at all.

    Regards,
    Clément

  • 0 in reply to Clement FR
    Guru 19890 points

    Hi Clément,

    This is just for your information.
    I think Sasha's suggestion is first, but there is a second option :
    You can edit your platform information with text editor by creating your own config.bld. 

    http://rtsc.eclipse.org/docs-tip/Using_Targets_and_Platforms

    Best Regards,
    Kawada 

  • 0 in reply to Naoki Kawada
    Genius 4750 points

    Hi Kawada,

    We'll try your suggestion if we don't succeed with Sasha's suggestion first.

    Thank you for your input.

    Regards,

    Clément

  • 0 in reply to Sasha Slijepcevic
    Prodigy 10 points

    Hi Sasha,

    I'm currently working with Clément on creating my own platform.

    You advise in your post to find a TI platform package then copy and rename it before rebuilding it using 'xdc', that sounds clear for me.
    However i'm getting confused when looking for my platform package, that is to say in my folder "package" i have lots of files (for instance package.bld.xml, package.xdc.dep, package.xdc.inc, package_ti.platform.evmc6678l.c, ti.platform.evmc6678l.ccs, ti.platform.evmc6678l.sch and many others), i know many of those files are automatically generated.
    Could you please be more specific on the "TI platform package the most similar to your platform"?

    Thank you.

    Best regards,

    Morgan

  • 0 in reply to Morgan Guinois1
    TI__Mastermind 37985 points

    Morgan,
    ideally you would start from a platform that's using the same device as your platform. If you are using C6678, you would want to use evm6678 as a starting point. If there is no platform with the same device, you can start from any C66xx or any C64+ platform. The advantage of starting from a similar platform is that you'll have to change fewer things, but it's not really a big deal. In most cases, you'll just change the memory addresses and device names.

    Once you select and copy a platform, you should first rename it so that the directory path corresponds to your platform package name. Let's say you decide to copy ti.platforms.evm6678. You can copy the platform to platforms/my6678. Now, you should change the package name in package.xdc from 'ti.platforms.evm6678' to 'platforms.my6678'. Now, when you run 'xdc clean' all generated files will be deleted and you'll be left only with source files. Now you can change them according to your needs, and then run 'xdc' to build the package so you can use it.

  • 0 in reply to Sasha Slijepcevic
    Genius 4750 points

    Sasha,

    I work with Morgan on this.

    What you suggested works. We had a bit of trouble at first because where we took evm6678 there was no package.bld or .mak files.

    If anyone else reads this, here's what we finally did.

    Create a custom platform with CCS wizard.
    Copy the generated folder, rename it,  modify package.xdc with the new name of the platform, modify the platform file as needed.
    then run 'xdc clean' (most files are removed) then "xdc release".

    Then you can use the new platform for new projects. You need to add the folder address  path when the new project wizard window asks you to choose a platform with a dropdown list.

    Thank you for your time Sasha.

    Morgan and Clement.