How can I build an image for the MaaxBoard myself?

Question

I would like to compile my own image using Yocto, is there a guide for this?

gonewtinwind · Answer

Hi

I have the same problem.

I need the yocto source code.

I do not understand, the maaxboad shipped with a yocto image and works well. but why do not release the yocto source code to us?

I need yocto source code to build optee.

I will take long time to build yocto using the individual kernel and u-boot source code. It waste time.

I asked the technical support , they give a i.MX_Yocto_Project_User's_Guide.pdf and tell me that because the yocto source is too huge so they do not release it. but the imx-yocto-bsp does not include maaxboard support. I try to use imx8mqevk board to build. but the image can not start up. the means the mx8mqevk board is different with the maaxboard.(of course)

can you give us the maaxboard layers files to us so that we can bulid yocto image by ourselves? or give us some main idea becuase of you did and always generated the yocto image.

Thanks.

joshb86 · Answer

First build utilizing imx8_all failed with errors relating to optee. It initially looked like there was a typo somewhere down the layer conf. It reports " Unsupported PLATFORM_FLAVOR "mx8_all " - Notice the "i" missing in imx8_all. That doesn't seem intentional, so I did a sweeping grep against that variable name... ../sources/meta-fsl-bsp-release/imx/meta-bsp/recipes-security/optee-imx/optee-os-imx_git.bb:B = "${WORKDIR}/build.${PLATFORM_FLAVOR}" ../sources/meta-fsl-bsp-release/imx/meta-bsp/recipes-security/optee-imx/optee-os-imx_git.bb: PLATFORM_FLAVOR = "${@d.getVar('MACHINE')[1:]}" ../sources/meta-fsl-bsp-release/imx/meta-bsp/recipes-security/optee-imx/optee-os-imx_git.bb:PLATFORM_FLAVOR_imx6qpdlsolox = "mx6qsabresd" ../sources/meta-fsl-bsp-release/imx/meta-bsp/recipes-security/optee-imx/optee-os-imx_git.bb:PLATFORM_FLAVOR_imx6ul7d = "mx6ulevk" ../sources/meta-fsl-bsp-release/imx/meta-bsp/recipes-security/optee-imx/optee-os-imx_git.bb:PLATFORM_FLAVOR_imx6ull14x14evk = "mx6ullevk" ../sources/meta-fsl-bsp-release/imx/meta-bsp/recipes-security/optee-imx/optee-os-imx_git.bb:PLATFORM_FLAVOR_imx6ull9x9evk = "mx6ullevk" ../sources/meta-fsl-bsp-release/imx/meta-bsp/recipes-security/optee-imx/optee-os-imx_git.bb:PLATFORM_FLAVOR_imx6ulz14x14evk = "mx6ullevk" ../sources/meta-fsl-bsp-release/imx/meta-bsp/recipes-security/optee-imx/optee-os-imx_git.bb:PLATFORM_FLAVOR_mx8mm = "mx8mmevk" ../sources/meta-fsl-bsp-release/imx/meta-bsp/recipes-security/optee-imx/optee-os-imx_git.bb:PLATFORM_FLAVOR_imx8qmqxp = "mx8qmmek" ../sources/meta-fsl-bsp-release/imx/meta-bsp/recipes-security/optee-imx/optee-os-imx_git.bb:EXTRA_OEMAKE = "PLATFORM=imx PLATFORM_FLAVOR=${PLATFORM_FLAVOR} \ ../sources/meta-fsl-bsp-release/imx/meta-bsp/recipes-security/optee-imx/optee-os-imx_git.bb: ${TARGET_PREFIX}objcopy -O binary ${B}/core/tee.elf ${DEPLOYDIR}/tee.${PLATFORM_FLAVOR}.bin ../sources/meta-fsl-bsp-release/imx/meta-bsp/recipes-security/optee-imx/optee-os-imx_git.bb: -d ${DEPLOYDIR}/tee.${PLATFORM_FLAVOR}.bin ${DEPLOYDIR}/uTee-${OPTEE_BIN_EXT} ../sources/meta-fsl-bsp-release/imx/meta-bsp/recipes-security/optee-imx/optee-os-imx_git.bb: ln -sf tee.${PLATFORM_FLAVOR}.bin tee.bin I see no static assignments, but you can see on the second line that the value is being set by parsing the MACHINE name. Since we can't add an appending space to a machine name in local.conf, I edited this line of the .bb changing the 1 to 0 so it would not cut off the "i" in the MACHINE name. Making this change resolved the parsing issue, but still received.... *** Unsupported PLATFORM_FLAVOR "imx8_all". Stop. This tells me that optee doesn't know what to do with the MACHINE imx8_all, so I edited the optee-os-imx_git.bb by commenting out the line assigning the PLATFORM_FLAVOR variable by parsing the MACHINE name and added a new line statically setting it to "imx-imx8mqevk" per the docs here> https://github.com/OP-TEE/optee_docs/blob/master//general/platforms.rst This will fail under SUMO (the same version the MAAXBOARD ships with), because the optee version under the BSP did not yet inherit 8mq support. So this leaves me with going BACK to warrior if I want to test imx8_all build.... just to test, I did set the PLATFORM_FLAVOR to "mx8qmmek" just to get a successful build, but same result once the image is flashed... nada. At this point it looks like we will either have to prep our own machine conf with the data we have, or wait on an office conf that supports this machine. I also need to be on warrior due to dependencies I need, so I'll likely go back to warrior and tinker some more. If I have any luck I'll be sure to keep you posted.

joshb86 · Answer

bryantfhayes , To potentially save you from pulling any hair out... our fantastic Avnet support team forwarded this message to us last night. I don't know if this means no Yocto conf planned, but at least we will have a usable Debian image soon that can be easily tweaked. " Instead of Yocto, We're building a Debian Buster based Linux distribution. Compared to Yocto, Debian is ready to use, customers don't have to build a filesystem from scratch. But they can also do some customization on the filesystem through the "apt install/remove" packaging management system. We also have native support for the hardware accelerations like GPU, VPU, QT5 and etc. It's really simple and easy for customers to do customization / secondary development based on Debian ecosystems. Now, the test team is doing the final verification and expect to distribute it to customers in the early next week. Will let you know then and send you the download link(Image, Latest Manuals and etc), Thanks"

clem57 · Answer

bryantfhayes although old, this blog gives the methods of using Yocto to build a custom image: https://boundarydevices.com/what-is-a-yocto-image-and-how-can-i-modify-it/ . Please read all parts before trying.

joshb86 · Answer

I'm hunting down the same trail Bryant. I can confirm that no distro or image variation built for imx8mqevk.conf will boot on the MAAXBOARD. I'm running a build for imx8_all now and will report back if I have any luck. It appears to me that there isn't a machine conf specifically supported just yet.

paulderr1 · Answer

Good Morning All! The Debian Linux has just been released. You can get the download link from Embest MaaXBoard product web page -> Download Tab -> MaaXBoard Development resource / download . It will redirect to a Dropbox share link, All MaaXBoard resources (Manuals, Source code, Images and etc) will be uploaded to this Dropbox share link. Besides the latest version, the previous versions are still over their. Please always get the latest version to download. - MaaXBoard-Hardware_UserManual-V1.1-EN.pdf - MaaXBoard-Linux-Debian-UserManual-V1.2-EN.pdf - MaaXBoard-Linux-Development_Guide-V1.0-EN.pdf - MaaXBoard-Linux-ReleaseNote-V1.2.pdf - 91200026-MaaXBoard-LinuxShipmentImage-Debian-V1.1.1r10.rar - MaaXBoard-LinuxSourceCode-V1.1.1r10.rar (Linux Kernel, U-Boot) - Tools(MaaXBoard-LinuxTools-V1.0.rar)

joshb86 · Answer

I haven't had the chance to push some updates on our yocto image since I've been deep into the recently released debian image, but I should be able to provide some more feedback soon. Once I get our dev team 100% running on the debian base I'll jump over to yocto as I believe I have a solution to try until a proper machine conf lands.

gonewtinwind · Answer

hi I have successfully merged maaxboard company's linux and uboot code into the yocto project. some key steps: 1. in freescale yocto guide I use yocto version:(asked from technical supporter) ... $ mkdir imx-yocto-bsp $ cd imx-yocto-bsp $ repo init -u https://source.codeaurora.org/external/imx/imx-manifest -b imx-linux-sumo -m imx-4.14.98-2.0.0_ga.xml $ repo sync .. 2.the board is imx8mqevk 3. patches kernel DTB using: em_sbc_imx8m.dts remove the other dts we do not use. that 's it! 3.directly use maaxboard uboot code em_sbc_imx8m_defconfig for uboot config modify key files modified: ../../conf/machine/imx8mqevk.conf (flash_ddr4_em for uboot image,for dtb, for uboot config ,please change modified: ../u-boot/u-boot-imx_2018.03.bb modified: ../../recipes-kernel/linux/linux-imx-src-4.14.98.inc 4. uboot makimage tools; modified: imx-mkimage_git.inc (directly company's source code in u-boot folder : source/u-boot/tools/imx-boot) Thant's it!

gonewtinwind · Answer

but in my yocto project. it can NOT support optee. so I asked here: https://community.nxp.com/message/1275797 and here: https://www.element14.com/community/message/288875/l/i-need-opteeos-support-for-maaxboard-in-yocto-project-any-help#2888… any help ?

james.flynn · Answer

Bryant, I am checking with Embest to get this information. They were in the process of switching to the Debian rootfs (Buster) and I am not aware of the current status.

jafoste4 · Answer

Hi Bryant, This documentation by NXP shows their typical process for rebuilding an image for one of their boards. Perhaps you can take this and re-purpose this to the MaaXBoard? https://community.nxp.com/docs/DOC-94866 -Josh

clem57 · Answer

Thanks joshb86 . This certainly has to be the move in the right direction. Clem

How can I build an image for the MaaxBoard myself?

Top Replies