Hi everyone and thank you for the comments/ideas etc. I found my problem. In the new imx8mm-evk.dts for 5.10.69 the flexspi node has spi-tx-bus-width = <1>; and in all the previous kernel versions it

Hello, I found my problem. In the new imx8mm-evk.dts for 5.10.69 the flexspi node has spi-tx-bus-width = <1>; and in all the previous kernel versions it was spi-tx-bus-width = <4>; so when moving our

Does imx8mm have tools to find pinmux conflicts, see pins in use etc.? Regards, Brian

Hi, At first I was chasing why fw_setenv (see thread "fw_printenv works but fw_setenv does not after switching to linux-fslc-imx 5.10.69 from linux-fslc-imx 5.4.112") quit working after updating to li

Hi Peter, Update below. No. Apparently not. I've compared kernel .config and device tree source from 5.4 series kernel and 5.10 series kernel and I cannot find an explanation for this but the followin

Hi Peter, You got me! In my previous build I just had libubootenv and that appeared to work for my dunfell build somehow even that release shows fw_printenv/fw_setenv to be in the libubootenv-bin pack

Update. I booted my board via NFS using core-image-base from the hardknot build I got 5.10.69 from and libubootenv. I copied in fw_printenv/fs_setenv from tmp/work/imx8mm_ddr4_evk-poky-linux/libuboote

Hi Fabio, Nope, cat /proc/mtd looks good. Same order as in previous kernels. It does not. It shows no signs of a problem, returns no errors or warnings at all. It "looks" like it worked normal but doe

On Mon, Nov 8, 2021 at 3:03 AM Peter Bergin <peter@...> wrote: Hi Peter, Hi Brian, On 2021-11-08 05:01, Brian Hutchinson wrote: Hi, I'm using u-boot U-Boot 2019.04-4.19.35-1.1.0+g4d377539

Hi, I'm using u-boot U-Boot 2019.04-4.19.35-1.1.0+g4d377539a1 in pre-programmed NOR flash and was using linux-fslc-imx 5.4.114 kernel and fw_printenv/fw_setenv were working fine. After upgrading to li

REFERRED_PROVIDER_virtual/kernel = "linux-fslc-imx"Hi Andrey, So I did a repo sync in my hardknott checkout. Then changed to IMX_DEFAULT_BSP = "nxp" in imx8mm-evk.inc and added PREFERRED_PROVIDER_virt

Hey Andrey, So I was in error. I looked back at the local.conf where our 5.4 kernel came from that we are happy with (and has multi-lane) and it was linux-fslc-imx so I guess it's linux-fslc with some

Hey Fabio, I went back and looked at my 5.4 kernel that has the multi-lane support. My local.conf has REFERRED_PROVIDER_virtual/kernel = "linux-fslc-imx" Regards, Brian

Hi Andrey, I really would like to stick with linux-fslc since that's what we've been using for more than a year now. Kind of scared to switch back to linux-fslc-imx (I'll try to do better with my term

I hoped folks would know what I was talking about without getting too far into the weeds. But I guess I need to explain more. The older 5.4 kernels (and even 4 series kernels) had a imx8mm-evk.dts sai

And that link I accidentally posted by itself https://source.codeaurora.org/external/imx/linux-imx/tree/sound/soc/fsl/fsl_sai.c?h=lf-5.10.y ... is the reference I mentioned where I see multi-lane supp

Hi, First, forgive me for posting a link in an post with no context ... I hit a wrong button and accidentally sent before ready. Bottom line up front. How can I get a 5.10 kernel with multi-lane suppo

https://source.codeaurora.org/external/imx/linux-imx/tree/sound/soc/fsl/fsl_sai.c?h=lf-5.10.y

Anyone? Anyone?

Hate to bring up an old thread again but I'm back to trying to pair down my image size and trying to use core-image-minimal and having issues with firmware-imx-sdma-imx7d & sdma-imx7d.bin If I just bu