marcinozog Posted December 30, 2015 Share Posted December 30, 2015 Where are config files in source kernel with function to enable next uart port in udoo? Link to comment Share on other sites More sharing options...
Igor Posted December 30, 2015 Share Posted December 30, 2015 In the source which we use: https://github.com/UDOOboard/linux_kernel/blob/3.14-1.0.x-udoo/arch/arm/boot/dts/imx6qdl-udoo.dtsi#L384-L394 Link to comment Share on other sites More sharing options...
marcinozog Posted January 1, 2016 Author Share Posted January 1, 2016 I'm new, I need to modify the kernel under udoo before compiling, at which point I do that? Link to comment Share on other sites More sharing options...
marcinozog Posted January 1, 2016 Author Share Posted January 1, 2016 I'm trying create new image, but for end i have error in install.log: Fingerprinting. Armbian 4.81 Udoo Debian jessie next Linux 4.2.8 info Displaying message: Building deb package. linux-jessie-root-next-udoo_4.81_armhf.deb info Displaying message: Install locales en_US.UTF-8 info chroot: failed to run command ‘/bin/bash’: No such file or directory Displaying message: Installation of package failed err In install.log from archives: Displaying message: Compiling uboot. Please wait. 2015.10 info 31.12.2015 17:17:23 /home/marcin/sources/u-boot-udoo/2015.10.fslc-qdl/udoo_qdl_config Displaying message: Target directory /home/marcin/output/debs/ info Displaying message: Building deb linux-u-boot-next-udoo_4.81_armhf.deb info Displaying message: Building failed, check configuration. linux-u-boot-next-udoo_4.81_armhf.deb deleted err Link to comment Share on other sites More sharing options...
Igor Posted January 1, 2016 Share Posted January 1, 2016 Where are you compiling this? On what host? Have you read manuals? Reboot if you get such problems, remove cached files and run again. Compilation is working on Ubuntu Trusty (checked this moment), elsewhere you need to install proper compiler. Link to comment Share on other sites More sharing options...
marcinozog Posted January 2, 2016 Author Share Posted January 2, 2016 System ubuntu 14.04 on virtual machine. Today i compiled new image udoo ubuntu trusty 3.14.28 but not boot on my udoo quad. U-Boot SPL 2015.10-armbian (Jan 02 2016 - 11:41:27) U-Boot 2015.10-armbian (Jan 02 2016 - 11:41:27 +0100) CPU: Freescale i.MX6Q rev1.2 at 792 MHz Reset cause: POR Board: UDOO Quad DRAM: 1 GiB MMC: FSL_SDHC: 0 *** Warning - bad CRC, using default environment No panel detected: default to HDMI Display: HDMI (1024x768) In: serial Out: serial Err: serial Net: using phy at 6 FEC [PRIME] Hit any key to stop autoboot: 0 switch to partitions #0, OK mmc0 is current device Scanning mmc Found U-Boot script /boot.scr ** File not found /boot.scr ** ** Unrecognized filesystem type ** Found U-Boot script /boot/boot.scr 590 bytes read in 160 ms (2.9 KiB/s) Running bootscript from mmc ... ## Executing script at 12000000 ** File not found /boot/dtb/imx6q-udoo-hdmi.dtb ** ** Unrecognized filesystem type ** 6681024 bytes read in 483 ms (13.2 MiB/s) Kernel image @ 0x12000000 [ 0x000000 - 0x65f1c0 ] ERROR: Did not find a cmdline Flattened Device Tree Could not find a valid device tree Device Tree: dts/imx6q-udoo-hdmi.dtb ** Unrecognized filesystem type ** Booting from net ... BOOTP broadcast 1 BOOTP broadcast 2 BOOTP broadcast 3 DHCP client bound to address 192.168.0.101 (3016 ms) Using FEC device TFTP from server 0.0.0.0; our IP address is 192.168.0.101; sending through gateway 192.168.0.1 Filename 'zImage'. Load address: 0x12000000 Loading: T T T T T T T T T T Retry count exceeded; starting again BOOTP broadcast 1 BOOTP broadcast 2 BOOTP broadcast 3 DHCP client bound to address 192.168.0.101 (3015 ms) Using FEC device TFTP from server 0.0.0.0; our IP address is 192.168.0.101; sending through gateway 192.168.0.1 Filename 'dts/imx6q-udoo-hdmi.dtb'. Load address: 0x18000000 Loading: T T T T T T T T T T Retry count exceeded; starting again Bad Linux ARM zImage magic! Link to comment Share on other sites More sharing options...
Igor Posted January 2, 2016 Share Posted January 2, 2016 Your kernel is not compiling properly. That's all I can tell from this boot log. Check debug log in output/debug or put it to pastebin.com that I can see more info. Link to comment Share on other sites More sharing options...
zador.blood.stained Posted January 2, 2016 Share Posted January 2, 2016 Found U-Boot script /boot/boot.scr 590 bytes read in 160 ms (2.9 KiB/s) boot.scr is present 6681024 bytes read in 483 ms (13.2 MiB/s) Kernel image @ 0x12000000 [ 0x000000 - 0x65f1c0 ] kernel (zImage) is present ERROR: Did not find a cmdline Flattened Device Tree Could not find a valid device tree but U-Boot didn't load any Device Tree file (this error is printed by u-boot, not by kernel) ** File not found /boot/dtb/imx6q-udoo-hdmi.dtb ** Link to comment Share on other sites More sharing options...
marcinozog Posted January 2, 2016 Author Share Posted January 2, 2016 Install.log : http://pastebin.com/yhHcpXsk Link to comment Share on other sites More sharing options...
Igor Posted January 2, 2016 Share Posted January 2, 2016 Ahaa, I see where is the problem now. Because of this "hack" ... which works for legacy kernel but not for 4.2 ... https://github.com/UDOOboard/uboot-imx/commit/68849f96afa56d5a4cfcdd918bafebc552958d3a if you boot without HDMI ... what happened ? quick solution: copy or link imx6q-udoo.dtb to imx6q-udoo-hdmi.dtb Link to comment Share on other sites More sharing options...
Recommended Posts