PROCESSOR-SDK-J721E: Processor SDK Linux ADAS Yocto build fails

Randy St. John

Tool/software:

I am following the steps outlined here:

https://software-dl.ti.com/jacinto7/esd/processor-sdk-linux-jacinto7/11_00_00_08/exports/docs/linux/Overview_Building_the_SDK.html

To build the tisdk-adas-image.

At first I could not even run bitbake because of Windows Line endings in the "sources/bitbake/bin" directory. I sorted that out but when I run the recommended command line

MACHINE="j721e-evm" bitbake -k tisdk-adas-image

I get many erros similiar to those below:

ERROR: qtbase-native-6.9.1-r0 do_patch: Applying patch '0001-Add-linux-oe-g-platform.patch' on target directory '/home/rstjohn/Repos/NTS2/ti-processor-sdk-linux-adas-evm-11_00_00_08/yocto-build/build/arago-tmp-default-glibc/work/x86_64-linux/qtbase-native/6.9.1/git'
CmdError('quilt --quiltrc /home/rstjohn/Repos/NTS2/ti-processor-sdk-linux-adas-evm-11_00_00_08/yocto-build/build/arago-tmp-default-glibc/work/x86_64-linux/qtbase-native/6.9.1/recipe-sysroot-native/etc/quiltrc push', 0, 'stdout: Applying patch 0001-Add-linux-oe-g-platform.patch
patching file mkspecs/features/qt.prf
Hunk #1 FAILED at 164 (different line endings).
Hunk #2 FAILED at 319 (different line endings).
2 out of 2 hunks FAILED -- rejects in file mkspecs/features/qt.prf
patching file mkspecs/features/qt_functions.prf
Hunk #1 FAILED at 95 (different line endings).
Hunk #2 FAILED at 140 (different line endings).
2 out of 2 hunks FAILED -- rejects in file mkspecs/features/qt_functions.prf
patching file mkspecs/linux-oe-g++/qmake.conf
patching file mkspecs/linux-oe-g++/qplatformdefs.h
patching file mkspecs/oe-device-extra.pri
Patch 0001-Add-linux-oe-g-platform.patch does not apply (enforce with -f)

This may be related to line endings as well.

Why am I getting this and is there a way to fix it?

1 month ago

0 Jared McArthur 1 month ago

TI__Genius 17235 points

Hi Randy,

Randy St. John said:
At first I could not even run bitbake because of Windows Line endings in the "sources/bitbake/bin" directory. I sorted that out but when I run the recommended command line

What do you mean by Windows Line endings?

I have never seen this issue before. What machine and OS are you using to build?

Best,
Jared

0 Randy St. John 1 month ago in reply to Jared McArthur

Prodigy 170 points

Meaning, Windows uses Carriage Return and Line Feed to end lines. Linux only uses Line Feed.

After downloading and installing the SDK, I had to change all the line endings in the python scripts found in yocto_build/build/sources/bitkake/bin using dos2unix for bitbake command to even work.

I am on Ubuntu 24.02, running inside Windows Linux Subsystem (WSL)

0 Jared McArthur 1 month ago in reply to Randy St. John

TI__Genius 17235 points

Hi Randy,

It looks like WSL may not work: https://docs.yoctoproject.org/dev-manual/start.html#preparing-the-build-host

"The Yocto Project is not compatible with version 1 of Windows Subsystem for Linux. It is compatible but neither officially supported nor validated with WSL 2. If you still decide to use WSL please upgrade to WSL 2."

Best,
Jared

0 Randy St. John 1 month ago in reply to Jared McArthur

Prodigy 170 points

I am on Version 2 of WSL

wsl --version
WSL version: 2.5.9.0
Kernel version: 6.6.87.2-1
WSLg version: 1.0.66
MSRDC version: 1.2.6074
Direct3D version: 1.611.1-81528511
DXCore version: 10.0.26100.1-240331-1435.ge-release
Windows version: 10.0.19045.6093

0 Randy St. John 1 month ago

Prodigy 170 points

I understand that TI does not officially test running on WSL 2 but thought here in the forum someone might have got it to work. It worked for us on SDK version 10 but not working for the new Version 11 of the SDK.

0 Jared McArthur 1 month ago in reply to Randy St. John

TI__Genius 17235 points

Hi Randy,

It looks like an issue with the qt6 recipes/patches specifically. Can you try running dos2unix on the files within the meta-qt6 repository?

Best,
Jared

0 Randy St. John 1 month ago in reply to Jared McArthur

Prodigy 170 points

Thats what I thought as well. I converted all *.patch file. Then after that didn't work converted every file under yocto-build/. It almost looks like the patches it is downloading during the bitbake process might have different line endings then the files they are replacing.

I installed the SDK from the *.bin file from the TI site. Maybe if I cloned the SDK repository it might work different? I don't know.

0 Jared McArthur 1 month ago in reply to Randy St. John

TI__Genius 17235 points

Hi Randy,

I doubt it would change anything. All of the sources should be downloaded after the *.bin is installed (they're cloned while running ./oe-layertool-setup.sh).

The patches should be located in meta-qt6:

$ find -name 0001-Add-linux-oe-g-platform.patch
./meta-qt6/recipes-qt/qt6/qtbase/0001-Add-linux-oe-g-platform.patch

Best,
Jared

0 Randy St. John 1 month ago in reply to Jared McArthur

Prodigy 170 points

Thank you for your attempts to help. I have looked at all the files and cannot find why they say the line endings are different. I am going to start fresh and see what happens.

0 Jared McArthur 1 month ago in reply to Randy St. John

TI__Genius 17235 points

Hi Randy,

Sounds good, let me know if any other issues appear.

Best,
Jared

+1 Randy St. John 1 month ago

Prodigy 170 points

So the base of the problem was the following:

My global git line endings settings was wrong. It was set to 'true' wich will checkout files and put /r/n (windows style) for line endings. I changed the global line endings setting to 'input' which leaves line endings alone when checking out.

To list current global settings:
git config --global --list

To change the current setting to not change line endings on checkout

git config --global core.autocrlf=input

Processors

Processors forum

PROCESSOR-SDK-J721E: Processor SDK Linux ADAS Yocto build fails