LinuxQuestions.org - [SOLVED] Orange Pi Plus 2E H3 (unofficial)

Page 1 of 3

Show 50 post(s) from this thread on one page

- Slackware - ARM (https://www.linuxquestions.org/questions/slackware-arm-108/)

- - Orange Pi Plus 2E H3 (unofficial) (https://www.linuxquestions.org/questions/slackware-arm-108/orange-pi-plus-2e-h3-unofficial-4175643661/)

sndwvs

12-04-2018 10:25 PM

Orange Pi Plus 2E H3 (unofficial)

build image for SDcard
- kernel 4.19.6
- mainline u-boot 2019.01-rc1-00582-gd452f27b3e-dirty
- work hdmi
- and other patches

README.TXT

slack-current-arm-miniroot_29Sep18-4.19.6-orange_pi_plus_2e-build-20181205.img.tar.xz
slack-current-arm-miniroot_29Sep18-4.19.6-orange_pi_plus_2e-build-20181205.img.tar.xz.md5

drmozes

12-05-2018 03:47 AM

Quote:

Originally Posted by sndwvs (Post 5933394)

Thanks for this. Since 4.19 is an LTS, let's get some of this back up stream in to Slackware ARM.
Can you tell me which patches specifically are required to enable HDMI for the H3? I think a newer U-boot is required as well, but that ought to be (I hope) a simple upgrade.

sndwvs

12-05-2018 09:53 AM

Quote:

Originally Posted by drmozes (Post 5933459)

1. u-boot was taken the last cut with git
2. the linux source was taken from here branch orange-pi-4.19
3. I only used these patches and it works (patches are also applied to mainline)

Code:

0099-dt-bindings-sun4i-drm-add-HDMI-VCC-supply-property-f.patch

0100-drm-sun4i-Add-support-for-HDMI-voltage-regulator.patch

0126-drm-bridge-move-ANA78xx-driver-to-analogix-subdirect.patch

0127-drm-bridge-split-some-definitions-of-ANX78xx-to-dedi.patch

0128-drm-bridge-extract-some-Analogix-I2C-DP-common-code.patch

0130-drm-bridge-Add-Analogix-anx6345-support.patch

4. configure kernel

Code:

CONFIG_DRM_SUN4I_HDMI=y

CONFIG_DRM_SUN4I_HDMI_CEC=y

CONFIG_DRM_SUN8I_DW_HDMI=y

CONFIG_DRM_DW_HDMI=y

CONFIG_HDMI=y

drmozes

12-05-2018 12:22 PM

I upgraded to

Code:

U-Boot 2019.01-rc1 (Dec 05 2018 - 17:34:37 +0000) Allwinner Technology



=> saveenv

Saving Environment to FAT... Unable to use mmc 1:0... Failed (1)

Where are you storing the environment? I haven't looked yet but may be I just need to edit the defaults in the source and rebuild.

sndwvs

12-05-2018 12:28 PM

I use /boot/boot.cmd /boot/boot.scr

drmozes

12-06-2018 01:57 AM

Quote:

Originally Posted by sndwvs (Post 5933661)

I use /boot/boot.cmd /boot/boot.scr

Where are you writing u-boot to? the eMMC?
It isn't as straight forward as I had hoped and it's not obvious what they changed, so I might ask on the u-boot mailing list.

sndwvs

12-06-2018 02:32 AM

Quote:

Originally Posted by drmozes (Post 5933915)

Where are you writing u-boot to? the eMMC?
It isn't as straight forward as I had hoped and it's not obvious what they changed, so I might ask on the u-boot mailing list.

to boot from eMMC, you need to write u-boot:
# clear u-boot

Code:

dd if=/dev/zero of=/dev/mmcblk1 bs=1k count=1023 seek=1 status=noxfer

dd if=u-boot-sunxi-with-spl.bin of=/dev/mmcblk1 bs=1024 seek=8 status=noxfer

after that add root to boot in /boot/uEnv.txt:

Code:

verbosity=8

console=both

rootdev=/dev/mmcblk1p1

transfer boot.cmd boot.scr to eMMC in /boot

and change fstab on eMMC to mind:

Code:

/dev/mmcblk1p1 / ext4 noatime,nodiratime,derrors=remount-ro 0 1

drmozes

12-06-2018 07:10 AM

Quote:

Originally Posted by sndwvs (Post 5933919)

to boot from eMMC, you need to write u-boot:
# clear u-boot

Code:

dd if=/dev/zero of=/dev/mmcblk1 bs=1k count=1023 seek=1 status=noxfer

dd if=u-boot-sunxi-with-spl.bin of=/dev/mmcblk1 bs=1024 seek=8 status=noxfer

after that add root to boot in /boot/uEnv.txt:

Code:

verbosity=8

console=both

rootdev=/dev/mmcblk1p1

transfer boot.cmd boot.scr to eMMC in /boot

and change fstab on eMMC to mind:

Code:

/dev/mmcblk1p1 / ext4 noatime,nodiratime,derrors=remount-ro 0 1

How does u-boot know where to find /boot ? are you using the default environment present within the u-boot binary that scans available media?

One of the precepts I work to is that people installing Slackware ARM should be safe, if they follow the instructions.
If I suggest overwriting u-boot on the eMMC, and it doesn't work out, you've got a bricked device - which is usually hard to fix.
That's why I go with the SD card approach: at least this is a safe approach.
I'm not sure that I can do that with this method, unless I'm missing something?

sndwvs

12-06-2018 07:49 AM

Quote:

Originally Posted by drmozes (Post 5934018)

How does u-boot know where to find /boot ? are you using the default environment present within the u-boot binary that scans available media?

yes, the default u-boot is used.

Quote:

Originally Posted by drmozes (Post 5934018)

One of the precepts I work to is that people installing Slackware ARM should be safe, if they follow the instructions.
If I suggest overwriting u-boot on the eMMC, and it doesn't work out, you've got a bricked device - which is usually hard to fix.
That's why I go with the SD card approach: at least this is a safe approach.
I'm not sure that I can do that with this method, unless I'm missing something?

i also want the images for SDcard, the transfer from SDcard to eMMC is described above.
for orange pi with non-working u-boot in eMMC, it will boot from SDcard.

drmozes

12-06-2018 08:30 AM

Quote:

Originally Posted by sndwvs (Post 5934028)

for orange pi with non-working u-boot in eMMC, it will boot from SDcard.

Aha! I didn't know that.
Thanks. This might simplify things then.

sndwvs

12-06-2018 08:57 AM

for information Boot Process

Broder Tuck

12-07-2018 04:33 AM

I don't see this config option mentioned in this thread:

CONFIG_SUN8I_DE2_CCU=y

I believe I had to add this one, back when I did an experimental DE2/HDMI backport to the 4.16 kernel for my little H3 device.

sndwvs

12-07-2018 06:31 AM

Quote:

Originally Posted by Broder Tuck (Post 5934383)

this parameter is included in this build.

drmozes

12-08-2018 04:11 AM

Quote:

Originally Posted by sndwvs (Post 5934049)

for information Boot Process

Having thought it through, this is helpful for someone who wants to use the SD card slot for something else, but not for a new user.
We still need a way to place the newer u-boot on to the eMMC - which would mean they need to boot a Linux OS (which may not work properly with the factory version of u-boot, or may have different options - e.g. "save" used to save the environment, and now it is an unknown operation: I need to be able to document from a known state), or do it from u-boot directly (either way requires more documentation). With the SD card route they can do this on an x86.
I'll have to find out why the newer version no longer can save its environment.

sndwvs

11-29-2019 01:32 PM

build image for SDcard
- kernel 5.3.13
- mainline u-boot 2019.10
- work hdmi,audio,wifi,ethernet,lima

slack-current-miniroot_27Nov19-5.3.13-orange_pi_plus_2e-build-20191129.img.xz
slack-current-miniroot_27Nov19-5.3.13-orange_pi_plus_2e-build-20191129.img.xz.md5

slack-current-xfce_27Nov19-5.3.13-orange_pi_plus_2e-build-20191129.img.xz
slack-current-xfce_27Nov19-5.3.13-orange_pi_plus_2e-build-20191129.img.xz.md5

All times are GMT -5. The time now is 03:55 PM.

Page 1 of 3

Show 50 post(s) from this thread on one page