39 39
constantius

Orangepi 3 h6 allwiner chip

Recommended Posts

46 minutes ago, Werner said:

Check top for load. With 3.10.65 image it stabilizes at 3 which means three of four cores are permanently under full load which also explains the temperature issues. Did not test on OPi3 though as I do not have one but on OPi1+ which comes with H6 as well. 4.17 with initial support for H6 fixed this for me.

Oh my, I didn't notice. It's even worse than you describe! I left for half an hour the OPi3 idling and its load average is around 7, with cfinteractive taking 100% of the CPU...
I managed to compile the kernel from https://github.com/orangepi-xunlong/OrangePiH6_Linux4.9 but now I have to figure out how to convert the image to u-boot format (this u-boot thing is new to me).

@krachlatte did you receive your board? I'd like to help with testing but the instruction here: https://github.com/krachlatte/armbian-orangepi3/blob/master/README.md are not clear to me.

I'll try with the latest image from https://github.com/krachlatte/armbian-orangepi3/releases/

Share this post


Link to post
Share on other sites

I just received OPI 3 2G + 8G EMMC and trying your image.

 

I flashed following image

https://github.com/krachlatte/armbian-orangepi3/releases/download/v0.11/v0.11_Armbian_5.76_Orangepi3_Ubuntu_bionic_dev_4.20.12.img.bz2

 

HDMI was on until Loading Kernel written on screen then red power light illuminated. I waited nearly 1 hour but nothing happened.  What is the meaning of ages as objective? :) 

 

I will try to help by attaching logs but can someone basicly provide info about how to do it?

 

Note : Image file Armbian_5.59.180824_Orangepioneplus_Ubuntu_bionic_dev_4.18.0-rc7 successfully booted with HDMI & w/o network

 

Share this post


Link to post
Share on other sites
(edited)

Here is the outputs

 

U-Boot says 

 

Err:   vidconsole
Net:   No ethernet found.

 

Can someone put HDMI related lines of Armbian_5.59.180824_Orangepioneplus_Ubuntu_bionic_dev_4.18.0-rc7 to OPI3 image? Isn't that much easy?

Spoiler

 


U-Boot SPL 2018.09-rc1-armbian (Feb 28 2019 - 21:27:18 +0100)
DRAM: 2048 MiB
Trying to boot from MMC1
NOTICE:  BL31: v2.0(debug):64503b2
NOTICE:  BL31: Built : 21:26:49, Feb 28 2019
NOTICE:  BL31: Detected Allwinner H6 SoC (1728)
NOTICE:  BL31: Found U-Boot DTB at 0xc070f88, model: OrangePi 3
INFO:    ARM GICv2 driver initialized
NOTICE:  PMIC: Probing AXP805
NOTICE:  PMIC: AXP805 detected
INFO:    BL31: Platform setup done
INFO:    BL31: Initializing runtime services
INFO:    BL31: cortex_a53: CPU workaround for 855873 was applied
INFO:    BL31: Preparing for EL3 exit to normal world
INFO:    Entry point address = 0x4a000000
INFO:    SPSR = 0x3c9


U-Boot 2018.09-rc1-armbian (Feb 28 2019 - 21:27:18 +0100) Allwinner Technology

CPU:   Allwinner H6 (SUN50I)
Model: OrangePi 3
DRAM:  2 GiB
MMC:   SUNXI SD/MMC: 0, SUNXI SD/MMC: 1
Loading Environment from FAT... *** Warning - bad CRC, using default environment

Failed (-5)
Using device 'sun50i_dw_hdmi', disp_uc_priv=00000000b9f33320
fb=be000000, size=1920 1080
In:    serial
Out:   vidconsole
Err:   vidconsole
Net:   No ethernet found.
starting USB...
No controllers found
Hit any key to stop autoboot:  0
switch to partitions #0, OK
mmc0 is current device
Scanning mmc 0:1...
Found U-Boot script /boot/boot.scr
3042 bytes read in 13 ms (228.5 KiB/s)
## Executing script at 4fc00000
U-boot loaded from SD
Boot script loaded from mmc
165 bytes read in 10 ms (15.6 KiB/s)
19138 bytes read in 35 ms (533.2 KiB/s)
4155 bytes read in 44 ms (91.8 KiB/s)
Applying kernel provided DT fixup script (sun50i-h6-fixup.scr)
## Executing script at 44000000
8821549 bytes read in 908 ms (9.3 MiB/s)
14422024 bytes read in 1471 ms (9.3 MiB/s)
## Loading init Ramdisk from Legacy Image at 4fe00000 ...
   Image Name:   uInitrd
   Image Type:   AArch64 Linux RAMDisk Image (gzip compressed)
   Data Size:    8821485 Bytes = 8.4 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
## Flattened Device Tree blob at 4fa00000
   Booting using the fdt blob at 0x4fa00000
   Loading Ramdisk to 49796000, end 49fffaed ... OK
   reserving fdt memory region: addr=4fa00000 size=6b000
   Loading Device Tree to 0000000049728000, end 0000000049795fff ... OK
Setting up simplefb
Cannot setup simplefb: node not found

Starting kernel ...


Ubuntu 18.04.2 LTS orangepi3 ttyS0

orangepi3 login:



root@orangepi3:~# tail -n 100 /var/log/syslog
Feb 28 20:46:37 localhost NetworkManager[760]: <info>  [1551386797.7472] policy: auto-activating connection 'Wired connection 1'
Feb 28 20:46:37 localhost kernel: [   17.700395] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
Feb 28 20:46:37 localhost NetworkManager[760]: <info>  [1551386797.7508] device (eth0): Activation: starting connection 'Wired connection 1' (564d0e86-3f22-3ab9-855f-bb171bb11410)
Feb 28 20:46:37 localhost NetworkManager[760]: <info>  [1551386797.7516] device (eth0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Feb 28 20:46:37 localhost NetworkManager[760]: <info>  [1551386797.7522] manager: NetworkManager state is now CONNECTING
Feb 28 20:46:37 localhost NetworkManager[760]: <info>  [1551386797.7536] device (eth0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Feb 28 20:46:37 localhost NetworkManager[760]: <info>  [1551386797.7548] device (eth0): state change: config -> failed (reason 'config-failed', sys-iface-state: 'managed')
Feb 28 20:46:37 localhost NetworkManager[760]: <info>  [1551386797.7556] manager: NetworkManager state is now DISCONNECTED
Feb 28 20:46:37 localhost NetworkManager[760]: <warn>  [1551386797.7566] device (eth0): Activation: failed for connection 'Wired connection 1'
Feb 28 20:46:37 localhost kernel: [   17.708840] platform 5020000.ethernet eth0: Could not attach to PHY
Feb 28 20:46:37 localhost kernel: [   17.708854] platform 5020000.ethernet eth0: stmmac_open: Cannot attach to PHY (error: -19)
Feb 28 20:46:37 localhost NetworkManager[760]: <info>  [1551386797.8391] device (eth0): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed')
Feb 28 20:46:37 localhost kernel: [   17.794194] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
Feb 28 20:46:37 localhost NetworkManager[760]: <info>  [1551386797.8447] policy: auto-activating connection 'Wired connection 1'
Feb 28 20:46:37 localhost NetworkManager[760]: <info>  [1551386797.8484] device (eth0): Activation: starting connection 'Wired connection 1' (564d0e86-3f22-3ab9-855f-bb171bb11410)
Feb 28 20:46:37 localhost NetworkManager[760]: <info>  [1551386797.8492] device (eth0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Feb 28 20:46:37 localhost NetworkManager[760]: <info>  [1551386797.8498] manager: NetworkManager state is now CONNECTING
Feb 28 20:46:37 localhost NetworkManager[760]: <info>  [1551386797.8511] device (eth0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Feb 28 20:46:37 localhost NetworkManager[760]: <info>  [1551386797.8520] device (eth0): state change: config -> failed (reason 'config-failed', sys-iface-state: 'managed')
Feb 28 20:46:37 localhost NetworkManager[760]: <info>  [1551386797.8527] manager: NetworkManager state is now DISCONNECTED
Feb 28 20:46:37 localhost kernel: [   17.806182] platform 5020000.ethernet eth0: Could not attach to PHY
Feb 28 20:46:37 localhost kernel: [   17.806196] platform 5020000.ethernet eth0: stmmac_open: Cannot attach to PHY (error: -19)
Feb 28 20:46:37 localhost NetworkManager[760]: <warn>  [1551386797.8537] device (eth0): Activation: failed for connection 'Wired connection 1'
Feb 28 20:46:37 localhost NetworkManager[760]: <info>  [1551386797.8554] device (eth0): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed')
Feb 28 20:46:37 localhost kernel: [   17.810496] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
Feb 28 20:46:37 localhost NetworkManager[760]: <info>  [1551386797.8616] policy: auto-activating connection 'Wired connection 1'
Feb 28 20:46:37 localhost NetworkManager[760]: <info>  [1551386797.8648] device (eth0): Activation: starting connection 'Wired connection 1' (564d0e86-3f22-3ab9-855f-bb171bb11410)
Feb 28 20:46:37 localhost NetworkManager[760]: <info>  [1551386797.8656] device (eth0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Feb 28 20:46:37 localhost NetworkManager[760]: <info>  [1551386797.8663] manager: NetworkManager state is now CONNECTING
Feb 28 20:46:37 localhost NetworkManager[760]: <info>  [1551386797.8676] device (eth0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Feb 28 20:46:37 localhost NetworkManager[760]: <info>  [1551386797.8686] device (eth0): state change: config -> failed (reason 'config-failed', sys-iface-state: 'managed')
Feb 28 20:46:37 localhost NetworkManager[760]: <info>  [1551386797.8693] manager: NetworkManager state is now DISCONNECTED
Feb 28 20:46:37 localhost kernel: [   17.822695] platform 5020000.ethernet eth0: Could not attach to PHY
Feb 28 20:46:37 localhost kernel: [   17.822708] platform 5020000.ethernet eth0: stmmac_open: Cannot attach to PHY (error: -19)
Feb 28 20:46:37 localhost NetworkManager[760]: <warn>  [1551386797.8705] device (eth0): Activation: failed for connection 'Wired connection 1'
Feb 28 20:46:37 localhost NetworkManager[760]: <info>  [1551386797.8724] device (eth0): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed')
Feb 28 20:46:37 localhost kernel: [   17.827538] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
Feb 28 20:46:37 localhost NetworkManager[760]: <info>  [1551386797.8779] policy: auto-activating connection 'Wired connection 1'
Feb 28 20:46:37 localhost NetworkManager[760]: <info>  [1551386797.8811] device (eth0): Activation: starting connection 'Wired connection 1' (564d0e86-3f22-3ab9-855f-bb171bb11410)
Feb 28 20:46:37 localhost NetworkManager[760]: <info>  [1551386797.8819] device (eth0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Feb 28 20:46:37 localhost NetworkManager[760]: <info>  [1551386797.8825] manager: NetworkManager state is now CONNECTING
Feb 28 20:46:37 localhost NetworkManager[760]: <info>  [1551386797.8839] device (eth0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Feb 28 20:46:37 localhost NetworkManager[760]: <info>  [1551386797.8849] device (eth0): state change: config -> failed (reason 'config-failed', sys-iface-state: 'managed')
Feb 28 20:46:37 localhost kernel: [   17.839025] platform 5020000.ethernet eth0: Could not attach to PHY
Feb 28 20:46:37 localhost kernel: [   17.839037] platform 5020000.ethernet eth0: stmmac_open: Cannot attach to PHY (error: -19)
Feb 28 20:46:37 localhost NetworkManager[760]: <info>  [1551386797.8855] manager: NetworkManager state is now DISCONNECTED
Feb 28 20:46:37 localhost NetworkManager[760]: <warn>  [1551386797.8866] device (eth0): Activation: failed for connection 'Wired connection 1'
Feb 28 20:46:37 localhost NetworkManager[760]: <info>  [1551386797.8882] device (eth0): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed')
Feb 28 20:46:37 localhost kernel: [   17.843231] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
Feb 28 20:46:37 localhost NetworkManager[760]: <info>  [1551386797.8942] manager: startup complete
Feb 28 20:46:37 localhost systemd[1]: Started Network Manager Wait Online.
Feb 28 20:46:37 localhost systemd[1]: Reached target Network is Online.
Feb 28 20:46:37 localhost systemd[1]: Starting LSB: Advanced IEEE 802.11 management daemon...
Feb 28 20:46:37 localhost systemd[1]: Starting /etc/rc.local Compatibility...
Feb 28 20:46:37 localhost systemd[1]: Started LSB: Advanced IEEE 802.11 management daemon.
Feb 28 20:46:37 localhost systemd[1]: Started /etc/rc.local Compatibility.
Feb 28 20:46:37 localhost systemd[1]: Started Getty on tty1.
Feb 28 20:46:37 localhost systemd[1]: Started Serial Getty on ttyS0.
Feb 28 20:46:37 localhost systemd[1]: Reached target Login Prompts.
Feb 28 20:46:37 localhost systemd[1]: Reached target Multi-User System.
Feb 28 20:46:37 localhost systemd[1]: Reached target Graphical Interface.
Feb 28 20:46:37 localhost systemd[1]: Starting Update UTMP about System Runlevel Changes...
Feb 28 20:46:37 localhost systemd[1]: Started Update UTMP about System Runlevel Changes.
Feb 28 20:46:38 localhost polkitd[1369]: started daemon version 0.105 using authority implementation `local' version `0.105'
Feb 28 20:46:38 localhost dbus-daemon[694]: [system] Successfully activated service 'org.freedesktop.PolicyKit1'
Feb 28 20:46:38 localhost systemd[1]: Started Authorization Manager.
Feb 28 20:46:38 localhost systemd[1]: Startup finished in 6.782s (kernel) + 11.409s (userspace) = 18.192s.
Feb 28 20:46:44 localhost systemd[1]: Reloading.
Feb 28 20:46:45 localhost systemd[1]: Starting resolvconf-pull-resolved.service...
Feb 28 20:46:45 localhost systemd[1]: Started resolvconf-pull-resolved.service.
Feb 28 20:46:45 localhost systemd[1]: Reloading.
Feb 28 20:46:45 localhost systemd[1]: Starting resolvconf-pull-resolved.service...
Feb 28 20:46:45 localhost systemd[1]: Started resolvconf-pull-resolved.service.
Feb 28 20:46:45 localhost systemd[1]: Stopping OpenBSD Secure Shell server...
Feb 28 20:46:45 localhost systemd[1]: Stopped OpenBSD Secure Shell server.
Feb 28 20:46:45 localhost systemd[1]: Starting OpenBSD Secure Shell server...
Feb 28 20:46:45 localhost systemd[1]: Started OpenBSD Secure Shell server.
Feb 28 20:46:46 localhost systemd[1]: Stopping OpenBSD Secure Shell server...
Feb 28 20:46:46 localhost systemd[1]: Stopped OpenBSD Secure Shell server.
Feb 28 20:46:46 localhost systemd[1]: Starting OpenBSD Secure Shell server...
Feb 28 20:46:46 localhost systemd[1]: Started OpenBSD Secure Shell server.
Feb 28 20:46:46 localhost armbian-firstrun[764]: Removed /etc/systemd/system/multi-user.target.wants/armbian-firstrun.service.
Feb 28 20:46:46 localhost systemd[1]: Reloading.
Feb 28 20:46:46 localhost systemd[1]: Starting resolvconf-pull-resolved.service...
Feb 28 20:46:46 localhost systemd[1]: Started resolvconf-pull-resolved.service.
Feb 28 20:48:19 localhost systemd[1]: Created slice User Slice of root.
Feb 28 20:48:19 localhost systemd[1]: Starting User Manager for UID 0...
Feb 28 20:48:19 localhost systemd[1]: Started Session 1 of user root.
Feb 28 20:48:20 localhost systemd[1868]: Reached target Paths.
Feb 28 20:48:20 localhost systemd[1868]: Listening on GnuPG cryptographic agent (ssh-agent emulation).
Feb 28 20:48:20 localhost systemd[1868]: Reached target Timers.
Feb 28 20:48:20 localhost systemd[1868]: Listening on GnuPG cryptographic agent and passphrase cache (restricted).
Feb 28 20:48:20 localhost systemd[1868]: Listening on GnuPG network certificate management daemon.
Feb 28 20:48:20 localhost systemd[1868]: Listening on GnuPG cryptographic agent and passphrase cache (access for web browsers).
Feb 28 20:48:20 localhost systemd[1868]: Listening on GnuPG cryptographic agent and passphrase cache.
Feb 28 20:48:20 localhost systemd[1868]: Reached target Sockets.
Feb 28 20:48:20 localhost systemd[1868]: Reached target Basic System.
Feb 28 20:48:20 localhost systemd[1868]: Reached target Default.
Feb 28 20:48:20 localhost systemd[1868]: Startup finished in 206ms.
Feb 28 20:48:20 localhost systemd[1]: Started User Manager for UID 0.



root@orangepi3:~# ifconfig -a
lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 1000  (Local Loopback)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

root@orangepi3:~# ethtool eth0
Settings for eth0:
Cannot get device settings: Device or resource busy
Cannot get wake-on-lan settings: Device or resource busy
Cannot get message level: Device or resource busy
Cannot get link status: Device or resource busy
No data available


root@orangepi3:~# lsmod
Module                  Size  Used by
zstd                   16384  4
cpufreq_dt             16384  0
sun50i_h6_ths          16384  0
thermal_sys            65536  2 cpufreq_dt,sun50i_h6_ths
zram                   24576  5
hid_logitech_hidpp     28672  0
hid_logitech_dj        20480  0
dwc3_of_simple         16384  0

 

Edited by Tido
added spoiler - for better reading, please do that yourself next time. thx

Share this post


Link to post
Share on other sites
(edited)

If I add

 

/etc/network/interfaces.d/eth0

 

auto lo eth0

allow-hotplug eth0

iface eth0 inet dhcp

hwaddress ether **************

 

It stucks at Starting kernel ...

 

after 6 min it successfully booted still without network

Edited by obenturk
Update

Share this post


Link to post
Share on other sites
3 hours ago, hojnikb said:

a second working sbc can also double as a serial adapter.

Brilliant idea!! 

I attached an arduino to the OPi3 serial port with an old cdrom audio connector (where I moved a pin in order to have three adjacent pins connected) and three male-male pin cables, now I can see the output :thumbup:

Share this post


Link to post
Share on other sites
On 2/28/2019 at 9:35 PM, krachlatte said:

v0.11 released and available for download

 

This is the serial port output when booting v0.11:

 

Spoiler

U-Boot SPL 2018.09-rc1-armbian (Feb 28 2019 - 21:27:18 +0100)
DRAM: 2048 MiB
Trying to boot from MMC1

NOTICE:  BL31: v2.0(debug):64503b2
NOTICE:  BL31: Built : 21:26:49, Feb 28 2019
NOTICE:  BL31: Detected Allwinner H6 SoC (1728)
NOTICE:  BL31: Found U-Boot DTB at 0xc070f88, model: OrangePi 3
INFO:    ARM GICv2 driver initialized
NOTICE:  PMIC: Probing AXP805
NOTICE:  PMIC: AXP805 detected
INFO:    BL31: Platform setup done
INFO:    BL31: Initializing runtime services
INFO:    BL31: cortex_a53: CPU workaround for 855873 was applied
INFO:    BL31: Preparing for EL3 exit to normal world
INFO:    Entry point address = 0x4a000000
INFO:    SPSR = 0x3c9


U-Boot 2018.09-rc1-armbian (Feb 28 2019 - 21:27:18 +0100) Allwinner Technology

CPU:   Allwinner H6 (SUN50I)
Model: OrangePi 3
DRAM:  2 GiB
MMC:   SUNXI SD/MMC: 0, SUNXI SD/MMC: 1
Loading Environment from FAT... Unable to use mmc 1:1... Failed (-5)
Using device 'sun50i_dw_hdmi', disp_uc_priv=00000000b9f33320
sunxi_de3_init: device 'sunxi_de3' display won't probe (ret=-1)
Using device 'sun50i_dw_hdmi', disp_uc_priv=00000000b9f33320
sunxi_de3_init: device 'sunxi_de3' display won't probe (ret=-1)
In:    serial
Out:   serial
Err:   serial
Net:   No ethernet found.
starting USB...
No controllers found
Hit any key to stop autoboot:  1 0
=> MMC:   SUNXI SD/MMC: 0, SUNXI SD/MMC: 1
Unknown command 'MMC:' - try 'help'
=> 
Unknown command 'MMC:' - try 'help'
=> Loading Environment from FAT... Unable to use mmc 1:1... Failed (-5)
Unknown command 'Loading' - try 'help'
=> 
Unknown command 'Loading' - try 'help'
=> Using device 'sun50i_dw_hdmi', disp_uc_priv=00000000b9f33320
Unknown command 'Using' - try 'help'
=> 
Unknown command 'Using' - try 'help'
=> sunxi_de3_init: device 'sunxi_de3' display won't probe (ret=-1)

> Using device 'sun5 
Unknown command 'sunxi_de3_init:' - try 'help'
=> => MMC:   SUNXI SD/MMC: 0, SUNXI SD/MMC
Unknown command '=>' - try 'help'
=> 
Unknown command '=>' - try 'help'
=> => Loading Environment from FAT... Unable to use mmc 1:1... Failed (
Unknown command '=>' - try 'help'
=> 
Unknown command '=>' - try 'help'
=> => Using device 'sun50i_dw_hdmi', disp_uc_priv=00000000b9f33
Unknown command '=>' - try 'help'
=> 
Unknown command '=>' - try 'help'
=> => sunxi_de3_init: device 'sunxi_de3' display won't probe (ret=


> > Using device 'su
Unknown command '=>' - try 'help'
=> => => MMC:   SUNXI SD/MMC: 0, SUNXI SD/
Unknown command '=>' - try 'help'
=> 
Unknown command '=>' - try 'help'
=> => => Loading Environment from FAT... Unable to use mmc 1:1... Faile
Unknown command '=>' - try 'help'
=> 
Unknown command '=>' - try 'help'
=> => => Using device 'sun50i_dw_hdmi', disp_uc_priv=00000000b9
Unknown command '=>' - try 'help'
=> 
Unknown command '=>' - try 'help'
=> => => sunxi_de3_init: device 'sunxi_de3' display won't probe (r



> > > Using device 
> => => => MMC:   SUNXI SD/MMC: 0, SUNXI 

> => => => Loading Environment from FAT... Unable to use mmc 1:1... Fa

> => => => Using device 'sun50i_dw_hdmi', disp_uc_priv=0000000

> => => => sunxi_de3_init: device 'sunxi_de3' display won't probe
Unknown command '=>' - try 'help'
=> 
Unknown command '=>' - try 'help'
=> 
Unknown command '=>' - try 'help'
=> 
Unknown command '=>' - try 'help'
=> 
Unknown command '=>' - try 'help'
=> > > > Using devi
Unknown command '>' - try 'help'
=> 
Unknown command '>' - try 'help'
=> > => => => MMC:   SUNXI SD/MMC: 0, SUN
Unknown command '>' - try 'help'
=> 
Unknown command '>' - try 'help'
=> 
Unknown command '>' - try 'help'
=> > => => => Loading Environment from FAT... Unable to use mmc 1:1...
Unknown command '>' - try 'help'
=> 
Unknown command '>' - try 'help'
=> 
Unknown command '>' - try 'help'
=> > => => => Using device 'sun50i_dw_hdmi', disp_uc_priv=0000
Unknown command '>' - try 'help'
=> 
Unknown command '>' - try 'help'
=> 
Unknown command '>' - try 'help'
=> > => => => sunxi_de3_init: device 'sunxi_de3' display won't pr




> => > > > Using d

> => > => => => MMC:   SUNXI SD/MMC: 0, 


> => > => => => Loading Environment from FAT... Unable to use mmc 1:1


> => > => => => Using device 'sun50i_dw_hdmi', disp_uc_priv=0


> => > => => => sunxi_de3_init: device 'sunxi_de3' display won't
Unknown command '>' - try 'help'
=> 
Unknown command '>' - try 'help'
=> 
Unknown command '>' - try 'help'
=> 
Unknown command '>' - try 'help'
=> 
Unknown command '>' - try 'help'
=> 
Unknown command '>' - try 'help'
=> > => > > > Usin
Unknown command '>' - try 'help'
=> 
Unknown command '>' - try 'help'
=> 
Unknown command '>' - try 'help'
=> > => > => => => MMC:   SUNXI SD/MMC: 
Unknown command '>' - try 'help'
=> 
Unknown command '>' - try 'help'
=> 
Unknown command '>' - try 'help'
=> 
Unknown command '>' - try 'help'
=> > => > => => => Loading Environment from FAT... Unable to use mmc 
Unknown command '>' - try 'help'
=> 
Unknown command '>' - try 'help'
=> 
Unknown command '>' - try 'help'
=> 
Unknown command '>' - try 'help'
=> > => > => => => Using device 'sun50i_dw_hdmi', disp_uc_pri
Unknown command '>' - try 'help'
=> 
Unknown command '>' - try 'help'
=> 
Unknown command '>' - try 'help'
=> 
Unknown command '>' - try 'help'mand '=>' - try 'help'
=> => => => > => > => => => MMC:   SUNXI
Unknown command '=>' - try 'help'
=> 
Unknown command '=>' - try 'help'
=> 
Unknown command '=>' - try 'help'
=> 
Unknown command '=>' - try 'help'
=> => => => > => > => => => Loading Environment from FAT... Unable to
Unknown command '=>' - try 'help'
=> 
Unknown command '=>' - try 'help'
=> 
Unknown command '=>' - try 'help'
=> 
Unknown command '=>' - try 'help'
=> => => => > => > => => => Using device 'sun50i_dw_hdmi', di
Unknown command '=>' - try 'help'
=> 
Unknown command '=>' - try 'help'
=> 
Unknown command '=>' - try 'help'
=> 
Unknown command '=>' - try 'help'
=> => => => > => > => => => sunxi_de3_init: device 'sunxi_de3' d
Unknown command '=>' - try 'help'
=> 
Unknown command '=>' - try 'help'
=> 
Unknown command '=>' - try 'help'
=> 
Unknown command '=>' - try 'help'
=> 
Unknown command '=>' - try 'help'
=> 
Unknown command '=>' - try 'help'
=> => => => => > =
Unknown command '=>' - try 'help'
=> 
Unknown command '=>' - try 'help'
=> 
Unknown command '=>' - try 'help'
=> => => => => > => > => => => MMC:   SU
Unknown command '=>' - try 'help'
=> 
Unknown command '=>' - try 'help'
=> 
Unknown command '=>' - try 'help'
=> 
Unknown command '=>' - try 'help'
=> => => => => > => > => => => Loading Environment from FAT... Unable
Unknown command '=>' - try 'help'
=> 
Unknown command '=>' - try 'help'
=> 
Unknown command '=>' - try 'help'
=> 
Unknown command '=>' - try 'help'
=> => => => => > => > => => => Using device 'sun50i_dw_hdmi',
Unknown command '=>' - try 'help'
=> 
Unknown command '=>' - try 'help'
=> 
Unknown command '=>' - try 'help'
=> 
Unknown command '=>' - try 'help'
=> => => => => > => > => => => sunxi_de3_init: device 'sunxi_de3





> => => => => => 


> => => => => => > => > => => => MMC:  



> => => => => => > => > => => => Loading Environment from FAT... Una



> => => => => => > => > => => => Using device 'sun50i_dw_hdm
Unknown command '=>' - try 'help'
=> 
Unknown command '=>' - try 'help'
=> 
Unknown command '=>' - try 'help'
=> 
Unknown command '=>' - try 'help'
=> => => => => => > => > => => => sunxi_de3_init: device 'sunxi_






> > => => => => 



> > => => => => => > => > => => => MMC




> > => => => => => > => > => => => Loading Environment from FAT... 




> > => => => => => > => > => => => Using device 'sun50i_dw_
Unknown command '=>' - try 'help'
=> 
Unknown command '=>' - try 'help'
=> 
Unknown command '=>' - try 'help'
=> 
Unknown command '=>' - try 'help'
=> => => => => => => > => > => => => sunxi_de3_init: device 'sun







> > > => => => 




> > > => => => => => > => > => => => 





> > > => => => => => > => > => => => Loading Environment from FAT.





> > > => => => => => > => > => => => Using device 'sun50i_
Unknown command '=>' - try 'help'
=> 
Unknown command '=>' - try 'help'
=> 
Unknown command '=>' - try 'help'
=> 
Unknown command '=>' - try 'help'
=> => => => => => => => > => > => => => sunxi_de3_init: device '








> > > > => => 





> > > > => => => => => > => > => => 






> > > > => => => => => > => > => => => Loading Environment from F






> > > > => => => => => > => > => => => Using device 'sun5
Unknown command '=>' - try 'help'
=> 
Unknown command '=>' - try 'help'
=> 
Unknown command '=>' - try 'help'
=> 
Unknown command '=>' - try 'help'
=> => => => => => => => => > => > => => => sunxi_de3_init: devic
Unknown command '=>' - try 'help'
=> 
Unknown command '=>' - try 'help'
=> 
Unknown command '=>' - try 'help'
=> 
Unknown command '=>' - try 'help'
=> 
Unknown command '=>' - try 'help'
=> 
Unknown command '=>' - try 'help'
=> 
Unknown command '=>' - try 'help'
=> 
Unknown command '=>' - try 'help'
=> 
Unknown command '=>' - try 'help'
=> 
Unknown command '=>' - try 'help'
=> > > > > => 
Unknown command '>' - try 'help'
=> 
Unknown command '>' - try 'help'
=> 
Unknown command '>' - try 'help'
=> 
Unknown command '>' - try 'help'
=> 
Unknown command '>' - try 'help'
=> 
Unknown command '>' - try 'help'
=> 
Unknown command '>' - try 'help'
=> > > > > =>   









 


And then goes on like this

Share this post


Link to post
Share on other sites

I see in the download notes that there is a MAC address issue and I have also experienced it with my testing. Is this a hardware issue or is it on the OS side of things?  I also had something similar with the aml-s905x-cc and I seem to remember I partially fixed it by hard-defining a MAC address.

 

If it's on the Armbian side of things I will just wait for the stable build to release but otherwise I would like to fix it if I can.

 

Also, does anybody have a recommended heatsink size or even a specific amazon listing they can point to?

Share this post


Link to post
Share on other sites
1 hour ago, datsuns said:

Also, does anybody have a recommended heatsink size or even a specific amazon listing they can point to?

 

Heatsinks for the Raspberry Pi will work, although ~1mm small. Copper > aluminum in my experience. Check out AliExpress or eBay

Share this post


Link to post
Share on other sites
(edited)
On 3/3/2019 at 4:49 PM, obenturk said:

Here is the outputs

 

U-Boot says 

 

Err:   vidconsole
Net:   No ethernet found.

 

Can someone put HDMI related lines of Armbian_5.59.180824_Orangepioneplus_Ubuntu_bionic_dev_4.18.0-rc7 to OPI3 image? Isn't that much easy?

 


U-Boot SPL 2018.09-rc1-armbian (Feb 28 2019 - 21:27:18 +0100)
DRAM: 2048 MiB
Trying to boot from MMC1
NOTICE:  BL31: v2.0(debug):64503b2
NOTICE:  BL31: Built : 21:26:49, Feb 28 2019
NOTICE:  BL31: Detected Allwinner H6 SoC (1728)
NOTICE:  BL31: Found U-Boot DTB at 0xc070f88, model: OrangePi 3
INFO:    ARM GICv2 driver initialized
NOTICE:  PMIC: Probing AXP805
NOTICE:  PMIC: AXP805 detected
INFO:    BL31: Platform setup done
INFO:    BL31: Initializing runtime services
INFO:    BL31: cortex_a53: CPU workaround for 855873 was applied
INFO:    BL31: Preparing for EL3 exit to normal world
INFO:    Entry point address = 0x4a000000
INFO:    SPSR = 0x3c9


U-Boot 2018.09-rc1-armbian (Feb 28 2019 - 21:27:18 +0100) Allwinner Technology

CPU:   Allwinner H6 (SUN50I)
Model: OrangePi 3
DRAM:  2 GiB
MMC:   SUNXI SD/MMC: 0, SUNXI SD/MMC: 1
Loading Environment from FAT... *** Warning - bad CRC, using default environment

Failed (-5)
Using device 'sun50i_dw_hdmi', disp_uc_priv=00000000b9f33320
fb=be000000, size=1920 1080
In:    serial
Out:   vidconsole
Err:   vidconsole
Net:   No ethernet found.
starting USB...

 

did you try to do an insmod realtek, because here it is missing

 

still did not receive the ornagepi 3 to do tests.

 

Edited by Tido
shorted quote - for better reading

Share this post


Link to post
Share on other sites
45 minutes ago, krachlatte said:

did you try to do an insmod realtek, because here it is missing

 

still did not receive the ornagepi 3 to do tests.

 

Curious, did you get a shipping update yet? I'll try your image as well if I can figure out my serial drivers

Share this post


Link to post
Share on other sites
(edited)

I tried modprobe realtek

then

/etc/init.d/networking restart
 

root@orangepi3:~# ifup eth0
ifup: waiting for lock on /run/network/ifstate.eth0

Nothing happens I need to stop it ctrl+z

 

root@orangepi3:~# ifconfig -a
eth0: flags=4098<BROADCAST,MULTICAST>  mtu 1500
        ether 72:d6:05:4f:b9:3b  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
        device interrupt 17

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 1000  (Local Loopback)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
 

 

Edited by obenturk
I forget to add with Armbian_5.59.180824_Orangepioneplus_Ubuntu_bionic_dev_4.18.0-rc7 network lights are illuminating even w/o networking but with your image no lights

Share this post


Link to post
Share on other sites

@Krachlatte v0.11 ubuntu work USB and works with a usb-ethernet
I have compiled the image of debian with your patches but usb does not work. What changes are necessary for the USB?

Share this post


Link to post
Share on other sites
18 hours ago, max-cldx said:

@Krachlatte v0.11 ubuntu work USB and works with a usb-ethernet
I have compiled the image of debian with your patches but usb does not work. What changes are necessary for the USB?

does that mean usb not working in v0.11 ?

 

still waiting for the package to arive

Share this post


Link to post
Share on other sites
(edited)

I have watched this thread and decided to check the status of the mainline kernel 5.0 for the H6 with the @Icenowy 's work on top of it.

I can say it works really nice (tested on Orange Pi 3 H6):

* HDMI

* DVFS

* Gbps / ethernet

 

I have prepared a blindly DT that should work on Opi 3 H6: https://github.com/avafinger/orangepi-h6-ubuntu-base-minimal/tree/master/dts

 @Igor , Basically fetch the mainline kernel 5, apply your patch set on top and add/modify my DT.

 

I have tried to add i2c and spi but it did not work as i expected.

I had something like this:

For the i2c

        i2c0: i2c@5002000 {
            compatible = "allwinner,sun6i-a31-i2c";
            reg = <0x05002000 0x400>;
            interrupts = <GIC_SPI 4 IRQ_TYPE_LEVEL_HIGH>;
            clocks = <&ccu CLK_BUS_I2C0>;
            resets = <&ccu RST_BUS_I2C0>;
            status = "disabled";
            #address-cells = <1>;
            #size-cells = <0>;
        };

        i2c1: i2c@5002400 {
            compatible = "allwinner,sun6i-a31-i2c";
            reg = <0x05002400 0x400>;
            interrupts = <GIC_SPI 5 IRQ_TYPE_LEVEL_HIGH>;
            clocks = <&ccu CLK_BUS_I2C1>;
            resets = <&ccu RST_BUS_I2C1>;
            status = "disabled";
            #address-cells = <1>;
            #size-cells = <0>;
        };
            i2c0_pins: i2c0_pins {
                pins = "PH5", "PH6";
                function = "i2c0";
            };

            i2c1_pins: i2c1_pins {
                pins = "PD25", "PD26";
                function = "i2c1";
            };

Default i2c in use (PMIC and possibly HDMI):

ls /dev/i2c-*
/dev/i2c-0  /dev/i2c-1

i2cdetect -y 0
     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
00:          -- -- -- -- -- -- -- -- -- -- -- -- -- 
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
30: -- -- -- -- -- -- UU -- -- -- -- -- -- -- -- -- 
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
70: -- -- -- -- -- -- -- --                         
i2cdetect -y 1
     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
00:          -- -- -- -- -- -- -- -- -- -- -- -- -- 
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
30: 30 -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
50: 50 51 52 53 54 55 56 57 -- -- -- -- -- -- -- -- 
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
70: -- -- -- -- -- -- -- --          

 

For the SPI0:

 

        spi0: spi@5010000 {
            compatible = "allwinner,sun8i-h3-spi";
            reg = <0x05010000 0x1000>;
            interrupts = <GIC_SPI 10 IRQ_TYPE_LEVEL_HIGH>;
            clocks = <&ccu CLK_BUS_SPI0>, <&ccu CLK_SPI0>;
            clock-names = "ahb", "mod";
            dmas = <&dma 23>, <&dma 23>;
            dma-names = "rx", "tx";
            pinctrl-names = "default";
            pinctrl-0 = <&spi0_pins>;
            resets = <&ccu RST_BUS_SPI0>;
            status = "disabled";
            num-cs = <1>;
            #address-cells = <1>;
            #size-cells = <0>;
        };
            spi0_pins: spi0 {
                pins = "PC0", "PC2", "PC3", "PC5";
                function = "spi0";
            };

One thing i noticed was some instability on SD card but resorting to 4.19-rc6 clk values fixed it.

 

Regarding the reboot command, i applied the latest ATF power fix (as suggested by @jernej but reboot works exactly as shutdown -h now

Edited by @lex
reboot issue

Share this post


Link to post
Share on other sites
42 minutes ago, @lex said:

I have tried to add i2c and spi but it did not work as i expected.

In which way ? your i2c tests seems to work, right ?

42 minutes ago, @lex said:

Regarding the reboot command, i applied the latest ATF power fix (as suggested by @jernej but reboot works exactly as shutdown -h now

We still have to figure out where is the issue ... In another thread, I've mentioned that PineH64, with the same Armbian scripts, does reboot properly, while OrangePiOnePlus doesn't ...

 

Share this post


Link to post
Share on other sites

I suspect there might be some issue with PMIC, like improper voltage set to some regulator... I noticed also some clock issues, which I'll investigate.

Share this post


Link to post
Share on other sites
51 minutes ago, martinayotte said:

In which way ? your i2c tests seems to work, right ?

The printed info above (i2cdetect -y 0/1) is from the stock kernel, as soon as i added the i2c entries i2c gets lazy and do not detect the device i attach on PH6 and PH5 (Orange Pi One Plus).

I added:

&i2c0_pins {
    bias-pull-up;
};

just in case. No success.:unsure:

SPI seems to be in the right direction, i tried to drive ili9341 display but kernel complains PC5 is already in use, so i gave up for now.

 

Share this post


Link to post
Share on other sites
(edited)
40 minutes ago, jernej said:

issue with PMIC, like improper voltage set to some regulator

Possible, do you mean u-boot? I am using old u-boot with old values,  will re-check and see if it changes something. Thanks for the tip.

Edited by @lex
no regulators on u-boot

Share this post


Link to post
Share on other sites

Forgot to print the dma used:

 

         dma: dma-controller@3002000 {
            compatible = "allwinner,sun50i-a64-dma";
            reg = <0x03002000 0x1000>;
            interrupts = <GIC_SPI 43 IRQ_TYPE_LEVEL_HIGH>;
            clocks = <&ccu CLK_BUS_DMA>;
            dma-channels = <8>;
            dma-requests = <27>;
            resets = <&ccu RST_BUS_DMA>;
            #dma-cells = <1>;
        };

 

Share this post


Link to post
Share on other sites
8 minutes ago, @lex said:

Forgot to print the dma used: 

 


         dma: dma-controller@3002000 {
            compatible = "allwinner,sun50i-a64-dma";
            reg = <0x03002000 0x1000>;
            interrupts = <GIC_SPI 43 IRQ_TYPE_LEVEL_HIGH>;
            clocks = <&ccu CLK_BUS_DMA>;
            dma-channels = <8>;
            dma-requests = <27>;
            resets = <&ccu RST_BUS_DMA>;
            #dma-cells = <1>;
        };

 

 

That won't fly. DMA is not the same as in A64. But fear not, I have patches which I plan to send soon (just before I2S stuff): https://github.com/jernejsk/linux-1/commits/h6_i2s

Share this post


Link to post
Share on other sites
47 minutes ago, jernej said:

improper voltage set to some regulator.

These are the changes from H64 and OpiOne+

 

@@ -161,6 +155,7 @@
                 regulator-min-microvolt = <3300000>;
                 regulator-max-microvolt = <3300000>;
                 regulator-name = "vcc-ac200";
+                regulator-enable-ramp-delay = <100000>;
             };
 
             reg_aldo3: aldo3 {
@@ -219,7 +214,7 @@
             reg_dcdca: dcdca {
                 regulator-always-on;
                 regulator-min-microvolt = <810000>;
-                regulator-max-microvolt = <1160000>;
+                regulator-max-microvolt = <1080000>;
                 regulator-name = "vdd-cpu";
             };
 
 

Share this post


Link to post
Share on other sites
Just now, @lex said:

BTW Do you have mali working on your kernel?

Yes, with proprietary userspace blobs. Yesterday I posted initial LibreELEC PineH64 image, so most important things from my perspective already work, although not stable yet.

Share this post


Link to post
Share on other sites

BTW, newest U-Boot (2019.01) is the most optimal choice for H6. It correctly detects and sets boards with 3 GiB of RAM. It also has some DRAM stability fixes. The only thing you would lose is simplefb HDMI driver, but Linux 5.0 has initial H6 DRM driver anyway. OrangePi DTs don't have HDMI/DE/TCON nodes, but it should be easy to add them (copy over from PineH64). I didn't do it just because I don't have any OrangePi with H6 for testing.

Share this post


Link to post
Share on other sites
48 minutes ago, jernej said:

OrangePi DTs don't have HDMI/DE/TCON node

The opi3-h6.dts i pointed to already have all the nodes. HDMI works like a charm. Those who will try need to compile the kernel with Wifi and BT enabled.

I synced the regulators with H64 but that does not fix the reboot issue.

 

I just noticed the power ON/OFF button works, maybe the H64 does not have this button?

 

Do you have any suggestion about i2c? 

I will use your dma code and see if i get SPI0 to work.

Share this post


Link to post
Share on other sites
3 minutes ago, @lex said:

The opi3-h6.dts i pointed to already have all the nodes. HDMI works like a charm.

Can you please send that patch upstream? There is no reason to hold it up and you would lower patch count when using newer versions of kernel.

 

5 minutes ago, @lex said:

I just noticed the power ON/OFF button works, maybe the H64 does not have this button?

I didn't pay attention to that functionality.

 

6 minutes ago, @lex said:

Do you have any suggestion about i2c? 

I will use your dma code and see if i get SPI0 to work.

No suggestions about I2C or SPI. Maybe just compare registers if they are the same and on same addresses, if you plan to use some non-H6 compatible string.

Share this post


Link to post
Share on other sites
2 hours ago, jernej said:

Can you please send that patch upstream?

Err... Just don't know how to do that... In a proper way I mean.

Share this post


Link to post
Share on other sites
39 39