• State Resolved
  • Locked Locked
  • Replies 9 replies
  • Subscribers 99 subscribers
  • Views 1713 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.

Arago - build root filesystem for kernel 2.6.32?

Michael Kagalenko
Prodigy 180 points
Other Parts Discussed in Thread: AM3517

Hello,

I have successfully downloaded and built Arago distribution for MACHINE=am3517-evm. using TI SDK compilers

My AM3517 system from Adlink came preinstalled with Linux 2.6.32 . Its root filesystem is likely to have been built with Arago project as well, ( telnetting to the unit displays Arago banner).

My problem is, current arago seems to be built for 2.6.16 kernel:

[linux-devkit]:~/SP-860/arago> file ./arago-tmp/work/armv7a-arago-linux-gnueabi/openssh-5.6p1-r9.0/openssh-5.6p1/sftp
./arago-tmp/work/armv7a-arago-linux-gnueabi/openssh-5.6p1-r9.0/openssh-5.6p1/sftp: ELF 32-bit LSB executable, ARM, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.16, not stripped
[linux-devkit]:~/SP-860/arago> file ./arago-tmp/work/armv5te-arago-linux-gnueabi/openssh-5.6p1-r9.0/openssh-5.6p1/sftp
./arago-tmp/work/armv5te-arago-linux-gnueabi/openssh-5.6p1-r9.0/openssh-5.6p1/sftp: ELF 32-bit LSB executable, ARM, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.16, not stripped

The question is, how do I build userland packages for kernel 2.6.32? Is there TI git repository where I could pull the right tag?

Thanks,

Michael

  • 0
    TI__Expert 5960 points

    Hi Michael,

    I'm far from an Arago expert, but I do use it on occasion.  This may not be the answer you are looking for, but you could build the TI base-sdk with the following recipe.

    arago/recipes/images/arago-base-tisdk-image.bb.  This should build the correct kernel version - 2.6.32, and will provide a prebuilt u-boot and kernel images.

  • 0 in reply to Jeff L
    Prodigy 180 points

    Hi, Jeff, thanks for your reply. Since I've learned about arago about a couple of weeks ago, your advice's plenty expert to me.

    Are you talking about main Arago repository (http://arago-project.org/git/), or AM-SDK (git://arago-project.org/git/projects/arago-amsdk.git) one?

    In my case, kernel and u-boot are preinstalled on the target, together with some custom drivers, so I don't want to change them. I'm just trying to add some packages, including, eventually, my own program. So I need the correct environment to build them

  • 0 in reply to Michael Kagalenko
    TI__Expert 5960 points

    Hi Michael,

    The repository is: 

    git://arago-project.org/git/arago.git - This one contains TI specific recipes.
    We use the repository above along with with git://arago-project.org/git/arago-oe-dev.git, which is a snapshot of  OpenEmbedded mainline to build our SDKs.
    The recipe mentioned earlier was the base SDK which is the most basic file system you need to get booted, but not much else. The recipe arago-tisdk-image.bb will build the SDK with all the current additional packages. From what I've read, it may be easier to add packages to the base filesystem than remove from the populated filesystem.
    This page is for a different platform, but provides information about setting up: http://www.arago-project.org/wiki/index.php/Setting_Up_Build_Environment
  • 0 in reply to Jeff L
    Prodigy 180 points

    I built 'master' tags from both "git://arago-project.org/git/arago.git,arago-oe-dev.git" and "git://arago-project.org/git/projects/arago-amsdk.git, arago-oe-dev.git"

    and they seem to build the kernel 2.6.31. At least, search of arago-tmp for any filename including 2.6.32 returns nothing

  • 0 in reply to Michael Kagalenko
    TI__Expert 5960 points

    Michael,

    2.6.31 is very old.  I'm not sure what is going on there. You should be using the "master" tag for both. Our arago expert is out this week but back next week.  I'm having my own problems building right now, sorry for the delay.  I hope to be back up on Monday.

  • 0 in reply to Jeff L
    Prodigy 180 points

    I am using the 'master' tag for "git://arago-project.org/git/arago.git,arago-oe-dev.git". Recipes for 2.6.32 are present in ./arago-oe-dev/recipes/linux/, ./arago/recipes/linux/, however they do not get built. After "bitbake arago-base-image" completes normally,  there're no 2.6.32 files created by build process:

    [linux-devkit]:~/SP-860/arago> find ./arago-tmp -name "*2.6.32*"
    [linux-devkit]:~/SP-860/arago> find ./arago-tmp -name "*2.6.31*"
    ./arago-tmp/pstage/angstromglibc/staging-linux-libc-headers-native-i686-linux_2.6.31-r6_i686-linux.ipk
    ./arago-tmp/deploy/glibc/ipk/armv7a/linux-libc-headers-dev_2.6.31-r10.6_armv7a.ipk
    ./arago-tmp/work/armv7a-arago-linux-gnueabi/external-toolchain-arago-1.0-r10/staging-pkg/deploy/glibc/ipk/armv7a/linux-libc-headers-dev_2.6.31-r10.6_armv7a.ipk
    ./arago-tmp/work/i686-linux/linux-libc-headers-native-2.6.31-r6
    ./arago-tmp/work/i686-linux/linux-libc-headers-native-2.6.31-r6/linux-2.6.31
    ./arago-tmp/work/i686-linux/linux-libc-headers-native-2.6.31-r6/staging-pkg/stamps/i686-linux/linux-libc-headers-native-2.6.31-r6.do_qa_configure
    ./arago-tmp/work/i686-linux/linux-libc-headers-native-2.6.31-r6/staging-pkg/stamps/i686-linux/linux-libc-headers-native-2.6.31-r6.do_install
    ./arago-tmp/work/i686-linux/linux-libc-headers-native-2.6.31-r6/staging-pkg/stamps/i686-linux/linux-libc-headers-native-2.6.31-r6.do_compile
    ./arago-tmp/work/i686-linux/linux-libc-headers-native-2.6.31-r6/staging-pkg/stamps/i686-linux/linux-libc-headers-native-2.6.31-r6.do_populate_sysroot
    ./arago-tmp/work/i686-linux/linux-libc-headers-native-2.6.31-r6/staging-pkg/stamps/i686-linux/linux-libc-headers-native-2.6.31-r6.do_qa_staging
    ./arago-tmp/work/i686-linux/linux-libc-headers-native-2.6.31-r6/staging-pkg/stamps/i686-linux/linux-libc-headers-native-2.6.31-r6.do_patch
    ./arago-tmp/work/i686-linux/linux-libc-headers-native-2.6.31-r6/staging-pkg/stamps/i686-linux/linux-libc-headers-native-2.6.31-r6.do_fetch
    ./arago-tmp/work/i686-linux/linux-libc-headers-native-2.6.31-r6/staging-pkg/stamps/i686-linux/linux-libc-headers-native-2.6.31-r6.do_package
    ./arago-tmp/work/i686-linux/linux-libc-headers-native-2.6.31-r6/staging-pkg/stamps/i686-linux/linux-libc-headers-native-2.6.31-r6.do_configure
    ./arago-tmp/work/i686-linux/linux-libc-headers-native-2.6.31-r6/staging-pkg/stamps/i686-linux/linux-libc-headers-native-2.6.31-r6.do_unpack
    ./arago-tmp/work/i686-linux/linux-libc-headers-native-2.6.31-r6/staging-pkg/stamps/i686-linux/linux-libc-headers-native-2.6.31-r6.do_setscene
    ./arago-tmp/work/i686-linux/linux-libc-headers-native-2.6.31-r6/staging-pkg/stamps/i686-linux/linux-libc-headers-native-2.6.31-r6.do_package_stage
    ./arago-tmp/work/i686-linux/linux-libc-headers-native-2.6.31-r6/staging-pkg/stamps/i686-linux/linux-libc-headers-native-2.6.31-r6.do_package_write
    ./arago-tmp/work/i686-linux/linux-libc-headers-native-2.6.31-r6/staging-pkg/stamps/i686-linux/linux-libc-headers-native-2.6.31-r6.do_create_srcipk
    ./arago-tmp/work/i686-linux/linux-libc-headers-native-2.6.31-r6/staging-pkg/stamps/i686-linux/linux-libc-headers-native-2.6.31-r6.do_package_write_ipk
    ./arago-tmp/stamps/i686-linux/linux-libc-headers-native-2.6.31-r6.do_qa_configure
    ./arago-tmp/stamps/i686-linux/linux-libc-headers-native-2.6.31-r6.do_install
    ./arago-tmp/stamps/i686-linux/linux-libc-headers-native-2.6.31-r6.do_compile
    ./arago-tmp/stamps/i686-linux/linux-libc-headers-native-2.6.31-r6.do_populate_sysroot
    ./arago-tmp/stamps/i686-linux/linux-libc-headers-native-2.6.31-r6.do_qa_staging
    ./arago-tmp/stamps/i686-linux/linux-libc-headers-native-2.6.31-r6.do_patch
    ./arago-tmp/stamps/i686-linux/linux-libc-headers-native-2.6.31-r6.do_fetch
    ./arago-tmp/stamps/i686-linux/linux-libc-headers-native-2.6.31-r6.do_package
    ./arago-tmp/stamps/i686-linux/linux-libc-headers-native-2.6.31-r6.do_configure
    ./arago-tmp/stamps/i686-linux/linux-libc-headers-native-2.6.31-r6.do_unpack
    ./arago-tmp/stamps/i686-linux/linux-libc-headers-native-2.6.31-r6.do_setscene
    ./arago-tmp/stamps/i686-linux/linux-libc-headers-native-2.6.31-r6.do_package_stage
    ./arago-tmp/stamps/i686-linux/linux-libc-headers-native-2.6.31-r6.do_package_write
    ./arago-tmp/stamps/i686-linux/linux-libc-headers-native-2.6.31-r6.do_create_srcipk
    ./arago-tmp/stamps/i686-linux/linux-libc-headers-native-2.6.31-r6.do_package_write_ipk

  • 0 in reply to Michael Kagalenko
    TI__Expert 5450 points

    Michael,

    The arago-base-image does not by itself build the kernel image.  Instead it does stage the linux-headers which is what you are seeing.

    If you want to build the kernel image you should bitbake "virtual/kernel"

    Chase

  • 0 in reply to Chase Maupin
    Prodigy 180 points

    So, after I build arago-tisdk-image target, there is no files containing "2.6.32" string in their names, only 2.6.31 (). Does this indicate that binary packages of rootfs utilities may be incompatible with 2.6.32 kernel?

  • 0 in reply to Michael Kagalenko
    TI__Expert 5450 points

    Michael,

    No.  The 2.6.31 headers were good enough.  That being said, bitbaking the virtual/kernel will allow staging some additional headers and is still a good idea.

    Chase