Build image for more devices beyond IMX6 EVK

キャンセル
次の結果を表示 
表示  限定  | 次の代わりに検索 
もしかして: 

Build image for more devices beyond IMX6 EVK

ソリューションへジャンプ
2,429件の閲覧回数
jupiter_hce
Contributor III
Hi,

I was building and running Yocto images on iMX6 EVK using https://github.com/Freescale/meta-freescale, I am going to build a new Yocto image for a product using i.MX-6ULZ MCU, there are more extra devices such as Flash, real time clock etc.

I think there are a couple of modifications I need do:

- Replace iMX6 EVK device tree by new hardware device tree (that will be in meta-linux).
- Can I still use the BSP recipe https://github.com/Freescale/meta-freescale for the hardware Are there anything I need to change or make recipe append for adding and extending BSP recites for Flash, real time clock etc?

Thank you.

Kind regards,

- jupiter

ラベル(3)
0 件の賞賛
返信
1 解決策
2,300件の閲覧回数
gusarambula
NXP TechSupport
NXP TechSupport

Hello Jupiter,

There are two BSPs, the BSP Release and the Community BSP. You can see the differences between the two on the following thread:

https://community.nxp.com/message/409716?commentID=409716#comment-409716

In both cases you can use them as a starting point for your application and add packages or appends as requires, which is part of the advantages of Yocto. You can see a bit more on how to manage this on the Yocto Reference Manual and also on the BSP Documentation.

I hope this helps!

Regards,

元の投稿で解決策を見る

0 件の賞賛
返信
4 返答(返信)
2,301件の閲覧回数
gusarambula
NXP TechSupport
NXP TechSupport

Hello Jupiter,

There are two BSPs, the BSP Release and the Community BSP. You can see the differences between the two on the following thread:

https://community.nxp.com/message/409716?commentID=409716#comment-409716

In both cases you can use them as a starting point for your application and add packages or appends as requires, which is part of the advantages of Yocto. You can see a bit more on how to manage this on the Yocto Reference Manual and also on the BSP Documentation.

I hope this helps!

Regards,

0 件の賞賛
返信
2,300件の閲覧回数
jupiter_hce
Contributor III

Thanks gusarambula, so the url = git://git.yoctoproject.org/meta-freescale is NXP official release project, correct?

I've actually already had a Yocto build system based on OE, that building system can build a Yocto image running on imx6 EVK, how can simply replace url = git://git.yoctoproject.org/meta-freescale by the community fsl BSP? I don't need to replace my whole Yocto build system based on url = https://github.com/Freescale/fsl-community-bsp-platform.

Another thing is where and how can I customize the device tree for the community project? I could only find recipes-kernel/linux/linux-fslc/imx6q-var-som-vsc.dts which is not for imx6ull, should I create the dts myself?

Thank you.

Kind regards,

- jupiter

0 件の賞賛
返信
2,300件の閲覧回数
jupiter_hce
Contributor III

I now believe that  url = git://git.yoctoproject.org/meta-freescale is the community FSL BSP as the OpenEmbedded/Yocto BSP layer for Freescale's in platforms in README. I have my own hardware device tree imx6ull_customized_device.dts, but where should I add it to? How does the kernel know the dtb file needs be compiled based on imx6ull_customized_device.dts?

Thank you.

- jh

0 件の賞賛
返信
2,300件の閲覧回数
gusarambula
NXP TechSupport
NXP TechSupport

Hello Jupiter,

You can find more details on how the device tree works and is customized on the following document:

https://community.nxp.com/docs/DOC-329664

Device Trees compiled are listed on the Makefile on arch/arm/boot/dts, all these will be compiled and then it's the bootloader who determines which device tree to use depending on the MACHINE selected.

I hope this helps!

Regards,