cm201-2 m8273hi300海兔擦除后刷入其他引导头后无法正常启动

神伤q · 发表于 2025-2-4 09:56

请问大佬，怎么办，新人，啥都不知道

1337565980 · 发表于 2025-2-4 15:51

擦除就把fastboot也去掉了，这个不是什么引导头，是启动。找对应cpu和运存的一致的fastboot烧写上就好了。一般用同款机器的fastboot最好。fastboot的适应主要看reg。cm201-2,M8273主板的mv300cpu的
fastboot 的reg是这样的: v120v1.5.3\ 2017/12/19 14:02:12 hi3798mv3dmw_hi3798mv300_DDR3-1866_1GB_16bitx2_2layers.reg.

月光※傾城 · 发表于 2025-2-4 10:48

神伤q 发表于 2025-2-4 10:00
怎么引导数据不能在帖子里发出来呀

我有

神伤q · 发表于 2025-2-4 10:00

怎么引导数据不能在帖子里发出来呀

神伤q · 发表于 2025-2-4 10:03

Bootrom start
Boot Media: eMMC
Decrypt auxiliary code ...OK

lsadc voltage min: 00000100, max: 00000108, aver: 00000101, index: 00000004

Enter boot auxiliary code

Auxiliary code - v1.00
DDR code - V1.1.2 20160205
Build: Nov 29 2017 - 19:56:56

Reg Version:  v1.5.3\
Reg Time:    2017/12/19 14:02:12
Reg Name:    hi3798mv3dmw_hi3798mv300_DDR3-1866_1GB_16bitx2_2layers.reg

Boot auxiliary code success
Bootrom success

System startup

Relocate Boot

Jump to C code

Fastboot 3.3.0 (rongxinjing@TSD182) (Mar 15 2018 - 17:10:36)

神伤q · 发表于 2025-2-5 13:11

scan edges:2 p2f:4 f2p:6
mix set temp-phase 1
scan elemnts: startp:81 endp:78
Tuning SampleClock. mix set phase:[01/07] ele:[09/14]
MMC/SD Card:
MID:       0x70
Read Block:  512 Bytes
Write Block: 512 Bytes
Chip Size: 7296M Bytes (High Capacity)
Name:       "T22708"
Chip Type: MMC
Version:    5.0
Speed:    100000000Hz
Mode:       HS400
Voltage:    1.8V
Bus Width: 8bit
Boot Addr: 0 Bytes

*** Warning - bad CRC or eMMC, using default environment

Net: upWarning: failed to set MAC address
, gmac0Warning: failed to set MAC address

Boot Env on eMMC
Env Offset:       0x00400000
Env Size:          0x00010000
Env Range:          0x00010000
Get ID_WORD lock flag : 0

SDK Version: v6r3c01spc030_patch3

emmc<5>
[sw_ptable_init,114] begin
partition addr : [0x0]
partition addr : [0x200000, 0x100000]
[swflash_partition_read,217]part_addr:0x200000, part_size:0x100000, offset:0x0, bytes:0xb10
[sw_ptable_check,292]cksum [0xddba], ptable->checksum[0xddba]
[sw_ptable_init,140] data at 0x0 is ok
[swflash_partition_read,217]part_addr:0x300000, part_size:0x100000, offset:0x0, bytes:0xb10
[sw_ptable_check,292]cksum [0xddba], ptable->checksum[0xddba]
0       fastboot 0x000000000    0x000200000
0       partition 0x000200000    0x000200000
0       recovery 0x000400000    0x001000000
0       swdevinfo 0x001400000    0x000200000
0       baseparam 0x001600000    0x000800000
0          pqparam 0x001E00000    0x000800000
0             logo 0x002600000    0x000800000
0       fastplay 0x002E00000    0x002000000
0             boot 0x004E00000    0x001000000
0             misc 0x005E00000    0x000200000
0    trustedcore 0x006000000    0x002800000
0    securestore 0x008800000    0x000800000
0             swdb 0x009000000    0x001000000
0          cache 0x00A000000    0x02D000000
0          system 0x037000000    0x040000000
0       userdata 0x077000000    0x14E800000

ptable info:2M(fastboot),2M(partition),16M(recovery),2M(swdevinfo),8M(baseparam),8M(pqparam),8M(logo),32M(fastplay),16M(boot),2M(misc),40M(trustedcore),8M(securestore),16M(swdb),720M(cache),1024M(system),5352M(userdata)

[sw_ptable_dump->252] tmp_bootargs_env=blkdevparts=mmcblk0:2M(fastboot),2M(partition),16M(recovery),2M(swdevinfo),8M(baseparam),8M(pqparam),8M(logo),32M(fastplay),16M(boot),2M(misc),40M(trustedcore),8M(securestore),16M(swdb),720M(cache),1024M(system),5352M(userdata)
[sw_ptable_init,183] partition : ok
sw_devinfo_init begin [sw_devinfo_init,823]
[swflash_partition_read,217]part_addr:0x1400000, part_size:0x200000, offset:0x0, bytes:0x8461c
[swflash_partition_read,217]part_addr:0x1500000, part_size:0x200000, offset:0x0, bytes:0x8461c
version : [1]
[devinfo_check,169] ok! msg->checksum:0x5dff, crc16:0x5dff
devinfo_init begin [sw_devinfo_init,946]
[devinfo_ext_check,258] ok! msg->checksum:0x0, crc16:0x0
sw_devinfo_init OK
[swflash_partition_read,217]part_addr:0x4e00000, part_size:0x1000000, offset:0x2000, bytes:0x2000
[swfastboot_flash_getinfo->114] flash TotalSize:0x1c8000000    BlockSize:0x2000       PageSize:0x1
[swfastboot_get_flashsize->133][SW]TotalSize=7650410496  flash_totalsize=7650410496
[sw_boot_set_bootargs->197]enable serial,use cmdline:[mem=1G mmz=ddr,0,0,48M console=ttyAMA0,115200 blkdevparts=mmcblk0:2M(fastboot),2M(partition),16M(recovery),2M(swdevinfo),8M(baseparam),8M(pqparam),8M(logo),32M(fastplay),16M(boot),2M(misc),40M(trustedcore),8M(securestore),16M(swdb),720M(cache),1024M(system),5352M(userdata)]
sw_ir_detect begin 500 count
sw_ir_detect ok

[sw_boot_set_bootargs->243]bootargs:[mem=1G mmz=ddr,0,0,48M console=ttyAMA0,115200 blkdevparts=mmcblk0:2M(fastboot),2M(partition),16M(recovery),2M(swdevinfo),8M(baseparam),8M(pqparam),8M(logo),32M(fastplay),16M(boot),2M(misc),40M(trustedcore),8M(securestore),16M(swdb),720M(cache),1024M(system),5352M(userdata) androidboot.selinux=permissive androidboot.force_open_console=none]

[Android_Main,39] begin
[sw_set_gpio,128] OK
[swflash_partition_read,217]part_addr:0x5e00000, part_size:0x200000, offset:0x0, bytes:0x10000
boot normal!!!
[sw_boot_set_bootcmd->366]bootm now: mmc read 0 0x1FFFFC0 0x27000 0x8000;bootm 0x1FFFFC0
[Android_Main,86] ok
Reserve Memory
Start Addr:       0xFFFE000
Bound Addr:       0x8DAA000
Free  Addr:       0xF01D000
Alloc Block:  Addr       Size
               0xFBFD000 0x400000
               0xF8FC000 0x300000
               0xF8F9000 0x2000
               0xF878000 0x80000
               0xF847000 0x30000
               0xF549000 0x2FD000
               0xF1C4000 0x384000
               0xF1C0000 0x3000
               0xF02A000 0x195000
               0xF020000 0x9000
               0xF01D000 0x2000

[abortboot,110] begin
[abortboot,113] close loader keyed

MMC read: dev # 0, block # 159744, count 32768 ... 32768 blocks read: OK

105881117 Bytes/s
Check Hisilicon_ADVCA ...
Not hisilicon ADVCA image ...
Wrong Image Format for bootm command
ERROR: can't get kernel image!
fastboot#

神伤q · 发表于 2025-2-5 13:16

月光※傾城发表于 2025-2-4 10:48
我有

大佬怎么联系呀

神伤q · 发表于 2025-2-5 13:37

1337565980 发表于 2025-2-4 15:51
擦除就把fastboot也去掉了，这个不是什么引导头，是启动。找对应cpu和运存的一致的fastboot烧写上就好了。 ...

大佬，这个是我从网上找的，但是刷入后，不能正常运行代码，比如说df，无法运行

1337565980 · 发表于 2025-2-5 16:27

神伤q 发表于 2025-2-5 13:11
scan edges:2 p2f:4 f2p:6
mix set temp-phase 1
scan elemnts: startp:81 endp:78

能跑这个fastboot就没问题啊，把其他分区烧上就好了。

1337565980 · 发表于 2025-2-5 16:31

神伤q 发表于 2025-2-5 13:37
大佬，这个是我从网上找的，但是刷入后，不能正常运行代码，比如说df，无法运行 ...

单就一个fastboot只是能启动，启动后要调用kernel核心，然后再运行其他配置后运行系统，系统运行了才有机会在终端输入指令，能输入指令也要系统本身是允许终端对话，有些系统是禁用终端对话的。

› 你问我答 / 玩机教程 / 固件 › ZNDS刷机/救砖

cm201-2 m8273hi300海兔擦除后刷入其他引导头后无法正常 ...

cm201-2 m8273hi300海兔擦除后刷入其他引导头后无法正常启动

浏览过的版块

站长推荐 /1