[meta-freescale] Best way (good way?) to make different U-boot for different machine images
Stephen.Munnings at nuvation.com
Wed Jun 25 10:47:30 PDT 2014
I have been hitting a brick wall trying to do what I thought must be a fairly common procedure.
I have two different images that I need to build for our custom board.
Each image should have a slightly different version of u-boot built into it.
One image is for running from the NAND-flash, and one image is for running from the SD Card.
One (for example) should have the Watchdog timer enabled, and the other should not.
I need to be able to build these images from an automated system.
I am having trouble figuring out how to do this.
First, I thought of having different recipes for each image, but the u-boot recipe is a bbappend, not a new recipe.
Then I tried to have the one image create a new override variable, and have the bbappend include new lines based on that override variable.
(This failed because, once built, the u-boot is not re-built automatically, even if the bbappend runs slightly differently)
I could make this work if I could set preprocessor variables to the u-boot build, (and it would always rebuild) but am not sure how to do that.
Basically, my problem is two-fold:
1. Setting different preprocessor variables or patches to source code for each different image
2. Getting the u-boot binary to be re-built once one of the images has built it.
Any hints, clues, or ideas on how to manage this?
Sr. Design Engineer | NUVATION ENGINEERING
stephen.munnings at nuvation.com<mailto:stephen.munnings at nuvation.com> | www.nuvation.com<http://www.nuvation.com>
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the meta-freescale