• Announcements

    • 1. Check power supply, check SD card and check other people experiences

      Power supply issues are one of the three biggest issues you'll face when starting with Single Board Computers (SBCs). SD card issues, whether fake or faulty, are another and issues resulting from poor board design is the other common issues you can encounter.   Power supply issues can be tricky. You might have a noisy power supply that works with one board because it has extra filtering, but won't work with another. Or you're using that cheap phone charger because your board has a microUSB connector, and it is either erratic, or doesn't start up, or even becomes the cause of some SD card issues.    Some tips to avoid the most common causes of problems reported:   Don't power via micro USB  - unless you have optimised your setup for low power requirements. Micro USB is great for mobile phones because they are simply charging a battery. It's bad for SBCs. Yes, it does work for a lot of people, but it also causes more problems and headaches over time than it is worth, unless you know exactly what you are doing. If you have a barrel jack power connector on your SBC, use it instead! If there is an option for powering via header connections, use that option!
        Don't use mobile phone chargers. They might be convenient and cheap, but this is because they are meant for charging phones, not powering your SBC which has particular power requirements.
        When you are evaluating a power supply, make sure you run some stress tests on your system to ensure that it will not cause issues down the path.   (Micro) SD card issues can be sneaky. They might appear right at the start causing strange boot and login errors, or they might cause problems over time. It is best to run a test on any new SD card you use, to ensure that it really is what it is, and to ensure that isn't faulty. Armbian provides you a simple way to do this   --   armbianmonitor -c /path/to/device/to/test  
    • 2. Make sure to collect and provide all necessary information

      We can only help if you provide quality information for us to work with. All stable images from the download section are tested, most stable upgrades are tested and we have tens of thousands of users. Even with regular and extensive testings, bugs sometimes do slip through. This is a voluntary support service and is unrelated to board makers, and is not obligated to provide you any answers. Repeated asking the same questions because you're not happy with the answers will result in you being ignored.

      Before you post a question, use the forum search as someone else might have already had the same problem and resolved it. And make sure you've read the Armbian documentation. If you still haven't found an answer, make sure you include the following in your post:   1. Logs when you can boot the board: armbianmonitor -u (paste URL to your forum post)   2. If your board does not boot, provide a log from serial console or at least make a picture, where it stops.   3. Describe the problem the best you can and provide all necessary info that we can reproduce the problem. We are not clairvoyant or mind readers. Please describe your setup as best as possible so we know what your operating environment is like.     We will not help in cases you are not using stable official Armbian builds, you have a problem with 3rd party hardware or reported problem would not be able to reproduced.

UDOO Latest images (next + default) fail to boot after custom kernel
0

15 posts in this topic

Recommended Posts

Hey All -

 

So I decided to upgrade my Udoo from 4.5 (Debian Jessia, kernel 3.14.28) to the latest 5.25 Xenial.

 

I gave next (4.4.46) a try, and it seemed to work awesome, however it seems like no one wants 1wire (still - it only takes up 1 gpio!).

 

I built custom kernels enabling 1wire in the kernel and updated (or for default adding) 1wire to be enabiled in the imx6qdl-udoo.dtsi, however after I install the kernels, it just sits indefinitely at the red Armbian logo on boot.

 

On 4.4.46, i was able to just install all the debs via dpkg -i *.deb

On 3.14.56, I had to use dpkg --force-all -i *.deb

 

Any ideas on what I'm doing wrong?  Its been a while, so I'm sure a bunch has changed, but adding 1wire in the kernel shouldn't cause a freeze

Share this post


Link to post
Share on other sites

I built custom kernels enabling 1wire in the kernel and updated (or for default adding) 1wire to be enabiled in the imx6qdl-udoo.dtsi, however after I install the kernels, it just sits indefinitely at the red Armbian logo on boot.

 

Strange, upgrade / kernel install should work this way. Can you catch boot log via serial console, that we can see more?

Share this post


Link to post
Share on other sites

So one thing I noticed is that armbian's udoo kernel configs (both default & next) are pretty different than from both default & next in respective git repos (patrykk's has all the 1wire stuff as modules, with 1wire as disabled, but you can just rebuild the dtb file) - shouldn't be an issue since I assume you build with the configs in your repo vs theirs..  Below are the my kernel diffs vs armbian, install, and boot log.  I just edited imx6qdl-udoo.dtsi and changed "disabled" to "okay" during kernel config & made the mods - don't think that should cause the boot to break

 

Kernel diffs:

$ diff armbian_default/linux-udoo-next.config linux-udoo-next.config
3c3
< # Linux/arm 4.4.6 Kernel Configuration
---
> # Linux/arm 4.4.0 Kernel Configuration
2055c2055,2082
< # CONFIG_W1 is not set
---
> CONFIG_W1=y
> CONFIG_W1_CON=y
>
> #
> # 1-wire Bus Masters
> #
> # CONFIG_W1_MASTER_DS2490 is not set
> # CONFIG_W1_MASTER_DS2482 is not set
> CONFIG_W1_MASTER_MXC=y
> # CONFIG_W1_MASTER_DS1WM is not set
> CONFIG_W1_MASTER_GPIO=y
>
> #
> # 1-wire Slaves
> #
> CONFIG_W1_SLAVE_THERM=y
> # CONFIG_W1_SLAVE_SMEM is not set
> # CONFIG_W1_SLAVE_DS2408 is not set
> # CONFIG_W1_SLAVE_DS2413 is not set
> # CONFIG_W1_SLAVE_DS2406 is not set
> # CONFIG_W1_SLAVE_DS2423 is not set
> # CONFIG_W1_SLAVE_DS2431 is not set
> # CONFIG_W1_SLAVE_DS2433 is not set
> # CONFIG_W1_SLAVE_DS2760 is not set
> # CONFIG_W1_SLAVE_DS2780 is not set
> # CONFIG_W1_SLAVE_DS2781 is not set
> # CONFIG_W1_SLAVE_DS28E04 is not set
> # CONFIG_W1_SLAVE_BQ27000 is not set
4175a4203
> # CONFIG_DEBUG_UART_BCM63XX is not set
 
Update:
root@udoo:~/kupdate# ls -la
total 17072
drwxr-xr-x 2 root root    4096 Feb 11 23:28 .
drwx------ 7 root root    4096 Feb 11 23:28 ..
-rwxr--r-- 1 root root   50196 Feb 11 06:11 linux-firmware-image-4.4.0-udoo_5.25_armhf.deb
-rwxr--r-- 1 root root 7188908 Feb 11 06:11 linux-headers-4.4.0-udoo_5.25_armhf.deb
-rwxr--r-- 1 root root 9289516 Feb 11 06:12 linux-image-4.4.0-udoo_5.25_armhf.deb
-rwxr--r-- 1 root root  799462 Feb 11 06:11 linux-libc-dev_5.25_armhf.deb
-rwxr--r-- 1 root root  135072 Feb 11 06:03 linux-u-boot-next-udoo_5.25_armhf.deb
root@udoo:~/kupdate# dpkg -i *.deb
Selecting previously unselected package linux-firmware-image-4.4.0-udoo.
(Reading database ... 140089 files and directories currently installed.)
Preparing to unpack linux-firmware-image-4.4.0-udoo_5.25_armhf.deb ...
Unpacking linux-firmware-image-4.4.0-udoo (5.25) ...
Selecting previously unselected package linux-headers-4.4.0-udoo.
Preparing to unpack linux-headers-4.4.0-udoo_5.25_armhf.deb ...
Unpacking linux-headers-4.4.0-udoo (5.25) ...
Selecting previously unselected package linux-image-4.4.0-udoo.
Preparing to unpack linux-image-4.4.0-udoo_5.25_armhf.deb ...
Unpacking linux-image-4.4.0-udoo (5.25) ...
Preparing to unpack linux-libc-dev_5.25_armhf.deb ...
Unpacking linux-libc-dev (5.25) over (4.4.0-59.80) ...
Preparing to unpack linux-u-boot-next-udoo_5.25_armhf.deb ...
Unpacking linux-u-boot-udoo-next (5.25) over (5.25) ...
Setting up linux-firmware-image-4.4.0-udoo (5.25) ...
Setting up linux-headers-4.4.0-udoo (5.25) ...
Setting up linux-image-4.4.0-udoo (5.25) ...
update-initramfs: Generating /boot/initrd.img-4.4.0-udoo
update-initramfs: Converting to u-boot format
Setting up linux-libc-dev (5.25) ...
Setting up linux-u-boot-udoo-next (5.25) ...
Updating u-boot on device /dev/mmcblk0
root@udoo:~/kupdate# 
 
Boot Log (after update):
U-Boot SPL 2015.10-armbian (Feb 10 2017 - 23:03:32)
 
 
U-Boot 2015.10-armbian (Feb 10 2017 - 23:03:32 -0700)
 
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
 
auto-detected panel HDMI
Display: HDMI (1280x720)
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
** Unrecognized filesystem type **
Device Tree: dts/imx6q-udoo-hdmi.dtb
** Unrecognized filesystem type **
Booting from net ...
FEC Waiting for PHY auto negotiation to complete......... TIMEOUT !
BOOTP broadcast 1
BOOTP broadcast 2
BOOTP broadcast 3
BOOTP broadcast 4
BOOTP broadcast 5
BOOTP broadcast 6
BOOTP broadcast 7
BOOTP broadcast 8
BOOTP broadcast 9
BOOTP broadcast 10
BOOTP broadcast 11
BOOTP broadcast 12
BOOTP broadcast 13
BOOTP broadcast 14
BOOTP broadcast 15
BOOTP broadcast 16
BOOTP broadcast 17
 
Retry time exceeded; starting again
FEC Waiting for PHY auto negotiation to complete......... TIMEOUT !
BOOTP broadcast 1
BOOTP broadcast 2
BOOTP broadcast 3
BOOTP broadcast 4
BOOTP broadcast 5
BOOTP broadcast 6
BOOTP broadcast 7
BOOTP broadcast 8
BOOTP broadcast 9
BOOTP broadcast 10
BOOTP broadcast 11
BOOTP broadcast 12
BOOTP broadcast 13
BOOTP broadcast 14
BOOTP broadcast 15
BOOTP broadcast 16
BOOTP broadcast 17
 
Retry time exceeded; starting again
Bad Linux ARM zImage magic!
=>
 

Share this post


Link to post
Share on other sites

Here's the first boot I captured.. I'm going to try again, without updating uboot, just linux-image-4.4.0-udoo_5.25_armhf.deb and linux-firmware-image-4.4.0-udoo_5.25_armhf.deb

 

U-Boot SPL 2015.10-armbian (Feb 02 2017 - 03:15:42)
 
 
U-Boot 2015.10-armbian (Feb 02 2017 - 03:15:42 +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
 
auto-detected panel HDMI
Display: HDMI (1280x720)
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
1757 bytes read in 109 ms (15.6 KiB/s)
Running bootscript from mmc ...
## Executing script at 12000000
Booting from SD
** File not found /boot/armbianEnv.txt **
** Unrecognized filesystem type **
4764730 bytes read in 379 ms (12 MiB/s)
6144136 bytes read in 497 ms (11.8 MiB/s)
0 bytes read in 98 ms (0 Bytes/s)
37690 bytes read in 564 ms (64.5 KiB/s)
Kernel image @ 0x12000000 [ 0x000000 - 0x5dc088 ]
## Loading init Ramdisk from Legacy Image at 14800000 ...
   Image Name:   uInitrd
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    4764666 Bytes = 4.5 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
## Flattened Device Tree blob at 18000000
   Booting using the fdt blob at 0x18000000
   Using Device Tree in place at 18000000, end 1800c339
 
Starting kernel ...
 
Loading, please wait...
starting version 229
Begin: Loading essential drivers ... done.
Begin: Running /scripts/init-premount ... done.
Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done.
Begin: Running /scripts/local-premount ... Scanning for Btrfs filesystems
done.
Begin: Will now check root file system ... fsck from util-linux 2.27.1
[/sbin/fsck.ext4 (1) -- /dev/mmcblk0p1] fsck.ext4 -a -C0 /dev/mmcblk0p1
/dev/mmcblk0p1: clean, 147301/178816 files, 526555/713984 blocks
done.
done.
Begin: Running /scripts/local-bottom ... done.
Begin: Running /scripts/init-bottom ... done.
 
Welcome to Ubuntu 16.04.1 LTS!
 
[  OK  ] Listening on udev Control Socket.
[  OK  ] Set up automount Arbitrary Executab...ats File System Automount Point.
[  OK  ] Listening on /dev/initctl Compatibility Named Pipe.
[  OK  ] Reached target Remote File Systems (Pre).
[  OK  ] Created slice System Slice.
[  OK  ] Created slice system-serial\x2dgetty.slice.
[  OK  ] Reached target Swap.
[  OK  ] Listening on Journal Socket.
         Starting Restore / save the current clock...
[  OK  ] Listening on Syslog Socket.
[  OK  ] Started Forward Password Requests to Wall Directory Watch.
[  OK  ] Created slice User and Session Slice.
         Starting Create list of required st... nodes for the current kernel...
[  OK  ] Reached target Encrypted Volumes.
[  OK  ] Started Dispatch Password Requests to Console Directory Watch.
[  OK  ] Listening on fsck to fsckd communication Socket.
[  OK  ] Listening on udev Kernel Socket.
         Mounting POSIX Message Queue File System...
[  OK  ] Reached target Remote File Systems.
[  OK  ] Reached target User and Group Name Lookups.
         Starting Nameserver information manager...
         Starting Load Kernel Modules...
         Starting Set console keymap...
[  OK  ] Reached target Slices.
         Starting Remount Root and Kernel File Systems...
[  OK  ] Listening on Journal Socket (/dev/log).
[  OK  ] Mounted POSIX Message Queue File System.
[  OK  ] Started Restore / save the current clock.
[  OK  ] Started Create list of required sta...ce nodes for the current kernel.
[  OK  ] Started Load Kernel Modules.
[  OK  ] Started Set console keymap.
[  OK  ] Started Remount Root and Kernel File Systems.
[  OK  ] Started Nameserver information manager.
         Starting udev Coldplug all Devices...
         Starting Load/Save Random Seed...
         Starting Apply Kernel Variables...
         Mounting FUSE Control File System...
         Starting Create Static Device Nodes in /dev...
[  OK  ] Mounted FUSE Control File System.
[  OK  ] Started Load/Save Random Seed.
[  OK  ] Started Apply Kernel Variables.
[  OK  ] Started Create Static Device Nodes in /dev.
         Starting udev Kernel Device Manager...
[  OK  ] Reached target Local File Systems (Pre).
         Mounting /tmp...
[  OK  ] Mounted /tmp.
[  OK  ] Started udev Coldplug all Devices.
[  OK  ] Started udev Kernel Device Manager.
[  OK  ] Started Entropy daemon using the HAVEGE algorithm.
         Starting Journal Service...
[  OK  ] Reached target Local File Systems.
         Starting Raise network interfaces...
         Starting Set console font and keymap...
         Starting Armbian enhanced Log2Ram...
[  OK  ] Found device /dev/ttymxc1.
[  OK  ] Reached target Sound Card.
[  OK  ] Started Journal Service.
[  OK  ] Started Armbian enhanced Log2Ram.
[  OK  ] Started Raise network interfaces.
[  OK  ] Listening on Load/Save RF Kill Switch Status /dev/rfkill Watch.
[  OK  ] Started ifup for eth0.
         Starting Flush Journal to Persistent Storage...
[  OK  ] Started Flush Journal to Persistent Storage.
         Starting Create Volatile Files and Directories...
         Starting Load/Save RF Kill Switch Status...
[  OK  ] Started Create Volatile Files and Directories.
[  OK  ] Started Load/Save RF Kill Switch Status.
         Starting Update UTMP about System Boot/Shutdown...
[  OK  ] Reached target System Time Synchronized.
[  OK  ] Started Update UTMP about System Boot/Shutdown.
[  OK  ] Reached target System Initialization.
[  OK  ] Started Daily Cleanup of Temporary Directories.
[  OK  ] Reached target Paths.
[  OK  ] Listening on D-Bus System Message Bus Socket.
[  OK  ] Started Daily apt activities.
[  OK  ] Reached target Timers.
         Starting Armbian filesystem resize service...
[  OK  ] Listening on Avahi mDNS/DNS-SD Stack Activation Socket.
[  OK  ] Reached target Sockets.
[FAILED] Failed to start Set console font and keymap.
See 'systemctl status console-setup.service' for details.
[  OK  ] Started Armbian filesystem resize service.
[  OK  ] Reached target Basic System.
         Starting LSB: Start/stop sysstat's sadc...
         Starting Accounts Service...
[  OK  ] Started Armbian first run tasks.
[  OK  ] Created slice system-getty.slice.
         Starting Avahi mDNS/DNS-SD Stack...
         Starting LSB: No Display Manager...
         Starting Login Service...
         Starting System Logging Service...
         Starting LSB: Starts LIRC daemon....
[  OK  ] Started Regular background program processing daemon.
         Starting LSB: Load kernel modules needed to enable cpufreq scaling...
         Starting LSB: Armbian gathering hardware information...
[  OK  ] Started D-Bus System Message Bus.
[  OK  ] Started Avahi mDNS/DNS-SD Stack.
         Starting Network Manager...
         Starting Permit User Sessions...
         Starting Save/Restore Sound Card State...
[  OK  ] Started System Logging Service.
[  OK  ] Started Permit User Sessions.
[  OK  ] Started Save/Restore Sound Card State.
[  OK  ] Started LSB: Start/stop sysstat's sadc.
[  OK  ] Started LSB: Armbian gathering hardware information.
[  OK  ] Started LSB: No Display Manager.
[  OK  ] Started LSB: Starts LIRC daemon..
[  OK  ] Started LSB: Load kernel modules needed to enable cpufreq scaling.
[  OK  ] Started Network Manager.
[  OK  ] Started Login Service.
         Starting Network Manager Script Dispatcher Service...
[  OK  ] Reached target Network.
         Starting OpenBSD Secure Shell server...
         Starting Network Manager Wait Online...
         Starting Authenticate and Authorize Users to Run Privileged Tasks...
         Starting LSB: set CPUFreq kernel parameters...
         Starting Set console scheme...
[  OK  ] Started Network Manager Script Dispatcher Service.
[  OK  ] Started Set console scheme.
[  OK  ] Started LSB: set CPUFreq kernel parameters.
         Starting LSB: Set sysfs variables from /etc/sysfs.conf...
         Starting Hostname Service...
[  OK  ] Started LSB: Set sysfs variables from /etc/sysfs.conf.
[  OK  ] Started Authenticate and Authorize Users to Run Privileged Tasks.
[  OK  ] Started Accounts Service.
[  OK  ] Started Hostname Service.
[  OK  ] Started OpenBSD Secure Shell server.
         Starting WPA supplicant...
[  OK  ] Started WPA supplicant.
[  OK  ] Started Network Manager Wait Online.
[  OK  ] Reached target Network is Online.
         Starting LSB: disk temperature monitoring daemon...
         Starting LSB: Start NTP daemon...
         Starting LSB: Advanced IEEE 802.11 management daemon...
         Starting /etc/rc.local Compatibility...
[  OK  ] Started LSB: Advanced IEEE 802.11 management daemon.
[  OK  ] Started /etc/rc.local Compatibility.
[  OK  ] Started LSB: disk temperature monitoring daemon.
[  OK  ] Started Serial Getty on ttymxc1.
[  OK  ] Started Getty on tty1.
[  OK  ] Reached target Login Prompts.
[  OK  ] Started LSB: Start NTP daemon.
[  OK  ] Reached target Multi-User System.
[  OK  ] Reached target Graphical Interface.
         Starting Update UTMP about System Runlevel Changes...
[  OK  ] Started Update UTMP about System Runlevel Changes.
 
Ubuntu 16.04.1 LTS udoo ttymxc1
 
udoo login: root
Password:
You are required to change your password immediately (root enforced)
Changing password for root.
(current) UNIX password:
Enter new UNIX password:
Retype new UNIX password:
 _   _     _
| | | | __| | ___   ___
| | | |/ _` |/ _ \ / _ \
| |_| | (_| | (_) | (_) |
 \___/ \__,_|\___/ \___/
 
 
Welcome to ARMBIAN 5.25 stable Ubuntu 16.04.1 LTS 4.4.46-udoo
System load:   1.77             Up time:       1 min
Memory usage:  3 % of 1002Mb    IP:
CPU temp:      26°C
Usage of /:    8% of 28G
 
New to Armbian? Check the documentation first: docs.armbian.com
 
 
Thank you for choosing Armbian! Support: www.armbian.com
 
Creating a new user account. Press <Ctrl-C> to abort
Desktop environment will not be enabled if you abort the new user creation
 
Please provide a username (eg. your forename):
 
<blah blah blah>
 
Now starting desktop environment...

Share this post


Link to post
Share on other sites

So I did this:

 

sed -i "s/apt/beta/" /etc/apt/sources.list.d/armbian.list
apt-get update
apt-get upgrade

 

and it still boots ("deb http://beta.armbian.com $(lsb_release -cs) main utils $(lsb_release -cs)-desktop" didn't work on xenial)

chiefwigms likes this

Share this post


Link to post
Share on other sites

Also - I updated just the custom kernel and firmware, and the board booted, so I'm guessing it's something with uboot

OK, thank you. Will try to recreate and fix.

Share this post


Link to post
Share on other sites

Good uboot (prior to updating custom kernel):

baudrate=115200
board_rev=MX6Q
boot_a_script=ext2load mmc ${mmcdev}:${mmcpart} ${loadaddr} ${prefix}${script} || fatload mmc ${mmcdev}:${mmcpart} ${loadaddr} ${prefix}${script}
boot_fdt=try
boot_prefixes=/ /boot/
bootcmd=mmc dev ${mmcdev}; if mmc rescan; then if run loadbootscript; then run bootscript; fi; udooinit; if run loadimage; then run mmcboot; else run netboot; fi; else run netboot; fi
bootdelay=3
bootscript=echo Running bootscript from mmc ...; source
console=ttymxc1
ethact=FEC
ethaddr=00:c0:08:88:10:2c
ethprime=FEC
fdt_addr=0x18000000
fdt_file=undefined
fdt_high=0xffffffff
image=zImage
initrd_high=0xffffffff
ip_dyn=yes
loadaddr=0x12000000
loadbootscript=run scan_dev_for_boot;
loadfdt=fatload mmc ${mmcdev}:${mmcpart} ${fdt_addr} ${fdt_file}
loadimage=fatload mmc ${mmcdev}:${mmcpart} ${loadaddr} ${image}
mmcargs=setenv bootargs console=${console},${baudrate} ${video} ${memory} root=${mmcroot} rootfstype=${mmcrootfstype} ahci_imx.hotplug=1
mmcboot=echo Booting from mmc ...; run mmcargs; if test ${boot_fdt} = yes || test ${boot_fdt} = try; then if run loadfdt; then bootz ${loadaddr} - ${fdt_addr}; else if test ${boot_fdt} = try; then bootz; else echo WARN: Cannot load the DT; fi; fi; else bootz; fi;
mmcdev=0
mmcpart=1
mmcroot=/dev/mmcblk0p2 rootwait rw
mmcrootfstype=ext4
netargs=setenv bootargs console=${console},${baudrate} root=/dev/nfs ip=dhcp nfsroot=${serverip}:${nfsroot},v3,tcp
netboot=echo Booting from net ...; run netargs; if test ${ip_dyn} = yes; then setenv get_cmd dhcp; else setenv get_cmd tftp; fi; ${get_cmd} ${image}; if test ${boot_fdt} = yes || test ${boot_fdt} = try; then if ${get_cmd} ${fdt_addr} ${fdt_file}; then bootz ${loadaddr} - ${fdt_addr}; else if test ${boot_fdt} = try; then bootz; else echo WARN: Cannot load the DT; fi; fi; else bootz; fi;
scan_dev_for_boot=echo Scanning mmc ; for prefix in ${boot_prefixes}; do run scan_dev_for_scripts; done
scan_dev_for_scripts=if test -e ${mmcdev}:${mmcpart} ${prefix}${script}; then echo Found U-Boot script ${prefix}${script}; run boot_a_script; else echo Checking here ${prefix} ... not found; fi;
script=boot.scr
splashpos=m,m
update_sd_firmware=if test ${ip_dyn} = yes; then setenv get_cmd dhcp; else setenv get_cmd tftp; fi; if mmc dev ${mmcdev}; then if ${get_cmd} ${update_sd_firmware_filename}; then setexpr fw_sz ${filesize} / 0x200; setexpr fw_sz ${fw_sz} + 1; mmc write ${loadaddr} 0x2 ${fw_sz}; fi; fi
update_sd_firmware_filename=u-boot.imx
 
Environment size: 2528/8188 bytes
 
 
 
Bad uboot (after updating custom kernel):
baudrate=115200
board_rev=MX6Q
boot_fdt=try
bootcmd=mmc dev ${mmcdev}; if mmc rescan; then if run loadbootscript; then run bootscript; fi; udooinit; if run loadimage; then run mmcboot; else run netboot; fi; else run netboot; fi
bootdelay=3
bootscript=echo Running bootscript from mmc ...; env import -t ${loadaddr} ${filesize};
console=ttymxc1
ethact=FEC
ethaddr=00:c0:08:88:10:2c
ethprime=FEC
fdt_addr=0x18000000
fdt_file=undefined
fdt_high=0xffffffff
image=zImage
initrd_high=0xffffffff
ip_dyn=yes
loadaddr=0x12000000
loadbootscript=fatload mmc ${mmcdev}:${mmcpart} ${loadaddr} ${script};
loadfdt=fatload mmc ${mmcdev}:${mmcpart} ${fdt_addr} ${fdt_file}
loadimage=fatload mmc ${mmcdev}:${mmcpart} ${loadaddr} ${image}
mmcargs=setenv bootargs console=${console},${baudrate} ${video} ${memory} root=${mmcroot} rootfstype=${mmcrootfstype} ahci_imx.hotplug=1
mmcboot=echo Booting from mmc ...; run mmcargs; if test ${boot_fdt} = yes || test ${boot_fdt} = try; then if run loadfdt; then bootz ${loadaddr} - ${fdt_addr}; else if test ${boot_fdt} = try; then bootz; else echo WARN: Cannot load the DT; fi; fi; else bootz; fi;
mmcdev=0
mmcpart=1
mmcroot=/dev/mmcblk0p2 rootwait rw
mmcrootfstype=ext4
netargs=setenv bootargs console=${console},${baudrate} root=/dev/nfs ip=dhcp nfsroot=${serverip}:${nfsroot},v3,tcp
netboot=echo Booting from net ...; run netargs; if test ${ip_dyn} = yes; then setenv get_cmd dhcp; else setenv get_cmd tftp; fi; ${get_cmd} ${image}; if test ${boot_fdt} = yes || test ${boot_fdt} = try; then if ${get_cmd} ${fdt_addr} ${fdt_file}; then bootz ${loadaddr} - ${fdt_addr}; else if test ${boot_fdt} = try; then bootz; else echo WARN: Cannot load the DT; fi; fi; else bootz; fi;
script=uEnv.txt
splashpos=m,m
update_sd_firmware=if test ${ip_dyn} = yes; then setenv get_cmd dhcp; else setenv get_cmd tftp; fi; if mmc dev ${mmcdev}; then if ${get_cmd} ${update_sd_firmware_filename}; then setexpr fw_sz ${filesize} / 0x200; setexpr fw_sz ${fw_sz} + 1; mmc write ${loadaddr} 0x2 ${fw_sz}; fi; fi
update_sd_firmware_filename=u-boot.imx
 
Environment size: 2116/8188 bytes
 

 

I did a diff and updated all the variables to match the good uboot, and the new kernel loaded, however I don't see one wire..  I'll mess around more today

Share this post


Link to post
Share on other sites

Find anything?

 

Yes. You must compile kernel by using our tools or include our kernel patches and it will work. We also fixed bugs and prepare kernel packages for our boot scenario. Just in this case everything works simply by installing the package. If not ... you need to set and adjust paths and boot scripts manually.

Share this post


Link to post
Share on other sites

Yes. You must compile kernel by using our tools or include our kernel patches and it will work. We also fixed bugs and prepare kernel packages for our boot scenario. Just in this case everything works simply by installing the package. If not ... you need to set and adjust paths and boot scripts manually.

 

So I must be doing something wrong.  Just did a pull on your repo - attached are my changes:

 

compile.sh

16,17c16,17
< KERNEL_ONLY=""				# leave empty to select each time, set to "yes" or "no" to skip dialog prompt
< KERNEL_CONFIGURE="no"			# change provided kernel configuration
---
> KERNEL_ONLY="yes"				# leave empty to select each time, set to "yes" or "no" to skip dialog prompt
> KERNEL_CONFIGURE="yes"			# change provided kernel configuration
27c27
< KERNEL_KEEP_CONFIG="no"			# do not overwrite kernel config before compilation
---
> KERNEL_KEEP_CONFIG="yes"			# do not overwrite kernel config before compilation
31c31
< FORCE_CHECKOUT="yes"			# ignore manual changes to source
---
> FORCE_CHECKOUT="no"			# ignore manual changes to source
 

kernel config diffs (from your repo):

3c3
< # Linux/arm 4.4.6 Kernel Configuration
---
> # Linux/arm 4.4.0 Kernel Configuration
2055c2055,2082
< # CONFIG_W1 is not set
---
> CONFIG_W1=y
> CONFIG_W1_CON=y
> 
> #
> # 1-wire Bus Masters
> #
> # CONFIG_W1_MASTER_DS2490 is not set
> # CONFIG_W1_MASTER_DS2482 is not set
> CONFIG_W1_MASTER_MXC=y
> # CONFIG_W1_MASTER_DS1WM is not set
> CONFIG_W1_MASTER_GPIO=y
> 
> #
> # 1-wire Slaves
> #
> CONFIG_W1_SLAVE_THERM=y
> # CONFIG_W1_SLAVE_SMEM is not set
> # CONFIG_W1_SLAVE_DS2408 is not set
> # CONFIG_W1_SLAVE_DS2413 is not set
> # CONFIG_W1_SLAVE_DS2406 is not set
> # CONFIG_W1_SLAVE_DS2423 is not set
> # CONFIG_W1_SLAVE_DS2431 is not set
> # CONFIG_W1_SLAVE_DS2433 is not set
> # CONFIG_W1_SLAVE_DS2760 is not set
> # CONFIG_W1_SLAVE_DS2780 is not set
> # CONFIG_W1_SLAVE_DS2781 is not set
> # CONFIG_W1_SLAVE_DS28E04 is not set
> # CONFIG_W1_SLAVE_BQ27000 is not set
4175a4203
> # CONFIG_DEBUG_UART_BCM63XX is not set

git diff from sources/linux-udoo-next/4.4-5.0.11.p7.3 (this is the only change for the whole tree):

diff --git a/arch/arm/boot/dts/imx6qdl-udoo.dtsi b/arch/arm/boot/dts/imx6qdl-udoo.dtsi
old mode 100644
new mode 100755
index 502e741..7ad9abe
--- a/arch/arm/boot/dts/imx6qdl-udoo.dtsi
+++ b/arch/arm/boot/dts/imx6qdl-udoo.dtsi
@@ -231,7 +231,7 @@
         	compatible = "w1-gpio";
                 pinctrl-names = "default";
                 pinctrl-0 = <&w1_gpio_pins>;
-                status = "disabled";
+                status = "okay";
                 gpios = <&gpio1 21 0>; 
 	};
 };

I run my compile.sh, and install all the generated debs:

linux-firmware-image-4.4.0-udoo_5.26_armhf.deb
linux-headers-4.4.0-udoo_5.26_armhf.deb
linux-image-4.4.0-udoo_5.26_armhf.deb
linux-libc-dev_5.26_armhf.deb
linux-u-boot-next-udoo_5.26_armhf.deb

via "dpkg -i *.deb" - so I assume that it will use your tools & install your kernel patches.

 

After the install - goes straight to trying to boot off net

Share this post


Link to post
Share on other sites

Leave this as is

FORCE_CHECKOUT="yes"            # ignore manual changes to source

and use

CREATE_PATCHES="yes"

Apply change to source when asked and pickup patch which will be created userpatches/patch ... this patch should be moved to appropriate dir:

userpatches/kernel/udoo-next

or move it to 

lib/patch/kernel/udoo-next

and create PR to our repository since it might be useful for others too.

 

Option which you used is working properly only on source where no patches are initially involved  ... we have to change / note this.

Share this post


Link to post
Share on other sites

Leave this as is

FORCE_CHECKOUT="yes"            # ignore manual changes to source

and use

CREATE_PATCHES="yes"

Apply change to source when asked and pickup patch which will be created userpatches/patch ... this patch should be moved to appropriate dir:

userpatches/kernel/udoo-next

or move it to 

lib/patch/kernel/udoo-next

and create PR to our repository since it might be useful for others too.

 

Option which you used is working properly only on source where no patches are initially involved  ... we have to change / note this.

 

perfect - that worked!

Igor likes this

Share this post


Link to post
Share on other sites

I try this procedure (without PR) but I can't succeed, I modify this file :

./sources/linux-sun8i/sun8i/drivers/media/rc/sunxi-cir.c

 

Before compiling I have this :

[ warn ] Make your changes in this directory: [ /root/crosscompile/sources/u-boot/v2017.03 ]
[ warn ] Press <Enter> after you are done [ waiting ]

 

I paste the file, but I have :

[ warn ] No changes found, skipping patch creation

 

Where I must copy paste my "sunxi-cir.c" file ?

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

0

  • Support the project

    We need your help to stay focused on the project.

    Choose the amount and currency you would like to donate in below.