Armbian for H313 X96-Q LPDDR3 TV-Box

[Nick A]

Your tv stick probably has secure boot enabled. You can compile a secure boot image using these steps.

 

 

[Randlin]

Nice! I'll try that. Thank you for your help so far. Finding the right documentation has been a little tricky for me and I really appreciate the help.

[Randlin]

Alright, I built the x96q-lpddr3 image using the patches suggested. It booted (partially). Nothing on the screen, but it is starting!
I chose that image because it is H313 and lpddr3 (the android uboot build that worked before detected it as such)
I attached the serial log. It's getting late here and I may not get much more done on this until Monday, but this is a good sign in my opinion.

uboot.txt

[Nick A]

H313/H616/H618 are pretty much the same SOC. It’s the AXP power management IC that’s different. Also RAM and WIFi chips are usually different.

 

https://linux-sunxi.org/AXP_PMICs

Edited Saturday at 12:08 AM by Nick A

[Randlin]

Cool, good to know. I'll try one with the same AXP and go from there.

[Randlin]

Hmm, according to the config, the X96q lpddr3 uses the AXP313 already. Maybe ram is wrong? Pretty sure it's lpddr3, if there is any way to check that, I can. Gonna do a little digging in android.

[Randlin]

According to Android uboot, DRAM_VCC= 1200mv
DRAM CLK =648 MHZ
DRAM TYPE=7 (lpddr3)
DRAM SIZE =1536 MBytes, para1 = 30fa, para2 = 6001000, dram_tpr13 = 26061
gonna try some of this in the x96q image, see what happens
 

[Randlin]

Hmm, in boot log I see AXP1530 mentioned in theandroid boot (booted off the sd card, not emmc). I attached the log.

bootinfo.txt

[Randlin]

I set the dram speed to 648, no difference. Gotta be the axp or another option.

[Nick A]

AXP1530 is the same as AXP313a. Take a look at the link I posted above. 
 

You could use this tool to extract your dram settings from an android update or boot0.bin. 
https://github.com/apritzel/sunxi-fw

 

sunxi-fw info -v boot0.bin

Edited 9 hours ago by Nick A

[Randlin]

Will do

[Randlin]

uboot-config-dump.txt Here it is

[Randlin]

I did notice in the log:
INFO:    PMIC: Probing AXP305 on RSB
ERROR:   RSB: set run-time address: 0x10003
INFO:    Could not init RSB: -65539

[Randlin]

Wait, that was the Linux kernel, not uboot. I'll get that

[Randlin]

/sunxi-fw info -v fulldisk.img 
@     0: mbr: DOS MBR
    protective MBR, GPT used
    GPT version 00010000
    usable disk size: 7419 MB
    number of partition entries: 17
@   16: toc0: signed boot image
    2 items
    size: 98304 bytes
@ 321: toc0: signed boot image
    2 items
    size: 98304 bytes
@26812: fit: U-Boot FIT image
    fit:__overlay__: "<no description>"
    fit:__overlay__: "<no description>"
    fit:fragment@2: "<no description>"

So I never dumped just boot0  (and no firmware update available), but I have full emmc dump named fulldisk.img.
I would assume it is the toc0?
Trying to extract does not work , however: (maybe because there are two?)

/sunxi-fw extract -v -n toc0 -o uboot0 /home/Tr/fulldisk.img 
unknown image file

extracting the mbr works fine though.

[Nick A]

This post should help extracting your boot.img from android. That’s if your box is already rooted.

[Randlin]

Oh, so it is the devicetree of Linux we want. My bad. Here it is: devicetree.txt
FYI I was able to use binwalk -e on the boot partition dump, nice to see there is another way. Thanks for all the help

Edited 8 hours ago by Randlin

[Nick A]

Actually in that post it was about downloading the boot_a partition. Then extracting the dts.. you can skip the dts extraction part for now. We need your boot_a partition.

 

also that’s not the android dts you posted. It has some info but not all of it.

Edited 6 hours ago by Nick A