From: "JoeB" <joseph.beissel@caci.com>
To: meta-freescale@lists.yoctoproject.org
Subject: Unable to resolve error when attempting to use a custom device tree
Date: Tue, 16 Apr 2024 07:05:48 -0700 [thread overview]
Message-ID: <LnvH.1713276348847803177.kSBY@lists.yoctoproject.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 2554 bytes --]
Yocto Release: Mickledore
I am getting the following error when running "bitbake -c compile virtual/kernel" when attempting to add a custom device tree. I have not been able to figure out what is going on.,
| make[2]: *** No rule to make target 'arch/arm64/boot/dts/freescale/fsl-lx2160a-qds.dtbfreescale/lgs-scv4.dtb'. Stop.
| make[1]: *** [/work/output/build/tmp/work-shared/lx2160ardb/kernel-source/scripts/Makefile.build:500: arch/arm64/boot/dts/freescale] Error 2
| make: *** [/work/output/build/tmp/work-shared/lx2160ardb/kernel-source/Makefile:1471: freescale/fsl-lx2160a-qds.dtbfreescale/lgs-scv4.dtb] Error 2
| ERROR: oe_runmake failed
| WARNING: /work/output/build/tmp/work/lx2160ardb-fsl-linux/linux-qoriq/6.1.55+gitAUTOINC+770c5fe2c1-r0/temp/run.do_compile.515699:307 exit 1 from 'exit 1'
| WARNING: Backtrace (BB generated script):
| #1: bbfatal_log, /work/output/build/tmp/work/lx2160ardb-fsl-linux/linux-qoriq/6.1.55+gitAUTOINC+770c5fe2c1-r0/temp/run.do_compile.515699, line 307
| #2: die, /work/output/build/tmp/work/lx2160ardb-fsl-linux/linux-qoriq/6.1.55+gitAUTOINC+770c5fe2c1-r0/temp/run.do_compile.515699, line 291
| #3: oe_runmake, /work/output/build/tmp/work/lx2160ardb-fsl-linux/linux-qoriq/6.1.55+gitAUTOINC+770c5fe2c1-r0/temp/run.do_compile.515699, line 219
| #4: do_compile, /work/output/build/tmp/work/lx2160ardb-fsl-linux/linux-qoriq/6.1.55+gitAUTOINC+770c5fe2c1-r0/temp/run.do_compile.515699, line 156
| #5: main, /work/output/build/tmp/work/lx2160ardb-fsl-linux/linux-qoriq/6.1.55+gitAUTOINC+770c5fe2c1-r0/temp/run.do_compile.515699, line 311
ERROR: Task (/work/repository/mickledore/meta-qoriq/recipes-kernel/linux/linux-qoriq_6.1.bb:do_compile) failed with exit code '1'
The dts that I am adding is installed at:
/tmp/work/lx2160ardb-fsl-linux/linux-qoriq/6.1.55+gitAUTOINC+770c5fe2c1-r0/arch/arm64/boot/dts/freescale/lgs-scv4.dts
In our customer layer I created the following file structure and associated files:
recipes-kernel
|--- linux
|-- linux-qoriq_%.bbappend
|-- files
|-- lgs-scv4.dts (custom device tree)
My linux-qoriq_%.bbappend contains the following:
KERNEL_DEVICETREE:append = "freescale/lgs-scv4.dtb"
FILESEXTRAPATHS:append := "${THISDIR}/files:"
SRC_URI:append:lx2160ardb = " \
file://lgs-scv4.dts;subdir=arch/${ARCH}/boot/dts/freescale \
"
So it appears that the dts file is getting installed by the above but it is not getting compiled into the dtb. I am not sure what step I am missing.
[-- Attachment #2: Type: text/html, Size: 4167 bytes --]
next reply other threads:[~2024-04-16 14:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-16 14:05 JoeB [this message]
2024-04-17 6:42 ` Unable to resolve error when attempting to use a custom device tree Marco Cavallini
2024-04-17 7:52 ` [meta-freescale] " Andrey Zhizhikin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=LnvH.1713276348847803177.kSBY@lists.yoctoproject.org \
--to=joseph.beissel@caci.com \
--cc=meta-freescale@lists.yoctoproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).