• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Subscribers 100 subscribers
  • Views 532 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.

mixing EZSDK and Arago

Joel Keller
Expert 1305 points

Hi,

For our product we have been using the EZSDK, which has worked well and seems to be the best supported 'SDK' for Davinci 8148 development.  Now we need lots of additional software which is not included in EZSDK, so I have been building the Arago distribution.  My current plan is as follows:

1) Build a base arago filesystem, which will provide the majority of the usermode software we need

2) build EZSDK components (uboot, linux kernel, drivers, video components, etc..) and 'make install' these in to the arago-built filesystem


This seems to be working, however I'm concerned about potential mismatches and other subtle problems that could occur when doing mix.  Is it important that the usermode software (including glibc) from the Arago project is built against the actual kernel headers that I am using from EZSDK?  Or is it okay if I just ensure the Arago build uses kernel headers of the same kernel version as my EZSDK?  

I don't have a lot of filesystem-building experience, so I am looking for advice/best practices.

I'd appreciate any advice, or ideas on how to use both EZSDK and Arago.

Thanks,

Joel

  • 0
    Expert 2030 points

    What compiler are you using? If it is codesourcery lite (CSL), I see no issues as EZSDK kernel is built using this toolchain. If not, please see this post to build user mode software using  CSL toolchain.

    RV
     

  • 0
    Expert 1305 points

    Just in case anyone reads this post in the future:

    We have had good results using u-boot, Linux (kernel), OMX & other TI firmware & modules (syslink) from the EZSDK paired with a filesystem built from the Arago project.  Up to this point we've had no issues with this mix.

  • 0 in reply to Joel Keller
    Intellectual 540 points

    We are also doing this, except we are using the RDK. We have been extracting packages we need from the arago bitbake tree, and then setting up so we can compile them standalone. It has worked well for us, though some of the arago packages have complex interdependencies.

  • 0 in reply to Brett Kuehner
    Intellectual 465 points

    We have a base Arago system but apply many newer packages as well as the TI provided Graphics SDK and EZSDK as updates occur.

    When a new release of the EZSDK appears, we make sure to find/create recipes for each component and apply any patches provided as part of the EZSDK.  Similarly with the Graphics SDK.

    With this approach we get a root file system image produced by Bitbake which contains all of the latest packages, compiled with our gcc toolchain, that works well.