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.

Root File System - Angstrom

Hi All,

I am developing DM816x base on DVR RDK. After some digging, I found that the provided (from Udworks) is build from arago. My project require fair a amount of external package and cross compile seems to be a tedious work. I am attract to use Angstrom file system as it support opkg package management system.

I have try to recompile whole DVR RDK (including QT) using angstrom compiler but upon execuation of DVR RDK, the program just stop half way. No error is giving out.

My question would be:

1. Is it feasible to recompile DVR RDK using angstrom tool-chain?

2.When I recompile using angstrom tool-chain, do I also require to compile for linux kernel using angstrom-tool-chain? So far I am using original TI-kernel(compiled with Code Sourcery) and is working fine. When I boot using angstrom compiled kernel, I saw some kernel panic message.

3.Is there any better option that  I can use out there instead of Angstrom?

Thank you very much.

  • We've taken a hybrid approach. I use the OpenEmbedded/Arago stuff to download and build all of the packages the first time (via bitbake). Tthen I move the source for the packages that I care about into my own repository, so I don't have to depend on bitbake for production builds. I use the CodeSourcery toolchain that TI recommends for the RDK, and using that all the packages extracted from the OE/Arago tree have built fine so far.

  • Hi,

    Thank you for your advice. But I have some question as below.

    1. Which command to use under bitbake to create a version that build all of the packages? (I am using MACHINE=c6a816x-evm bitbake arago-base-image) or we have to tweak the config files inside bitbake?

    2. Is the files *.ipk is the package source you are referring to?

    Thanks.

  • I've used the following commands to build various images(you'll probably need to change the "MACHINE" env variable to match your board):

    MACHINE=dm814x-evm bitbake arago-console-image
    MACHINE=dm814x-evm bitbake arago-gst-image
    MACHINE=dm814x-evm bitbake arago-qte-image

    You can also look in oe/arago/recipes for individual package recipes that you can bitbake. For example:
    bitbake curl
    bitbake thhtpd

    2) Once you've built a package,you can find the build directory in:
    oe/arago-tmp/work/armv5te-none-linux-gnueabi

    I copy them out of there and into my tree. They should generally build standalone, though you may have dependencies between things like SSL librarys that you have to sort out.

    The .ipk files can be handy for a quick install into a filesystem, since you can use opkg to install them directly on your 81xx board.

  • Hi Brett,

    Thanks a lot, this method works fine on package building.

    My task require me to install some python module(example: greenlet) using python 'easy_install'. Now I am achieving this by by running installation on target and during installation (on the dm8168 board), it is looking for compiler (running on dm816x). I had tried to build a native compiler (on dm8168) using

    MACHINE=c6a816x-evm ./arago-bitbake/bin/bitbake gcc-4.3.3(since codesourcery is using 4.3.3) or
    MACHINE=c6a816x-evm ./arago-bitbake/bin/bitbake task-sdk-native

    but bump into error. The error file for building gcc-4.3.3 is here.0636.config.log

    Thus, I would like to know:

    1. Is there any other way to install python module - like building in on host instead of doing it in target.

    2. Have you try/success building native compiler on target(dm8168).

    Thank you very much.

  • I'm afraid I can't help with either of those. I have not tried to cross-compile with python. I did find this link, maybe ti will help (but I haven't tried it):

    http://randomsplat.com/id5-cross-compiling-python-for-embedded-linux.html

     

    And I have built gdb for the EVM, but I never tried to build gcc. It looks like there might be bitbake recipes for native gcc in OpenEmbedded, but I have no idea which one to use or if it will build the entire toolchain.