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.

Code Sourcery vs Yocto



Hi All,

From customer

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

Can any of you give me insight into when TI will move to Yocto?  When will you be moving away from the CodeSourcery tools?

 

Just wondering what a ballpark roadmap is so I can get up to speed on my end.  I've been following it but haven't had a chance to get into it as deep as I would like to yet.

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

Thank you,

Adam

  • Adam,

     

    Great questions.  Starting with SDK 5.02, AM37x (including Beagleboard-xM support), AM35x, AM180x now use the gcc4.3.3 toolchain.  We are in the middle of our 4Q SDK development cycle now looking at gcc4.5 by the end of this year.  Stay tuned on this as we continue to work out the kinks.  We are also engaged with Yocto Project and are working to provide a solution based on this in the 1Q time frame.  Stay tuned.  :)

     

     

     

     

  • Adam,

    Looks like Kevin gave you the key information.  If you are particularly interested in the Yocto Project, you can try out their reference BSP for the BeagleBoard-xM that is available from the Yocto Project today.  I've done some limited reviews of it and we haven't quite aligned on the approach, so you'll find that the BSP is a bit different in meta-ti.  Meta-ti is the repository with preliminary work on building BSP support for oe-core and the Yocto Project beyond what you'll find in the reference platform BSPs.

    Discussion regarding meta-ti will be done at https://lists.yoctoproject.org/listinfo/meta-ti.  Currently, meta-ti is tested with the Angstrom distribution (http://git.angstrom-distribution.org/cgi-bin/cgit.cgi/meta-texasinstruments/tree/README), but testing with the Yocto Project reference distro (Poky) and Arago (http://arago-project.org) will come soon and will give you early code drops ahead of the official OE-core/Yocto-based SDKs to be released in roughly 1Q.

    Regards,
    Jason