[meta-ti] Building Yocto for Pandaboard

[Christian.Schulenberg at bmw.de]

Hi,

I'm using a Pandaboard Rev A4, so it is in fact an OMAP4430 board.

You can change to u-boot bootloader in /meta-ti/conf/machine/omap4430-panda.conf:

#EXTRA_IMAGEDEPENDS = "x-load u-boot-sakoman " -> remove or comment this line out
EXTRA_IMAGEDEPENDS += "u-boot" -> I used this line, but because omap4430-panda.conf includes omap3.inc, it should be obsolete. Same definition is in there. X-Load can be removed from omap3.inc from my point of view, because it's not necessary.

#PREFERRED_PROVIDER_virtual/bootloader = "u-boot-sakoman"  -> remove or comment this line out
PREFERRED_PROVIDER_virtual/bootloader = "u-boot"

Your question about gcc4.7: I haven't used this version yet.

I have build core-image-base as well as core-image-basic successfully for Pandaboard. I connect to the board via the serial interface, so I don't need a configured eth0 yet.

Thanks for your suggestion about systemd. I will try to pull in system in the next days.

BR,
Christian




-----Ursprüngliche Nachricht-----
Von: Robert P. J. Day [mailto:rpjday at crashcourse.ca] 
Gesendet: Montag, 5. März 2012 14:05
An: Schulenberg Christian, EI-42
Cc: meta-ti mailing list
Betreff: Re: [meta-ti] Building Yocto for Pandaboard


  i'd like to try to reproduce what's below, so a few questions first.
is this for a regular panda, or a 4460-based panda ES?  i'm
specifically interested in the ES, but there's a good chance a regular
build will still at least boot and i'll worry about any weirdness
later.  and i don't see anything in the meta-ti layer yet
*specifically* for the 4460.

  FYI, my setup is 64-bit ubuntu 11.10 with fully pulled

  * yocto
  * meta-ti
  * meta-openembedded (with underlying meta-oe layer, of course)

  and now, the stupid questions ...

On Mon, 5 Mar 2012, Christian.Schulenberg at bmw.de wrote:

> Hi,
>
> finally, I managed to bring up the Pandaboard with the meta-ti layer
> by myself. For all of you, who are facing the same problems and who
> don't want to use Angstrom, here are some hints, how to do this just
> using Yocto Poky:
>
> Remove systemd in local.conf as mentioned above.

  i remember that issue and, rather than remove systemd, i followed
someone else's suggestion and just added the meta-oe layer to pull it
in.  here's my layers info, does it look sane?  (is that the correct
order to get the right precedence?)

BBLAYERS ?= " \
  /home/rpjday/yocto/git/meta \
  /home/rpjday/yocto/git/meta-yocto \
  /home/rpjday/yocto/git/meta-openembedded/meta-oe \
  /home/rpjday/yocto/git/meta-ti \
  "

if systemd is truly a problem, i can take it out.

> I used machine configuration for "omap4430-panda", because machine
> "pandaboard" did not build the kernel.  i suspect the "pandaboard"
> file will be disappearing given its superfluity.

i noticed that already, that's what i'll be using as well.

> Because this configuration use the sakoman bootloader, which caused
> some trouble for me, I switched over to (denx) u-boot.

  and you did that how?

> Use gcc4.5 instead of gcc4.6. The reason for this is a compiler
> error that came up when compiling the u-boot bootloader. You can
> change the compiler in ./meta/conf/distro/include/tcmode-default.inc
> , variable GCCVERSION. Another alternative might be patching the
> gcc4.6, because there is already a fix for this compiler error.

  based on what i read here:

http://www.mail-archive.com/openembedded-devel@lists.openembedded.org/msg24283.html

can i just add that line

GCCVERSION = "4.7%"

to my local.conf?  might as well jump up to gcc 4.7.

  and i currently get a fetch error for udev 173, so i set the
PREFERRED_VERSION to 181.  did you not get such an error?  more later.

rday

-- 

========================================================================
Robert P. J. Day                                 Ottawa, Ontario, CANADA
                        http://crashcourse.ca

Twitter:                                       http://twitter.com/rpjday
LinkedIn:                               http://ca.linkedin.com/in/rpjday
========================================================================