Hi Dieter,

Could you try the latest image from:
http://download.opensuse.org/repositories/devel:/ARM:/Factory:/Contrib:/Odroid/images/


Guillaume


Le 29/01/2016 14:47, Dieter Thalmayr a écrit :
Hi there,

Guillaume Gardet helped me to get an odroid u3 running with a SUSE anything 
younger than a 12.3.
Actually, we used an image that can be found at

http://download.opensuse.org/repositories/devel:/ARM:/Factory:/Contrib:/Odroid/images/

That image is "factory".

We had many issues with the uboot bootloader, but after months and close to one 
dozen tries the bootloader boots the kernel.

But then:
----snip ----
U-Boot 2016.01 (Jan 25 2016 - 22:47:58 +0000)

CPU:   Exynos4412 @ 1 GHz
Model: Odroid based on Exynos4412
Board: Odroid based on Exynos4412
Type:  u3
DRAM:  2 GiB
LDO20@VDDQ_EMMC_1.8V: set 1800000 uV; enabling
LDO22@VDDQ_EMMC_2.8V: set 2800000 uV; enabling
LDO21@TFLASH_2.8V: set 2800000 uV; enabling
MMC:   SAMSUNG SDHCI: 0, EXYNOS DWMMC: 1
*** Warning - bad CRC, using default environment

Net:   No ethernet found.
Hit any key to stop autoboot:  0
2721 bytes read in 135 ms (19.5 KiB/s)
## Executing script at 42000000
autoboot=if test -e mmc 0 boot.scr; then; run boot_script; elif test -e mmc 0 I;
baudrate=115200
boardname=odroidu3
boot_fit=setenv kerneladdr 0x42000000;setenv kernelname Image.itb;run loadkerne}
boot_script=run loadbootscript;source ${scriptaddr}
boot_uimg=setenv kerneladdr 0x40007FC0;setenv kernelname uImage;run check_dtb;r;
boot_zimg=setenv kerneladdr 0x40007FC0;setenv kernelname zImage;run check_dtb;r;
bootargs=Please use defined boot
bootcmd=run autoboot
bootdelay=0
check_dtb=if run loaddtb; then setenv fdt_addr ${fdtaddr};else setenv fdt_addr;;
check_ramdisk=if run loadinitrd; then setenv initrd_addr ${initrdaddr};else set;
console=console=ttySAC1,115200n8
consoleoff=set console console=ram; save; reset
consoleon=set console console=ttySAC1,115200n8; save; reset
dfu_alt_info=Please reset the board
dfu_alt_system=uImage fat 0 1;zImage fat 0 1;Image.itb fat 0 1;uInitrd fat 0 1;2
fdtaddr=40800000
fdtcontroladdr=bae47f70
fdtfile=exynos4412-odroidu3.dtb
fileaddr=42000000
filesize=aa1
initrdaddr=42000000
initrdname=uInitrd
kernel_args=setenv bootargs root=/dev/mmcblk${mmcrootdev}p${mmcrootpart} rootwa}
loadbootscript=load mmc ${mmcbootdev}:${mmcbootpart} ${scriptaddr} boot.scr
loaddtb=load mmc ${mmcbootdev}:${mmcbootpart} ${fdtaddr} ${fdtfile}
loadinitrd=load mmc ${mmcbootdev}:${mmcbootpart} ${initrdaddr} ${initrdname}
loadkernel=load mmc ${mmcbootdev}:${mmcbootpart} ${kerneladdr} ${kernelname}
mmcbootdev=0
mmcbootpart=1
mmcrootdev=0
mmcrootpart=2
scriptaddr=0x42000000
soc_id=4412
soc_rev=2.0

Environment size: 2090/4092 bytes
switch to partitions #0, OK
mmc0 is current device
7420680 bytes read in 4206 ms (1.7 MiB/s)
68337422 bytes read in 31408 ms (2.1 MiB/s)
53476 bytes read in 464 ms (112.3 KiB/s)
Kernel image @ 0x40007fc0 [ 0x000000 - 0x713b08 ]
## Loading init Ramdisk from Legacy Image at 44007fc0 ...
Image Name:   Initrd
Image Type:   ARM Linux RAMDisk Image (uncompressed)
Data Size:    68337358 Bytes = 65.2 MiB
Load Address: 00000000
Entry Point:  00000000
Verifying Checksum ... OK
## Flattened Device Tree blob at 43f07fc0
Booting using the fdt blob at 0x43f07fc0
Using Device Tree in place at 43f07fc0, end 43f180a3

Starting kernel ...

--- snap ---

and afterwards only the sad sound of the ventilator.

Does anybody have an idea what goes wrong?
What can I do to get more information

Plus, I would be very interested in building an image on my own.
Is there somewhere a howto that can help me with the first steps?

Although I have to admit that I am only a high-hearted amateur if it comes down 
to real technics..

Greetings

Dieter


--
To unsubscribe, e-mail: [email protected]
To contact the owner, e-mail: [email protected]

Reply via email to