Jump to content

Orangepi 3 h6 allwiner chip


constantius

Recommended Posts

1 hour ago, Frank Kettenbeil said:

Where are these firmware files activated or used?

Those files are loaded when the BRCM Kernel driver been started.

You can check with "dmesg | grep -i sdio" or "dmesg | grep -i brcm"

 

BTW, how did you enabled the WiFi ? Is it using /etc/network/interface or using "nmtui" ?

Link to comment
Share on other sites

Thanks for your reply - just managed to check out things now.
There are no occurences of sdio or brcm within dmesg output. I could not find any driver and therefore could not enable the wifi.
only occurence of wifi at all in dmesg output is 

[    2.087183] vcc-wifi-1: Bringing 700000uV into 3300000-3300000uV
[    2.088053] vcc-wifi-2: Bringing 700000uV into 3300000-3300000uV

I tried "blindly" with nmtui but as expected did not get any connection.

 

Link to comment
Share on other sites

2 hours ago, Frank Kettenbeil said:

There are no occurences of sdio or brcm within dmesg output.

Which kernel/image are you running ? Did you built it yourself ?

With Armbian DEV branch with 5.0.y kernel, you should clearly see the following :

[    4.213027] mmc1: new high speed SDIO card at address 0001
[    7.960498] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43455-sdio for chip BCM4345/9
[    8.088730] Bluetooth: Generic Bluetooth SDIO driver ver 0.1
[   10.181048] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43455-sdio for chip BCM4345/9
[    7.960498] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43455-sdio for chip BCM4345/9
[   10.181048] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43455-sdio for chip BCM4345/9
[   10.472854] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM4345/9 wl0: Jun 16 2017 12:38:26 version 7.45.96.2 (66c4e21@sh-git) (r) FWID 01-1813af84

 

Link to comment
Share on other sites

I do build the dev image myself using bionic desktop - actually getting Armbian_5.77_Orangepi3_Ubuntu_bionic_dev_5.0.2_desktop.

As far as I understand there seems to be some 5.0.2 kernel included with this branch - even when build interface still tells me about 4.x kernel - Am I correct?

Should I instead better pick one of the debian images? - Where in kernel config or other parts of configuration could I possibly have taken  the wrong lane?

Will it be possible for me to do kernel builds on the OPi3 itself later on - so I do not have to reconfigure everything on new version?

Link to comment
Share on other sites

6 minutes ago, Frank Kettenbeil said:

even when build interface still tells me about 4.x kernel - Am I correct?

Yes, the menu need to be fixed to say "(4.x -5.x)" instead of "(4.x)", because 5.0.y came only a week ago ...

8 minutes ago, Frank Kettenbeil said:

Will it be possible for me to do kernel builds on the OPi3 itself later on

Not with Armbian build scripts ...

 

For those "sdio/brcm" missing, my bad :(, I had some "un-committed" patches sitting on my desktop for about a week, not they are committed :

https://github.com/armbian/build/commit/56c71fc2ba95b5feee0a6b8951b90aaee953a64c

 

So, please, do another new build and report back ...

Link to comment
Share on other sites

Great work!
running from the start (well, I still had to copy those files around like:

mv /lib/firmware/brcm/brcmfmac43455-sdio.bin /lib/firmware/brcm/brcmfmac43455-sdio.bin-ORIG
mv /lib/firmware/brcm/brcmfmac43455-sdio.txt /lib/firmware/brcm/brcmfmac43455-sdio.txt-ORIG
cp /lib/firmware/rkwifi/fw_bcm43456c5_ag.bin /lib/firmware/brcm/brcmfmac43455-sdio.bin
cp /lib/firmware/rkwifi/nvram_ap6256.txt /lib/firmware/brcm/brcmfmac43455-sdio.txt

 

but afterwards just added my WLAN to the nmtui configuration - works like a charm!
Thank you!

 

Just for your information:

Adding the following line and calling the compiler as shown below still did not make a difference for screen resolution.

setenv video-mode sunxi:1920x1080,monitor=hdmi,hpd=0,edid=1

--

mkimage -C none -A arm -T script -d /boot/boot.cmd /boot/boot.scr

 

Link to comment
Share on other sites

1 hour ago, Frank Kettenbeil said:

Adding the following line and calling the compiler as shown below still did not make a difference for screen resolution.

setenv video-mode sunxi:1920x1080,monitor=hdmi,hpd=0,edid=1

I'm not fluent with HDMI since all my boards are headless, but I think you are wrongly use "video-mode".

In the bootargs definition, it should be something like "disp.screen0_output_mode=1920x1080p60" .

Link to comment
Share on other sites

@Frank Kettenbeil @martinayotte U-Boot environment doesn't influence anything. That U-Boot line works only with DE1 hardware (mostly pre-A83T SoCs) and even then only for simplefb driver. That kernel parameter maybe works with BSP kernel, but not mainline. On mainline, one of the possible ways to force resolution is using:

drm.edid_firmware=edid/1920x1080.bin

as kernel parameter.

 

More details: https://wiki.archlinux.org/index.php/kernel_mode_setting#Forcing_modes_and_EDID

Link to comment
Share on other sites

 

7 hours ago, martinayotte said:

Yes, the menu need to be fixed to say "(4.x -5.x)" instead of "(4.x)", because 5.0.y came only a week ago ...

Not with Armbian build scripts ...

 

For those "sdio/brcm" missing, my bad :(, I had some "un-committed" patches sitting on my desktop for about a week, not they are committed :

https://github.com/armbian/build/commit/56c71fc2ba95b5feee0a6b8951b90aaee953a64c

 

So, please, do another new build and report back ...

confirmed that wifi is fine now.  just compiled image Armbian_5.77_Orangepi3_Ubuntu_bionic_dev_5.0.2_desktop.img and copying firmware files as suggested made wifi available.

root@orangepi3:~# nmcli c s
NAME                  UUID                                  TYPE      DEVICE
Susitiko zirnis pupa  41028de0-521f-42ec-9f40-2d083fefd799  wifi      wlan0
Wired connection 1    30c13842-98ba-3a75-8f70-720e36af852d  ethernet  eth0
root@orangepi3:~# uname -r
5.0.2-sunxi64

 

3 hours ago, jernej said:

@Frank Kettenbeil @martinayotte U-Boot environment doesn't influence anything. That U-Boot line works only with DE1 hardware (mostly pre-A83T SoCs) and even then only for simplefb driver. That kernel parameter maybe works with BSP kernel, but not mainline. On mainline, one of the possible ways to force resolution is using:


drm.edid_firmware=edid/1920x1080.bin

as kernel parameter.

 

More details: https://wiki.archlinux.org/index.php/kernel_mode_setting#Forcing_modes_and_EDID

 

I tried same in older and latest image, without a success.

I even have tried to mesh all suggestion and even then i was not able to make resolution higher than 1024x768

 

root@orangepi3:~# cat /sys/class/drm/card0-HDMI-A-1/modes
1024x768
800x600
800x600
848x480
640x480
root@orangepi3:~# cat /proc/cmdline
root=UUID=8a049638-52f5-404a-975e-82635cd28050 rootwait rootfstype=ext4 console=ttyS0,115200 console=tty1 panic=10 consoleblank=0 loglevel=1 ubootpart=bdbfba5b-01 usb-storage.quirks=0x2537:0x1066:u,0x2537:0x1068:u   drm.edid_firmware=edid/1920x1080.bin cgroup_enable=memory swapaccount=1

 

 

also tried add same code as per https://github.com/Icenowy/linux/commit/468b998b3b9f84b2e7f2da5ee355c14d28824451 and compile image, but that haven't change anything.  (i made sure that file have not changed before compilers kicks in)

 

maybe someone knows how to manipulate allwinner h6 gpios ? any guide would be helpful.

 

Link to comment
Share on other sites

for those who do not want to spend their preciaus CPU time  - https://drive.google.com/file/d/10v5c9imEsbQBmH3NxoL-PODEzfd2XU8z/view

 

wifi trick:

mv /lib/firmware/brcm/brcmfmac43455-sdio.bin /lib/firmware/brcm/brcmfmac43455-sdio.bin-ORIG
mv /lib/firmware/brcm/brcmfmac43455-sdio.txt /lib/firmware/brcm/brcmfmac43455-sdio.txt-ORIG
cp /lib/firmware/rkwifi/fw_bcm43456c5_ag.bin /lib/firmware/brcm/brcmfmac43455-sdio.bin
cp /lib/firmware/rkwifi/nvram_ap6256.txt /lib/firmware/brcm/brcmfmac43455-sdio.txt 

if display is not supporting resolution 1024x768 (like mines) then apt install x11vnc should help to change resolution down to supported one.

Link to comment
Share on other sites

On 3/23/2019 at 2:19 PM, alterfritz said:

By using that image (https://github.com/krachlatte/armbian-orangepi3/releases) the pi3 still seems to boot into pre-configured Android, not booting from SD.

 

Any idea how to change that? 

I do not think, that krachlatte has updated his branch. I had the same problem last week until I realized that I was still using his branch.

So I switched back to the original one. 
Actually you should be able to take this image if you like (it's been built yesterday): https://cloud.multivalenzen.de/s/2k36y6QeHrnZHbx 2019-03-27: link outdated - no longer available

Link to comment
Share on other sites

I build a new image today. 
 

23 hours ago, kexec said:

wifi trick:


mv /lib/firmware/brcm/brcmfmac43455-sdio.bin /lib/firmware/brcm/brcmfmac43455-sdio.bin-ORIG
mv /lib/firmware/brcm/brcmfmac43455-sdio.txt /lib/firmware/brcm/brcmfmac43455-sdio.txt-ORIG
cp /lib/firmware/rkwifi/fw_bcm43456c5_ag.bin /lib/firmware/brcm/brcmfmac43455-sdio.bin
cp /lib/firmware/rkwifi/nvram_ap6256.txt /lib/firmware/brcm/brcmfmac43455-sdio.txt 

 

That worked for on-board wifi. 

And I've got 1080p to work too.
Here's what I've done
 

nicod@orangepi3:~$ sudo cvt 1920 1080 60                                 
# 1920x1080 59.96 Hz (CVT 2.07M9) hsync: 67.16 kHz; pclk: 173.00 MHz
Modeline "1920x1080_60.00"  173.00  1920 2048 2248 2576  1080 1083 1088 1120 -hsync +vsync

nicod@orangepi3:~$ sudo xrandr --newmode "1920x1080_60.00"  173.00  1920 2048 2248 2576  1080 1083 1088 1120 -hsync +vsync

nicod@orangepi3:~$ sudo xrandr --addmode HDMI-1 1920x1080_60.00

nicod@orangepi3:~$ sudo xrandr --output HDMI-1 --mode 1920x1080_60.00    

Very happy with this. I think I've got everything working now on it. (that I need)
This board is ready to make a review video about it. Thank you all.

P.S.: Forum was down when I made it work, how disappointed I was I couldn't let everyone know :)

Link to comment
Share on other sites

16 hours ago, NicoD said:

I build a new image today. 
 

That worked for on-board wifi. 

And I've got 1080p to work too.
Here's what I've done
 


nicod@orangepi3:~$ sudo cvt 1920 1080 60                                 
# 1920x1080 59.96 Hz (CVT 2.07M9) hsync: 67.16 kHz; pclk: 173.00 MHz
Modeline "1920x1080_60.00"  173.00  1920 2048 2248 2576  1080 1083 1088 1120 -hsync +vsync

nicod@orangepi3:~$ sudo xrandr --newmode "1920x1080_60.00"  173.00  1920 2048 2248 2576  1080 1083 1088 1120 -hsync +vsync

nicod@orangepi3:~$ sudo xrandr --addmode HDMI-1 1920x1080_60.00

nicod@orangepi3:~$ sudo xrandr --output HDMI-1 --mode 1920x1080_60.00    

Very happy with this. I think I've got everything working now on it. (that I need)
This board is ready to make a review video about it. Thank you all.

P.S.: Forum was down when I made it work, how disappointed I was I couldn't let everyone know :)

did u make any change while building?

Link to comment
Share on other sites

Everything seems to be working very well. I've tested the USB3, works fine. +300MB/s.
5G wifi works great (5MB/s)
It is fast for a quad-core. Only my Odroid C2 can keep up when it's overclocked to 1.75Ghz + ram OC 1104Mhz. It can't keep up at stock settings.
I've used a mid-large heatsink with a 5V fan connected at 3.3V and while maxed out for 2hours it didn't go over 52°C.

Last time the temperature shot up to +70°C after a second maxed out. It's not doing this anymore.(I don't know why, it's the same heatsink, just another image)

Now it does throttle at 60°C. It goes down to 1.3Ghz. So this is a big difference. Maybe this could be done a bit better. Example : at 70°C to 1.5Ghz and +80°C to 1.3Ghz?

It stays at 65°C and 1.3Ghz with heatsink and without a fan.

So without a fan you don't have a good performance right now.

I couldn't get acces to the eMMC. Maybe this still needs to be added.

Otherwise it's a joy to work with.

 

Link to comment
Share on other sites

32 minutes ago, NicoD said:

I couldn't get acces to the eMMC. Maybe this still needs to be added.

It is there on the commit I did on Friday ... I'm currently running 5.0.y from the eMMC ... Oh ! you're right ! I've the eMMC still on 4.20.y ... I must have forgotten some thing ... Now checking !

Link to comment
Share on other sites

Hello, thank you all so much for your work, very much looking forward to using it!

I tried building the current dev image debian and ubuntu without desktop for my orangepi3 (without eMMC) (instructions worked great!) but when I power it on, it does not show in the network, its connected via LAN.

I also tried Nico and Krachlates image with the same result.

 

Using the image from OrangePi, it gets an iP and connects.

 

I sadly cannot check what the output is as I have no HDMI cable around (sad but true), jus wondering if there is something I'd need to do in order to make it connect to the Network? IPs are assigned using DHCP and it works fine for Raspis that I have running. For the raspis I have to put in an `ssh` file to enable ssh, I thought maybe there was something similar regarding network for armbian but I did not find something like this mentioned?

 

thanks in any case, maybe I just need to wait for an official image from you guys.

Link to comment
Share on other sites

1 hour ago, Murdag said:

I tried building the current dev image debian and ubuntu without desktop for my orangepi3 (without eMMC) (instructions worked great!) but when I power it on, it does not show in the network, its connected via LAN.

I don't have ethernet here. I didn't test that.
 

2 hours ago, NicoD said:

It stays at 65°C and 1.3Ghz with heatsink and without a fan.

I've done a blender test with, and without fan.
With fan : 2h13m21s     Max temp : 52°C always at 1.80Ghz
No fan    : 2h47m04s     Max temp : 68°C between 1.80Ghz - 1.32Ghz
That's a 20% difference, and the max temperature isn't that high.

@martinayotte Also on-board sound isn't working. Neither hmdi nor 3.5mm. I've tried usb audio adapters and these work.
 

Link to comment
Share on other sites

49 minutes ago, NicoD said:

I don't have ethernet here. I didn't test that.

I was under the wrong impression this was assumed to be working because wifi seemed more advanced but in reality they're just not related at all I guess. 

Link to comment
Share on other sites

55 minutes ago, mraiser said:

Maximum resolution is 1024x768 and I can also confirm no "boot from emmc" no reboot and no audio. I was able to get wifi working using kexec's trick. 

For 1080p do this.
 

xrandr --newmode "1920x1080_60.00"  173.00  1920 2048 2248 2576  1080 1083 1088 1120 -hsync +vsync &&  xrandr --addmode HDMI-1 1920x1080_60.00 && xrandr --output HDMI-1 --mode 1920x1080_60.00

Look up to see how to do it with other resolutions.
@mraiser @TuricaT Can you guys test ethernet please?
SBC-bench result of the OPi3 with Armbian Bionic dev 5.0.2 fan at 3.3V : http://ix.io/1Ep9 
 

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines