udoo-dual u-boot

[MaSchuessler]

Dear Igor,

 

Thank you very mutch for tis great job!

 

I did some tests based on your image with udoo-quad, works perfect!

 

But I do have some trouble on udoo-dual, kernel stops without any console output (just loading kernel...)

 

so I decided to compile my own, but I get

 

 

[ o.k. ] Compiling uboot
[ o.k. ] Compiler version [ arm-linux-gnueabihf-gcc 5.4.0 ]
make: *** Keine Regel, um „udoo_qdl_config“ zu erstellen.  Schluss.
 

 

What do I have to change?

 

 

Best regards

 

Marcus

[Igor]

Theirs sources and a path was changed so I need to adjust patches ... working on it.

 

Thanks! 

 

Edit: It builds now but need to see if it boots too since there were some other changes in uboot.

[Igor]

Unfortunately it does not boot - it keeps resetting when kernel is loaded. I have to dig in more or set u-boot sources back in the past.

[Igor]

Fixed with this commit.

https://github.com/igorpecovnik/lib/commit/86797e04dac7a4132cae7280220034db5b91e4f2

[MaSchuessler]

Deag Igor, 

 

thanks a lot. I will test today and give response.

[MaSchuessler]

Dear Igor,

 

I am sorry to disturbe again, now I am able to compile and create image (next-console), but the kernel still wont start on udoo-d and even not on udoo-quad

 

Marcus

[Igor]

Huh. It was booting on mine ... will check again, perhaps I forgot to push something.
 

One thing which could be the problem - since sources were changed, you need to delete:

sources/u-boot-udoo 

before restart the compilation. This will download new / working u-boot source. I am almost sure this is the problem.

[MaSchuessler]

Hi Igor,

 

I just set up my virtual machine completely new.

 

I am getting following (unchanged) result:

 

 

U-Boot SPL 2015.10-armbian (Sep 05 2016 - 18:35:42)

 

 

U-Boot 2015.10-armbian (Sep 05 2016 - 18:35:42 +0200)

 

CPU:   Freescale i.MX6DL rev1.1 at 792 MHz

Reset cause: POR

Board: UDOO DualLite

DRAM:  1 GiB

MMC:   FSL_SDHC: 0

*** Warning - bad CRC, using default environment

 

No panel detected: default to HDMI

Display: HDMI (1280x720)

In:    serial

Out:   serial

Err:   serial

Net:   Phy 4 not found

using phy at 4

PHY reset timed out

FEC [PRIME]

Error: FEC address not set.

 

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

824 bytes read in 88 ms (8.8 KiB/s)

Running bootscript from mmc ...

## Executing script at 12000000

0 bytes read in 59 ms (0 Bytes/s)

0 bytes read in 64 ms (0 Bytes/s)

37690 bytes read in 379 ms (96.7 KiB/s)

6137616 bytes read in 419 ms (14 MiB/s)

Kernel image @ 0x12000000 [ 0x000000 - 0x5da710 ]

## Flattened Device Tree blob at 18000000

   Booting using the fdt blob at 0x18000000

   Using Device Tree in place at 18000000, end 1800c339

 

Starting kernel ...

[Igor]

Not much output to console from kernel could be normal - change console to serial and enlarge verbosity level or just wait little longer that serial console kick in and / or connect remotely. Initial problem was broken u-boot, the rest is more or less unchanged.

[MaSchuessler]

Ok I did som testing,

 

it works fine on udoo quad, udoo dual lite does not start

 

do I have to modify the device tree? 

[Igor]

For double you most likely need to select other / proper device tree in boot script. I never search to make support for other versions beside Quad.

[MaSchuessler]

Yes! that works!!!!!!

 

Thank you very much! I just changed dtb files in boot.cmd and compiled it!