Jump to content

Recommended Posts

Posted

According to apritzel OPI zero2 has - unsupported Allwinner WiFi/BT chip

The firmware of the wifi seems to be available here. The schematics of WiFi/BT are available here

If I understand correctly, we need a pr for the firmware and a patch(overlay?) of the upcoming DT provided by apritzel.

Is anyone skilled enough to write a patch for the DT?

Posted
  On 7/20/2021 at 4:48 PM, lampra said:

Is anyone skilled enough to write a patch for the DT?

Expand  


I trade my skills for help on tasks that doesn't require so much skills, but they still require time and attention.
https://forum.armbian.com/forum/54-help-wanted/

 

Currently working on sunxi bump to 5.13.y but since I am on vacations, my wife can interrupt this violently :D;) If time permits, I'll try to fix this, but can't promise.

Posted
  On 7/20/2021 at 4:48 PM, lampra said:

According to apritzel OPI zero2 has - unsupported Allwinner WiFi/BT chip

The firmware of the wifi seems to be available here. The schematics of WiFi/BT are available here

If I understand correctly, we need a pr for the firmware and a patch(overlay?) of the upcoming DT provided by apritzel.

Is anyone skilled enough to write a patch for the DT?

Expand  

Hi,

 

I'm new to this thing, but I did some digging.

 

There's a possibility that the AW859A is either a rebadged UWE5622, or is compatible with it. There's also a reference to a device, that is SC2355.

 

I only managed to find a little info about the UWE5622, and it might have some connections to Unisoc, a yet another Chinese fabless semiconductor maker, but not sure. You can get a bit more info by googling, including the name of some binary file.

Posted

Is there any way to get an image output out from the board currently? I would like to help with testing at least, but currently I don't have a UART cable, only a monitor with an HDMI input, and an old CRT TV (which would be good if it had a reason to stay with me for at least a bit longer, like for testing :) ).

Posted
  On 7/24/2021 at 3:06 PM, ZILtoid1991 said:

Hi,

 

I'm new to this thing, but I did some digging.

 

There's a possibility that the AW859A is either a rebadged UWE5622, or is compatible with it. There's also a reference to a device, that is SC2355.

 

I only managed to find a little info about the UWE5622, and it might have some connections to Unisoc, a yet another Chinese fabless semiconductor maker, but not sure. You can get a bit more info by googling, including the name of some binary file.

Expand  

Here is the Datasheet for AW859A

CDW-20U5622-02_SPECIFICATIONS_20200306(全志专用AW859A).pdfFetching info...

Posted

https://github.com/armbian/build/pull/2620/files

We have more or less fully functional image with legacy kernel, but 5.13.y hangs at:

 

  Reveal hidden contents

@jernej Do you know latest working combination (atf / u-boot / kernel) ?

Posted

Hasn't ATF been mainlined already? Also U-Boot master received necessary changes already IIRC. Linux sources from apritzel are most up-to-date AFAIK with h616-v9 branch or whatever number he is currently working on.

Posted
  On 8/12/2021 at 4:01 AM, Werner said:

Hasn't ATF been mainlined already? Also U-Boot master received necessary

Expand  


Yes, we are attached to mainline ATF and u-boot. Probably kernel is the problem. 

Posted
  On 8/14/2021 at 8:16 PM, lampra said:

Then this should probably point to the mainline ATF source.

Expand  


Nice catch, I must have forget about that.

 

I am unable to test if that helps at least by the end of this week.

Posted
  On 8/12/2021 at 4:01 AM, Werner said:

Linux sources from apritzel are most up-to-date AFAIK with h616-v9 branch or whatever number he is currently working on.

Expand  

Latest versions are actually less featureful because it's easier to merge series if there is less patches and thus more consensus how to do things. I can't tell which is the most featureful branch from the top of my head, probably v6 or v7. Certainly last variant contain no USB support.

Posted
  On 8/15/2021 at 8:14 PM, Igor said:

I am unable to test if that helps at least by the end of this week.

Expand  

Tested after changing ATF to mainline master, and it's loading the kernel. Ethernet and usb also working http://ix.io/3woR

To me, it seems that we need to stick to 5.13 (which  includes all the patches) for a while, as the discussion for the mainline support is far from concluded.

Posted
  On 8/19/2021 at 12:15 AM, lampra said:

5.13

Expand  

Yeah, would also not make much sense to backport those to 5.10 since 5.15 will probably be next LTS release and is only a few month ahead and probably will include those patches already.

Posted

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.

Posted
  On 8/26/2021 at 12:07 PM, mantouboji said:

How long will it take to boot properly?

Expand  

I expect within a day and eternity or never. You could as well ask a clairvoyant.
This is the only board using this SoC. So not that much development for it. Things are evolving. But no idea if it will ever be a good board for everyone.
So only for the brave for now. I'm also waiting and watching for good news about it. Hardware wise it's an ok board. But not worth buying.

Posted
  On 8/28/2021 at 9:21 AM, mantouboji said:

I tried,can't pass build

Expand  

This is what I did here

ATFSOURCE='https://github.com/ARM-software/arm-trusted-firmware'
ATFBRANCH='branch:master'

edit: You also need all the patches (for h616 and opz2). I did not check if the patches are present or not in armbian master, as I had included them in previous builds. If not, you need to include them. 

Posted
  On 8/28/2021 at 9:27 AM, lampra said:

This is what I did here

ATFSOURCE='https://github.com/ARM-software/arm-trusted-firmware'
ATFBRANCH='branch:master'

edit: You also need all the patches (for h616 and opz2). I did not check if the patches are present or not in armbian master, as I had included them in previous builds. If not, you need to include them. 

Expand  

where did you get those H616 patches?

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

Important Information

Terms of Use - Privacy Policy - Guidelines