From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail-vs1-f52.google.com (mail-vs1-f52.google.com [209.85.217.52]) by mx.groups.io with SMTP id smtpd.web11.9516.1602064632066985068 for ; Wed, 07 Oct 2020 02:57:12 -0700 Authentication-Results: mx.groups.io; dkim=pass header.i=@gmail.com header.s=20161025 header.b=D2Q9rKQR; spf=pass (domain: gmail.com, ip: 209.85.217.52, mailfrom: andrey.z@gmail.com) Received: by mail-vs1-f52.google.com with SMTP id r24so827861vsp.8 for ; Wed, 07 Oct 2020 02:57:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=wbs/1864ib+D4MjPK3Ts/CbIDdcfD04kL6ZXN2WTvs0=; b=D2Q9rKQRD8p5aBCV7sgtoqCBjoeCVR8a6pyj4s0n7zQFFH6XGPBxZB1dBKB5Wrw6um RniFrzhTkCQ4XblEQFJnrDbFxjnvPToYyJAEAX4oIOUyXCPuvveEwyvr4jsr0CYITUfN AERMgSBZLCdGxF7NVOr0S21D/3CUrchV4bo/qMFqGvEvoDKEc01BAOG474dZ8ySHNSf7 zPmBpCcru9bKChUOKEMhdeXQlCmqfeqOXBfS6GT9pJypjJpFd0pmn5z211/BrTyc6m1S AYijJ9Lh/Z+6ELUSIocVZRtcAFgfCnIHQ6OF0ShYBc4KF2tWu/rKXUzraBsB3E+i8oLT hHrA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=wbs/1864ib+D4MjPK3Ts/CbIDdcfD04kL6ZXN2WTvs0=; b=qaMKdOpEZ+EOvbQ0aSwImETpPYxL7GsAlxuTXrkl6hyGK/QwbZyqsIUN+O44e0GgTo HmvqOdlwksIAzr891wLoRZ29oxBss2GgGcGqeKjDsWytKYppB5cjfNuUWs7G8f3BUwEm SzOm7Ov+Md+OnI3N+oPFbS4tTIki7mLjQeI/w47uTI2cDKQpFR3lF3WdYQt3ujlAJVih R+QmvpbhQVQFjxP1dIXu0G5WBHavAh62dBkbrVd4CWaJ0ml0n8kKnZucTO5vsbTqHTLI T4TLraL20qdkxdeFjINB1Hdj0c/l9P3XZvG69XRspPYS4Cmd1+3ds0fBJZias84BvkCA +ukg== X-Gm-Message-State: AOAM532Cun7PdeIROFzgnlgyrrtYhfLvxmtjaom4YC5b31OVYfTFp8wT Jq/J93NW8j2LzIa8PpbwMfzTb3nPCpCcj4oxnHA= X-Google-Smtp-Source: ABdhPJyF7mENW4bYx7DMi00s3mxiaDWzj5GLvE+gVnKVpm4M9YdkV9Q6dZzULMAuDw+u/WfKxpBsk5rOyuU7Mb9GN48= X-Received: by 2002:a67:fdc6:: with SMTP id l6mr1099673vsq.31.1602064631194; Wed, 07 Oct 2020 02:57:11 -0700 (PDT) MIME-Version: 1.0 References: <27157.1602017061306262562@lists.yoctoproject.org> In-Reply-To: <27157.1602017061306262562@lists.yoctoproject.org> From: "Andrey Zhizhikin" Date: Wed, 7 Oct 2020 11:56:59 +0200 Message-ID: Subject: Re: [meta-freescale] How to get firmware-imx for imx8mm evk into sdcard image? I'm getting firmware loading errors for sdma-imx7d.bin etc. To: Brian Hutchinson Cc: meta-freescale@lists.yoctoproject.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Tue, Oct 6, 2020 at 10:44 PM Brian Hutchinson wro= te: > > On Tue, Oct 6, 2020 at 01:22 PM, Andrey Zhizhikin wrote: > > Hello Brian, > > On Tue, Oct 6, 2020 at 9:51 PM Brian Hutchinson w= rote: > > ... what "distro" 'should' I be using since I have a custom board that's= based on imx8mm evk but I don't necessarily want/need wifi, bluetooth, vid= eo, touchscreen etc.??? > > I suggest you go with your own distro then, as you can leverage the > DISTRO_FEATURES in it yourself. You can either take any of 'fsl-' > prefixed distros over 'poky' if you need some NXP proprietary > components (e.g. VPU, GPU, etc), or take any of 'fslc-' prefixed ones > if you want to stay with mainline. Please note - I do not say that > 'poky' would not work here! :) It is just a reference distro from > Yocto Project, which targets qemu on the first place, but also works > well for real HW. > > This is the way we build our distro (derived from 'fsl-wayland'), and > so far it has proven to be working quite well. I also do sanity build > and run the 'fsl-wayland' off the master on imx8mmevk to make sure > there are no regressions. > > When I did NXP released builds I would use fsl-wayland distro but if mem= ory serves me right a core-image-minimal would not boot. Only core-image-b= ase images did and they were quite large. > > I do need to create my own distro but kind of would like to start from c= ore-image-minimal and build up rather than take something like fsl-wayland = and try to figure out what I don't need. Being new to NXP family this appr= oach "feels" more logical. I think you're mixing up 2 conceptual points here: distro vs image. You can have a wayland distro, but only include a handful of packages and features of it into the image. Distro does not define the content of the image, image recipe does. Section 4.3.2. of Yocto Overview Manual gives a very nice overview of those concepts: https://www.yoctoproject.org/docs/3.1.2/overview-manual/overview-manual.ht= ml#metadata-machine-configuration-and-policy-configuration > > Is poky what's causing my pain? > > You can see what distro features you have included when you do > 'bitbake -e' and search for DISTRO_FEATURES. If you have (and > according to what you say - you do :) ) some pieces you do not need - > you can always either not include them in your custom distro, or use > DISTRO_FEATURES_remove =3D "". > > I've been doing TI based builds forever and recently switched over to NX= P based products so still learning the lay of the land. I finally discovere= d I don't think I want to be building based off NXP releases from codeauror= a and that Freescale is the better base for our products but not 100% clear= what distro's are available and which ones I should focus on. > > Those distros are located in a meta-freescale-distro layer, you can > peek there to see what's available. > > I'll look. Thanks > > Regards, > > Brian >=20 > --=20 Regards, Andrey.