Re: [meta-intel] swupdate yocto
On 4/2/18 11:49 PM, Mohammad, Jamal M wrote: > I modified EFI_PROVIDER to "grub-efi" for intel-core-i7 machine and generated > a root filesystem ( ext4 ) > > Now I need to create an additional partition to keep this initrd image and > then modify the grub configuration to jump into this. > > Do you have any idea on this where I have to modify the partition script in > yocto.. If you are using a recent version of Yocto, have a look at wic: https://www.yoctoproject.org/docs/latest/mega-manual/mega-manual.html#creating-partitioned-images-using-wic That is how we produce multiple partitions since our last release (2.4). Before that you would have to do this manually. Freescale has a great example of how to do this in their image_types child class: https://github.com/Freescale/meta-fsl-arm/blob/master/classes/image_types_fsl.bbclass Again, I would only recommend this if you do not have access to wic and wks (wic kick start) files. --S > > Regards, > Jamal > > -Original Message- > From: Stephano Cetola [mailto:stephano.cet...@linux.intel.com] > Sent: Monday, April 02, 2018 7:19 PM > To: Mohammad, Jamal M > Cc: meta-intel@yoctoproject.org > Subject: Re: [meta-intel] swupdate yocto > > For swupdate support, please see their google group: > > https://urldefense.proofpoint.com/v2/url?u=https-3A__groups.google.com_forum_-23-21topic_swupdate_MGq0uMQAUvs&d=DwID-g&c=gJN2jf8AyP5Q6Np0yWY19w&r=4h__2a8-7N65qoDnmtsyGh_QYq3kPCn-Loy2L0LHnCs&m=mmFyyRToaSShSSW6iBMDSgFBGdZwS6N_3E0Gh_Rg4oY&s=1ozow8dnGfNk8acsmAlQ0i3pGQM6YI-ULbt1c9SnoIs&e= > > It sounds like you need to understand swupdate better so that you can utilize > their GRUB or EFI Boot Guard support. > > Cheers, > Stephano > > On 4/2/18 2:56 AM, Mohammad, Jamal M wrote: >> Hi, >> >> I cloned the master branch of poky, meta-intel and meta-swupdate and >> then I added both layers to bblayers.conf file >> >> When I run "bitbake swupdate-image", I get the following error: >> >> >> ERROR: Nothing PROVIDES 'u-boot-fw-utils' (but >> /home/jamal/Yocto/poky/meta-swupdate/recipes-support/swupdate/https:// >> urldefense.proofpoint.com/v2/url?u=http-3A__swupdate-5F2018.03.bb&d=Dw >> ID-g&c=gJN2jf8AyP5Q6Np0yWY19w&r=4h__2a8-7N65qoDnmtsyGh_QYq3kPCn-Loy2L0 >> LHnCs&m=mmFyyRToaSShSSW6iBMDSgFBGdZwS6N_3E0Gh_Rg4oY&s=i4W4pGZF6XiTAmaS >> _-nkyCmsELJf5Irdu5h9vGY_MrM&e= >> DEPENDS on or otherwise requires it) >> >> u-boot-fw-utils was skipped: Either UBOOT_MACHINE or UBOOT_CONFIG must >> be set in the intel-corei7-64 machine configuration. >> >> NOTE: Runtime target 'swupdate-www' is unbuildable, removing... >> >> Missing or unbuildable dependency chain was: ['swupdate-www', >> 'u-boot-fw-utils'] >> >> ERROR: Required build target 'swupdate-image' has no buildable providers. >> >> Missing or unbuildable dependency chain was: ['swupdate-image', >> 'swupdate-www', 'u-boot-fw-utils'] >> >> As, it is Intel board, the bootloader should not be uboot, so why it >> is throwing that error. I am just a beginner in Yocto.. Forgive me if >> I made a small mistake. Did anyone have steps of how to get started >> for swupdate on Intel Yocto. >> >> Thanks and Regards, >> Mohammad Jamal, >> NCR Corporation > -- ___ meta-intel mailing list meta-intel@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-intel
Re: [meta-intel] bootloader used for core-image-full-cmdline
On 4/3/18 2:54 AM, Mohammad, Jamal M wrote: > Can we use u-boot with Intel boards? This depends on which specific device you are referencing and whether that device manufacturer supports u-boot. I have never seen any x86 based device use u-boot in a production environment. --S > > -Original Message- > From: Anuj Mittal [mailto:anuj.mit...@intel.com] > Sent: Tuesday, April 03, 2018 3:23 PM > To: Mohammad, Jamal M ; > meta-intel@yoctoproject.org > Subject: Re: [meta-intel] bootloader used for core-image-full-cmdline > > On 04/03/2018 11:11 AM, Mohammad, Jamal M wrote: >> Hi, >> >> >> >> What is the bootloader used when we flash core-image-minimal or >> core-image-full-cmdline image. >> > > It depends on the value of EFI_PROVIDER. It can be grub-efi or systemd-boot. > >> >> >> I don't see any grub image there in tmp/deploy/images folder >> >> >> >> Is bootx64.efi a bootloader? >> > > Yes, that is what the firmware looks for. > > Thanks, > Anuj > -- ___ meta-intel mailing list meta-intel@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-intel
Re: [meta-intel] swupdate yocto
For swupdate support, please see their google group: https://groups.google.com/forum/#!topic/swupdate/MGq0uMQAUvs It sounds like you need to understand swupdate better so that you can utilize their GRUB or EFI Boot Guard support. Cheers, Stephano On 4/2/18 2:56 AM, Mohammad, Jamal M wrote: > Hi, > > I cloned the master branch of poky, meta-intel and meta-swupdate and > then I added both layers to bblayers.conf file > > When I run “bitbake swupdate-image”, I get the following error: > > > ERROR: Nothing PROVIDES 'u-boot-fw-utils' (but > /home/jamal/Yocto/poky/meta-swupdate/recipes-support/swupdate/swupdate_2018.03.bb > DEPENDS on or otherwise requires it) > > u-boot-fw-utils was skipped: Either UBOOT_MACHINE or UBOOT_CONFIG must > be set in the intel-corei7-64 machine configuration. > > NOTE: Runtime target 'swupdate-www' is unbuildable, removing... > > Missing or unbuildable dependency chain was: ['swupdate-www', > 'u-boot-fw-utils'] > > ERROR: Required build target 'swupdate-image' has no buildable providers. > > Missing or unbuildable dependency chain was: ['swupdate-image', > 'swupdate-www', 'u-boot-fw-utils'] > > As, it is Intel board, the bootloader should not be uboot, so why it is > throwing that error. I am just a beginner in Yocto.. Forgive me if I > made a small mistake. Did anyone have steps of how to get started for > swupdate on Intel Yocto. > > Thanks and Regards, > Mohammad Jamal, > NCR Corporation -- ___ meta-intel mailing list meta-intel@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-intel
Re: [meta-intel] Apollo Lake Yocto BSP
What board are you booting specifically? Looking at the UART (serial) output can help to diagnose booting problems. --S On 3/22/18 7:51 PM, Mohammad, Jamal M wrote: > Thanks both of you.. I am now trying the intel website link.. I tried the > default master branch of meta-intel with master branch of poky.. > Core-image-minimal target was working fine.. But when I booted using > core-image-sato target, Yocto Splash screen was displayed and the screen went > blank.. What does this mean... > > -Original Message- > From: Tan, Jui Nee [mailto:jui.nee@intel.com] > Sent: Friday, March 23, 2018 8:17 AM > To: Stephano Cetola ; Mohammad, Jamal M > > Cc: meta-intel@yoctoproject.org > Subject: RE: [meta-intel] Apollo Lake Yocto BSP > > Hi, > > > > Alternatively, you can refer to this link: > https://urldefense.proofpoint.com/v2/url?u=https-3A__www.yoctoproject.org_bsps_jethro203-2Dleaf-2Dhill_&d=DwIGaQ&c=gJN2jf8AyP5Q6Np0yWY19w&r=4h__2a8-7N65qoDnmtsyGh_QYq3kPCn-Loy2L0LHnCs&m=MdWAB4reZSNS7PHk74O08IadCyL8SMfJ6BHORLUNf-A&s=ETjROtUwhwzvGw3-iARW7k4XX01FFTdRd_v9ixkaGJY&e= > to get Apollo Lake-i Yocto Project BSP and build the image. > > > > Thanks, > > Juinee > > > >> -Original Message- > >> From: meta-intel-boun...@yoctoproject.org [mailto:meta-intel- > >> boun...@yoctoproject.org] On Behalf Of Stephano Cetola > >> Sent: Friday, March 23, 2018 1:48 AM > >> To: Mohammad, Jamal M > >> Cc: meta-intel@yoctoproject.org > >> Subject: Re: [meta-intel] Apollo Lake Yocto BSP > >> > >> On 3/21/18 9:58 PM, Mohammad, Jamal M wrote: > >>> Does it mean, I cannot use the default meta-intel layer and have to > >> follow the Intel document. > >>> > >>> -Original Message- > >>> From: Anuj Mittal [mailto:anuj.mit...@intel.com] > >>> Sent: Wednesday, March 21, 2018 9:12 AM > >>> To: Mohammad, Jamal M ; meta- > >> in...@yoctoproject.org > >>> Subject: Re: [meta-intel] Apollo Lake Yocto BSP > >>> > >>> On 03/19/2018 07:03 PM, Mohammad, Jamal M wrote: > >>>> Hi Guys, > >>>> > >>>> We have Apollo Lake based board. And want to install Yocto Image. Does > >>>> the meta-intel master branch has BSP Support for Apollo Lake. > >>>> > >>>> git clone git://git.yoctoproject.org/meta-intel > >>>> > >>>> If not where can I find the BSP Support Layer for Apollo Lake. If yes > >>>> what branch of poky should I use. > >>>> > >>> > >>> You can refer to the BSP documentation here: > >>> > >>> https://urldefense.proofpoint.com/v2/url?u=https- > >> 3A__www.intel.com_content_www_us_en_embedded_products_apollo- > >> 2Dlake_technical-2Dlibrary.html&d=DwID- > >> g&c=gJN2jf8AyP5Q6Np0yWY19w&r=4h__2a8-7N65qoDnmtsyGh_QYq3kPCn- > >> Loy2L0LHnCs&m=4i-KLG-O9Nw8nR9XSeNEt- > >> mY_ykTyzcI8FObTaCjC1k&s=oYpdE6x9YRj3mGzMPnMQ0e1soX035puKW8MxA_6W4nc&e= > >>> > >>> Thanks, > >>> > >>> Anuj > >>> > >> > >> You are welcome to build your own BSP using the meta-intel layer, as it > >> has support for Apollo Lake SoC's. The BSP is intended to make support > >> easier when working with your corporate representative. > >> > >> The published BSPs are also a good reference guide for building your own > >> BSP as they will enable many features that may not be enabled by default > >> in meta-intel. > >> > >> Cheers, > >> Stephano > >> -- > >> ___ > >> meta-intel mailing list > >> meta-intel@yoctoproject.org > >> https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.yoctoproject.org_listinfo_meta-2Dintel&d=DwIGaQ&c=gJN2jf8AyP5Q6Np0yWY19w&r=4h__2a8-7N65qoDnmtsyGh_QYq3kPCn-Loy2L0LHnCs&m=MdWAB4reZSNS7PHk74O08IadCyL8SMfJ6BHORLUNf-A&s=kqZqbjJUqSN2bU9SJh38GQ3Zn9eeL6uCkpTj_qnzpZE&e= > -- ___ meta-intel mailing list meta-intel@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-intel
Re: [meta-intel] Apollo Lake Yocto BSP
On 3/21/18 9:58 PM, Mohammad, Jamal M wrote: > Does it mean, I cannot use the default meta-intel layer and have to follow > the Intel document. > > -Original Message- > From: Anuj Mittal [mailto:anuj.mit...@intel.com] > Sent: Wednesday, March 21, 2018 9:12 AM > To: Mohammad, Jamal M ; > meta-intel@yoctoproject.org > Subject: Re: [meta-intel] Apollo Lake Yocto BSP > > On 03/19/2018 07:03 PM, Mohammad, Jamal M wrote: >> Hi Guys, >> >> We have Apollo Lake based board. And want to install Yocto Image. Does >> the meta-intel master branch has BSP Support for Apollo Lake. >> >> git clone git://git.yoctoproject.org/meta-intel >> >> If not where can I find the BSP Support Layer for Apollo Lake. If yes >> what branch of poky should I use. >> > > You can refer to the BSP documentation here: > > https://urldefense.proofpoint.com/v2/url?u=https-3A__www.intel.com_content_www_us_en_embedded_products_apollo-2Dlake_technical-2Dlibrary.html&d=DwID-g&c=gJN2jf8AyP5Q6Np0yWY19w&r=4h__2a8-7N65qoDnmtsyGh_QYq3kPCn-Loy2L0LHnCs&m=4i-KLG-O9Nw8nR9XSeNEt-mY_ykTyzcI8FObTaCjC1k&s=oYpdE6x9YRj3mGzMPnMQ0e1soX035puKW8MxA_6W4nc&e= > > Thanks, > > Anuj > You are welcome to build your own BSP using the meta-intel layer, as it has support for Apollo Lake SoC's. The BSP is intended to make support easier when working with your corporate representative. The published BSPs are also a good reference guide for building your own BSP as they will enable many features that may not be enabled by default in meta-intel. Cheers, Stephano -- ___ meta-intel mailing list meta-intel@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-intel
Re: [meta-intel] galileo
On 3/11/18 2:10 PM, Trevor Woerner wrote: > Hi, > > I realize that the Galileo board has been completely abandoned; I'm not > looking for "official" information, but I'm hoping someone would be > willing to provide some anecdotal information... perhaps offline? Abandoned but not forgotten. tldr: use this kernel config with 4.9 or 4.14 or probably 4.15: https://github.com/andy-shev/linux/tree/galileo see: arch/x86/configs/i386_defconfig I did some work recently on a project that was using the Quark chip on a board whose design heavily borrowed from Galileo. We were able to ship with a modern kernel off rocko, but I can't help much with Arduino functionality. We were using that UART for something completely different :). > > I thought it would be a fun exercise to investigate updating the Linux > image and arduino-IDE-toolchain for my Galileo Gen2 board. Unfortunately > I've hit some walls and was looking for some ideas. > > With its LOCKing problem[*1], projects like Yocto and Buildroot are > natural homes for Galileo support. It looks as though Galileo support > was added to The Yocto Project somewhere around Dylan [1.4] with > https://github.com/intel/Galileo-Runtime.git. Using the sub-repositories > found there and a virtual machine I'm able to build a working toolchain > which I can install in my Arduino 1.8.5 IDE to build, upload, and run > Blink. I can also build a rootfs image, but there isn't much in the way > of guidance on how to get the resulting artifacts cobbled together onto > an SDcard. But if I leave the SDcard slot empty, I can boot the default > flash image that was shipped with the board (which is based on Dylan), > and the IDE and sketches all work[*2]. Many moons ago there was a wks file for galileo: http://git.yoctoproject.org/cgit/cgit.cgi/meta-intel/commit/?id=272d4cb66b8e553e3fc27455ca3bb8e70472c510 http://git.yoctoproject.org/cgit/cgit.cgi/meta-intel/commit/?id=0109c3d7f2c3ae269842b6126a65323a6dd4608b In my experience it is easier to use the default meta-intel rocko build for Quark and manually add a grub.conf to the correct location. To be fair I did not spend much time on automating this process. > > After Dylan, Galileo-Runtime.git appears to have been abandoned (it's > still stuck at Dylan) and meta-intel-quark and meta-intel-galileo > appear... for Daisy [1.6]. Building with these layers (with everything > setup for Daisy) doesn't work out-of-the-box due to some complaining > about circular dependencies of initscripts on initscripts. I've tried > several different things and combinations, but I can't successfully > build an image or toolchain using these layers. These layers also have > Dizzy [1.7] branches, so I gave those a whirl too without any success > either. > > After Dizzy, meta-intel-quark and meta-intel-galileo appear to have been > abandoned and Quark/Galileo support migrated to meta-intel (and was > subsequently removed after Rocko [2.4]). Yes, this seems to be the basic idea. Quark support was rolled into meta-intel, and then removed after rocko (machine intel-quark is now gone in master). When I built from rocko for that machine and boot on Galileo the kernel config doesn't enable anything useful, so I had to switch to the Andy's kernel config (see above). > Along that path, the bootloader > moved from grub0 to gummiboot to systemd-boot. The out-of-tree binutils > -mquark-strip-lock patch was upstreamed as the -momit-lock-prefix > option. The meta-intel layer included wic support making it dead-simple > to create an SDcard from the build artifacts (yay!). Uclibc support died > with Krogoth [2.1] (boo). And the suggested kernel for Quark moved from > upstream linux-3.8 with about two dozen patches, to linux-intel-4.9 > (as-is)... and this is where I'm stuck. Keep in mind that meta-intel did not support Galileo, only Quark. When the kernel stuff got merged into meta-intel (and linux-intel) they didn't feel the need to add / support a Galileo kernel config (them, whoever they were). > > In the early days it doesn't seem like there was much distinction > between Quark and Galileo, they were mostly synonymous. But by the time > we get to Rocko, we find that the linux-intel kernel has support for > Quark, but nothing for Galileo. When I boot the factory-installed Dylan > image, I find loads of stuff under /sys/class/gpio, /sys/class/pwm, and > /sys/class/platform which are what the Arduino code uses for > identification and interaction with the Arduino headers. When I run > linux-intel[*3] I have a /sys/class/gpio that only claims 8 gpios are > available for use, none of which appear to relate to the Arduino > headers. Was the Galileo support never "upstreamed"? Not even in Intel's > own kernel fork? Again, check out Andy's config changes. I got the Galileo to work after banging my head against the config for a week, but he does it nicer and cleaner. > > With Rocko I can build a bootable image (yay!!) but without proper > kernel support for Galileo
Re: [meta-intel] Bare minimum configuration
On 3/18/18 3:56 PM, Tim Jones wrote: > Hi Folks, > > I've now gotten a good feel for how Yocto puts things together, but I'm > running into a wall trying to find the package selections. What I'm > shooting for is a meta-intel build with the hardware as provided, but I > want to remove everything from the package list except for a few > specific items - busybox, a custom python configuration, dhcp tools, > vim, init, and grub. > > Is there a document that describes paring things down to this level? > > Thanks, > Tim > What is your goal with the image you are describing? It sounds like you are heading for on-target development. --S -- ___ meta-intel mailing list meta-intel@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-intel
Re: [meta-intel] Rocko build of meta-intel reports MACHINE=intel-corei7-64 is invalid
On 3/17/18 3:13 PM, Tim Jones wrote: > Hi Stephano, > > Thanks. The oddity is that I added the meta-intel path to the bblayers > config file manually. After deleting my addition and then using the > bitbake-layers command you listed, it's taken off. Huh, that is strange. The tool is a convenience and doesn't do anything fancy that I know of. Glad it worked for you. Cheers, Stephano > > -- > Tim > >> On Mar 17, 2018, at 2:45 PM, Stephano Cetola >> wrote: >> -- ___ meta-intel mailing list meta-intel@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-intel
Re: [meta-intel] Rocko build of meta-intel reports MACHINE=intel-corei7-64 is invalid
On 3/17/18 1:39 PM, Tim Jones wrote: > Hi Folks, > > I've prepped a build platform and installed rocko and meta-intel from > the GIT repo in the proper hierarchy. I then made sure that the only > active MACHINE line in my local.conf was MACHINE ?= "intel-corei7-64" as > outlined in the README. > > Upon running bitbake of core-image-sato, bitbake exits with > "MACHINE=intel-corei7-64 is invalid". > > Any tips on a resolution? > > Tim > > You have not added the meta-intel layer to your bblayers.conf. You can use the bitbake-layers tool to do that: $ bitbake-layers add-layer /[path]/[to]/[your]/meta-intel Cheers, Stephano -- ___ meta-intel mailing list meta-intel@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-intel
[meta-intel] [PATCH] tlk: layer.conf: Add proper priority and pattern
It is expected that every layer provides a priority and its
BBFILE_PATTERN. This includes the needed information in
layer.conf.
Signed-off-by: Stephano Cetola
---
meta-tlk/conf/layer.conf | 4
1 file changed, 4 insertions(+)
diff --git a/meta-tlk/conf/layer.conf b/meta-tlk/conf/layer.conf
index 38b0e0c..fc10405 100644
--- a/meta-tlk/conf/layer.conf
+++ b/meta-tlk/conf/layer.conf
@@ -4,3 +4,7 @@ BBPATH .= ":${LAYERDIR}"
# We have recipes-* directories, add to BBFILES
BBFILES += "${LAYERDIR}/recipes-*/*/*.bb \
${LAYERDIR}/recipes-*/*/*.bbappend"
+
+BBFILE_COLLECTIONS += "tlk"
+BBFILE_PATTERN_tlk := "^${LAYERDIR}/"
+BBFILE_PRIORITY_tlk = "5"
--
2.7.4
--
___
meta-intel mailing list
meta-intel@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-intel
