| |

iFix 爱修网

 找回密码
 注册

QQ登录

只需一步,快速开始

iFix爱修网知识星球,等待你的加入。。。
查看: 882|回复: 1

哪位仁兄,帮我看看这个打印信息有何问题

[复制链接]
发表于: 2020-8-31 11:59:01
| 显示全部楼层 |阅读模式
001:  序列号:20180422190223-031914  ,PCB V1.80,Boot V1.00
002:  >------------------------------------OK---------------------------------------<
003:  C:\Users\Administrator\Desktop\Print.log
004:  COM10, BaudRate:115200 bps, RXD: VGA->15,TXD: VGA->12,
sbrom commit : 44d448f1d618c4d6b225570ac4cef3692fcdc8d5

try to probe rtc region
fel_flag = 0x00000000
rtc[0] value = 0x00000000
rtc[1] value = 0x00000000
rtc[2] value = 0x00000000
rtc[3] value = 0x00000000
rtc[4] value = 0x00000000
rtc[5] value = 0x00000000
rtc[6] value = 0x00000000
rtc[7] value = 0x00000000
flag=0x00000000
try to setup mmu
mmu setup ok
try to init dram
DRAM DRIVE INFO: kst
the chip id is 0x00000042
the chip id is 0x00000042
the chip id is 0x00000042
the chip id is 0x00000042
the chip id is 0x00000042
NOT GATE MODE
READ DQS LCDL = 00232323
DRAM Type = 3 (2DR2,3DR3,6PDDR2,7PDDR3)
DRAM CLK = 576 MHz
DRAM zq value: 003b3bfb
DRAM dram para1: 10e40200
DRAM dram para2: 00000001
DRAM workmode1: 000009f4
DRAM SIZE =512 M
odt delay
init dram ok, size=512M
mmu resetup
init heap
init flash
NAND_PIORequest, nand_index: 0x00001000
Reg 0x01c20848: 0x0001ad93
Reg 0x01c2084c: 0x0001ad86
Reg 0x01c20850: 0x0001ad86
NAND_ClkRequest, nand_index: 0x0001ad9e
Reg 0x01c20080: 0x0001ad9b
Reg 0x01c20060: 0x0001ad8e
Reg 0x01c202c0: 0x0001ad8e
NAND_SetClk, nand_index: 0x0000000a
Reg 0x01c20080: 0x0001ad9f
NB0 : nand phy init ok
Check is correct.
*******************TOC1 Head Message*************************
Toc_name          = sunxi-secure
Toc_magic         = 0x89119800
Toc_add_sum              = 0x4542ffa0
Toc_serial_num    = 0x00000000
Toc_status        = 0x00000000
Toc_items_nr      = 0x00000005
Toc_valid_len     = 0x000f4000
TOC_MAIN_END      = 0x3b45494d
***************************************************************



*******************TOC1 Item Message*************************
Entry_name        = rootkey
Entry_data_offset = 0x00000800
Entry_data_len    = 0x00000968
encrypt                  = 0x00000000
Entry_type        = 0x00000000
run_addr          = 0x00000000
index             = 0x00000000
Entry_call        = 0x00000000
Entry_end         = 0x3b454949
***************************************************************



*******************TOC1 Item Message*************************
Entry_name        = boot
Entry_data_offset = 0x00001400
Entry_data_len    = 0x0000035f
encrypt                  = 0x00000000
Entry_type        = 0x00000002
run_addr          = 0x00000000
index             = 0x00000000
Entry_call        = 0x00000000
Entry_end         = 0x3b454949
***************************************************************



*******************TOC1 Item Message*************************
Entry_name        = recovery
Entry_data_offset = 0x00001800
Entry_data_len    = 0x00000363
encrypt                  = 0x00000000
Entry_type        = 0x00000002
run_addr          = 0x00000000
index             = 0x00000000
Entry_call        = 0x00000000
Entry_end         = 0x3b454949
***************************************************************



*******************TOC1 Item Message*************************
Entry_name        = u-boot
Entry_data_offset = 0x00001c00
Entry_data_len    = 0x00000361
encrypt                  = 0x00000000
Entry_type        = 0x00000002
run_addr          = 0x00000000
index             = 0x00000000
Entry_call        = 0x00000000
Entry_end         = 0x3b454949
***************************************************************



*******************TOC1 Item Message*************************
Entry_name        = u-boot
Entry_data_offset = 0x00002000
Entry_data_len    = 0x000f0000
encrypt                  = 0x00000000
Entry_type        = 0x00000003
run_addr          = 0x4a000000
index             = 0x00000000
Entry_call        = 0x4a000000
Entry_end         = 0x3b454949
***************************************************************


probe root certif
find boot key stored in root certif
find recovery key stored in root certif
find u-boot key stored in root certif

ready to run u-boot
secure_without_OS mode  
storage_type=0
still in secure world  
dram = 512 M
SUNXI_SECURE_MODE_NO_SECUREOS

[      1.547]


U-Boot 2011.09-rc1-dirty (Aug 09 2017 - 15:05:17) Allwinner Technology


[      1.555]version: 1.1.0
[      1.557]uboot commit : 44d448f1d618c4d6b225570ac4cef3692fcdc8d5

not using multi config
normal mode
[      1.570]pmbus:   ready
not set main pmu id
axp_probe error
gpio value=0x0
cpux freq run low
[      1.610]PMU: pll1 1008 Mhz,PLL6=600 Mhz
AXI=336 Mhz,AHB=200 Mhz, APB1=100 Mhz
sid read already
fel key new mode
run key detect
no key found
no key input
dram_para_set start
dram_para_set end
[      1.639]DRAM:  512 MiB
relocation Offset is: 15ae3000
[box standby] read rtc = 0x0
[box_start_os] mag be start_type no use
user_gpio config
user_gpio ok
gic: normal or no secure os mode
workmode = 0
[      1.720]NAND: NAND_UbootInit
NAND_UbootInit start
NB1 : enter NAND_LogicInit
nand : get id number_ctl fail, 1
uboot: nand version: 3 6012 20170525 1826
nand : get CapacityLevel fail, 5fb9655c
not burn nand partition table!
NB1 : nftl num: 1
init nftl: 0
NB1 : nftl_build_all fail
NAND_UbootInit end: 0xfffffffb
[      4.490]nand init fail
script config pll_de to 864 Mhz
Not Found clk pll_video1 in script
script config pll_video to 297 Mhz
script config pll_periph0 to 600 Mhz
[boot]disp_init_tv
[DISP_TV] disp_init_tv enter g_tv_used
screen 0 do not support TV TYPE!
[BOOOT_DISP_TV] disp tv device_registered
unable to find regulator vcc-hdmi-18 from [pmu1_regu] or [pmu2_regu]
enable power vcc-hdmi-18, ret=-1
DRV_DISP_Init end
[disk_read_fs] no the partition
error: open tv_vdid.fex, maybe it is not exist
[disk_read_fs] no the partition
error: open disp_rsl.fex, maybe it is not exist
[disk_read_fs] no the partition
error: open disp_rsl.fex, maybe it is not exist
boot_disp.auto_hpd=1
auto hpd check has 100 times!
auto check no any connected, the output_type is 2
attched ok, mgr1<-->device1, type=2, mode=11----
ready to set mode
disp_tv_enable
[      5.901]finally, output_type=0x2, output_mode=0xb, screen_id=0x1, disp_para=0x20b0000
no item name key_burned_flag in the map
sunxi secure storage has no flag
[      5.915]usb burn from boot
delay time 0
[      6.008]usb prepare ok
[      6.810]timer occur
[      6.812]overtime
[      6.847]do_burn_from_boot usb : no usb exist
fail to find part named env
Using default environment


In:    serial
Out:   serial
Err:   serial
--------fastboot partitions--------
mbr not exist
base bootcmd=run setargs_nand boot_normal
bootcmd set setargs_nand
key 0
cant find rcvy value
cant find fstbt value
no misc partition is found
Try to burn rootkey by ota
error:Get env rootkey fail
try to read rotpk
[sunxi_efuse_read] securemode=3
read key start
key name = rotpk
key index = 0x64
3b 6d 9b a0 62 33 b7 f8 77 aa a3 2f fe 9d 58 51
f0 86 af 41 24 4d b0 bd 86 11 5f 07 a3 10 c3 63


to be run cmd=run setargs_nand boot_normal
[sunxi_efuse_read] securemode=3
read key start
key name = wifi_mac_efuse
key index = 0x18
00 00 00 00 00 00 00 00 95 ed 67 5d aa b4 bf ea


have not burned wifi_mac to efuse
check user data form private
the private part isn't exist
WORK_MODE_BOOT
[      6.927]Hit any key to stop autoboot:  3  2  1  0
cant find part named boot
sunxi_flash - sunxi_flash sub-system


Usage:
sunxi_flash read command parmeters :
parmeters 0 : addr to load(hex only)
parmeters 1 : the name of the part to be load
[parmeters 2] : the number of bytes to be load(hex only)
if [parmeters 2] not exist, the number of bytes to be load is the size of the part indecated on partemeter 1
boota: bad boot image magic, maybe not a boot.img?
sunxi#
回复

使用道具 举报

发表于: 2020-8-31 18:49:25
| 显示全部楼层
单独NAND方案的?什么型号机器?
回复 支持 反对

使用道具 举报

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

本版积分规则

QQ|||iFix 爱修网 ( 粤ICP备2021135374号 )

粤公网安备 44060602002064号

GMT+8, 2024-4-20 02:08 , Processed in 0.050294 sec., 9 queries .

Powered by Discuz! X3.4

Release 20191201, © 2001-2024 Comsenz Inc.

MultiLingual version, Rev. 850, © 2009-2024 codersclub.org

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