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

The lack of explanation for meta-arago bitbake target.

jongjin yi
Prodigy 80 points

Hi,

I just started to study arago project, because I want more optimized root filesystem for am335x platform.

I didn't have any knowledge of OpenEmbedded and Yocto before, so I'm not familiar with this build system and environment.

To build meta-arago, I have to use following command

MACHINE=am335x-evm bitbake arago-core-tisdk-image

I found other meta-arago bitbake target under ./tisdk/sources/meta-arago/meta-arago-distro/recipes-core/images.

That is, 

arago-amsdk-image.bb

arago-base-tisdk-image.bb

arago-core-tisdk-image.bb

tisdk-server-rootfs-image.bb

arago-base-image.bb

arago-console-image.bb

tisdk-rootfs-image.bb

I think the name of the above bb files can be used as bitbake target specific for meta-arago distribution.

But, there is no detailed explanation about each target.

I want to know which kind of packages can be selected for each target.

Because I don't have enough knowledge about OpenEmbedded, I cannot understand the meaning of bb file.

Is there any document about the above target?

Or, Could somebody explain that?

  • 0
    Expert 1255 points

    I have the same problem. I also wonder why TI forked off and made the Arago project, and why there isn't a board support package layer like OE and Yocto recommend? Should we be able to simply plug in an AM335x BSP, set MACHINE, and build a system? It's a frustrating system.

  • 0 in reply to Steve Ziuchkovski
    Intellectual 975 points

    I gotta concur with you, the OpenEmbedded, Yocto, Arago, TI SDK mess is very confusing. 

    On the surface Yocto and Arago sound great and the simple examples they provide kind of sort of work but there is a lot left out on how to make your own distribution and the latest stuff doesn't seem to be well tested with the eval boards TI is shipping. 

    Case in point the EVMSK AM335x board I just received 2 weeks ago came with a SD card with an image from SDK 05.05. The current release is 07.00, the quick start guild for 07.00 takes you through setting up NFS boot using the setup.sh script but 07.00 has a but in the network code that prevents it from working. 

    Very frustrating. 

    Matt S. 

  • 0 in reply to Steve Ziuchkovski
    Mastermind 8040 points

    Hey, look at it on the bright side:  at least you have this arago stuff, a recent kernel, and "device tree" to inform linux of your board.  If you had designed a board with a dm8148 like we did then you'd have had the fun of seeing arago drop support for it, still have 2.6.37 as the latest TI-supported kernel (and "there are no plans for updating to 3.10 linux kernel") and as far as I can tell you're expected to patch it to add a hardcoded board config.

    (And threads about this of course end in a similar enjoyment of the sound of crickets.)