Jump to content

Single Armbian image for RK + AML + AW (aarch64 ARMv8)

balbes150

By balbes150
in General Chat

 Share

Recommended Posts

balbes150

balbes150

Posted
  • Author
Posted
2 hours ago, zero said:

will try the new

For some reason that I don't understand yet, on the Allwinner H6 (Tanix TX6) model, I have the SD card and eMMC numbers on the opposite side than on the other RK and AML models. If you have problems running on H6, try replacing these files with these options.

 

https://yadi.sk/d/3crtWoQvvosh1w

Link to comment
Share on other sites
balbes150

balbes150

Posted
  • Author
Posted

Good news for RockPI 4B owners. This is an image with Armbian Bionic that includes support for running from USB. I checked this image with eMMC and SD card, running direct system startup from USB. :)

RockPI 4B does not have a very convenient placement of eMMC and SD connectors (if the NVMe module is connected on top, the loop from it overlaps the SD connector) so it is very difficult to test different systems. This image solves this problem. You can write any system to SD or eMMC and add a u-boot version that supports USB startup to the media (second link). Install the eMMC module or SD card and start the main system from them. When you need to quickly check or just start another system with USB, you simply connect the USB drive with the new system and it starts automatically when you turn on the power, turn off the USB and return to the normal system. If Radxa added one small patch to the source code for SPI, you can get a unique u-boot that supports direct launch from USB. :)

 

I recorded an Armbian image on eMMC and installed it on the Board, and now it is very convenient for me to quickly launch Libreelec from USB, I can use a universal image that does not depend on the availability of the necessary u-boot for the SD card, just configure the DTB correctly and voila, the system works completely with USB, without any additional steps. I connected the USB-I have LE, disabled USB and can immediately start Armbian. :)

 

Armbian Biomic

https://yadi.sk/d/M1hzFvNq7SpfmA

 

u-boot

https://yadi.sk/d/Se637oJkw54tfA

1
Link to comment
Share on other sites
zero

zero

Posted
Posted
18 hours ago, balbes150 said:

For some reason that I don't understand yet, on the Allwinner H6 (Tanix TX6) model, I have the SD card and eMMC numbers on the opposite side than on the other RK and AML models. If you have problems running on H6, try replacing these files with these options.

 

https://yadi.sk/d/3crtWoQvvosh1w

just tried to run "Armbian_19.11.5_Arm-64_bionic_dev_5.5.0-rc2_2020017.img" on on my H6 tvb (slightly different from tanix tx6 but it could run a tanix tx6 img from sdcard)

and the result is as u expected,,, it's not boot the armbian, it's boot the android on the emmc directly, no attempt to boot the sdcard from logs...

i did apply the "ALLWINNER_FIX_SCRIPT", and still the problem persist,,,

may be there is another different issue especially on my h6 board (since its not exact tanix tx6)? or there was an issue on the u-boot?

the last 19.11.4 did boot the armbian,,,

what step i can try next?

Link to comment
Share on other sites
balbes150

balbes150

Posted
  • Author
Posted
36 minutes ago, zero said:

may be there is another different issue especially on my h6 board (since its not exact tanix tx6)? or there was an issue on the u-boot?

By default, the image contains u-boot for rk3399. Did you replace u-boot with your version after writing the image to the SD card ?

 

Images that already include u-boot for H6 (Tanix TX6) can be found here

https://yadi.sk/d/GJbDt3-FjQ-dQA

Link to comment
Share on other sites
zero

zero

Posted
Posted
20 minutes ago, balbes150 said:

By default, the image contains u-boot for rk3399. Did you replace u-boot with your version after writing the image to the SD card ?

 

Images that already include u-boot for H6 (Tanix TX6) can be found here

https://yadi.sk/d/GJbDt3-FjQ-dQA

that time (while not booting to sdcard) not yet replace the u-boot,,,

and now i did, replace the allwinner u-boot...

first i got this (compiled config from orangepi 3 with ddr3 patch), stuck on the "Starting kernel ..." 

U-Boot SPL 2019.10-armbian (Jan 18 2020 - 04:35:32 +0700)
DRAM: 2048 MiB
Trying to boot from MMC1


U-Boot 2019.10-armbian (Jan 18 2020 - 04:35:32 +0700) Allwinner Technology

CPU:   Allwinner H6 (SUN50I)
Model: OrangePi 3
DRAM:  2 GiB
MMC:   mmc@4020000: 0, mmc@4022000: 1
Loading Environment from EXT4...
** Unable to use mmc 0:auto for loading the env **
In:    serial@5000000
Out:   serial@5000000
Err:   serial@5000000
Net:   No ethernet 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.scr
673 bytes read in 2 ms (328.1 KiB/s)
## Executing script at 4fc00000
start mainline u-boot
1113 bytes read in 2 ms (543 KiB/s)
## Error: "mac" not defined
## Error: "eth_mac" not defined
23357952 bytes read in 2340 ms (9.5 MiB/s)
17531 bytes read in 6 ms (2.8 MiB/s)
## Flattened Device Tree blob at 4fa00000
   Booting using the fdt blob at 0x4fa00000
   Loading Device Tree to 0000000049ff8000, end 0000000049fff47a ... OK

Starting kernel ...

 

second try (compiled config from orangepi oneplus with ddr3 patch) 

U-Boot SPL 2019.10 (Jan 16 2020 - 22:13:46 +0700)
DRAM: 2048 MiB
Trying to boot from MMC1
NOTICE:  BL31: v2.2(debug):a04808c-dirty
NOTICE:  BL31: Built : 07:15:09, Jan 16 2020
NOTICE:  BL31: Detected Allwinner H6 SoC (1728)
NOTICE:  BL31: Found U-Boot DTB at 0xc07fff8, model: OrangePi One Plus
INFO:    ARM GICv2 driver initialized
NOTICE:  PMIC: Probing AXP805
IN

 

both u-boot compiled using u-boot tools v2019.10 from Armbian build tools...

 

Link to comment
Share on other sites
balbes150

balbes150

Posted
  • Author
Posted
5 minutes ago, zero said:

and now i did, replace the allwinner u-boot...

first i got this (compiled config from orangepi 3 with ddr3 patch), stuck on the "Starting kernel ..."

This is a working u-boot. With it, you need to check the rest of the DTBS. To do this, you need to change the settings of the used dtb in the uEnv file one by one.txt. You can see the list of available DTBS in the /dtb/allwinner directory (try all files with h6 in the name in turn)

Link to comment
Share on other sites
zero

zero

Posted
Posted

is that?

congratulation to me,,, "my very first working self compiled u-boot":lol:

ok sir, next, move on to the dtbs,,, will try to find which is working...

will continue using "Armbian_19.11.5_Arm-64_bionic_dev_5.5.0-rc2_2020017.img" which already write on my sdcard...

 

thank for the advice,,,

1
Link to comment
Share on other sites
Alex83

Alex83

Posted
Posted
On 1/11/2020 at 10:23 AM, balbes150 said:

For a universal image, the installation is performed only through the direct launch of the desired script , for each platform it is different.

 

All long logs need to be removed in the spoiler, they make it very difficult to read the topic.

Or put them in a text file and make an attachment to the message.

 

 

Wiredguard is included in the working (non-DEV) versions.

what should I do with the full root partition with 256MB

 

ITS WITH EVERY CHANGE OF KERNEL OR BOOT OPTIONS AN ERROR MESSAGE FOR BOOT PARTITION (NO SPACE LEFT)

On 1/11/2020 at 10:23 AM, balbes150 said:

 

 

To All

 

DEV versions are intended for experienced users to test new core functionality.

 

Link to comment
Share on other sites
balbes150

balbes150

Posted
  • Author
Posted

Update to version 19.11.5 (20200120) kernel 5.5.0-rc6.

Important change. the way DTB is configured has changed. The universal multiload for the AML platform has changed. Now a single configuration method is used for all platforms, using the file (uEnv.txt). You need to edit this file to configure it. You need to uncomment the two lines that are responsible for your platform and specify the correct DTB for your model. If you use this image to run on the one platform, you can delete it from the settings file (uEnv.txt) strings from other platforms.

 

Pay attention. The installation algorithm in eMMC has changed. My recommend that you perform a clean installation in eMMC. Be sure to make a full backup of eMMC before installing it in eMMC. Important. On models S905\S905X and partially on S912, there may be problems with starting the desktop, management is possible only via SSH or UART.

 

 

For the aw H6 platform, all scripts are already in the image (which have the ending aw). You need to rename the files with the replacement (remove the .aw ending).

1
Link to comment
Share on other sites
Turgus

Turgus

Posted
Posted

While newest LE builds boot and all armbian images up to 19.11.4 (I tested) work(and install) nice -like always with usb sound and ETH- on x96mini 2/16 test box, I didn't manage to get any of the 19.11.5 builds working..on the earlier .5 builds device booted(with usual meson-gxl-s905w-p281.dtb set) but there was no usb keyboard working. On newer builds I get just black screen flickering slightly for some seconds until tv switches to "no signal".

Is there any trick to get the video output back like the  video=HDMI-A-1:e tweak on (some) allwinner h6 devices?

Until now I also had no luck booting any build on the flowfon f1 4/32 H6 box I got. The pcb is 3rd revision of H6mini board used also on Eachlink H6mini, Eachlink H6max(yes same board, but on max always 4 gb ram) and several other petrel-p1-h6 boxes. Just once after an alert that cpu is too hot I could boot tanix' tx6 LE from card. Everything I tested worked(HDMI + sound, network, playback, radio/tv streams..), but I never could get the card reboot again. Like on other builds (LE/armbian)I tried try to boot from card, it give just blank screen(no signal). Maybe it is the odd ram timing this device uses-when comparing dts files extracted from tx6 android rom and from a rom that works on this device there are slight differences, but could also be u-boot. Are there any (working) dtb's for these h6mini boards or other approaches to get this beast boot anything useful?!

 

 

Link to comment
Share on other sites
balbes150

balbes150

Posted
  • Author
Posted
8 hours ago, Turgus said:

While newest LE builds boot and all armbian images up to 19.11.4 (I tested) work(and install) nice -like always with usb sound and ETH- on x96mini 2/16 test box, I didn't manage to get any of the 19.11.5 builds working..on the earlier .5 builds device booted(with usual meson-gxl-s905w-p281.dtb set) but there was no usb keyboard working. On newer builds I get just black screen flickering slightly for some seconds until tv switches to "no signal".

 

 

On 1/21/2020 at 12:30 PM, balbes150 said:

On models S905\S905X and partially on S912, there may be problems with starting the desktop, management is possible only via SSH or UART.

 

 

 

8 hours ago, Turgus said:

Until now I also had no luck booting any build on the flowfon f1 4/32 H6 box I got. The pcb is 3rd revision of H6mini board used also on Eachlink H6mini, Eachlink H6max(yes same board, but on max always 4 gb ram) and several other petrel-p1-h6 boxes. Just once after an alert that cpu is too hot I could boot tanix' tx6 LE from card. Everything I tested worked(HDMI + sound, network, playback, radio/tv streams..), but I never could get the card reboot again. Like on other builds (LE/armbian)I tried try to boot from card, it give just blank screen(no signal). Maybe it is the odd ram timing this device uses-when comparing dts files extracted from tx6 android rom and from a rom that works on this device there are slight differences, but could also be u-boot. Are there any (working) dtb's for these h6mini boards or other approaches to get this beast boot anything useful?!

 

If after adding u-boot does not start, add UART and see what happens.

 

 

 

1
Link to comment
Share on other sites
Tarzanus

Tarzanus

Posted
Posted

Kernel 5.5.0-rc6 works nice and stable on my RK3318 based box. USB3 works again. The only isue I have now is slow rendering of websites in chromium (high CPU usage) and completely useless Kodi which also uses almost 100% CPU without even starting a movie - even moving around the menus lags.

Is Mali450 GPU that slow or is it not fully supported so most (all) rendering is done through CPU using software rendering instead of GPU rendering? It seems strange, libreelec worked quite nice with Kodi.

Link to comment
Share on other sites
Turgus

Turgus

Posted
Posted

..if you want use pure kodi, pop in a card with libreelec installed, or maybe use android..consider armbian on these boxes as sbc for server tasks or as tiny low cost and low-medium performance desktop mini-pc with just basic multimedia features with built in and patched mpv player..

 

 

Link to comment
Share on other sites
Tarzanus

Tarzanus

Posted
Posted
11 hours ago, Turgus said:

..if you want use pure kodi, pop in a card with libreelec installed, or maybe use android..consider armbian on these boxes as sbc for server tasks or as tiny low cost and low-medium performance desktop mini-pc with just basic multimedia features with built in and patched mpv player..

 

 

I know and I do have a libreelec/Kodi sd-card, but it would be more than great if somehow we could make Armbian on these TV boxes more optimized. They could be easily used as cheap basic Desktop computer replacement used for video playback, internet browsing and libreoffice work. While there's  unnecessary high CPU load, these chips are also overheating which again cause them to throttle and slow down.
My first thought and the reason I bought it was basic webserver for a not-so-large website and the first results are more than promising.

Link to comment
Share on other sites
martinayotte

martinayotte

Posted
Posted
15 hours ago, starman345 said:

but no wifi

Try that and reboot : 

mv /lib/firmware/brcm/brcmfmac4356-sdio.bin /lib/firmware/brcm/brcmfmac4356-sdio.bin-ORIG
mv /lib/firmware/brcm/brcmfmac4356-sdio.txt /lib/firmware/brcm/brcmfmac4356-sdio.txt-ORIG
cp /lib/firmware/brcm/brcmfmac4356-sdio-nanopi-m4v2.bin /lib/firmware/brcm/brcmfmac4356-sdio.bin
cp /lib/firmware/brcm/brcmfmac4356-sdio-nanopi-m4v2.txt /lib/firmware/brcm/brcmfmac4356-sdio.txt

 

1
Link to comment
Share on other sites
balbes150

balbes150

Posted
  • Author
Posted
19 minutes ago, martinayotte said:

Try that and reboot :

I have long thought about making separate packages with specific firmware and settings for different models that use the same files, but with different content (version) of the files. But unfortunately there is not enough time for these steps.If there are users who will build such packages, they can be placed in the Armbian network repo for easy installation by regular users.

 

p.s. By the way, I received a sample of NanoPC T4 today and now I can test all the tests on it at once. :)

Link to comment
Share on other sites
starman345

starman345

Posted
Posted
35 minutes ago, martinayotte said:

Try that and reboot : 


mv /lib/firmware/brcm/brcmfmac4356-sdio.bin /lib/firmware/brcm/brcmfmac4356-sdio.bin-ORIG
mv /lib/firmware/brcm/brcmfmac4356-sdio.txt /lib/firmware/brcm/brcmfmac4356-sdio.txt-ORIG
cp /lib/firmware/brcm/brcmfmac4356-sdio-nanopi-m4v2.bin /lib/firmware/brcm/brcmfmac4356-sdio.bin
cp /lib/firmware/brcm/brcmfmac4356-sdio-nanopi-m4v2.txt /lib/firmware/brcm/brcmfmac4356-sdio.txt

 

 that is what I used to get wifi working. You posted that in another thread a few days(weeks) ago, thanks for that. 

Link to comment
Share on other sites
sivanoff

sivanoff

Posted
Posted
48 minutes ago, balbes150 said:

Armbian version 20200124 with 5.5 core with working HDMI for s905\s905x\s912. Sound doesn't work

Should this version work on S905X3? I'm seeing green screen if i copy u-boot.sd to u-boot.ext and original x96max+ logo if not but nothing boots in any case.

 

Link to comment
Share on other sites
balbes150

balbes150

Posted
  • Author
Posted
24 minutes ago, sivanoff said:

Should this version work on S905X3? I'm seeing green screen if i copy u-boot.sd to u-boot.ext and original x96max+ logo if not but nothing boots in any case.

I don't have s905x3, I don't test anything for this chip.

Link to comment
Share on other sites
stut

stut

Posted
Posted

Thanks for the awesome work merging all the boxes into one build. I tried the 19.11.5 build on my p212 box, pretty much everything works out of the box including wifi but the cpu only switches between 500 and 1000mhz when it should have more steps up to 1200mhz. I put a UART/bootlog for 19.11.5 here. How can I fix the cpu to have the right frequency and frequency steps for cpufreqd? 

root@arm:~# cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_frequencies
100000 250000 500000 667000 1000000 

Installing to internal works on previous non-unified 19.11.3 but on this build it causes a kernel panic while it's copying files: 

[  108.969561] SError Interrupt on CPU2, code 0xbf000000 -- SError
[  108.969566] CPU: 2 PID: 1642 Comm: tar Tainted: G         C        5.5.0-rc7-arm-64 #19.11.5
[  108.969569] Hardware name: Amlogic Meson GXL (S905X) P212 Development Board (DT)
[  108.969571] pstate: 20000005 (nzCv daif -PAN -UAO)
[  108.969573] pc : __arch_copy_from_user+0x1bc/0x240
[  108.969574] lr : copyin+0x94/0xa8
[  108.969576] sp : ffff8000136d3c10
[  108.969577] x29: ffff8000136d3c10 x28: ffff000059011828 
[  108.969581] x27: 00000000000100a1 x26: fffffdfffff4c000 
[  108.969586] x25: 0000000000000000 x24: ffff8000136d3d40 
[  108.969589] x23: 0000000000001000 x22: 0000000000001000 
[  108.969593] x21: 0000000000001000 x20: ffff8000136d3d50 
[  108.969597] x19: ffff000005300000 x18: 0000000000000000 
[  108.969601] x17: 0000000000000000 x16: 0000000000000000 
[  108.969605] x15: 0000000000000000 x14: 20202020200a276e 
[  108.969608] x13: 5c656854202e7374 x12: 6e656d7567726120 
[  108.969612] x11: 73746920666f206d x10: 7573206568742073 
[  108.969616] x9 : 646c65697920726f x8 : 73746e656d756772 
[  108.969620] x7 : 6127202020202020 x6 : ffff0000053000d0 
[  108.969624] x5 : ffff000005301000 x4 : 0000000000000000 
[  108.969627] x3 : 0000aaaaddf5a000 x2 : 0000000000000ec0 
[  108.969631] x1 : 0000aaaaddf5a110 x0 : ffff000005300000 
[  108.969636] Kernel panic - not syncing: Asynchronous SError Interrupt
[  108.969638] CPU: 2 PID: 1642 Comm: tar Tainted: G         C        5.5.0-rc7-arm-64 #19.11.5
[  108.969641] Hardware name: Amlogic Meson GXL (S905X) P212 Development Board (DT)
[  108.969642] Call trace:
[  108.969644]  dump_backtrace+0x0/0x1d0
[  108.969645]  show_stack+0x14/0x20
[  108.969647]  dump_stack+0xbc/0x100
[  108.969648]  panic+0x160/0x320
[  108.969650]  nmi_panic+0x60/0x90
[  108.969651]  arm64_serror_panic+0x74/0x80
[  108.969653]  do_serror+0x80/0x138
[  108.969654]  el1_error+0x8c/0x108
[  108.969656]  __arch_copy_from_user+0x1bc/0x240
[  108.969658]  copy_page_from_iter+0xdc/0x260
[  108.969659]  pipe_write+0x12c/0x480
[  108.969661]  new_sync_write+0x16c/0x180
[  108.969663]  __vfs_write+0x2c/0x40
[  108.969664]  vfs_write+0xb0/0x1d0
[  108.969666]  ksys_write+0xd0/0xe8
[  108.969667]  __arm64_sys_write+0x18/0x20
[  108.969669]  el0_svc_handler+0xac/0x218
[  108.969671]  el0_sync_handler+0x18c/0x490
[  108.969672]  el0_sync+0x140/0x180
[  108.969692] SMP: stopping secondary CPUs
[  108.969693] Kernel Offset: disabled
[  108.969695] CPU features: 0x00002,20002000
[  108.969697] Memory Limit: none

If any more logs or debugging is needed let me know, happy to provide whatever I can.

Link to comment
Share on other sites
hippo5329

hippo5329

Posted
Posted

Thank you for the awesome works.

 

I tested 20200124 on a Tanix TX3 (TX3-H) S905X3 64G+4G with USB boot and HDMI display and installed to emmc. The wlan0 device appeared but can not connect. The HDMI sound doesn't work even with pulseaudio removed and g12_sound.

 

Could you please push the updates to Github? It would help me adjust the kernel config. I need to run pppoe and ufw.

Link to comment
Share on other sites
noname

noname

Posted
Posted

I have a Tronsmart S95 Pro (s905, 1/8 G).
The latest version (5.5.0-rc7) is not loaded, the logo just flashes cyclically.

With version legacy_5.5.0-rc1 , everything loads and works fine.

In all cases I use bionic (console and desktop), meson-gxbb-vega-s95-pro.dtb

Link to comment
Share on other sites
Guest
This topic is now closed to further replies.
 Share
Go to topic listing
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines

  I accept