Mity CPU Platforms » MitySOM-AM57X

Hi Sandeep,

That repository is mirrored here:

https://support.criticallink.com/git/meta-mitysom.git

I think you should be able to update the URL for this repository.

We will look into updating the config file and remove our internal links. Sorry for the inconvenience.

-Mike

Summary repo link:

https://support.criticallink.com/gitweb/?p=meta-mitysom.git;a=summary

sandeep Sivadas wrote:

Hi,

We purchased MitySOM AM572x development kit and trying to build our own yocto linux.
Then we have a problem while cloning the branches of mitysom AM57x.
While cloning the below git files, it shows as "fatal: unable to access 'https://gitlab.syr.criticallink.com/critical-link/yocto/meta-mitysom.git/': Could not resolve host: gitlab.syr.criticallink.com"

meta-mitysom,https://gitlab.syr.criticallink.com/critical-link/yocto/meta-mitysom.git,thud,HEAD,layers=

The config file i got from Critical link is attaching here. Kindly look in to it.

The correct config file is processor-sdk-06.03.00.106-cl-external-config.txt

See https://support.criticallink.com/redmine/projects/mitysom_am57x/wiki/Linux_Kernel_Yocto_for_MitySOM-AM57X

Hi,

Thank you for your support.
I have followed the steps in the link you provided. https://support.criticallink.com/redmine/projects/mitysom_am57x/wiki/Linux_Kernel_Yocto_for_MitySOM-AM57X

But got some error as shown below.

_pokyuser@31657297eb91:/work/oe-layersetup/build$ MACHINE=mitysom-am57x bitbake arago-base-tisdk-image
Traceback (most recent call last):
File "/work/oe-layersetup/sources/bitbake/bin/bitbake", line 31, in <module>
import bb
File "/work/oe-layersetup/sources/bitbake/lib/bb/_init__.py", line 81, in <module>
import bb.msg
File "/work/oe-layersetup/sources/bitbake/lib/bb/msg.py", line 32, in <module>
import bb.event
File "/work/oe-layersetup/sources/bitbake/lib/bb/event.py", line 35, in <module>
import bb.compat
File "/work/oe-layersetup/sources/bitbake/lib/bb/compat.py", line 3, in <module>
from collections import MutableMapping, KeysView, ValuesView, ItemsView, OrderedDict
ImportError: cannot import name 'MutableMapping' from 'collections' (/opt/poky/4.1/sysroots/x86_64-pokysdk-linux/usr/lib/python3.10/collections/__init__.py)__

Kindly look in to it.

Sandeep S

Sandeep Sivadas wrote in RE: Yocto build for mitySOM AM57x:

Hi,

Thank you for your support.
I have followed the steps in the link you provided. https://support.criticallink.com/redmine/projects/mitysom_am57x/wiki/Linux_Kernel_Yocto_for_MitySOM-AM57X

But got some error as shown below.

_pokyuser@31657297eb91:/work/oe-layersetup/build$ MACHINE=mitysom-am57x bitbake arago-base-tisdk-image
Traceback (most recent call last):
File "/work/oe-layersetup/sources/bitbake/bin/bitbake", line 31, in <module>
import bb
File "/work/oe-layersetup/sources/bitbake/lib/bb/_init__.py", line 81, in <module>
import bb.msg
File "/work/oe-layersetup/sources/bitbake/lib/bb/msg.py", line 32, in <module>
import bb.event
File "/work/oe-layersetup/sources/bitbake/lib/bb/event.py", line 35, in <module>
import bb.compat
File "/work/oe-layersetup/sources/bitbake/lib/bb/compat.py", line 3, in <module>
from collections import MutableMapping, KeysView, ValuesView, ItemsView, OrderedDict
ImportError: cannot import name 'MutableMapping' from 'collections' (/opt/poky/4.1/sysroots/x86_64-pokysdk-linux/usr/lib/python3.10/collections/__init__.py)__

Kindly look in to it.

Sandeep S

Hi Sandeep, the crops/poky group decided they needed a newer python, etc in their 18.04 ubuntu image which breaks the older thud build. We can work around this by mounting an empty tmpfs directory over /opt/poky so that the original 18.04 tools will be used.

I will update the wiki to address this.

docker run --rm -it -v $PWD:/work -v /home/tools:/home/tools --tmpfs /opt/poky --env "TOOLCHAIN_PATH_ARMV7=/home/tools/mitysom-57x/gcc-arm-8.3-2019.03-x86_64-arm-linux-gnueabihf" crops/poky:ubuntu-18.04 --workdir=/work

Note there is a docker-poky.sh helper script in sources/meta-mitysom/build/ that can be used to call the "docker run ..." command so you don't have to remember it every time.

Wiki has been updated. Thanks for reporting this.

Hi,

Thank you for your support.
I tried the updated steps for yocto build and it worked fine.

1. The command i used for bitbake build is "MACHINE=mitysom-am57x bitbake arago-base-tisdk-image". The image written to the SD card and booting is completed.
But LCD Display connected to the HDMI port is blank (showing white page). Is there any other setting we need to do for HDMI communication?

2. When i tried the command for changing the configuration of the kernel, i got the following errors. It showing Unable to find the ncurses package.
Please help on this..

• Unable to find the ncurses package.
• Install ncurses (ncurses-devel or libncurses-dev
• depending on your distribution).
  /work/oe-layersetup/build/arago-tmp-external-arm-toolchain/work-shared/mitysom-am57x/kernel-source/scripts/kconfig/Makefile:228: recipe for target 'scripts/kconfig/.mconf-cfg' failed
  make³: [scripts/kconfig/.mconf-cfg] Error 1
  /work/oe-layersetup/build/arago-tmp-external-arm-toolchain/work-shared/mitysom-am57x/kernel-source/Makefile:534: recipe for target 'menuconfig' failed
  make²: [menuconfig] Error 2
  Makefile:146: recipe for target 'sub-make' failed
  make¹: [sub-make] Error 2
  Makefile:24: recipe for target '__sub-make' failed
  make: * [__sub-make] Error 2
  Command failed.
  Press any key to continue..._

--Sandeep S

Sandeep Sivadas wrote in RE: Yocto build for mitySOM AM57x:

Hi,

Thank you for your support.
I tried the updated steps for yocto build and it worked fine.

1. The command i used for bitbake build is "MACHINE=mitysom-am57x bitbake arago-base-tisdk-image". The image written to the SD card and booting is completed.
But LCD Display connected to the HDMI port is blank (showing white page). Is there any other setting we need to do for HDMI communication?

The arago-base-tisdk-image is a minimal filesystem that doesn't include the packages for the video driver or an Xserver.
You can check arago-base-tisdk-image-mitysom-am57x.manifest to see all the packages that get installed.

The tisdk-rootfs-image is a full featured image which does have the graphics drivers and wayland installed so that you will get a desktop prompt.

2. When i tried the command for changing the configuration of the kernel, i got the following errors. It showing Unable to find the ncurses package.
Please help on this..

_
GEN ./Makefile *

• Unable to find the ncurses package.
• Install ncurses (ncurses-devel or libncurses-dev
• depending on your distribution).
  /work/oe-layersetup/build/arago-tmp-external-arm-toolchain/work-shared/mitysom-am57x/kernel-source/scripts/kconfig/Makefile:228: recipe for target 'scripts/kconfig/.mconf-cfg' failed
  make³: [scripts/kconfig/.mconf-cfg] Error 1
  /work/oe-layersetup/build/arago-tmp-external-arm-toolchain/work-shared/mitysom-am57x/kernel-source/Makefile:534: recipe for target 'menuconfig' failed
  make²: [menuconfig] Error 2
  Makefile:146: recipe for target 'sub-make' failed
  make¹: [sub-make] Error 2
  Makefile:24: recipe for target '__sub-make' failed
  make: * [__sub-make] Error 2
  Command failed.
  Press any key to continue..._

--Sandeep S

The crops/poky docker image doesn't have the libncurses-dev package installed that menuconfig requires.

Depending on what you're trying to do I can make a few suggestions.

• You can create your own Dockerfile, using the crops image as a base, and add the missing packages you want
  • mkdir custom-crops && cd custom-crops
  • vim Dockerfile
    

    FROM crops/poky:ubuntu-18.04
    USER root
    
    RUN apt-get install libncurses5-dev -y
    
    USER usersetup
    

  • docker build . --tag custom_crops
  • Then replace "crops/poky:ubuntu-18.04" in the docker command with "custom_crops"
    

    docker run --rm -it -v $PWD:/work -v /home/tools:/home/tools --tmpfs /opt/poky --env "TOOLCHAIN_PATH_ARMV7=/home/tools/mitysom-57x/gcc-arm-8.3-2019.03-x86_64-arm-linux-gnueabihf" custom_crops --workdir=/work
    pokyuser@a6dbf190ee68:/work/build$ MACHINE=mitysom-am57x bitbake virtual/kernel -c menuconfig
    ...
    Loading cache: 100% |##############################################################################| Time: 0:00:01
    Loaded 4677 entries from dependency cache.
    

Sorry about this confusion, I'll see if we can clean up the docs

Hi,

1. I tried the custom-crops modifications and got the menuconfig window.

2. I have tried to build MACHINE=mitysom-am57x bitbake tisdk-rootfs-image, but got some errors as shown below

ERROR: qtbase-5.11.3+gitAUTOINC+08de243eaa-r0.arago16.tisdk5.7 do_compile: oe_runmake failed
ERROR: qtbase-5.11.3+gitAUTOINC+08de243eaa-r0.arago16.tisdk5.7 do_compile: Function failed: do_compile (log file is located at /work/oe-layersetup/build/arago-tmp-external-arm-toolchain/work/armv7at2hf-neon-linux-gnueabi/qtbase/5.11.3+gitAUTOINC+08de243eaa-r0.arago16.tisdk5.7/temp/log.do_compile.23819)
ERROR: Logfile of failure stored in: /work/oe-layersetup/build/arago-tmp-external-arm-toolchain/work/armv7at2hf-neon-linux-gnueabi/qtbase/5.11.3+gitAUTOINC+08de243eaa-r0.arago16.tisdk5.7/temp/log.do_compile.23819
Log data follows:

Log data file is attaching here with. Kindly check the file.

Thanks and regards
Sandeep S

1. Great

2. I'm not sure what would have caused this file to get truncated. Seems like some kind of file corruption, not sure. Can you try to rebuild just qtbase? MACHINE=mitysom-am57x bitbake qtbase -c cleanall && MACHINE=mitysom-am57x bitbake qtbase

| /home/mitysom/tools/mitysom-57x/gcc-arm-8.3-2019.03-x86_64-arm-linux-gnueabihf/bin/../lib/gcc/arm-linux-gnueabihf/8.3.0/../../../../arm-linux-gnueabihf/bin/ld: .obj/tst_qeventdispatcher.o: file not recognized: file truncated

Hi Sandeep,

I've run into some issues building the systemd package during the build. I am looking into it.

Hi,

I have tried to rebuild qtbase as told above. The log files are attaching here.

Thanks & regards

Sandeep s

Looks like it built successfully this time. I'll let you know how I get along with the systemd issue, I may not have time until next week.

In the meantime, you should be able to use the released filesystem and replace just the kernel on it. And be able to make headway with customizing your kernel.
https://support.criticallink.com/redmine/projects/mitysom_am57x/wiki/Repositories_and_Pre-built_Images

Added some fixes for a few recipes which SRC urls changed slightly. Let me know if you run into any more issues.

Hi,

1. In the meantime, you should be able to use the released filesystem and replace just the kernel on it. And be able to make headway with customizing your kernel.

Q. Can you please clarify the point above.I didnt get how to do this.

2. Added some fixes for a few recipes which SRC urls changed slightly. Let me know if you run into any more issues.

Q. Do i need to update the changes in my build directory? where can i find the updated fixes.

Thanks & regards

Sandeep s

Sandeep Sivadas wrote in RE: Yocto build for mitySOM AM57x:

Hi,

1. In the meantime, you should be able to use the released filesystem and replace just the kernel on it. And be able to make headway with customizing your kernel.

Q. Can you please clarify the point above. I didnt get how to do this.

You can update/customize the kernel without rebuilding the whole filesystem. You just need to update the files located on the boot partition of the sdcard.
See https://support.criticallink.com/redmine/projects/mitysom_am57x/wiki/Linux_Kernel#Building-the-kernel

2. Added some fixes for a few recipes which SRC urls changed slightly. Let me know if you run into any more issues.

Q. Do i need to update the changes in my build directory? where can i find the updated fixes.

If you rerun the "oe-layertool-setup.sh" step on the wiki it will grab any new changes.