x96q h313

[Alexander Zavaruev]

The second box. I received both with a non-working native Android. Under armbian built-in mmc is read only, I could not mount "boot" partition (unknown fs type?), so I did not manage to extract original android dts. What am I doing wrong?

[NotAMirage]

Hello everyone, does anyone have his image: https://github.com/NickAlilovic/build/releases/download/20250130/Armbian-unofficial_25.02.0-trunk_Q1_bookworm_edge_6.12.11_xfce_desktop.img.xz

I have an h313 board with 1.5Gb DRAM with secureboot

[Nick A]

You can find secure boot in that link. Also, we are having issues with 1.5g boards. You can read the latest posts in that thread.

Edited Tuesday at 08:23 PM by Nick A

[mdidis]

Goodmorning, I have a Q plus TV Box with the chip Allwinner H616 v2.0 in configuration RAM: 4GB eMMC: 64GB . This is what is written on the box, but not completely trusted because was said also H6, instead of H616 that's actually is. These are some images of the pcb. I have tried to flash some random armbian, but nothing seems to work. From ttl serial this is a part of log, and I don't know why is found only 1GB of DRAM.

https://i.ibb.co/1GSbZdRg/20250813-083105.jpg

https://i.ibb.co/rG4zZ0s6/20250813-083122.jpg
 

 

Which armbian you suggest to try out? If I start with pressing "UBOOT" button nothing appears on Serial console.

Thanks in advance to all who could help me

 

[344]DRAM BOOT DRIVE INFO: V0.645
[347]the chip id is 0x5000
[350]chip id check OK
[354]DRAM_VCC set to 1500 mv
[357]DRAM CLK =648 MHZ
[359]DRAM Type =3 (3:DDR3,4:DDR4,7:LPDDR3,8:LPDDR4)
[366]Actual DRAM SIZE =1024 M
[369]DRAM SIZE =1024 MBytes, para1 = 30eb, para2 = 4000000, dram_tpr13 = 6041
[378]DRAM simple test OK.
[380]rtc standby flag is 0x0, super standby flag is 0x0
[386]boot0 Nand0 clk: 10MHz,PERI=600,N=4,M=15,T=10
[391]boot0 Nand Ecc clk: 20MHz,PERI=600,N=2,M=15,T=20
[396]NB0 : nand phy init ok
[399]block from 4 to 11
[658]Check is correct.
[660]OLD version: 0.0
[663]NEW version: 0.0
[738]load rotpk hash
[801]load monitor-key hash
[803]load monitor hash
[1007]load boot-key hash
[1009]load boot hash
[1075]load vbmeta-key hash
[1077]load vbmeta hash
[1144]load recovery-key hash
[1147]load recovery hash
[1151]monitor entry=0x48000000
[1153]uboot entry=0x4a000000
[1156]optee entry=0x48600000
[1161]run out of boot0
NOTICE:  BL3-1: v1.0(debug):be96482
NOTICE:  BL3-1: Built : 18:32:32, 2021-04-21
NOTICE:  BL3-1 commit: 8
NOTICE:  cpuidle init version V1.0
NOTICE:  secure os exist
MESSAGE: [0x0] TEE-CORE: OP-TEE version: 5c40397e #1 Tue Feb  2 07:45:37 UTC 2021 arm
NOTICE:  BL3-1: Preparing for EL3 exit to normal world
NOTICE:  BL3-1: Next image address = 0x4a000000
NOTICE:  BL3-1: Next image spsr = 0x1d3

U-Boot 2018.05 (Oct 25 2021 - 08:42:07 +0800) Allwinner Technology

[01.251]CPU:   Allwinner Family
[01.253]Model: sun50iw9
I2C:   ready
[01.258]DRAM:  1 GiB
[01.261]Relocation Offset is: 35ec5000
[01.296]secure enable bit: 1
[01.299]pmu_axp152_probe pmic_bus_read fail
[01.303]PMU: AXP1530
[01.309]CPU=1008 MHz,PLL6=600 Mhz,AHB=200 Mhz, APB1=100Mhz  MBus=400Mhz

 

[Nick A]

@mdidis try the transpeed or x98h image. You might need to enable secure boot.

[mdidis]

11 minutes ago, Nick A said:

try the transpeed or x98h image

Thank you, will try asap.

 

11 minutes ago, Nick A said:

You might need to enable secure boot.

How can I do? 

Do you think is useful also 01_dtbdump_,sun50iw9.dtb that I have extracted through adb shell?

Edited Wednesday at 11:25 AM by mdidis

[Nick A]

https://github.com/NickAlilovic/build/releases/

[01.296]secure enable bit: 1

I see this in your android log so I believe you have to enable secure boot.

If the images don’t boot. These are the steps to enable secure boot for tanix_tx6s_axp313. (Link below)

[01.303]PMU: AXP1530

You have a axp313a so transpeed, x98h and tanix might work for you.

 

[359]DRAM Type =3 (3:DDR3,4:DDR4,7:LPDDR3,8:LPDDR4)
Transpeed, x98h and tanix use ddr3

 

If emmc or wifi do not work. You can use your android dts to find the gpio numbers. You might also need to take a picture of your wifi chip.

 

 

Edited Wednesday at 12:07 PM by Nick A

[mdidis]

20 hours ago, Nick A said:

If the images don’t boot. These are the steps to enable secure boot for tanix_tx6s_axp313. (Link below)

Thanks. I have tried and compiled image, but when I boot with SD card nothing appears, and Serial interface seems that disconnects. I have tried both with "uboot" button pressed and not.

 

These are, I think, the gpio you asked

		gpio_encrypt {
			compatible = "allwinner,gpio_encrypt";
			gpio_number_sun = <0x05>;
			gpio1_value = <0x00>;
			gpio2_value = <0x01>;
			gpio3_value = <0x01>;
			gpio4_value = <0x01>;
			gpio5_value = <0x01>;
			gpio1_pin = <0x53 0x08 0x0d 0x01 0xffffffff 0xffffffff 0x00>;
			gpio2_pin = <0x53 0x08 0x09 0x01 0xffffffff 0xffffffff 0x00>;
			gpio3_pin = <0x53 0x08 0x01 0x01 0xffffffff 0xffffffff 0x00>;
			gpio4_pin = <0x53 0x07 0x06 0x01 0xffffffff 0xffffffff 0x00>;
			gpio5_pin = <0x53 0x07 0x07 0x01 0xffffffff 0xffffffff 0x00>;
			status = "okay";
			linux,phandle = <0x17d>;
			phandle = <0x17d>;
		};  

or these ones?
 

		boot_init_gpio {
			device_type = "boot_init_gpio";
			status = "okay";
			gpio0 = <0x53 0x08 0x0b 0x01 0xffffffff 0xffffffff 0x00>;
			gpio1 = <0x53 0x08 0x0c 0x01 0xffffffff 0xffffffff 0x01>;
			gpio2 = <0x53 0x08 0x0e 0x01 0xffffffff 0xffffffff 0x00>;
		};

 

[Nick A]

@mdidisDid you compile with the secure boot patch? Because it sounds like that’s your issue. If secure boot is not enabled you won’t get any output from your serial interface.

 

post your dts. I’ll tell you the correct gpio for wifi and emmc.

 

 

[mdidis]

20 minutes ago, Nick A said:

Did you compile with the secure boot patch?

Yes, followed the guide you linked on the other thread. Here is my dts.
 

sun50iw9.dts

[Nick A]

@mdidis do non secure boot images show any output. The one posted is an android boot output.