On 05/20/2016 02:18 AM, Andreas Reschke wrote:
Am 19.05.2016 um 11:30 schrieb Peter Robinson:
On Thu, May 19, 2016 at 9:32 AM, <arm_ml@xxxxxxxxxxx> wrote:
Am 2016-05-18 21:24, schrieb Peter Robinson:
Hi,
I've found in fedora-minimal-armhfp-rawhide-2016-05-08.n.0.sda.raw.xz
support for U-boot for Odroid-XU4. Can I "dd" the Image to a microSD ?
Or should I use the fedora-arm-image-installer, but which target?
I'm using the XU4 with the Ubuntu?-Kernel and Fedora 23 on top as a
Home/Nas-Server with the Cloudshell.
So there's some extra steps needed for exynos processors as there's a
binary blob, which we can't redistribute, needed for boot. You can use
the Fedora u-boot and kernel. There's details of where to get the blob
needed (depends on your version) in the README below (we ship this
readme with the new 2016.05 u-boot).
So you should be able to dd out the image or "arm-image-installer
--image=XX --target=none" and then follow the instructions to write
the blob/u-boot.
Peter
[1]
http://git.denx.de/?p=u-boot.git;a=blob_plain;f=doc/README.odroid;hb=HEAD
_______________________________________________
arm mailing list
arm@xxxxxxxxxxxxxxxxxxxxxxx
http://lists.fedoraproject.org/admin/lists/arm@xxxxxxxxxxxxxxxxxxxxxxx
Hi Peter,
thank you for this information. What I've done:
[root@destnadml00 Arm]# fedora-arm-image-installer
--image=Fedora-Minimal-armhfp-Rawhide-20160518.n.0-sda.raw.xz --target=none
--media=/dev/sdc
=====================================================
= Selected Image:
= Fedora-Minimal-armhfp-Rawhide-20160518.n.0-sda.raw.xz
= Selected Media : /dev/sdc
= U-Boot Target : none
=====================================================
*****************************************************
*****************************************************
******** WARNING! ALL DATA WILL BE DESTROYED ********
*****************************************************
*****************************************************
Type 'YES' to proceed, anything else to exit now
= Proceed? YES
= Writing:
= Fedora-Minimal-armhfp-Rawhide-20160518.n.0-sda.raw.xz
= To: /dev/sdc ....
0+216811 Datensätze ein
0+216811 Datensätze aus
2146435072 Bytes (2,1 GB) kopiert, 176,355 s, 12,2 MB/s
= Writing image complete!
= No U-Boot will be installed.
= Installation Complete! Insert into the none and boot.
[root@destnadml00 Arm]# cd Odroid\ XU4/U-Boot/
[root@destnadml00 U-Boot]# ls -l
insgesamt 944
-rw-rw-r--. 1 resch resch 15616 19. Mai 08:42 bl1.bin.hardkernel
-rw-rw-r--. 1 resch resch 14592 19. Mai 08:37 bl2.bin.hardkernel.1mb_uboot
-rw-r--r--. 1 root root 47808 19. Mai 09:49 exynos5422-odroidxu4.dtb
-rw-rw-r--. 1 resch resch 54209 19. Mai 08:26 movi_partition.patch
-rwxr-xr-x. 1 resch resch 1894 19. Mai 08:38 sd_fusing.1M.sh
-rw-rw-r--. 1 resch resch 262144 19. Mai 08:38 tzsw.bin.hardkernel
-rw-r--r--. 1 root root 544935 19. Mai 09:57 u-boot.bin
-rw-r--r--. 1 root root 11399 19. Mai 09:57 u-boot.dtb
[root@destnadml00 U-Boot]# ./sd_fusing.1M.sh /dev/sdc
++ '[' -z /dev/sdc ']'
++ '[' -b /dev/sdc ']'
++ echo '/dev/sdc reader is identified.'
/dev/sdc reader is identified.
++ '[' -d /sys/block/sdcboot0 ']'
++ '[' -n '' ']'
++ signed_bl1_position=1
++ bl2_position=31
++ uboot_position=63
++ tzsw_position=2111
++ device=/dev/sdc
++ '[' -f ./u-boot-dtb.bin ']'
++ '[' -f ./u-boot.bin ']'
++ uboot=./u-boot.bin
++ echo 'BL1 fusing'
BL1 fusing
++ sudo dd iflag=dsync oflag=dsync if=./bl1.bin.hardkernel of=/dev/sdc
seek=1
30+1 Datensätze ein
30+1 Datensätze aus
15616 Bytes (16 kB) kopiert, 0,0437169 s, 357 kB/s
++ echo 'BL2 fusing'
BL2 fusing
++ sudo dd iflag=dsync oflag=dsync if=./bl2.bin.hardkernel.1mb_uboot
of=/dev/sdc seek=31
28+1 Datensätze ein
28+1 Datensätze aus
14592 Bytes (15 kB) kopiert, 0,0736991 s, 198 kB/s
++ echo 'u-boot fusing'
u-boot fusing
++ sudo dd iflag=dsync oflag=dsync if=./u-boot.bin of=/dev/sdc seek=63
1064+1 Datensätze ein
1064+1 Datensätze aus
544935 Bytes (545 kB) kopiert, 1,67099 s, 326 kB/s
++ echo 'TrustZone S/W fusing'
TrustZone S/W fusing
++ sudo dd iflag=dsync oflag=dsync if=./tzsw.bin.hardkernel of=/dev/sdc
seek=2111
512+0 Datensätze ein
512+0 Datensätze aus.
262144 Bytes (262 kB) kopiert, 0,932371 s, 281 kB/s
++ echo 'U-boot image is fused successfully.'
U-boot image is fused successfully.
++ echo 'Eject /dev/sdc and insert it again.'
Eject /dev/sdc and insert it again.
[root@destnadml00 U-Boot]#
I've insert the SD-card into the XU4, switch to SD-Boot and Power on.
The fan is running, red light is on, but no output on screen. Neither the
mini LCD from the cloudshell or the monitor at HDMI.
What's wrong?
No idea. I don't have one of these. Do you have a serial USB-TTL cable
to be able to debug? It's very likely it's outputting errors to the
serial console telling you what the issue is.
Update
Output from serial:
[root@rechner1 ~]# cu -s 115200 -l /dev/ttyUSB0
Connected.
U-Boot 2016.05 (May 16 2016 - 21:15:04 +0000) 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.
Hit any key to stop autoboot: 0
switch to partitions #0, OK
mmc1(part 0) is current device
Scanning mmc 1:1...
reading /exynos5422-odroidxu4.dtb
45419 bytes read in 9 ms (4.8 MiB/s)
switch to partitions #0, OK
mmc0 is current device
Scanning mmc 0:1...
starting USB...
USB0: USB EHCI 1.00
USB1: Register 2000140 NbrPorts 2
Starting the controller
USB XHCI 1.00
USB2: Register 2000140 NbrPorts 2
Starting the controller
USB XHCI 1.00
scanning bus 0 for devices... 1 USB Device(s) found
scanning bus 1 for devices... Device NOT ready
Request Sense returned 02 3A 00
3 USB Device(s) found
scanning bus 2 for devices... 2 USB Device(s) found
scanning usb for ethernet devices... 1 Ethernet Device(s) found
Waiting for Ethernet connection... done.
BOOTP broadcast 1
BOOTP broadcast 2
DHCP client bound to address 192.168.1.20 (5004 ms)
*** Warning: no boot file name; using 'C0A80114.img'
Using r8152#0 device
TFTP from server 192.168.1.1; our IP address is 192.168.1.20
Filename 'C0A80114.img'.
Load address: 0x43e00000
Loading: T T T T T T T T T T
Retry count exceeded; starting again
missing environment variable: pxeuuid
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/C0A80114
Using r8152#0 device
TFTP from server 192.168.1.1; our IP address is 192.168.1.20
Filename 'pxelinux.cfg/C0A80114'.
Load address: 0x51000000
Loading: T T T T T T T T T T
Retry count exceeded; starting again
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/C0A8011
Using r8152#0 device
TFTP from server 192.168.1.1; our IP address is 192.168.1.20
Filename 'pxelinux.cfg/C0A8011'.
Load address: 0x51000000
Loading: T T T T T T T T T T
Hi,
As is shown above, your board is PXE booting fron the network. Are you
intend to do so? If not, I guess you should pull out your ethernet cable
and try again.
Zamir
and so on.
It seems to me, that booting is OK but the bootloader didn't find the
Fedora Kernel. How to resolv this?
Greeting
Andreas
_______________________________________________
arm mailing list
arm@xxxxxxxxxxxxxxxxxxxxxxx
http://lists.fedoraproject.org/admin/lists/arm@xxxxxxxxxxxxxxxxxxxxxxx
--
Zamir SUN
zsun@xxxxxxxxxxxxxxxxx
zsun in #fedora-zh #openshift on freenode.net
_______________________________________________
arm mailing list
arm@xxxxxxxxxxxxxxxxxxxxxxx
http://lists.fedoraproject.org/admin/lists/arm@xxxxxxxxxxxxxxxxxxxxxxx
