SK-AM62A-LP: Yocto ti-vision-apps fails to download from repo for both 10.00 and 10.01

Hi Noah,

Noah said:

error: command 'sync' requires repo to be installed first.
        Use "repo init" to install it here.

Are you by any chance using this on something other than Ubuntu 22.04?

I remember seeing issues like this when trying to do builds on Ubuntu 24.04, which is not something we support for SDK v10.x at this time. The `repo` tool version changed, hence the errors.

Can you please try building on Ubuntu 22.04 in case you aren't doing this already.

Regards, Andreas

I'm using the TI container. Only modifications are forcing it to use UID 1000 so as not to run afoul of file permissions issues. So far this is the only error, other layers seem to pull/build just fine.

Separately I did try running a yocto build from the sdk installer, but encountered different issues there, namely a line in processor-sdk-analytics-10_01-config.txt which tries to download from an ssh repo, swapping this to https didn't seem to work either.

Hi Noah,

Noah said:

I'm using the TI container.

Can you point to the very specific container/version you are using?

Also (it should matter less since you are using the container build, but I still would like to know), what's your host OS?

Regards, Andreas

ghcr.io/texasinstruments/ubuntu-distro:latest, and I pulled it 3 days ago or so.

My host is Arch. I could try running this again on mac, but arm, emulating x86 to compile arm is a pretty cursed setup.

The relevant bits:

Bootstrap script elements:

```bootstrap.sh

export MY_UID="$(id -u)"
export MY_GID="$(id -g)"

if $(docker compose &>/dev/null); then
  d_c="docker compose"
else
  d_c="docker-compose"
fi

...

$d_c exec tisdk /bin/bash

...

```

```compose.yml

services:
  tisdk:
    image: ghcr.io/texasinstruments/ubuntu-distro:latest
    user: ${MY_UID}:${MY_GID}
    volumes:
      - .:/home/tisdk
      - /dev:/dev
      - /media/:/media/
    working_dir: /home/tisdk
    privileged: true
    stdin_open: true
    tty: true

```

Commands run inside the container:

```

#!/usr/bin/env bash
export MACHINE=am62axx-evm
export TARGET=tisdk-edgeai-image

... (working in /home/tisdk which is shared with the host and owned by UID 1000)

git clone git.ti.com/.../oe-layersetup.git tisdk-yocto-git

cd tisdk-yocto-git

export CONFIG="configs/processor-sdk-analytics/processor-sdk-analytics-10.01.00-config.txt"

./oe-layertool-setup.sh -f "$CONFIG"
cd build
. conf/setenv
echo 'ARAGO_BRAND = "edgeai"' >> conf/local.conf

MACHINE=$MACHINE ARAGO_RT_ENABLE=1 bitbake $TARGET

```

I just setup a completely new Docker environment from scratch, to build AM62A SDK v10.1, as per

https://software-dl.ti.com/processor-sdk-linux/esd/AM62AX/10_01_00/exports/docs/linux/Overview_Building_the_SDK.html#steps-to-run-yocto-builds-inside-container

https://github.com/TexasInstruments/ti-docker-images?tab=readme-ov-file#steps-to-run-yocto-builds-inside-container

Will see if I can get a successful build with this and report back. It'll take a bit because it'll be a download/build completely from scratch.

Regards, Andreas

Thanks Andreas,

I think the cause may actually be hiding in that first log. I ran it again and encountered what appears to be a new error, but a lot of old ones too.

Why is this variable like this? HOME="/" I also got a: "fatal: cannot make /.repoconfig directory: Permission denied" this time. It seems something somewhere is trying to write stuff to the container root? That's pretty crazy...

Hey Andreas:

 Do you know if an equivalent to run on Ubuntu 24.04.1 LTS is getting into that git repo?  I how about a package to run AM64X SDK V10.1 ?

Thanks

Jim

Hi Noah,

Andreas Dannenberg said:

Will see if I can get a successful build with this and report back. It'll take a bit because it'll be a download/build completely from scratch.

I was able to get to a successful Docker-based build of the AM62A edge AI image without any issues, using the instructions from the SDK.

My host OS was actually Ubuntu 24.04 (note that for this particular OS, you need to run $ sudo apparmor_parser -R /etc/apparmor.d/unprivileged_userns on the command line after booting the system, to work around network permission issues that otherwise would cause the build to fail)

Noah said:

My host is Arch. I could try running this again on mac, but arm, emulating x86 to compile arm is a pretty cursed setup.

You should first try re-creating a good build using a regular Ubuntu 22.04 or 24.04 host OS, like I did, and then look for differences why your setup might not work. We cannot provide much assistance debugging such non-standard setups like you have.

Regards, Andreas

Noted, thank you for confirming, I'll fiddle on my end and ideally report back what the root issue is when I find it. Building code in a shared container path with a UID that doesn't reflect the UID of the host user is generally bad practice, if there is a solution I discover it would be great if it could be evaluated for any upcoming SDK versions/docker recommended processes.

Hi Jim,

Jim Mrowca said:

 Do you know if an equivalent to run on Ubuntu 24.04.1 LTS is getting into that git repo?

Natively building the v10.1 Yocto SDK on both Ubuntu 22.04 as well as Ubuntu 24.04 (officially not supported!) have no issues accessing this repo. I've done both myself.

Jim Mrowca said:

I how about a package to run AM64X SDK V10.1

I don't understand what you mean by this, can you please elaborate further.

Regards, Andreas

Hi Noah,

Noah said:

Building code in a shared container path with a UID that doesn't reflect the UID of the host user is generally bad pract

This seems to be a common/general problem. Doing some quick web search I found this here, which might be helpful: https://nickjanetakis.com/blog/running-docker-containers-as-a-non-root-user-with-a-custom-uid-and-gid

If you get something simple proven and working in the SDK context, feel free to share it here, I'm sure I'd be helpful for others.

Regards, Andreas

Hi Andreas:

 I suspect Ubuntu 24.04 LTS support needs to happen officially on AM64x by SDK 12.0 (already CCS Theia 20 is supporting Ubuntu 24.04 LTS ).

I am quite interested in the  $ sudo apparmor_parser -R /etc/apparmor.d/unprivileged_userns  step you mentioned - is that due to chanes in file permissions?

When I looked at that github location, it seemed to just mention AM62x - so should the process be similar for AM64x

thanks,

Jim