Jump to content

OrangePi Zero2 - Allwinner H616


Werner

Recommended Posts

Hi all

I was tested the last image orangepi xfce 5.16 kernel released few dais back in orangepi web. 

 

But I was therified... The usage of its is 0, worst experience even whit compare to old rpi zero with desktop test. 

 

There I think is broken wifi can't conect to 2.4ghz 40mhz wide (20mhz is OK). 

 

And my question is, is there any usable kernel right now that has working h265 hw decode? 

Because in the last opi image it was impossible to play it even on sw. I have tride default player in opi image and vlc. 

 

I have plans for this board I want swap for rpi4 in multimedia home center, because lower powerconsumotion.. But still not usable...  I thin more months to wait now... :-(

Link to comment
Share on other sites

6 hours ago, DvoraNoob said:

Why my armbian don't have a Hardware option on system?

 

You mean adjusting HW features? Because there are no overlays and nobody developed them. No, we have not plans nor budget for that.

 

On 5/14/2022 at 10:33 PM, CyberDeath said:

I thin more months to wait now... 😞


We are also waiting and waiting that you realise that you need to support R&D in order to have some small rights to complain ;) 

 

This graph below shows how many days is needed before reported issues is resolved. Terrible, right? https://docs.armbian.com/User-Guide_FAQ/#development-time Remember that if you don't contribute on the project, you can't add bugs / tasks to the system at all. With another words - we have no resources not even for write bugs into the system and if we would listen to your problems, situation for the project that helps you, but you don't help it, would only be much worse.
prenos.png

 

If all people that complain and report bugs to themselves would have Angel https://forum.armbian.com/subscriptions/ we would be able to perhaps hire full time person for you that would record bugs and solve them one by one. Since this is not the case and you expect the impossible, graph can only get steeper. 

Link to comment
Share on other sites

On 4/24/2022 at 6:43 AM, mrjack said:

please help me... i learned to install ipset but the result is always the same...

 

 

How to fix...please..

 

 

 

IMG_20220424_054159.jpg

you should change kernel config (iptables and depends )to y

Link to comment
Share on other sites

On 2020/11/28 at PM6点08分, Werner said:

在抱怨问题之前,请阅读此内容!

 

tl;dr:将您的 Zero2 和/或任何其他基于 H616 的设备放在架子上,等待适当的支持。和不。没有预计到达时间。假设可用状态为 2021 年底/2022 年初。

 

软件支持仍在进行中并正在大力开发中。提供的预览图像可以随时中断。请勿举报,我们知道这一点,如果您不愿意自行调查和研究,我们可以/不会帮助您。

随时与其他开发人员一起努力创建适当的软件支持。但是不要浪费我们的时间抱怨。谢谢!

 

https://github.com/apritzel/linux/commits/h616-v5

https://github.com/jernejsk/u-boot/tree/h616-v2

https://github.com/apritzel/arm-trusted-firmware/tree/h616-v2-wip _

 

 

-------------------------------------------------- --------------------------

 

我开始玩这个板,显然失败了,创建一个基本的 Armbian 集成。

 

反正。这些是我到目前为止收集的信息:

 

旭龙图片dtb提取: https ://pastebin.com/raw/Uni2JzBF

 

橙皮监视器🙄   http://ix.io/2FM0

 

 



		

 

内核配置:https ://pastebin.com/raw/e2jTTZ7A

h616-v11 can be built success and uboot is a challange to match kernel image format from uImage to Image

 

Link to comment
Share on other sites

6 hours ago, Igor said:

 

You mean adjusting HW features? Because there are no overlays and nobody developed them. No, we have not plans nor budget for that.

 

Yes, I think is needed activate SPI HW features to add a ADXL345.

Link to comment
Share on other sites

11 hours ago, Igor said:

 

You mean adjusting HW features? Because there are no overlays and nobody developed them. No, we have not plans nor budget for that.

 


We are also waiting and waiting that you realise that you need to support R&D in order to have some small rights to complain ;) 

 

This graph below shows how many days is needed before reported issues is resolved. Terrible, right? https://docs.armbian.com/User-Guide_FAQ/#development-time Remember that if you don't contribute on the project, you can't add bugs / tasks to the system at all. With another words - we have no resources not even for write bugs into the system and if we would listen to your problems, situation for the project that helps you, but you don't help it, would only be much worse.
prenos.png

 

If all people that complain and report bugs to themselves would have Angel https://forum.armbian.com/subscriptions/ we would be able to perhaps hire full time person for you that would record bugs and solve them one by one. Since this is not the case and you expect the impossible, graph can only get steeper. 

Sorry for misunderstanding. 

I did not complain. I just state the fact and houpet that somebody will tell me otherwise.  It lays in my desk for few months so... It will lays more, no trouble... I did play meanwhile with other boards and other projects. 

 

If I take the board in cli most of the stuff works OK. It's pitti that the developer/manufacturer of the board dit not provide at least some working kernel (even old) ... 

 

But I did not get answer to the h265 so I thing it's not that easy to get it working... If even on orange pi kernel it's not working. 

Link to comment
Share on other sites

1 hour ago, CyberDeath said:

It's pitti that the developer/manufacturer of the board dit not provide at least some working kernel (even old) ...

 

They are providing old working kernel even you only paid hardware at BOM price. Not saying everything works, but for the price you pay (nothing) ... its something to boot. If you want luxury you mention before, you need to actively contribute. 

 

1 hour ago, CyberDeath said:

But I did not get answer to the h265


What is wrong with not getting an answer? 

Link to comment
Share on other sites

On 8/24/2021 at 12:37 PM, iHackFX said:

Hi, I recently received this board and I was able to get the docker started. Maybe someone may find it useful.
After installing via "armbian-confix" if try to start docker service with

$ systemctl start docker

 we get this error: 

● docker.service - Docker Application Container Engine
   Loaded: loaded (/lib/systemd/system/docker.service; enabled; vendor preset: enabled)
   Active: activating (auto-restart) (Result: exit-code) since Tue 2021-08-24 20:09:34 MSK; 26ms ago
     Docs: https://docs.docker.com
  Process: 11947 ExecStart=/usr/bin/dockerd -H fd:// --containerd=/run/containerd/containerd.sock (code=exited, status=1/FAILURE)
 Main PID: 11947 (code=exited, status=1/FAILURE)
dpkg: error handling package docker-ce (--configure):
 installed docker-ce package post-installation script subprocess returned error exit status 1

In "journalctl -xe" we get the following - "Running iptables --wait -t nat -L -n failed with message: `# Warning: iptables-legacy tables present, use iptables-legacy to see them\niptables: Operation not supported.`, error: exit status 1."
And to fix it, you need to use the following command:

$ update-alternatives --set iptables /usr/sbin/iptables-legacy

Then restart the service and docker works.

Thank you very much for sharing this! 

Link to comment
Share on other sites

Hello there.

 

I acquired this card recently, and when researching a bit more, to my surprise, I just came across the info that the h616 linux support isn't mainlined (this explain why it was so cheap).

I would like to know how close h616 is to get mainline support, what is still missing? there were some reports that device tree was missing, but some reports stating that it was added in 5.16 or something.

 

Link to comment
Share on other sites

9 hours ago, fksalamfkla said:

I would like to know how close h616 is to get mainline support, what is still missing?

Kernel 5.19 (rc1 will be released in about one week) will have all drivers, but no DT. So 5.20 will presumably have initial support, with DT included. Probably USB too. However, patches exists for most features.

Link to comment
Share on other sites

12 hours ago, fksalamfkla said:

I just came across the info that the h616 linux support isn't mainlined (this explain why it was so cheap).


That is certainly not the reason. All hardware is released with some old private / BSP / Android / presentation kernel. It always takes years to get to the mainline. Some HW never came there and never all functions gets there. This is just how this world function and Armbian is also mitigating this problem to the best possible degree. Otherwise you would be destined to much lower quality / usability and have it much later.

Welcome!

Link to comment
Share on other sites

On 5/28/2022 at 8:30 AM, jernej said:

Kernel 5.19 (rc1 will be released in about one week) will have all drivers, but no DT. So 5.20 will presumably have initial support, with DT included. Probably USB too. However, patches exists for most features.

This welcome news indeed, although its all discovery for me, personally I've been trying to get cpu frequency working 5.17.11-sunxi64. CONFIG_ARM_ALLWINNER_SUN50I_CPUFREQ_NVMEM=m and dependencies can be configured and built, however the device tree has no opp table etc

 

 opp_l_table {
                compatible = "allwinner,sun50i-operating-points";
                nvmem-cells = <0xd7>;
                nvmem-cell-names = "speed";
                opp-shared;
                linux,phandle = <0xd4>;
                phandle = <0xd4>;

 

I have so-far seen the differences in 4.9.255 cpufreq-dt.c and 5.17.5, but still have much to learn, and possibly way beyond my current comprehension state to begin solving....

Link to comment
Share on other sites

At this point I have h616-cpu-opp table parameters with which I can patch a new build, any advise from seasoned armbians welcome, there are sure to be gotchas.

 

failure points cpufreq-dt.ko

 

cpufreq_dt: 
    failed to find data for cpu%d
    failed to get clk: %d 
    no regulator for cpu%d
    failed to set regulators: %d
    OPP table can't be empty
    failed to mark OPPs as shared: %d
    failed to init cpufreq table: %d
    failed register driver: %d

Link to comment
Share on other sites

Having a crack at this but not much success!

 

alistair@orangepizero2:/boot/dtb-5.17.11-sunxi64/allwinner$ dtdiff sun50i-h616-orangepi-zero2.dts \ sun50i-h616-orangepi-zero2.dtb | grep "^+" | wc -l
Unrecognized format for  sun50i-h616-orangepi-zero2.dtb
Error: sun50i-h616-cpu-opp.dtsi:95.1-6 Label or path cpu0 not found
Error: sun50i-h616-cpu-opp.dtsi:99.1-6 Label or path cpu1 not found
Error: sun50i-h616-cpu-opp.dtsi:103.1-6 Label or path cpu2 not found
Error: sun50i-h616-cpu-opp.dtsi:107.1-6 Label or path cpu3 not found
FATAL ERROR: Syntax error parsing input tree
0
 

Link to comment
Share on other sites

Help with Bullseye, My Orange Pi was working normally, but Now I can't boot more neither if I flashing the Armbian again.

 

Serial LOG:

Spoiler

[72]HELLO! BOOT0 is starting May 13 2020 14:10:04!
[77]BOOT0 commit : 593cf83
[79]set pll start
[82]periph0 has been enabled
[85]set pll end
[86]unknow PMU
[88]PMU: AXP806
[95]vaild para:1  select dram para0
[99]board init ok
[100]DRAM BOOT DRIVE INFO: V0.52
[104]the chip id is 0x5000
[106]chip id check OK
[109]DRAM_VCC set to 1500 mv
[112]read_calibration error
[116]read_calibration error
[120]read_calibration error
[124]read_calibration error
[128]read_calibration error
[132]read_calibration error
[136]read_calibration error
[140]read_calibration error
[144]read_calibration error
[148]read_calibration error
[151]retraining final error
[155][AUTO DEBUG]32bit,1 ranks training success!
[163]DRAM CLK =720 MHZ
[165]DRAM Type =3 (3:DDR3,4:DDR4,7:LPDDR3,8:LPDDR4)
[171]Actual DRAM SIZE =1024 M
[174]DRAM SIZE =1024 MBytes, para1 = 30fa, para2 = 4000000, dram_tpr13 = 6041
[187]DRAM simple test OK.
[190]rtc standby flag is 0x0, super standby flag is 0x0
[195]dram size =1024
[197]*****dram handle ok****
[201]card no is 0
[203]sdcard 0 line count 4
[205][mmc]: mmc driver ver 2019-12-19 10:41
[210][mmc]: sdc0 spd mode error, 2
[213][mmc]: set f_max to 50M, set f_max_ddr to 25M
[218][mmc]: mmc 0 bias 0
[226][mmc]: Wrong media type 0x0
[229][mmc]: ***Try SD card 0***
[238][mmc]: HSSDR52/SDR25 4 bit
[242][mmc]: 50000000 Hz
[244][mmc]: 29508 MB
[246][mmc]: ***SD/MMC 0 init OK!!!***
[345]Loading boot-pkg Succeed(index=0).
[349]Entry_name        = u-boot
[358]Entry_name        = monitor
[362]Entry_name        = dtbo
[365]Entry_name        = dtb
[368]Jump to second Boot.
NOTICE:  BL3-1: v1.0(debug):9fecd83
NOTICE:  BL3-1: Built : 17:08:29, 2020-05-28
NOTICE:  BL3-1 commit: 8
ERROR:   Error initializing runtime service tspd_fast
NOTICE:  BL3-1: Preparing for EL3 exit to normal world
NOTICE:  BL3-1: Next image address = 0x4a000000
NOTICE:  BL3-1: Next image spsr = 0x1d3

U-Boot 2018.05-armbian (May 28 2022 - 09:09:02 +0000) Xunlong Software

[00.445]CPU:   Allwinner H616
[00.447]Model: Orange Pi Zero 2
I2C:   ready
[00.452]DRAM:  1 GiB
Relocation Offset is: 35ec7000
[00.493]secure enable bit: 0
[00.495]PMU: AXP806
[00.500]CPU=1008 MHz,PLL6=600 Mhz,AHB=200 Mhz, APB1=100Mhz  MBus=400Mhz
[00.682]sunxi overlay merged okqv
[00.686]drv_disp_init
[00.715]__clk_enable: clk is null.
tv_init()950 fetch tv0 err.
[00.720]drv_disp_init finish
[00.723]gic: sec monitor mode
[00.728]flash init start
[00.730]workmode = 0,storage type = 1
[00.734]MMC:     0
[00.735][mmc]: mmc driver ver uboot2018:2021-07-19 14:09:00
[00.741][mmc]: get sdc_type fail and use default host:tm1.
[00.752][mmc]: Using default timing para
[00.755][mmc]: SUNXI SDMMC Controller Version:0x40200
[00.773][mmc]: card_caps:0x3000000a
[00.776][mmc]: host_caps:0x3000003f
[00.780]sunxi flash init ok
[00.784]Loading Environment from FAT...
[00.787][mmc]: mmc driver ver uboot2018:2021-07-19 14:09:00
[00.793][mmc]: get sdc_type fail and use default host:tm1.
[00.804][mmc]: Using default timing para
[00.807][mmc]: SUNXI SDMMC Controller Version:0x40200
** Bad device mmc 1 **
Failed (-5)
[00.819]usb burn from boot
delay time 0
weak:otg_phy_config
[00.832]usb prepare ok
[01.635]overtime
[01.639]do_burn_from_boot usb : no usb exist
[01.643]boot_gui_init:start
141 bytes read in 14 ms (9.8 KiB/s)
Set HDMI disp_mode to 1080p60
141 bytes read in 14 ms (9.8 KiB/s)
Set fb0_width to 1280
Set fb0_height to 720
[01.956]boot_gui_init:finish
[01.959]bmp_name=/boot/boot.bmp
230454 bytes read in 37 ms (5.9 MiB/s)
[02.009]update dts
Net:   [02.012]No ethernet found.
Hit any key to stop autoboot:  0
no mmc device at slot 1
[03.039][mmc]: card_caps:0x3000000a
[03.042][mmc]: host_caps:0x3000003f
switch to partitions #0, OK
mmc0 is current device
Scanning mmc 0:1...
Found U-Boot script /boot/boot.scr
3202 bytes read in 17 ms (183.6 KiB/s)
## Executing script at 43100000
U-boot loaded from SD
Boot script loaded from mmc
141 bytes read in 13 ms (9.8 KiB/s)
262144 bytes read in 44 ms (5.7 MiB/s)
** File not found /boot/dtb/allwinner/overlay/-fixup.scr **
6995211 bytes read in 608 ms (11 MiB/s)
** File not found /boot/Image **
Unknown command 'booti' - try 'help'
SCRIPT FAILED: continuing...
No ethernet found.
missing environment variable: pxeuuid
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/00000000
No ethernet found.
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/0000000
No ethernet found.
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/000000
No ethernet found.
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/00000
No ethernet found.
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/0000
No ethernet found.
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/000
No ethernet found.
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/00
No ethernet found.
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/0
No ethernet found.
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/default-arm-sunxi
No ethernet found.
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/default-arm
No ethernet found.
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/default
No ethernet found.
Config file not found
No ethernet found.
 

 

Link to comment
Share on other sites

3 часа назад, DvoraNoob сказал:

Help with Bullseye, My Orange Pi was working normally, but Now I can't boot more neither if I flashing the Armbian again.

one my zero2 was received with the same trouble. it's looks like RAM fault. item from ali was refunded by seller without dispute after video evidence

Edited by nightguest
Link to comment
Share on other sites

5 hours ago, nightguest said:

one my zero2 was received with the same trouble. it's looks like RAM fault. item from ali was refunded by seller without dispute after video evidence

I already used Armbian on this device, I think it was the update, now I'm testing the Orange Pi official firmware

Link to comment
Share on other sites

On 1/29/2021 at 9:08 PM, Werner said:

If you really wanna do serious stuff with it do what I did: Put it on the shelf and let it sit there for about a year from now. Then come back to it.

Ok, i've done it. Put it on the shelf behind my desk and waited for much than a year. ))

And now I can only see nice words in the center of screen "armbian initializing boot loader" for more than an hour. (Reboot didn't help, alas).
May be I should read something to understand what to do next? Really don't want to wait one year more.

Link to comment
Share on other sites

1 hour ago, yar83 said:

May be I should read something to understand what to do next? Really don't want to wait one year more

Nobody wants to wait but also very few of those are a willing to do something to decrease waiting time. One year was a rough estimation. Mainline development of arm platform is very slow in comparison to x86.

For example it took several years to bring RK3399 SoC to a well matured state and still not all functions are well supported yet. Now think about how long it might take for a mid-grade SoC like H616;)

Link to comment
Share on other sites

Quote

May be I should read something to understand what to do next?

 

Well yeah its a long swim, dive in though, mainline has enough already working, from 5.20 seriously wishing that more is there to make it easier!

Link to comment
Share on other sites

39 minutes ago, Werner said:

Nobody wants to wait but also very few of those are a willing to do something to decrease waiting time. One year was a rough estimation. Mainline development of arm platform is very slow in comparison to x86.

For example it took several years to bring RK3399 SoC to a well matured state and still not all functions are well supported yet. Now think about how long it might take for a mid-grade SoC like H616;)

So what really can I do for help besides donating? Can it be that it's the right time to read Chris Simmonds's book that waited for this moment for two years exactly next to inoperative zero2.

Link to comment
Share on other sites

Good start if you have the time and use case.

 

Quote

 read Chris Simmonds's book

 

You will have to think outside the 'book' its examples are different soc.

 

Whats your use case? Is it fun or fairly serious project.

 

If it a project that you have time to put into, then effort might be justifiable, should you make some progress contribute back to the community. Otherwise keep hoping that someone else will make the effort and part with that back to community.

 

Best of luck.

Link to comment
Share on other sites

37 minutes ago, ALIGMSTEN said:

Good start if you have the time and use case.

 

 

You will have to think outside the 'book' its examples are different soc.

 

Whats your use case? Is it fun or fairly serious project.

 

If it a project that you have time to put into, then effort might be justifiable, should you make some progress contribute back to the community. Otherwise keep hoping that someone else will make the effort and part with that back to community.

 

Best of luck.

Nobody has enough time to do everything the do but as for me I want to enroll in embedded linux programming. I always had a lot of interest but never tried seriously. I wanted begin with small private project of automated garage surveillance and security system with all features like logging to remote server, mobile app and web application. And I've done almost all environment: backend, frontend, draft of mobile app, but stopped on hardware stage. So I don't see any obstacles to finish the project except inoperative device. By the way, I've done something with RPi, but it looks like cheating. I used pigpio lib to make sensors and actuators work, but still haven't managed to understand underlying mechanisms of OS.

Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines