[参考译文] PROCESSOR-SDK-AM62X：[AM62X]如何在 Yocto 版本中添加自定义机器名称

您好！

有任何关于这一点的更新吗?

谢谢。

纳雷什

您好、Nareesh、

最好的做法可能是我创建一个示例,说明如何在我们的 SDK v9.x 的上下文中添加自定义机器,但我正在出差一整周 ,所以没有太多的时间,所以可能要等到下周最早,我可以处理这个问题。  同时,我建议您坚持自定义所提供的机器。

此致、Andreas

Sure Andreas ,

谢谢。  

Br、

纳雷什

尊敬的 Andreas：

下面的更改我完成了自定义机器名称构建。

• build/conf/local.conf

             机器?="am62xx-custom"

• sources/meta-ti/meta-ti-bsp/recips-bsp/u-boot/ u-boot-ti.inc 、：：：：  在这里,我没有改变任何东西。
             compatible_machine ="ti soc "

    创建以下2个文件 (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/recips-bsp/u-boot/ ti-extras.inc
              compatible_machine ="am62xx-custom"
• sources/meta-ti/meta-ti-bsp/conf/machine/am62xx-evm-k3r5.conf
              SYSFW_CONFIG ="定制"

在上述更改后,我尝试构建 Yocto ,自定义映像在 " tisdk/build/arago-tmp-default-glibc/deploy/images/am62xx-custom"生成,但由于固件不生成而获得 ti-sci 固件问题。

请在下面找到 ti-sci 固件错误日志。

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.

请更正我的上述更改对自定义机器名称构建错误 吗？

谢谢、Nareesh

当然, ThankQ 如此多的 安德烈亚斯.  

请在您返回工作时更新  

BR、Nareesh

尊敬的 Andreas：  

如果您有,请您今天更新此.

感谢您的支持。

Br、

纳雷什

您好、Nareesh、

我开始研究这种情况。 如果事情进展顺利、明天应该采取一些措施。 持续关注。

此致、Andreas

Sure Andreas ,

感谢您的快速响应。

Br, Naresh

您好、Nareesh、

我能够设置一个新的 am62xx-自定义机器如下...

# 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"

...和这做一个成功的构建 tisdk-base-image 目标...

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.

正在生成预期的输出图像...

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

...并引导映像没有任何问题。 注意计算机名称如何传播到命令提示符中。

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

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

此致、Andreas

尊敬的 Andreas：

非常感谢您的支持和快速响应。

/tisdk/sources/meta-processor-sdk/recipes-core/images vim tisdk-core-bundle.bappend ;在这里,在这个文件中,它没有这样的信息,你已经修改了下面

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.bappend

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

但在这里在 Arago 路径"meta-Arago/meta-Arago-dastro/recips-core/images/tisdk-core-bundle.inc "有这样的信息,请找到下面。

# 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 \

仅低于源路径中可用的隔离层  

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

请帮我解决这个问题。

Br, Naresh

您好、Nareesh、

根据 https://software-dl.ti.com/processor-sdk-linux/esd/AM62X/09_02_01_09/exports/docs/linux/、Overview_Building_the_SDK.html、我的说明/步骤应适用于 SDK v9.2指令的全新安装

我在您的日志中看到了一些对较旧的 SDK v8.6项目的引用、或许您还有一些其他自定义或层混合/匹配正在进行、但这并不明显。 请重新设置 SDK v9.2并重新尝试。

此外、如果您使用的是 SDK v8.x、我看到人们使其正常工作、但在这种情况下自定义机器名称是一项很大的工作/头疼、因为在机器和 SOC 项目之间缺乏适当的抽象、因此这不是我建议做的事情、因为无法以简单的方式轻松完成。 此外、作为一个较旧的 SDK、我们在论坛上花费大量的额外精力无法在此提供支持。 在短短几个月内、我们将会发布 SDK v10、因此您应该处于9.2级别、至少不会落后太多。

此致、Andreas

尊敬的 Andreas：

明白了。

实际上、我已经在全新版本(SDK_09_00_00_03)上完成了本练习。

我没有添加 SDK_08_06_04中的任何补丁。 甚至我遇到了固件问题。

即使我没有应用任何补丁、也只需添加提及的更改、然后还会在 SDK_09_00_0003上获得固件问题。

但我是  在  SDK_09_02_01_09上成功编译 Yocto 的、更改了自定义机器名称。   

您能帮助 我 如何 在 SDK_09_00_00_03中更改自定义机器名称 并进行构建 吗？ 我们是否需要进行任何额外更改来构建 SDK_09_00_00_03？

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

SDK_09_00_00_03具有 Linux 内核6.1.33 (实际上、我在6.1.33 Linux 内核中进行了 BSP 更改)

SDK_09_02_01_09具有 Linux 内核6.1.80  

我是否应该向 SDK_09_02_01_09 (Linux 内核：6.1.80) Yocto 构建应用 Linux 内核6.1.33补丁程序？ 或者有什么问题会 Ariases ?

谢谢、Nareesh