PROCESSOR-SDK-AM62X: [AM62X] How to add custom machine name in Yocto build

Hi ,

Any update on this ?

Thanks,

Naresh

Hi Naresh,

The best is probably for me to create an example on how to add a custom machine in the context of our SDK v9.x but I'm on business travel all week so there isn't much time, so it will likely not be until next week the earliest before I can work on this. In the meantime I'd recommend you stick with customizing a provided machine.

Regards, Andreas

Sure Andreas ,

Thanking you. 

BR,

Naresh

Hi Andreas ,

Below changes i was done for custom machine name build .

• build/conf/local.conf

                        MACHINE ?= "am62xx-custom"

• sources/meta-ti/meta-ti-bsp/recipes-bsp/u-boot/u-boot-ti.inc  , ::: Here i didnt change anything.
              COMPATIBLE_MACHINE = "ti-soc"

       created below 2 files  (am62xx-custom.conf , am62xx-custom-k3r5.conf)

• sources/meta-ti/meta-ti-bsp/conf/machine/am62xx-custom.conf
• sources/meta-ti/meta-ti-bsp/conf/machine/am62xx-custom-k3r5.conf

• sources/meta-ti/meta-ti-bsp/recipes-bsp/u-boot/ti-extras.inc
               COMPATIBLE_MACHINE = "am62xx-custom"
• sources/meta-ti/meta-ti-bsp/conf/machine/am62xx-evm-k3r5.conf
               SYSFW_CONFIG = "custom"

After above changes , i tried to build the yocto , custom images are generated at  " tisdk/build/arago-tmp-default-glibc/deploy/images/am62xx-custom" but getting ti-sci firmware issue as firmware is not generating.

Please find below ti-sci firmware ERROR logs.

ERROR: mc:k3r5:ti-sci-fw-08.06.04-r4.0.psdk1 do_deploy: ExecutionError('/home/test/projects/OTOTRAK/Yocto_Workspace/tisdk/build/arago-tmp-default-glibc/work/am62xx_custom_k3r5-oe-linux-gnueabi/ti-sci-fw/08.06.04-r4.0.psdk1/temp/run.do_deploy.715230', 1, None, None)
ERROR: Logfile of failure stored in: /home/test/projects/OTOTRAK/Yocto_Workspace/tisdk/build/arago-tmp-default-glibc/work/am62xx_custom_k3r5-oe-linux-gnueabi/ti-sci-fw/08.06.04-r4.0.psdk1/temp/log.do_deploy.715230
Log data follows:
| DEBUG: Executing python function sstate_task_prefunc
| DEBUG: Python function sstate_task_prefunc finished
| DEBUG: Executing shell function do_deploy
| install: cannot stat '/home/test/projects/OTOTRAK/Yocto_Workspace/tisdk/build/arago-tmp-default-glibc/work/am62xx_custom_k3r5-oe-linux-gnueabi/ti-sci-fw/08.06.04-r4.0.psdk1/git/ti-sysfw/ti-sci-firmware-am62x-*.bin': No such file or directory
| WARNING: /home/test/projects/OTOTRAK/Yocto_Workspace/tisdk/build/arago-tmp-default-glibc/work/am62xx_custom_k3r5-oe-linux-gnueabi/ti-sci-fw/08.06.04-r4.0.psdk1/temp/run.do_deploy.715230:142 exit 1 from 'install -m 644 /home/test/projects/OTOTRAK/Yocto_Workspace/tisdk/build/arago-tmp-default-glibc/work/am62xx_custom_k3r5-oe-linux-gnueabi/ti-sci-fw/08.06.04-r4.0.psdk1/git/ti-sysfw/ti-sci-firmware-am62x-*.bin /home/test/projects/OTOTRAK/Yocto_Workspace/tisdk/build/arago-tmp-default-glibc/work/am62xx_custom_k3r5-oe-linux-gnueabi/ti-sci-fw/08.06.04-r4.0.psdk1/deploy-ti-sci-fw/'
| WARNING: Backtrace (BB generated script):
| 	#1: do_deploy, /home/test/projects/OTOTRAK/Yocto_Workspace/tisdk/build/arago-tmp-default-glibc/work/am62xx_custom_k3r5-oe-linux-gnueabi/ti-sci-fw/08.06.04-r4.0.psdk1/temp/run.do_deploy.715230, line 142
| 	#2: main, /home/test/projects/OTOTRAK/Yocto_Workspace/tisdk/build/arago-tmp-default-glibc/work/am62xx_custom_k3r5-oe-linux-gnueabi/ti-sci-fw/08.06.04-r4.0.psdk1/temp/run.do_deploy.715230, line 146
ERROR: Task (mc:k3r5:/home/test/projects/OTOTRAK/Yocto_Workspace/tisdk/sources/meta-ti/meta-ti-bsp/recipes-bsp/ti-sci-fw/ti-sci-fw_git.bb:do_deploy) failed with exit code '1'
NOTE: Tasks Summary: Attempted 8069 tasks of which 8068 didn't need to be rerun and 1 failed.
NOTE: Writing buildhistory
NOTE: Writing buildhistory took: 2 seconds
NOTE: Writing buildhistory
NOTE: Writing buildhistory took: 2 seconds
 
Summary: 1 task failed:
  mc:k3r5:/home/test/projects/OTOTRAK/Yocto_Workspace/tisdk/sources/meta-ti/meta-ti-bsp/recipes-bsp/ti-sci-fw/ti-sci-fw_git.bb:do_deploy
Summary: There was 1 WARNING message.
Summary: There was 1 ERROR message, returning a non-zero exit code.

Please correct me if my above changes are wrong for custom machine name build  ?

Thanks, Naresh

Hi Naresh,

good to see you are still trying to make some progress here by yourself. As stated earlier I'm out of office this week so the earliest I can look into this in more detail is next week. Thanks for your patience.

Regards, Andreas

Sure , ThankQ so much  Andreas . 

Kindly update once you are back to work 

Br,Naresh

Hi Andreas, 

If possbile , could you please update on this today .

Thanks for supporting .

BR,

Naresh

Hi Naresh,

I started looking into this. Should have some steps tomorrow if things go well. Stay tuned.

Regards, Andreas

SUre Andreas ,

Thank you for Quick response .

Br, Naresh

Hi Naresh,

I was able to setup a new am62xx-custom MACHINE as follows...

# Changes to 'meta-ti'
a0797059@dasso:~/tisdk/am62xx-evm/sources (dev)
$ git -C meta-ti diff --cached
diff --git a/meta-ti-bsp/conf/machine/am62xx-custom-k3r5.conf b/meta-ti-bsp/conf/machine/am62xx-custom-k3r5.conf
new file mode 100644
index 00000000..f48ff06b
--- /dev/null
+++ b/meta-ti-bsp/conf/machine/am62xx-custom-k3r5.conf
@@ -0,0 +1,12 @@
+#@TYPE: Machine
+#@NAME: AM62XX Custom Board (R5F)
+#@DESCRIPTION: Machine configuration for custom AM62XX board (R5F core)
+
+require conf/machine/include/k3r5.inc
+require conf/machine/include/ti-extras.inc
+
+SYSFW_SOC = "am62x"
+SYSFW_CONFIG = "evm"
+SYSFW_SUFFIX = "hs-fs"
+
+UBOOT_MACHINE = "am62x_evm_r5_defconfig"
diff --git a/meta-ti-bsp/conf/machine/am62xx-custom.conf b/meta-ti-bsp/conf/machine/am62xx-custom.conf
new file mode 100644
index 00000000..a829cb91
--- /dev/null
+++ b/meta-ti-bsp/conf/machine/am62xx-custom.conf
@@ -0,0 +1,12 @@
+#@TYPE: Machine
+#@NAME: AM62XX Custom Board
+#@DESCRIPTION: Machine configuration for custom AM62XX board
+
+require conf/machine/include/am62xx.inc
+require conf/machine/include/ti-extras.inc
+
+KERNEL_DEVICETREE = " \
+    ti/k3-am625-custom.dtb \
+"
+
+UBOOT_MACHINE = "am62x_evm_a53_defconfig"


# Changes to 'meta-tisdk'
a0797059@dasso:~/tisdk/am62xx-evm/sources (dev)
$ git -C meta-tisdk/ diff
diff --git a/recipes-core/images/tisdk-core-bundle.bbappend b/recipes-core/images/tisdk-core-bundle.bbappend
index 4f2e42f..2890173 100644
--- a/recipes-core/images/tisdk-core-bundle.bbappend
+++ b/recipes-core/images/tisdk-core-bundle.bbappend
@@ -31,6 +31,7 @@ DTB_FILTER:j721s2 = "j721s2\|am68\|fpdlink"
 DTB_FILTER:j784s4 = "j784s4\|am69\|fpdlink"
 DTB_FILTER:j722s = "j722s\|fpdlink"
 DTB_FILTER:am65xx = "k3-am654"
+DTB_FILTER:am62xx-custom = "k3-am625"
 DTB_FILTER:am62xx-evm = "k3-am625"
 DTB_FILTER:am62xx-lp-evm = "k3-am62-lp\|k3-am625-sk"
 DTB_FILTER:am62xxsip-evm = "k3-am625"

...and with this do a successful build of the tisdk-base-image target...

a0797059@dasso:~/tisdk/am62xx-evm/build (dev)
$ MACHINE=am62xx-custom bitbake -k tisdk-base-image
....
....
NOTE: Tasks Summary: Attempted 6176 tasks of which 5607 didn't need to be rerun and all succeeded.
NOTE: Writing buildhistory
NOTE: Writing buildhistory took: 4 seconds
NOTE: Writing buildhistory
NOTE: Writing buildhistory took: 3 seconds

Summary: There were 10 WARNING messages.

...generating the expected output images....

a0797059@dasso:~/tisdk/am62xx-evm/build (dev)
$ ll deploy-ti/images/am62xx-custom/*wic*
-rw-r--r-- 2 a0797059 a0797059      3392 May 21 15:42 deploy-ti/images/am62xx-custom/tisdk-base-image-am62xx-custom-20240521203049.rootfs.wic.bmap
-rw-r--r-- 2 a0797059 a0797059 109402376 May 21 15:42 deploy-ti/images/am62xx-custom/tisdk-base-image-am62xx-custom-20240521203049.rootfs.wic.xz
lrwxrwxrwx 2 a0797059 a0797059        61 May 21 15:42 deploy-ti/images/am62xx-custom/tisdk-base-image-am62xx-custom.wic.bmap -> tisdk-base-image-am62xx-custom-20240521203049.rootfs.wic.bmap
lrwxrwxrwx 2 a0797059 a0797059        59 May 21 15:42 deploy-ti/images/am62xx-custom/tisdk-base-image-am62xx-custom.wic.xz -> tisdk-base-image-am62xx-custom-20240521203049.rootfs.wic.xz

...and booting the image without any issues. Note how the MACHINE name propagated into the command prompt.

 _____                    _____           _         _
|  _  |___ ___ ___ ___   |  _  |___ ___  |_|___ ___| |_
|     |  _| .'| . | . |  |   __|  _| . | | | -_|  _|  _|
|__|__|_| |__,|_  |___|  |__|  |_| |___|_| |___|___|_|
              |___|                    |___|

am62xx-custom login:
root@am62xx-custom:~#
root@am62xx-custom:~#

Regards, Andreas

Hi Andreas,

Thank you so much for your support and quick response.

/tisdk/sources/meta-processor-sdk/recipes-core/images$ vim  tisdk-core-bundle.bbappend ; Here, in this file it doesnot have such information which you have mentoined below

DTB_FILTER:j784s4 = "j784s4\|am69\|fpdlink"
DTB_FILTER:j722s = "j722s\|fpdlink"
DTB_FILTER:am65xx = "k3-am654"
DTB_FILTER:am62xx-evm = "k3-am625"
DTB_FILTER:am62xx-lp-evm = "k3-am62-lp\|k3-am625-sk"
DTB_FILTER:am62xxsip-evm = "k3-am625"

tisdk-core-bundle.bbappend

PR:append = ".psdk3"

DEPLOY_IMAGES_NAME:append:am64xx-evm = " \
    tiboot3-am64x_sr2-hs-fs-evm.bin \
    tiboot3-am64x_sr2-hs-evm.bin \
    tiboot3-am64x-gp-evm.bin \
    ti-sci-firmware-am64x_sr2-hs-fs-cert.bin \
    ti-sci-firmware-am64x_sr2-hs-fs-enc.bin \
    ti-sci-firmware-am64x_sr2-hs-cert.bin \
    ti-sci-firmware-am64x_sr2-hs-enc.bin \
    fitImage \
    fitImage-its-am64xx-evm \
    wificfg \
"

DEPLOY_IMAGES_NAME:append:am62xx-evm = " \
    tiboot3-am62x-hs-fs-evm.bin \
    tiboot3-am62x-hs-evm.bin \
    tiboot3-am62x-gp-evm.bin \
    ti-fs-firmware-am62x-hs-fs-enc.bin \
    ti-fs-firmware-am62x-hs-fs-cert.bin \
    ti-fs-firmware-am62x-hs-enc.bin \
    ti-fs-firmware-am62x-hs-cert.bin \
    ti-fs-firmware-am62x-gp.bin \
    ipc_echo_testb_mcu1_0_release_strip.xer5f \
    fitImage \
    fitImage-its-am62xx-evm \
    wificfg \
"

DEPLOY_IMAGES_NAME:append:am62xx-lp-evm = " \
    tiboot3-am62x-hs-evm.bin \
    ti-fs-firmware-am62x-hs-enc.bin \
    ti-fs-firmware-am62x-hs-cert.bin \
    ti-fs-firmware-am62x-hs-fs-enc.bin \
    ti-fs-firmware-am62x-hs-fs-cert.bin \
    ti-fs-firmware-am62x-gp.bin \
    ipc_echo_testb_mcu1_0_release_strip.xer5f \
    fitImage \
    fitImage-its-am62xx-lp-evm \
    wificfg \
"

DEPLOY_IMAGES_NAME:append:am65xx-evm = " \
    tiboot3.bin \
    sysfw-am65x_sr2-evm.itb \
    sysfw-am65x-evm.itb \
    ti-sci-firmware-am65x_sr2-gp.bin \
"
....................................................
.....................................................
....................................................
etc

But here in arago path "meta-arago/meta-arago-distro/recipes-core/images/tisdk-core-bundle.inc " having such info, please find below.

# This include is for the common setting used to build TISDK images.  These images
# include both host and target side content.
LICENSE = "MIT"

IMAGE_FSTYPES = "tar.xz"
IMAGE_NAME_SUFFIX = ""

inherit tisdk-bundle

COMPATIBLE_MACHINE = "omapl138|ti33x|ti43x|omap-a15|k3"

# List of packages to remove from the host package.  This is usually due to
# licensing issues and unneeded dependencies.
HOST_CLEANUP_PACKAGES = ""
TOOLCHAIN_CLEANUP_PACKAGES = "libgnutls-dev libgnutls-extra26 libgnutls-openssl27 libtasn1-dev"

# Set DTB filters for each machine.  Use "unknown" by default to avoid
# picking up DTB files for devices with no DTB support.
DTB_FILTER = "unknown"
DTB_FILTER:ti33x = "am335x"
DTB_FILTER:dra7xx-evm = "dra7"
DTB_FILTER:am57xx-evm = "am57xx"
DTB_FILTER:am57xx-hs-evm = "${DTB_FILTER:am57xx-evm}"
DTB_FILTER:ti43x = "am43"
DTB_FILTER:omapl138 = "da850"
DTB_FILTER:am65xx = "am65"
DTB_FILTER:j721e = "j721e"
DTB_FILTER:j7200 = "j7200"
DTB_FILTER:j721s2 = "j721s2"

# List of target side images to build for the SDK
TARGET_IMAGES = "tisdk-base-image tisdk-default-image tisdk-thinlinux-image tisdk-bootstrap-image"

TISDK_TOOLCHAIN = "${@bb.utils.contains('DISTRO_FEATURES','opengl','meta-toolchain-arago-tisdk','meta-toolchain-arago-tisdk-server',d)}"
TOOLCHAIN_SUFFIX = "${@bb.utils.contains('DISTRO_FEATURES','opengl','-tisdk','-tisdk-server',d)}"

IMAGE_INSTALL = "\
    packagegroup-arago-tisdk-amsdk-sdk-host \

Only below layaers avaible in source path 

Yocto_Workspace/tisdk/sources$ ls
bitbake meta-arago meta-arm meta-edgeai meta-openembedded meta-processor-sdk meta-qt5 meta-ti meta-virtualization oe-core

Kindly help me on this .

BR, Naresh

Hi Naresh,

My instructions/steps should apply on a fresh installation of our SDK v9.2 instructions as per https://software-dl.ti.com/processor-sdk-linux/esd/AM62X/09_02_01_09/exports/docs/linux/Overview_Building_the_SDK.html

I see in your logs some references to older SDK v8.6 items, and perhaps you have some additional customizations or layer mix/matching going on that is not apparent. Please do a clean setup of SDK v9.2 and re-try.

Also, in case you are using SDK v8.x, I've seen people make it work but it is a ton of work/headache customizing the machine name in this context due to lack of proper abstraction between MACHINE and SOC items, so this is not something I'd recommend doing as it cannot be done cleanly in a simple fashion. Also this being an older SDK it is not something we can support here with a ton of extra effort in the forum. In just a few months we'll be releasing SDK v10 so you should really be on 9.2 to at least to not fall too far behind here.

Regards, Andreas

Hi Andreas,

Got it.

Actually, i have done this activity on fresh build (SDK_09_00_00_03).

And i didn't add any patches from SDK_08_06_04. Even i am getting firmware issues.

Even if i am not applying any patches, just adding changes which mentioned then also getting firmware issue on SDK_09_00_0003.

But i was compiled  the yocto build successfully with custom machine name changes  on  SDK_09_02_01_09.  

Could you please help  me  how  to change custom machine name in SDK_09_00_00_03  and build it  ? do we need any extra changes required to build SDK_09_00_00_03 ?

--------------------------------------------------------------------------------------------------------------------------------------------------------------------------

SDK_09_00_00_03 has Linux kernel 6.1.33 (actually i made BSP changes in 6.1.33 linux kernel)

SDK_09_02_01_09 has Linux kernel 6.1.80 

Should I apply Linux kernel 6.1.33 patches to SDK_09_02_01_09(Linux kernel: 6.1.80) Yocto build? or any issues will Ariases?

Thanks, Naresh