Hi,
I have successfully compiled the kernel without the config: CONFIG_DEBUG_FS=y. But when I enable it, the compiling became failed. The error information shows below:
Please provide the following info (tick the boxes after creating this topic): Software Version
DRIVE OS 6.0.6
DRIVE OS 6.0.5
[√] DRIVE OS 6.0.4 (rev. 1)
DRIVE OS 6.0.4 SDK
other
Target Operating System
[√] Linux
QNX
other
Hardware Platform
DRIVE AGX Orin Developer Kit (940-63710-0010-D00)
DRIVE AGX Orin Developer Kit (940-63710-0010-C00)
[√] DRIVE AGX Orin Developer Kit (not sure its number)
other
SDK Manager Version
[√] 1.9.2.10884
other
Host Machine Version
[√] native Ubuntu Linux 20.04 Host installed with SDK Manager
native Ubuntu Linux 20.04 Host installed with DRIVE OS Docker Containers
native Ubuntu Linux 18.04 Host installed with DRIVE OS Docker Containers
other
Compiler Version
nvidia_6.0.3.0/toolchains/aarch64–glibc–stable-2020.08-1/bin/aarch64-linux-gcc
gcc version 9.3.0 (Buildroot 2020.08)
Dear @haomiao.wang,
Are you using the DRIVE OS 6.0.4 installed using sdkmanager with Devzone credentials? The logs looks like a sepearte release. Please confirm it.
FYI, This forum is intended to support issues related DRIVE AGX Orin Devkit with devzone releases.
@SivaRamaKrishnaNV Hello, I find an interesting thing. The config CONFIG_DEBUG_INFO_BTF and CONFIG_DEBUG_FS can only enable either one. But it will be compiled failed when you enable that two meanwhile.
Dear @haomiao.wang,
I see below command in compile_error.log lotus@ubuntu:~/sda/ad4/lambda/lambda_image_src/6040_sdk/ipu04_soc_linux$ ./zfuse_build.sh host -j40 LOTUS_SOC_V6040_ADMC_V5.4.1A_PP-J1-EU-CS_20230519 LOTUS_sign
This script is not part of DRIVE OS 6.0.4 Devzone release.
@SivaRamaKrishnaNV Yeah, this script is used for generating our filesystem image. But it doesn’t matter, it will execute make kernel image. The important things is the .updated.defconfig. In the compile_error.log, you just only concern the line which I post on:
FAILED unresolved symbol udp6_sock
Just as I mentioned, The compile can be succeed when only enable either CONFIG_DEBUG_INFO_BTF or CONFIG_DEBUG_FS.
Can you take a try please?
By the way, It seems the bug of DRIVE OS 6.0.4. It is ok with DRIVE OS 6.0.6. You can have a try with the config CONFIG_DEBUG_INFO_BTF=y and CONFIG_DEBUG_FS=y meanwhile using DRIVE OS 6.0.4.