Jump to content

How to install armbian in h618?

alienxz77b

By alienxz77b
in Allwinner CPU Boxes

 Share

Recommended Posts

Sidha

Sidha

Posted
Posted

Hi, Thanks, I've tried both working image on my h618 Transpeed tv-box. I have some newbie questions:

- On the miniarch image: I managed to upgrade + setup the wifi, and it works, but I cannot install any desktop environment. I've done every steps and tried a lot different desktop environment, but no luck, it won't start, remains in the text console. Is it possible to install a (simple, like xfce4) desktop environment? How?

- On the Armbian image: everithing works fine (I used an usb hub+usb wifi+bt, internal not working), and there is a working desktop environment, which is great! But I've tried to upgrade (apt update + apt upgrade) and the upgrade maybe messed up the boot somehow, the device won't boot since the upgrade. Is it possible to upgrade the Armbian image? How?

Thanks,

Sidha

 

0
Nick A

Nick A

Posted
Posted (edited)

If there's a kernel or u-boot update then your box won't boot. The kernel and u-boot need patches from my repository for it to work on your box. There are no apt packages for this.

 

I guess you need to burn another sdcard and start from scratch.

Edited by Nick A
0
Sidha

Sidha

Posted
Posted
  On 6/7/2024 at 3:06 PM, Nick A said:

I guess you need to burn another sdcard and start from scratch.

Expand  

Sure. As a beginner, I just won't update it. :)

Or trying to understand the MiniArch desktop-installing thing on another card, it had no problem with upgrade somehow, still works, but on command line only.

0
Dmitriy Geels

Dmitriy Geels

Posted
Posted
  On 6/3/2024 at 3:26 AM, Kajen said:

tx6s, look like it still problem with mmc and keyring updating, at least is no cripple after reboot, but pacman -Syu cannot work, and no hdmi

Expand  

 

Pacman hangs because of mmc problems. Trying to resolve these, I believe the reason is: 

[    1.315833] sun50i-h616-pinctrl 300b000.pinctrl: supply vcc-ph not found, using dummy regulator
[    1.330686] sun50i-h616-pinctrl 300b000.pinctrl: supply vcc-pg not found, using dummy regulator
[    1.564426] sun50i-h616-pinctrl 300b000.pinctrl: supply vcc-pf not found, using dummy regulator
[    1.565408] sun50i-h616-pinctrl 300b000.pinctrl: supply vcc-pc not found, using dummy regulator

 

pinctrl@300b000 have no regulators defined. Also, it seems miniarch has less kernel patches, then armbian.

@Nick A can you share, how you test DT changes?
I tried making overlays, but it seems dtc doesn't like path references inside values. With recompiled full tree, armbian doesn't boot -- it seems I need the source, not decompiled dtb.

0
Dmitriy Geels

Dmitriy Geels

Posted
Posted

What a horrible forum engine. Tried to edit reply text -- and it won't let you!

Wanted to add:

- Vontar h618 miniarch image boots for me

- It has same problems as armbian: no hdmi output, no sound, no wifi, no bluetooth, but also mmc i/o problems

- difference between miniarch images is single line in `/boot/extlinux/extlinux.conf`: 

FDT /dtbs/allwinner/sun50i-h618-vontar-h618.dtb

change it to use different DT.

Need to make a proper uart connector to debug further...

0
Nick A

Nick A

Posted
Posted (edited)

I just got a X98H. It has the same problem.  

 

I was able to extract the Android dts.

 

I found the stock firmware for the box.

https://chinagadgetsreviews.com/download-android-12-stock-firmware-for-x98h-tv-box-2.html

 

Using Apritzel's sunxi firmware extraction tool.

https://github.com/apritzel/sunxi-fw 

nick@nick-Inspiron-5680:~/sunxi-fw$ ./sunxi-fw info -v X98H-20221020-1143.img
@   0: wty: PhoenixSuite image file
	header v3.0, 45 images, 1898 MB
		wty:sys_config.fex      :      34908 bytes @ +0x0000b800
		wty:board.fex           :       1024 bytes @ +0x00014400
		wty:config.fex          :      53248 bytes @ +0x00014800
		wty:split_xxxx.fex      :        512 bytes @ +0x00021800
		wty:sys_partition.fex   :       5601 bytes @ +0x00021c00
		wty:sunxi.fex           :      71168 bytes @ +0x00023400
		wty:boot0_nand.fex      :      61440 bytes @ +0x00034c00
		wty:boot0_sdcard.fex    :      61440 bytes @ +0x00043c00
		wty:u-boot.fex          :     884736 bytes @ +0x00052c00
		wty:u-boot-crash.fex    :         37 bytes @ +0x0012ac00
		wty:toc1.fex            :          8 bytes @ +0x0012b000
		wty:toc0.fex            :          8 bytes @ +0x0012b400
		wty:fes1.fex            :      40160 bytes @ +0x0012b800
		wty:boot_package.fex    :    1261568 bytes @ +0x00135800
		wty:usbtool.fex         :     154112 bytes @ +0x00269800
		wty:usbtool_crash.fex   :     621056 bytes @ +0x0028f400
		wty:aultools.fex        :     166515 bytes @ +0x00327000
		wty:aultls32.fex        :     152069 bytes @ +0x0034fc00
		wty:cardtool.fex        :      73728 bytes @ +0x00375000
		wty:cardscript.fex      :       1899 bytes @ +0x00387000
		wty:sunxi_gpt.fex       :       8192 bytes @ +0x00387800
		wty:sunxi_mbr.fex       :      65536 bytes @ +0x00389800
		wty:dlinfo.fex          :      16384 bytes @ +0x00399800
		wty:arisc.fex           :          6 bytes @ +0x0039d800
		wty:vmlinux.fex         :   12619923 bytes @ +0x0039dc00
		wty:boot-resource.fex   :    7490560 bytes @ +0x00fa7000
		wty:Vboot-resource.fex  :          4 bytes @ +0x016cbc00
		wty:env.fex             :     131072 bytes @ +0x016cc000
		wty:Venv.fex            :          4 bytes @ +0x016ec000
		wty:boot.fex            :   67108864 bytes @ +0x016ec400
		wty:Vboot.fex           :          4 bytes @ +0x056ec400
		wty:vendor_boot.fex     :   33554432 bytes @ +0x056ec800
		wty:Vvendor_boot.fex    :          4 bytes @ +0x076ec800
		wty:super.fex           : 1847555340 bytes @ +0x076ecc00
		wty:Vsuper.fex          :          4 bytes @ +0x758e4400
		wty:misc.fex            :   16777216 bytes @ +0x758e4800
		wty:Vmisc.fex           :          4 bytes @ +0x768e4800
		wty:vbmeta.fex          :       8192 bytes @ +0x768e4c00
		wty:Vvbmeta.fex         :          4 bytes @ +0x768e6c00
		wty:vbmeta_system.fex   :       4096 bytes @ +0x768e7000
		wty:Vvbmeta_system.fex  :          4 bytes @ +0x768e8000
		wty:vbmeta_vendor.fex   :       4096 bytes @ +0x768e8400
		wty:Vvbmeta_vendor.fex  :          4 bytes @ +0x768e9400
		wty:dtbo.fex            :    2097152 bytes @ +0x768e9800
		wty:Vdtbo.fex           :          4 bytes @ +0x76ae9800
@ 542: boot0: Allwinner boot0
	size: 61440 bytes
	eGON checksum matches: 0xbf64ad3a
	DRAM parameters:	A64		H616
		DRAM clock  :       0x288       0x288           -
		DRAM type   :         0x3         0x3           -
		ZQ value    :   0x3030303           -           -
		ODT enabled :   0xe0e0e0e         0x1           -
		DX ODT      :           -   0x3030303           -
		DX DRI      :           -   0xe0e0e0e           -
		CA DRI      :           -      0x1f12           -
		PARA1       :      0x1f12      0x30fb           -
		PARA2       :         0x1           0           -
		MR0         :      0x30fb       0x840           -
		MR1         :           0         0x4           -
		MR2         :       0x840         0x8           -
		MR3         :         0x4           0           -
		TPR0        :         0x8  0xc0001002           -
		TPR6        :           0  0x33808080           -
		TRP10       :           0    0x2f1107           -
		TRP11       :           0  0xddddcccc           -
		TRP12       :  0xc0001002  0xeddc7665           -
		TRP13       :           0        0x40           -

 

The Dram settings where the same so I didn't have to edit the U-boot patch.

https://github.com/NickAlilovic/build/blob/main/patch/u-boot/u-boot-sunxi/configs-Transpeed-8K618-T-Add-Transpeed-8K618-T-board-support.patch 

+CONFIG_DRAM_SUN50I_H616_DX_ODT=0x03030303
+CONFIG_DRAM_SUN50I_H616_DX_DRI=0x0e0e0e0e
+CONFIG_DRAM_SUN50I_H616_CA_DRI=0x1f12
+CONFIG_DRAM_SUN50I_H616_TPR0=0xc0001002
+CONFIG_DRAM_SUN50I_H616_TPR10=0x2f1107
+CONFIG_DRAM_SUN50I_H616_TPR11=0xddddcccc
+CONFIG_DRAM_SUN50I_H616_TPR12=0xeddc7665
+CONFIG_MACH_SUN50I_H616=y
+CONFIG_SUNXI_DRAM_H616_DDR3_1333=y
+CONFIG_DRAM_CLK=648

 

My 8K618-T image won't work because these values were different. MMC errors means your box won't boot past U-boot and load a kernel. So you won't get hdmi output, no sound, no wifi, no bluetooth. This is why it's important to have uart installed.

 

X98H mmc:

Android dts

cd-gpios = <0x23 0x05 0x06 0x11>;

 

Armbian dts

cd-gpios = <&pio 5 6 GPIO_ACTIVE_LOW>;    /* PF6 */ 

 

 

8K618-T mmc:

Android dts

cd-gpios = <0x23 0x08 0x10 0x11>;

 

Armbian dts

cd-gpios = <&pio 8 16 GPIO_ACTIVE_LOW>;    /* PI16 */

  

U-Boot SPL 2024.01-armbian (May 09 2024 - 19:55:37 -0400)
DRAM: 2048 MiB
Trying to boot from MMC1
NOTICE:  BL31: v2.10.2(debug):armbian
NOTICE:  BL31: Built : 19:53:26, May  9 2024
NOTICE:  BL31: Detected Allwinner H616 SoC (1823)
NOTICE:  BL31: Found U-Boot DTB at 0x4a0a0648, model: Transpeed 8K618-T
INFO:    ARM GICv2 driver initialized
INFO:    Configuring SPC Controller
INFO:    PMIC: Probing AXP305 on RSB
ERROR:   RSB: set run-time address: 0x10003
INFO:    Could not init RSB: -65539
INFO:    BL31: Platform setup done
INFO:    BL31: Initializing runtime services
INFO:    BL31: cortex_a53: CPU workaround for erratum 855873 was applied
INFO:    BL31: cortex_a53: CPU workaround for erratum 1530924 was applied
INFO:    PSCI: Suspend is unavailable
INFO:    BL31: Preparing for EL3 exit to normal world
INFO:    Entry point address = 0x4a000000
INFO:    SPSR = 0x3c9
INFO:    Changed devicetree.
ns16550_serial serial@5000000: pinctrl_select_state_full: uclass_get_device_by_phandle_id: err=-19


U-Boot 2024.01-armbian (May 09 2024 - 19:55:37 -0400) Allwinner Technology

CPU:   Allwinner H616 (SUN50I)
Model: Transpeed 8K618-T
DRAM:  2 GiB
Core:  61 devices, 22 uclasses, devicetree: separate
WDT:   Not starting watchdog@30090a0
MMC:   mmc@4020000: 0, mmc@4022000: 1
Loading Environment from FAT... MMC: no card present
** Bad device specification mmc 0 **
In:    serial@5000000
Out:   serial@5000000
Err:   serial@5000000
Net:   apply fix for AC300 ephy bb version bug ...
using AC300 emac1 ephy fixed config ...
eth0: ethernet@5030000
starting USB...
Bus usb@5101000: sun4i_usb_phy phy@5100400: External vbus detected, not enabling our own vbus
USB EHCI 1.00
Bus usb@5101400: USB OHCI 1.0
Bus usb@5200000: USB EHCI 1.00
Bus usb@5200400: USB OHCI 1.0
scanning bus usb@5101000 for devices... 1 USB Device(s) found
scanning bus usb@5101400 for devices... 1 USB Device(s) found
scanning bus usb@5200000 for devices... 1 USB Device(s) found
scanning bus usb@5200400 for devices... 1 USB Device(s) found
       scanning usb for storage devices... 0 Storage Device(s) found
Autoboot in 1 seconds, press <Space> to stop
MMC: no card present
switch to partitions #0, OK
mmc1(part 0) is current device
Scanning mmc 1:1...
MMC: no card present
No EFI system partition
No EFI system partition
Failed to persist EFI variables
BootOrder not defined
EFI boot manager: Cannot load any image

Device 0: unknown device
ethernet@5030000 Waiting for PHY auto negotiation to complete......... TIMEOUT !
missing environment variable: pxeuuid
Retrieving file: pxelinux.cfg/01-02-00-70-41-af-ea
ethernet@5030000 Waiting for PHY auto negotiation to complete......... TIMEOUT !
Retrieving file: pxelinux.cfg/00000000
ethernet@5030000 Waiting for PHY auto negotiation to complete......... TIMEOUT !
Retrieving file: pxelinux.cfg/0000000
ethernet@5030000 Waiting for PHY auto negotiation to complete......... TIMEOUT !
Retrieving file: pxelinux.cfg/000000
ethernet@5030000 Waiting for PHY auto negotiation to complete......... TIMEOUT !
Retrieving file: pxelinux.cfg/00000
ethernet@5030000 Waiting for PHY auto negotiation to complete......... TIMEOUT !
Retrieving file: pxelinux.cfg/0000
ethernet@5030000 Waiting for PHY auto negotiation to complete......... TIMEOUT !
Retrieving file: pxelinux.cfg/000
ethernet@5030000 Waiting for PHY auto negotiation to complete......... TIMEOUT !
Retrieving file: pxelinux.cfg/00
ethernet@5030000 Waiting for PHY auto negotiation to complete......... TIMEOUT !

 

A quick and easy way to fix this is to edit the one line in my patch. (Or whatever device dts patch that worked for you)

https://github.com/NickAlilovic/build/blob/main/patch/kernel/archive/sunxi-6.7/patches.armbian/arm64-dts-allwinner-h618-add-Transpeed-8K618-T-TV-box.patch

  

+&mmc0 {
+	vmmc-supply = <&reg_dldo1>;
+	cd-gpios = <&pio 8 16 GPIO_ACTIVE_LOW>;	/* PI16 */
+	bus-width = <4>;
+	status = "okay";
+};

 

If you need to add more lines then you would have follow my instructions at the bottom of page 2. (Note: the branch names may of changed "linux-6.7.y" and "v2024.01" for the format-patch command. Use "git branch --show-current" for the new branch name.)

 

You can't just add an Android DTS and hope it works. There's been a lot of changes to the linux kernel since than. You need to port the values to the latest Mainline kernel code. 

You can find examples here. (Look for DTS in patch file name. 0647-arm64-dts-allwinner-h618-add-vontar-h618-TVbox.patch)

 

 https://github.com/torvalds/linux/tree/master/arch/arm64/boot/dts/allwinner

https://github.com/warpme/minimyth2/tree/master/script/kernel/linux-6.9/files

https://github.com/NickAlilovic/build/tree/main/patch/kernel/archive/sunxi-6.7/patches.armbian

Edited by Nick A
0
kil

kil

Posted
Posted (edited)
  On 5/25/2024 at 11:12 AM, Nick A said:

Sorry Kil, I don't have your box and time to do this for you. I can only provide information. Without console output there's nothing I can do. Are you using baud rate 115200?

Expand  

 

@Nick A Yes, I used 115200, and validated with android boot process, that the console is working. I can also confirm, I tried different images (including miniarch), none of them gave any console output.

 

I also studied the boot process and the the power distribution. My deduction is that at booting phase the SD card correctly gets the 3.3V power, and few of the AXP305 DCDC converters are initialized in a way, that H616 is able to start its booting proces, just pressing the "UBOOT" button finally ends in FEL mode.

 

E.g. command "lsusb" gives back, if the tv box is connected to the host PC to the correct USB port (thus powered only from the same USB):

  

Bus 001 Device 005: ID 1f3a:efe8 Allwinner Technology sunxi SoC OTG connector in FEL/flashing mode

 

Downloading sunxi-tools (either compiling it starting from "git clone https://github.com/linux-sunxi/sunxi-tools" or installing  it with "sudo apt install sunxi-tools"), that is able to work with it, like command "sunxi-fel ver" echoes back message:

  

AWUSBFEX soc=00001823(H616) 00000001 ver=0001 44 08 scratchpad=00007e00 00000000 00000000

 

Building the tool from source gives the benefit, that it provides some other SPL test images too, like "uart0-helloworld-sdboot.sunxi" (attached).  And command "sunxi-fel spl uart0-helloworld-sdboot.sunxi"  adds the following message on the console (!):

  

Hello from Allwinner H616!
Returning back to FEL.

 

This uart test image shows correctly the "eGON" footprint in the header, and it is assumed, it can be put to the SPL position to an SD card, and booting from SD should also give then the above "Hello" message to the console output, but that does not happen in my case. I have learned that in case of H616 SoC, the SD card should contain the SPL code at 8K offset (this is valid also for the armbian or miniarch images), so I prepared my SD with the following two commands :

  

dd if=/dev/zero of=/dev/sdb bs=1024 count=1024
dd if=uart0-helloworld-sdboot.sunxi of=/dev/sdb bs=1024 seek=8

 

First command is optional, it only clears the beginning of SD card, including the partition table, second is doing the actual SPL patching to the SD, which was /dev/sdb in my case). I tried to put the "Hello" SPL test program to an existing distribution, but that did not help either.

 

After all I have a suspicion, that SD Card boot process may be disabled in T95H, and the "U-Boot" button is usable to put the device into FEL mode... 

 

Could someone test - who has uart console output and surely working SD booting, that putting the "uart0-helloworld-sdboot.sunxi" to SD gives "Hello" message on the console output? Theoretically the sample application works with many types of Allwinner SoCs (including [A10/A20/H3]/H6/H616/H618 etc, you can see it from the sample image, but of course, the attached one is compiled to 64bit ARM architecture only, thus 32bit version needs to be recompiled from source.) This would justify my suspicion...

 

Or did I do something in a wrong way?

 

uart0-helloworld-sdboot.sunxiUnavailable

Edited by kil
0
Kajen

Kajen

Posted
Posted

hi @jernej, can you help me?

 

I want to have HDMI output, but I got error on "sun4i-drm display-engine: [drm] Cannot find any crtc or sizes", so I forced hdmi output with video=HDMI-A-1:1920x1080@60e on armbianEnv.txt, but now I have "sun8i-dw-hdmi 6000000.hdmi: PHY PLL failed to lock"

 

here is the dmesg, I also added some log

  Reveal hidden contents

 

0001-add-dts-t98-616.patchFetching info... uboot.patchFetching info...

0
kil

kil

Posted
Posted
  On 6/14/2024 at 9:34 PM, Nick A said:

I think your problem has to do with boot rom security.

Expand  

 

@Nick A You were right. Finally I needed to change u-boot ARM option to "SPL Image Type (TOC0 (secure))" from "eGON", and to generate a pem key for the u-boot image build process. I also added a T95H specific DTB for powering up the DRAM and I try to play with u-boot patched orange pi zero2 sd card. At least I have the first signs of sd-card boot process on serial console already!

  

U-Boot SPL 2024.04 (Jun 19 2024 - 10:00:07 +0000)
DRAM: 4096 MiB
Trying to boot from MMC1
NOTICE:  BL31: v2.11.0(debug):v2.11.0-156-gef5181975
NOTICE:  BL31: Built : 09:54:52, Jun 19 2024
NOTICE:  BL31: Detected Allwinner H616 SoC (1823)
NOTICE:  BL31: Found U-Boot DTB at 0x4a09c6c8, model: T95H
INFO:    ARM GICv2 driver initialized
INFO:    Configuring SPC Controller
INFO:    PMIC: Probing AXP305 on RSB
INFO:    PMIC: aldo1 voltage: 3.300V
INFO:    PMIC: aldo2 voltage: 3.300V
INFO:    PMIC: aldo3 voltage: 3.300V
INFO:    PMIC: bldo1 voltage: 1.800V
INFO:    PMIC: dcdcd voltage: 1.500V
INFO:    BL31: Platform setup done
INFO:    BL31: Initializing runtime services
INFO:    BL31: cortex_a53: CPU workaround for erratum 855873 was applied
INFO:    BL31: cortex_a53: CPU workaround for erratum 1530924 was applied
INFO:    PSCI: Suspend is unavailable
INFO:    BL31: Preparing for EL3 exit to normal world
INFO:    Entry point address = 0x4a000000
INFO:    SPSR = 0x3c9
INFO:    Changed devicetree.

 

This "Changed devicetree" is the last message, and further booting is not showing up. Is this last message is coming already after the 64bit execution switch? Or is it still some DTB or other issue?

0
kil

kil

Posted
Posted

@Nick A Oh, with a fresh rebuild of u-boot image, SPL can start the next u-boot part, but there are other errors (MMC is not seen, and 2G RAM exists instead of 4G).

  

U-Boot 2024.04 (Jun 19 2024 - 15:16:15 +0000) Allwinner Technology

CPU:   Allwinner H616 (SUN50I)
Model: T95H
DRAM:  2 GiB
Core:  48 devices, 18 uclasses, devicetree: separate
WDT:   Not starting watchdog@30090a0
MMC:   mmc@4020000: 0
Loading Environment from FAT... MMC: no card present
** Bad device specification mmc 0 **
In:    serial@5000000
Out:   serial@5000000
Err:   serial@5000000
Net:   No ethernet found.
starting USB...
Bus usb@5200000: USB EHCI 1.00
Bus usb@5200400: USB OHCI 1.0
scanning bus usb@5200000 for devices... 1 USB Device(s) found
scanning bus usb@5200400 for devices... 1 USB Device(s) found
       scanning usb for storage devices... 0 Storage Device(s) found
Hit any key to stop autoboot:  0
MMC: no card present

Device 0: unknown device
No ethernet found.
missing environment variable: pxeuuid
Retrieving file: pxelinux.cfg/00000000
No ethernet found.
Retrieving file: pxelinux.cfg/0000000
No ethernet found.
Retrieving file: pxelinux.cfg/000000
No ethernet found.
Retrieving file: pxelinux.cfg/00000
No ethernet found.
Retrieving file: pxelinux.cfg/0000
No ethernet found.
Retrieving file: pxelinux.cfg/000
No ethernet found.
Retrieving file: pxelinux.cfg/00
No ethernet found.
Retrieving file: pxelinux.cfg/0
No ethernet found.
Retrieving file: pxelinux.cfg/default-arm-sunxi-sunxi
No ethernet found.
Retrieving file: pxelinux.cfg/default-arm-sunxi
No ethernet found.
Retrieving file: pxelinux.cfg/default-arm
No ethernet found.
Retrieving file: pxelinux.cfg/default
No ethernet found.
Config file not found
No ethernet found.
No ethernet found.
=>

 

0
kil

kil

Posted
Posted

@Nick A And even more... noticing, that USB tree is detected, I added an extra USB stick with MiniArch image, changing root partition from /dev/mmcblk0p2 to /dev/sda2, and MiniArch has been booted: 

U-Boot 2024.04 (Jun 19 2024 - 15:16:15 +0000) Allwinner Technology

CPU:   Allwinner H616 (SUN50I)
Model: T95H
DRAM:  2 GiB
Core:  48 devices, 18 uclasses, devicetree: separate
WDT:   Not starting watchdog@30090a0
MMC:   mmc@4020000: 0
Loading Environment from FAT... MMC: no card present
** Bad device specification mmc 0 **
In:    serial@5000000
Out:   serial@5000000
Err:   serial@5000000
Net:   No ethernet found.
starting USB...
Bus usb@5200000: USB EHCI 1.00
Bus usb@5200400: USB OHCI 1.0
scanning bus usb@5200000 for devices... 2 USB Device(s) found
scanning bus usb@5200400 for devices... 1 USB Device(s) found
       scanning usb for storage devices... 1 Storage Device(s) found
Hit any key to stop autoboot:  0
MMC: no card present

Device 0: Vendor: Mass     Rev: 1.00 Prod: Storage Device
            Type: Removable Hard Disk
            Capacity: 1886.0 MB = 1.8 GB (3862528 x 512)
... is now current device
Scanning usb 0:1...
Found /extlinux/extlinux.conf
Retrieving file: /extlinux/extlinux.conf
1:      MiniMyth2
Retrieving file: /Image
append: root=/dev/sda2 rw rootwait earlycon console=ttyS0,115200n8 loglevel=6 consoleblank=0 fsck.mode=auto fsck.repair=yes
Retrieving file: /dtbs/allwinner/sun50i-h616-t95h.dtb
Moving Image from 0x40080000 to 0x40200000, end=42430000
## Flattened Device Tree blob at 4fa00000
   Booting using the fdt blob at 0x4fa00000
Working FDT set to 4fa00000
   Loading Device Tree to 0000000049ff8000, end 0000000049fffd1f ... OK
Working FDT set to 49ff8000

Starting kernel ...

[    0.000000] Linux version 6.9.3 (piotro@minimyth2-aarch64) (aarch64-minimyth-linux-gnu-gcc (GCC) 14.1.0, GNU ld (GNU Binutils) 2.40) #1 SMP PREEMPT Sat Jun  1 18:06:41 CEST 2024
[    0.000000] Kernel command line: root=/dev/sda2 rw rootwait earlycon console=ttyS0,115200n8 loglevel=6 consoleblank=0 fsck.mode=auto fsck.repair=yes
[    0.001796] cacheinfo: Unable to detect cache hierarchy for CPU 0
[    0.034222] audit: type=2000 audit(0.026:1): state=initialized audit_enabled=0 res=1
[    0.058004] SCSI subsystem initialized
...
[  OK  ] Finished Permit User Sessions.
[  OK  ] Started Getty on tty1.
[  OK  ] Started Serial Getty on ttyS0.
[  OK  ] Reached target Login Prompts.
[  OK  ] Started User Login Management.
[  OK  ] Started D-Bus System Message Bus.
[  OK  ] Reached target Multi-User System.
[  OK  ] Reached target Graphical Interface.

Arch Linux 6.9.3 (ttyS0)

alarm login:

 

I think I need to find/make a good dtb, and MMC boot will also work...

 

So linux can work on T95H!!!

0
Nick A

Nick A

Posted
Posted (edited)

Looking at your Android DTS for sdc0.           

cd-gpios = <0x00000053 0x00000008 0x00000010 0x00000006 0x00000001 0x00000003 0xffffffff>;

 

I'm pretty sure your Linux DTS for mmc0 should be.

cd-gpios = <&pio 8 16 GPIO_ACTIVE_LOW>;    /* PI16 */

 

 

Not sure why there's so many hex numbers. But looking at Pine64 Android DTS for sdc0. 

https://github.com/ayufan-pine64/device-pine64-common/blob/master/bootloader/pine64/sun50i-a64-pine64-plus.dts

cd-gpios = <0x00000030 0x00000005 0x00000006 0x00000000 0x00000001 0x00000002 0xffffffff>;

 

Linux DTS for mmc0 shows.

https://github.com/torvalds/linux/blob/master/arch/arm64/boot/dts/allwinner/sun50i-a64-pine64.dts

cd-gpios = <&pio 5 6 GPIO_ACTIVE_LOW>;

 

Remember to add these changes to both your u-boot and linux DTS.

Edited by Nick A
0
kil

kil

Posted
Posted
  On 6/20/2024 at 1:01 AM, Nick A said:

I'm pretty sure your Linux DTS for mmc0 should be.

cd-gpios = <&pio 8 16 GPIO_ACTIVE_LOW>;    /* PI16 */

Expand  

 

@Nick A Thank you! It was in the way, you wrote! Changing cd-gpios from "5 6" to "8 16" solved the MMC booting issue!

  

U-Boot 2024.04 (Jun 20 2024 - 07:34:25 +0000) Allwinner Technology

CPU:   Allwinner H616 (SUN50I)
Model: T95H
DRAM:  2 GiB
Core:  48 devices, 18 uclasses, devicetree: separate
WDT:   Not starting watchdog@30090a0
MMC:   mmc@4020000: 0
Loading Environment from FAT... Unable to read "uboot.env" from mmc0:1...
In:    serial@5000000
Out:   serial@5000000
Err:   serial@5000000
Net:   No ethernet found.
starting USB...
Bus usb@5200000: USB EHCI 1.00
Bus usb@5200400: USB OHCI 1.0
scanning bus usb@5200000 for devices... 1 USB Device(s) found
scanning bus usb@5200400 for devices... 1 USB Device(s) found
       scanning usb for storage devices... 0 Storage Device(s) found
Hit any key to stop autoboot:  0
switch to partitions #0, OK
mmc0 is current device
Scanning mmc 0:1...
Found /extlinux/extlinux.conf
Retrieving file: /extlinux/extlinux.conf

 

Next step is to have the total 4 GiB RAM and working network! I wish I understood better the DTS/DTB world!

0
Rodrigo Campos

Rodrigo Campos

Posted
Posted (edited)

Hi @kil, I have a Transpeed M98 with the same problem as yours T95H, this secure boot option, but different than you, I can't understood what to do in the links informed by Nick A. It's my fault, because I have a limitate knowledge in English. Can you help me with the exact steps you made to put the image to work in the SD card?

 

Thanks in advance.

Edited by Rodrigo Campos
0
Nick A

Nick A

Posted
Posted (edited)

I haven''t done this before but I think you need to follow these instructions to compile u-boot with TOC0 support. I'm guessing the deconfig needs "CONFIG_SPL_IMAGE_TYPE_SUNXI_TOC0=y".

 

https://github.com/NickAlilovic/build/blob/main/patch/u-boot/u-boot-sunxi/configs-Transpeed-8K618-T-Add-Transpeed-8K618-T-board-support.patch

 

You probably want to change the makeimage command to option  "-A arm64"

 

https://linux-sunxi.org/TOC0#TOC0_images_generation

 

Here's more information on building  u-boot

https://linux-sunxi.org/U-Boot

Edited by Nick A
0
rick0cm

rick0cm

Posted
Posted

Hi,

 

I have a couple of the "Transpeed 8K" boxes, and have been able to actually productively use

them using the MiniArch distribution.  I'm booting of a uSD card and running from the uSD.

 

I can see the 32G emmc that is on the boards, but have left it untouched so far.

 

Question - has anyone successfully overwritten a known working image - like MiniArch  -

onto the emmc and booted and run off of it?  The emmc ought to be alot faster than uSD.

 

I don't want to risk bricking the boxes.  There are alot of tiny partitions on the emmc, (see below)

and I am kind of paranoid one of them is some sort of required bootloader.

Any idea how risky overwriting the emmc is?

 

Thanks..  Rick

 

  Quote

## This is the uSD w/ MiniArch

$ fdisk -l /dev/mmcblk0
Disk /dev/mmcblk0: 58.59 GiB, 62914560000 bytes, 122880000 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x346d1a6a

Device         Boot   Start       End   Sectors   Size Id Type
/dev/mmcblk0p1 *      32768    373553    340786 166.4M  c W95 FAT32 (LBA)
/dev/mmcblk0p2       374784   3510487   3135704   7.5G 83 Linux
/dev/mmcblk0p3      3510488 122879999 119369512  50.9G 83 Linux

 

## This is the EMMC with the original TV Box firmware

$ fdisk -l /dev/mmcblk2
Disk /dev/mmcblk2: 29.12 GiB, 31268536320 bytes, 61071360 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: AB6F3888-569A-4926-9668-80941DCB40BC

Device            Start      End  Sectors  Size Type
/dev/mmcblk2p1    73728   139263    65536   32M Microsoft basic data
/dev/mmcblk2p2   139264   204799    65536   32M Microsoft basic data
/dev/mmcblk2p3   204800   205311      512  256K Microsoft basic data
/dev/mmcblk2p4   205312   205823      512  256K Microsoft basic data
/dev/mmcblk2p5   205824   336895   131072   64M Microsoft basic data
/dev/mmcblk2p6   336896   467967   131072   64M Microsoft basic data
/dev/mmcblk2p7   467968   533503    65536   32M Microsoft basic data
/dev/mmcblk2p8   533504   599039    65536   32M Microsoft basic data
/dev/mmcblk2p9   599040  6890495  6291456    3G Microsoft basic data
/dev/mmcblk2p10 6890496  6923263    32768   16M Microsoft basic data
/dev/mmcblk2p11 6923264  6923519      256  128K Microsoft basic data
/dev/mmcblk2p12 6923520  6923775      256  128K Microsoft basic data
/dev/mmcblk2p13 6923776  6923903      128   64K Microsoft basic data
/dev/mmcblk2p14 6923904  6924031      128   64K Microsoft basic data
/dev/mmcblk2p15 6924032  6924159      128   64K Microsoft basic data
/dev/mmcblk2p16 6924160  6924287      128   64K Microsoft basic data
/dev/mmcblk2p17 6924288  6925311     1024  512K Microsoft basic data
/dev/mmcblk2p18 6925312  6956031    30720   15M Microsoft basic data
/dev/mmcblk2p19 6956032  6988799    32768   16M Microsoft basic data
/dev/mmcblk2p20 6988800  7021567    32768   16M Microsoft basic data
/dev/mmcblk2p21 7021568  7025663     4096    2M Microsoft basic data
/dev/mmcblk2p22 7025664  7029759     4096    2M Microsoft basic data
/dev/mmcblk2p23 7029760  7062527    32768   16M Microsoft basic data
/dev/mmcblk2p24 7062528  7095295    32768   16M Microsoft basic data
/dev/mmcblk2p25 7095296 61071326 53976031 25.7G Microsoft basic data

Expand  

 

0
SteeMan

SteeMan

Posted
Posted
  On 7/13/2024 at 7:20 PM, rick0cm said:

Hi,

 

I have a couple of the "Transpeed 8K" boxes, and have been able to actually productively use

them using the MiniArch distribution

Expand  

These forums are for Armbian not for the discussion of other distributions.  It would be more appropriate to post this in a forum dedicated to MiniArch.

0
Rodrigo Campos

Rodrigo Campos

Posted
Posted
  Quote

I haven''t done this before but I think you need to follow these instructions to compile u-boot with TOC0 support. I'm guessing the deconfig needs "CONFIG_SPL_IMAGE_TYPE_SUNXI_TOC0=y".

Expand  

Hi @Nick A, thanks for your answer. The @kil already give me the path in private massage (He tell me that for any reason his messages in here were not working). The step I skip was "At uboot build step "make menuconfig" I changed one option inside "ARM architecture" from "SPL Image Type (eGON (normal))" to "SPL Image Type (TOC0 (secure))"" that I think is the same as change the .config file and change CONFIG_SPL_IMAGE_TYPE_SUNXI_TOC0=y as you say.

Now the u-boot is starting and give the wart logo. So I used your last image with this u-boot, but it stopped in "Starting kernel" I tried other images, some stopped in Kernel Panic others with some other errors, but none of them booted all the system.

I still don't have HDMI image, but I see in your past messages that I have to put some patches in u-boot. I still don't know how to do it, but I'm still reading and trying.

BTW I tried the miniArch that I had kernel panic or other error that I don't remember exactly.

 

Best regards

0
Nick A

Nick A

Posted
Posted (edited)

Hey Rick, Try using the ddbr command to backup your emmc . I added a patch to boot off emmc I got from MiniArch. I haven't tried it yet personally. Too busy with work. But someone posted a while back that it works. 

 

 

Edited by Nick A
0
kil

kil

Posted
Posted

Armbian is also working on T95H box! HW is partly recognized, but now I am able to log in through network!

 

What I did was following a standard uboot build process plus turning on the security I did practically two extra steps:

 
1) Uboot security build process required a private key, which was searched under file name "root_key.pem" from the u-boot build folder (maybe root prefix is coming from the fact that I built the image under root user?). The key file was created with openssl command, if I can recall correctly in this way:

  

openssl genrsa -out root_key.pem

 

2) At uboot build step "make menuconfig" I changed one option inside "ARM architecture" from "SPL Image Type (eGON (normal))" to "SPL Image Type (TOC0 (secure))"!

 

After this uboot build generated "u-boot-sunxi-with-spl.bin" file contains the security requirements.

 

I made my final SD Card by patching an existing linux distribution with the above u-boot, and suitable DTB file into the boot folder. I am playing lately with the T95H hardware close OrangePi Zero 2 image (same SoC: H616, and same power control: AXP305), namely  Armbian_24.5.1_Orangepizero2_noble_current_6.6.31.img. I wrote a new SD Card with that image first.

 

Then I patched it with the compiled uboot (/dev/sdb is the SD card device on my linux PC):

  

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

 

Then I mounted the sd image partition and added my DTB file into the boot folder (I mounted the SD partition to /s/b1 folder), and for safety reasons I also overwrote the orangepi specific DTB file (sun50i-h616-orangepi-zero2.dtb) with mine, in case if that were referred.  At this phase I used my u-boot built dtb file still.

  

mount /dev/sdb1 /s/b1
cp sun50i-h616-t95h.dtb /s/b1/boot/dtb/allwinner/
chmod +x /s/b1/boot/dtb/allwinner/sun50i-h616-t95h.dtb
cp /s/b1/boot/dtb/allwinner/sun50i-h616-t95h.dtb /s/b1/boot/dtb/allwinner/sun50i-h616-orangepi-zero2.dtb
umount /dev/sdb1

 

I inserted that SD card into T95H, and after powering up the board the Armbian image was booted ( without pressing the uboot button behind the AV hole). I could log in using the console:


  

U-Boot SPL 2024.04 (Jun 24 2024 - 07:12:54 +0000)
DRAM: 4096 MiB
Trying to boot from MMC1
NOTICE:  BL31: v2.11.0(debug):v2.11.0-156-gef5181975
NOTICE:  BL31: Built : 14:39:25, Jun 19 2024
NOTICE:  BL31: Detected Allwinner H616 SoC (1823)
NOTICE:  BL31: Found U-Boot DTB at 0x4a09c550, model: T95H
INFO:    ARM GICv2 driver initialized
INFO:    Configuring SPC Controller
INFO:    PMIC: Probing AXP305 on RSB
INFO:    PMIC: aldo1 voltage: 3.300V
INFO:    PMIC: aldo2 voltage: 3.300V
INFO:    PMIC: aldo3 voltage: 3.300V
INFO:    PMIC: bldo1 voltage: 1.800V
INFO:    PMIC: dcdcd voltage: 1.500V
INFO:    BL31: Platform setup done
INFO:    BL31: Initializing runtime services
INFO:    BL31: cortex_a53: CPU workaround for erratum 855873 was applied
INFO:    BL31: cortex_a53: CPU workaround for erratum 1530924 was applied
INFO:    PSCI: Suspend is unavailable
INFO:    BL31: Preparing for EL3 exit to normal world
INFO:    Entry point address = 0x4a000000
INFO:    SPSR = 0x3c9
INFO:    Changed devicetree.


U-Boot 2024.04 (Jun 24 2024 - 07:12:54 +0000) Allwinner Technology

CPU:   Allwinner H616 (SUN50I)
Model: T95H
DRAM:  2 GiB
Core:  49 devices, 18 uclasses, devicetree: separate
WDT:   Not starting watchdog@30090a0
MMC:   mmc@4020000: 0
Loading Environment from FAT... Unable to use mmc 0:1...
In:    serial@5000000
Out:   serial@5000000
Err:   serial@5000000
Net:   No ethernet found.
starting USB...
Bus usb@5200000: USB EHCI 1.00
Bus usb@5200400: USB OHCI 1.0
scanning bus usb@5200000 for devices... 1 USB Device(s) found
scanning bus usb@5200400 for devices... 1 USB Device(s) found
       scanning usb for storage devices... 0 Storage Device(s) 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
3259 bytes read in 3 ms (1 MiB/s)
## Executing script at 4fc00000
U-boot loaded from SD
Boot script loaded from mmc
178 bytes read in 3 ms (57.6 KiB/s)
20384 bytes read in 7 ms (2.8 MiB/s)
Working FDT set to 4fa00000
Failed to load '/boot/dtb/allwinner/overlay/-fixup.scr'
17977207 bytes read in 744 ms (23 MiB/s)
23445512 bytes read in 969 ms (23.1 MiB/s)
Moving Image from 0x40080000 to 0x40200000, end=418f0000
## Loading init Ramdisk from Legacy Image at 4ff00000 ...
   Image Name:   uInitrd
   Image Type:   AArch64 Linux RAMDisk Image (gzip compressed)
   Data Size:    17977143 Bytes = 17.1 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
## Flattened Device Tree blob at 4fa00000
   Booting using the fdt blob at 0x4fa00000
Working FDT set to 4fa00000
   Loading Ramdisk to 48edb000, end 49ffff37 ... OK
   Loading Device Tree to 0000000048e6d000, end 0000000048edafff ... OK
Working FDT set to 48e6d000

Starting kernel ...

done.
Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done.
Begin: Running /scripts/local-premount ... Scanning for Btrfs filesystems
done.
Begin: Will now check root file system ... fsck from util-linux 2.39.3
[/usr/sbin/fsck.ext4 (1) -- /dev/mmcblk0p1] fsck.ext4 -a -C0 /dev/mmcblk0p1
armbi_root: clean, 43241/927360 files, 504145/3906560 blocks
done.
done.
Begin: Running /scripts/local-bottom ... done.
Begin: Running /scripts/init-bottom ... done.

Welcome to Armbian 24.5.1 noble!

-.mount
[  OK  ] Created slice system-modprobe.slice - Slice /system/modprobe.

....

[  OK  ] Finished systemd-user-sessions.service - Permit User Sessions.
systemd-user-sessions.service
         Starting plymouth-quit-wait.servic…d until boot process finishes up...
         Starting plymouth-quit.service - Terminate Plymouth Boot Screen...

Armbian 24.5.1 Noble ttyS0

orangepizero2 login: root
Password:
root@orangepizero2:~#

 

Later knowing that my board embedded network cards are not working (neither wifi nor wired ethernet), I added an RTL8188EU USB Wifi module, and could configure it for accessing my home network. SSH is configured too, and now I can log in to the box through network (e.g. with putty from my windows PC):

  

Using username "root".
Authenticating with public key "imported-openssh-key"
  ___  ____  _   _____             ____
 / _ \|  _ \(_) |__  /___ _ __ ___|___ \
| | | | |_) | |   / // _ \ '__/ _ \ __) |
| |_| |  __/| |  / /|  __/ | | (_) / __/
 \___/|_|   |_| /____\___|_|  \___/_____|

Welcome to Armbian 24.5.1 Noble with Linux 6.6.31-current-sunxi64

System load:   38%              Up time:       0 min
Memory usage:  6% of 1.88G      IP:            192.168.8.23
Usage of /:    4% of 57G
RX today:      1.0 MiB

[ 4 security updates available, 4 updates total: apt upgrade ]
Last check: 2024-07-10 07:58

[ General system configuration (beta): armbian-config ]

Last login: Wed Jul 10 06:31:40 2024 from 192.168.8.6
root@t95h:~#

 

ps: this message is posted later, earlier posts did not work

 

0
kil

kil

Posted
Posted

@Rodrigo Campos I could added my post now!

 

I can also confirm, that CONFIG_SPL_IMAGE_TYPE_SUNXI_TOC0=y is in the config file replaces the menuconfig changes I wrote previously.

 

Nice you have console messages now!!!

 

FYI: I had cases, that booting stopped at "Starting kernel ..." when I had bad dtb file in the boot partition! I mean the only difference between a working and nonworking case was the "/boot/dtb/allwinner/sun50i-h616-t95h.dtb" file.

 

0
Timmie Shepherd

Timmie Shepherd

Posted
Posted

https://armdev.pixeldrift.net/transpeed/8k618-t/ gives me a 404 error.

 

Also trying to build the kernel gives me this stupid error for almost any combination of options I try:

 

lib/test_fortify.log
[]     CC      lib/string.o
[]     AR      lib/lib.a
[]     CC [M]  kernel/kheaders.o
[]   make[2]: *** [Makefile:1923: .] Error 2
[]   make[1]: *** [/home/timbo303/build/cache/sources/linux-kernel-worktree/6.6__sunxi64__arm64/Makefile:359
: __build_one_by_one] Error 2
[]   make: *** [Makefile:234: __sub-make] Error 2
[] Cleaning up [ please wait for cleanups to finish ]
[] ANSI log file built; inspect it by running: [ less -RS output/logs/log-build-a2872f8d-6dc7-4a9e-a18a-eee4
c158a2a5.log.ans ]
[] Share log manually (or SHARE_LOG=yes): [ curl --data-binary @output/logs/log-build-a2872f8d-6dc7-4a9e-a18
a-eee4c158a2a5.log.ans https://paste.armbian.com/log ]

 

0
Rodrigo Campos

Rodrigo Campos

Posted
Posted

Hi @kil, Thanks for your new information, but I just tried all dtb files in dtb folder, but with no sucess. Even with the new compilation that Nick posted in last massage.

What I see was that with armbian, with any dtb file, it stops in "Starting kernel ..." and with miniarch the kernel ran, but stop with kernel panic.

I tried with orangepi armbian with the transpeed dtb with same result than Nick's image.

 

BTW, for any dont know, to change the dtb file that will be used you need to change the armbianEnv.txt and write in the end of the file a "fdtfile=" and the path for fdt filelike "fdtfile=/allwinner/sun50i-h618-transpeed-8k618-t.dtb"

 

above is my uart with armbian:

 

U-Boot 2024.07-rc5 (Jul 16 2024 - 11:41:56 -0300) Allwinner Technology

CPU:   Allwinner H616 (SUN50I)
Model: Transpeed 8K618-T
DRAM:  2 GiB
Core:  59 devices, 21 uclasses, devicetree: separate
WDT:   Not starting watchdog@30090a0
MMC:   mmc@4020000: 0, mmc@4022000: 1
Loading Environment from FAT... Unable to use mmc 0:1...
In:    serial@5000000
Out:   serial@5000000
Err:   serial@5000000
Net:   No ethernet found.
starting USB...
Bus usb@5101000: USB EHCI 1.00
Bus usb@5101400: USB OHCI 1.0
Bus usb@5200000: USB EHCI 1.00
Bus usb@5200400: USB OHCI 1.0
scanning bus usb@5101000 for devices... 1 USB Device(s) found
scanning bus usb@5101400 for devices... 1 USB Device(s) found
scanning bus usb@5200000 for devices... 1 USB Device(s) found
scanning bus usb@5200400 for devices... 1 USB Device(s) found
       scanning usb for storage devices... 0 Storage Device(s) 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
3259 bytes read in 2 ms (1.6 MiB/s)
## Executing script at 4fc00000
U-boot loaded from SD
Boot script loaded from mmc
209 bytes read in 2 ms (101.6 KiB/s)
35515 bytes read in 7 ms (4.8 MiB/s)
Working FDT set to 4fa00000
4203 bytes read in 6 ms (683.6 KiB/s)
Applying kernel provided DT fixup script (sun50i-h616-fixup.scr)
## Executing script at 45000000
18349552 bytes read in 765 ms (22.9 MiB/s)
23572488 bytes read in 982 ms (22.9 MiB/s)
Moving Image from 0x40080000 to 0x40200000, end=41910000
## Loading init Ramdisk from Legacy Image at 4ff00000 ...
   Image Name:   uInitrd
   Image Type:   AArch64 Linux RAMDisk Image (gzip compressed)
   Data Size:    18349488 Bytes = 17.5 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
## Flattened Device Tree blob at 4fa00000
   Booting using the fdt blob at 0x4fa00000
Working FDT set to 4fa00000
   Loading Ramdisk to 48e80000, end 49fffdb0 ... OK
   Loading Device Tree to 0000000048e0e000, end 0000000048e7ffff ... OK
Working FDT set to 48e0e000

Starting kernel ...

0
Nick A

Nick A

Posted
Posted (edited)

Something changed when loading the kernel.. It's not showing the output to your serial console. 

 

I'm pretty sure it's due to "plymouth.ignore-serial-consoles" in your /armbi_root/boot/boot.cmd

 

if test "${bootlogo}" = "true"; then
    setenv consoleargs "splash plymouth.ignore-serial-consoles ${consoleargs}"

 

 

edit /armbi_root/boot/armbianEnv.txt

 

change

bootlogo=true

to

bootlogo=false

 

 

Kernel panic could be due to incorrect Dram settings. 

 

Try extracting your Android boot_a.img, vendor_boot_a and dtbo_a.

Instructions at the bottom of this page.

 

You can also use https://github.com/apritzel/sunxi-fw to extract the dram settings. If you can find a firmware update for you box. 

Edited by Nick A
0
Rodrigo Campos

Rodrigo Campos

Posted
Posted

Thanks for your reply @Nick A, but my bootlogo is already false. My armbianEnv.txt contents is the above:

verbosity=1
bootlogo=false
console=both
disp_mode=1920x1080p60
overlay_prefix=sun50i-h616
rootdev=UUID=6de22aaf-f6c2-4ed0-9715-b931c3d7602d
rootfstype=ext4
fdtfile=/allwinner/sun50i-h618-transpeed-8k618-t.dtb

 

 

I extracted my android dts, but don't know what to do with it.

I think there are a problem in boot armbian and boot secure, because some other with same M98 plus like mine told that theirs worked with your image untouched.

Anyway I will attach my extracted dts file that is very similar than the one you posted here in page 5.

Unfortunately I thik that I will have to give up to put Armbian in my Transpeed M98 plus.

dtb.0.dtsFetching info...

0
Nick A

Nick A

Posted
Posted (edited)

Try changing the verbosity=1 to 7.

Or you can try this to get more debug information.

 

Some DTS would show the dram settings. This one doesn't. 

 

Is this your box?  

https://androidpctv.com/firmware-m98-8k-plus/

 

This firmware shows the same dram settings as the 8K618-T

 

rick0cm has a transpeed 8K618-T like mine but with a different wifi chip. Not all boxes are the same. 

 

The firmware above might be for M98 plus without secure boot. Maybe with different Ram chips. It would be better to extract your boot0 partition and figure out your dram settings. 

 

One last thing before you quit. I just want to see the kernel errors you are getting. You could be right about the secure boot being the problem.

 

You can always ask for help at #linux-sunxi IRC

https://oftc.irclog.whitequark.org/linux-sunxi/2024-07-19

Edited by Nick A
0

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.

×
 Share
Go to topic listing
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines

  I accept