On 07/16/2012 04:25 PM, Chris Tapp wrote:
I've built the 'atom-pc' kernel as follows:
1) git clone git://git.yoctoproject.org/poky.git
2) git checkout denzil
3) source poky/oe-init-build-env work-area
4) Edit local.conf so that threads/parallel make are both 16 and MACHINE is 'atom-pc'
8) bitbake virtual/kernel.
However, the kernel that gets produced fails to boot. All I get is a screen full of random characters and nothing comes out of the serial port (configured for kernel messages). I don't get any 'Loading...' or 'Uncompressing...' messages either. Using a kernel image from else where (e.g. Voyage Linux) works as expected.
What do I need to do differently to get the above to build a bootable image? I'm assuming that 'atom-pc' works for others?
When I build for Atom PCs, I'm usually targeting a specific BSP like CrownBay, n450, Cedartrail. All of those require the meta-intel layer. So you need to edit the local.conf with a machine like n450, crownbay, cedartrail, etc. and you need to edit bblayer.conf to add the meta-intel layer and the meta-intel/meta/crownbay, etc.
I always bitbake core-image minimal or core-image-sato.
yocto mailing list