Orangepi2/plus2/PC H3 Linux mainline support

elcct · Published in 2015-11-5 23:19:49

I couldn't apply v4 patches cleanly. Unfortunately have little time now to go further

faddat · Published in 2015-11-8 17:33:03

my desire for a cluster computing necklace is going to drive me to learn C-- not like that's a bad thing, anyway.....

codekipper · Published in 2015-11-9 01:42:46

@elcct
You may find it easier to sync to Hans' sunxi-wip git branch, it now contains all the H3 patches from Jens and it looks like he's working on usb.
Details are here https://github.com/jwrdegoede/linux-sunxi/commits/sunxi-wip
I've not tried this yet but I will ASAP,
CK

faddat · Published in 2015-11-10 07:15:27

@codekipper, thanks once again! I'm giving it another go

tdack · Published in 2015-11-15 10:39:15

I've followed CodeKipper's steps in post #2 to build u-boot and then built a 4.3.0rc6 kernel using the sunxi-wip branch of jwrdegoede/linux-sunxi

To get u-boot to boot a kernel I had to use the h3-*.dts* files from the linux-sunxi sunxi-wip branch in the u-boot sources.

The OrangePi Plus boots to a u-boot prompt, but can't set core voltage and cpu freq:

U-Boot SPL 2015.10-00058-gf4ccf7d-dirty (Nov 15 2015 - 13:14:51)
DRAM: 1024 MiB
Failed to set core voltage! Can't set CPU frequency
U-Boot 2015.10-00058-gf4ccf7d-dirty (Nov 15 2015 - 13:14:51 +1100) Allwinner Technology
CPU: Allwinner H3 (SUN8I)
DRAM: 1 GiB
MMC: SUNXI SD/MMC: 0
*** Warning - bad CRC, using default environment

Copy code

It then boots the kernel but the kernel doesn't finish booting and hangs at:

<div><div>[ 0.987517] sunxi-wdt 1c20ca0.watchdog: Watchdog enabled (timeout=16 sec, nowayout=0)</div><div>[ 0.996380] sunxi-mmc 1c0f000.mmc: No vqmmc regulator found</div><div>[ 1.002527] sunxi-mmc 1c0f000.mmc: Got CD GPIO</div></div><div></div>

Copy code

Full u-boot and kernel boot log: http://pastebin.com/QkfZMw5e

Any suggestions on what to do to resolve the initial u-boot core voltage and cpu freq errors or how to progress further in booting the kernel?

fritz · Published in 2015-11-15 16:02:15

the sunxi-wip branch of jwrdegoede/linux-sunxi use the first version of @jemk's H3-support-patchset.
commits are from 15 May 2015.but it's not for sure that this is a problem.
Will try later with this branch.
If you want compare my boot.log compiled from linux-next branch and yours:
http://pastebin.com/b9ynk2f2

fritz · Published in 2015-11-15 18:49:27

@tdack
Can confirm. sunxi-wip halts at:

[ 1.013141] sunxi-mmc 1c0f000.mmc: Got CD GPIO

there is something wrong.
But there are some patches for enabling USB support for the H3 not yet pushed to the mailinglist.
looks interesting.

fritz · Published in 2015-11-15 21:46:34

Sorry for the "triple" posting, but @melanrz is my master.

Ok serious now.
When i apply the WIP USB patches from sunxi-wip branch of @jwrdegoede to my linux-next branch with the V4 patches from @jemk then it works.
definitly something wrong with sunxi-wip
complete boot-log:
http://pastebin.com/xpqj3VFz

For now you can only play with GPIO's but USB support is coming.

tdack · Published in 2015-11-16 08:01:09

Edited by tdack at 2015-11-16 10:30

When i apply the WIP USB patches from sunxi-wip branch of @jwrdegoede to my linux-next branch with the V4 patches from @jemk then it works.

Fritz, can you point me to the linux-next branch that you are using? I assume that the V4 patches are coming from the linux-sunxi mailing list?

Just to make sure I've got things in the right order:

1. Grab linux-next source
2. Apply jwrdegoede/linux-sunxi sunxi-wip patches for H3 USB support
3. Apply jemk H3 V4 patches from linux-sunxi mailing list
4. Profit, only with GPIO though

Update ...

Using @jwrdegoede/u-boot-sunxi/sunxi-wip and @jwrdegoede/linux-sunxi/sunxi-wip I've now managed to get a full kernel boot.

http://pastebin.com/pBt1iZhT

Looks like USB is progressing!

[ 0.777507] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[ 0.784098] ehci-platform: EHCI generic platform driver
[ 0.789635] ehci-platform 1c1b000.usb: EHCI Host Controller
[ 0.795254] ehci-platform 1c1b000.usb: new USB bus registered, assigned bus number 1
[ 0.803236] ehci-platform 1c1b000.usb: irq 23, io mem 0x01c1b000
[ 0.827604] ehci-platform 1c1b000.usb: USB 2.0 started, EHCI 1.00
[ 0.835123] hub 1-0:1.0: USB hub found
[ 0.839003] hub 1-0:1.0: 1 port detected
[ 0.843788] ehci-platform 1c1c000.usb: EHCI Host Controller
[ 0.849454] ehci-platform 1c1c000.usb: new USB bus registered, assigned bus number 2
[ 0.857365] ehci-platform 1c1c000.usb: irq 25, io mem 0x01c1c000
[ 0.877608] ehci-platform 1c1c000.usb: USB 2.0 started, EHCI 1.00
[ 0.884996] hub 2-0:1.0: USB hub found
[ 0.888851] hub 2-0:1.0: 1 port detected
[ 0.893526] ehci-platform 1c1d000.usb: EHCI Host Controller
[ 0.899180] ehci-platform 1c1d000.usb: new USB bus registered, assigned bus number 3
[ 0.907071] ehci-platform 1c1d000.usb: irq 27, io mem 0x01c1d000
[ 0.927601] ehci-platform 1c1d000.usb: USB 2.0 started, EHCI 1.00
[ 0.934906] hub 3-0:1.0: USB hub found
[ 0.939314] hub 3-0:1.0: 1 port detected
[ 0.943905] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
[ 0.950164] ohci-platform: OHCI generic platform driver
[ 0.955639] ohci-platform 1c1b400.usb: Generic Platform OHCI controller
[ 0.962323] ohci-platform 1c1b400.usb: new USB bus registered, assigned bus number 4
[ 0.970233] ohci-platform 1c1b400.usb: irq 24, io mem 0x01c1b400
[ 1.032832] hub 4-0:1.0: USB hub found
[ 1.036647] hub 4-0:1.0: 1 port detected
[ 1.041830] ohci-platform 1c1c400.usb: Generic Platform OHCI controller
[ 1.048535] ohci-platform 1c1c400.usb: new USB bus registered, assigned bus number 5
[ 1.056429] ohci-platform 1c1c400.usb: irq 26, io mem 0x01c1c400
[ 1.122800] hub 5-0:1.0: USB hub found
[ 1.126612] hub 5-0:1.0: 1 port detected
[ 1.131349] ohci-platform 1c1d400.usb: Generic Platform OHCI controller
[ 1.138050] ohci-platform 1c1d400.usb: new USB bus registered, assigned bus number 6
[ 1.145928] ohci-platform 1c1d400.usb: irq 28, io mem 0x01c1d400
[ 1.212832] hub 6-0:1.0: USB hub found
[ 1.216644] hub 6-0:1.0: 1 port detected

Copy code

fritz · Published in 2015-11-17 16:34:43

@tdack
You can safely remove ehci2/ohci2 from the sun8i-h3-orangepi-plus.dts. port2 is not used on opi plus, there are only 2 test-pads (DM2-DP2)
And ohci1, ohci3 should not be needed to.