1fa1fba729
If a new build is kicked off, and no changes are required to the image contents themselves, but a new rockchip gpt image needs to be generated, the build will fail because this build (run now) will look for an ext4 rootfs that should also exist from this build. However, since no changes were made to the rootfs, a rootfs with this build's timestamp will not exist. I.e. when generating the rockchip gpt image, the script currently looks for the rootfs in: <image name>-<machine name>-<timestamp>.rootfs.<rootfs type> In other words, if the last build to be done had a timestamp of <yesterday> and the build the is currently running has a timestamp of <now>, when the build tries to generate the rockchip gpt image, it will look for: <image name>-<machine name>-<now>.rootfs.ext4 but that file will not exist. The file that will exist is: <image name>-<machine name>-<yesterday>.rootfs.ext4 Therefore, don't look for the absolute file, but use the symlink instead which does not include the timestamp, but will point to the latest rootfs: <image name>-<machine name>.ext4 Signed-off-by: Trevor Woerner <twoerner@gmail.com> |
||
|---|---|---|
| classes | ||
| conf | ||
| licenses | ||
| recipes-bsp | ||
| recipes-core/images | ||
| recipes-devtools/net-kexec | ||
| recipes-graphics/xorg-driver | ||
| recipes-kernel | ||
| recipes-support | ||
| COPYING.MIT | ||
| README | ||
This README file contains information on building with the meta-rockchip BSP layer.
Dependencies
This layer depends on:
{ URI: git://git.openembedded.org/bitbake branch:
AND
URI: git://git.openembedded.org/openembedded-core
layers: meta
branch: <the same release used for meta-rockchip>
}
Contributing
Please submit any patches against this BSP to the maintainers of this layer. The mail must be sent to the following people (as "To:" in the header):
Maintainer: Romain Perier <romain.perier@collabora.com>
Maintainer: Trevor Woerner <twoerner@gmail.com>
Please also include the Yocto Project mailing list "yocto@yoctoproject.org", as Cc. (As "Cc:" in the header).
When sending patches please take a look at the contribution guide available here:
https://www.openembedded.org/wiki/Commit_Patch_Message_Guidelines
Please also send your patches by using git send-email and prefix your subject by "[meta-rockchip]".
I. Configure yocto/oe environment
In order to build an image with BSP support for a given release, you need to download the corresponding tools described in the "Dependencies" section. Be sure that everything is in the same directory.
$ mkdir yocto; cd yocto
~/yocto $ git clone git://git.openembedded.org/bitbake
~/yocto $ git clone git://git.openembedded.org/openembedded-core
~/yocto $ git clone git://git.yoctoproject.org/meta-rockchip
Then you need to source the configuration script:
~/yocto $ source openembedded-core/oe-init-build-env build bitbake
Having done that, you can build an image for a rockchip board by adding the location of the meta-rockchip layer to bblayers.conf, along with any other layers needed (to access common metadata shared between BSPs)
To enable the build for a specific board, add its name in the MACHINE variable to local.conf:
MACHINE ?= "radxarock"
All supported machines can be found in meta-rockchip/conf/machine.
You should then be able to build a image as such:
~/yocto/build $ bitbake core-image-minimal
At the end of a successful build, you should have an image in
tmp-glibc/deploy/images/<MACHINE>/<IMAGE_NAME>