From mboxrd@z Thu Jan 1 00:00:00 1970 Subject: Re: How to get firmware-imx for imx8mm evk into sdcard image? I'm getting firmware loading errors for sdma-imx7d.bin etc. To: meta-freescale@lists.yoctoproject.org From: "Brian Hutchinson" X-Originating-Location: Big Island, Virginia, US (184.105.1.51) X-Originating-Platform: Linux Firefox 81 User-Agent: GROUPS.IO Web Poster MIME-Version: 1.0 Date: Tue, 06 Oct 2020 13:44:21 -0700 References: In-Reply-To: Message-ID: <27157.1602017061306262562@lists.yoctoproject.org> Content-Type: multipart/alternative; boundary="fvMFcALfUdpoTFmxzn5g" --fvMFcALfUdpoTFmxzn5g Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable On Tue, Oct 6, 2020 at 01:22 PM, Andrey Zhizhikin wrote: >=20 > Hello Brian, >=20 > On Tue, Oct 6, 2020 at 9:51 PM Brian Hutchinson > wrote: >=20 >> ... 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, >> video, touchscreen etc.??? >=20 > 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. >=20 > 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 memor= y serves me right a core-image-minimal would not boot.=C2=A0 Only core-imag= e-base images did and they were quite large. I do need to create my own distro but kind of would like to start from cor= e-image-minimal and build up rather than take something like fsl-wayland an= d try to figure out what I don't need.=C2=A0 Being new to NXP family this a= pproach "feels" more logical. >=20 >=20 >> Is poky what's causing my pain? >=20 > 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 "". >=20 >=20 >> I've been doing TI based builds forever and recently switched over to N= XP >> based products so still learning the lay of the land. I finally discove= red >> I don't think I want to be building based off NXP releases from codeaur= ora >> and that Freescale is the better base for our products but not 100% cle= ar >> what distro's are available and which ones I should focus on. >=20 > Those distros are located in a meta-freescale-distro layer, you can > peek there to see what's available. I'll look.=C2=A0=C2=A0 Thanks Regards, Brian --fvMFcALfUdpoTFmxzn5g Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: quoted-printable On Tue, Oct 6, 2020 at 01:22 PM, Andrey Zhizhikin wrote:
Hello Brian,

On Tue, Oct 6, 2020 at 9:51 PM Brian H= utchinson <b.hutchman@gmail.com> wrote:
... what "distro" 'should' I be using since I have a custom bo= ard that's based on imx8mm evk but I don't necessarily want/need wifi, blue= tooth, video, touchscreen etc.???
I suggest you go with your own distro then, as you can leverage the
D= ISTRO_FEATURES in it yourself. You can either take any of 'fsl-'
prefi= xed 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 t= o 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'), a= nd
so far it has proven to be working quite well. I also do sanity bui= ld
and run the 'fsl-wayland' off the master on imx8mmevk to make sure<= br />there are no regressions.
When I did NXP released builds I would use fsl-wayland distro but if memor= y serves me right a core-image-minimal would not boot.  Only core-imag= e-base images did and they were quite large.

I do need to create= my own distro but kind of would like to start from core-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 approach "feels" more= logical.

Is poky what's causing my pain?
You can see what distro features you have included when you do
'bitba= ke -e' and search for DISTRO_FEATURES. If you have (and
according to w= hat 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 "<unneeded list>".

I've been doing TI based builds forever and recently switched = over to NXP based products so still learning the lay of the land. I finally= discovered I don't think I want to be building based off NXP releases from= codeaurora 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
p= eek there to see what's available.
I'll look.   Thanks

Regards,

Brian --fvMFcALfUdpoTFmxzn5g--