Hi, Bottom line up front, built fsl-community-bsp dunfell for imx8mmevk and Linux 5.4 kernel hangs on boot. So far I've been NXP official releases. I really needed the 5.4 kernel so was excited when I

Sure, here you go: bitbake core-image-minimal Loading cache: 100% |##################################################################################################| Time: 0:00:00 Loaded 3244 entries

Here is the one from the fsl-community-bsp build using fslc-wayland distro and building core-image-base: hutch@Gondor:~/yocto/imx8/fsl-community-bsp/build/tmp/deploy/images/imx8mmevk$ bitbake core-ima

You're right. I see: [ 1.337691] mmc0: CQHCI version 5.10 [ 1.341666] mmc1: CQHCI version 5.10 [ 1.345690] mmc2: CQHCI version 5.10 [ 1.381326] mmc2: SDHCI controller on 30b60000.mmc [30b60000.mmc] us

Update. I went into kernel config and gutted a bunch of setting for things I don't care about (wow ... 5.4 sure has a bunch of new stuff). I turned off PCI, bluetooth, wifi etc. I really think turning

I don't think so. The core-image-minimal image I built with poky as distro boots clean when I replace the kernel with the one where I went into make menuconfig and turned off PCI and some other things

Andrey, I changed my local.conf and doing another buid to test with. I added the first two lines, the rest is stock the way it was created: PREFERRED_PROVIDER_virtual/kernel = "linux-fslc-imx" PREFERR

Which imx6 board are you using specifically? Regards, Brian

#define #yocto #compilation #meta-freescale

Hi, I'm looking into doing the rt patch against linux-fslc-imx 5.4.51. Doesn't look like anyone has done this for the imx8mm. I see a recipe for linux-fslc-imx-rt 4.1.-1.0.x but looks like it's for th

I'll answer my own question ... I applied the 5.4.54 rt patch and it worked. Built rt-tests and ran cyclictest and pi_stress so I'm happy. At this point looks like things are working as far as I can t

When the sdcard is created, the u-boot environment has fdt_file defaulted to imx8mm-evk.dtb. I've not yet figured out how to override the recipe to specify which .dtb file should be used. For sdcard b

Ha, ha, I figured there was already some way to do it and I just overlooked it or wasn't smart enough to figure it out. Yeah, you can do anything with good ole sed. I plan to switch back to using the

Just built latest Freescale Community BSP core-image-minimal (kernel 5.4.67 was built) for imx8mm-evk and firmware-imx is not included in sdcard image ... which I think is why I'm getting messages lik

I'm using core-image-minimal because I have a custom board based off of imx8mm evk but don't use wifi, bluetooth, video, touch pad etc. so I don't want all the "stuff" that comes in core-image-base. J

Another update ... decided to build core-image-base just in case it was related to core-image-minimal missing something ... I get the same sdma errors. So I add IMAGE_INSTALL_append = " firmware-imx-s

Hi Otavio, That's great! Just curious when was this done as I did a fresh repo init/sync of dunfell yesterday afternoon. repo init -u https://github.com/Freescale/fsl-community-bsp-platform -b dunfell

Excellent! Thank you! I got to poking around in one of the include files and looks like I should have done: MACHINE_FIRMWARE = 'MACHINE_FIRMWARE_append_mx7d' ... instead of: IMAGE_INSTALL_append = " f

So I did build of core-image-minimal with local.conf containing MACHINE_FIRMWARE = 'MACHINE_FIRMWARE_append_mx7d' and still got the sdma errors. No firmware-imx packages were installed and no /lib/fir

More background information in case it matters. I did my original setup with: EULA=1 MACHINE=imx8mmevk DISTRO=poky source setup-environment build ... because I don't want/need graphics etc. After Otav

... 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.??? Is poky what's causing my pai