This does not look good. The only thing i can suggest is to use the RAM memory directly. To do this, read this document Amlogic_update_usb_tool_user_guide.
The individual steps are described in section 4.2.
This does not look good. The only thing i can suggest is to use the RAM memory directly. To do this, read this document Amlogic_update_usb_tool_user_guide.
The individual steps are described in section 4.2.
because I uploaded FW from an older version of s905
Ah ok. But I still don't understand how flashing the gxbb fw could affect the boot ROM (BL1). Additional start devices SPI and NAND appeared in the BL1 boot sequence. Ok, let's assume - the card reader in your box is no longer working or the SD card is defective. This could lead to incorrect loading of BL2. I will create an aml_upgrade_package.img file and integrate the new u-boot. You will try to do the USB-burn via UBT.
Second time... Your bootloader also contains this string:
Code "Built : 15:21:58, Mar 26 2020. gxl g486bc38 - gongwei.chen@droid11-sz"
Yes, I am aware of this. Here the gxl bl2 blob is loaded and executed because it used the bootloader I posted. However, this does not explain the difference described above. )
There are KI Plus boards with an S905 processor. A photo of someone else's board does not explain the difference between the two different boot ROM logs.
Please remove the heat sink and attach CPU photo
You are posting logs from 2 completely different devices..
This is from gxl Platform:
QuoteBL1:9ac50e:a1974b;FEAT:ADFC318C;POC:3;RCY:0;EMMC:0;READ:0;CHK:AA;SD:0;READ:0;CHK:AA;USB:8;
And this is probably gxbb platform:
QuoteBL1:9ac50e:bb16dc;FEAT:ADFC318C:0;POC:0;RCY:0;USB:0;SPI:0;CHK:A7;EMMC:400;NAND:81;SD:0;READ:0;0.0;CHK:0;
The full log would be helpful here. Take some board photos..
files available on sd card are already shown in attached image, in the previous post, (sd card is prepared from boot card maker, then files pasted on it.
ie
aml_upgrade_package.img
gxl_p230_2g_pie.dtb
u-boot.bin
I mean LibreElec files.
Quote"copy unpacked partitions to the sd card"
means copy all unpacked files to sd card root and then
Yes.
Android you can also write to emmc by hand. To do this, you first have to unpack the aml_upgrade_package.img with a repack tool, copy unpacked partitions to the sd card and write to emmc with the following commands:
(First you have to burn the dtb that you already did in step 3), then
sdc_update dtbo dtbo.PARTITION normal
sdc_update boot boot.PARTITION normal
sdc_update recovery recovery.PARTITION normal
sdc_update logo logo.PARTITIO normal
sdc_update system system.PARTITION sparse
sdc_update vendor vendor.PARTITION sparse
sdc_update odm odm.PARTITION sparse
sdc_update product product.PARTITION sparse
reboot
No, everything is fine. I suspect a weak power supply, or something like that..
This bootloader needs aml_autoscript so that booting from the SD card works. This script is currently missing on the FAT partition of your SD card. I haven't used an LE for a long time - which files are on your LE SD card?
QuoteBL1:9ac50e:bb16dc;FEAT:ADFC318C:0;POC:0;RCY:0;USB:0;SPI:0;CHK:A7;EMMC:400;NAND:81;SD:0;READ:0;0.0;CHK:0;
Log is incomplete.The information about the platform in front of the BL1 is missing. Post the full log. Is that GXBB: BL1… or GXL: BL1…?
How do you write the u-boot on the sd card? Do you have linux?
Try the following steps:
1. Determine the exact name of your block device sdX (sd card) with the lsblk command.
2. Unmount the FAT partition of the found block device
3. Clean the unpartitioned area on the SD card
sudo dd if=/dev/zero of=/dev/sdX bs=1 count=444
sudo dd if=/dev/zero of=/dev/sdX bs=512 skip=1 seek=1 count=2047
4. Write this u-boot.bin.sd.bin binary
Updated uboot for 1g lpddr3 device. Install u-boot.bin.sd.bin on the sd card and attach uart log here
To avoid the installation errors, perform the following steps in the u-boot terminal (gxl_p230_v1#):
1. Copy u-boot.bin and gxl_p230_2g_pie.dtb to the FAT partition of the previously prepared mSD card. Boot the box from the mSD card and execute the following commands:
2. Write the u-boot.bin into the eMMC
3. Write the *.dtb file into the eMMC (partitioning)
After these steps you must now be able to boot from the LibreElec SD card.
Insert the LE SD card into the box and execute this command in the u-boot terminal:
or use the RESET button.
I will upload Android IMG a little later...
when i press on make with selected bin file, it formats the card in fat32 and then shows success.
but sd card shows empty, then i copied the provided bin file manually on sd card. & booted the box with sd card, with recovery button pressed,
but no benefit, it still initializing on 720mhz.... may be it's not booting through SDcard....
That's right - Bootcardmaker writes the u-boot.bin from the 0 sector into a non-partitioned area on the SD card and creates a new partition table + formats it in FAT32. You do not have to copy the u-boot.bin to the FAT partition. Plug the mSD into the box, short-circuit the eMMC pins 29-30 and switch the box on. After 2 sec. let go of the pins. In this case, the processor ROM BL1 searches for the BL2 from the 0 sector on the mSD card