MYS-6ULX yocto build error

取消
显示结果 
显示  仅  | 搜索替代 
您的意思是: 
已解决

MYS-6ULX yocto build error

跳至解决方案
2,047 次查看
sdi1100002
Contributor II

Hello NXP forum,

We have a MYirtech MYS-6ULX IoT, the vendor supports their 4.1 kernel and u-boot and a layer meta-myir which builds on Yocto 2.1 (korgoth)/Ubuntu 16.04.5 LTS 64-bit as per their instructions. Switching distribution is not a solution neither is using outdated software. I 'm in Debian 9. As of now, I cannot make it build, the latest error is about perl.

I have installed perlbrew and perl-5.22.1 through perlbrew and then "perlbrew switch perl-5.22.1", it didn't work.

Has anyone managed to work with the board on 2019? Could you share some info or experience? Perhaps someone knows if I should try to build their kernel to Yocto latest instead?

I attached the error log for "bitbake openssl".

Thanks.

标签 (2)
0 项奖励
1 解答
1,878 次查看
gusarambula
NXP TechSupport
NXP TechSupport

Hello Katerina Voulgary,


There have been works on newer Poky releases, you can find more details on the BSP platform github:
https://github.com/Freescale/fsl-community-bsp-platform


Documentation on https://freescale.github.io is a bit far behind, but work is continuing over the newer branches. I would recommend against using the latest one as it may still have a lot of pending work but there are newer branches than 2.4 that are very stable now.


OtavioSalvador, would you why the https://freescale.github.io has not been updated with the latest branches?


Regards,

在原帖中查看解决方案

5 回复数
1,878 次查看
gusarambula
NXP TechSupport
NXP TechSupport

Hello Katerina Voulgary,

The MYS-6ULX module is manufactured and supported by MYIR so they may be able to provide more help on this regard.

Their BSP is probably based on the Community BSP, which means that Ubuntu is required as host. While Yocto can run on Debian, the Community BSP requires some packages from Ubuntu. You could port the BSP yourself but it’s not a trivial task.

My apologies for the inconvenience.
Regards,

1,878 次查看
sdi1100002
Contributor II

@gusarambula: Can I ask you then about the Community BSP? It has stopped being maintained from 2016, correct? If I am going to port the BSP as you say, it means I will aim to make it work for meta-freescale official? Is there any reason to try for the latest Community BSP that has stopped at Yocto 2.4?

0 项奖励
1,879 次查看
gusarambula
NXP TechSupport
NXP TechSupport

Hello Katerina Voulgary,


There have been works on newer Poky releases, you can find more details on the BSP platform github:
https://github.com/Freescale/fsl-community-bsp-platform


Documentation on https://freescale.github.io is a bit far behind, but work is continuing over the newer branches. I would recommend against using the latest one as it may still have a lot of pending work but there are newer branches than 2.4 that are very stable now.


OtavioSalvador, would you why the https://freescale.github.io has not been updated with the latest branches?


Regards,

1,878 次查看
sdi1100002
Contributor II

Thank you both, you've been very helpful, I have now built an image as per vendor's instructions. I will mark @gusarambula's answer as correct, but if I may ask for a clarification?
Is it normal practice for BSP's to depend on the host's packages? (It doesn't seem good practice to me.)
Eventually, once the image is built and works on myirtech's board, we will be making our own board with a subset of its features (without ethernet for example and a camera). So I will have to make a new BSP that we'll call it our own, correct? My naive idea is that I will remove parts of the dtb to achieve it easily, but I'd much prefer to work on newer tools and independant of linux distribution, so that I can maintain it for longer(I guess). Should our custom board still rely on myirtech's kernel, uboot and host restrictions or should I write one from the beginning inheriting from meta-freescale or meta-fslc or something? I'd very much value your insight in this.

Katerina

0 项奖励
1,878 次查看
OtavioSalvador
Senior Contributor II

We need more people to contribute and send pull requests.