Part Number: SK-AM62
Tool/software:
HI,
I could not compile debian on 09.02.01.010
compile command:sudo ./build.sh am62-bookworm-09.02.01.010
The following problem is found by viewing the am62-bookworm-09.02.01.010.log file
This thread has been locked.
If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.
Part Number: SK-AM62
Tool/software:
HI,
I could not compile debian on 09.02.01.010
compile command:sudo ./build.sh am62-bookworm-09.02.01.010
The following problem is found by viewing the am62-bookworm-09.02.01.010.log file
Hi,
I just started a build to see if I can re-create this or not.
Which commit did you use of the `ti-bdebstrap` repository? (try `git show` and check the commit ID). I noticed the instructions in https://software-dl.ti.com/processor-sdk-linux/esd/AM62X/09_02_01_Debian/exports/docs/debian/Building_Debian_Image.html are broken when used as-is as the current `master` branch has advanced past SDK v9.2 compatibility, so I actually had to manually check out an older commit. I filed an internal issue report as SITSW-5040 to have this fixed.
Also were you ever able to build Debian successfully, or is this your first attempt?
Regards, Andreas
Hi Andi,
my build just completed and didn't have any issues. I followed the instructions at https://software-dl.ti.com/processor-sdk-linux/esd/AM62X/09_02_01_Debian/exports/docs/debian/Building_Debian_Image.html but I made a change to check out the commit needed for SDK v9.2 by creating a new branch as follows:
a0797059@dasso:~/git/ti-bdebstrap (master) $ git checkout -b 09.02.01.010 3d6148c0aafae30a8897bb326d461ca391c4472c Switched to a new branch '09.02.01.010'
Then, I was able to do the build as follows:
a0797059@dasso:~/git/ti-bdebstrap (09.02.01.010) $ sudo -E ./build.sh am62-bookworm-09.02.01.010 am62-bookworm-09.02.01.010 machine: am62xx-evm bsp_version: 09.02.00.010 distro_variant: am62-bookworm host_arch: x86_64 > Arm Toolchain: checking .. > Arm Toolchain: not found. Downloading .. > Arm Toolchain: downloaded .. > Aarch64 Toolchain: checking .. > Aarch64 Toolchain: not found. downloading .. > Aarch64 Toolchain: downloaded .. > Building rootfs .. > BSP sources: checking .. >> atf: not found. cloning .. >> atf: cloned >> optee_os: not found. cloning .. >> optee_os: cloned >> ti-u-boot: not found. cloning .. >> ti-u-boot: cloned >> ti-linux-firmware: not found. cloning .. >> ti-linux-firmware: cloned > BSP sources: cloned > BSP sources: creating backup .. > BSP sources: backup created .. > ATF: building .. > optee: building .. > uboot-r5: building .. > uboot-a53: building .. > Cleaning up am62-bookworm-09.02.01.010 > Packaging am62-bookworm-09.02.01.010
...and after that the build artifacts can be seen here:
a0797059@dasso:~/git/ti-bdebstrap (09.02.01.010) $ ll -hR build build: total 2.1G drwxr-xr-x 3 root root 4.0K Aug 6 02:26 ./ drwxrwxr-x 10 a0797059 a0797059 4.0K Aug 6 02:10 ../ drwxr-xr-x 2 root root 4.0K Aug 6 02:26 am62-bookworm-09.02.01.010/ -rw-r--r-- 1 root root 2.1G Aug 6 02:26 am62-bookworm-09.02.01.010.tar.xz build/am62-bookworm-09.02.01.010: total 2.1G drwxr-xr-x 2 root root 4.0K Aug 6 02:26 ./ drwxr-xr-x 3 root root 4.0K Aug 6 02:26 ../ -rw-r--r-- 1 root root 1.2G Aug 6 02:25 bsp_sources.tar.xz -rw-r--r-- 1 root root 4.0K Aug 6 02:11 config.yaml -rw-r--r-- 1 root root 1.8M Aug 6 02:26 tisdk-am62-bookworm-am62xx-evm-boot.tar.xz -rw-r--r-- 1 root root 988M Aug 6 02:26 tisdk-am62-bookworm-am62xx-evm-rootfs.tar.xz
Some things to double-check...
Regards, Andreas
Hi Andy,
I use the commit is 7a03b21a546d979fe5ca9ea7a4be4c9787551ae7
Yes that looks like a valid commit to me to use. Almost the same I used plus some minor additional fix related to "suspend to RAM" which you may or may not care about in your application.
It is now possible to successfully build a debian system. but I haven't changed anything, It's weird.
This is what I described as point "3" earlier; sometimes build issues are transient. Glad to hear it's working now!!
Thanks, Andreas