Jump to content

Recommended Posts

Posted
  On 10/29/2019 at 8:41 AM, raschid said:

This image is currently running on exactly this box (android TV-box R69). I used Etcher to burn the image to a Class 10 SAN-Disk card. Insert card and boot.

There seem to be different versions of this box around - maybe yours is different from mine ...

 

Cheers!

Expand  

Dear you,

I think your board and my board is different version.

I having a blue board.  Below is picture about it.

It using Allwinner sun8iw7p1 (max 1008 MHz), ram 1GB ddr2 (Max 400MHz), NAND 8GB (dolphin-fvd-p1).

How is your board?

Excuseme! Do you get image directly and burn to sdcrad? Or do you rebuild from open source code?

I think we have to config about dram (speed clock,etc...) correctly. After that, we can re build open source code, to get new image.

 

 

r69_sunvell.jpg

Posted
  On 10/29/2019 at 8:51 AM, congtm said:

How is your board?

Expand  

 

Mine is the red 2017 version (rev.1.3) - the boards seem to be very different. Yours has 8G NAND, mine has 2 Samsung DDR3L SDRAM modules. Lot's of other differences from the pics.

I built the OS using Armbians build environment. There is a "community supported" profile for the Sunvell R69 which in its current (mainline) version does not run on my device. I did not test the (FEX-based) legacy version which is available as well. The kernel image provided above was built with a somewhat modified kernel patch (I had to add a cpu voltage regulated to the device tree to make it work).

 

Cheers!

IMG_8667small.JPG

IMG_8668small.JPG

Posted
  On 10/29/2019 at 9:57 AM, raschid said:

 

Mine is the red 2017 version (rev.1.3) - the boards seem to be very different. Yours has 8G NAND, mine has 2 Samsung DDR3L SDRAM modules. Lot's of other differences from the pics.

I built the OS using Armbians build environment. There is a "community supported" profile for the Sunvell R69 which in its current (mainline) version does not run on my device. I did not test the (FEX-based) legacy version which is available as well. The kernel image provided above was built with a somewhat modified kernel patch (I had to add a cpu voltage regulated to the device tree to make it work).

 

Cheers!

IMG_8667small.JPG

IMG_8668small.JPG

Expand  

Dear you,

Thank you for your helps.

Lot's of other differences from the pics. I think that, too.

So, my board can't boot images.

I know this link:

https://github.com/karabek/SunvellR69

https://github.com/armbian/build

It is open source code link. I can get and rebuild it.

But it is very difficult to change config in source code to apply for my board correctly.

Thank you.

 

 

Posted
  On 10/29/2019 at 4:21 AM, congtm said:

Dear you,

I have just tried h3droid_installer.img.xz.

Use tool 'Etcher' or use dd command to burn image to my sdcard.

My sdcard which I tried all.

- sandisk sd card class 4 , 8GB.

- sandisk sd card extreme pro class 10, 16GB.

- samsung evo plus class 10, 32GB.

My OS is ubuntu 18.04 LTS.

But, I have the same error.

U-Boot SPL 2017.07-00494-g19d1f1a2f3-dirty (May 30 2019 - 18:01:48)
DRAM: 0 MiB
### ERROR ### Please RESET the board ###

Can you check it to help me, please?
Below is log booting default on my board, not use sdcard on board.

 

log_r69_default.txt 7.97 kB · 3 downloads

Expand  

My friend, I think I can propose what is your issue here, please do let me know how close I get:

 

#1. When a sdcard is not booting and you boot from the onboard 8GB eMMc on the Sunvell R69 you will get the error you are seeing above, this is because the u-boot on the eMMc from factory is not made to boot from sdcard

#2. While you downloaded the h3droid_installer.img.xz file, you did not decompress the image file with the program 'xz' or similar decompression program for your operating system

#3. If you will try again and first decompress the file, then write it to the Sdcard with etcher and place it into the Sunvell R69 I think you will see a different outcome at boot time

#4. My guess is also when using other images you may have also failed to decompress them as well.  You may want to revisit Armbian images and make sure you have decompressed them with '7zip' or '7z' on Linux before you write them to the card. 

 

To clarify, if you fail to decompress the image and write it to the card there will be no u-boot and the data on the card unusable, so it will not boot from the card.  If you have written the sdcard correctly, the uboot (bios) will be there and should start when you plug the power in for the board.

 

It is understandable for someone new at this to miss this step, so don't feel too much shame if I hit the nail on the head.  My hope is you will at least be able to get something booted.

 

Good Luck!

 

Cheers!

Posted
  On 10/30/2019 at 12:18 AM, TheLinuxBug said:

My friend, I think I can propose what is your issue here, please do let me know how close I get:

 

#1. When a sdcard is not booting and you boot from the onboard 8GB eMMc on the Sunvell R69 you will get the error you are seeing above, this is because the u-boot on the eMMc from factory is not made to boot from sdcard

#2. While you downloaded the h3droid_installer.img.xz file, you did not decompress the image file with the program 'xz' or similar decompression program for your operating system

#3. If you will try again and first decompress the file, then write it to the Sdcard with etcher and place it into the Sunvell R69 I think you will see a different outcome at boot time

#4. My guess is also when using other images you may have also failed to decompress them as well.  You may want to revisit Armbian images and make sure you have decompressed them with '7zip' or '7z' on Linux before you write them to the card. 

 

To clarify, if you fail to decompress the image and write it to the card there will be no u-boot and the data on the card unusable, so it will not boot from the card.  If you have written the sdcard correctly, the uboot (bios) will be there and should start when you plug the power in for the board.

 

It is understandable for someone new at this to miss this step, so don't feel too much shame if I hit the nail on the head.  My hope is you will at least be able to get something booted.

 

Good Luck!

 

Cheers!

Expand  

Thank you so much!

I will try again with h3droid_installer.img.xz file.

Furthermore, I know that android box tv r69 have more PCB versions.

My board using Allwinner sun8iw7p1 (max 1008 MHz), ram 1GB ddr2 (Max 400MHz), NAND 8GB.

It is a blue board.

Code on board is "R69-8X4XDDR3_V2.0", "2018-04-08". But data log default about ram is ram 1GB ddr2.

 

Posted
  On 10/30/2019 at 12:18 AM, TheLinuxBug said:

My friend, I think I can propose what is your issue here, please do let me know how close I get:

 

#1. When a sdcard is not booting and you boot from the onboard 8GB eMMc on the Sunvell R69 you will get the error you are seeing above, this is because the u-boot on the eMMc from factory is not made to boot from sdcard

#2. While you downloaded the h3droid_installer.img.xz file, you did not decompress the image file with the program 'xz' or similar decompression program for your operating system

-> 

I have just decompressed by command "xz --decompress h3droid_installer.img.xz", to get h3droid_installer.img file (223,3 MB).

After that, write it to the Sdcard with 'etcher' tool and place it into the my board.

image.thumb.png.21cae06577df00ea114c43a6973c537a.png

image.thumb.png.01a7b1c3b84528a373c5b51c3b4a04b0.png

But I have the same issue.

I think #1 is reason which you said.

How is solutions to fix #1?

Thank you.

 

#3. If you will try again and first decompress the file, then write it to the Sdcard with etcher and place it into the Sunvell R69 I think you will see a different outcome at boot time

#4. My guess is also when using other images you may have also failed to decompress them as well.  You may want to revisit Armbian images and make sure you have decompressed them with '7zip' or '7z' on Linux before you write them to the card. 

 

To clarify, if you fail to decompress the image and write it to the card there will be no u-boot and the data on the card unusable, so it will not boot from the card.  If you have written the sdcard correctly, the uboot (bios) will be there and should start when you plug the power in for the board.

 

It is understandable for someone new at this to miss this step, so don't feel too much shame if I hit the nail on the head.  My hope is you will at least be able to get something booted.

 

Good Luck!

 

Cheers!

Expand  

 

Posted
  On 2/8/2018 at 8:41 AM, manuti said:

 

Hi @raschid or @guidol can you share this new image?

Or is going to be included in the official repo from armbian in the future?

Thanks in advance.

Expand  

@raschid @manuti

yesterday & today I did try to re-use my old Sunvell R69 (Red PCB H2+ CPU v1.3), but the only image which will boot/start is my "old" image Armbian_5.41_Sunvell-r69_Debian_stretch_next_4.14.34.img.zip

which I have now uploaded to Google-Drive for other users here:

https://drive.google.com/file/d/1-_wAqnbTR1y7OVVVn9rpsQ2jhIm4n8_b/view?usp=sharing

 

With Armbian_5.41_Sunvell-r69_Debian_stretch_next_4.14.34.img.zip the boot process is fine:

 

login as: root
root@192.168.6.152's password:
 ____                       _ _   ____   __   ___
/ ___| _   _ _ ____   _____| | | |  _ \ / /_ / _ \
\___ \| | | | '_ \ \ / / _ \ | | | |_) | '_ \ (_) |
 ___) | |_| | | | \ V /  __/ | | |  _ <| (_) \__, |
|____/ \__,_|_| |_|\_/ \___|_|_| |_| \_\\___/  /_/


Welcome to ARMBIAN 5.41 user-built Debian GNU/Linux 9 (stretch) 4.14.34-sunxi
package bsp-kernel[5.41] u-boot[5.41] dtb[5.41] firmware[5.41] config[5.41]
branch[next]

System load:   0.09 0.17 0.20   Up time:       25 min
Memory usage:  6 % of 1000MB    IP:            192.168.6.152
CPU temp:      39°C
Usage of /:    8% of 15G

Last login: Sat Apr 14 14:08:54 2018

root@sunvell-r69:~#


 

  Reveal hidden contents

 

https://linux-sunxi.org/Sunvell_R69 did state that also armbian v5.67 with kernel 4.14 should work but not with kernel 4.19:
 

  Quote

Current status

Armbian 5.72 with kernel version 4.19 does not boot correctly on this board as of January 2019, neither from a fresh microSD or upgraded from previous versions on the NAND.

Armbian 5.67 with kernel version 4.14 seems to work correctly.

Expand  

 

With the serial-TTL attached I did try yesterday & today some "actual"  images unsuccessful :(

 

Armbian_19.11.3_Sunvell-r69_buster_legacy_4.19.86.img did start and does apply the 2 dtb-overlays,
does start to blink with the blue heartbeat LED, but then dies without any message:

  Reveal hidden contents

 

The following 2 images does start, but cant apply the dtb-overlays and try to fallback to the original dtb.
Blue Heartbeat LED does start, will blink faster and faster and then also did die :(
Armbian_19.11.3_Sunvell-r69_stretch_current_5.3.13.img
Armbian_19.11.3_Sunvell-r69_buster_dev_5.3.13.img

  Reveal hidden contents

 

Also a problem is to update the image Armbian_5.41_Sunvell-r69_Debian_stretch_next_4.14.34.img.zip,

because while updating its reaches armbian v5.92 and kernel 4.19.x and after reboot is will dies very quick in u-boot

 

So I did freeze the kernel in armbian-config at 4.14.34.

Had to remove armbian-stretch = /etc/apt/sources.d/armbian.list and leave only the content of /etc/apt/sources.list

 

Does anyone got a idea, what changed after Kernel 4.14 (no more .fex? only dtb?) or newer u-boot

Has anyone (with the red PCB v1.3) got a newer release running on the R69?

Posted

Just for FUN I did check whats the minimal kernel for debian buster...
its something like 3.1.2 - so I did (with the frozen armbian 5.41 kernel 4.1.4.34)

  Quote

The following packages have been kept back:
  linux-dtb-next-sunxi linux-image-next-sunxi
0 upgraded, 0 newly installed, 0 to remove and 2 not upgraded.

Expand  


a dist-upgrade from Stretch to Buster (firstly without the armbian.list - was also the old stretch version)
the debian way ;)

(some say I/we shouldnt do that with armbian!?)

 

After that I inserted the buster version of armbian.list from my NanoPi Neo2 and re-did the apt upgrade....

 

Now I have a armbian v5.41 Buster with kernel 4.1.4.34 but armbian-config and armbian-firmware of v5.98:

Sunvell_R69_buster_41434.jpg.22816d1f8309dbcde9d5f3a1aed5ff23.jpg

 

Better than nothing ;)

 

@raschid but it would be very nice to read about your (kernel?) 5.3 version :) Thanks in advance!

 

Posted (edited)
  On 11/27/2019 at 4:26 PM, raschid said:
Expand  

Yes - I did give it a try - but first a little helpful reminder ;)

You can ZIP the .img from 923MB to 282MB - so its faster for you to upload and faster to us to download :)

 

932 MB (977.272.832 Bytes) Armbian_19.11.3_Sunvell-r69_bionic_dev_5.4.0-rc8.img

282 MB (296.077.974 Bytes) Armbian_19.11.3_Sunvell-r69_bionic_dev_5.4.0-rc8.img.zip

 

I did boot the image with serial-TTL attached and the image also didnt load the overlays for analog-audio and cir:
 

Found mainline kernel configuration
29532 bytes read in 8 ms (3.5 MiB/s)
382 bytes read in 8 ms (45.9 KiB/s)
Applying kernel provided DT overlay sun8i-h3-cir.dtbo
failed on fdt_overlay_apply(): FDT_ERR_NOTFOUND
339 bytes read in 9 ms (36.1 KiB/s)
Applying kernel provided DT overlay sun8i-h3-analog-codec.dtbo
failed on fdt_overlay_apply(): FDT_ERR_BADMAGIC
base fdt does did not have a /__symbols__ node
make sure you've compiled with -@
Error applying DT overlays, restoring original DT
29532 bytes read in 8 ms (3.5 MiB/s)

BUT the blue led keeps blinking and the kernel DOENST die :)
 

Uncompressing Linux... done, booting the kernel.

Armbian 19.11.3 Bionic ttyS0

sunvell login: root
Password:
Last login: Wed Nov 27 17:19:58 UTC 2019 on ttyS0
 ____                       _ _   ____   __   ___
/ ___| _   _ _ ____   _____| | | |  _ \ / /_ / _ \
\___ \| | | | '_ \ \ / / _ \ | | | |_) | '_ \ (_) |
 ___) | |_| | | | \ V /  __/ | | |  _ <| (_) \__, |
|____/ \__,_|_| |_|\_/ \___|_|_| |_| \_\\___/  /_/

Welcome to Armbian Bionic with Linux 5.4.0-rc8-sunxi

System load:   1.08 0.26 0.08   Up time:       0 min
Memory usage:  7 % of 998MB     IP:            192.168.6.151
CPU temp:      41°C
Usage of /:    6% of 15G

 

How did you did that (what did you changed before or while the compile process)?

And do you got a image with working analog-audio and cir (OK, analog-audio would be enough for me :) )

 

Thanks in advance

Edited by guidol
Also edited the download-link for smaller filesize :)
Posted

@guidol, thank you for the kind hint - I updated the link.

I added a cpu voltage regulator node to the device tree - oddly enough to build a viable kernel there seems to have to be one ... although this box reportedly does not have anything remotely resembling a PMIC (still working on that ...).

Regarding the overlays: the IR overlay seems to be missing while the audio overlay appears to have been compiled for another kernel version ('bad magic'). No idea how armbian generates overlays, sorry. But IR is "OKed" in the DTS and should work anyway.

Posted
  On 11/27/2019 at 5:57 PM, raschid said:

@guidol, thank you for the kind hint - I updated the link.

I added a cpu voltage regulator node to the device tree - oddly enough to build a viable kernel there seems to have to be one ... although this box reportedly does not have anything remotely resembling a PMIC (still working on that ...).

Regarding the overlays: the IR overlay seems to be missing while the audio overlay appears to have been compiled for another kernel version ('bad magic'). No idea how armbian generates overlays, sorry. But IR is "OKed" in the DTS and should work anyway.

Expand  

@raschid

I took the uncompiled .dts files for analog-audio and cir out of the armbian-build-system from

/build/cache/sources/linux-mainline/orange-pi-5.4/arch/arm/boot/dts/overlay/sun8i-h3-analog-codec.dts
/build/cache/sources/linux-mainline/orange-pi-5.4/arch/arm/boot/dts/overlay/sun8i-h3-cir.dts

andc copied they via ftp to the Sunvell R69.

 

Then I decompiled the sun8i-h2-plus-sunvell-r69.dtb

dtc -I dtb -O dts /boot/dtb/sun8i-h2-plus-sunvell-r69.dtb -o /boot/dtb/sun8i-h2-plus-sunvell-r69_guido.dts

and edited/inserted the changes of the 2 .dts/overlays (the right way) in the new complete 

/boot/dtb/sun8i-h2-plus-sunvell-r69_guido.dts

 

after that I recompiled the .dts back to .dtb with

dtc -I dts -O dtb /boot/dtb/sun8i-h2-plus-sunvell-r69_guido.dts -o /boot/dtb/sun8i-h2-plus-sunvell-r69_guido.dtb

now backup the original .dtb:

cp /boot/dtb/sun8i-h2-plus-sunvell-r69.dtb /boot/dtb/sun8i-h2-plus-sunvell-r69.dtb_org

 

then copy the new compiled .dtb over the old one:

cp /boot/dtb/sun8i-h2-plus-sunvell-r69_guido.dtb /boot/dtb/sun8i-h2-plus-sunvell-r69.dtb

 

Now check /boot/armbianEnv.txt for lines about overlays or user-overlays to load and delete them, then save the file.

 

Boot should now be like this (without applying overlays) - click to open:
 

  Reveal hidden contents

 

 

After login you could see the analog-audio available with

aplay -l

**** List of PLAYBACK Hardware Devices ****
card 0: Codec [H3 Audio Codec], device 0: CDC PCM Codec-0 [CDC PCM Codec-0]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 1: allwinnerhdmi [allwinner-hdmi], device 0: 1c22800.i2s-i2s-hifi i2s-hifi-0 [1c22800.i2s-i2s-hifi i2s-hifi-0]
  Subdevices: 1/1
  Subdevice #0: subdevice #0

A problem can be that armbian-config => system => hardware always try to add these 2 overlays to /boot/armbianEnv.txt as normal overlay (not as useroverlay).

 

If you/we got a matching .dts (uncompiled overlay) got then you could add it to armbian (compile and add to /boot/overlays-user)

with 

armbian-add-overlay ./sun8i-h3-analog-codec.dts
armbian-add-overlay ./sun8i-h3-cir.dts

 But the .dts-files (uncompiled overlay) doenst match exact the original sun8i-h2-plus-sunvell-r69.dtb :(

 

As attachment the .dts/.dtb-files I did work with as .zip ;)

 

BTW: the reactions-times in the ssh-shell are mostly longer tahn on the serial-console.... I dont know why :(

[EDIT] the SSH-"problem" seems to be the networkcard dropping the connection very often
see dmesg -w

[ 1994.263612] dwmac-sun8i 1c30000.ethernet eth0: Link is Down
[ 1997.332536] dwmac-sun8i 1c30000.ethernet eth0: Link is Up - 100Mbps/Full - flow control rx/tx
[ 2002.452590] dwmac-sun8i 1c30000.ethernet eth0: Link is Down
[ 2005.524796] dwmac-sun8i 1c30000.ethernet eth0: Link is Up - 100Mbps/Full - flow control rx/tx
[ 2008.596679] dwmac-sun8i 1c30000.ethernet eth0: Link is Down
[ 2013.716942] dwmac-sun8i 1c30000.ethernet eth0: Link is Up - 100Mbps/Full - flow control rx/tx
[ 2027.029061] dwmac-sun8i 1c30000.ethernet eth0: Link is Down
 

2 forum links about that "old" problem:
https://forum.armbian.com/topic/6189-ethernet-connection-keeps-dropping-out/
https://forum.armbian.com/topic/3951-nanopi-neo-and-arabian-527-my-first-impression-and-issues/

 

 

 

r69_dts_dtb.zipFetching info...

Posted

Ha :) I think I did found some "network-problem"  :)

When my armbian-build-system PC is on (which has a 1GBit/1000MBit Network card and connectted to the same 100MBit-Hub)

then I do get much Down/Up messages in dmesg  :(

BUT when I poweroff my PC with the GBit-Network-card then I do get very less messages.

I think the rest will come from another GBit-device (another SBC on my 100MBit Hub)

 

So when the GBit-device want to send with GBit and couldnt it switch/reset the connection to 100MBit and this does see the R69?

 

So my new little theory :)

 

I will test it out - unlucky me I only got a 5port GBit-Hub and a 20-port 100MBit-Hub - so Ihavent enough GBit ports :(

But this is the first time I do see that problem and only with the R69

 

Posted

@guidol I have a similar setup - PC GBit interface and R69 connected to the same switch => no up/down events in dmesg.

 

IR indeed works. Audio indeed does not. The <codec> node for H3 devices which is activated by the sun8i-h3-analog-codec overlay is defined in sunxi-h3-h5.dtsi and thus part of our dts here. No idea why the overlay fails.

 

By the way, building via armbian build environment works fine now:
 

./compile.sh BOARD=sunvell-r69 BRANCH=dev

 

Posted

Just tried "current" - same audio issue:

root@sunvell:~# cat /proc/asound/cards
 0 [allwinnerhdmi  ]: allwinner_hdmi - allwinner,hdmi
                      allwinner,hdmi

so H3_Audio_Codec is also missing in 5.3.x

 

 

Posted
  On 11/28/2019 at 4:55 PM, raschid said:

so H3_Audio_Codec is also missing in 5.3.x

Expand  

OK - then you have to compile the .dts (that have I changed for ananlog and cir = /boot/dtb/sun8i-h2-plus-sunvell-r69_guido.dts)
with kernel 5.3 and place it in /boot/dtb/

Did work for 5.40.-rc8 with the bionic miage from you:
 

root@sunvell-r69(192.168.6.118):/toshiba/iradio/stations# uname -a
Linux sunvell-r69 5.4.0-rc8-sunxi #19.11.3 SMP Wed Nov 27 17:01:29 CET 2019 armv7l armv7l armv7l GNU/Linux
root@sunvell-r69(192.168.6.118):/toshiba/iradio/stations# cat /proc/asound/cards
 0 [Codec          ]: H3_Audio_Codec - H3 Audio Codec
                      H3 Audio Codec
 1 [allwinnerhdmi  ]: allwinner-hdmi - allwinner-hdmi
                      allwinner-hdmi
root@sunvell-r69(192.168.6.118):/toshiba/iradio/stations# mpg123 -v -b 1024 -@ ./MP3_SAW_80s
High Performance MPEG 1.0/2.0/2.5 Audio Player for Layers 1, 2 and 3
        version 1.25.10; written and copyright by Michael Hipp and others
        free software (LGPL) without any warranty but with best wishes
Decoder: generic
Trying output module: alsa, device: <nil>
Using playlist from ./MP3_SAW_80s ...
Note: guessed M3U playlist type

Directory: http://saw-de-hz-fal-stream10-cluster01.radiohost.de/

Terminal control enabled, press 'h' for listing of keys and functions.

Playing MPEG stream 1 of 1: saw-80er_128 ...
ICY-NAME: 80er
ICY-URL: http://stream.saw-musikwelt.de/saw-80er

MPEG 1.0 L III cbr128 44100 j-s
> 24+01 -00:00.02+00:00.62 [00:00.65] --- 100=100 128 kb/s  418 B acc    0 clip p+0.000
ICY-META: StreamTitle='BILLY OCEAN - GET OUTTA MY DREAMS GET INTO MY CAR';
> 455+001  00:06.04+00:05.84 [00:05.84] --- 100=100 128 kb/s  418 B acc    0 clip p+0.000

 

Posted
  On 11/28/2019 at 5:39 PM, raschid said:

"current" on an OPi zero also seems to be missing analog audio at this time - so this is not specific to this board.

Expand  

My OPi Zero is at dev Linux opi-zero 5.4.0-rc8-sunxi #19.11.3  at this time and analog-audio is available.
 

root@opi-zero(192.168.6.99):~# cat /proc/asound/cards
 0 [Codec          ]: H3_Audio_Codec - H3 Audio Codec
                      H3 Audio Codec
root@opi-zero(192.168.6.99):~# aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: Codec [H3 Audio Codec], device 0: CDC PCM Codec-0 [CDC PCM Codec-0]
  Subdevices: 1/1
  Subdevice #0: subdevice #0


 

Posted
  On 11/28/2019 at 4:55 PM, raschid said:

Just tried "current" - same audio issue:

so H3_Audio_Codec is also missing in 5.3.x

Expand  

@raschid that ONLY ;) the same dtb-problem as in 5.4 :)

I copied my changed sun8i-h2-plus-sunvell-r69_guido.dts from the 5.4 kernel to the 5.3 buster installation via ftp 

 

then compiled it with kernel 5.3 as .dtb

dtc -I dts -O dtb /home/guido/r69_dts_dtb/sun8i-h2-plus-sunvell-r69_guido.dts -o /home/guido/r69_dts_dtb/sun8i-h2-plus-sunvell-r69_guido.dtb

backuped the 5.3 original .dtb

cp /boot/dtb/sun8i-h2-plus-sunvell-r69.dtb ./sun8i-h2-plus-sunvell-r69.dtb_org_53

and inserted the new compiled .dtb into /boot/dtb

cp sun8i-h2-plus-sunvell-r69_guido.dtb /boot/dtb/sun8i-h2-plus-sunvell-r69.dtb

after that I deleted the follwoing lines from /boot/armbianEnv.txt (because the overlays are included in the dtb)

overlay_prefix=sun8i-h3
overlays=cir analog-codec

now reboot and you will have analog audio (and cir) also in kernel 5.3 (Ok I got debian buster and not ubuntu bionic):

Welcome to Armbian Buster with Linux 5.3.13-sunxi

package bsp-kernel[19.11.3] u-boot[19.11.3] dtb[19.11.3] firmware[19.11.3] config[19.11.3]
branch[current]

root@sunvell:~# aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: Codec [H3 Audio Codec], device 0: CDC PCM Codec-0 [CDC PCM Codec-0]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 1: allwinnerhdmi [allwinner-hdmi], device 0: 1c22800.i2s-i2s-hifi i2s-hifi-0 [1c22800.i2s-i2s-hifi i2s-hifi-0]
  Subdevices: 1/1
  Subdevice #0: subdevice #0

I will attach the compiled 5.3 version which you could copy to /boot/dtb  and reboot - I think the "debian" version 5.3 should work with ubuntu 5.3
(and dont forget to kill the 2 lines in /boot/armbianEnv.txt)

sun8i-h2-plus-sunvell-r69.dtbFetching info...

Posted

Hi,

 

I bought not one but two R69 boxes on the Internet. My problem is that both boxes show wrong mac adress from what they are suppossed to show and both boxes are showing the same mac adress. I conected both boxes one at the time with cable to my router so they where not conected at the same time and still they show the same mac adress. I dont know how. Do anyone know what can be wrong and how to fix it? Is it possible to change mac adress perminantley and how? I would like to change the mac adress on both boxes to the mac adress they are suppose to have/show. I dont know if this is the right place to post this questain but I am glad for all the help I can get. I tried to register an app that I bought with the mac adress that the box shows and it said that the mac adress is banned.

 

 

Posted
  On 12/27/2019 at 4:07 AM, Manolo said:

Hi,

 

I bought not one but two R69 boxes on the Internet. My problem is that both boxes show wrong mac adress from what they are suppossed to show and both boxes are showing the same mac adress. I conected both boxes one at the time with cable to my router so they where not conected at the same time and still they show the same mac adress. I dont know how. Do anyone know what can be wrong and how to fix it? Is it possible to change mac adress perminantley and how? I would like to change the mac adress on both boxes to the mac adress they are suppose to have/show. I dont know if this is the right place to post this questain but I am glad for all the help I can get. I tried to register an app that I bought with the mac adress that the box shows and it said that the mac adress is banned.

 

 

Expand  

I hope you're not asking how to troubleshoot Android issues.

Posted

USB on the back does not work => Information:

 

I compiled Armbian (Bionic, 5.5.0rc2) and tested it on my r69 h2 ver. 1.3 blue PCB with nothing special.

Everything works fine except the USB on the back.

After some investigation I checked the dtb file and there is the back-USB port configured as OTG.

I dont' know if is this a bug or a feature but if you want to use both USB you have ti change the dtb file.

After decompile change line 322 in dtb from "otg" to "host", compile it again and replace the orginal file in /boot

I added the corrected dts and the compiled dtb file for Kernel 5.5.0rc2.

 

sun8i-h2-plus-sunvell-r69.dtbFetching info... sun8i-h2-plus-sunvell-r69.dtsFetching info...

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.

×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines