1 1
wildcat_paris

[Device specific] Odroid XU4 part4 / PARTUUID

Recommended Posts

Regarding XU4 there are these things to test:

In case u-boot environment is properly loaded, booting by filesystem UUID can be activated for XU4.

Share this post


Link to post
Share on other sites

@zador.blood.stain

 

1/

ok, pulled 3 files changes. Your UUID architecture is like a charm.

 

On the 3rd testing, the SDcard was booting & system running (Jessie).

I guess eMMC will be working as well because it was working with root=LABEL=rootfs (to be confirmed yet)

 

2/ initrd was already implemented and working for XU4 next, so no changes here.

 

3/ I will be looking when possible about why u-boot 2016.09 was not compiling.

Still uboot 2016.05 can be used for both SD/eMMC (huge move from 2012.07)

 

4/ I will check if 2016.05 can boot legacy kernel

 

4/ I will be looking to add some lines of documentation

 

boot details:

 

 

U-Boot 2016.05-armbian (Oct 25 2016 - 03:01:42 +0200) for ODROID-XU3

CPU:   Exynos5422 @ 800 MHz
Model: Odroid XU3 based on EXYNOS5422
Board: Odroid XU3 based on EXYNOS5422
Type:  xu4
DRAM:  2 GiB
MMC:   EXYNOS DWMMC: 0, EXYNOS DWMMC: 1
*** Warning - bad CRC, using default environment

In:    serial
Out:   serial
Err:   serial
Net:   No ethernet found.
Autoboot in 0 seconds, press <ESC> to stop
Card did not respond to voltage select!
switch to partitions #0, OK
mmc0 is current device
Scanning mmc 0:1...
Found U-Boot script /boot/boot.scr
1134 bytes read in 27 ms (41 KiB/s)
## Executing script at 50000000
129 bytes read in 23 ms (4.9 KiB/s)
4524640 bytes read in 335 ms (12.9 MiB/s)
3162130 bytes read in 236 ms (12.8 MiB/s)
54607 bytes read in 54 ms (987.3 KiB/s)
Kernel image @ 0x40800000 [ 0x000000 - 0x450a60 ]
## Loading init Ramdisk from Legacy Image at 42000000 ...
   Image Name:   uInitrd
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    3162066 Bytes = 3 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
## Flattened Device Tree blob at 44000000
   Booting using the fdt blob at 0x44000000
   Loading Ramdisk to 4fcfc000, end 4fffffd2 ... OK
   Loading Device Tree to 4fceb000, end 4fcfb54e ... OK

Starting kernel ...

[    0.000000] Booting Linux on physical CPU 0x100
[    0.000000] Linux version 4.8.4-odroidxu4 (root@server1604) (gcc version 5.4.0 20160609 (Ubuntu/Linaro 5.4.0-6ubuntu1~16.04.1) ) #4 SMP PREEMPT Tue Oct 25 03:02:31 CEST 2016
[    0.000000] CPU: ARMv7 Processor [410fc073] revision 3 (ARMv7), cr=10c5387d
[    0.000000] CPU: div instructions available: patching division code
[    0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
[    0.000000] OF: fdt:Machine model: Hardkernel Odroid XU4
[    0.000000] Reserved memory: created DMA memory pool at 0xbe200000, size 8 MiB
[    0.000000] OF: reserved mem: initialized node region_mfc_right, compatible id shared-dma-pool
[    0.000000] Reserved memory: created DMA memory pool at 0xbd200000, size 16 MiB
[    0.000000] OF: reserved mem: initialized node region_mfc_left, compatible id shared-dma-pool
[    0.000000] cma: Reserved 64 MiB at 0xb9000000
[    0.000000] Memory policy: Data cache writealloc
[    0.000000] Samsung CPU ID: 0xe5422001
[    0.000000] Running under secure firmware.
[    0.000000] percpu: Embedded 14 pages/cpu @eeda9000 s26380 r8192 d22772 u57344
[    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 510784
[    0.000000] Kernel command line: console=tty1 console=ttySAC2,115200n8 root=UUID=71796f22-c468-4000-8690-399f030aa396 rootfstype=ext4 rootwait rw earlyprintk

 

 

Share this post


Link to post
Share on other sites

my TODO list:

 

1/

(from zador.b.s) can you please test default branch on XU4 and report here?

Last time command line didn't pass from u-boot to the kernel for some reason.

 

2/

looking why u-boot 2016.09 was not compiling.

 

3/

checking if 2016.05 can boot legacy kernel

 

4/

adding some documentation

 

5/ L-R1

https://github.com/igorpecovnik/lib/issues/511#issuecomment-256111716




			
		

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
1 1