• State TI Thinks Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 98 subscribers
  • Views 163 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.

BEAGLEBOARD-X15: SDK development platform

mustafa.gonul
Intellectual 535 points
Part Number: BEAGLEBOARD-X15

Hi,

I am Processor SDK Linux for AM57x on Beagleboard-x15. Currently, working on Ubuntu is suggested and supported. I would like to give support to other distros and I would like to ask which is the best way to do that.

Kind Regards,

Mustafa

  • 0
    TI__Mastermind 30526 points

    Mustafa,

    I'm afraid this is a very complex question in my mind. The Dev Toolchain included with the SDK that is used to build everything is probably the trickiest part. However, package dependencies and other challenges will surely arise. 

    Probably the best recommendation I can make is to pick another distro and start the process of getting the SDK up and running on it and document the gaps that are encountered.

    I hope this is helpful. Thank you.

  • 0 in reply to RonB
    Intellectual 535 points

    Hi Ron,

    I am currently using Arch Linux and installed the SDK and build any kind of problem with that on my side. The thing is I would like to automatize the things I have done on my side and share it with the community. There are several repositories at https://git.ti.com/cgit/ . I would like to know how I can contribute these repositories, there are several repositories, which ones should I use for this task. I need a small introduction for the contribution.

    Kind regards,

    Mustafa

  • 0 in reply to mustafa.gonul
    TI__Mastermind 30526 points

    Hi Mustafa,

    I'm sorry, we don't usually take community patches directly on our trees as this is our released and tested software. It would be best to work with the appropriate communities directly and get code added there (upstream) and we would pick it up as we pull the latest releases. This would be true of U-Boot, Linux, Yocto/OE, Arago, or any of the many other open source components that we integrate. Each of these should have information on how to contribute.

    Thank you, it is great to see someone interested in giving back to the open source community.