3

So, I am currently trying to get a hold on Open Embedded to build for an i.MX53 platform, but i have some difficulties in understanding the main outline of the OE concept, as well as how the folder structure should be, gaining an upper view.

So, I was hoping someone could in a few words summarize why not just using the make command in the kernel root.

more importantly(for me ), i would like to know how the folder structure should be, having a Oe-core and the meta-fsl-arm layer built for an i:MX53QSB.

Which file am I supposed to run with bitbake to get a custom image for my device?

Paulo Scardine
  • 73,447
  • 11
  • 124
  • 153
Qw_freak
  • 81
  • 1
  • 10
  • Been waiting for some time now, with no answer.. I am digging into the matter and will hopefully produce an answer which I will post here... – Qw_freak Jul 30 '12 at 07:34
  • I've been trying with OpenEmbedded-Core on Freescale i.MX28, but no success yet, as described in [my question](http://stackoverflow.com/questions/12135129/cant-boot-basic-openembedded-core-on-freescale-i-mx28). – Craig McQueen Aug 27 '12 at 01:16

2 Answers2

0

you should start building some bitbake example recipes, if you hace success with this you should move forward to build your own images. look for the configuration scripts for angstrom, they will help you for setting up some things like architecture and deploy platform. After all these stuff you should put your custom image in your openembedded images folder and execute:

bitbake my_image

ricardohg
  • 39
  • 4
0

Start with this link It is a comprehensive study of the Yocto Open Embedded project. Yocto is a ready-to-go subset that is known to work and is a good place to start.

This link shows you the directory hierarchy.

Frak
  • 832
  • 1
  • 11
  • 32