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.

SK-AM62: Compile debian system, update image source Connection timed out

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

I: running apt-get update...
Get:1 http://mirrors.aliyun.com/debian bookworm InRelease [151 kB]
Get:2 http://mirrors.aliyun.com/debian buster InRelease [122 kB]
Get:4 http://mirrors.aliyun.com/debian bookworm/contrib arm64 Packages [45.7 kB]
Get:5 http://mirrors.aliyun.com/debian bookworm/non-free-firmware arm64 Packages [5832 B]
Get:3 https://texasinstruments.github.io/ti-debpkgs bookworm InRelease [9695 B]
Get:6 http://mirrors.aliyun.com/debian bookworm/main arm64 Packages [8688 kB]
Get:7 https://texasinstruments.github.io/ti-debpkgs bookworm/main Sources [2699 B]
Get:8 https://texasinstruments.github.io/ti-debpkgs bookworm/non-free arm64 Packages [3778 B]
Get:9 https://texasinstruments.github.io/ti-debpkgs bookworm/main arm64 Packages [11.8 kB]
Get:10 http://deb.debian.org/debian bookworm InRelease [151 kB]
Get:11 http://mirrors.aliyun.com/debian buster/main arm64 Packages [7737 kB]
Get:12 http://deb.debian.org/debian bookworm/contrib arm64 Packages [45.7 kB]
Get:13 http://deb.debian.org/debian bookworm/main arm64 Packages [8688 kB]
Get:14 http://mirrors.aliyun.com/debian buster/contrib arm64 Packages [38.4 kB]
Get:15 http://mirrors.aliyun.com/debian buster/non-free arm64 Packages [53.9 kB]
Ign:13 http://deb.debian.org/debian bookworm/main arm64 Packages
Ign:16 http://deb.debian.org/debian bookworm/non-free-firmware arm64 Packages
Ign:13 http://deb.debian.org/debian bookworm/main arm64 Packages
Ign:16 http://deb.debian.org/debian bookworm/non-free-firmware arm64 Packages
Ign:13 http://deb.debian.org/debian bookworm/main arm64 Packages
Ign:16 http://deb.debian.org/debian bookworm/non-free-firmware arm64 Packages
Ign:13 http://deb.debian.org/debian bookworm/main arm64 Packages
Ign:13 http://deb.debian.org/debian bookworm/main arm64 Packages
Ign:13 http://deb.debian.org/debian bookworm/main arm64 Packages
Ign:13 http://deb.debian.org/debian bookworm/main arm64 Packages
Ign:13 http://deb.debian.org/debian bookworm/main arm64 Packages
Err:13 http://deb.debian.org/debian bookworm/main arm64 Packages
Connection timed out [IP: 151.101.90.132 80]
Fetched 17.1 MB in 3min 12s (89.1 kB/s)
Reading package lists...
W: http://mirrors.aliyun.com/debian/dists/bookworm/InRelease: Key is stored in legacy trusted.gpg keyring (/usr/share/keyrings/debian-archive-keyring.gpg), see the DEPRECATION section in apt-key(8) for details.
W: http://mirrors.aliyun.com/debian/dists/buster/InRelease: Key is stored in legacy trusted.gpg keyring (/usr/share/keyrings/debian-archive-keyring.gpg), see the DEPRECATION section in apt-key(8) for details.
W: http://deb.debian.org/debian/dists/bookworm/InRelease: Key is stored in legacy trusted.gpg keyring (/usr/share/keyrings/debian-archive-keyring.gpg), see the DEPRECATION section in apt-key(8) for details.
E: Failed to fetch http://deb.debian.org/debian/dists/bookworm/main/binary-arm64/Packages Connection timed out [IP: 151.101.90.132 80]
E: Some index files failed to download. They have been ignored, or old ones used instead.
E: apt-get update --error-on=any -oAPT::Status-Fd=<$fd> -oDpkg::Use-Pty=false failed
W: listening on child socket failed:
E: mmdebstrap failed to run
2024-08-01 13:47:57,886 bdebstrap ERROR: mmdebstrap failed with exit code 25. See above for details.
There's a Connection timed out problem. Why? Is TI officially under maintenance or update?
This didn't happen when I compiled last week, but the Connection timed out problem started yesterday.
I checked the proxy network and it's working.
  • Hi 

    This E2E was previously blocked for some reason and could not get assigned to the right expert. I have done so now, but the expert has limited access this week, please expect delays 

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

    1. If you are behind a firewall/proxy, make sure the related ENV variables are accessible to the `sudo` user. In my case above variables like `https_proxy` are defined for the current user. And I use `sudo -E` to pass those along to the root user, so that the build process can download the needed files from the Internet

    2. Try building on a different machine / a machine that's directly connected to the Internet (w/o proxy server)

    3. Sometimes download issues can be transient due to temporary network issues. Re-starting the build sometimes allows it to move along further.

    Regards, Andreas

  • Hi Andreas,

        It is now possible to successfully build a debian system. but I haven't changed anything, It's weird.

        I use the  commit is 7a03b21a546d979fe5ca9ea7a4be4c9787551ae7

  • 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