Hello Hans-Ulrich, On 1/21/20 7:28 PM, Hans-Ulrich Schlieben wrote: > Hi Ahmad, > >> git clone https://eur04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgit.pengutronix.de%2Fgit%2Fbarebox&data=01%7C01%7Chu.schlieben%40codewrights.de%7C5fdd291346554b1d5e3d08d79dbdda2b%7C0974af9b352b437cb606e9f242c0c227%7C0&sdata=L8WAZYdcm0kjTNZG8OFnedXXyG3DHyIHx1r4gh%2B%2FC%2BI%3D&reserved=0 >> cd barebox >> cp $your_barebox_config_in_yocto .config >> make -j$(nproc) CROSS_COMPILE=/path/to/your/yocto/toolchain/bin/arm-$your_vendor-linux-gnueabihf- ARCH=arm > > I tried to build the barebox sources but got the following error: > $ make -j$(nproc) CROSS_COMPILE=/path/to/your/yocto/toolchain/bin/arm-$your_vendor-linux-gnueabihf- ARCH=arm > make: /path/to/your/yocto/toolchain/bin/arm--linux-gnueabihf-gcc: Kommando nicht gefunden > LEX scripts/kconfig/lexer.lex.c > /bin/sh: 1: flex: not found > make[2]: *** [scripts/Makefile.lib:194: scripts/kconfig/lexer.lex.c] Fehler 127 > make[2]: *** Es wird auf noch nicht beendete Prozesse gewartet.... > YACC scripts/kconfig/parser.tab.h > /bin/sh: 1: bison: not found > make[2]: *** [scripts/Makefile.lib:208: scripts/kconfig/parser.tab.h] Fehler 127 > make[1]: *** [/opt/apps/zeus/barebox/barebox/Makefile:422: syncconfig] Fehler 2 > make: *** [Makefile:463: include/config/auto.conf.cmd] Fehler 2 > > Is the .config file wrong? I copied it from the barebox folder where I built barebox 2017 version. You missed the $your_vendor placeholders, which you need to replace with the toolchain vendor you configured for your Yocto Toolchain. If in doubt, just apt install gcc-arm-linux-gnueabihf and use CROSS_COMPILE=gcc-arm-linux-gnueabihf You also need to install flex and bison. >> under images/ you will have the barebox images. You can get that onto your device using a SD-Card, imx-usb-loader, tftp ... etc. > When the build succeeds where or how to put the image on the sdcard? > By the way, which image is it there a lots of images in the ./image folder and there is none named imx6qdl? There are some named imx6dl and one imx6q. You will note that device trees starting with imx6qdl always have a .dtsi extension, which are device tree source _includes_. They aren't full device trees. Most importantly, they miss the SoC nodes that differentiate between i.MX6 Quad and DualLite. This is done this way, so you can have the same dtsi and use it in a dts once with imx6q.dtsi and once more with imx6dl.dtsi without having to replicate the common parts on the SoM. As for which one to use, depends on your board. If you have a Quad or Dual, use imx6q-$boardname, if you have Dual Lite or Solo use imx6dl-. Cheers Ahmad -- Pengutronix e.K. | | Steuerwalder Str. 21 | http://www.pengutronix.de/ | 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 | Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 | _______________________________________________ barebox mailing list barebox@xxxxxxxxxxxxxxxxxxx http://lists.infradead.org/mailman/listinfo/barebox
