固件烧录问题

SUSHI · 发表于昨天 17:58

（为了高效，请按如下格式提问）

硬件主板型号：YY3588
固件名称/系统版本：Android14
自编的或固件下载地址：官网提供YY3588固件下载的官方下载
Log日志: (可以导出，用TXT附件上传)

问题描述及复现步骤:固件烧录显示成功后无法开机，只能进入loader或者maskrom，这么解决？

SUSHI · 发表于昨天 19:10

另，鸿蒙系统也是一样的问题：[ 0.932263][ T0] Booting Linux on physical CPU 0x0000000000 [0x412fd050]
[ 0.932288][ T0] Linux version 5.10.160 (youyeetoo@youyeetoo-D80) (OHOS (d                                                                                                                                  ev) clang version 15.0.4 (llvm-project 7e44bed824d29a5240f775e22e13d753a66218dd)                                                                                                                                  , LLD 15.0.4) #11 SMP PREEMPT Thu Oct 23 06:36:11 EAT 2025
[ 0.943255][ T0] Machine model: RK3588 Youyeetoo YY3588
[ 0.993539][ T0] earlycon: uart8250 at MMIO32 0x00000000feb50000 (options                                                                                                                                  '')
[ 0.997097][ T0] printk: bootconsole [uart8250] enabled
[ 1.001792][ T0] OF: fdt: Reserved memory: failed to reserve memory for no                                                                                                                                  de 'drm-cubic-lut@00000000': base 0x0000000000000000, size 0 MiB
[ 1.003022][ T0] Reserved memory: created CMA memory pool at 0x00000000100                                                                                                                                  00000, size 256 MiB
[ 1.003826][ T0] OF: reserved mem: initialized node cma, compatible id sha                                                                                                                                  red-dma-pool
[ 1.004743][ C0] SError Interrupt on CPU0, code 0xbe000011 -- SError
[ 1.004746][ C0] CPU: 0 PID: 0 Comm: swapper Not tainted 5.10.160 #11

SUSHI · 发表于昨天 19:17

开发板是YY3588 DEV KIT V3.0

SUSHI · 发表于昨天 20:28

在安卓固件烧录的过程中，因篇幅限制，无法提供全部的串口调试日志：=> sysmem_dump

sysmem_dump_all:
--------------------------------------------------------------------
memory.rgn[0].addr    = 0x00200000 - 0x08400000 (size: 0x08200000)
memory.rgn[1].addr    = 0x09400000 - 0xf0000000 (size: 0xe6c00000)

memory.total          = 0xeee00000 (3822 MiB. 0 KiB)
--------------------------------------------------------------------
allocated.rgn[0].name  = "STACK"
                  .addr  = 0xeb7fa470 - 0xeb9fa470 (size: 0x00200000)
allocated.rgn[1].name  = "FDT_DTBO"
                  .addr  = 0x08300000 - 0x08348cb4 (size: 0x00048cb4)

kmem-resv.rgn[0].name  = "cma"
                  .addr  = 0x10000000 - 0x18000000 (size: 0x08000000)
kmem-resv.rgn[1].name  = "ramoops@110000"
                  .addr  = 0x00110000 - 0x001f0000 (size: 0x000e0000)

framework malloc_r    =  32 MiB
framework malloc_f    = 512 KiB

allocated.total       = 0x08328cb4 (131 MiB. 163 KiB)
--------------------------------------------------------------------
LMB.allocated[0].addr  = 0x08300000 - 0x08348cb4 (size: 0x00048cb4)
LMB.allocated[1].addr  = 0xeb7fa470 - 0xeb9fa470 (size: 0x00200000)

reserved.core.total = 0x00248cb4 (2 MiB. 291 KiB)
--------------------------------------------------------------------

=> <INTERRUPT>
=> fdt addr 0x0a100000
libfdt fdt_check_header(): FDT_ERR_BADMAGIC
=> <INTERRUPT>
=> fdt addr 0x08300000
=> <INTERRUPT>
=> fdt print /reserved-memory
reserved-memory {
      #address-cells = <0x00000002>;
      #size-cells = <0x00000002>;
      ranges;
      cma {
            compatible = "shared-dma-pool";
            reusable;
            reg = <0x00000000 0x10000000 0x00000000 0x08000000>;
            linux,cma-default;
            size = <0x00000000 0x00800000>;
      };
      drm-logo@0 {
            compatible = "rockchip,drm-logo";
            reg = <0x00000000 0x00000000 0x00000000 0x00000000>;
            phandle = <0x00000037>;
      };
      drm-cubic-lut@0 {
            compatible = "rockchip,drm-cubic-lut";
            reg = <0x00000000 0x00000000 0x00000000 0x00000000>;
            phandle = <0x000004ac>;
      };
      vendor-storage-rm@00000000 {
            compatible = "rockchip,vendor-storage-rm";
            reg = <0x00000000 0x00000000 0x00000000 0x00000000>;
            phandle = <0x000001f7>;
      };
      ramoops@110000 {
            compatible = "ramoops";
            reg = <0x00000000 0x00110000 0x00000000 0x000e0000>;
            boot-log-size = <0x00008000>;
            boot-log-count = <0x00000001>;
            console-size = <0x00080000>;
            pmsg-size = <0x00030000>;
            ftrace-size = <0x00000000>;
            record-size = <0x00014000>;
            phandle = <0x000004ad>;
      };
      minidump-smem@1f0000 {
            reg = <0x00000000 0x001f0000 0x00000000 0x00000100>;
            no-map;
            status = "disabled";
            phandle = <0x000001f5>;
      };
      minidump-mem@c000000 {
            reg = <0x00000000 0x0c000000 0x00000000 0x02000000>;
            no-map;
            status = "disabled";
            phandle = <0x000001f6>;
      };
};
=> <INTERRUPT>
=>

SUSHI · 发表于昨天 20:32

YY3588 (16GB) 烧录新内核启动崩溃：
一、
> [ 1.004634][ C0] pc : __memset+0x178/0x188
> [ 1.004636][ C0] lr : early_pgtable_alloc+0x7c/0x118
> [ 1.004659][ C0] x19: 00000003fffbf000
> [ 1.004694][ C0] Kernel panic - not syncing: Asynchronous SError Interrupt
二、
> Adding bank: 0x3fc500000 - 0x3fffc0000 (size: 0x03ac0000)
三、
> memory.rgn[0].addr = 0x00200000 - 0x08400000 (size: 0x08200000)
> memory.rgn[1].addr = 0x09400000 - 0xf0000000 (size: 0xe6c00000)
> memory.total = 0xeee00000 (3822 MiB. 0 KiB)
四、
在 U-Boot 下执行 `fdt addr 0x08300000` 后 `fdt print /reserved-memory`，输出结果显示：
所有预留节点（cma, ramoops, drm-logo 等）全都在 0x00000000 ~ 0x18000000 的低地址区间。
五、
> NOTICE: BL31: Built : 18:24:24, Apr 21 2022
> U-Boot 2017.09 (Aug 31 2022 - 16:08:40 +0800)
> ch:1 dq1 fail,write:0x2,read:0x0
> ch:1 dq0 fail,write:0xfffffffe,read:0xfffdfffe
> error
> ERR

peter · 发表于昨天 20:52