ODROID-XU4

Moderators: meveric, mdrjr, odroid

ODROID-XU4

Unread postby odroid » Tue Jul 14, 2015 4:06 pm

The XU4 is fully software compatible with XU3!
However, the XU4 is more compact, more affordable and more expandable.



More about ODROID-XU4


Image

ODROID-XU4 is a new generation of computing device with more powerful, more energy-efficient hardware and a smaller form factor.
Offering open source support, the board can run various flavors of Linux, including the latest Ubuntu 15.04 and Android 4.4 KitKat and 5.1 Lollipop.
By implementing the eMMC 5.0, USB 3.0 and Gigabit Ethernet interfaces, the ODROID-XU4 boasts amazing data transfer speeds,
a feature that is increasingly required to support advanced processing power on ARM devices.
This allows users to truly experience an upgrade in computing, especially with faster booting, web browsing, networking, and 3D games.

CPU/RAM PERFORMANCE
We ran several benchmarks to measure the computing power on the XU4. The same tests were performed on the Raspberry Pi 2 Model B, ODROID-C1, ODROID-U3 and ODROID-XU4.
The values of the test results were scaled uniformly for comparison purposes. The computing power of the XU4 was measured to be ~3-4 times faster than the latest Raspberry Pi 2 thanks to the 2Ghz Cortex-A15 cores and much higher memory bandwidth. Using the XU4 as a computer provides a "desktop like" experience, unlike the sluggish performance of most single-board computers!
Particularly for developers, compiling code on the XU4 is about 3 to 4 times faster. The high-performance 2GB DDR3 RAM is an additional advantage allowing most programs to be compiled directly on the XU4.
Image


SD/eMMC PERFORMANCE
The XU4 can boot from a MicroSD card or an eMMC module. An easy-access hardware switch is provided to select the boot interface (MicroSD/eMMC). The MicroSD interface supports the higher performance UHS-1 mode as well.
File access of a 512MB file (read/write) on three different storage options shows distinct performance differences.
The eMMC 5.0 storage is ~7x faster than the MicroSD Class-10 card in read tests. The MicroSD UHS-1 card is ~2x faster than the MicroSD Class-10 card in read tests. The MicroSD UHS-1 card provides a great low-cost option for many applications!
Image


USB 3.0 PERFORMANCE
The XU4 has two standard-sized USB 3.0 SuperSpeed host ports.
To measure the USB 3.0 performance, we connected an SSD via a USB-SATA bridge. We used the Toshiba SSD HDT312 128GB model for this test.
USB 3.0 read access speed is ~5x faster than USB 2.0 on the XU4!
Image


ETHERNET PERFORMANCE
The XU4 has an on-board Gigabit Ethernet controller. Our bi-directional streaming speed was measured at ~880Mbps.
Thanks to the advanced technology of the RTL8135 controller, the XU4's Ethernet controller easily outperforms the connectivity solutions of prior generations.
Image


NETWORK STORAGE PERFORMANCE
These days, network storage applications like NAS and cloud services are popular. We ran the famous OMV (Open Media Vault) OS on the XU4 to measure network storage performance.
An SSD was connected to the XU4 via a USB 3.0 to SATA bridge. The Gigabit Ethernet port was connected to a Windows 8 PC via a simple switching hub.

We sent a big 1.6GB file from the XU4 to the PC via a Samba connection. This resulted in a download speed of ~75-85MB/sec.
The upload speed was measured at ~70MB/sec. Even though this performance is great, we are working on optimizing it even further.

The XU4 is a great solution to make a DIY personal cloud storage server!
Image
Image


Mainline Kernel boots (Experimental)
The latest Kernel 4.2.0 RC1 runs on the XU4. Look at this booting log. You can scroll the log.
Code: Select all
[    0.000000] Booting Linux on physical CPU 0x100
[    0.000000] Linux version 4.2.0-rc1+ (tobetter@hkxeon) (gcc version 4.9.2 20140904 (prerelease) (crosstool-NG linaro-1.13.1-4.9-2014.09 - Linaro GCC 4.9-2014.09) ) #4 SMP PREEMPT Fri Jul 10 16:45:24 KST 2015
[    0.000000] CPU: ARMv7 Processor [410fc073] revision 3 (ARMv7), cr=10c5387d
[    0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
[    0.000000] Machine model: Hardkernel Odroid XU4
[    0.000000] cma: Reserved 64 MiB at 0xba800000
[    0.000000] Memory policy: Data cache writealloc
[    0.000000] Samsung CPU ID: 0xe5422001
[    0.000000] On node 0 totalpages: 514560
[    0.000000] free_area_init_node: node 0, pgdat c07f12c0, node_mem_map ee81f000
[    0.000000]   Normal zone: 1520 pages used for memmap
[    0.000000]   Normal zone: 0 pages reserved
[    0.000000]   Normal zone: 190464 pages, LIFO batch:31
[    0.000000]   HighMem zone: 324096 pages, LIFO batch:31
[    0.000000] Running under secure firmware.
[    0.000000] PERCPU: Embedded 11 pages/cpu @ee78f000 s14336 r8192 d22528 u45056
[    0.000000] pcpu-alloc: s14336 r8192 d22528 u45056 alloc=11*4096
[    0.000000] pcpu-alloc: [0] 0 [0] 1 [0] 2 [0] 3 [0] 4 [0] 5 [0] 6 [0] 7
[    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 513040
[    0.000000] Kernel command line: console=tty1 console=ttySAC2,115200n8 root=UUID=a4b494db-320a-4ce2-bb3a-841db943f9c0 rootwait ro smsc95xx.macaddr=00:1e:06:61:7a:39
[    0.000000] PID hash table entries: 4096 (order: 2, 16384 bytes)
[    0.000000] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
[    0.000000] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
[    0.000000] Memory: 1962856K/2058240K available (5506K kernel code, 200K rwdata, 1992K rodata, 404K init, 295K bss, 29848K reserved, 65536K cma-reserved, 1230848K highmem)
[    0.000000] Virtual kernel memory layout:
[    0.000000]     vector  : 0xffff0000 - 0xffff1000   (   4 kB)
[    0.000000]     fixmap  : 0xffc00000 - 0xfff00000   (3072 kB)
[    0.000000]     vmalloc : 0xf0000000 - 0xff000000   ( 240 MB)
[    0.000000]     lowmem  : 0xc0000000 - 0xef800000   ( 760 MB)
[    0.000000]     pkmap   : 0xbfe00000 - 0xc0000000   (   2 MB)
[    0.000000]     modules : 0xbf000000 - 0xbfe00000   (  14 MB)
[    0.000000]       .text : 0xc0008000 - 0xc075ad74   (7500 kB)
[    0.000000]       .init : 0xc075b000 - 0xc07c0000   ( 404 kB)
[    0.000000]       .data : 0xc07c0000 - 0xc07f2220   ( 201 kB)
[    0.000000]        .bss : 0xc07f5000 - 0xc083ec6c   ( 296 kB)
[    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=8, Nodes=1
[    0.000000] Preemptible hierarchical RCU implementation.
[    0.000000]    Additional per-CPU info printed with stalls.
[    0.000000]    Build-time adjustment of leaf fanout to 32.
[    0.000000] NR_IRQS:16 nr_irqs:16 16
[    0.000000] L2C: failed to init: -19
[    0.000000] Switching to timer-based delay loop, resolution 41ns
[    0.000000] clocksource: mct-frc: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 79635851949 ns
[    0.000007] sched_clock: 32 bits at 24MHz, resolution 41ns, wraps every 89478484971ns
[    0.000696] Console: colour dummy device 80x30
[    0.001447] console [tty1] enabled
[    0.001491] Calibrating delay loop (skipped), value calculated using timer frequency.. 48.00 BogoMIPS (lpj=120000)
[    0.001549] pid_max: default: 32768 minimum: 301
[    0.001729] Mount-cache hash table entries: 2048 (order: 1, 8192 bytes)
[    0.001767] Mountpoint-cache hash table entries: 2048 (order: 1, 8192 bytes)
[    0.002658] CPU: Testing write buffer coherency: ok
[    0.003184] CPU0: update cpu_capacity 448
[    0.003222] CPU0: thread -1, cpu 0, socket 1, mpidr 80000100
[    0.003491] Setting up static identity map for 0x40008280 - 0x400082d8
[    0.003865] ARM CCI driver probed
[    0.004152] Exynos MCPM support installed
[    0.020519] CPU1: update cpu_capacity 1535
[    0.020527] CPU1: thread -1, cpu 0, socket 0, mpidr 80000000
[    0.025503] CPU2: update cpu_capacity 1535
[    0.025510] CPU2: thread -1, cpu 1, socket 0, mpidr 80000001
[    0.030522] CPU3: update cpu_capacity 1535
[    0.030529] CPU3: thread -1, cpu 2, socket 0, mpidr 80000002
[    0.035509] CPU4: update cpu_capacity 1535
[    0.035517] CPU4: thread -1, cpu 3, socket 0, mpidr 80000003
[    0.040602] CPU5: update cpu_capacity 448
[    0.040610] CPU5: thread -1, cpu 1, socket 1, mpidr 80000101
[    0.045599] CPU6: update cpu_capacity 448
[    0.045607] CPU6: thread -1, cpu 2, socket 1, mpidr 80000102
[    0.050588] CPU7: update cpu_capacity 448
[    0.050596] CPU7: thread -1, cpu 3, socket 1, mpidr 80000103
[    0.050702] Brought up 8 CPUs
[    0.051039] SMP: Total of 8 processors activated (384.00 BogoMIPS).
[    0.051072] CPU: WARNING: CPU(s) started in wrong/inconsistent modes (primary CPU mode 0x1a)
[    0.051115] CPU: This may indicate a broken bootloader or firmware.
[    0.052135] devtmpfs: initialized
[    0.080775] VFP support v0.3: implementor 41 architecture 2 part 30 variant 7 rev 3
[    0.082343] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 9556302231375000 ns
[    0.086012] pinctrl core: initialized pinctrl subsystem
[    0.086799] regulator-dummy: no parameters
[    0.087610] NET: Registered protocol family 16
[    0.089703] DMA: preallocated 256 KiB pool for atomic coherent allocations
[    0.104988] cpuidle: using governor ladder
[    0.124978] cpuidle: using governor menu
[    0.129700] gpiochip_add: registered GPIOs 0 to 7 on device: gpy7
[    0.129898] gpiochip_add: registered GPIOs 8 to 15 on device: gpx0
[    0.130131] gpiochip_add: registered GPIOs 16 to 23 on device: gpx1
[    0.130335] gpiochip_add: registered GPIOs 24 to 31 on device: gpx2
[    0.130529] gpiochip_add: registered GPIOs 32 to 39 on device: gpx3
[    0.132024] gpiochip_add: registered GPIOs 40 to 47 on device: gpc0
[    0.132237] gpiochip_add: registered GPIOs 48 to 55 on device: gpc1
[    0.132430] gpiochip_add: registered GPIOs 56 to 62 on device: gpc2
[    0.132628] gpiochip_add: registered GPIOs 63 to 66 on device: gpc3
[    0.132842] gpiochip_add: registered GPIOs 67 to 68 on device: gpc4
[    0.133049] gpiochip_add: registered GPIOs 69 to 76 on device: gpd1
[    0.133243] gpiochip_add: registered GPIOs 77 to 82 on device: gpy0
[    0.133436] gpiochip_add: registered GPIOs 83 to 86 on device: gpy1
[    0.133643] gpiochip_add: registered GPIOs 87 to 92 on device: gpy2
[    0.133839] gpiochip_add: registered GPIOs 93 to 100 on device: gpy3
[    0.134034] gpiochip_add: registered GPIOs 101 to 108 on device: gpy4
[    0.134232] gpiochip_add: registered GPIOs 109 to 116 on device: gpy5
[    0.134439] gpiochip_add: registered GPIOs 117 to 124 on device: gpy6
[    0.135672] gpiochip_add: registered GPIOs 125 to 132 on device: gpe0
[    0.135867] gpiochip_add: registered GPIOs 133 to 134 on device: gpe1
[    0.136055] gpiochip_add: registered GPIOs 135 to 140 on device: gpf0
[    0.136239] gpiochip_add: registered GPIOs 141 to 148 on device: gpf1
[    0.136426] gpiochip_add: registered GPIOs 149 to 156 on device: gpg0
[    0.136615] gpiochip_add: registered GPIOs 157 to 164 on device: gpg1
[    0.136799] gpiochip_add: registered GPIOs 165 to 166 on device: gpg2
[    0.136986] gpiochip_add: registered GPIOs 167 to 170 on device: gpj4
[    0.138109] gpiochip_add: registered GPIOs 171 to 178 on device: gpa0
[    0.138297] gpiochip_add: registered GPIOs 179 to 184 on device: gpa1
[    0.138485] gpiochip_add: registered GPIOs 185 to 192 on device: gpa2
[    0.138679] gpiochip_add: registered GPIOs 193 to 197 on device: gpb0
[    0.138865] gpiochip_add: registered GPIOs 198 to 202 on device: gpb1
[    0.139049] gpiochip_add: registered GPIOs 203 to 206 on device: gpb2
[    0.139232] gpiochip_add: registered GPIOs 207 to 214 on device: gpb3
[    0.139427] gpiochip_add: registered GPIOs 215 to 216 on device: gpb4
[    0.139615] gpiochip_add: registered GPIOs 217 to 224 on device: gph0
[    0.140878] gpiochip_add: registered GPIOs 225 to 231 on device: gpz
[    0.143298] exynos-audss-clk 3810000.audss-clock-controller:: setup completed
[    0.152608] EXYNOS5420 PMU initialized
[    0.194093] SCSI subsystem initialized
[    0.194706] usbcore: registered new interface driver usbfs
[    0.194861] usbcore: registered new interface driver hub
[    0.195150] usbcore: registered new device driver usb
[    0.196236] s3c-i2c 12c80000.i2c:: slave address 0x00
[    0.196282] s3c-i2c 12c80000.i2c:: bus frequency set to 65 KHz
[    0.196935] s3c-i2c 12c80000.i2c:: i2c-2: S3C I2C adapter
[    0.200745] clocksource: Switched to clocksource mct-frc
[    0.201244] FS-Cache: Loaded
[    0.224210] NET: Registered protocol family 2
[    0.225113] TCP established hash table entries: 8192 (order: 3, 32768 bytes)
[    0.225279] TCP bind hash table entries: 8192 (order: 5, 163840 bytes)
[    0.225691] TCP: Hash tables configured (established 8192 bind 8192)
[    0.225940] UDP hash table entries: 512 (order: 2, 24576 bytes)
[    0.226043] UDP-Lite hash table entries: 512 (order: 2, 24576 bytes)
[    0.226446] NET: Registered protocol family 1
[    0.226966] RPC: Registered named UNIX socket transport module.
[    0.227007] RPC: Registered udp transport module.
[    0.227036] RPC: Registered tcp transport module.
[    0.227065] RPC: Registered tcp NFSv4.1 backchannel transport module.
[    0.227430] Trying to unpack rootfs image as initramfs...
[    0.537926] Freeing initrd memory: 3876K (c2000000 - c23c9000)
[    0.540696] futex hash table entries: 2048 (order: 5, 131072 bytes)
[    0.564313] ntfs: driver 2.1.32 [Flags: R/W].
[    0.565053] romfs: ROMFS MTD (C) 2007 Red Hat, Inc.
[    0.565411] fuse init (API version 7.23)
[    0.567241] bounce: pool size: 64 pages
[    0.567280] io scheduler noop registered
[    0.567310] io scheduler deadline registered
[    0.567690] io scheduler cfq registered (default)
[    0.568071] phy phy-video-phy@10040728:.0: Looking up phy-supply from device tree
[    0.568087] phy phy-video-phy@10040728:.0: Looking up phy-supply property in node /video-phy@10040728 failed
[    0.568695] phy phy-video-phy@10040714:.1: Looking up phy-supply from device tree
[    0.568711] phy phy-video-phy@10040714:.1: Looking up phy-supply property in node /video-phy@10040714 failed
[    0.568890] phy phy-video-phy@10040714:.2: Looking up phy-supply from device tree
[    0.568904] phy phy-video-phy@10040714:.2: Looking up phy-supply property in node /video-phy@10040714 failed
[    0.569067] phy phy-video-phy@10040714:.3: Looking up phy-supply from device tree
[    0.569081] phy phy-video-phy@10040714:.3: Looking up phy-supply property in node /video-phy@10040714 failed
[    0.569245] phy phy-video-phy@10040714:.4: Looking up phy-supply from device tree
[    0.569259] phy phy-video-phy@10040714:.4: Looking up phy-supply property in node /video-phy@10040714 failed
[    0.570242] phy phy-12130000.phy:.5: Looking up phy-supply from device tree
[    0.570258] phy phy-12130000.phy:.5: Looking up phy-supply property in node /phy@12130000 failed
[    0.570435] phy phy-12130000.phy:.6: Looking up phy-supply from device tree
[    0.570450] phy phy-12130000.phy:.6: Looking up phy-supply property in node /phy@12130000 failed
[    0.570613] phy phy-12130000.phy:.7: Looking up phy-supply from device tree
[    0.570627] phy phy-12130000.phy:.7: Looking up phy-supply property in node /phy@12130000 failed
[    0.570856] phy phy-12130000.phy:.8: Looking up phy-supply from device tree
[    0.570874] phy phy-12130000.phy:.8: Looking up phy-supply property in node /phy@12130000 failed
[    0.571623] exynos5_usb3drd_phy 12100000.phy:: Looking up vbus-supply from device tree
[    0.571639] exynos5_usb3drd_phy 12100000.phy:: Looking up vbus-supply property in node /phy@12100000 failed
[    0.571651] 12100000.phy: supply vbus not found, using dummy regulator
[    0.571762] exynos5_usb3drd_phy 12100000.phy:: Looking up vbus-boost-supply from device tree
[    0.571777] exynos5_usb3drd_phy 12100000.phy:: Looking up vbus-boost-supply property in node /phy@12100000 failed
[    0.571787] 12100000.phy: supply vbus-boost not found, using dummy regulator
[    0.571888] phy phy-12100000.phy:.9: Looking up phy-supply from device tree
[    0.571902] phy phy-12100000.phy:.9: Looking up phy-supply property in node /phy@12100000 failed
[    0.572089] phy phy-12100000.phy:.10: Looking up phy-supply from device tree
[    0.572104] phy phy-12100000.phy:.10: Looking up phy-supply property in node /phy@12100000 failed
[    0.572402] exynos5_usb3drd_phy 12500000.phy:: Looking up vbus-supply from device tree
[    0.572417] exynos5_usb3drd_phy 12500000.phy:: Looking up vbus-supply property in node /phy@12500000 failed
[    0.572428] 12500000.phy: supply vbus not found, using dummy regulator
[    0.572521] exynos5_usb3drd_phy 12500000.phy:: Looking up vbus-boost-supply from device tree
[    0.572536] exynos5_usb3drd_phy 12500000.phy:: Looking up vbus-boost-supply property in node /phy@12500000 failed
[    0.572546] 12500000.phy: supply vbus-boost not found, using dummy regulator
[    0.572645] phy phy-12500000.phy:.11: Looking up phy-supply from device tree
[    0.572660] phy phy-12500000.phy:.11: Looking up phy-supply property in node /phy@12500000 failed
[    0.572850] phy phy-12500000.phy:.12: Looking up phy-supply from device tree
[    0.572864] phy phy-12500000.phy:.12: Looking up phy-supply property in node /phy@12500000 failed
[    0.578092] dma-pl330 3880000.adma: Loaded driver for PL330 DMAC-241330
[    0.578128] dma-pl330 3880000.adma:    DBUFF-4x8bytes Num_Chans-6 Num_Peri-16 Num_Events-6
[    0.583870] dma-pl330 121a0000.pdma: Loaded driver for PL330 DMAC-241330
[    0.583905] dma-pl330 121a0000.pdma:    DBUFF-32x4bytes Num_Chans-8 Num_Peri-32 Num_Events-32
[    0.589678] dma-pl330 121b0000.pdma: Loaded driver for PL330 DMAC-241330
[    0.589714] dma-pl330 121b0000.pdma:    DBUFF-32x4bytes Num_Chans-8 Num_Peri-32 Num_Events-32
[    0.591378] dma-pl330 10800000.mdma: Loaded driver for PL330 DMAC-241330
[    0.591413] dma-pl330 10800000.mdma:    DBUFF-64x8bytes Num_Chans-8 Num_Peri-1 Num_Events-32
[    0.702141] Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
[    0.704902] 12c00000.serial:: ttySAC0 at MMIO 0x12c00000 (irq = 58, base_baud = 0) is a S3C6400/10
[    0.705626] 12c10000.serial:: ttySAC1 at MMIO 0x12c10000 (irq = 59, base_baud = 0) is a S3C6400/10
[    0.706383] 12c20000.serial:: ttySAC2 at MMIO 0x12c20000 (irq = 60, base_baud = 0) is a S3C6400/10
[    1.434038] console [ttySAC2] enabled
[    1.438403] 12c30000.serial:: ttySAC3 at MMIO 0x12c30000 (irq = 61, base_baud = 0) is a S3C6400/10
[    1.448653] [drm] Initialized drm 1.1.0 20060810
[    1.455635] of_get_named_gpiod_flags: parsed 'hpd-gpio' property of node '/hdmi@14530000[0]' - status (0)
[    1.455829] exynos-hdmi 14530000.hdmi:: Looking up vdd-supply from device tree
[    1.455856] exynos-hdmi 14530000.hdmi:: Failed to get supply 'vdd': -517
[    1.461132] [drm:hdmi_probe] *ERROR* failed to get regulators
[    1.466837] [drm:hdmi_probe] *ERROR* hdmi_resources_init failed
[    1.491261] brd: module loaded
[    1.503212] loop: module loaded
[    1.507360] exynos-dwc3 usb@12000000:: Looking up vdd33-supply from device tree
[    1.507937] exynos-dwc3 usb@12400000:: Looking up vdd33-supply from device tree
[    1.508503] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[    1.513604] ehci-exynos: EHCI EXYNOS driver
[    1.517993] of_get_named_gpiod_flags: can't parse 'samsung,vbus-gpio' property of node '/usb@12110000[0]'
[    1.518260] exynos-ehci 12110000.usb:: EHCI Host Controller
[    1.523378] exynos-ehci 12110000.usb:: new USB bus registered, assigned bus number 1
[    1.531258] exynos-ehci 12110000.usb:: irq 115, io mem 0x12110000
[    1.545805] exynos-ehci 12110000.usb:: USB 2.0 started, EHCI 1.00
[    1.550662] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[    1.557221] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    1.564423] usb usb1: Product: EHCI Host Controller
[    1.569260] usb usb1: Manufacturer: Linux 4.2.0-rc1+ ehci_hcd
[    1.574985] usb usb1: SerialNumber: 12110000.usb:
[    1.580689] hub 1-0:1.0: USB hub found
[    1.583428] hub 1-0:1.0: 3 ports detected
[    1.588474] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
[    1.593555] ohci-exynos: OHCI EXYNOS driver
[    1.598048] exynos-ohci 12120000.usb:: USB Host Controller
[    1.603185] exynos-ohci 12120000.usb:: new USB bus registered, assigned bus number 2
[    1.611003] exynos-ohci 12120000.usb:: irq 115, io mem 0x12120000
[    1.675022] usb usb2: New USB device found, idVendor=1d6b, idProduct=0001
[    1.680378] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    1.688108] usb usb2: Product: USB Host Controller
[    1.692332] usb usb2: Manufacturer: Linux 4.2.0-rc1+ ohci_hcd
[    1.698049] usb usb2: SerialNumber: 12120000.usb:
[    1.703692] hub 2-0:1.0: USB hub found
[    1.706495] hub 2-0:1.0: 3 ports detected
[    1.712062] mousedev: PS/2 mouse device common for all mice
[    1.717695] s3c-rtc 101e0000.rtc:: failed to find rtc source clock
[    1.723006] i2c /dev entries driver
[    1.731283] vdd_ldo1: 1000 mV
[    1.732496] LDO2: at 1800 mV
[    1.734168] vdd_ldo3: 1800 mV
[    1.735379] LDO4: at 1800 mV
[    1.737158] vdd_ldo5: 1800 mV
[    1.738937] vdd_ldo6: 1000 mV
[    1.740711] vdd_ldo7: 1800 mV
[    1.742531] vdd_ldo8: 1800 mV
[    1.744305] vdd_ldo9: 3000 mV
[    1.746082] vdd_ldo10: 1800 mV
[    1.747865] vdd_ldo11: 1000 mV
[    1.749637] vdd_ldo12: 1800 mV
[    1.753198] vdd_ldo13: ramp_delay not set
[    1.756267] vdd_ldo13: 2800 mV
[    1.757544] LDO14: at 3000 mV
[    1.759317] vdd_ldo15: 3100 mV
[    1.761113] vdd_ldo16: 2200 mV
[    1.762892] tsp_avdd: 3300 mV
[    1.764169] LDO18: at 1800 mV
[    1.767727] vdd_sd: ramp_delay not set
[    1.770503] vdd_sd: 2800 mV
[    1.771774] LDO20: at 1800 mV
[    1.773064] LDO21: at 1800 mV
[    1.774329] LDO22: at 1200 mV
[    1.775615] LDO23: at 1100 mV
[    1.777431] tsp_io: 2800 mV
[    1.778705] LDO25: at 1800 mV
[    1.780498] vdd_ldo26: 3000 mV
[    1.781770] LDO27: at 1000 mV
[    1.783052] LDO28: at 3300 mV
[    1.784327] LDO29: at 1800 mV
[    1.785607] LDO30: at 1800 mV
[    1.786920] LDO31: at 1800 mV
[    1.788197] LDO32: at 1800 mV
[    1.789476] LDO33: at 1800 mV
[    1.790770] LDO34: at 3000 mV
[    1.792051] LDO35: at 1600 mV
[    1.793336] LDO36: at 1800 mV
[    1.794602] LDO37: at 1800 mV
[    1.795873] LDO38: at 2800 mV
[    1.797651] vdd_mif: 800 <--> 1300 mV at 1100 mV
[    1.799434] vdd_arm: 800 <--> 1500 mV at 1000 mV
[    1.801258] vdd_int: 800 <--> 1400 mV at 1000 mV
[    1.803039] vdd_g3d: 800 <--> 1400 mV at 1000 mV
[    1.804814] vdd_mem: 800 <--> 1400 mV at 1200 mV
[    1.806539] vdd_kfc: 800 <--> 1500 mV at 1025 mV
[    1.808215] vdd_1.0v_ldo: 800 <--> 1500 mV at 900 mV
[    1.809902] vdd_1.8v_ldo: 800 <--> 1500 mV at 1225 mV
[    1.811729] vdd_2.8v_ldo: 3000 <--> 3750 mV at 5000 mV
[    1.813507] vdd_vmem: 2850 mV
[    1.820105] s5m-rtc s2mps14-rtc: rtc core: registered s5m-rtc as rtc0
[    1.830198] thermal thermal_zone0: failed to read out thermal zone (-22)
[    1.835485] exynos-tmu 10060000.tmu:: Looking up vtmu-supply from device tree
[    1.836376] thermal thermal_zone1: failed to read out thermal zone (-22)
[    1.842155] exynos-tmu 10064000.tmu:: Looking up vtmu-supply from device tree
[    1.843035] thermal thermal_zone2: failed to read out thermal zone (-22)
[    1.848827] exynos-tmu 10068000.tmu:: Looking up vtmu-supply from device tree
[    1.849747] thermal thermal_zone3: failed to read out thermal zone (-22)
[    1.855507] exynos-tmu 1006c000.tmu:: Looking up vtmu-supply from device tree
[    1.856433] thermal thermal_zone4: failed to read out thermal zone (-22)
[    1.862172] exynos-tmu 100a0000.tmu:: Looking up vtmu-supply from device tree
[    1.864055] s3c2410-wdt 101d0000.watchdog:: watchdog inactive, reset disabled, irq disabled
[    1.871854] device-mapper: ioctl: 4.32.0-ioctl (2015-6-26) initialised: dm-devel@redhat.com
[    1.879713] cpu cpu0: Looking up cpu-cluster.1-supply from device tree
[    1.882215] cpu cpu0: bL_cpufreq_init: CPU 0 initialized
[    1.889137] cpu cpu1: Looking up cpu-cluster.0-supply from device tree
[    1.891982] cpu cpu1: bL_cpufreq_init: CPU 1 initialized
[    1.898865] arm_big_little: bL_cpufreq_register: Registered platform driver: dt-bl
[    1.905237] sdhci: Secure Digital Host Controller Interface driver
[    1.911122] sdhci: Copyright(c) Pierre Ossman
[    1.915612] Synopsys Designware Multimedia Card Interface Driver
[    1.921911] dwmmc_exynos 12200000.mmc:: num-slots property not found, assuming 1 slot is available
[    1.930415] dwmmc_exynos 12200000.mmc:: IDMAC supports 32-bit address mode.
[    1.937333] dwmmc_exynos 12200000.mmc:: Using internal DMA controller.
[    1.943798] dwmmc_exynos 12200000.mmc:: Version ID is 250a
[    1.949276] dwmmc_exynos 12200000.mmc:: DW MMC controller at irq 90, 64 bit host data width, 64 deep fifo
[    1.958804] dwmmc_exynos 12200000.mmc:: Looking up vmmc-supply from device tree
[    1.958812] dwmmc_exynos 12200000.mmc:: Looking up vmmc-supply property in node /mmc@12200000 failed
[    1.958825] dwmmc_exynos 12200000.mmc:: Looking up vqmmc-supply from device tree
[    1.958833] dwmmc_exynos 12200000.mmc:: Looking up vqmmc-supply property in node /mmc@12200000 failed
[    1.958842] dwmmc_exynos 12200000.mmc:: No vmmc regulator found
[    1.964671] dwmmc_exynos 12200000.mmc:: No vqmmc regulator found
[    1.970661] dwmmc_exynos 12200000.mmc:: GPIO lookup for consumer cd
[    1.970668] dwmmc_exynos 12200000.mmc:: using device tree for GPIO lookup
[    1.970680] of_get_named_gpiod_flags: parsed 'cd-gpios' property of node '/mmc@12200000[0]' - status (0)
[    1.970697] dwmmc_exynos 12200000.mmc:: Got CD GPIO
[    1.975503] dwmmc_exynos 12200000.mmc:: GPIO lookup for consumer wp
[    1.975510] dwmmc_exynos 12200000.mmc:: using device tree for GPIO lookup
[    1.975517] of_get_named_gpiod_flags: can't parse 'wp-gpios' property of node '/mmc@12200000[0]'
[    1.975524] of_get_named_gpiod_flags: can't parse 'wp-gpio' property of node '/mmc@12200000[0]'
[    1.975530] dwmmc_exynos 12200000.mmc:: using lookup tables for GPIO lookup
[    1.975538] dwmmc_exynos 12200000.mmc:: lookup for GPIO wp failed
[    1.975630] platform pwrseq:: GPIO lookup for consumer reset
[    1.975636] platform pwrseq:: using device tree for GPIO lookup
[    1.975647] of_get_named_gpiod_flags: parsed 'reset-gpios' property of node '/pwrseq[0]' - status (0)
[    1.975664] dwmmc_exynos 12200000.mmc:: allocated mmc-pwrseq
[    2.011000] dwmmc_exynos 12200000.mmc:: 1 slots initialized
[    2.015286] dwmmc_exynos 12220000.mmc:: num-slots property not found, assuming 1 slot is available
[    2.024099] dwmmc_exynos 12220000.mmc:: IDMAC supports 32-bit address mode.
[    2.031009] dwmmc_exynos 12220000.mmc:: Using internal DMA controller.
[    2.037486] dwmmc_exynos 12220000.mmc:: Version ID is 250a
[    2.042967] dwmmc_exynos 12220000.mmc:: DW MMC controller at irq 91, 64 bit host data width, 64 deep fifo
[    2.052483] dwmmc_exynos 12220000.mmc:: Looking up vmmc-supply from device tree
[    2.052491] dwmmc_exynos 12220000.mmc:: Looking up vmmc-supply property in node /mmc@12220000 failed
[    2.052503] dwmmc_exynos 12220000.mmc:: Looking up vqmmc-supply from device tree
[    2.052510] dwmmc_exynos 12220000.mmc:: Looking up vqmmc-supply property in node /mmc@12220000 failed
[    2.052519] dwmmc_exynos 12220000.mmc:: No vmmc regulator found
[    2.058364] dwmmc_exynos 12220000.mmc:: No vqmmc regulator found
[    2.064348] dwmmc_exynos 12220000.mmc:: GPIO lookup for consumer cd
[    2.064354] dwmmc_exynos 12220000.mmc:: using device tree for GPIO lookup
[    2.064361] of_get_named_gpiod_flags: can't parse 'cd-gpios' property of node '/mmc@12220000[0]'
[    2.064368] of_get_named_gpiod_flags: can't parse 'cd-gpio' property of node '/mmc@12220000[0]'
[    2.064374] dwmmc_exynos 12220000.mmc:: using lookup tables for GPIO lookup
[    2.064382] dwmmc_exynos 12220000.mmc:: lookup for GPIO cd failed
[    2.064390] dwmmc_exynos 12220000.mmc:: GPIO lookup for consumer wp
[    2.064396] dwmmc_exynos 12220000.mmc:: using device tree for GPIO lookup
[    2.064402] of_get_named_gpiod_flags: can't parse 'wp-gpios' property of node '/mmc@12220000[0]'
[    2.064409] of_get_named_gpiod_flags: can't parse 'wp-gpio' property of node '/mmc@12220000[0]'
[    2.064415] dwmmc_exynos 12220000.mmc:: using lookup tables for GPIO lookup
[    2.064422] dwmmc_exynos 12220000.mmc:: lookup for GPIO wp failed
[    2.090826] dwmmc_exynos 12220000.mmc:: 1 slots initialized
[    2.096053] of_get_named_gpiod_flags: parsed 'gpios' property of node '/gpioleds/redled[0]' - status (0)
[    2.097110] usbcore: registered new interface driver usbhid
[    2.101308] usbhid: USB HID core driver
[    2.106430] NET: Registered protocol family 17
[    2.109456] NET: Registered protocol family 15
[    2.114180] Registering SWP/SWPB emulation handler
[    2.120103] of_get_named_gpiod_flags: parsed 'hpd-gpio' property of node '/hdmi@14530000[0]' - status (0)
[    2.120184] exynos-hdmi 14530000.hdmi:: Looking up vdd-supply from device tree
[    2.120715] exynos-hdmi 14530000.hdmi:: Looking up vdd_osc-supply from device tree
[    2.121266] exynos-hdmi 14530000.hdmi:: Looking up vdd_pll-supply from device tree
[    2.121782] exynos-hdmi 14530000.hdmi:: Looking up hdmi-en-supply from device tree
[    2.121790] exynos-hdmi 14530000.hdmi:: Looking up hdmi-en-supply property in node /hdmi@14530000 failed
[    2.121800] 14530000.hdmi: supply hdmi-en not found, using dummy regulator
[    2.128183] exynos-drm exynos-drm: bound 14400000.fimd: (ops fimd_component_ops)
[    2.134663] exynos-drm exynos-drm: bound 14450000.mixer: (ops mixer_component_ops)
[    2.142311] exynos-drm exynos-drm: bound 14530000.hdmi: (ops hdmi_component_ops)
[    2.149488] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[    2.156067] [drm] No driver support for vblank timestamp query.
[    2.159665] mmc_host mmc1: Bus speed (slot 0) = 50000000Hz (slot req 50000000Hz, actual 50000000HZ div = 0)
[    2.159871] mmc1: new high speed SDHC card at address aaaa
[    2.162128] mmcblk0: mmc1:aaaa SU08G 7.40 GiB
[    2.164505]  mmcblk0: p1 p2
[    2.184319] [drm] Initialized exynos 1.0.0 20110530 on minor 0
[    2.190715] exynos-dwc3 usb@12000000:: Looking up vdd33-supply from device tree
[    2.191285] exynos-dwc3 usb@12000000:: Looking up vdd10-supply from device tree
[    2.394680] xhci-hcd xhci-hcd.6.auto: xHCI Host Controller
[    2.398728] xhci-hcd xhci-hcd.6.auto: new USB bus registered, assigned bus number 3
[    2.406606] xhci-hcd xhci-hcd.6.auto: hcc params 0x0220f04c hci version 0x100 quirks 0x00010010
[    2.415034] xhci-hcd xhci-hcd.6.auto: irq 137, io mem 0x12000000
[    2.421113] usb usb3: New USB device found, idVendor=1d6b, idProduct=0002
[    2.427738] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    2.434936] usb usb3: Product: xHCI Host Controller
[    2.439780] usb usb3: Manufacturer: Linux 4.2.0-rc1+ xhci-hcd
[    2.445503] usb usb3: SerialNumber: xhci-hcd.6.auto
[    2.450972] hub 3-0:1.0: USB hub found
[    2.454080] hub 3-0:1.0: 1 port detected
[    2.458357] xhci-hcd xhci-hcd.6.auto: xHCI Host Controller
[    2.463449] xhci-hcd xhci-hcd.6.auto: new USB bus registered, assigned bus number 4
[    2.471218] usb usb4: New USB device found, idVendor=1d6b, idProduct=0003
[    2.477825] usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    2.485022] usb usb4: Product: xHCI Host Controller
[    2.489867] usb usb4: Manufacturer: Linux 4.2.0-rc1+ xhci-hcd
[    2.495582] usb usb4: SerialNumber: xhci-hcd.6.auto
[    2.501027] hub 4-0:1.0: USB hub found
[    2.504163] hub 4-0:1.0: 1 port detected
[    2.508975] exynos-dwc3 usb@12400000:: Looking up vdd33-supply from device tree
[    2.509466] exynos-dwc3 usb@12400000:: Looking up vdd10-supply from device tree
[    2.712823] xhci-hcd xhci-hcd.9.auto: xHCI Host Controller
[    2.716872] xhci-hcd xhci-hcd.9.auto: new USB bus registered, assigned bus number 5
[    2.724756] xhci-hcd xhci-hcd.9.auto: hcc params 0x0220f04c hci version 0x100 quirks 0x00010010
[    2.733176] xhci-hcd xhci-hcd.9.auto: irq 138, io mem 0x12400000
[    2.739245] usb usb5: New USB device found, idVendor=1d6b, idProduct=0002
[    2.745880] usb usb5: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    2.753078] usb usb5: Product: xHCI Host Controller
[    2.757922] usb usb5: Manufacturer: Linux 4.2.0-rc1+ xhci-hcd
[    2.763785] usb usb5: SerialNumber: xhci-hcd.9.auto
[    2.768503] usb 3-1: new high-speed USB device number 2 using xhci-hcd
[    2.775659] hub 5-0:1.0: USB hub found
[    2.778738] hub 5-0:1.0: 1 port detected
[    2.783026] xhci-hcd xhci-hcd.9.auto: xHCI Host Controller
[    2.788091] xhci-hcd xhci-hcd.9.auto: new USB bus registered, assigned bus number 6
[    2.795897] usb usb6: New USB device found, idVendor=1d6b, idProduct=0003
[    2.802466] usb usb6: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    2.809656] usb usb6: Product: xHCI Host Controller
[    2.814508] usb usb6: Manufacturer: Linux 4.2.0-rc1+ xhci-hcd
[    2.820240] usb usb6: SerialNumber: xhci-hcd.9.auto
[    2.825094] usb 4-1: new SuperSpeed USB device number 2 using xhci-hcd
[    2.832216] hub 6-0:1.0: USB hub found
[    2.835303] hub 6-0:1.0: 1 port detected
[    2.840532] s3c-rtc 101e0000.rtc:: rtc core: registered s3c as rtc1
[    2.847584] s5m-rtc s2mps14-rtc: setting system clock to 2015-07-14 01:08:25 UTC (1436836105)
[    2.855481] usb 4-1: New USB device found, idVendor=05e3, idProduct=0616
[    2.861321] usb 4-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[    2.868415] usb 4-1: Product: USB3.0 Hub
[    2.872317] usb 4-1: Manufacturer: GenesysLogic
[    2.887803] hub 4-1:1.0: USB hub found
[    2.890455] hub 4-1:1.0: 2 ports detected
[    2.901940] Freeing unused kernel memory: 404K (c075b000 - c07c0000)
[    2.906992] usb 3-1: New USB device found, idVendor=05e3, idProduct=0610
[    2.913513] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[    2.920612] usb 3-1: Product: USB2.0 Hub
[    2.924514] usb 3-1: Manufacturer: GenesysLogic
[    2.952009] hub 3-1:1.0: USB hub found
[    2.954924] hub 3-1:1.0: 2 ports detected
[    2.970064] random: systemd-udevd urandom read with 80 bits of entropy available
[    3.215994] usb 6-1: new SuperSpeed USB device number 2 using xhci-hcd
[    3.237723] usb 6-1: New USB device found, idVendor=0bda, idProduct=8153
[    3.243129] usb 6-1: New USB device strings: Mfr=1, Product=2, SerialNumber=6
[    3.250172] usb 6-1: Product: USB 10/100/1000 LAN
[    3.254846] usb 6-1: Manufacturer: Realtek
[    3.258914] usb 6-1: SerialNumber: 000001000000
[    3.322067] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: (null)
[    3.386033] usb 4-1.2: new SuperSpeed USB device number 3 using xhci-hcd
[    3.408811] usb 4-1.2: New USB device found, idVendor=05e3, idProduct=0735
[    3.414239] usb 4-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[    3.421539] usb 4-1.2: Product: USB3.0 SATA Bridge
[    3.426275] usb 4-1.2: Manufacturer: USB Storage
[    3.430862] usb 4-1.2: SerialNumber: 0000000000000033
[    4.105635] udevd[1746]: starting version 175
[    4.379721] random: nonblocking pool is initialized
[    4.476677] samsung-pwm 12dd0000.pwm:: tried to request PWM channel 1 without output
[    4.483029] leds_pwm pwmleds:: unable to request PWM for green:mmc0: -22
[    4.490794] leds_pwm: probe of pwmleds: failed with error -22
[    4.576076] usb_phy_generic.0.auto supply vcc not found, using dummy regulator
[    4.582190] usb_phy_generic.1.auto supply vcc not found, using dummy regulator
[    4.589654] usb_phy_generic.2.auto supply vcc not found, using dummy regulator
[    4.597056] usb_phy_generic.3.auto supply vcc not found, using dummy regulator
[    4.603756] usb_phy_generic.4.auto supply vcc not found, using dummy regulator
[    4.611029] usb_phy_generic.5.auto supply vcc not found, using dummy regulator
[    4.621414] usb_phy_generic.7.auto supply vcc not found, using dummy regulator
[    4.628822] usb_phy_generic.8.auto supply vcc not found, using dummy regulator
[    4.657950] usbcore: registered new interface driver r8152
[    4.669980] usb-storage 4-1.2:1.0: USB Mass Storage device detected
[    4.675842] scsi host0: usb-storage 4-1.2:1.0
[    4.680144] usbcore: registered new interface driver usb-storage
[    4.700543] usbcore: registered new interface driver cdc_ether
[    4.812164] usb 6-1: reset SuperSpeed USB device number 2 using xhci-hcd
[    4.870365] r8152 6-1:1.0 eth0: v2.04.0 (2015/03/06)
[    4.873898] r8152 6-1:1.0 eth0: This product is covered by one or more of the following patents:
[    4.873898]       US6,570,884, US6,115,776, and US6,327,625.
[    4.873898]
[    5.668463] EXT4-fs (mmcblk0p2): re-mounted. Opts: (null)
[    5.676463] scsi 0:0:0:0: Direct-Access     Samsung  SSD 850 EVO 120G 1003 PQ: 0 ANSI: 6
[    5.684417] sd 0:0:0:0: Attached scsi generic sg0 type 0
[    5.684666] sd 0:0:0:0: [sda] 234441632 512-byte logical blocks: (120 GB/111 GiB)
[    5.685461] sd 0:0:0:0: [sda] Write Protect is off
[    5.685471] sd 0:0:0:0: [sda] Mode Sense: 5f 00 10 08
[    5.686169] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, supports DPO and FUA
[    5.690823]  sda: sda1
[    5.702201] sd 0:0:0:0: [sda] Attached SCSI disk
[    6.807014] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: data=ordered
[    7.678428] NET: Registered protocol family 10
[    7.800947] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[   10.348978] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready

INIT: Entering runlevel: 2
[info] Using makefile-style concurrent boot in runlevel 2.
[....] Starting enhanced syslogd: rsyslogd. ok
[....] Starting periodic command scheduler: cron. ok
[....] Starting system message bus: dbus. ok
[....] Starting OpenBSD Secure Shell server: sshd. ok
[....] Starting Samba daemons: nmbd smbd. ok

Debian GNU/Linux 7 odroid ttySAC2

odroid login: root
Password:

Last login: Tue Jul 14 10:27:15 KST 2015 on tty1
Linux odroid 4.2.0-rc1+ #4 SMP PREEMPT Fri Jul 10 16:45:24 KST 2015 armv7l

The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.

Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.

root@odroid:~# uname -a
Linux odroid 4.2.0-rc1+ #4 SMP PREEMPT Fri Jul 10 16:45:24 KST 2015 armv7l
GNU/Linux

Grab the Kernel source code from our Github if you want to try.
https://github.com/hardkernel/linux/com ... 4-v4.2-rc1
This experimental Kernel 4.2 supports the SMP 4 x A15 cores, USB 3.0, Gigabit Ethernet and some other basic features.
But HDMI, GPU, VPU(MFC), and HMP are not working. So it is useful only for the headless applications probably.
The OMV(Open Media Vault) OS will run on the latest mainline Kernel.


Our Stock Kernel 3.10 supports HDMI, GPU, VPU(MFC), and HMP.
User avatar
odroid
Site Admin
 
Posts: 23691
Joined: Fri Feb 22, 2013 11:14 pm
languages_spoken: English
ODROIDs: ODROID

Re: ODROID-XU4

Unread postby karlkloss » Tue Jul 14, 2015 4:51 pm

Does the cooling fan run all the time, or is it temperature controlled?
Is there a passive cooling option?
User avatar
karlkloss
 
Posts: 140
Joined: Tue Jan 13, 2015 9:34 pm
languages_spoken: english
ODROIDs: C1

Re: ODROID-XU4

Unread postby odroid » Tue Jul 14, 2015 5:02 pm

The fan runs by temperature controlled proportionally.
If you limit the max frequency to 1Ghz from 2Ghz of A15 cores, a passive cooler can be used.
User avatar
odroid
Site Admin
 
Posts: 23691
Joined: Fri Feb 22, 2013 11:14 pm
languages_spoken: English
ODROIDs: ODROID

Re: ODROID-XU4

Unread postby karlkloss » Tue Jul 14, 2015 5:07 pm

Is there an analog audio output?
If not, is there an already available I2S solution?
After the bad experience with the C1 and USB audio, I don't want to go this way again.
User avatar
karlkloss
 
Posts: 140
Joined: Tue Jan 13, 2015 9:34 pm
languages_spoken: english
ODROIDs: C1

Re: ODROID-XU4

Unread postby odroid » Tue Jul 14, 2015 5:09 pm

We are considering to make an add-on board of I2S/DAC. But there is no firm schedule at this moment.
User avatar
odroid
Site Admin
 
Posts: 23691
Joined: Fri Feb 22, 2013 11:14 pm
languages_spoken: English
ODROIDs: ODROID

Re: ODROID-XU4

Unread postby karlkloss » Tue Jul 14, 2015 5:33 pm

I'm not talking about a board, I'm more interested in a working I2S driver.
I2S boards I can get a dime a dozen.
User avatar
karlkloss
 
Posts: 140
Joined: Tue Jan 13, 2015 9:34 pm
languages_spoken: english
ODROIDs: C1

Re: ODROID-XU4

Unread postby odroid » Tue Jul 14, 2015 6:02 pm

There was a MAX98090 CODEC on the XU3 board and it worked with the I2S driver in the Kernel.
But you need to check whether your I2S board supports 1.8Volt interface or not.
Here is the pin-map of 12-pin header for the audio application.
http://odroid.com/dokuwiki/doku.php?id= ... connectors
User avatar
odroid
Site Admin
 
Posts: 23691
Joined: Fri Feb 22, 2013 11:14 pm
languages_spoken: English
ODROIDs: ODROID

Re: ODROID-XU4

Unread postby karlkloss » Tue Jul 14, 2015 7:56 pm

Ah, there's that 1.8V problem again.
All affordable I2s boards I know of use 3.3V level. And I'm currently not in the mood of fiddling around with half-working things.

So if I want to use the XU4 as a media center, I'd have to buy a XU4, a (yet to come) I2S adapter, a housing, some wires, and then I'll end up at a price where I'd better buy an all-in-one Android box with the same processor.

Honestly guys, why do you think that everybody is fine with the speaker built into the TV or monitor?
All my friends that use a media box or media PC use external amplifiers and speakers.
So you should really think about adding a codec or a S/PDIF output.
User avatar
karlkloss
 
Posts: 140
Joined: Tue Jan 13, 2015 9:34 pm
languages_spoken: english
ODROIDs: C1

Re: ODROID-XU4

Unread postby zonk » Wed Jul 15, 2015 3:34 am

hello all.. i'm have a plan to try and buy Odroid for first time.. im not a developer, and im buy Odroid just for play Android..
im willing to buy:
- 1pcs XU4
- 1pcs MicroSD UHS-1 Android 16GB
- 1pcs HDMI Cable
- 1set Case
And my question is:
1. is my list above correct only to play Android? or must i buy other peripheral again?
2. MicroSD UHS-1 included MicroSD Reader or not??
3. is XU4 save to run 12hours per day??

thankz before..
zonk
 
Posts: 1
Joined: Wed Jul 15, 2015 2:48 am
languages_spoken: english, indonesia
ODROIDs: not have yet

Re: ODROID-XU4

Unread postby hokoon » Wed Jul 15, 2015 7:20 am

1. Yes, but you might need a USB WiFi
2. No
3. Yes


IMO, if this is your first ODROID I suggest you buy U3. It's more user friendly and lots of forum post that's cover almost anything you want to do.
hokoon
 
Posts: 252
Joined: Tue Jun 11, 2013 2:55 pm
languages_spoken: ไทย
ODROIDs: U2, XU, U3, C-1

Re: ODROID-XU4

Unread postby robroy » Wed Jul 15, 2015 7:36 am

Honestly guys, why do you think that everybody is fine with the speaker built into the TV or monitor?
All my friends that use a media box or media PC use external amplifiers and speakers.

You can use an HDMI audio splitter or simply plug the amplifier into the audio pass-through output of the TV.
Rob Roy, Editor-in-Chief of ODROID Magazine (submit an article | make a donation)
User avatar
robroy
 
Posts: 3328
Joined: Mon Feb 25, 2013 2:29 am
Location: San Francisco, California
languages_spoken: English
ODROIDs: Q2, X, X2, U2, U3, XU-E, XU3, XU4, C1, C1+, C2

Re: ODROID-XU4

Unread postby memeka » Wed Jul 15, 2015 9:44 am

Is the 30-pin header compatible with the xu/xu3 header?
User avatar
memeka
 
Posts: 3529
Joined: Mon May 20, 2013 10:22 am
languages_spoken: english
ODROIDs: XU rev2 + eMMC + UART
U3 + eMMC + IO Shield + UART

Re: ODROID-XU4

Unread postby tobetter » Wed Jul 15, 2015 9:54 am

memeka wrote:Is the 30-pin header compatible with the xu/xu3 header?

100% compatible with XU3, but not 100% compatible with XU due to some of signal added new from XU.
tobetter
 
Posts: 2040
Joined: Mon Feb 25, 2013 10:55 am
Location: Republic Of Korea
languages_spoken: Korean, English
ODROIDs: X, X2, U2, U3, XU3, C1

Re: ODROID-XU4

Unread postby folderman » Wed Jul 15, 2015 10:02 am

Oh, good to hear that the launch of XU4, seems that I can replace my odroid-x now.

However, you mentioned: "But HDMI, GPU, VPU(MFC), and HMP are not working. So it is useful only for the headless applications probably"

What does it mean? As I used odroid everyday, using it as headless seems not my cup of tea.

Thanks!

Rgds,
Kenneth
folderman
 
Posts: 19
Joined: Thu Feb 28, 2013 2:43 pm
languages_spoken: english
ODROIDs: odroid-x

Re: ODROID-XU4

Unread postby tobetter » Wed Jul 15, 2015 10:10 am

folderman wrote:However, you mentioned: "But HDMI, GPU, VPU(MFC), and HMP are not working. So it is useful only for the headless applications probably"

Read the text little more carefully :), this is about the unsupported features with mainline Linux kernel 4.x. But basically XU4 will use the same kernel 3.10.x, which means all supported features and benefits will be continued on XU4. :)
tobetter
 
Posts: 2040
Joined: Mon Feb 25, 2013 10:55 am
Location: Republic Of Korea
languages_spoken: Korean, English
ODROIDs: X, X2, U2, U3, XU3, C1

Re: ODROID-XU4

Unread postby folderman » Wed Jul 15, 2015 10:23 am

Good to hear that~~~~ :D
folderman
 
Posts: 19
Joined: Thu Feb 28, 2013 2:43 pm
languages_spoken: english
ODROIDs: odroid-x

Re: ODROID-XU4

Unread postby karlkloss » Wed Jul 15, 2015 2:55 pm

You can use an HDMI audio splitter or simply plug the amplifier into the audio pass-through output of the TV.


Captain Obvious, is this you?

The audio outputs of most TVs are of surprisingly low quality. Lots of noise that you don't notice when you use the inbuilt speakers, but will when you use an external amplifier. Also I don't want the TV running all the time when I'm just listening to music.
A decent HDMI Audio splitter costs nearly as much as the whole board.
And all this because you wanted to save the $2 for an audio codec or a S/P-DIF output.

You may say that the Odroid boards are just meant as development boards or a cheap PC surrogate, but then you ignore the fact that many of us already have PC monitors with just DVI and Displayport, but without any audio function. In this case, you can't play a game, watch a video, or hear music while programming, without additional hardware.
With the C1, I'm up to now not able to use an USB audio adapter without lots of crackling and popping, if it is working at all.
Will this be any better with the XU4?
User avatar
karlkloss
 
Posts: 140
Joined: Tue Jan 13, 2015 9:34 pm
languages_spoken: english
ODROIDs: C1

Re: ODROID-XU4

Unread postby stmicro » Wed Jul 15, 2015 3:02 pm

I want to buy this board.
It seems to be a replacement of xu3.
Does it replace the u3 too?
Xu4 is cheaper than u3 if we consider the psu and fan.
I hope we can keep buying the u3 for a while because its gpu driver is more stable and faster than other boards.
stmicro
 
Posts: 205
Joined: Tue Apr 28, 2015 4:23 pm
Location: shenzhen
languages_spoken: english, chinese
ODROIDs: 2 x C1+, 2 x C2
1 x XU-L, 2 x XU3-L, 3 x U3, 2 x U2, 9 x XU4

Re: ODROID-XU4

Unread postby robroy » Wed Jul 15, 2015 4:42 pm

karlkloss wrote:
You can use an HDMI audio splitter or simply plug the amplifier into the audio pass-through output of the TV.


Captain Obvious, is this you?

Let's adjust the sarcasm/condescension volume control down to 0 before we continue.

The audio outputs of most TVs are of surprisingly low quality. Lots of noise that you don't notice when you use the inbuilt speakers, but will when you use an external amplifier. Also I don't want the TV running all the time when I'm just listening to music.

All of the TVs that I have bought in the past 8 years offer a fiber optic digital audio output as well as a "Music-only" mode. You need to use appropriate equipment to build a nice media center.

A decent HDMI Audio splitter costs nearly as much as the whole board.
And all this because you wanted to save the $2 for an audio codec or a S/P-DIF output.

Hardkernel's SPDIF adapter is $16. This should give you a better idea of the actual cost - not $2, and certainly not $79.

You may say that the Odroid boards are just meant as development boards or a cheap PC surrogate, but then you ignore the fact that many of us already have PC monitors with just DVI and Displayport, but without any audio function. In this case, you can't play a game, watch a video, or hear music while programming, without additional hardware.

Additional hardware, or appropriate hardware? A small audio-less PC monitor would not be my first choice if I wanted to experience high-quality sound or watch movies.

The basic board is meant to be versatile in order to offer it at a competitive price. For those using it for its intended purpose as a dev board like you described, it would be a waste of hardware and money to pre-bundle it as a gaming or multi-media device. The way these boards work is that you add in the peripherals that you need for your project, keeping the cost coincidental with its actual use. The HDMI port already offers a digital audio output and you can build from that.

FYI, the U3 has an analog headphone jack and is more suitable for your use case than a C1 or XU3/4. I personally use a bluetooth speaker system with one of my U3s.
Last edited by robroy on Thu Jul 16, 2015 12:02 pm, edited 2 times in total.
Rob Roy, Editor-in-Chief of ODROID Magazine (submit an article | make a donation)
User avatar
robroy
 
Posts: 3328
Joined: Mon Feb 25, 2013 2:29 am
Location: San Francisco, California
languages_spoken: English
ODROIDs: Q2, X, X2, U2, U3, XU-E, XU3, XU4, C1, C1+, C2

Re: ODROID-XU4

Unread postby youka » Wed Jul 15, 2015 6:29 pm

Impressive price, very impressive size, normal HDMI port, and I like the CloudShell idea too~ Will be ordering soon and (slightly off-topic) looking forward to GLES 3.1 support one day.
youka
 
Posts: 163
Joined: Wed Oct 09, 2013 8:38 pm
languages_spoken: english
ODROIDs: Odroid XU+E, U2, U3, XU3, XU4 + Cloudshell

Re: ODROID-XU4

Unread postby memeka » Wed Jul 15, 2015 8:34 pm

@odroid

why the reduction in memory bandwidth from xu3? what's the effect of that - any benchmarks?
User avatar
memeka
 
Posts: 3529
Joined: Mon May 20, 2013 10:22 am
languages_spoken: english
ODROIDs: XU rev2 + eMMC + UART
U3 + eMMC + IO Shield + UART

Re: ODROID-XU4

Unread postby odroid » Wed Jul 15, 2015 10:33 pm

There was no reduction of memory bandwidth.
XU3 and XU4 have the same 750Mhz DDR3 clock frequency.

In fact, the old value of 933Mhz was given by Samsung. But the Kernel driver has been set at 750Mhz over one year and we found that 750Mhz is the real value when we tested some XU4 engineering samples.
Anyway, we need to try 933Mhz or 866Mhz of DDR3 clock speed with XU3/XU4 one day. :)
User avatar
odroid
Site Admin
 
Posts: 23691
Joined: Fri Feb 22, 2013 11:14 pm
languages_spoken: English
ODROIDs: ODROID

Re: ODROID-XU4

Unread postby patchoncas » Wed Jul 15, 2015 10:59 pm

karlkloss wrote:
You can use an HDMI audio splitter or simply plug the amplifier into the audio pass-through output of the TV.


Captain Obvious, is this you?

The audio outputs of most TVs are of surprisingly low quality. Lots of noise that you don't notice when you use the inbuilt speakers, but will when you use an external amplifier. Also I don't want the TV running all the time when I'm just listening to music.
A decent HDMI Audio splitter costs nearly as much as the whole board.
And all this because you wanted to save the $2 for an audio codec or a S/P-DIF output.

You may say that the Odroid boards are just meant as development boards or a cheap PC surrogate, but then you ignore the fact that many of us already have PC monitors with just DVI and Displayport, but without any audio function. In this case, you can't play a game, watch a video, or hear music while programming, without additional hardware.
With the C1, I'm up to now not able to use an USB audio adapter without lots of crackling and popping, if it is working at all.
Will this be any better with the XU4?


Then buy the ODROID XU-3 if you need the feature, it's as simple as that.
Hardkernel seems to have made a great device with this board. For the price it's awesome. The Gigabit ethernet + 2x USB 3.0 is really tempting.

One thing though: why was the frequency of the PoP memory lowered to 750 Mhz?
Edit: only saw odroid's answer now, that makes sense!

Looking to order one soon via Pollin. Congratulations for the product, Hardkernel!
patchoncas
 
Posts: 12
Joined: Wed Apr 02, 2014 9:49 am
languages_spoken: english, portuguese

Re: ODROID-XU4

Unread postby Bingo » Thu Jul 16, 2015 3:45 am

karlkloss wrote:Ah, there's that 1.8V problem again.
All affordable I2s boards I know of use 3.3V level. And I'm currently not in the mood of fiddling around with half-working things.

So if I want to use the XU4 as a media center, I'd have to buy a XU4, a (yet to come) I2S adapter, a housing, some wires, and then I'll end up at a price where I'd better buy an all-in-one Android box with the same processor.

Honestly guys, why do you think that everybody is fine with the speaker built into the TV or monitor?
All my friends that use a media box or media PC use external amplifiers and speakers.
So you should really think about adding a codec or a S/PDIF output.


If I2S is like I2C , you could give this levelshifter a try (Not expensive and .de located) but easy to DIY.
What speed is I2S ?

http://www.watterott.com/de/Level-Shifter
https://github.com/watterott/Level-Shif ... er_v10.pdf

It's based on the NXP App-Note , and should work with 1v8 / 3v3 - Adafruit sells one like this one also.
The bss138 should have a VGS(th) of max 1v5 , and you could substitute the bss138 for a Si2342DS that have a VGS(th) of 1v2

bss138 DS
http://www.adafruit.com/datasheets/BSS138.pdf

Si2342DS DS
http://www.vishay.com/doc?63302


For the digital lines (non bidirectional) use a CPLD ;)
viewtopic.php?f=80&t=11888

I haven't got an XU4 - So i cant test a CPLD core for it.
But i would expect to be able to levelshift all 30 IO-Ports from 1v8 to 3v3 and still have pins for levelshifting a few other pins


/Bingo
Bingo
 
Posts: 73
Joined: Thu Dec 04, 2014 5:46 pm
Location: Denmark
languages_spoken: english
ODROIDs: odroid-u3 & odroid-c1/c2

Re: ODROID-XU4

Unread postby luxmile » Thu Jul 16, 2015 9:07 am

Is this new XU4 compatible with previous eMMC version?
Just want to know if I buy it and reuse my old eMMC v4.5 instead of buy a new one...
luxmile
 
Posts: 33
Joined: Wed Feb 25, 2015 10:52 am
languages_spoken: english

Re: ODROID-XU4

Unread postby tobetter » Thu Jul 16, 2015 9:09 am

luxmile wrote:Is this new XU4 compatible with previous eMMC version?
Just want to know if I buy it and reuse my old eMMC v4.5 instead of buy a new one...

You can use your eMMC on XU4.
tobetter
 
Posts: 2040
Joined: Mon Feb 25, 2013 10:55 am
Location: Republic Of Korea
languages_spoken: Korean, English
ODROIDs: X, X2, U2, U3, XU3, C1

Re: ODROID-XU4

Unread postby memeka » Thu Jul 16, 2015 9:49 am

Bingo wrote:
karlkloss wrote:Ah, there's that 1.8V problem again.
All affordable I2s boards I know of use 3.3V level. And I'm currently not in the mood of fiddling around with half-working things.

So if I want to use the XU4 as a media center, I'd have to buy a XU4, a (yet to come) I2S adapter, a housing, some wires, and then I'll end up at a price where I'd better buy an all-in-one Android box with the same processor.

Honestly guys, why do you think that everybody is fine with the speaker built into the TV or monitor?
All my friends that use a media box or media PC use external amplifiers and speakers.
So you should really think about adding a codec or a S/PDIF output.


If I2S is like I2C , you could give this levelshifter a try (Not expensive and .de located) but easy to DIY.
What speed is I2S ?

http://www.watterott.com/de/Level-Shifter
https://github.com/watterott/Level-Shif ... er_v10.pdf

It's based on the NXP App-Note , and should work with 1v8 / 3v3 - Adafruit sells one like this one also.
The bss138 should have a VGS(th) of max 1v5 , and you could substitute the bss138 for a Si2342DS that have a VGS(th) of 1v2

bss138 DS
http://www.adafruit.com/datasheets/BSS138.pdf

Si2342DS DS
http://www.vishay.com/doc?63302


For the digital lines (non bidirectional) use a CPLD ;)
viewtopic.php?f=80&t=11888

I haven't got an XU4 - So i cant test a CPLD core for it.
But i would expect to be able to levelshift all 30 IO-Ports from 1v8 to 3v3 and still have pins for levelshifting a few other pins


/Bingo



have you seen the xu4 shifter shield? http://www.hardkernel.com/main/products ... 3556253995

got all of the pins up to 3.3/5 selectable.
User avatar
memeka
 
Posts: 3529
Joined: Mon May 20, 2013 10:22 am
languages_spoken: english
ODROIDs: XU rev2 + eMMC + UART
U3 + eMMC + IO Shield + UART

Re: ODROID-XU4

Unread postby Aussiehash » Thu Jul 16, 2015 11:29 am

Just out of curiosity, would these I2S boards work with a XU4 ?
https://volumio.org/raspberry-pi-i2s-da ... s-so-good/
Aussiehash
 
Posts: 6
Joined: Sun May 03, 2015 1:41 am
languages_spoken: english

Re: ODROID-XU4

Unread postby memeka » Thu Jul 16, 2015 12:00 pm

Aussiehash wrote:Just out of curiosity, would these I2S boards work with a XU4 ?
https://volumio.org/raspberry-pi-i2s-da ... s-so-good/


I don't think so, but I think it fits and works on the XU4 + shifter board: http://www.hardkernel.com/main/products ... 3556253995

@odroid - does the shifter board have mounting holes compatible with rpi?
User avatar
memeka
 
Posts: 3529
Joined: Mon May 20, 2013 10:22 am
languages_spoken: english
ODROIDs: XU rev2 + eMMC + UART
U3 + eMMC + IO Shield + UART

Re: ODROID-XU4

Unread postby tana32 » Thu Jul 16, 2015 1:44 pm

:roll: :roll: :roll: :roll: :roll:

ร่วมเล่นสนุกๆไปกับพวกเรา ได้ที่นี่ คาสิโนออนไลน์
tana32
 
Posts: 1
Joined: Thu Jul 16, 2015 1:39 pm
languages_spoken: english
ODROIDs: Exynos 4412 Prime

Re: ODROID-XU4

Unread postby karlkloss » Thu Jul 16, 2015 3:03 pm

memeka wrote:
Bingo wrote:have you seen the xu4 shifter shield? http://www.hardkernel.com/main/products ... 3556253995

got all of the pins up to 3.3/5 selectable.


Well, everybody is excited about the low price of the base board.
But then you add this level shifter and that adapter, some special cables, a pricey Flash module, and spend a lot of time trying to get everything working.
And then you compare the overall price to a Mini-ITX board, and you'll see that it provides tons of features and peripherals, runs all actual operating systems, runs games and applications out of the box, that ARM boards can only dream of, etc. And most of them are passively cooled.

I like small, cheap boards like the C1. Really. I have two C1s, several Rapsberry Pis, two Banana Pis, a Cubieboard, a Beaglebone Black, etc.
They are really nice when you are ok with the features they come with. I also like it to have an ARM architecture, and not having to give my money to Intel's deep, greedy pockets.
But with the bigger, more expensive boards, the math just doesn't add up.
User avatar
karlkloss
 
Posts: 140
Joined: Tue Jan 13, 2015 9:34 pm
languages_spoken: english
ODROIDs: C1

Re: ODROID-XU4

Unread postby murrman » Thu Jul 16, 2015 3:23 pm

karlkloss wrote:Well, everybody is excited about the low price of the base board.
But then you add this level shifter and that adapter, some special cables, a pricey Flash module, and spend a lot of time trying to get everything working.
And then you compare the overall price to a Mini-ITX board, and you'll see that it provides tons of features and peripherals, runs all actual operating systems, runs games and applications out of the box, that ARM boards can only dream of, etc.

I like small, cheap boards like the C1. Really. I have two C1s, several Rapsberry Pis, two Banana Pis, a Cubieboard, a Beaglebone Black, etc.
They are really nice when you are ok with the features they come with. I also like it to have an ARM architecture, and not having to give my money to Intel's deep, greedy pockets.
But with the bigger, more expensive boards, the math just doesn't add up.


These sort of boards are extremely useful for robotics, embedded computer vision, machine perception, etc. A Mini-ITX is still very much intended for desktop environments, and the "cheap" boards like raspberry Pi, C1, etc are generally not powerful enough to perform any significant real-time processing of 2D or 3D data. I realize that this is probably not the largest segment of the ODROID market, but boards like the XU4 are very important for a wide range of R&D projects.
User avatar
murrman
 
Posts: 240
Joined: Mon Jul 08, 2013 8:53 am
Location: Texas
languages_spoken: english

Re: ODROID-XU4

Unread postby Gaurav277 » Thu Jul 16, 2015 4:09 pm

HI
I've recently ordered XU4 and plan to use as NAS with Ubuntu and 2 USB3.0 drives (2.5" drives) . I have couple of questions ?

1. Can this board sustain 24x7 uptime ? If not then how long maximum I can run this per day ?
2. Is there audio through HDMI ? If no, Will you release any audio module for this ?
Gaurav277
 
Posts: 18
Joined: Thu Jul 16, 2015 3:12 pm
languages_spoken: english
ODROIDs: XU4

Re: ODROID-XU4

Unread postby luxmile » Thu Jul 16, 2015 5:56 pm

tobetter wrote:
luxmile wrote:Is this new XU4 compatible with previous eMMC version?
Just want to know if I buy it and reuse my old eMMC v4.5 instead of buy a new one...

You can use your eMMC on XU4.


A very good news... :)
and since this XU4 fully compatible with XU3,
I'm pretty sure it has also virtualization capability,
am I right?
luxmile
 
Posts: 33
Joined: Wed Feb 25, 2015 10:52 am
languages_spoken: english

Re: ODROID-XU4

Unread postby mdrjr » Thu Jul 16, 2015 8:08 pm

Gaurav277 wrote:HI
I've recently ordered XU4 and plan to use as NAS with Ubuntu and 2 USB3.0 drives (2.5" drives) . I have couple of questions ?

1. Can this board sustain 24x7 uptime ? If not then how long maximum I can run this per day ?
2. Is there audio through HDMI ? If no, Will you release any audio module for this ?


1. Yes, you can run 24/7 no issues.
2. Yes there's audio over hdmi.

luxmile wrote:
tobetter wrote:
luxmile wrote:Is this new XU4 compatible with previous eMMC version?
Just want to know if I buy it and reuse my old eMMC v4.5 instead of buy a new one...

You can use your eMMC on XU4.


A very good news... :)
and since this XU4 fully compatible with XU3,
I'm pretty sure it has also virtualization capability,
am I right?


Yes, there's even an article on ODROID Magazine about it.
mdrjr
Site Admin
 
Posts: 11620
Joined: Fri Feb 22, 2013 11:34 pm
Location: Brazil
languages_spoken: english, portuguese
ODROIDs: -

Re: ODROID-XU4

Unread postby LiquidAcid » Thu Jul 16, 2015 8:18 pm

Just a small suggestion: Maybe Hardkernel shouldn't disclose that they're using pirated movies to do their benchmarks.
LiquidAcid
 
Posts: 1056
Joined: Fri Oct 11, 2013 11:07 pm
languages_spoken: english
ODROIDs: X2

Re: ODROID-XU4

Unread postby odroid » Thu Jul 16, 2015 8:24 pm

LiquidAcid wrote:Just a small suggestion: Maybe Hardkernel shouldn't disclose that they're using pirated movies to do their benchmarks.


Oh sorry... we've used some test files which our customers sent us for the video codec test.
We will update the screen captures early next week.
Thank you for the suggestion!
User avatar
odroid
Site Admin
 
Posts: 23691
Joined: Fri Feb 22, 2013 11:14 pm
languages_spoken: English
ODROIDs: ODROID

Re: ODROID-XU4

Unread postby patoberli » Thu Jul 16, 2015 11:46 pm

LiquidAcid wrote:Just a small suggestion: Maybe Hardkernel shouldn't disclose that they're using pirated movies to do their benchmarks.

In some countries (like here Switzerland) it's not pirating, it's legally allowed copying ;)
I just am not allowed to share the file to others. In any case, the file was not provided from me.
-
pato
patoberli
 
Posts: 401
Joined: Mon Feb 23, 2015 6:32 pm
Location: Switzerland
languages_spoken: english, german
ODROIDs: C1 with RTC, Bluetooth 4.0, Wireless stick 4.0

Re: ODROID-XU4

Unread postby magnum_pi » Fri Jul 17, 2015 1:33 am

Wow. I haven't checked on the hardkernel site for several months and now when I come back I see this. It looks like an excellent piece of kit. The cloud thingie looks like what I was trying to achieve last year with the XU3-Lite and USB3->SATA enclosure. I never got that to work, but now I'm seriously tempted by the Cloudshell kit even if it's restricted to using a 2.5" laptop drive...

Actually, that begs the question, "or is it?" Could the SATA bridge that's included in the kit be used to connect up to a desktop 3.5" drive, assuming I can get external power into it?

I've got one other question: the assembly instructions and pictures on the Cloudshell page seem to show the 2nd USB3 port being effectively lost. Is there a way to route a cable into the box without drilling holes in the case?

Sorry... just one other thing. The Cloudshell has a screen that looks quite like another iteration of the ODROID SHOW. Is this the case? If so, I assume that it's Arduino-compatible and fully programmable? I don't see any buttons on the outside, though, so I assume that the only way to control the box (short of attaching a keyboard/mouse or connecting over the net) would be with an IR remote?
magnum_pi
 
Posts: 198
Joined: Tue Mar 05, 2013 6:37 am
languages_spoken: English, Japanese, French, Irish
ODROIDs: U2, X2, XU, U3

Re: ODROID-XU4

Unread postby tobetter » Fri Jul 17, 2015 1:55 am

magnum_pi wrote:Wow. I haven't checked on the hardkernel site for several months and now when I come back I see this. It looks like an excellent piece of kit. The cloud thingie looks like what I was trying to achieve last year with the XU3-Lite and USB3->SATA enclosure. I never got that to work, but now I'm seriously tempted by the Cloudshell kit even if it's restricted to using a 2.5" laptop drive...

Welcome back!!
Actually, that begs the question, "or is it?" Could the SATA bridge that's included in the kit be used to connect up to a desktop 3.5" drive, assuming I can get external power into it?

SATA connector is standard, same size for 2.5" and 3.5". Only the problem with 3.5" drive since it requires +5V and +12V with more currents, hence you must provide external power. For 3.5" HDD, CloudShell package is useless except the PCB with USB3.0-to-SATA bridge.

I've got one other question: the assembly instructions and pictures on the Cloudshell page seem to show the 2nd USB3 port being effectively lost. Is there a way to route a cable into the box without drilling holes in the case?

There are multiple half circles on side and rear, please look for these from part E), F) and C). It might be 5mm.
Sorry... just one other thing. The Cloudshell has a screen that looks quite like another iteration of the ODROID SHOW. Is this the case? If so, I assume that it's Arduino-compatible and fully programmable? I don't see any buttons on the outside, though, so I assume that the only way to control the box (short of attaching a keyboard/mouse or connecting over the net) would be with an IR remote?

Yes, same LCD. 320x240 resolution with ILI9340 controller. There is no button but IR receiver is included, this can work as input device. LIRC will be supported, you can register your remote with irrecord what LIRC support. The remote for C1 will be supported by default anyway, so purchase one. :D
tobetter
 
Posts: 2040
Joined: Mon Feb 25, 2013 10:55 am
Location: Republic Of Korea
languages_spoken: Korean, English
ODROIDs: X, X2, U2, U3, XU3, C1

Re: ODROID-XU4

Unread postby LiquidAcid » Fri Jul 17, 2015 2:22 am

patoberli wrote:In some countries (like here Switzerland) it's not pirating, it's legally allowed copying ;)
I just am not allowed to share the file to others. In any case, the file was not provided from me.

Uhm, no, see swiss law. The aforementioned files were created by one of the many release groups. The material is eventually distributed publicly, e.g. through open torrent trackers. So this is no reproduction for your own purpose, and also no reproduction for your inner circle of friends. In particular the reproduction was done without authorization of the copyright holders.

If the download of such reproductions is actively persecuted is a totally different question. I know that almost everyone does it, and as long as you don't upload the authorites usually don't care, but it don't think it's a smart idea for a internationally acting company like Hardkernel to blatantly admit it.
LiquidAcid
 
Posts: 1056
Joined: Fri Oct 11, 2013 11:07 pm
languages_spoken: english
ODROIDs: X2

Re: ODROID-XU4

Unread postby rooted » Fri Jul 17, 2015 2:27 am

I thought the same thing LiquidAce, best to stick with Blender Open Project files and other non-copywrite material.

We are looking out for you Hard Kernel ;)
User avatar
rooted
 
Posts: 3652
Joined: Fri Dec 19, 2014 9:12 am
Location: Gulf of Mexico, US
languages_spoken: english
ODROIDs: C1
C1+
C2
XU3 Lite
XU4
VU7+
HiFi Shield 2
Smart Power (original)

Re: ODROID-XU4

Unread postby Bingo » Fri Jul 17, 2015 3:47 am

memeka wrote:
have you seen the xu4 shifter shield? http://www.hardkernel.com/main/products ... 3556253995

got all of the pins up to 3.3/5 selectable.


He..He
I know the shifters , might even have hinted HK about them ;) , see my CPD article in the June magazine.
They are excellent , but not suitable for I2C.

But i am quite fun of FPGA/CPLD's for the moment, and while $18 is not a steep price , that would easily translate to 25€ @Pollin.
I'd use a "Blue CPLD board" just for the VHDL excersise : http://www.ebay.com/itm/181436966398

For i2c i'd give the FET xlation a go.

Bit i agree that the expansion board is neat , and might save wiring.

But $6 for a CPLD board that can do lot's of xlation and fun things, that would be my choice of weapon.

/Bingo
Bingo
 
Posts: 73
Joined: Thu Dec 04, 2014 5:46 pm
Location: Denmark
languages_spoken: english
ODROIDs: odroid-u3 & odroid-c1/c2

Re: ODROID-XU4

Unread postby magnum_pi » Fri Jul 17, 2015 5:33 am

Thanks, tobetter. On closer inspection, it seems that I could also remove the back plate where most of the connectors go if the ~5mm gap wasn't wide enough to fit a cable through. That shouldn't be a problem. I wonder if there's enough space internally to fit two USB3 cables, though. It looks like a tight fit. I'm considering either attaching an external USB3 hard drive (for more storage) or a USB3 to Gbit Ethernet dongle like the one hardkernel supplies (to turn it into a router/NAS combo). I could use the "external" USB2 port for a wifi dongle or something else.
My only problem now is saving enough spare cash for the device. It does seem like great value but my main PC is also on its way out so that has a higher priority for me right now.
Thanks again...
magnum_pi
 
Posts: 198
Joined: Tue Mar 05, 2013 6:37 am
languages_spoken: English, Japanese, French, Irish
ODROIDs: U2, X2, XU, U3

Re: ODROID-XU4

Unread postby robroy » Fri Jul 17, 2015 7:24 am

but it don't think it's a smart idea for a internationally acting company like Hardkernel to blatantly admit it.

Technically, it is just a picture of a file name, they could have named a very large text file whatever they wanted. There is no real proof of any violation ;)

Although just for safety, I recommend microwaving that eMMC module on high for 10 minutes :lol:
Rob Roy, Editor-in-Chief of ODROID Magazine (submit an article | make a donation)
User avatar
robroy
 
Posts: 3328
Joined: Mon Feb 25, 2013 2:29 am
Location: San Francisco, California
languages_spoken: English
ODROIDs: Q2, X, X2, U2, U3, XU-E, XU3, XU4, C1, C1+, C2

Re: ODROID-XU4

Unread postby fl0wtec » Fri Jul 17, 2015 9:39 pm

odroid wrote:The fan runs by temperature controlled proportionally.
If you limit the max frequency to 1Ghz from 2Ghz of A15 cores, a passive cooler can be used.


Will this bee the exact same cooler dimensions and mounting holes as the one for XU3 and U3?

Thanks!
fl0wtec
 
Posts: 18
Joined: Thu May 28, 2015 11:46 pm
languages_spoken: english
ODROIDs: C1, XU, X2, U2

Re: ODROID-XU4

Unread postby tobetter » Fri Jul 17, 2015 9:50 pm

fl0wtec wrote:
odroid wrote:The fan runs by temperature controlled proportionally.
If you limit the max frequency to 1Ghz from 2Ghz of A15 cores, a passive cooler can be used.


Will this bee the exact same cooler dimensions and mounting holes as the one for XU3 and U3?

Thanks!

Exactly same.
tobetter
 
Posts: 2040
Joined: Mon Feb 25, 2013 10:55 am
Location: Republic Of Korea
languages_spoken: Korean, English
ODROIDs: X, X2, U2, U3, XU3, C1

Re: ODROID-XU4

Unread postby piker » Sat Jul 18, 2015 11:34 am

all, a newbie here sorry.
Bought 8x XU4, 1 XU3, 1U3.

Focusing on the XU4: Bought 12x 64gb samsung Pro 90mb/80mb working on getting a ubuntu server install and need some help. The Microsd cards are having issue with IO error and USB1 error. Tried the disableuhs but no good. Tried multiple cards but same issue. tried multiple boards same issue.

Is this a XU3 issue image or ?? Need help... I have the samsung evo 64gb as well as the samsung pro 128gb. If all goes well I will buy 20+ of these boards next week and then possibly 100+ in the next month for a project we are trying...
piker
 
Posts: 8
Joined: Sat Jul 18, 2015 8:25 am
languages_spoken: english
ODROIDs: XU3, XU4, U3

Re: ODROID-XU4

Unread postby glscantlen » Sat Jul 18, 2015 11:43 am

Where is the MicroUSB OTG ?
glscantlen
 
Posts: 8
Joined: Sat Apr 18, 2015 2:27 am
languages_spoken: english
ODROIDs: XU3

Re: ODROID-XU4

Unread postby piker » Sat Jul 18, 2015 12:03 pm

no Micro USB on the XU4... 2xstd USB3 and 1x std USB2
piker
 
Posts: 8
Joined: Sat Jul 18, 2015 8:25 am
languages_spoken: english
ODROIDs: XU3, XU4, U3

Next

Return to News

Who is online

Users browsing this forum: No registered users and 1 guest