element14 Community
element14 Community
    Register Log In
  • Site
  • Search
  • Log In Register
  • About Us
  • Community Hub
    Community Hub
    • What's New on element14
    • Feedback and Support
    • Benefits of Membership
    • Personal Blogs
    • Members Area
    • Achievement Levels
  • Learn
    Learn
    • Ask an Expert
    • eBooks
    • element14 presents
    • Learning Center
    • Tech Spotlight
    • STEM Academy
    • Webinars, Training and Events
    • Learning Groups
  • Technologies
    Technologies
    • 3D Printing
    • FPGA
    • Industrial Automation
    • Internet of Things
    • Power & Energy
    • Sensors
    • Technology Groups
  • Challenges & Projects
    Challenges & Projects
    • Design Challenges
    • element14 presents Projects
    • Project14
    • Arduino Projects
    • Raspberry Pi Projects
    • Project Groups
  • Products
    Products
    • Arduino
    • Avnet Boards Community
    • Dev Tools
    • Manufacturers
    • Multicomp Pro
    • Product Groups
    • Raspberry Pi
    • RoadTests & Reviews
  • Store
    Store
    • Visit Your Store
    • Choose another store...
      • Europe
      •  Austria (German)
      •  Belgium (Dutch, French)
      •  Bulgaria (Bulgarian)
      •  Czech Republic (Czech)
      •  Denmark (Danish)
      •  Estonia (Estonian)
      •  Finland (Finnish)
      •  France (French)
      •  Germany (German)
      •  Hungary (Hungarian)
      •  Ireland
      •  Israel
      •  Italy (Italian)
      •  Latvia (Latvian)
      •  
      •  Lithuania (Lithuanian)
      •  Netherlands (Dutch)
      •  Norway (Norwegian)
      •  Poland (Polish)
      •  Portugal (Portuguese)
      •  Romania (Romanian)
      •  Russia (Russian)
      •  Slovakia (Slovak)
      •  Slovenia (Slovenian)
      •  Spain (Spanish)
      •  Sweden (Swedish)
      •  Switzerland(German, French)
      •  Turkey (Turkish)
      •  United Kingdom
      • Asia Pacific
      •  Australia
      •  China
      •  Hong Kong
      •  India
      •  Korea (Korean)
      •  Malaysia
      •  New Zealand
      •  Philippines
      •  Singapore
      •  Taiwan
      •  Thailand (Thai)
      • Americas
      •  Brazil (Portuguese)
      •  Canada
      •  Mexico (Spanish)
      •  United States
      Can't find the country/region you're looking for? Visit our export site or find a local distributor.
  • Translate
  • Profile
  • Settings
Single-Board Computers
  • Products
  • Dev Tools
  • Single-Board Computers
  • More
  • Cancel
Single-Board Computers
Forum How can I build an image for the MaaxBoard myself?
  • Blog
  • Forum
  • Documents
  • Files
  • Members
  • Mentions
  • Sub-Groups
  • Tags
  • More
  • Cancel
  • New
Join Single-Board Computers to participate - click to join for free!
Actions
  • Share
  • More
  • Cancel
Forum Thread Details
  • State Suggested Answer
  • Replies 30 replies
  • Answers 12 answers
  • Subscribers 62 subscribers
  • Views 3868 views
  • Users 0 members are here
  • maaxboard
Related

How can I build an image for the MaaxBoard myself?

bryantfhayes
bryantfhayes over 5 years ago

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

  • Sign in to reply
  • Cancel

Top Replies

  • gonewtinwind
    gonewtinwind over 5 years ago +2
    done! because the maaxboard modified the soc.mk file at u-boot/tools/imx-boot/iMX8M/soc.mk(yocto at imx-mkimage/imx-boot ) it can not support optee before because of no yocto project. I change back, so…
  • bryantfhayes
    bryantfhayes over 5 years ago in reply to joshb86 +1
    Joshua, Great to hear someone is in the same boat. I appreciate you letting me know that EVK conf didn’t work, as that was something I wanted to try. Please do let me know if you have any success with…
  • joshb86
    joshb86 over 5 years ago in reply to bryantfhayes +1 suggested
    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…
Parents
  • joshb86
    0 joshb86 over 5 years ago

    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.

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Reject Answer
    • Cancel
Reply
  • joshb86
    0 joshb86 over 5 years ago

    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.

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Reject Answer
    • Cancel
Children
  • bryantfhayes
    0 bryantfhayes over 5 years ago in reply to joshb86

    Joshua,

     

    Great to hear someone is in the same boat. I appreciate you letting me know that EVK conf didn’t work, as that was something I wanted to try. Please do let me know if you have any success with the imx8_all build!

    • Cancel
    • Vote Up +1 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
  • joshb86
    0 joshb86 over 5 years ago in reply to bryantfhayes

    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.

    • Cancel
    • Vote Up +1 Vote Down
    • Sign in to reply
    • Verify Answer
    • Reject Answer
    • Cancel
  • joshb86
    0 joshb86 over 5 years ago in reply to bryantfhayes

    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"

    • Cancel
    • Vote Up +1 Vote Down
    • Sign in to reply
    • Verify Answer
    • Reject Answer
    • Cancel
  • clem57
    0 clem57 over 5 years ago in reply to joshb86

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

    Clem

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Reject Answer
    • Cancel
  • bryantfhayes
    0 bryantfhayes over 5 years ago in reply to joshb86

    Joshua,

     

    Thanks for letting us know their response! That’s a bummer if there will be no Yocto conf, but a Debian image is better than nothing I suppose.

     

    I will need to get a Yocto build going one way or another, so hopefully we can figure out our own conf that works

     

    -Bryant

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
  • paulderr1
    0 paulderr1 over 5 years ago in reply to bryantfhayes

    I am talking to the engineering team now to verify if a Yocto build will or will not be available.  Don't get too bummed yet.    image

    • Cancel
    • Vote Up +1 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
element14 Community

element14 is the first online community specifically for engineers. Connect with your peers and get expert answers to your questions.

  • Members
  • Learn
  • Technologies
  • Challenges & Projects
  • Products
  • Store
  • About Us
  • Feedback & Support
  • FAQs
  • Terms of Use
  • Privacy Policy
  • Legal and Copyright Notices
  • Sitemap
  • Cookies

An Avnet Company © 2025 Premier Farnell Limited. All Rights Reserved.

Premier Farnell Ltd, registered in England and Wales (no 00876412), registered office: Farnell House, Forge Lane, Leeds LS12 2NE.

ICP 备案号 10220084.

Follow element14

  • X
  • Facebook
  • linkedin
  • YouTube