Werner

Armbian has now the new OrangePi3 WIP !
WiFi and eMMC tested ...
 

Hi everyone !
 
I'm starting this new dedicated thread because I've got some new headache about this issue that we tried to figured out since months...
 
I've received my PineH64 last week, and with this board I don't faced the reboot hang behaviour !
 
Today, since I've committed the OPi3 WIP scripts, and facing same reboot hang, I've decided to to try booting PineH64 image on this OPi3 board, but unfortunately reboot hang still occurs ...
 
This brings me to a conclusion that it is not a software issue, but maybe hardware one ... I will dig on that during next few days by comparing PMIC and other between all those boards ...
 
But I remember that @jernej said that Reboot worked on one of his H6 board ...
@jernej can you confirm which board ? Do you have some boards where you still face reboot hang issue ? Can you try to mix image like I did to give clues ?
 
 
 

I've just installed it, and first impression is, it isn't much better than before.
It's unstable. Runs at 1.5Ghz, but seems a lot slower than others at the same speed. 1.8Ghz isn't possible anymore.
Temperatures are of course better now.
Here a 7zip benchmark with stock settings.
orangepi@OrangePi:~$ 7z b 7-Zip 9.20 Copyright (c) 1999-2010 Igor Pavlov 2010-11-18 p7zip Version 9.20 (locale=C,Utf16=off,HugeFiles=on,4 CPUs) RAM size: 1980 MB, # CPU hardware threads: 4 RAM usage: 850 MB, # Benchmark threads: 4 Dict Compressing | Decompressing Speed Usage R/U Rating | Speed Usage R/U Rating KB/s % MIPS MIPS | KB/s % MIPS MIPS 22: 1667 286 567 1622 | 35573 263 1218 3209 23: 1766 313 575 1800 | 45386 344 1206 4153 24: 1704 315 581 1832 | 44655 345 1200 4142 25: 1547 299 591 1767 | 38169 302 1189 3589 ---------------------------------------------------------------- Avr: 303 578 1755 314 1203 3773 Tot: 308 891 2764 It performs very badly. 2/3 of what it should be at 1.5Ghz.
I've then set the governor to performance and everything starts to lag like crazy. 7-zip results are very bad.
 
orangepi@OrangePi:~$ sudo cpufreq-set -g performance orangepi@OrangePi:~$ 7z b 7-Zip 9.20 Copyright (c) 1999-2010 Igor Pavlov 2010-11-18 p7zip Version 9.20 (locale=C,Utf16=off,HugeFiles=on,4 CPUs) RAM size: 1980 MB, # CPU hardware threads: 4 RAM usage: 850 MB, # Benchmark threads: 4 Dict Compressing | Decompressing Speed Usage R/U Rating | Speed Usage R/U Rating KB/s % MIPS MIPS | KB/s % MIPS MIPS 22: 551 85 628 536 | 10925 82 1209 985 23: 566 89 647 577 | 11939 90 1214 1092 24: 506 83 658 545 | 11711 90 1208 1086 25: 529 89 676 604 | 11491 90 1197 1080 ---------------------------------------------------------------- Avr: 87 652 565 88 1207 1061 Tot: 87 930 813  

I believe the temperature isn't showing right. It shows it's constantly at 55°C at idle, and above 60°C when in use. But the heatsink isn't even hot to the touch. It feels very cool. This can't be right.
Must be something wrong with the temperature sensor settings.

No auto-resize either. I'll try updating to bionic.

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

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 

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.

I've received mine today ... Thanks to Humberg !
I've built an Armbian 4.20.y image this afternoon, it boot fine, but no eth0 or WiFi, but I got networking using USB-WiFi dongle.
For RTL8723, I've tried adding it in DT, but it still not appearing ... It is difficult to figure out without schematic, and schematic doesn't seems to be public yet ...
I've posted on forum.pine64.org asking for that schematic, but no answer yet ...
 
EDIT : Forgot to mention, "reboot" is working fine on this H6 board, I don't experience freezing found with other H6s ...

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/

First off, this happens on x86. Google "rowhammer" if you think that this kind of situation isn't a problem even for "expensive" computers.
 
 
Xunlong never advertised the Orange Pi Zero as an AP! Please, show me where they said "use the Orange Pi Zero as a WiFi router"
 
Even the cheapest WiFi routers that I know of cost $15 (AR9331/MT7620).
 
This is additional functionality that we've been lucky to get from the WiFi radio, and now people are getting all pissed that it doesn't work as well as a Raspberry Pi.
 
In my country, the Orange Pi Zero costs as much as a hamburger meal from McDonalds. Just try and use your hamburger as an AP...
 
Fack, people. Lower your expectations.

Oh ! I've found that Armbian build for H6 exceptionally using https://github.com/Icenowy/u-boot , which is pretty old, that could be that, I will try u-boot mainstream ...
 
EDIT : Mainstream U-Boot doesn't seems to be enough ...

https://github.com/leeboby/OrangePiH6_Linux4.9

@lanefu will help around admin duties.

Anyone can add announcement, but moderators decide whether its worth to approve it. If there will be too much, this will be limited only to staff and developers.

to WIP forums (RK3399 & H6) header to make it more clear about the support level.

Thank you very much @martinayotte !

It works like a charm! We're able to communicate with an external device.

We will try and see what's going on in the sun4i-i2s driver.

Again great job martinayotte, thank you!

Edit: Donated a little bit of money, it would be nice that others looking for help would do the same.

well Let's try it in a 'markdown' way, where #category ## forum ###subforum.
 
#Announcements & first aid
   ## Annoucements (e.g. someone steps back, someone gets maintainership, new major release - only certain people can post here)
   ## Board doesn't boot
      ### Hall of Shame aka SD-Card and PSU related issues
#Bugtracker/ Armbian related issues
   ## Allwinner A20
   ## Allwinner H2 & H3
   ## Allwinner H5 & A64
   ## [WIP] Allwinner H6
   ## Armada A388, A3700
   ## Amlogic S905(x)
   ## NXP (Freescale)
   ## Rockchip 3288 & 3328
   ## [WIP] Rockchip 3399
   ## Other supported boards
 
#Community forums
   ## P2P tech support
      ### Debian/Ubuntu or general Linux related issues
      ### Hardware Hacks
      ### Unsupported boards
   ## From users for users
      ### Reviews
      ### Research guides and tutorials
   ## TV boxes
   ## Chitchat
   ## trash
# Development
   ## Board bring up
   ## Armbian build framework
   ## Features development (here should stuff be discussed which we want to fix/rewrite e.g. when nand-sata-install gets reworked etc.)
 
 
development is then only a small part (but probably not in subforum after subfroum).. for development of armbian or it's buildscript.. the SoC related development threads will move into a bug-tracker since it doesn't matter if it's a bug for a supported platform or not.. we want it fixed in the end.. the wip marked forums will just have a polite remember what wip means.. Maybe we could kill all subforums to have it more clear..

Unlikely. It's a problem with their kernel. We don't use Debian kernel - it's way too old, but I will pay attentions to upstream changes in this area. 

I got the things working !
Although I didn't tested it with real SPI device, I've at least tested it with loopback wire between MISO/MOSI and executed spidev_test ...
https://github.com/armbian/build/commit/34205e60b3efa0ef3acc293ed9e02b801f8a52c1
 

Which boards?

as give away .... for developing  ... to support the ARMBIAN Project
 
;-)
 
Have fun! 
Feel free to contact me:
   post@humberg.de

Do you mean you have some spares to give away ?
Maybe I could be interested ...

Hello community,
 
I got some brand new Pine H64 Model B this week.
Anyone interested in a free test device?
 
Markus

There are a few differences between both boards. It's like saying that an Audi car is the same as a BMW because they have the same engine(I know nothing about cars).

I've got the PineH64 model B here, but I don't have a complete overview of the specs yet.
What I can say is OPi has LPDDR3 ram up to 2GB, while the PINE H64 has got LPDDR4 up to 3GB.
The OPi has got room for a smd eMMC module, while the Pine has got a eMMC socket so you can remove it.
The OPi has got 4xUSB3.0 ports while the Pine64 only has one USB3 + 2 USB2 ports. I don't know if there is only on USB3 root hub or multiple. So could be that the 4xUSB3 on the OPi are just over the same hub what makes both OPi/Pine as fast.
The Opi also has got USB2.0. The Pine H64 is a lot more compact.
 
It is way too early to say if these boards will have good support for everything you want. You'd be better buy something that's know to have all that instead of one of these. It will take months, and it is to see how many people want to develop for it.
For now all I have is a very badly working Android image, and a Armbian Bionic that only works when I dissable all networking. But that's not very useful at all. It is a very nice board tho. 9/10 for looks
The OPi is also on the way, should have been here a while ago. But they didn't send before Chinese Newyear, so only this week it's departed. Great I've got the PineH64 now. (thank you @Humberg )

Proposed actions:
 
1. Renaming section "Technical support" to "Bug tracker" (leave restrictions as is)
2. Merging "Common issues" with "Peer to peer" and place under "Community forums" section
3. Creating new section "First aid" 
    - move "SD card and power supply"
    - create "Board doesn't boot"    
    
    or move "SD card and power supply" one level up and rename to "Board doesn't boot"    
 
Alternatively:
4. Make "armbianmonitor -u" field mandatory for "Bug tracker" section except "board doesn't boot"
5. Move NXP and Armada A388/A3700 under "Other supported boards"