Where is u-boot source?

cancel
Showing results for 
Search instead for 
Did you mean: 

Where is u-boot source?

Jump to solution
13,577 Views
sbl
Contributor II

I have baked several images for the SabreSD and there are u-boot binaries in the deploy/images folder.  I need to modify u-boot for our board but the source does not exist in the build tree.  Where is it?  There exists a u-boot-imx folder but there is no source in it.  The recipe pulls from git:

# branch=imx_v2013.04_3.5.7_1.0.0_alpha

SRC_URI = "git://${FSL_ARM_GIT_SERVER}/uboot-imx.git;protocol=git"

SRCREV = "a5a24c34364d59175d7d3130d02e8472572b9f4e"

Labels (1)
Tags (2)
1 Solution
1,292 Views
daiane_angolini
NXP Employee
NXP Employee

I thought another way to know where your missing source code is.

from my u-boot tmp/work dir I have run.do_unpack and log.do_unpack. And from your log you don't have this file.

It may explain why you cannot see your source code..

But, why your bitbake did not run unpack I don't know.

Is there a config to place on local.conf exactly to remove the  work dir "INHERIT += rm_work", but it does not look to be this case. (I looked at default local.conf  from git.freescale.com and it is not set there)

Do the command bitbake -c unpack u-boot work for you?

Please share the error message or the error file

View solution in original post

0 Kudos
27 Replies
1,215 Views
daiane_angolini
NXP Employee
NXP Employee

Where I can see u-boot source code on my rootfs:

daiane@b19406:~/master/build$ ls -l tmp/work/imx53qsb-poky-linux-gnueabi/u-boot-fslc/v2013.10-r0/git/
total 3132
drwxrwxr-x   2 daiane daiane    4096 Sep  5 14:11 api
drwxrwxr-x  16 daiane daiane    4096 Sep  5 14:11 arch
drwxrwxr-x 286 daiane daiane   12288 Sep  5 14:11 board
-rw-rw-r--   1 daiane daiane  129700 Sep  5 14:11 boards.cfg
drwxrwxr-x   3 daiane daiane   12288 Sep  5 14:11 common
-rw-rw-r--   1 daiane daiane   11899 Sep  5 14:11 config.mk
-rw-rw-r--   1 daiane daiane   12166 Sep  5 14:11 CREDITS
drwxrwxr-x   2 daiane daiane    4096 Sep  5 14:11 disk
drwxrwxr-x   7 daiane daiane    4096 Sep  5 14:11 doc
drwxrwxr-x  30 daiane daiane    4096 Sep  5 14:11 drivers
drwxrwxr-x   2 daiane daiane    4096 Sep  5 14:11 dts
drwxrwxr-x   4 daiane daiane    4096 Sep  5 14:11 examples
drwxrwxr-x  13 daiane daiane    4096 Sep  5 14:11 fs
drwxrwxr-x  20 daiane daiane   12288 Sep  5 14:11 include
drwxrwxr-x   8 daiane daiane    4096 Sep  5 14:11 lib
drwxrwxr-x   2 daiane daiane    4096 Sep  5 14:11 Licenses
-rw-rw-r--   1 daiane daiane   27883 Sep  5 14:11 MAINTAINERS
-rwxrwxr-x   1 daiane daiane   23401 Sep  5 14:11 MAKEALL
-rw-rw-r--   1 daiane daiane   30377 Sep  5 14:11 Makefile
-rwxrwxr-x   1 daiane daiane    4283 Sep  5 14:11 mkconfig
drwxrwxr-x   3 daiane daiane    4096 Sep  5 14:11 nand_spl
drwxrwxr-x   2 daiane daiane    4096 Sep  5 14:11 net
drwxrwxr-x   6 daiane daiane    4096 Sep  5 14:11 post
-rw-rw-r--   1 daiane daiane  205627 Sep  5 14:11 README
-rw-rw-r--   1 daiane daiane    1752 Sep  5 14:11 rules.mk
-rw-rw-r--   1 daiane daiane      17 Sep  5 14:11 snapshot.commit
drwxrwxr-x   2 daiane daiane    4096 Sep  5 14:11 spl
drwxrwxr-x   5 daiane daiane    4096 Sep  5 14:11 test
drwxrwxr-x  15 daiane daiane    4096 Sep  5 14:11 tools
-rwxr-xr-x   1 daiane daiane 1733868 Sep  5 14:11 u-boot
-rw-r--r--   1 daiane daiane  298856 Sep  5 14:11 u-boot.bin
-rw-r--r--   1 daiane daiane  302952 Sep  5 14:11 u-boot.imx
-rw-r--r--   1 daiane daiane    1085 Sep  5 14:11 u-boot.lds
-rw-r--r--   1 daiane daiane  320103 Sep  5 14:11 u-boot.map

daiane@b19406:~/master/downloads$ ls git2_github.com.Freescale.u-boot-imx.git.tar.gz*
git2_github.com.Freescale.u-boot-imx.git.tar.gz  git2_github.com.Freescale.u-boot-imx.git.tar.gz.done

This is what I have already built on my machine right now.

0 Kudos
1,293 Views
daiane_angolini
NXP Employee
NXP Employee

I thought another way to know where your missing source code is.

from my u-boot tmp/work dir I have run.do_unpack and log.do_unpack. And from your log you don't have this file.

It may explain why you cannot see your source code..

But, why your bitbake did not run unpack I don't know.

Is there a config to place on local.conf exactly to remove the  work dir "INHERIT += rm_work", but it does not look to be this case. (I looked at default local.conf  from git.freescale.com and it is not set there)

Do the command bitbake -c unpack u-boot work for you?

Please share the error message or the error file

View solution in original post

0 Kudos
1,215 Views
sbl
Contributor II

The unpack command made the source code show up under /tmp/work/imx6qsabresd-poky-linux-gnueabi/u-boot-imx/2013-04-5/git

My local.conf follows.  I only added the SSTATE and DL lines.

MACHINE ??= 'imx6qsabresd'

DISTRO ?= 'poky'

PACKAGE_CLASSES ?= "package_rpm"

EXTRA_IMAGE_FEATURES = "debug-tweaks"

USER_CLASSES ?= "buildstats image-mklibs image-prelink"

PATCHRESOLVE = "noop"

DL_DIR="/media/i.MX6_ddr3/fsl-community-bsp/downloads"

SSTATE_DIR="/media/i.MX6_ddr3/fsl-community-bsp/sstate-cache"

BB_DISKMON_DIRS = "\

    STOPTASKS,${TMPDIR},1G,100K \

    STOPTASKS,${DL_DIR},1G,100K \

    STOPTASKS,${SSTATE_DIR},1G,100K \

    ABORT,${TMPDIR},100M,1K \

    ABORT,${DL_DIR},100M,1K \

    ABORT,${SSTATE_DIR},100M,1K"

CONF_VERSION = "1"

BB_NUMBER_THREADS = '8'

PARALLEL_MAKE = '-j 8'

ACCEPT_FSL_EULA = ""

DISTRO_FEATURES = "x11 alsa argp bluetooth ext2 irda largefile pcmcia usbgadget usbhost wifi xattr nfs zeroconf pci 3g ${DISTRO_FEATURES_LIBC}"

Thank you,

sbl

0 Kudos
1,215 Views
leoschwab
Contributor III

Scott Leonard wrote:

The unpack command made the source code show up under /tmp/work/imx6qsabresd-poky-linux-gnueabi/u-boot-imx/2013-04-5/git

Be aware that, every time the 'unpack' task runs (which is basically any time a recipe affecting U-Boot changes), this directory will be blown away and re-created from scratch.  So if you have any work-in-progress in here, it will be destroyed.  This is why the Yocto developers say to do iterative development elsewhere, and only use Yocto for doing builds.  (Which is easier said than done, given how many environment variables have to be set up to do the compile properly.)

0 Kudos
1,215 Views
LeonardoSandova
Specialist I

have you run the toolchain's setup script?

Leo

0 Kudos
1,215 Views
sbl
Contributor II

The problem was I didn't install the toolchain in the default location under /opt/poky.  I created a symbolic link at /opt/poky/ and it works now.  This bug was reported a year ago and apparently has never been fixed.

[OE-core] ld problems with relocated toolchain

0 Kudos
1,222 Views
daiane_angolini
NXP Employee
NXP Employee

Look.

If you had read all the documents, you would know what I will say to you here. So, please, be calm and read one line at a time.

Yocto is not supposed to be a development tool. It´s supposed to wrap all things you have already done, ready, released, and place altogether on an image.

Said so. You will find only a COPY of u-boot source code inside the yocto build dir, it´s located at tmp/work/<your-board>/u-boot-fslc. If you had find -name *u-boot* you would had find it.

If you need to develop with u-boot you MUST git clone it from the source:

Freescale:

http://git.freescale.com/git/cgit.cgi/imx/uboot-imx.git/

Denx

git.denx.de Git - u-boot.git/summary

Then, you clone it to any place you want. Develop it. And after your board is booting you create one recipe into your meta layer to fetch your u-boot and build/deploy it.

I will not reply to your direct message. It´s not my fault that you´re a newbie. (I don´t want to be rude, you started it)

Oh, and "modify u-boot" in yocto is *exactly the same* as modifying kernel.

0 Kudos
1,222 Views
sbl
Contributor II

Daiane Angolini wrote:

Look.

I have.  Extensively for the last week.  It is not there.

If you had read all the documents, you would know what I will say to you here. So, please, be calm and read one line at a time.

I am calm (I'm not the one calling people names and typing in all caps) and I have been reading the documents (I am on my third time through the Yocto Mega Manual, and I have read the attached Freescale document at least a dozen times).

Yocto is not supposed to be a development tool. It´s supposed to wrap all things you have already done, ready, released, and place altogether on an image.

I understand that.  It builds the whole kit and kaboodle from u-boot to rootfs to sd card image.  Wonderful.

Said so. You will find only a COPY of u-boot source code inside the yocto build dir, it´s located at tmp/work/<your-board>/u-boot-fslc. If you had find -name *u-boot* you would had find it.

No, it is not, and I have:

build@ubuntu:/media/i.MX6_ddr3/fsl-community-bsp/build.x11$ find . -iname *u-boot*

./tmp/work/x86_64-linux/u-boot-mkimage-native

./tmp/work/x86_64-linux/u-boot-mkimage-native/2011.06-r0/u-boot-2011.06

./tmp/work/x86_64-linux/u-boot-mkimage-native/2011.06-r0/license-destdir/u-boot-mkimage-native

./tmp/work/x86_64-linux/qemu-native/1.4.0-r0/qemu-1.4.0/roms/SLOF/board-qemu/slof/qemu-bootlist.fs

./tmp/work/imx6qsabresd-poky-linux-gnueabi/imx-test/1_3.5.7-1.0.0-r7.0/imx-test-3.5.7-1.0.0/test/mxc_secureboot/V2009/u-boot

./tmp/work/imx6qsabresd-poky-linux-gnueabi/imx-test/1_3.5.7-1.0.0-r7.0/imx-test-3.5.7-1.0.0/test/mxc_secureboot/V2012/u-boot

./tmp/work/imx6qsabresd-poky-linux-gnueabi/linux-imx/3.5.7-1.0.0-r32.5/package/usr/src/kernel/arch/avr32/boot/u-boot

./tmp/work/imx6qsabresd-poky-linux-gnueabi/linux-imx/3.5.7-1.0.0-r32.5/sysroot-destdir/usr/src/kernel/arch/avr32/boot/u-boot

./tmp/work/imx6qsabresd-poky-linux-gnueabi/linux-imx/3.5.7-1.0.0-r32.5/packages-split/kernel-dev/usr/src/kernel/arch/avr32/boot/u-boot

./tmp/work/imx6qsabresd-poky-linux-gnueabi/u-boot-imx

./tmp/work/imx6qsabresd-poky-linux-gnueabi/u-boot-imx/2013-04-5/deploy-u-boot-imx

./tmp/work/imx6qsabresd-poky-linux-gnueabi/u-boot-imx/2013-04-5/deploy-u-boot-imx/u-boot-imx6qsabresd.imx

./tmp/work/imx6qsabresd-poky-linux-gnueabi/u-boot-imx/2013-04-5/deploy-u-boot-imx/u-boot.imx

./tmp/work/imx6qsabresd-poky-linux-gnueabi/u-boot-imx/2013-04-5/deploy-u-boot-imx/u-boot-imx6qsabresd-2013-04-5.imx

./tmp/work/imx6qsabresd-poky-linux-gnueabi/u-boot-imx/2013-04-5/package/boot/u-boot.imx

./tmp/work/imx6qsabresd-poky-linux-gnueabi/u-boot-imx/2013-04-5/package/boot/u-boot-imx6qsabresd-2013-04-5.imx

./tmp/work/imx6qsabresd-poky-linux-gnueabi/u-boot-imx/2013-04-5/deploy-rpms/imx6qsabresd/u-boot-imx-dbg-2013+04-5.imx6qsabresd.rpm

./tmp/work/imx6qsabresd-poky-linux-gnueabi/u-boot-imx/2013-04-5/deploy-rpms/imx6qsabresd/u-boot-imx-dev-2013+04-5.imx6qsabresd.rpm

./tmp/work/imx6qsabresd-poky-linux-gnueabi/u-boot-imx/2013-04-5/deploy-rpms/imx6qsabresd/u-boot-imx-2013+04-5.imx6qsabresd.rpm

./tmp/work/imx6qsabresd-poky-linux-gnueabi/u-boot-imx/2013-04-5/pkgdata/runtime/u-boot-imx-dev.packaged

./tmp/work/imx6qsabresd-poky-linux-gnueabi/u-boot-imx/2013-04-5/pkgdata/runtime/u-boot-imx-dev

./tmp/work/imx6qsabresd-poky-linux-gnueabi/u-boot-imx/2013-04-5/pkgdata/runtime/u-boot-imx.packaged

./tmp/work/imx6qsabresd-poky-linux-gnueabi/u-boot-imx/2013-04-5/pkgdata/runtime/u-boot-imx-locale

./tmp/work/imx6qsabresd-poky-linux-gnueabi/u-boot-imx/2013-04-5/pkgdata/runtime/u-boot-imx-dbg

./tmp/work/imx6qsabresd-poky-linux-gnueabi/u-boot-imx/2013-04-5/pkgdata/runtime/u-boot-imx

./tmp/work/imx6qsabresd-poky-linux-gnueabi/u-boot-imx/2013-04-5/pkgdata/runtime/u-boot-imx-doc

./tmp/work/imx6qsabresd-poky-linux-gnueabi/u-boot-imx/2013-04-5/pkgdata/runtime/u-boot-imx-dbg.packaged

./tmp/work/imx6qsabresd-poky-linux-gnueabi/u-boot-imx/2013-04-5/pkgdata/runtime/u-boot-imx-staticdev

./tmp/work/imx6qsabresd-poky-linux-gnueabi/u-boot-imx/2013-04-5/pkgdata/u-boot-imx

./tmp/work/imx6qsabresd-poky-linux-gnueabi/u-boot-imx/2013-04-5/pkgdata/runtime-reverse/u-boot-imx-dev

./tmp/work/imx6qsabresd-poky-linux-gnueabi/u-boot-imx/2013-04-5/pkgdata/runtime-reverse/u-boot-imx-locale

./tmp/work/imx6qsabresd-poky-linux-gnueabi/u-boot-imx/2013-04-5/pkgdata/runtime-reverse/u-boot-imx-dbg

./tmp/work/imx6qsabresd-poky-linux-gnueabi/u-boot-imx/2013-04-5/pkgdata/runtime-reverse/u-boot-imx

./tmp/work/imx6qsabresd-poky-linux-gnueabi/u-boot-imx/2013-04-5/pkgdata/runtime-reverse/u-boot-imx-doc

./tmp/work/imx6qsabresd-poky-linux-gnueabi/u-boot-imx/2013-04-5/pkgdata/runtime-reverse/u-boot-imx-staticdev

./tmp/work/imx6qsabresd-poky-linux-gnueabi/u-boot-imx/2013-04-5/license-destdir/u-boot-imx

./tmp/work/imx6qsabresd-poky-linux-gnueabi/u-boot-imx/2013-04-5/packages-split/u-boot-imx-dev

./tmp/work/imx6qsabresd-poky-linux-gnueabi/u-boot-imx/2013-04-5/packages-split/u-boot-imx-locale

./tmp/work/imx6qsabresd-poky-linux-gnueabi/u-boot-imx/2013-04-5/packages-split/u-boot-imx-dbg

./tmp/work/imx6qsabresd-poky-linux-gnueabi/u-boot-imx/2013-04-5/packages-split/u-boot-imx

./tmp/work/imx6qsabresd-poky-linux-gnueabi/u-boot-imx/2013-04-5/packages-split/u-boot-imx/boot/u-boot.imx

./tmp/work/imx6qsabresd-poky-linux-gnueabi/u-boot-imx/2013-04-5/packages-split/u-boot-imx/boot/u-boot-imx6qsabresd-2013-04-5.imx

./tmp/work/imx6qsabresd-poky-linux-gnueabi/u-boot-imx/2013-04-5/packages-split/u-boot-imx-doc

./tmp/work/imx6qsabresd-poky-linux-gnueabi/u-boot-imx/2013-04-5/packages-split/u-boot-imx-staticdev

./tmp/log/cleanlogs/u-boot-imx

./tmp/deploy/rpm/imx6qsabresd/u-boot-imx-dbg-2013+04-5.imx6qsabresd.rpm

./tmp/deploy/rpm/imx6qsabresd/u-boot-imx-dev-2013+04-5.imx6qsabresd.rpm

./tmp/deploy/rpm/imx6qsabresd/u-boot-imx-2013+04-5.imx6qsabresd.rpm

./tmp/deploy/images/u-boot-imx6qsabresd.imx

./tmp/deploy/images/u-boot.imx

./tmp/deploy/images/u-boot-imx6qsabresd-2013-04-5.imx

./tmp/deploy/licenses/u-boot-mkimage-native

./tmp/deploy/licenses/u-boot-imx

./tmp/sstate-control/manifest-imx6qsabresd-u-boot-imx.package

./tmp/sstate-control/manifest-x86_64-u-boot-mkimage-native.populate-lic

./tmp/sstate-control/manifest-x86_64-u-boot-mkimage-native.populate-sysroot

./tmp/sstate-control/manifest-imx6qsabresd-u-boot-imx.packagedata

./tmp/sstate-control/manifest-imx6qsabresd-u-boot-imx.deploy-rpm

./tmp/sstate-control/manifest-imx6qsabresd-u-boot-imx.populate-sysroot

./tmp/sstate-control/manifest-imx6qsabresd-u-boot-imx.deploy

./tmp/sstate-control/manifest-imx6qsabresd-u-boot-imx.populate-lic

./tmp/stamps/x86_64-linux/u-boot-mkimage-native

./tmp/stamps/imx6qsabresd-poky-linux-gnueabi/u-boot-imx

./tmp/pkgdata/imx6qsabresd-poky-linux-gnueabi/runtime/u-boot-imx-dev.packaged

./tmp/pkgdata/imx6qsabresd-poky-linux-gnueabi/runtime/u-boot-imx-dev

./tmp/pkgdata/imx6qsabresd-poky-linux-gnueabi/runtime/u-boot-imx.packaged

./tmp/pkgdata/imx6qsabresd-poky-linux-gnueabi/runtime/u-boot-imx-locale

./tmp/pkgdata/imx6qsabresd-poky-linux-gnueabi/runtime/u-boot-imx-dbg

./tmp/pkgdata/imx6qsabresd-poky-linux-gnueabi/runtime/u-boot-imx

./tmp/pkgdata/imx6qsabresd-poky-linux-gnueabi/runtime/u-boot-imx-doc

./tmp/pkgdata/imx6qsabresd-poky-linux-gnueabi/runtime/u-boot-imx-dbg.packaged

./tmp/pkgdata/imx6qsabresd-poky-linux-gnueabi/runtime/u-boot-imx-staticdev

./tmp/pkgdata/imx6qsabresd-poky-linux-gnueabi/u-boot-imx

./tmp/pkgdata/imx6qsabresd-poky-linux-gnueabi/runtime-reverse/u-boot-imx-dev

./tmp/pkgdata/imx6qsabresd-poky-linux-gnueabi/runtime-reverse/u-boot-imx-locale

./tmp/pkgdata/imx6qsabresd-poky-linux-gnueabi/runtime-reverse/u-boot-imx-dbg

./tmp/pkgdata/imx6qsabresd-poky-linux-gnueabi/runtime-reverse/u-boot-imx

./tmp/pkgdata/imx6qsabresd-poky-linux-gnueabi/runtime-reverse/u-boot-imx-doc

./tmp/pkgdata/imx6qsabresd-poky-linux-gnueabi/runtime-reverse/u-boot-imx-staticdev

./tmp/buildstats/fsl-image-x11-imx6qsabresd/201310011259/u-boot-mkimage-native-2011.06-r0

./tmp/buildstats/fsl-image-x11-imx6qsabresd/201310011259/u-boot-imx-2013-04-5

./tmp/buildstats/fsl-image-x11-imx6qsabresd/201310011642/u-boot-imx-2013-04-5

./tmp/buildstats/u-boot-imx-imx6qsabresd

./tmp/buildstats/u-boot-imx-imx6qsabresd/201310021528/u-boot-imx-2013-04-5

./tmp/sysroots/imx6qsabresd/usr/src/kernel/arch/avr32/boot/u-boot

build@ubuntu:/media/i.MX6_ddr3/fsl-community-bsp/build.x11$

If you need to develop with u-boot you MUST git clone it from the source:

Freescale:

http://git.freescale.com/git/cgit.cgi/imx/uboot-imx.git/

Denx

git.denx.de Git - u-boot.git/summary

I've already done this, as I said in a previous post (speaking of not reading things).

Then, you clone it to any place you want. Develop it. And after your board is booting you create one recipe into your meta layer to fetch your u-boot and build/deploy it.

That is what I am currently in the process of doing.

I will not reply to your direct message. It´s not my fault that you´re a newbie. (I don´t want to be rude, you started it)

I have been building embedded devices for the last 5+ years using u-boot directly and using ltib on other Freescale platforms.  I am not new to this bring-up process (as stated in a previous post).  I should be finished patching u-boot today and have a booting platform again.  I am new to the Yocto build environment, so wasting my time trying to follow incorrect documentation is frustrating.  The entire point of all of my posts has been to simply find out where in the build tree is the source to u-boot.  Being treated like I don't know how to use find and grep (which I have already posted the results from in previous posts) is insulting.  I have read my message to you a couple of times now and I fail to find any occurrence of me blaming you for anything.  If that was your impression, I apologize for making you feel defensive.  The only reason I was trying to take the discussion off line was for the purpose of discussion supposedly confidential Freescale information and to not clutter up the forum with threads like this.  I was trying to express my frustration without being rude, so I didn't start it.  There were no derogatory remarks, all caps typing, name-calling or insults in my message to you.  The same cannot be said of your reply.  Glad to see that Freescale employees keep things at a professional level [not].  I would surmise that your next step will be to delete this post/thread and ban me.  Do you treat all of your partners this way?

Oh, and "modify u-boot" in yocto is *exactly the same* as modifying kernel.

Except for the part where modifying the kernel says (paraphrased): "Go into the build tree, find the kernel source and either use the quilt or git method to patch the kernel".

Let's try that with u-boot, shall we?  Again, paraphrased: "Go into the build tree, find the u-boot source (sorry, it doesn't exist!) and either use the quilt or git method to patch u-boot".

Not quite the same thing.

I implore you to please follow the directions in the attached document for fetching and building fsl-image-x11.  If, after you have built it, you can show me where in build tree the u-boot source is, I will happily paypal you enough cash to go to a local establishment and have a glass of your favorite beverage to relax as compensation for having to deal with ilk such as me.  On the other hand, if you can't find the u-boot source in the build tree, I would be just as happy to receive a public apology from you.

Regards,

sbl

0 Kudos
1,215 Views
daiane_angolini
NXP Employee
NXP Employee

I´m really sorry. If you read my activities you see how much I lost my mind in the past.

All my support life is open and public. That´s part of my job.

and I personally don´t have permission (I mean, system permission) to delete even my posts. So I (personally) will not delete any.

Your private message is not offensive, but it hurt me, I cannot apologize of felt the way I did. I´m here always open to help.  Why not wait to my reply on the public topic we asked you to open? I´m sure I asked you to share it with me, and you didn´t.

It´s all my fault, absolutely. I need to take a breath when something  hurt me and I didn´t. I´m so sorry.

Can we, please, focus on try to find your source code? Can we be at same side again?

0 Kudos
1,215 Views
daiane_angolini
NXP Employee
NXP Employee

And I just figured out why we are not talking about the same thing.

You´re using the 3.5.7-1.0.0 BSP.

And, my mind only consider meta-fsl-arm itself.

0 Kudos
1,222 Views
daiane_angolini
NXP Employee
NXP Employee

I apologize.

I´m so sorry. I will believe in what you say in future.

0 Kudos
1,222 Views
LeonardoSandova
Specialist I

Which branches are you using? dylan, dora, master?

Leo

0 Kudos
1,222 Views
sbl
Contributor II

Dylan

0 Kudos
1,222 Views
LeonardoSandova
Specialist I

Scott, have you found it? I participated on the 3.5.7 sanity and looking at the build folder, all u-boot code is on tmp/work/imx6qsabresd-poky-linux-gnueabi/u-boot-imx/2013-04-5/git/

Double-checked, it is there :smileyhappy:

1,222 Views
sbl
Contributor II

I've run the bitbake meta-toolchain.  Do I run "make ARCH=arm CROSS_COMPILE=??? -j8" to build it in place?  What is the cross compiler prefix?

sbl

0 Kudos
1,222 Views
LeonardoSandova
Specialist I

linux-imx $ export ARCH=arm 

linux-imx $ export CROSS_COMPILE=arm-poky-linux-gnueabi-

linux-imx $ unset LDFLAGS

Check:

i.MX Yocto Project: How can I compile the kernel manually?

1,222 Views
sbl
Contributor II

Thank you.  I had found that a couple of days ago but couldn't remember where.  Build is erroring out:

make[1]: `libmx6qsabresd.o' is up to date.

make[1]: Leaving directory `/media/i.MX6_ddr3/fsl-community-bsp/build.x11/tmp/work/imx6qsabresd-poky-linux-gnueabi/u-boot-imx/2013-04-5/git/board/freescale/mx6qsabresd'

cd /media/i.MX6_ddr3/fsl-community-bsp/build.x11/tmp/work/imx6qsabresd-poky-linux-gnueabi/u-boot-imx/2013-04-5/git && arm-poky-linux-gnueabi-ld.bfd  -pie -T u-boot.lds -Bstatic -Ttext 0x17800000 arch/arm/cpu/armv7/start.o --start-group api/libapi.o arch/arm/cpu/armv7/libarmv7.o arch/arm/cpu/armv7/mx6/libmx6.o arch/arm/imx-common/libimx-common.o arch/arm/lib/libarm.o board/freescale/common/libfreescale.o common/libcommon.o disk/libdisk.o drivers/bios_emulator/libatibiosemu.o drivers/block/libblock.o drivers/crypto/libcrypto.o drivers/dfu/libdfu.o drivers/dma/libdma.o drivers/fpga/libfpga.o drivers/gpio/libgpio.o drivers/hwmon/libhwmon.o drivers/i2c/libi2c.o drivers/input/libinput.o drivers/misc/libmisc.o drivers/mmc/libmmc.o drivers/mtd/libmtd.o drivers/mtd/nand/libnand.o drivers/mtd/onenand/libonenand.o drivers/mtd/spi/libspi_flash.o drivers/mtd/ubi/libubi.o drivers/net/libnet.o drivers/net/phy/libphy.o drivers/pci/libpci.o drivers/pcmcia/libpcmcia.o drivers/power/battery/libbattery.o drivers/power/fuel_gauge/libfuel_gauge.o drivers/power/libpower.o drivers/power/pmic/libpmic.o drivers/rtc/librtc.o drivers/serial/libserial.o drivers/sound/libsound.o drivers/spi/libspi.o drivers/tpm/libtpm.o drivers/twserial/libtws.o drivers/usb/eth/libusb_eth.o drivers/usb/gadget/libusb_gadget.o drivers/usb/host/libusb_host.o drivers/usb/musb-new/libusb_musb-new.o drivers/usb/musb/libusb_musb.o drivers/usb/phy/libusb_phy.o drivers/usb/ulpi/libusb_ulpi.o drivers/video/libvideo.o drivers/watchdog/libwatchdog.o fs/cbfs/libcbfs.o fs/cramfs/libcramfs.o fs/ext4/libext4fs.o fs/fat/libfat.o fs/fdos/libfdos.o fs/jffs2/libjffs2.o fs/libfs.o fs/reiserfs/libreiserfs.o fs/sandbox/libsandboxfs.o fs/ubifs/libubifs.o fs/yaffs2/libyaffs2.o fs/zfs/libzfs.o lib/libfdt/libfdt.o lib/libgeneric.o lib/lzma/liblzma.o lib/lzo/liblzo.o lib/zlib/libz.o net/libnet.o post/libpost.o test/libtest.o board/freescale/mx6qsabresd/libmx6qsabresd.o --end-group /media/i.MX6_ddr3/fsl-community-bsp/build.x11/tmp/work/imx6qsabresd-poky-linux-gnueabi/u-boot-imx/2013-04-5/git/arch/arm/lib/eabi_compat.o  -L . -lgcc -Map u-boot.map -o u-boot

arm-poky-linux-gnueabi-ld.bfd: cannot find -lgcc

make: *** [u-boot] Error 1

0 Kudos
1,222 Views
sbl
Contributor II

Yes, Daiane pointed me at the unpack command (post below) which produced the source at that location.

Thank you,

sbl

0 Kudos
1,222 Views
awright
Contributor II

The Freescale i.MX u-boot Tree code can be found at the following locations.

git://git.freescale.com/imx/uboot-imx.git

http://git.freescale.com/git/cgit.cgi/imx/uboot-imx.git

0 Kudos
1,222 Views
sbl
Contributor II

Where is it in the yocto build tree?

0 Kudos