Date
1 - 2 of 2
meta-imx issue with Hardknott #hardknott
|
Ken Davidson
There is no subgroup for meta-imx, so I'm guessing this one is the closest.
I'm trying to create a Hardknott version of Yocto for the i.MX 8M Mini board that we're using. The manufacturer (Congatec) only has code up to Zeus, so I'm starting with the Hardknott version of fsl-community-bsp and am trying to add in code from the manufacturer's Zeus implementation. I've run into a problem with the Hardknott release of meta-imx. Under meta-bsp/recipes-bsp/u-boot, the u-boot-imx_2021.04.bb recipe is trying to find u-boot-imx-common.inc. However, the only file present is u-boot-common.inc. This is true for all three Hardknott branches of meta-imx. The equivalent folder under meta-freescale does include the proper file. Is this a bug or am I missing something? Or should I be using only meta-freescale and abandon meta-imx? Thanks.
|
|
|
|
Otavio Salvador
Hello Ken,
Em sex., 17 de dez. de 2021 às 19:18, Ken Davidson <ken.davidson@...> escreveu: There is no subgroup for meta-imx, so I'm guessing this one is the closest.This is something which is expected to happen when you mix branches ... I'd suggest you to use meta-freescale and move to mainline releases if it is supported. If it doesn't, you should contact Congatec support and ask them. I've run into a problem with the Hardknott release of meta-imx. Under meta-bsp/recipes-bsp/u-boot, the u-boot-imx_2021.04.bb recipe is trying to find u-boot-imx-common.inc. However, the only file present is u-boot-common.inc. This is true for all three Hardknott branches of meta-imx.We try to be as close as possible to meta-imx; eventually they diverge when NXP does new releases but they are pretty close nowadays. -- Otavio Salvador O.S. Systems http://www.ossystems.com.br http://code.ossystems.com.br Mobile: +55 (53) 9 9981-7854 Mobile: +1 (347) 903-9750
|
|
|