Skip to content
View in the app

A better way to browse. Learn more.
Armbian Community Forums

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Cuboxi: Kernel 4.14.y does not compile, failing to compile imx6dl-cubox-i.dtb

gkkpch
in Other families

Featured Replies

Hi,

 

I'm trying to build the next kernel (4.14.y) for Cubox-i, but the process fails here:

  

  DTC     arch/arm/boot/dts/imx6dl-cubox-i.dtb
Error: arch/arm/boot/dts/imx6qdl-cubox-i.dtsi:261.1-9 Label or path vcc_3v3 not found
FATAL ERROR: Syntax error parsing input tree
scripts/Makefile.lib:317: recipe for target 'arch/arm/boot/dts/imx6dl-cubox-i.dtb' failed
make[1]: *** [arch/arm/boot/dts/imx6dl-cubox-i.dtb] Error 1
arch/arm/Makefile:348: recipe for target 'dtbs' failed
make: *** [dtbs] Error 2
make: *** Waiting for unfinished jobs....

When I compiled the kernel approx. 2 months ago (4.15.?) I did not get that error.

Any ideas?

 

 

  • gkkpch changed the title to Cuboxi: Kernel 4.14.y does not compile, failing to compile imx6dl-cubox-i.dtb
51 minutes ago, gkkpch said:

Any ideas?

 


None without providing build logs. I was able to build a kernel without any problem: 

dpkg-deb: building package 'linux-dtb-next-cubox' in '../linux-dtb-next-cubox_5.52_armhf.deb'.
dpkg-deb: building package 'linux-headers-next-cubox' in '../linux-headers-next-cubox_5.52_armhf.deb'.
dpkg-deb: building package 'linux-image-next-cubox' in '../linux-image-next-cubox_5.52_armhf.deb'.
dpkg-genchanges: warning: unknown substitution variable ${kernel:debarch}
dpkg-genchanges: warning: package linux-libc-dev-next-cubox in control file but not in files list
dpkg-genchanges: info: binary-only upload (no source code included)
dpkg-deb: building package 'linux-source-4.14.55-next-cubox' in '/home/igorp/master/.tmp/linux-source-next-cubox_5.52_all.deb'.
[ o.k. ] Kernel build done [ @host ]
[ o.k. ] Target directory [ /home/igorp/master/output/debs/ ]
[ o.k. ] File name [ linux-image-next-cubox_5.52_armhf.deb ]
[ o.k. ] Runtime [ 12 min ]

You can find them under debug subdirectory.

  • Author

question: does it have an influence that you are building version 5.52 and mine was 5.51?

7 minutes ago, gkkpch said:

question: does it have an influence that you are building version 5.52 and mine was 5.51?


5.52 is a development branch which is changed only for Allwinner and Odroid XU4, which are under some heavy changes. I also tried to build on a master branch (5.51) and it also builds. I also notice that you are using Ubuntu Xenial builds host. That should not affect this ... 

 

Try removing the cache directory, mainly sources, and try again. Also, a clean build script would be a way to go.

  • Author

A fresh clone of the build scripts and no modifications, but the result is exactly the same, compile error on imx6dl-cubox-i.dts

 

output.log

patching.log

 

Edit: which build host are you using?

  • Author

 

It looks as if the Armbian imx6dl-cubox-i.dts dtsi includes do not have the vcc_3v3 regulator defined.

When I replace imx6qdl-sr-som.dtsi with the one from the SR 4.9.y kernel, then imx6dl-cubox-i.dts compiles without issues.

 

But, then it fails on one of the next dts: 

arch/arm/boot/dts/imx6dl-hummingboard2.dts:46:10: fatal error: imx6qdl-sr-som-brcm.dtsi: No such file or directory
 #include "imx6qdl-sr-som-brcm.dtsi"
          ^~~~~~~~~~~~~~~~~~~~~~~~~~
compilation terminated.
scripts/Makefile.lib:317: recipe for target 'arch/arm/boot/dts/imx6dl-hummingboard2.dtb' failed
make[1]: *** [arch/arm/boot/dts/imx6dl-hummingboard2.dtb] Error 1
arch/arm/Makefile:348: recipe for target 'dtbs' failed
make: *** [dtbs] Error 2
make: *** Waiting for unfinished jobs....

I don't know why you don't get an error...

On my test Ubuntu Xenial, I am getting strange compiler errors (arm-linux-gnueabihf-gcc: internal compiler error: Killed (program cc1)
) when compiling modern kernels (which can be also related to some KVM bugs, hard to say) ... while Ubuntu Bionic host doesn't produce those errors. Since I am unable to look more into this and since recommended host Bionic works, I can only point you to start with Bionic ...

  • Author

I just finished a compile without the dts patches, that compiles OK (because the vcc_3v3 regulator definition is in imx6ql-sr-som.dtsi).

Nevertheless it is a good thing to setup a Ubuntu Bionic machine and take it from there.

 

  • Author

Unfortunately Ubuntu Bionic does not work for me, tried in a VM and on a laptop, it throws the follwoing error while running the compile script: 

./compile.sh
[ o.k. ] Using config file [ config-default.conf ]
[ warn ] This script requires root privileges, trying to use sudo 
[ o.k. ] Using config file [ config-default.conf ]
[ o.k. ] This script will try to update
remote: Counting objects: 31418, done.
remote: Compressing objects: 100% (9720/9720), done.
remote: Total 31418 (delta 21787), reused 30834 (delta 21269), pack-reused 0
Receiving objects: 100% (31418/31418), 228.85 MiB | 5.76 MiB/s, done.
Resolving deltas: 100% (21787/21787), completed with 323 local objects.
From https://github.com/armbian/build
   0a54d03e..32bf59de master     -> origin/master
 * [new tag]           s500-eol    -> s500-eol
 * [new tag]           v2015.01-rc -> v2015.01-rc
 * [new tag]           v2015.12    -> v2015.12
 * [new tag]           v2016.02    -> v2016.02
 * [new tag]           v2016.06    -> v2016.06
 * [new tag]           v2016.08    -> v2016.08
 * [new tag]           v2016.09    -> v2016.09
 * [new tag]           v2017.01-rc -> v2017.01-rc
 * [new tag]           v2017.07    -> v2017.07
 * [new tag]           v2017.11    -> v2017.11
Updating 0a54d03e..32bf59de
Fast-forward
 lib/configuration.sh | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
Already on 'master'
Your branch is up to date with 'origin/master'.
[ o.k. ] Preparing [ host ]
[ o.k. ] Build host OS release [ bionic ]
[ o.k. ] Syncing clock [ host ]
[ .... ] Downloading [ gcc-linaro-arm-linux-gnueabihf-4.8-2014.04_linux ]
-=O=-    #    #    #    #                                                      
curl: (35) OpenSSL SSL_connect: SSL_ERROR_SYSCALL in connection to dl.uk.armbian.com:443 
-=O=-   #   #    #    #                                                        
curl: (35) OpenSSL SSL_connect: SSL_ERROR_SYSCALL in connection to dl.uk.armbian.com:443 
[ .... ] Verifying 
grep: gcc-linaro-arm-linux-gnueabihf-4.8-2014.04_linux.tar.xz.asc: No such file or directory
md5sum: gcc-linaro-arm-linux-gnueabihf-4.8-2014.04_linux.tar.xz.asc: No such file or directory
[ warn ] Verification failed 
[ .... ] Downloading [ gcc-linaro-4.9.4-2017.01-x86_64_aarch64-linux-gnu ]
-=O=-   #   #    #    #                                                        
curl: (35) OpenSSL SSL_connect: SSL_ERROR_SYSCALL in connection to dl.uk.armbian.com:443 
-=O=-   #   #    #    #                                                        
curl: (35) OpenSSL SSL_connect: SSL_ERROR_SYSCALL in connection to dl.uk.armbian.com:443 
[ .... ] Verifying 
grep: gcc-linaro-4.9.4-2017.01-x86_64_aarch64-linux-gnu.tar.xz.asc: No such file or directory
md5sum: gcc-linaro-4.9.4-2017.01-x86_64_aarch64-linux-gnu.tar.xz.asc: No such file or directory
[ warn ] Verification failed 
[ .... ] Downloading [ gcc-linaro-4.9.4-2017.01-x86_64_arm-linux-gnueabi ]
-=O=-      #    #    #    #                                                    
curl: (35) OpenSSL SSL_connect: SSL_ERROR_SYSCALL in connection to dl.uk.armbian.com:443 
-=O=-            #    #     #     #                                            
curl: (35) OpenSSL SSL_connect: SSL_ERROR_SYSCALL in connection to dl.uk.armbian.com:443 
[ .... ] Verifying 
grep: gcc-linaro-4.9.4-2017.01-x86_64_arm-linux-gnueabi.tar.xz.asc: No such file or directory
md5sum: gcc-linaro-4.9.4-2017.01-x86_64_arm-linux-gnueabi.tar.xz.asc: No such file or directory
[ warn ] Verification failed 
[ .... ] Downloading [ gcc-linaro-4.9.4-2017.01-x86_64_arm-linux-gnueabihf ]
-=O=-    #    #    #    #                                                      
curl: (35) OpenSSL SSL_connect: SSL_ERROR_SYSCALL in connection to dl.uk.armbian.com:443 
-=O=-              #    #     #     #                                          
curl: (35) OpenSSL SSL_connect: SSL_ERROR_SYSCALL in connection to dl.uk.armbian.com:443 
[ .... ] Verifying 
grep: gcc-linaro-4.9.4-2017.01-x86_64_arm-linux-gnueabihf.tar.xz.asc: No such file or directory
md5sum: gcc-linaro-4.9.4-2017.01-x86_64_arm-linux-gnueabihf.tar.xz.asc: No such file or directory
[ warn ] Verification failed 
[ .... ] Downloading [ gcc-linaro-5.5.0-2017.10-x86_64_aarch64-linux-gnu ]
-=O=-      #    #    #    #                                                    
curl: (35) OpenSSL SSL_connect: SSL_ERROR_SYSCALL in connection to dl.uk.armbian.com:443 
-=O=-   #   #    #    #                                                        
curl: (35) OpenSSL SSL_connect: SSL_ERROR_SYSCALL in connection to dl.uk.armbian.com:443 
[ .... ] Verifying 
grep: gcc-linaro-5.5.0-2017.10-x86_64_aarch64-linux-gnu.tar.xz.asc: No such file or directory
md5sum: gcc-linaro-5.5.0-2017.10-x86_64_aarch64-linux-gnu.tar.xz.asc: No such file or directory
[ warn ] Verification failed 
[ .... ] Downloading [ gcc-linaro-5.5.0-2017.10-x86_64_arm-linux-gnueabi ]
-=O=-    #    #    #    #                                                      
curl: (35) OpenSSL SSL_connect: SSL_ERROR_SYSCALL in connection to dl.uk.armbian.com:443 
-=O=-   #   #    #    #                                                        
curl: (35) OpenSSL SSL_connect: SSL_ERROR_SYSCALL in connection to dl.uk.armbian.com:443 
[ .... ] Verifying 
grep: gcc-linaro-5.5.0-2017.10-x86_64_arm-linux-gnueabi.tar.xz.asc: No such file or directory
md5sum: gcc-linaro-5.5.0-2017.10-x86_64_arm-linux-gnueabi.tar.xz.asc: No such file or directory
[ warn ] Verification failed 
[ .... ] Downloading [ gcc-linaro-5.5.0-2017.10-x86_64_arm-linux-gnueabihf ]
-=O=-      #    #    #    #                                                    
curl: (35) OpenSSL SSL_connect: SSL_ERROR_SYSCALL in connection to dl.uk.armbian.com:443 
-=O=-    #    #    #    #                                                      
curl: (35) OpenSSL SSL_connect: SSL_ERROR_SYSCALL in connection to dl.uk.armbian.com:443 
[ .... ] Verifying 
grep: gcc-linaro-5.5.0-2017.10-x86_64_arm-linux-gnueabihf.tar.xz.asc: No such file or directory
md5sum: gcc-linaro-5.5.0-2017.10-x86_64_arm-linux-gnueabihf.tar.xz.asc: No such file or directory
[ warn ] Verification failed 
[ .... ] Downloading [ gcc-linaro-6.4.1-2017.11-x86_64_arm-linux-gnueabihf ]
-=O=-   #   #    #    #                                                        
curl: (35) OpenSSL SSL_connect: SSL_ERROR_SYSCALL in connection to dl.uk.armbian.com:443 
-=O=-    #    #    #    #                                                      
curl: (35) OpenSSL SSL_connect: SSL_ERROR_SYSCALL in connection to dl.uk.armbian.com:443 
[ .... ] Verifying 
grep: gcc-linaro-6.4.1-2017.11-x86_64_arm-linux-gnueabihf.tar.xz.asc: No such file or directory
md5sum: gcc-linaro-6.4.1-2017.11-x86_64_arm-linux-gnueabihf.tar.xz.asc: No such file or directory
[ warn ] Verification failed 
[ .... ] Downloading [ gcc-linaro-6.4.1-2017.11-x86_64_aarch64-linux-gnu ]
-=O=-        #    #    #     #                                                 
curl: (35) OpenSSL SSL_connect: SSL_ERROR_SYSCALL in connection to dl.uk.armbian.com:443 
-=O=-      #    #    #    #                                                    
curl: (35) OpenSSL SSL_connect: SSL_ERROR_SYSCALL in connection to dl.uk.armbian.com:443 
[ .... ] Verifying 
grep: gcc-linaro-6.4.1-2017.11-x86_64_aarch64-linux-gnu.tar.xz.asc: No such file or directory
md5sum: gcc-linaro-6.4.1-2017.11-x86_64_aarch64-linux-gnu.tar.xz.asc: No such file or directory
[ warn ] Verification failed 
[ .... ] Downloading [ gcc-linaro-7.2.1-2017.11-x86_64_aarch64-linux-gnu ]
-=O=-    #    #    #    #                                                      
curl: (35) OpenSSL SSL_connect: SSL_ERROR_SYSCALL in connection to dl.uk.armbian.com:443 
-=O=-                                                           #    #  #  #   
curl: (35) OpenSSL SSL_connect: SSL_ERROR_SYSCALL in connection to dl.uk.armbian.com:443 
[ .... ] Verifying 
grep: gcc-linaro-7.2.1-2017.11-x86_64_aarch64-linux-gnu.tar.xz.asc: No such file or directory
md5sum: gcc-linaro-7.2.1-2017.11-x86_64_aarch64-linux-gnu.tar.xz.asc: No such file or directory
[ warn ] Verification failed 
[ .... ] Downloading [ gcc-linaro-7.2.1-2017.11-x86_64_arm-linux-gnueabihf ]
-=O=-              #    #     #     #                                          
curl: (35) OpenSSL SSL_connect: SSL_ERROR_SYSCALL in connection to dl.uk.armbian.com:443 
-=O=- #   #    #    #                                                          
curl: (35) OpenSSL SSL_connect: SSL_ERROR_SYSCALL in connection to dl.uk.armbian.com:443 
[ .... ] Verifying 
grep: gcc-linaro-7.2.1-2017.11-x86_64_arm-linux-gnueabihf.tar.xz.asc: No such file or directory
md5sum: gcc-linaro-7.2.1-2017.11-x86_64_arm-linux-gnueabihf.tar.xz.asc: No such file or directory
[ warn ] Verification failed 
[ .... ] Downloading [ gcc-linaro-7.2.1-2017.11-x86_64_arm-eabi ]
-=O=-        #    #    #     #                                                 
curl: (35) OpenSSL SSL_connect: SSL_ERROR_SYSCALL in connection to dl.uk.armbian.com:443 
-=O=-    #    #    #    #                                                      
curl: (35) OpenSSL SSL_connect: SSL_ERROR_SYSCALL in connection to dl.uk.armbian.com:443 
[ .... ] Verifying 
grep: gcc-linaro-7.2.1-2017.11-x86_64_arm-eabi.tar.xz.asc: No such file or directory
md5sum: gcc-linaro-7.2.1-2017.11-x86_64_arm-eabi.tar.xz.asc: No such file or directory
[ warn ] Verification failed

I will have to stick to the version without the imx6dl-cubox-i.dts patches as it seems I can build a correctly working volumio image with it.

Perhaps sometime the dts issue will be resolved ;)

output.log

  • Author

Thanks, that did the trick!

 

However, the dts problem is still there.

And it would to be, because the vcc_3v3 regulator definition IS really missing from imx6qdl-sr-som.dtsi after patching.

Just check it out when you have time.

 

(still worth the effort, now I have a clean Ubuntu Bionic dev environment)

  • Author

What would I loose when compiling from the SR 4.9.y kernel repo directly, apart from not having the latest wifi stuff?

 

Btw: In general, would you have issues with us (Volumio team, mainly me) to use your kernels/ uboot for some of the boards you support with Armbian?

It is what I tried for cuboxi here, but got a little stuck because of the issues mentioned.

16 hours ago, gkkpch said:

What would I loose when compiling from the SR 4.9.y kernel repo directly, apart from not having the latest wifi stuff?

 

Those BSP kernels are usually in a pretty bad state. You can only expect more troubles and certainly less support than here. Kernel 4.14.y works well and also SPDIF, which I assume has some value in this case, while it is (was?) broken in more recent kernels. 

 

I will try to check later today again what is causing this problem.

 

  • Author

@IgorThanks for the fix, the kernel build script now works without any issues, much appreciated!!

A volumio version with it, main focus SPDIF, works perfectly with excellent eth0 and usb performance.

Tested it with a cubox 2iex, waiting for confirmation that i4pro also boots (expected as such, but did not work for a previous 4.15.<something>),

 

 

 

7 hours ago, gkkpch said:

Tested it with a cubox 2iex, waiting for confirmation that i4pro also boots (expected as such, but did not work for a previous 4.15.<something>),


In that case further u-boot patching will be required. It's important to catch serial console logs in case it doesn't boot. We might fix that too.

Guest
This topic is now closed to further replies.
Go to topic listing

Account

Navigation

Search

Search

Configure browser push notifications
Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.