AnsweredAssumed Answered

How do I get fw_printenv and fw_setenv included in my rootfs?

Question asked by Cary O'Brien on Sep 25, 2014
Latest reply on Jul 12, 2018 by Ryan Pabis

I am using QorIQ-SDK-1.6 to build code for a P1022 system.

We have a custom machine defined, since our board is different

enough from the eval boards.


We have a working u-boot, kernel, and jffs2 rootfs.


Our application needs to modify u-boot environment variables during

runtime, so we need the fw_printenv and fw_setenv from the uboot

tools/env directory.


There are recipes that are supposed to do this:



Even if I tell these (in a .bbappend) to use an existing

machine (Board) definition (i.e P1022DS) they don't

complete because (I believe) the u-boot version

is older than the used u-boot version (2014.01+fslgit).  It can't

find the compiler.


I modified our u-boot_git.bbappend to COMPILE the utilities,

and the resulting binaries when copied to the rootfs work

correctly, but I cannot figure out how to get these installed

automatically.  More specifically, I have do_fw_compile and

do_fw_install tasks, but the code doesn't end up in the

u-boot RPMS. Except for the image rpm they are empty.


Is there a recipe that will work 'out of the box' with this

version of u-boot?  Is there somewhere I can look for an

example of the tasks I would need to implement to do this?


I can always work around and pull them out of the

build tree 'by hand' but I'd like to do it the right way.


Thanks in Advance,


Cary O'Brien