Jump to content

Orangepi 3 h6 allwiner chip


constantius

Recommended Posts

13 minutes ago, Flole said:

Nope, it clearly says Orange_PI-3 on it, downloaded from the Google Drive. Dated at November 26th 2018.

So, it should be the same as mine : Ok ! The block diagram is wrong, but I never care about block diagram, I care only about real schematic ... Page 8 clearly states that VCC-5V is direct from DC-IN !

Link to comment
Share on other sites

2 hours ago, Flole said:

t's indeed a little low on mine aswell

Hi. I've only had that powering with barrel jack. With microUSB it's as stable as could be. It's the world in reverse.
I expected the cables from OPi to not be good enough. I've got 2 and both are like that. I don't know.
I havent tried with a PSU with barrel jack. Don't know if I've got one.
I've showed this behaviour in my review video : https://www.youtube.com/watch?v=D2SIpXTOb9A&t=492s
 

Link to comment
Share on other sites

30 minutes ago, martinayotte said:

So, it should be the same as mine : Ok ! The block diagram is wrong, but I never care about block diagram, I care only about real schematic ... Page 8 clearly states that VCC-5V is direct from DC-IN !

Not only the block diagram is wrong but the Power Tree aswell (which is somewhat important). And Page 10 clearly says that the VCC-5V is connected to the GND Pin of the USB, which is also not correct.....  I don't really trust these schematics anymore....

 

18 minutes ago, NicoD said:

With microUSB it's as stable as could be. It's the world in reverse.
 

Just tried this aswell, and indeed it's a lot better. Weird.....

 

Anyways, there doesn't seem to be some kind of regulator involved so it's all good now!

Link to comment
Share on other sites

5 hours ago, GeorgeP said:

With my OPi3 powered from the 'genuine' power adaptor via the power jack I'm not seeing any voltage issues.

On no load I see 5.2v at the USB sockets..

That sais enough. They are overvolting their PSU's so it would not undervolt too quickly. I'm using a 4A 5V PSU that's 5.1V and I've got undervoltage.
And it's not no load voltage that's important. It's full load voltage.
But because doing it wrong you've proven they know about it.

Link to comment
Share on other sites

I trying to get the USB3 working with orange pi lite 2 and the latest nigtly snapshot 5.1.3-sunxi64 #5.87.190522.

I notice that the usb3 is disabled in the the dtb file:
 

                                dwc3@5200000 {

                                                compatible = "snps,dwc3";

                                                reg = <0x5200000 0x10000>;

                                                interrupts = <0x0 0x1a 0x4>;

                                                clocks = <0x2 0x72 0x2 0x72 0xa 0x0>;

                                                clock-names = "ref", "bus_early", "suspend";

                                                resets = <0x2 0x33>;

                                                dr_mode = "host";

                                                phys = <0x1f>;

                                                phy-names = "usb3-phy";

                                                status = " disabled ";

                                                phandle = <0x52>;

                                };

 

                                phy@5210000 {

                                                compatible = "allwinner,sun50i-h6-usb3-phy";

                                                reg = <0x5210000 0x10000>;

                                                clocks = <0x2 0x6a>;

                                                resets = <0x2 0x2d>;

                                                #phy-cells = <0x0>;

                                                status = "disabled";

                                                phandle = <0x1f>;

                                };

 

I changed the status (from disable to okay) on  both and recompile the dts file, and now I can see the usb3 HUB:

lsusb -t
/:  Bus 07.Port 1: Dev 1, Class=root_hub, Driver=musb-hdrc/1p, 480M
/:  Bus 06.Port 1: Dev 1, Class=root_hub, Driver=ohci-platform/1p, 12M
/:  Bus 05.Port 1: Dev 1, Class=root_hub, Driver=ehci-platform/1p, 480M
/:  Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 5000M
/:  Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 480M
/:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ohci-platform/1p, 12M
/:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-platform/1p, 480M

However no devices are detected, no even powering when plugged into the USB port. I contacted Icenowy, who currently maintains the usb3 driver, and have been advised that current driver should be working.
I wonder if the issue rests in the dts file setup, current parameter setup,  given the fact it was marked as disabled?
 I noticed someone in the H6 dev forum mentioned that this was working back a month or so ago, however it does not seem to be working in the latest sanpshot.    
 

Link to comment
Share on other sites

hello I've been gone from the game for a while, just flashed a new image ( 5.1.5 kernel for orangepioneplus )

and it seems it has been decided to downgrade CPU speed to 1,5GHz instead of 1.8GHz:  "current policy: frequency should be within 480 MHz and 1.49 GHz. " ?

Hopefully this can be set back to 1,8?

 

 

Link to comment
Share on other sites

14 hours ago, dolphs said:

hello I've been gone from the game for a while, just flashed a new image ( 5.1.5 kernel for orangepioneplus )

and it seems it has been decided to downgrade CPU speed to 1,5GHz instead of 1.8GHz:  "current policy: frequency should be within 480 MHz and 1.49 GHz. " ?

Hopefully this can be set back to 1,8?

 

 

 

i have just tried latest debian build kernel 5.1.3

and CPU show 1.8Ghz.

HDMI works as it should, edid bug gone. you can now enjoy full HD resolution without any nasty magic

i2c device is still not showing up my devices

 

 

Link to comment
Share on other sites

apt upgrade returned following

 

Setting up linux-image-dev-sunxi64 (5.88.190529) ...
Error! Your kernel headers for kernel 5.1.5-sunxi64 cannot be found.
Please install the linux-headers-5.1.5-sunxi64 package,
or use the --kernelsourcedir option to tell DKMS where it's located

 

Unfortunately, there is no linux-headers-5.1.5-sunxi64 package

Link to comment
Share on other sites

U-Boot 2019.04-armbian (May 31 2019 - 01:42:20 +0200) Allwinner Technology      
                                                                                
CPU:   Allwinner H6 (SUN50I)                                                    
Model: OrangePi 3                                                               
DRAM:  2 GiB                                                                    
MMC:   mmc@4020000: 0, mmc@4022000: 1                                           
Loading Environment from EXT4... ** File not found /boot/boot.env **            
                                                                                
** Unable to read "/boot/boot.env" from mmc0:1 **                               
In:    serial@5000000                                                           
Out:   serial@5000000                                                           
Err:   serial@5000000                                                           
Net:   No ethernet found.                                                       
starting USB...                                                                 
No controllers found                                                            
Hit any key to stop autoboot:  0                                                
switch to partitions #0, OK                                                     
mmc0 is current device                                                          
Scanning mmc 0:1...                                                             
Found U-Boot script /boot/boot.scr                                              
3042 bytes read in 1 ms (2.9 MiB/s)                                             
## Executing script at 4fc00000                                                 
U-boot loaded from SD                                                           
Boot script loaded from mmc                                                     
165 bytes read in 2 ms (80.1 KiB/s)                                             
27608 bytes read in 8 ms (3.3 MiB/s)                                            
4161 bytes read in 4 ms (1015.6 KiB/s)                                          
Applying kernel provided DT fixup script (sun50i-h6-fixup.scr)                  
## Executing script at 44000000                                                 
5587948 bytes read in 567 ms (9.4 MiB/s)                                        
14563336 bytes read in 1473 ms (9.4 MiB/s)                                      
## Loading init Ramdisk from Legacy Image at 4fe00000 ...                       
   Image Name:   uInitrd                                                        
   Image Type:   AArch64 Linux RAMDisk Image (gzip compressed)                  
   Data Size:    5587884 Bytes = 5.3 MiB                                        
   Load Address: 00000000                                                       
   Entry Point:  00000000                                                       
   Verifying Checksum ... OK                                                    
## Flattened Device Tree blob at 4fa00000                                       
   Booting using the fdt blob at 0x4fa00000                                     
   Loading Ramdisk to 49aab000, end 49fff3ac ... OK                             
   Loading Device Tree to 0000000049a3b000, end 0000000049aaafff ... OK         
                                                                                
Starting kernel ...                                                             
                                                                                
                                                                                
Debian GNU/Linux 9 orangepi3 ttyS0                                              
                                                                                
orangepi3 login: [   82.424484] Internal error: SP/PC alignment exception: 8a00P
[   82.424489] Modules linked in: zstd zram btsdio bluetooth snd_soc_hdmi_codecx
[   82.463741] Process swapper/2 (pid: 0, stack limit = 0x0000000044a1bf13)     
[   82.473532] CPU: 2 PID: 0 Comm: swapper/2 Not tainted 5.1.5-sunxi64 #5.88.191
[   82.484073] Hardware name: OrangePi 3 (DT)                                   
[   82.491347] pstate: 00000085 (nzcv daIf -PAN -UAO)                           
[   82.499353] pc : 0xf                                                         
[   82.504745] lr : bsearch+0x50/0xb8                                           
[   82.511367] sp : ffff000010013c80                                            
[   82.517858] x29: ffff000010013c80 x28: 0000000000000010                      
[   82.526337] x27: 0000000000000000 x26: ffff800074c034a0                      
[   82.534819] x25: ffff800074c034a0 x24: 000000000000000f                      
[   82.543312] x23: 0000000000000008 x22: 000000000000000f                      
[   82.551786] x21: 0000000000000001 x20: 0000000000000017                      
[   82.560237] x19: 0000000000000001 x18: 0000000000000000                      
[   82.568668] x17: ffff000010acba60 x16: ffff000010a88c58                      
[   82.577098] x15: 0000000000000000 x14: ffff000010a88c58                      
[   82.585533] x13: 0000000000000001 x12: ffff000010a88c30                      
[   82.593964] x11: 0000000000000001 x10: ffffffffffffffff                      
[   82.602394] x9 : 0000000000000000 x8 : 0000000000000006                      
[   82.610834] x7 : ffff800077bad870 x6 : 0000000000000040                      
[   82.619232] x5 : ffff800073f30bc0 x4 : 000000000000000f                      
[   82.627577] x3 : 000000000000000f x2 : 0000000000000000                      
[   82.635919] x1 : 0000000000000017 x0 : ffff800074c034a0                      
[   82.644276] Call trace:                                                      
[   82.649759]  0xf                                                             
[   82.654611]  resched_cpu+0xe4/0xe8                                           
[   82.661029]  mod_timer+0x230/0x340                                           
[   82.667421]  rwb_arm_timer+0x48/0x78                                         
[   82.673976]  wb_timer_fn+0x154/0x178                                         
[   82.680515]  blk_stat_timer_fn+0x154/0x168                                   
[   82.687565]  call_timer_fn+0x20/0x78                                         
[   82.694114]  expire_timers+0xc8/0xf8                                         
[   82.700609]  run_timer_softirq+0xc4/0x200                                    
[   82.707501]  __do_softirq+0x114/0x22c                                        
[   82.714032]  irq_exit+0xac/0xc0                                              
[   82.720039]  __handle_domain_irq+0x60/0xb0                                   
[   82.727020]  gic_handle_irq+0x58/0xa8                                        
[   82.733575]  el1_irq+0xb8/0x140                                              
[   82.739577]  arch_cpu_idle+0x10/0x18                                         
[   82.745991]  do_idle+0x1f0/0x2d0                                             
[   82.752013]  cpu_startup_entry+0x20/0x28                                     
[   82.758704]  secondary_start_kernel+0x190/0x1d0                              
[   82.766041] Code: bad PC value                                               
[   82.771860] ---[ end trace 93be063b060c8efb ]---                             
[   82.779230] Kernel panic - not syncing: Fatal exception in interrupt         
[   82.788337] SMP: stopping secondary CPUs                                     
[   82.794975] Kernel Offset: disabled                                          
[   82.801130] CPU features: 0x002,20002004                                     
[   82.807715] Memory Limit: none                                               
[   82.813392] Rebooting in 10 seconds..   

kernbel panic in orangepi3 2GB RAM + Emmc, with last build:

https://dl.armbian.com/orangepi3/nightly/Armbian_5.88.190601_Orangepi3_Debian_stretch_dev_5.1.5.7z

 

 

Link to comment
Share on other sites

Ubuntu Bionic, latest kernels (5.1.6 and 5.1.7) from dev packages 190602+ not boot. Boot stopped after "[  OK  ] Started udev Kernel Device Manager." silently or shows "Unable to handle kernel paging request ..."

I went back to 190601 (latest 5.1.5).

Link to comment
Share on other sites

Seeing the current issues I'm happy that I'm running an earlier build :-)

Welcome to ARMBIAN 5.83 user-built Debian GNU/Linux 10 (buster) 5.0.9-sunxi64   
System load:   2.14 2.11 2.06      Up time:       23 days        
Memory usage:  60 % of 1997MB     Zram usage:    1 % of 998Mb      IP:            192.168.0.5
CPU temp:      56°C               
Usage of /:    27% of 7.1G       

Currently running PiHole, MQTT and SETI@Home :-D

Link to comment
Share on other sites

apt-get update & apt-get -y upgrade from 587 -> 5.88 no go on Orange Pi One+.

As well fresh 5.88 flash ( built manually just few minutes ago ), Armbian_5.88_Orangepioneplus_Debian_stretch_dev_5.1.7 - NOK ... 

BTW 5.1.8 just arrived, as well 4.19.49 is latest while 47 is being used, worth bumping both?

Unfortuantely " Armbian_5.88_Orangepioneplus_Debian_stretch_next_4.19.47 " - NOK

 

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