Posts by bumerc

The values were not accepted. Replace aml_autoscript in the root directory with the attached script, then in the uboot terminal

run update

Quote

When boot to LE/CE with correct dtb it's the same, Beelink logo and SPIDF on/off.

When boot to LE/CE with wrong p212 dtb get LE/CE logo and SPIDF stay on.

sounds like a HW issue. Try to reduce the number of CPU cores gradually and see what happens..

use proper dtb

uboot terminal:

setenv maxcpus 6
run storeargs

or

run bootfromsd

then

setenv maxcpus 4
run storeargs

or

run bootfromsd

Quote from balbes150

This command full erases all eMMC.

First, try in the UART console to run the command "defenv" and then the second command "saveenv". This will reset all variables to their original state. After that, you can try to write the regular firmware via USB Burn Tool.

After that, you can normally activate the multi-boot and run the LE from external media and install in eMMC without the risk of killing the TV box.

This is already done by the aml_autoscript. Also burning via ABT would execute the "flash erase" (init 3) and thus completely remove the uboot environment from emmc, so running from devenv would actually make no sense

reading aml_autoscript
795 bytes read in 3 ms (258.8 KiB/s)
## Executing script at 01080000
## defenv_reserve
Saving Environment to aml-storage...
mmc env offset: 0x27400000
Writing to MMC(1)... done

Quote from Nebojsa

Ok, thanks.

Here is CE log, is anything you can see from it?

Do You know any commands that I can use to "going to the maintance level of the box on boot up and tell it to clear all the flash area's" ?

CElog.txt

You are trying to boot with wrong p212 dtb, this will not work. (Probably the GPU is broken.) You can run store init 3 in the uboot terminal and try to burn the uboot onto the sd card to boot from it instead of from the internal bootloader partition, but I do not think it helps.

USB interface is detected, that's good. Install u-boot.bin.sd.bin via BootcardMaker (see method 3), insert the SDcard into the card slot of the box and start it again.

This is correct, because these two partitions are not yet formatted. The bootloader was written from offset 0 into the SD card. This area is not visible in user space. Is the device recognized in the AML Burning Tool?

Did you unpack the * .tar.gz archive before burning it? the bootloader is still not installed.

for testing

SDcard installation (Linux)

dd if=u-boot.bin.sd.bin of=/dev/sdX bs=1 count=444
dd if=u-boot.bin.sd.bin of=/dev/sdX bs=512 skip=1 seek=1
sync

or bootloader.img, installation e.g. via Win32 Disk Imager (Windows)

Download

bootloader.tar.gz

post the bootlog

dalina106

You have a boot loop because the bootloader has been deleted. Please take photos from RAM so we can install the right bootloader.

Quote from KernelPanic

...

Code

##############################################
#                  LibreELEC                 #
#            https://libreelec.tv            #
##############################################

LibreELEC (community): 8.2.3.1-LePotato (S905.arm)
LibreELEC:~ # install
install            installtointernal
LibreELEC:~ # installtointernal
One of BOOT, SYTEM, DATA or DTB partitions is missing.
Make sure that you are using a correct device tree and a device with internal memory!
LibreELEC:~ # blkid
/dev/loop0: TYPE="squashfs"
/dev/mmcblk0: PTUUID="0b7c79b9" PTTYPE="dos"
/dev/mmcblk0p1: SEC_TYPE="msdos" LABEL="LIBREELEC" UUID="4FDE-D398" TYPE="vfat" PARTUUID="0b7c79b9-01"
/dev/mmcblk0p2: LABEL="LIBREELEC_DISK" UUID="e3704881-f45b-4432-ba43-601135ca7d02" TYPE="ext4" PARTUUID="0b7c79b9-02"
LibreELEC:~ # e2label /dev/mmcblk0p2
LIBREELEC_DISK
LibreELEC:~ # e2label /dev/mmcblk0p2 ""
LibreELEC:~ # e2label /dev/data "LIBREELEC_DISK"
e2label: No such file or directory while trying to open /dev/data
Couldn't find valid filesystem superblock.
LibreELEC:~ # store erase partition boot
-sh: store: not found
LibreELEC:~ #

Display More

What was wrong?

...

I have already given you the answer to this question. You need a DTB file with "nand“ suffix, otherwise the integrated Nand memory can not be recognized.

I have corrected the link

The Chinese do not stop to surprise . Looking for a firmware with "Nand" support, try the last release of kszaq from here, use gxl_p212_1g_nand.dtb.

You have a p212 device and installed a P281 FW.

1. Abort Autoboot and execute the following command in the uboot terminal to remove the wrongly installed bootloader from the flash memory.

store erase boot

2. Find a suitable S905X Android FW (e.g AtvXperience) and install it via AML Burning Tool or SDcard method.

P.S. For LibreElec use gxl_p212_1g.dtb

KernelPanic

Before we move on, please remove the heatsink from the processor and check the exact type of CPU to avoid suspicion of installing a wrong bootloader.

Quote

Can I swap the file?

Yes

You have a p281 device with 1g RAM, follow the installation instructions and use gxl_p281_1g.dtb. Execute the command in the uboot terminal, the box should now boot to the LE.

Hi, cancel the Autoboot process by pressing the Space or Enter key and execute this command:

run update

saleh

It looks like a uboot problem. I might be able to help you, but I need the full log via uart interface.