element14 Community
element14 Community
    Register Log In
  • Site
  • Search
  • Log In Register
  • 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 can I build maaxboard zeus branch now?
  • Blog
  • Forum
  • Documents
  • Files
  • Members
  • Mentions
  • Sub-Groups
  • Tags
  • More
  • Cancel
  • New
Single-Board Computers requires membership for participation - click to join
Actions
  • Share
  • More
  • Cancel
Forum Thread Details
  • Replies 5 replies
  • Subscribers 57 subscribers
  • Views 1886 views
  • Users 0 members are here
Related

can I build maaxboard zeus branch now?

gonewtinwind
gonewtinwind over 4 years ago

Hi Josh,

Can I build maaxboard zeus branch now?

it shows The "zeus" branch will support MaaXBoard / MaaXBoard Mini in the end of Dec 2020.

beacuse my old maaxboard source code can not support 18.5" mimo touchscreem,I found some discussions in nxp forum,imx8mqevk board can not support some hdmi screem. so  I am going to try a higher version. I am building

https://github.com/Avnet/meta-maaxboard/tree/zeus

  • Sign in to reply
  • Cancel

Top Replies

  • gonewtinwind
    gonewtinwind over 4 years ago in reply to gonewtinwind +1
    Hi Josh, I have added optee sucessfully. at file ./meta-maaxboard/conf/machine/include/maaxboard-base.inc : MACHINE_FEATURES += " optee pci wifi bluetooth bcm43455" xtest passed! optee should work well…
  • gonewtinwind
    gonewtinwind over 4 years ago in reply to gonewtinwind +1
    I found help here: https://github.com/OSSystems/meta-browser/issues/388 and add mesa in file : ./meta-browser/recipes-browser/chromium/chromium-ozone-wayland_75.0.3770.142.bb ... DEPENDS += "\ mesa \ libxkbcommon…
Parents
  • jafoste4
    jafoste4 over 4 years ago

    Hi Peter,

     

    Yes that is now public and tested. Also to make you aware, we are publishing a new yocto out of box image this week targeting this Zeus branch.

     

    -Josh

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
  • gonewtinwind
    gonewtinwind over 4 years ago in reply to jafoste4

    Hi Josh,

    Thank you very much for your reply so soon.

    I built it successfully by myself (I only modified an  ip adress to get kernel code from GitHub avnet, file ./meta-maaxboard/conf/layer.conf

    # Internal Git mirror

    #MAAXBOARD_GIT_HOST_MIRROR ?= "git://git@192.168.2.100/imx8m"

     

    # Github Mirror: github.com/Avnet

    MAAXBOARD_GIT_HOST_MIRROR ?= "git://git@github.com/Avnet"

    :).

     

     

    and the updated version can support my 18.5' mimo touchscreen(I am very happy at this time),

    but, unfortunately, the kernel can not support optee!

     

    I added DISTRO_FEATURES_append =" optee-os optee-test" in local.conf

    but it still does not  support optee. can not run xtest (no the executable code), can not find  /dev/tee* devices.

     

    do you know how to do?

     

    I remember the older 4.14.98  version should work(I will go back to test again).

    Maybe the zeus do not add the optee support right now? right?

    Thank you.

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
  • gonewtinwind
    gonewtinwind over 4 years ago in reply to gonewtinwind

    Hi Josh,

    I have added optee sucessfully. at file ./meta-maaxboard/conf/machine/include/maaxboard-base.inc  : MACHINE_FEATURES += " optee pci wifi bluetooth bcm43455"

     

     

     

    xtest passed! optee should work well.

    Tomorrow  I will add chromium. before I tried to add IMAGE_INSTALL_append +=" chromium-ozone-wayland" in local.conf, it did not pass the bitbake . it's stranger. I will try more.

    if it will OK too, I will update all my app to the version so that can support mimo 18.5 touchscreen

    Thank you

    • Cancel
    • Vote Up +1 Vote Down
    • Sign in to reply
    • Cancel
  • gonewtinwind
    gonewtinwind over 4 years ago in reply to gonewtinwind

    sorry , the zeus branch can not pass chromium(IMAGE_INSTALL_append +=" chromium-ozone-wayland" in local.conf) compilation in ubuntu 18.04 

     

     

    any help?

     

    ERROR: chromium-ozone-wayland-75.0.3770.142-r0 do_configure: Execution of '/home/rnd2/work/maaxboard/zeus/imx-yocto-bsp/maaxboard/build/tmp/work/aarch64-mx8m-poky-linux/chromium-ozone-wayland/75.0.3770.142-r0/temp/run.do_configure.12588' failed with exit code 1:

    ERROR at //build/config/linux/dri/BUILD.gn:11:20: Script returned non-zero exit code.

      dri_driver_dir = exec_script(pkg_config_script,

                       ^----------

    Current dir: /home/rnd2/work/maaxboard/zeus/imx-yocto-bsp/maaxboard/build/tmp/work/aarch64-mx8m-poky-linux/chromium-ozone-wayland/75.0.3770.142-r0/chromium-75.0.3770.142/out/Release/

    Command: python /home/rnd2/work/maaxboard/zeus/imx-yocto-bsp/maaxboard/build/tmp/work/aarch64-mx8m-poky-linux/chromium-ozone-wayland/75.0.3770.142-r0/chromium-75.0.3770.142/build/config/linux/pkg-config.py --dridriverdir dri

    Returned 1 and printed out:

     

    Error from pkg-config.

     

    stderr:

     

    Package dri was not found in the pkg-config search path.

    Perhaps you should add the directory containing `dri.pc'

    to the PKG_CONFIG_PATH environment variable

    No package 'dri' found

     

    See //content/gpu/BUILD.gn:128:18: which caused the file to be included.

        configs += [ "//build/config/linux/dri" ]

                     ^-------------------------

    WARNING: exit code 1 from a shell command.

     

    ERROR: Logfile of failure stored in: /home/rnd2/work/maaxboard/zeus/imx-yocto-bsp/maaxboard/build/tmp/work/aarch64-mx8m-poky-linux/chromium-ozone-wayland/75.0.3770.142-r0/temp/log.do_configure.12588

    Log data follows:

    | DEBUG: Executing shell function do_configure

    | ERROR at //build/config/linux/dri/BUILD.gn:11:20: Script returned non-zero exit code.

    |   dri_driver_dir = exec_script(pkg_config_script,

    |                    ^----------

    | Current dir: /home/rnd2/work/maaxboard/zeus/imx-yocto-bsp/maaxboard/build/tmp/work/aarch64-mx8m-poky-linux/chromium-ozone-wayland/75.0.3770.142-r0/chromium-75.0.3770.142/out/Release/

    | Command: python /home/rnd2/work/maaxboard/zeus/imx-yocto-bsp/maaxboard/build/tmp/work/aarch64-mx8m-poky-linux/chromium-ozone-wayland/75.0.3770.142-r0/chromium-75.0.3770.142/build/config/linux/pkg-config.py --dridriverdir dri

    | Returned 1 and printed out:

    |

    | Error from pkg-config.

    |

    | stderr:

    |

    | Package dri was not found in the pkg-config search path.

    | Perhaps you should add the directory containing `dri.pc'

    | to the PKG_CONFIG_PATH environment variable

    | No package 'dri' found

    |

    | See //content/gpu/BUILD.gn:128:18: which caused the file to be included.

    |     configs += [ "//build/config/linux/dri" ]

    |                  ^-------------------------

    | WARNING: exit code 1 from a shell command.

    | ERROR: Execution of '/home/rnd2/work/maaxboard/zeus/imx-yocto-bsp/maaxboard/build/tmp/work/aarch64-mx8m-poky-linux/chromium-ozone-wayland/75.0.3770.142-r0/temp/run.do_configure.12588' failed with exit code 1:

    | ERROR at //build/config/linux/dri/BUILD.gn:11:20: Script returned non-zero exit code.

    |   dri_driver_dir = exec_script(pkg_config_script,

    |                    ^----------

    | Current dir: /home/rnd2/work/maaxboard/zeus/imx-yocto-bsp/maaxboard/build/tmp/work/aarch64-mx8m-poky-linux/chromium-ozone-wayland/75.0.3770.142-r0/chromium-75.0.3770.142/out/Release/

    | Command: python /home/rnd2/work/maaxboard/zeus/imx-yocto-bsp/maaxboard/build/tmp/work/aarch64-mx8m-poky-linux/chromium-ozone-wayland/75.0.3770.142-r0/chromium-75.0.3770.142/build/config/linux/pkg-config.py --dridriverdir dri

    | Returned 1 and printed out:

    |

    | Error from pkg-config.

    |

    | stderr:

    |

    | Package dri was not found in the pkg-config search path.

    | Perhaps you should add the directory containing `dri.pc'

    | to the PKG_CONFIG_PATH environment variable

    | No package 'dri' found

    |

    | See //content/gpu/BUILD.gn:128:18: which caused the file to be included.

    |     configs += [ "//build/config/linux/dri" ]

    |                  ^-------------------------

    | WARNING: exit code 1 from a shell command.

    |

    ERROR: Task (/home/rnd2/work/maaxboard/zeus/imx-yocto-bsp/sources/meta-browser/recipes-browser/chromium/chromium-ozone-wayland_75.0.3770.142.bb:do_configure) failed with exit code '1'

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
  • gonewtinwind
    gonewtinwind over 4 years ago in reply to gonewtinwind

    I found help here: https://github.com/OSSystems/meta-browser/issues/388

     

    and add mesa in  file : ./meta-browser/recipes-browser/chromium/chromium-ozone-wayland_75.0.3770.142.bb

    ...

    DEPENDS += "\

            mesa \

            libxkbcommon \

            virtual/egl \

            wayland \

            wayland-native \

     

    ..

    no the error appears,do_configure passed . now it is compiling.

    hope can pass the final compilation

    ---

    passed! works well!

    I do not how to run it by non root user, now root user run well!

    • Cancel
    • Vote Up +1 Vote Down
    • Sign in to reply
    • Cancel
Reply
  • gonewtinwind
    gonewtinwind over 4 years ago in reply to gonewtinwind

    I found help here: https://github.com/OSSystems/meta-browser/issues/388

     

    and add mesa in  file : ./meta-browser/recipes-browser/chromium/chromium-ozone-wayland_75.0.3770.142.bb

    ...

    DEPENDS += "\

            mesa \

            libxkbcommon \

            virtual/egl \

            wayland \

            wayland-native \

     

    ..

    no the error appears,do_configure passed . now it is compiling.

    hope can pass the final compilation

    ---

    passed! works well!

    I do not how to run it by non root user, now root user run well!

    • Cancel
    • Vote Up +1 Vote Down
    • Sign in to reply
    • Cancel
Children
No Data
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