Jump to content

OrangePi Zero2 - Allwinner H616

Werner

By Werner
in Orange Pi Zero 2

 Share

Recommended Posts

Recommended

Posted by XFer012,

Ok, so let's see the steps I followed.   1. Installed Armbian Unstable for OrangePi Zero2: https://imola.armbian.com/dl/orangepizero2/nightly/Armbian_21.05.0-trunk.77_Orangepizero2_hirsute_edge_5.11.11.img.xz   2. Forced ethernet at 100 mbit/s, otherwise it did not work: added in /etc/rc.local ethtool -s eth0 speed 100 duplex full autoneg off   3. Downloaded hexdump's precompiled kernel (derived from jernej's 5.11.0rc1 kernel): https://github.com/hexd
Recommended by Werner
5

Reputation Points

Go to this post
mantouboji

mantouboji

Posted
Posted

Why did you break the DT then cause USB is lost? 

  

yaofei@wgz2:~$ dmesg | grep vcc
[    1.409536] sun50i-h616-pinctrl 300b000.pinctrl: supply vcc-ph not found, using dummy regulator
[    1.427370] sun50i-h616-pinctrl 300b000.pinctrl: supply vcc-pc not found, using dummy regulator
[    2.685538] usb1-vbus: supplied by vcc-5v
[    2.685953] sun50i-h616-r-pinctrl 7022000.pinctrl: supply vcc-pl not found, using dummy regulator
[    2.687760] vdd-cpu: supplied by vcc-5v
[    2.688515] dcdcb: supplied by vcc-5v
[    2.688763] vdd-gpu-sys: supplied by vcc-5v
[    2.689253] vdd-dram: supplied by vcc-5v
[    2.689798] vcc-eth-mmc: supplied by vcc-5v
[    2.690290] vcc-pl: supplied by vcc-5v
[    2.690747] vcc3v3-ext: supplied by vcc-5v
[    2.691288] vcc3v3-ext2: supplied by vcc-5v
[    2.691744] vcc1v8: supplied by vcc-5v
[    2.692482] bldo2: supplied by vcc-5v
[    2.692899] bldo3: supplied by vcc-5v
[    2.693335] bldo4: supplied by vcc-5v
[    2.693817] cldo1: supplied by vcc-5v
[    2.694325] cldo2: supplied by vcc-5v
[    2.694774] cldo3: supplied by vcc-5v
[    2.781685] usb_phy_generic usb_phy_generic.1.auto: supply vcc not found, using dummy regulator
[    2.788334] sun50i-h616-pinctrl 300b000.pinctrl: supply vcc-pf not found, using dummy regulator
[    3.524820] sun50i-h616-pinctrl 300b000.pinctrl: supply vcc-pi not found, using dummy regulator

 

Link to comment
Share on other sites
mantouboji

mantouboji

Posted
Posted
On 11/18/2021 at 8:10 PM, mantouboji said:

Why did you break the DT then cause USB is lost? 

  

yaofei@wgz2:~$ dmesg | grep vcc
[    1.409536] sun50i-h616-pinctrl 300b000.pinctrl: supply vcc-ph not found, using dummy regulator
[    1.427370] sun50i-h616-pinctrl 300b000.pinctrl: supply vcc-pc not found, using dummy regulator
[    2.685538] usb1-vbus: supplied by vcc-5v
[    2.685953] sun50i-h616-r-pinctrl 7022000.pinctrl: supply vcc-pl not found, using dummy regulator
[    2.687760] vdd-cpu: supplied by vcc-5v
[    2.688515] dcdcb: supplied by vcc-5v
[    2.688763] vdd-gpu-sys: supplied by vcc-5v
[    2.689253] vdd-dram: supplied by vcc-5v
[    2.689798] vcc-eth-mmc: supplied by vcc-5v
[    2.690290] vcc-pl: supplied by vcc-5v
[    2.690747] vcc3v3-ext: supplied by vcc-5v
[    2.691288] vcc3v3-ext2: supplied by vcc-5v
[    2.691744] vcc1v8: supplied by vcc-5v
[    2.692482] bldo2: supplied by vcc-5v
[    2.692899] bldo3: supplied by vcc-5v
[    2.693335] bldo4: supplied by vcc-5v
[    2.693817] cldo1: supplied by vcc-5v
[    2.694325] cldo2: supplied by vcc-5v
[    2.694774] cldo3: supplied by vcc-5v
[    2.781685] usb_phy_generic usb_phy_generic.1.auto: supply vcc not found, using dummy regulator
[    2.788334] sun50i-h616-pinctrl 300b000.pinctrl: supply vcc-pf not found, using dummy regulator
[    3.524820] sun50i-h616-pinctrl 300b000.pinctrl: supply vcc-pi not found, using dummy regulator

 

not DTB, there are must some errors in USB driver. 

Link to comment
Share on other sites
ArkhanLK

ArkhanLK

Posted
Posted

Hello! 

I know this is for H616 and things are on early stages... But I read somewhere that the H313 is the same chip as H616, so I am wondering: would the images and procedure for H616 work on a H313 board? I don't have one yet to test, but I am planning on getting and trying. Just wondering if someone else has done it.

 

Thanks and best!

Link to comment
Share on other sites
jernej

jernej

Posted
Posted
1 hour ago, ArkhanLK said:

would the images and procedure for H616 work on a H313 board?

In theory, yes. As long as it has DDR3 RAM (no other RAM type is supported currently).

1 hour ago, ArkhanLK said:

Just wondering if someone else has done it.

Not to my knowledge.

1
Link to comment
Share on other sites
hexdump

hexdump

Posted
Posted

@ArkhanLK - i played around with an h313 x96q box - it was working as well as a h616 box, but maybe the h313 are the lower quality ones as i was not able to reach as high cpu clocks with it like with h616 and it also got hotter - so maybe h313 are the lower quality binned versions of the h616 (similar to rk3318 vs rk3328 for rockchip)

 

best wishes - hexdump

1
Link to comment
Share on other sites
ArkhanLK

ArkhanLK

Posted
Posted
On 12/3/2021 at 7:04 PM, hexdump said:

so maybe h313 are the lower quality binned versions of the h616 (similar to rk3318 vs rk3328 for rockchip)

Yeah, that's exactly what I have learned. But like, I have a rk3229 which can run things but it is very slow. Best performance "fix" is to have a 800x600 resolution. I am struggling to navigate on web, watch youtube at 480p is FAR from great... The mediaframework stuff is mostly to have the accelaration for Kodi, it doesn't helped that much with regular usage. On top of it, most of google stuff won't work (no google meet and google drive is pretty slow). Nor will any video chat platform really work, even if audio only. I am trying to make it into a cheap basic computer, mostly for productivity. 

Anyways, I'm hoping the H313 will be better just enough that these things won't be terrible. It can be bad, but hopefully work and it's not a trash performance. But I'm prepared for the same possible outcome, lol

 

On 12/3/2021 at 7:04 PM, hexdump said:

best wishes - hexdump

Thanks <3 

Link to comment
Share on other sites
pim

pim

Posted
Posted
On 11/4/2021 at 4:53 PM, Jelmer said:

Hi Guys,

 

The orangepi zero2 is an amazing powerfull sbc, I'm glad everything works as expected for me on this board (docker, domoticz, deconz, pihole etc).

 

But, I have 1 strange entry (every second) in the syslog, it logs this usually about 10 to 60 times an hour.

kernel: [69795.396748] sdiohal:sdiohal_cp_sleep_wakeup entry

 

Does anyobody know what to do, I researched it but found 0 results, I do know it has something to do with my sd-card i/o ?

I'm running Armbian 21.08.3 Buster with Linux 4.9.280-sun50iw9

 

I noticed some u-boot failing to upgrade after a apt-get upgrade before it happened, probably a reinstall removes the error but i'm just curious how to handle this.

hi Jelmer,

 

Would you please tell me how you got docker working on the orangepi zero2 i cant get it to work with armbian buster. it fails at install something to do with network issues iptables im not an expert.

i tried everything i could think off but dont get it working even after fresh install armbian it wont correctly install docker.

 

thanks for helping.

 

Pim

Link to comment
Share on other sites
krachlatte

krachlatte

Posted
Posted

hi guys, 

 

this morning after upgrading the uboot image to (22.02.0-trunk.0005)

 

=> boot
switch to partitions #0, OK
mmc0 is current device
Scanning mmc 0:1...
Found U-Boot script /boot/boot.scr
2612 bytes read in 3 ms (849.6 KiB/s)
## Executing script at 4fc00000
U-boot loaded from SD
Boot script loaded from mmc
180 bytes read in 3 ms (58.6 KiB/s)
No FDT memory address configured. Please configure
the FDT address via "fdt addr <address>" command.
Aborting!
No FDT memory address configured. Please configure
the FDT address via "fdt addr <address>" command.
Aborting!
No FDT memory address configured. Please configure
the FDT address via "fdt addr <address>" command.
Aborting!
No FDT memory address configured. Please configure
the FDT address via "fdt addr <address>" command.
Aborting!
No FDT memory address configured. Please configure
the FDT address via "fdt addr <address>" command.
Aborting!
No FDT memory address configured. Please configure
the FDT address via "fdt addr <address>" command.
Aborting!
No FDT memory address configured. Please configure
the FDT address via "fdt addr <address>" command.
Aborting!
12373835 bytes read in 518 ms (22.8 MiB/s)
Failed to load '/boot/uImage'
Wrong Image Format for bootm command
ERROR: can't get kernel image!
SCRIPT FAILED: continuing...
libfdt fdt_check_header(): FDT_ERR_BADMAGIC
BootOrder not defined
EFI boot manager: Cannot load any image
BOOTP broadcast 1
BOOTP broadcast 2
DHCP client bound to address 192.168.x.yz (1901 ms)
*** ERROR: `serverip' not set
Cannot autoload with TFTPGET
missing environment variable: pxeuuid
Retrieving file: pxelinux.cfg/01-02-00-15-7f-b0-f4
*** ERROR: `serverip' not set
Retrieving file: pxelinux.cfg/C0A80837
*** ERROR: `serverip' not set
Retrieving file: pxelinux.cfg/C0A8083
*** ERROR: `serverip' not set
Retrieving file: pxelinux.cfg/C0A808
*** ERROR: `serverip' not set
Retrieving file: pxelinux.cfg/C0A80
*** ERROR: `serverip' not set
Retrieving file: pxelinux.cfg/C0A8
*** ERROR: `serverip' not set
Retrieving file: pxelinux.cfg/C0A
*** ERROR: `serverip' not set
Retrieving file: pxelinux.cfg/C0
*** ERROR: `serverip' not set
Retrieving file: pxelinux.cfg/C
*** ERROR: `serverip' not set
Retrieving file: pxelinux.cfg/default-arm-sunxi-sunxi
*** ERROR: `serverip' not set
Retrieving file: pxelinux.cfg/default-arm-sunxi
*** ERROR: `serverip' not set
Retrieving file: pxelinux.cfg/default-arm
*** ERROR: `serverip' not set
Retrieving file: pxelinux.cfg/default
*** ERROR: `serverip' not set
Config file not found

 

 

any idea on how to fix this ?

 

many thanks and best regards

Link to comment
Share on other sites
krachlatte

krachlatte

Posted
Posted
vor 5 Stunden schrieb krachlatte:

hi guys, 

 

this morning after upgrading the uboot image to (22.02.0-trunk.0005)

 

=> boot
switch to partitions #0, OK
mmc0 is current device
Scanning mmc 0:1...
Found U-Boot script /boot/boot.scr
2612 bytes read in 3 ms (849.6 KiB/s)
## Executing script at 4fc00000
U-boot loaded from SD
Boot script loaded from mmc
180 bytes read in 3 ms (58.6 KiB/s)
No FDT memory address configured. Please configure
the FDT address via "fdt addr <address>" command.
Aborting!
No FDT memory address configured. Please configure
the FDT address via "fdt addr <address>" command.
Aborting!
No FDT memory address configured. Please configure
the FDT address via "fdt addr <address>" command.
Aborting!
No FDT memory address configured. Please configure
the FDT address via "fdt addr <address>" command.
Aborting!
No FDT memory address configured. Please configure
the FDT address via "fdt addr <address>" command.
Aborting!
No FDT memory address configured. Please configure
the FDT address via "fdt addr <address>" command.
Aborting!
No FDT memory address configured. Please configure
the FDT address via "fdt addr <address>" command.
Aborting!
12373835 bytes read in 518 ms (22.8 MiB/s)
Failed to load '/boot/uImage'
Wrong Image Format for bootm command
ERROR: can't get kernel image!
SCRIPT FAILED: continuing...
libfdt fdt_check_header(): FDT_ERR_BADMAGIC
BootOrder not defined
EFI boot manager: Cannot load any image
BOOTP broadcast 1
BOOTP broadcast 2
DHCP client bound to address 192.168.x.yz (1901 ms)
*** ERROR: `serverip' not set
Cannot autoload with TFTPGET
missing environment variable: pxeuuid
Retrieving file: pxelinux.cfg/01-02-00-15-7f-b0-f4
*** ERROR: `serverip' not set
Retrieving file: pxelinux.cfg/C0A80837
*** ERROR: `serverip' not set
Retrieving file: pxelinux.cfg/C0A8083
*** ERROR: `serverip' not set
Retrieving file: pxelinux.cfg/C0A808
*** ERROR: `serverip' not set
Retrieving file: pxelinux.cfg/C0A80
*** ERROR: `serverip' not set
Retrieving file: pxelinux.cfg/C0A8
*** ERROR: `serverip' not set
Retrieving file: pxelinux.cfg/C0A
*** ERROR: `serverip' not set
Retrieving file: pxelinux.cfg/C0
*** ERROR: `serverip' not set
Retrieving file: pxelinux.cfg/C
*** ERROR: `serverip' not set
Retrieving file: pxelinux.cfg/default-arm-sunxi-sunxi
*** ERROR: `serverip' not set
Retrieving file: pxelinux.cfg/default-arm-sunxi
*** ERROR: `serverip' not set
Retrieving file: pxelinux.cfg/default-arm
*** ERROR: `serverip' not set
Retrieving file: pxelinux.cfg/default
*** ERROR: `serverip' not set
Config file not found

 

 

any idea on how to fix this ?

 

many thanks and best regards

 

ther was a chane in the boot.cmd file booti has changed from booti to bootm

 

bootm ${kernel_addr_r} ${ramdisk_addr_r} ${fdt_addr_r}

 

booti ${kernel_addr_r} ${ramdisk_addr_r} ${fdt_addr_r}

Link to comment
Share on other sites
ArkhanLK

ArkhanLK

Posted
Posted

Hello o/

I have a Tanix tx6s and, as far as I could tell, there isn't much about it online on how to start armbian on it. I tried the general instructions for the orangepi zero 2 but the box just remains unbootable. 

Now, I have looked at the sunxi webpage and there is a, somewhat, set of instructions to get the bootloader and dtb properly working for this box...

I doubt it but, has anyone done/tried it?
And do you recommend a different approach?

Thanks!

Link to comment
Share on other sites
kprasadvnsi

kprasadvnsi

Posted
Posted
10 hours ago, ArkhanLK said:

Hello o/

I have a Tanix tx6s and, as far as I could tell, there isn't much about it online on how to start armbian on it. I tried the general instructions for the orangepi zero 2 but the box just remains unbootable. 

Now, I have looked at the sunxi webpage and there is a, somewhat, set of instructions to get the bootloader and dtb properly working for this box...

I doubt it but, has anyone done/tried it?
And do you recommend a different approach?

Thanks!

 

Please don't hijack this for your random TV Box. Its uses the same SoC doesn't mean we have any idea what goes into your particular TV box. There is a section for TV boxes in this forum. You can post your queries there. 

Link to comment
Share on other sites
silajim

silajim

Posted
Posted

Hi all, 

I've owned an orangepi zero 2 for quite a while now, I was running a wip build and well it was running but had old packages and kernels so I downloaded today the latest Bullseye stable build from the "official" page but it's not booting not even the red light lights up, total darkness. I tried with the focal image but it's the same. The latest Buster boots up with no problem at all, but it get's messed up by updating (restoring the boot folder fixes it, but it's a hack).

I am just  wanted to report the bug from the 2 latest stable builds. I did not try the edge builds. 

 

Thanks! 

Link to comment
Share on other sites
szabope

szabope

Posted
Posted

Hey all,

 

Anyone stuck with a non-booting bullseye after upgrading.

 

chroot into it (this one here about chrooting into an image, but should help with the sd card too https://gist.github.com/jkullick/9b02c2061fbdf4a6c4e8a78f1312a689 )

cat /var/log/apt/history.log

  ...

  armbian-config:arm64 (21.08.6, 21.11.0-trunk.85), armbian-bsp-cli-orangepizero2:arm64 (21.08.6, 21.08.8), linux-u-boot-orangepizero2-legacy:arm64 (21.08.6, 21.08.8)

  ...

You can find the old packages in /var/cache/apt/archives

then

dpkg -i armbian-config_21.08.6_all.deb armbian-bsp-cli-orangepizero2_21.08.6_arm64.deb linux-u-boot-orangepizero2-legacy_21.08.6_arm64.deb

 

This fixed my OS.

 

Hope this helps.

Link to comment
Share on other sites
Capeschae

Capeschae

Posted
Posted

Tested the latest builds (21.08 Bullseye and Focal) on a virgin OrangePi Zero 2 and they are not booting at all.

The Armbian_21.08.1_Orangepizero2_buster_legacy_4.9.280.img.xz from the archive boots properly.

 

An interesting observation was that Etcher (Windows 10) took an extremely long time to decompress the new image (noticed this with the Bullseye image). It finally did and flashed the image to the SD-card but these images do not boot at all. Even the red light on the board won't light.

When using Etcher to flash the Buster image everything was proceeding swiftly, as expected.

Link to comment
Share on other sites
krachlatte

krachlatte

Posted
Posted
vor 6 Stunden schrieb Werner:

I have my doubts that an image made for H2+ SoC will boot on H616...

totalay right the 2 is missing, goole search, i have this image here, its not in the archive anymore.

 

Armbian_21.08.1_Orangepizero2_hirsute_edge_5.13.12.img.xz

 

https://armbian.hosthatch.com/archive/orangepizero2/archive/Armbian_21.08.1_Orangepizero2_hirsute_edge_5.13.12.img.xz

 

 

 

Link to comment
Share on other sites
krachlatte

krachlatte

Posted
Posted

This image boots fine, reboot does work too

 

Armbian_21.08.9_Orangepizero2_focal_edge_5.15.11.img.xz

 

this image not showing anything on console  Armbian_22.02.0-trunk.0023_Orangepizero2_jammy_edge_5.15.18.img

 

 

 

 

Link to comment
Share on other sites
Hervé Changue

Hervé Changue

Posted
Posted
11 hours ago, krachlatte said:

This image boots fine, reboot does work too

 

Armbian_21.08.9_Orangepizero2_focal_edge_5.15.11.img.xz

 

this image not showing anything on console  Armbian_22.02.0-trunk.0023_Orangepizero2_jammy_edge_5.15.18.img

 

Hello did you try supported images from website?? (24 jan) i can't make it work i got nothing thanks

Link to comment
Share on other sites
Guest
This topic is now closed to further replies.
 Share
Go to topic listing
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines

  I accept