VIA Embedded has so far two Freescale i.MX6Q based products, the VAB-820 board and the matching AMOS-820 system. We have started to move from LTIB-based BSP images to Yocto recently for multiple reasons.
The first, very practical one is that Freescale and the community around it has moved onto Yocto for quite a while now. They are core supporters of the project, and we can see that that they are putting a lot of effort into it.
Second, connected reason is that we see the value very much as well, and want to make sure that both we and our customers can take advantage of the improvements. Yocto enables very interesting use cases, and should change quite a bit how companies are thinking about BSPs. It makes possible separating machine support and bootable image generation. A new product added to the existing code can take advantages of (hopefully) tried and tested OS images for specific use cases. Updating machine support (meaning mostly the kernel and u-boot) does not have to wait until a new version of the OS image is released, but can be developed parallel.
The good things also come with a steeper learning curve, though, both for us and for those who want to customize the generated images. To start learning, we have just released the beta version of the new BSP. It's still under development, but should be a good starting point.
What's your experience with Embedded BSPs? Do you use Yocto, or found something else more suitable for your workflow?
yes! solved! thanks again
Hi vertlim, figured out: the problem is the parentheses "(" and ")" in the path you use. Move your "via-release-bsp" release to a directory without any special characters (no brackets, parentheses, spaces, etc...) in the path, and try again! Eg. based on what you are using now, can try "~/DATA/hardware/VAB-820/V2.0.1/BSP/via-release-bsp/"
By the way, I got this hint from the #yocto community on IRC, lot of very helpful and knowledgeable people there, highly recommend looking in there if you want to have a quick opinion on any Yocto issues.
Hi,
thanks for your quick reply!
Unfortunately, no package you listed is missing and I did exactly the two steps you mentioned above (only added the "-b" option in front of "build-vab820", which I think you forgot in your previous post). I even tried now running Ubuntu natively and not in a virtual machine (I used VirtualBox on Windows 7 for the previous attempts). For this test I used Ubuntu 14.04.2 LTS (64 Bit) and did nothing but a software update after the fresh install. But, same result, same error:
http://pastebin.com/eR7SaP2s
What kind of additional information would you need? Do you run Ubuntu 12.04 or 12.04.5?
Hi Thomas/vertlim!
I just run a fresh compile from the same package and on 12.04, and did not run into the issue you posted. What were the steps you took? For me enough to run:
MACHINE=imx6qvab820 source via-setup-release.sh build-vab820
bitbake via-image-x11
My guess is that some of the packages are not installed on your system that are required for yocto. I've run:
sudo apt-get install wget git-core unzip texinfo libsdl1.2-dev gawk diffstat build-essential chrpath sed cvs subversion coreutils texi2html docbook-utils python-pysqlite2 help2man make gcc g++ desktop-file-utils libgl1-mesa-dev libglu1-mesa-dev mercurial autoconf automake groff curl lzop asciidoc xterm
Also successfully run core-image-minimal, core-image-sato, meta-toolchain too.
Any other info you can provide?
Hi all
I am curently testing the Yocto based BSP (v2.0.1 beta) for the VAB820. During compilation I get an error when executing "bitbake via-image-x11" (or any other target like "meta-toolchain"). I pasted the output to the following pastebin: VIA VAB-820 BSP Compile Error - Pastebin.com. Anyone experiencing the same problem or having a solution for this issue? My developing host is Ubuntu 12.04.5 LTS (64 bit).
Many thanks!
Thomas