trying to re-animate my jetson-nano-b01

[janesser]

I am stuck with that error for a while. Help would be highly appreciated.

| make -f /home/jan/projs/kirkstone-jetson-nano/build/tmp/work/jetson_nano_devkit-poky-linux/u-boot-tegra/1_2022.01+gAUTOINC+894fa67d7f-r0/git/scripts/Makefile.build obj=arch/arm/dts dtbs
| test -e arch/arm/dts/tegra210-p3450-0000.dtb || (                                             \
| echo >&2;                                                     \
| echo >&2 "Device Tree Source (arch/arm/dts/tegra210-p3450-0000.dtb) is not correctly specified.";     \
| echo >&2 "Please define 'CONFIG_DEFAULT_DEVICE_TREE'";                \
| echo >&2 "or build with 'DEVICE_TREE=<device_tree>' argument";        \
| echo >&2;                                                     \
| /bin/false)

Haven't tried anything fancy, see my config files here: https://github.com/janesser/kirkstone-jetson-nano/tree/main/build/conf

[kekiefer]

Have you tried to build and compare results against the tegra-demo-distro?

[janesser]

@kekiefer thanks for your prompt reply.

i tried tegra-demo-distro (device=jetson-nano-devkit-emmc on branch kirkstone-l4t-r32.7.x)

/tegra-demo-distro/build-testdistro/tmp/work/aarch64-linux/rust-llvm-native/1.│
59.0-r0/rustc-1.59.0-src/src/llvm-project/llvm/include/llvm/ADT/PointerSumType.h:279:21: warnin│
g: expected ‘template’ keyword before dependent template name [-Wmissing-template-keyword]     │
|   279 |     return SumType::create<SomeTag>(SomePointerInfo::getTombstoneKey());             │
|       |                     ^~~~~~                                                           │
|       |                     template                                                         │
| ninja: build stopped: subcommand failed.                                                     │
| WARNING: exit code 1 from a shell command.
ERROR: Task (virtual:native:/home/jan/projs/tegra-demo-distro/layers/meta/recipes-devtools/rust│
/rust-llvm_1.59.0.bb:do_compile) failed with exit code '1'

that is unrelated to my original, i am afraid tegra-demo-distro has rather more than less issues.

are there any hints how i could get the dtb files that are actually running on the jetson-nano into above mentioned situation.

[madisongh]

What are you using for the build host? Since this failure is from a -native recipe, I suspect it has something to do with the version of gcc/g++ you have installed - make sure it's not too new.

The autobuilder's last build off kirkstone-l4t-r32.7.x built OK, and step 13 of that build targets jetson-nano-devkit-emmc. We use Ubuntu 22.04 for running those builds.

[janesser]

That might be the problem with respect to rust-llvm.

cat /etc/lsb-release
Build Configuration:                                                                           │DISTRIB_ID=Ubuntu
BB_VERSION           = "2.0.0"                                                                 │DISTRIB_RELEASE=24.04
BUILD_SYS            = "aarch64-linux"                                                         │DISTRIB_CODENAME=noble
NATIVELSBSTRING      = "universal"                                                             │DISTRIB_DESCRIPTION="Ubuntu 24.04.4 LTS"

gcc --version
gcc (Ubuntu 13.3.0-6ubuntu2~24.04.1) 13.3.0
Copyright (C) 2023 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
``

i will dockerize or downgrade next. on the other hand is rust-llvm essential or can be excluded ?

KR, Jan

[madisongh]

Some open-source packages that are part of most builds are written in Rust, so yeah, building the Rust toolchain is pretty standard these days.

[kekiefer]

Yeah, this is a little bit perplexing. I quickly reviewed the u-boot tegra sources and everything looks correctly specified for this machine. Web searches for this issue point to the dtb not being specified in the makefile as the culprit, but it looks like it's there. We're relying on the u-boot recipe from openembedded-core for this, which in kirkstone is packaged with poky. So you might try rolling this back to an older vintage?

[janesser]

as suggested i dockerized into compatible ubuntu (this running on jetson itself docker on ubuntu 18)

now i am getting other errors. is there a cicd log i could use as reference, to rule out if i have any local issues ?

NOTE: Tasks Summary: Attempted 2373 tasks of which 0 didn't need to be rerun and all succeeded.

Summary: There were 163 WARNING messages.
Summary: There were 5 ERROR messages, returning a non-zero exit code.
Loading cache: 100% |##################################################################################################################################################################################| Time: 0:00:02
Loaded 3784 entries from dependency cache.
NOTE: Resolving any missing task queue dependencies

Build Configuration:
BB_VERSION           = "2.0.0"
BUILD_SYS            = "aarch64-linux"
NATIVELSBSTRING      = "universal"
TARGET_SYS           = "aarch64-poky-linux"
MACHINE              = "jetson-nano-devkit-emmc"
DISTRO               = "poky"
DISTRO_VERSION       = "4.0.35"
TUNE_FEATURES        = "aarch64 armv8a crc"
TARGET_FPU           = ""
meta
meta-poky
meta-yocto-bsp       = "kirkstone:393064579dfdd0ed2d4ed4c27d238d7d2292c08b"
meta-tegra           = "kirkstone-l4t-r32.7.x:94e3db3146dc273ec1df463426c0fcaeacc51b5f"
meta-oe
meta-python          = "kirkstone:ce8539c941f6fcbecaca4d16640ac105c0595589"

Initialising tasks: 100% |#############################################################################################################################################################################| Time: 0:01:38
Checking sstate mirror object availability: 100% |#####################################################################################################################################################| Time: 0:01:31
Sstate summary: Wanted 1947 Local 0 Mirrors 321 Missed 1626 Current 0 (16% match, 0% complete)
NOTE: Executing Tasks
ERROR: linux-libc-headers-5.16-r0 do_unpack: Bitbake Fetcher Error: UnpackError('Unpack command PATH="/workspace/build/kirkstone-jetson-nano/build/tmp/sysroots-uninative/aarch64-linux/usr/bin:/workspace/build/kirks
tone-jetson-nano/poky/scripts:/workspace/build/kirkstone-jetson-nano/build/tmp/work/armv8a-poky-linux/linux-libc-headers/5.16-r0/recipe-sysroot-native/usr/bin/aarch64-poky-linux:/workspace/build/kirkstone-jetson-na
no/build/tmp/work/armv8a-poky-linux/linux-libc-headers/5.16-r0/recipe-sysroot/usr/bin/crossscripts:/workspace/build/kirkstone-jetson-nano/build/tmp/work/armv8a-poky-linux/linux-libc-headers/5.16-r0/recipe-sysroot-n
ative/usr/sbin:/workspace/build/kirkstone-jetson-nano/build/tmp/work/armv8a-poky-linux/linux-libc-headers/5.16-r0/recipe-sysroot-native/usr/bin:/workspace/build/kirkstone-jetson-nano/build/tmp/work/armv8a-poky-linu
x/linux-libc-headers/5.16-r0/recipe-sysroot-native/sbin:/workspace/build/kirkstone-jetson-nano/build/tmp/work/armv8a-poky-linux/linux-libc-headers/5.16-r0/recipe-sysroot-native/bin:/workspace/build/kirkstone-jetson
-nano/poky/bitbake/bin:/workspace/build/kirkstone-jetson-nano/build/tmp/hosttools" xz -dc /workspace/build/kirkstone-jetson-nano/build/downloads/linux-5.16.tar.xz | tar --extract --no-same-owner -f - failed with re
turn value 2', 'https://cdn.kernel.org/pub/linux/kernel/v5.x/linux-5.16.tar.xz')
ERROR: Logfile of failure stored in: /workspace/build/kirkstone-jetson-nano/build/tmp/work/armv8a-poky-linux/linux-libc-headers/5.16-r0/temp/log.do_unpack.32443
ERROR: Task (/workspace/build/kirkstone-jetson-nano/poky/meta/recipes-kernel/linux-libc-headers/linux-libc-headers_5.16.bb:do_unpack) failed with exit code '1'
NOTE: Tasks Summary: Attempted 576 tasks of which 179 didn't need to be rerun and 1 failed.

Summary: 1 task failed:
  /workspace/build/kirkstone-jetson-nano/poky/meta/recipes-kernel/linux-libc-headers/linux-libc-headers_5.16.bb:do_unpack
Summary: There was 1 ERROR message, returning a non-zero exit code.

[madisongh]

The specific error looks like another environmental issue, but even if you get past that, I wouldn't be surprised if there are other failures later. Builds for versions that old were pretty much expected to run on x86-64 machines, and some of the NVIDIA tools used during the build are pre-built x86-64 or i386 binaries. They might be made to work if you've got binfmt support enabled, but really, you're pretty much on your own with this kind of setup.

[janesser]

Hi @madisongh ,

Thanks for giving directions, moving my container to amd64 now.

Cheers, Jan

[janesser]

Good news, for referal i built tegra-demo-distro.

Docker Setup like described here: https://github.com/OE4T/tegra-demo-distro/compare/kirkstone-l4t-r32.7.x...janesser:tegra-demo-distro:kirkstone-l4t-r32.7.x?expand=1

I am heading forward to bring it on hardware towards end of the week.

[janesser]

i made it work, hickups are documented here: https://github.com/janesser/tegra-demo-distro/blob/kirkstone-l4t-r32.7.x/README.md

many thanks for the support here @madisongh @kekiefer