找回密码
 立即注册

QQ登录

只需一步,快速开始

搜索
广告投放联系QQ68610888
查看: 975|回复: 1

U-boot报错无法引导,是Nand坏了?

[复制链接]
发表于 2024-6-17 16:07 | 显示全部楼层 |阅读模式
请帮忙看下以下U-boot信息,是否Nand刷坏了?荣耀路由XD28



======================================

U-Boot 2016.01 (Jan 08 2022 - 02:27:51 +0800)

DRAM:  smem ram ptable found: ver: 1 len: 4
256 MiB
USB: Node Not found, skipping initi▒*9▒  QPIC controller support serial NAND
ID = 21e521e5
Vendor = e5
Device = 21
Serial Nand Device Found With ID : 0xe5 0x21
Serial NAND device ManufacturerS35M1GA-IB
Device Size:128 MiB, Page size:2048, Spare Size:128, ECC:4-bit
qpic_nand: changing oobsize to 64 from 128 bytes
SF: Unsupported flash IDs: manuf 00, jedec 0000, ext_jedec 0000
ipq_spi: SPI Flash not found (bus/cs/speed/mode) = (0/0/48000000/0)
128 MiB
MMC:   sdhci: Node Not found, skipping initialization

In:    serial@78AF000
Out:   serial@78AF000
Err:   serial@78AF000
machid: 8040002
eth1 MAC Address from ART is not valid
record_reboot_reason: The last reason has not been read, so ignore this time!
apps_iscrashed: magic_value(0x10000), crash_flag(0x0)

ubi0: attaching mtd1
qpic_nand_read_page_scope_multi_page: ecc failure while reading from 2580800
qpic_nand_read_page_scope_multi_page: ecc failure while reading from 2580800
qpic_nand_read_page_scope_multi_page: ecc failure while reading from 2580800
qpic_nand_read_page_scope_multi_page: ecc failure while reading from 2580800
qpic_nand_read_page_scope_multi_page: ecc failure while reading from 2d00800
qpic_nand_read_page_scope_multi_page: ecc failure while reading from 2d00800
qpic_nand_read_page_scope_multi_page: ecc failure while reading from 2d00800
qpic_nand_read_page_scope_multi_page: ecc failure while reading from 2d00800
ubi0: scanning is finished
ubi0: attached mtd1 (name "mtd=0", size 42 MiB)
ubi0: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
ubi0: min./max. I/O unit sizes: 2048/2048, sub-page size 2048
ubi0: VID header offset: 2048 (aligned 2048), data offset: 4096
ubi0: good PEBs: 337, bad PEBs: 0, corrupted PEBs: 0
ubi0: user volume: 5, internal volumes: 1, max. volumes count: 128
ubi0: max/mean erase counter: 6/0, WL threshold: 4096, image sequence number: 441187066
ubi0: available PEBs: 0, total reserved PEBs: 337, PEBs reserved for bad PEB handling: 20
qpic_nand_read_page_scope_multi_page: ecc failure while reading from 2580800
qpic_nand_read_page_scope_multi_page: ecc failure while reading from 2580800
qpic_nand_read_page_scope_multi_page: ecc failure while reading from 2580800
qpic_nand_read_page_scope_multi_page: ecc failure while reading from 2580800
qpic_nand_read_page_scope_multi_page: ecc failure while reading from 2581000
qpic_nand_read_page_scope_multi_page: ecc failure while reading from 2581000
qpic_nand_read_page_scope_multi_page: ecc failure while reading from 2581000
qpic_nand_read_page_scope_multi_page: ecc failure while reading from 2581000
qpic_nand_read_page_scope_multi_page: ecc failure while reading from 2d00800
qpic_nand_read_page_scope_multi_page: ecc failure while reading from 2d00800
qpic_nand_read_page_scope_multi_page: ecc failure while reading from 2d00800
qpic_nand_read_page_scope_multi_page: ecc failure while reading from 2d00800
qpic_nand_read_page_scope_multi_page: ecc failure while reading from 2d01000
qpic_nand_read_page_scope_multi_page: ecc failure while reading from 2d01000
qpic_nand_read_page_scope_multi_page: ecc failure while reading from 2d01000
qpic_nand_read_page_scope_multi_page: ecc failure while reading from 2d01000
Read 0 bytes from volume kernel to 44000000
No size specified -> Using max size (4587224)
## Loading kernel from FIT Image at 44000000 ...
   Using 'config@mp03.3' configuration
   Trying 'kernel@1' kernel subimage
     Description:  ARM OpenWrt Linux-4.4.60
     Type:         Kernel Image
     Compression:  lzma compressed
     Data Start:   0x440000e4
     Data Size:    3157788 Bytes = 3 MiB
     Architecture: ARM
     OS:           Linux
     Load Address: 0x41208000
     Entry Point:  0x41208000
     Hash algo:    crc32
     Hash value:   ad506527
     Hash algo:    sha1
     Hash value:   f503c3c1cd91eb70a1b6b6167032c30895d3f27c
   Verifying Hash Integrity ... crc32+ sha1+ OK
## Loading fdt from FIT Image at 44000000 ...
   Using 'config@mp03.3' configuration
   Trying 'fdt@mp03.3' fdt subimage
     Description:  ARM OpenWrt qcom-ipq50xx-mpxx device tree blob
     Type:         Flat Device Tree
     Compression:  uncompressed
     Data Start:   0x44376e8c
     Data Size:    59210 Bytes = 57.8 KiB
     Architecture: ARM
     Hash algo:    crc32
     Hash value:   f94137e2
     Hash algo:    sha1
     Hash value:   7e33c37a9a97756e145e42db39f5909fb2a84ff0
   Verifying Hash Integrity ... crc32+ sha1+ OK
   Booting using the fdt blob at 0x44376e8c
   Uncompressing Kernel Image ... OK
   Loading Device Tree to 4a3ee000, end 4a3ff749 ... OK
Using machid 0x8040002 from environment

Starting kernel ...

==================================

只谈技术、莫论政事!(点击见详情) | 恩山无线论坛欢迎您的来访,请互相尊重、友善交流,建议保持一颗平常心看待网友的评论,切勿过度反应。
发表于 2024-6-17 20:36 | 显示全部楼层
Nand刷坏 Nand刷坏
只谈技术、莫论政事!(点击见详情) | 恩山无线论坛欢迎您的来访,请互相尊重、友善交流,建议保持一颗平常心看待网友的评论,切勿过度反应。
回复 支持 反对

使用道具 举报

您需要登录后才可以回帖 登录 | 立即注册

本版积分规则

关闭

欢迎大家光临恩山无线论坛上一条 /1 下一条

有疑问请添加管理员QQ86788181|手机版|小黑屋|Archiver|恩山无线论坛(常州市恩山计算机开发有限公司版权所有) ( 苏ICP备05084872号 )

GMT+8, 2024-9-28 12:40

Powered by Discuz! X3.5

© 2001-2024 Discuz! Team.

| 江苏省互联网有害信息举报中心 举报信箱:js12377 | @jischina.com.cn 举报电话:025-88802724 本站不良内容举报信箱:68610888@qq.com

快速回复 返回顶部 返回列表