Recently I purcase a Udoo develeopment board. From the arciteture perspective it looks similar to the Development board.
I would like to build and use latest kernel for this board. From the forum of Udoo supports 3.10.17 kernel, I am able to build the kernel but it I try to load the kernel it stucks at the boot loader showing message.
Blockquote: kernel starting ….
So my guess is that the it’s bootloader problem. I would like to compile and update my bootloader but I dont know how to do. Could you share some inputs on to this.
Could you share some of the underline change that happen in u-boot loader with respect to the current kernels.
Thanks for your quick replay. Yes i have posted this on the udoo forum but i did not get any replay. Please find the link below to refer.
Orignal kernel supported is 3.0.35 which come with the ubuntu image. I am able to build the old kernel and put it on the board.
Now I would like to build and put new kernel 3.10.17 image as its say’s it supported for the board.
I google a bit and got the following links to compile your own bootloader.
I wonder how it’s working for them and not working for me.
Below is the udoo logs I see on the console.
U-Boot 2013.10-rc3 (Jan 20 2014 – 13:33:34)
CPU: Freescale i.MX6Q rev1.2 at 792 MHz
Reset cause: WDOG
DRAM: 1 GiB
MMC: FSL_SDHC: 0
*** Warning – bad CRC, using default environment
No panel detected: default to LDB-WVGA
Display: LDB-WVGA (800×480)
Net: using phy at 6
Warning: failed to set MAC address
Hit any key to stop autoboot: 0
mmc0 is current device
** File not found boot.scr **
5077712 bytes read in 418 ms (11.6 MiB/s)
Booting from mmc …
** File not found imx6q-udoo.dtb **
Booting kernel from Legacy Image at 12000000 …
Image Name: Linux-3.10.17-80552-gd6e35d0
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 5077648 Bytes = 4.8 MiB
Load Address: 10800000
Entry Point: 10800000
Verifying Checksum … OK
Loading Kernel Image … OK
Starting kernel …
> Blockquote : Can I build the latest stable kernel for this board.
Please share your thought on this.
start with something what works – e.g. with configuration, where your bootloader + Linux fully boots up. If everything is working oki then compile a new kernel and try it. It should work. If it doesnt, there is probably something wrong with the kernel. Occasionally, the command line arguments (use “printenv” to list them) passed from bootloader to Linux may be wrong.
Did you try to ask at Udoo forum?
- Guest answered 1264 days ago
Please login first to submit.