Modifying kernel for LS1046RDB
Hello, I am trying to modify the Kernel of this RDB to add some I2C devices for power monitoring. When I do the update, building the individual images that includes these devices fail with the attached error message.
Steps I am taking -
bitbake -c cleanstate virtual/kernel
bitbake -c patch virtual/kernel
Edit the fsl-ls1046a-rdb.dts file to add the ina209 devices that I want hwmon to monitor.
bitbake -c menuconfig virtual/kernel. In the menu, I add the ina209 device under device drivers\hwmon
bitbake -c compile -f virtual/kernel
bitbake virtual/kernel
bitbake fsl-image-core
At this point the bitbake fails with the attached error log. The installation is working otherwise, I can make other changes and load them onto the board OK, it is just when I modify the kernel that it errors out/
It might be worth noting that I can successfully run bitbake fsl-image-minimal at this point, but that image does not have the hwmon drivers loaded into it.
Can anyone help me with this?
Original Attachment has been moved to: fsl-ls1046a-rdb.dts.zip
Original Attachment has been moved to: log.do_configure.31159.zip
I installed QorIQ-SDK-V2.0-SOURCE-20160527-yocto.iso and then the SDK2.0_LS1046ABSP_V0.4 on top.
I then build the fsl-image-core
Then I followed your procedure:
Edit the fsl-ls1046a-rdb.dts file to add the ina209 devices that I want hwmon to monitor.
bitbake -c menuconfig virtual/kernel. In the menu, I add the ina209 device under device drivers\hwmon
bitbake -c compile -f virtual/kernel
bitbake virtual/kernel
bitbake fsl-image-core
The image built fine.
I am using Ubuntu 14.04
Nelson,
Thanks for your input. Did you also install the QorIQ Linux SDK v2.0 AARCH64 Yocto Cache.iso after installing QorIQ-SDK-V2.0-SOURCE-20160527-yocto.iso?
I will tru a new VM based on Ubuntu 14.04 and not installing the chache iso to see if either help me.
Jeff
Hi Jeff,
Not sure if it would make any difference but I did not use did not use the cache iso.
Thanks
Nelson
All packages are up to date, and this is running on an Ubuntu 15.10 VM.
Below is the console output of the bitbake fsl-image-kernelitb when this fails -
ERROR: oe_runmake failed
ERROR: Function failed: do_configure (log file is located at /home/jeff/QorIQ-SDK-V2.0-20160527-yocto/build_ls1046ardb/tmp/work/ls1046ardb-fsl-linux/usdpaa-apps/git-r0/temp/log.do_configure.22826)
ERROR: Logfile of failure stored in: /home/jeff/QorIQ-SDK-V2.0-20160527-yocto/build_ls1046ardb/tmp/work/ls1046ardb-fsl-linux/usdpaa-apps/git-r0/temp/log.do_configure.22826
Log data follows:
| DEBUG: Executing python function sysroot_cleansstate
| DEBUG: Removing manifest: /home/jeff/QorIQ-SDK-V2.0-20160527-yocto/build_ls1046ardb/tmp/sysroots/ls1046ardb/usr/lib/libapp_rc_ip.a
| DEBUG: Removing manifest: /home/jeff/QorIQ-SDK-V2.0-20160527-yocto/build_ls1046ardb/tmp/sysroots/ls1046ardb/usr/lib/libfra_utils.a
| DEBUG: Removing manifest: /home/jeff/QorIQ-SDK-V2.0-20160527-yocto/build_ls1046ardb/tmp/sysroots/ls1046ardb/usr/lib/libapp_ipsecfwd_net.a
| DEBUG: Removing manifest: /home/jeff/QorIQ-SDK-V2.0-20160527-yocto/build_ls1046ardb/tmp/sysroots/ls1046ardb/usr/lib/libapp_ipsecfwd_ethernet.a
| DEBUG: Removing manifest: /home/jeff/QorIQ-SDK-V2.0-20160527-yocto/build_ls1046ardb/tmp/sysroots/ls1046ardb/usr/lib/libapps_ipsecfwd_arp.a
| DEBUG: Removing manifest: /home/jeff/QorIQ-SDK-V2.0-20160527-yocto/build_ls1046ardb/tmp/sysroots/ls1046ardb/usr/lib/libfra_fman_port.a
| DEBUG: Removing manifest: /home/jeff/QorIQ-SDK-V2.0-20160527-yocto/build_ls1046ardb/tmp/sysroots/ls1046ardb/usr/lib/libapp_lpm_ethernet.a
| DEBUG: Removing manifest: /home/jeff/QorIQ-SDK-V2.0-20160527-yocto/build_ls1046ardb/tmp/sysroots/ls1046ardb/usr/lib/libapp_ipsecfwd_ipsec.a
| DEBUG: Removing manifest: /home/jeff/QorIQ-SDK-V2.0-20160527-yocto/build_ls1046ardb/tmp/sysroots/ls1046ardb/usr/lib/libhash_table.a
| DEBUG: Removing manifest: /home/jeff/QorIQ-SDK-V2.0-20160527-yocto/build_ls1046ardb/tmp/sysroots/ls1046ardb/usr/lib/libapp_lpm_net.a
| DEBUG: Removing manifest: /home/jeff/QorIQ-SDK-V2.0-20160527-yocto/build_ls1046ardb/tmp/sysroots/ls1046ardb/usr/lib/libapp_ipsecfwd_refcount.a
| DEBUG: Removing manifest: /home/jeff/QorIQ-SDK-V2.0-20160527-yocto/build_ls1046ardb/tmp/sysroots/ls1046ardb/usr/lib/libapp_refcount.a
| DEBUG: Removing manifest: /home/jeff/QorIQ-SDK-V2.0-20160527-yocto/build_ls1046ardb/tmp/sysroots/ls1046ardb/usr/lib/libfra_cfg_parser.a
| DEBUG: Removing manifest: /home/jeff/QorIQ-SDK-V2.0-20160527-yocto/build_ls1046ardb/tmp/sysroots/ls1046ardb/usr/lib/libapp_rc_net.a
| DEBUG: Removing manifest: /home/jeff/QorIQ-SDK-V2.0-20160527-yocto/build_ls1046ardb/tmp/sysroots/ls1046ardb/usr/lib/libapp_rc_arp.a
| DEBUG: Removing manifest: /home/jeff/QorIQ-SDK-V2.0-20160527-yocto/build_ls1046ardb/tmp/sysroots/ls1046ardb/usr/lib/libapp_lpm_ip.a
| DEBUG: Removing manifest: /home/jeff/QorIQ-SDK-V2.0-20160527-yocto/build_ls1046ardb/tmp/sysroots/ls1046ardb/usr/lib/libfslcrypto.a
| DEBUG: Removing manifest: /home/jeff/QorIQ-SDK-V2.0-20160527-yocto/build_ls1046ardb/tmp/sysroots/ls1046ardb/usr/lib/libapp_rc_ethernet.a
| DEBUG: Removing manifest: /home/jeff/QorIQ-SDK-V2.0-20160527-yocto/build_ls1046ardb/tmp/sysroots/ls1046ardb/usr/lib/libusdpaa_ppac.a
| DEBUG: Removing manifest: /home/jeff/QorIQ-SDK-V2.0-20160527-yocto/build_ls1046ardb/tmp/sysroots/ls1046ardb/usr/lib/libfra_bpool.a
| DEBUG: Removing manifest: /home/jeff/QorIQ-SDK-V2.0-20160527-yocto/build_ls1046ardb/tmp/sysroots/ls1046ardb/usr/lib/librman_interface.a
| DEBUG: Removing manifest: /home/jeff/QorIQ-SDK-V2.0-20160527-yocto/build_ls1046ardb/tmp/sysroots/ls1046ardb/usr/lib/libusdpaa_syscfg.a
| DEBUG: Removing manifest: /home/jeff/QorIQ-SDK-V2.0-20160527-yocto/build_ls1046ardb/tmp/sysroots/ls1046ardb/usr/lib/libapp_lpm_arp.a
| DEBUG: Removing manifest: /home/jeff/QorIQ-SDK-V2.0-20160527-yocto/build_ls1046ardb/tmp/sysroots/ls1046ardb/usr/lib/libfra_fq_interface.a
| DEBUG: Removing manifest: /home/jeff/QorIQ-SDK-V2.0-20160527-yocto/build_ls1046ardb/tmp/sysroots/ls1046ardb/usr/lib/libapp_ipsecfwd_ip.a
| DEBUG: Removing manifest: /home/jeff/QorIQ-SDK-V2.0-20160527-yocto/build_ls1046ardb/tmp/sysroots/ls1046ardb/sysroot-providers/usdpaa-apps
| DEBUG: Removing manifest: /home/jeff/QorIQ-SDK-V2.0-20160527-yocto/build_ls1046ardb/tmp/sysroots/ls1046ardb/sysroot-providers/
| DEBUG: Removing manifest: /home/jeff/QorIQ-SDK-V2.0-20160527-yocto/build_ls1046ardb/tmp/sysroots/ls1046ardb/usr/lib/
| DEBUG: Removing manifest: /home/jeff/QorIQ-SDK-V2.0-20160527-yocto/build_ls1046ardb/tmp/sysroots/ls1046ardb/usr/
| DEBUG: Python function sysroot_cleansstate finished
| DEBUG: Executing shell function do_configure
| NOTE: make CC=aarch64-fsl-linux-gcc --sysroot=/home/jeff/QorIQ-SDK-V2.0-20160527-yocto/build_ls1046ardb/tmp/sysroots/ls1046ardb LD=aarch64-fsl-linux-ld --sysroot=/home/jeff/QorIQ-SDK-V2.0-20160527-yocto/build_ls1046ardb/tmp/sysroots/ls1046ardb AR=aarch64-fsl-linux-ar ARCH=arm64 clean
| ---- clean ----
| make: execvp: ./lib/common/objs_arm64/app_refcount_refcount.o: Permission denied
| Makefile:277: recipe for target 'clean' failed
| make: *** [clean] Error 127
| WARNING: exit code 1 from a shell command.
| ERROR: oe_runmake failed
| ERROR: Function failed: do_configure (log file is located at /home/jeff/QorIQ-SDK-V2.0-20160527-yocto/build_ls1046ardb/tmp/work/ls1046ardb-fsl-linux/usdpaa-apps/git-r0/temp/log.do_configure.22826)
ERROR: Task 1432 (/home/jeff/QorIQ-SDK-V2.0-20160527-yocto/sources/meta-freescale/recipes-dpaa/usdpaa-apps/usdpaa-apps_git.bb, do_configure) failed with exit code '1'
NOTE: Tasks Summary: Attempted 3025 tasks of which 2829 didn't need to be rerun and 1 failed.
Waiting for 0 running tasks to finish:
Summary: 1 task failed:
/home/jeff/QorIQ-SDK-V2.0-20160527-yocto/sources/meta-freescale/recipes-dpaa/usdpaa-apps/usdpaa-apps_git.bb, do_configure
Summary: There was 1 WARNING message shown.
Summary: There were 2 ERROR messages shown, returning a non-zero exit code.
jeff@jeff-VirtualBox:~/QorIQ-SDK-V2.0-20160527-yocto/build_ls1046ardb$
Based on the attached log, it looks like a corrupt Makefile issue,
make attempts to execvp() a non-executable file
(something that ends with .o). I do not think it is related to the
Device Tree. Looking at the terminal log should give more information
on which package fails and why. Just as a sanity check, make sure you
followed all requirements from the document at the link below: