Дамп нонейм регистратора 2516he

Вопросы по восстановлению, настройке, апгрейду, прошивкам и т.п.
Ответить
ivavictor
Новичок
Сообщения: 20
Зарегистрирован: 28 апр 2017, 10:33

Дамп нонейм регистратора 2516he

Сообщение ivavictor » 28 апр 2017, 10:48

Здравствуйте.
Умерла флеш нонейм регистратора. На прогере не читается даже ID.
Материнская плата 2516HE_v1.1
Платформа hi3520v100
Флеш Spansion S29AL016
Видео Techwell TW2864H
Очень нужен полный дамп прошивки.

dede
Специалист
Сообщения: 1957
Зарегистрирован: 22 мар 2017, 15:02
Откуда: Луганск

Re: Дамп нонейм регистратора 2516he

Сообщение dede » 28 апр 2017, 12:38

фото платы, всех шильдиков

ivavictor
Новичок
Сообщения: 20
Зарегистрирован: 28 апр 2017, 10:33

Re: Дамп нонейм регистратора 2516he

Сообщение ivavictor » 28 апр 2017, 13:24

Спасибо за скорый ответ.
Изображение

И со снятой флешкой
Изображение

Вообще есть еще лог загрузки если надо.

oleglevsha
Специалист
Сообщения: 855
Зарегистрирован: 15 ноя 2014, 22:34
Откуда: alarmsystem-cctv
Контактная информация:

Re: Дамп нонейм регистратора 2516he

Сообщение oleglevsha » 28 апр 2017, 13:32

Умерла в момент снятия?
Если были логи то не умерла, мой спиртом и чистенькую клади в панель программатора...

ivavictor
Новичок
Сообщения: 20
Зарегистрирован: 28 апр 2017, 10:33

Re: Дамп нонейм регистратора 2516he

Сообщение ivavictor » 28 апр 2017, 14:40

Спасибо за совет. Давно уже заимел привычку промывать микросхему прежде чем в программатор совать. Сдувал ее не от безделья - регистратор висел на заставке

dede
Специалист
Сообщения: 1957
Зарегистрирован: 22 мар 2017, 15:02
Откуда: Луганск

Re: Дамп нонейм регистратора 2516he

Сообщение dede » 28 апр 2017, 16:30

если висел на заставке, снимать категорически не стоило. вычитывайте теперь ее и показывайте дамп

ivavictor
Новичок
Сообщения: 20
Зарегистрирован: 28 апр 2017, 10:33

Re: Дамп нонейм регистратора 2516he

Сообщение ivavictor » 02 май 2017, 09:54

Здравствуйте.
Не понимаю причины почему снимать не стоило. Совсем недавно поднял два аппарата заменой флеш с загрузкой в нее дампа другого производителя. Майны были с одинаковыми шильдиками.

Лог загрузки:

Код: Выделить всё

NAND:  NAND_ECC_NONE selected by board driver. This is not recommended !!
128 MiB


U-Boot 2008.10 (Jun  1 2010 - 14:26:55)

DRAM:   3 GB
Flash:  2 MB
In:    serial
Out:   serial
Err:   serial
close watch dog begin...............
dog_close
product type 50 === 2
*****+++++******* do_auto_update 201009200936
USB:   scanning bus for devices... 1 USB Device(s) found
0 Storage Device(s) found
Press CTRL-C to abort autoboot in NAND:  NAND_ECC_NONE selected by board driver. This is not recommended !!
128 MiB


U-Boot 2008.10 (Jun  1 2010 - 14:26:55)

DRAM:   3 GB
Flash:  2 MB
In:    serial
Out:   serial
Err:   serial
close watch dog begin...............
dog_close
product type 50 === 2
*****+++++******* do_auto_update 201009200936
USB:   scanning bus for devices... 1 USB Device(s) found
0 Storage Device(s) found
Press CTRL-C to abort autoboot in open logo
ntsc pal 1
logo image len 6534
current logo file len 0x6534
jpeg decoding ...
<<addr=0x800c0000, size=0x6534, vobuf=0xcfe00000>>
<<imgwidth=480, imgheight=320, linebytes=960>>
decode success!!!!
start addr color = 0

NAND read: device 0 offset 0x200000, size 0x100000
 1048576 bytes read: OK

NAND read: device 0 offset 0x300000, size 0x200000
Skipping bad block 0x00420000
 2097152 bytes read: OK

NAND read: device 0 offset 0x500000, size 0x300000
 3145728 bytes read: OK

NAND read: device 0 offset 0x0, size 0x200000
 2097152 bytes read: OK
## Booting kernel from Legacy Image at c1300000 ...
   Image Name:   hilinux
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    1423688 Bytes =  1.4 MB
   Load Address: e2800000
   Entry Point:  e2800000
   Loading Kernel Image ... OK
OK

Starting kernel ...

Uncompressing Linux........................................................................................... done, booting the kernel.
Linux version 2.6.24-rt1-hi3520v100 (root@localhost.localdomain) (gcc version 3.4.3 (release) (CodeSourcery ARM Q3cvs 2004)) #2010033002 Wed Mar 31 13:05:50 EST 2010
CPU: ARMv6-compatible processor [410fb767] revision 7 (ARMv7), cr=00c5387f
Machine: hi3520v100
Memory policy: ECC disabled, Data cache writeback
CPU0: D VIPT write-back cache
CPU0: I cache: 16384 bytes, associativity 4, 32 byte lines, 128 sets
CPU0: D cache: 16384 bytes, associativity 4, 32 byte lines, 128 sets
Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 38608
Kernel command line: mem=152M console=ttyAMA0,115200 root=/dev/mtdblock2 rootfstype=yaffs2 mtdparts=physmap-flash.0:2M(boot);hinand:13M(nand_boot),16M(nand_root),64M(user),32M(abk) pcimod=host pciclksel=2 mac=F6:55:5D:3A:17:73
PID hash table entries: 1024 (order: 10, 4096 bytes)
Console: colour dummy device 80x30
Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
Memory: 152MB = 152MB total
Memory: 151168KB available (2596K code, 239K data, 100K init)
Mount-cache hash table entries: 512
HI_VERSION=LINUX_2_6_24-M01C04FB01F @Hi3520v100R001_C_0_2_0 2010-03-12 13:45:01
CPU: Testing write buffer coherency: ok
net_namespace: 64 bytes
NET: Registered protocol family 16
Hisilicon clock system V0.01
PCI: device 0000:00:01.0 has unknown header type 14, ignoring.
PCI: device 0000:00:03.0 has unknown header type 20, ignoring.
PCI: device 0000:00:04.0 has unknown header type 20, ignoring.
PCI: device 0000:00:05.0 has unknown header type 20, ignoring.
PCI: device 0000:00:06.0 has unknown header type 20, ignoring.
PCI: device 0000:00:07.0 has unknown header type 20, ignoring.
PCI: device 0000:00:08.0 has unknown header type 20, ignoring.
PCI: device 0000:00:09.0 has unknown header type 20, ignoring.
PCI: device 0000:00:0a.0 has unknown header type 20, ignoring.
PCI: device 0000:00:0b.0 has unknown header type 20, ignoring.
PCI: device 0000:00:0c.0 has unknown header type 20, ignoring.
PCI: device 0000:00:0d.0 has unknown header type 20, ignoring.
PCI: device 0000:00:0e.0 has unknown header type 20, ignoring.
PCI: device 0000:00:0f.0 has unknown header type 20, ignoring.
PCI: device 0000:00:10.0 has unknown header type 20, ignoring.
PCI: device 0000:00:11.0 has unknown header type 20, ignoring.
PCI: device 0000:00:12.0 has unknown header type 20, ignoring.
PCI: device 0000:00:13.0 has unknown header type 20, ignoring.
PCI: device 0000:00:14.0 has unknown header type 20, ignoring.
PCI: device 0000:00:15.0 has unknown header type 20, ignoring.
PCI: device 0000:00:16.0 has unknown header type 20, ignoring.
PCI: device 0000:00:17.0 has unknown header type 20, ignoring.
PCI: device 0000:00:18.0 has unknown header type 20, ignoring.
PCI: device 0000:00:19.0 has unknown header type 20, ignoring.
PCI: device 0000:00:1a.0 has unknown header type 20, ignoring.
PCI: device 0000:00:1b.0 has unknown header type 20, ignoring.
PCI: device 0000:00:1c.0 has unknown header type 20, ignoring.
PCI: device 0000:00:1d.0 has unknown header type 20, ignoring.
PCI: device 0000:00:1e.0 has unknown header type 20, ignoring.
PCI: device 0000:00:1f.0 has unknown header type 20, ignoring.
PCI: bus0: Fast back to back transfers enabled
SCSI subsystem initialized
NET: Registered protocol family 2
Time: hisi_timer1 clocksource has been installed.
IP route cache hash table entries: 2048 (order: 1, 8192 bytes)
TCP established hash table entries: 8192 (order: 4, 65536 bytes)
TCP bind hash table entries: 8192 (order: 3, 32768 bytes)
TCP: Hash tables configured (established 8192 bind 8192)
TCP reno registered
NetWinder Floating Point Emulator V0.97 (double precision)
JFFS2 version 2.2. (NAND) © 2001-2006 Red Hat, Inc.
yaffs Mar 23 2010 11:29:43 Installing.
io scheduler noop registered
io scheduler deadline registered (default)
Serial: AMBA PL011 UART driver
uart:0: ttyAMA0 at MMIO 0x20090000 (irq = 12) is a AMBA/PL011
console [ttyAMA0] enabled
uart:1: ttyAMA1 at MMIO 0x200a0000 (irq = 12) is a AMBA/PL011
uart:2: ttyAMA2 at MMIO 0x200b0000 (irq = 13) is a AMBA/PL011
uart:3: ttyAMA3 at MMIO 0x200c0000 (irq = 13) is a AMBA/PL011
RAMDISK driver initialized: 4 RAM disks of 16384K size 4096 blocksize
loop: module loaded
PPP generic driver version 2.4.2
PPP Deflate Compression module registered
PPP BSD Compression module registered
PPP MPPE Compression module registered
NET: Registered protocol family 24
PPPoL2TP kernel driver, V1.0
Driver 'sr' needs updating - please use bus_type methods
SCSI Media Changer driver v0.25
Driver 'ch' needs updating - please use bus_type methods
physmap platform flash device: 04000000 at 80000000
physmap-flash.0: Found 1 x16 devices at 0x0 in 8-bit bank
 Amd/Fujitsu Extended Query Table at 0x0040
number of CFI chips: 1
cfi_cmdset_0002: Disabling erase-suspend-program due to code brokenness.
1 cmdlinepart partitions found on MTD device physmap-flash.0
Creating 1 MTD partitions on "physmap-flash.0":
0x00000000-0x00200000 : "boot"
NAND device: Manufacturer ID: 0xad, Chip ID: 0xf1 (Hynix NAND 128MiB 3,3V 8-bit)
NAND_ECC_NONE selected by board driver. This is not recommended !!
Scanning device for bad blocks
Bad eraseblock 33 at 0x00420000
Bad eraseblock 166 at 0x014c0000
Bad eraseblock 654 at 0x051c0000
Bad eraseblock 881 at 0x06e20000
4 cmdlinepart partitions found on MTD device hinand
hinand_probe 604<5>Creating 4 MTD partitions on "hinand":
0x00000000-0x00d00000 : "nand_boot"
0x00d00000-0x01d00000 : "nand_root"
0x01d00000-0x05d00000 : "user"
0x05d00000-0x07d00000 : "abk"
TCP cubic registered
Initializing XFRM netlink socket
NET: Registered protocol family 1
NET: Registered protocol family 17
yaffs: dev is 32505858 name is "mtdblock2"
yaffs: passed flags ""
yaffs: Attempting MTD mount on 31.2, "mtdblock2"
block 63 is bad
yaffs_read_super: isCheckpointed 0
VFS: Mounted root (yaffs2 filesystem).
Freeing init memory: 100K
init started:  BusyBox v1.1.2 (2010.03.12-05:40+0000) multi-call binary

            _ _ _ _ _ _ _ _ _ _ _ _
            \  _  _   _  _ _ ___
            / /__/ \ |_/
           / __   /  -  _ ___
          / /  / /  / /
  _ _ _ _/ /  /  \_/  \_ ______
___________\___\__________________

[RCS]: /etc/init.d/S00devs
[RCS]: /etc/init.d/S01udev
[RCS]: /etc/init.d/S80network
modprobe: module nls_iso8859-2 not found.
modprobe: failed to load module nls_iso8859-2
modprobe: module scsi_mod not found.
modprobe: failed to load module scsi_mod
modprobe: module nls_base not found.
modprobe: failed to load module nls_base
modprobe: module nls_cp437 not found.
modprobe: failed to load module nls_cp437
modprobe: module nls_iso8859-1 not found.
modprobe: failed to load module nls_iso8859-1
modprobe: module libata not found.
modprobe: failed to load module libata
modprobe: module scsi_mod not found.
modprobe: failed to load module scsi_mod
Driver 'sd' needs updating - please use bus_type methods
PCI: enabling device 0000:00:00.0 (0140 -> 0143)
0x403f: latency timer and cache line value !
*************** bar5: b0020000
!!!!!!!! mmio_base phy: ec072000  ctl: 8a !
sata_sil 0000:00:00.0: Applying R_ERR on DMA activate FIS errata fix
scsi0 : sata_sil
scsi1 : sata_sil
scsi2 : sata_sil
scsi3 : sata_sil
ata1: SATA max UDMA/100 mmio m1024@0xb0020000 tf 0xb0020080 irq 29
ata2: SATA max UDMA/100 mmio m1024@0xb0020000 tf 0xb00200c0 irq 29
ata3: SATA max UDMA/100 mmio m1024@0xb0020000 tf 0xb0020280 irq 29
ata4: SATA max UDMA/100 mmio m1024@0xb0020000 tf 0xb00202c0 irq 29
ata1: SATA link down (SStatus 0 SControl 310)
ata2: SATA link down (SStatus 0 SControl 310)
ata3: SATA link down (SStatus 0 SControl 310)
ata4: SATA link down (SStatus 0 SControl 310)
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
h2v100-ohci h2v100-ohci.0: h2v100-ohci
h2v100-ohci h2v100-ohci.0: new USB bus registered, assigned bus number 1
h2v100-ohci h2v100-ohci.0: irq 22, io mem 0x100a0000
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 2 ports detected
h2v100-ehci h2v100-ehci.0: h2v100-ehci
h2v100-ehci h2v100-ehci.0: new USB bus registered, assigned bus number 2
h2v100-ehci h2v100-ehci.0: irq 23, io mem 0x100b0000
h2v100-ehci h2v100-ehci.0: USB 0.0 started, EHCI 1.00, driver 10 Dec 2004
usb usb2: configuration #1 chosen from 1 choice
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 2 ports detected
Initializing USB Mass Storage driver...
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
usbcore: registered new interface driver usbhid
drivers/hid/usbhid/hid-core.c: v2.6:USB HID core driver
mice: PS/2 mouse device common for all mice
modprobe: module sg not found.
modprobe: failed to load module sg
modprobe: module cdrom not found.
modprobe: failed to load module cdrom
modprobe: module sr_mod not found.
modprobe: failed to load module sr_mod
yaffs: dev is 32505859 name is "mtdblock3"
yaffs: passed flags ""
yaffs: Attempting MTD mount on 31.3, "mtdblock3"
block 423 is bad
yaffs_read_super: isCheckpointed 0
modprobe: module nls_iso8859-2 not found.
modprobe: failed to load module nls_iso8859-2
modprobe: module scsi_mod not found.
modprobe: failed to load module scsi_mod
modprobe: module nls_base not found.
modprobe: failed to load module nls_base
modprobe: module nls_cp437 not found.
modprobe: failed to load module nls_cp437
modprobe: module nls_iso8859-1 not found.
modprobe: failed to load module nls_iso8859-1
modprobe: module libata not found.
modprobe: failed to load module libata
modprobe: module scsi_mod not found.
modprobe: failed to load module scsi_mod
insmod: cannot insert `/lib/modules/2.6.24-rt1-hi3520v100/kernel/drivers/usb/host/ohci-hcd.ko': File exists (-1): File exists
modprobe: failed to load module ohci-hcd
insmod: cannot insert `/lib/modules/2.6.24-rt1-hi3520v100/kernel/drivers/usb/host/ehci-hcd.ko': File exists (-1): File exists
modprobe: failed to load module ehci-hcd
insmod: cannot insert `/lib/modules/2.6.24-rt1-hi3520v100/kernel/drivers/usb/storage/usb-storage.ko': File exists (-1): File exists
modprobe: failed to load module usb-storage
No need to recovery program from USB
H2GMAC module init start!
H2GMAC MDIO Bus: probed
H2GMAC module init done!
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
current product used multi td3520 device
Hisilicon Media Memory Zone Manager
HISI_PCI-MF @Hi3520v100R001_C_0_2_0 (201010081336)2010-06-29 22:34:31
hi3520_boot_multichipv2.0

slot 2 npmemaddr is b0400000, pfmemaddr is b8000000
cfgaddr is b0020400
[pci_slave_load,562] interrupt status is 0
/mnt/mtd/modules/pci_boot/u-boot.bin will be load
Load image u-boot.bin use time 23931 uS
/mnt/mtd/modules/pci_boot/kernel.img will be load
Load image kernel.img use time 27918 uS
/mnt/mtd/modules/pci_boot/cramfs.initrd.img will be load
Load image cramfs.initrd.img use time 64472 uS
/mnt/mtd/modules/pci_boot/u-boot-slave.bin will be load
Load image u-boot-slave.bin use time 16448 uS
/mnt/mtd/modules/pci_boot/kernel-slave.img will be load
Load image kernel-slave.img use time 28443 uS
/mnt/mtd/modules/pci_boot/cramfs-slave.initrd.img will be load
Load image cramfs-slave.initrd.img use time 64986 uS
data transfered!
MMZ force removed: PHYS(0xC0000000, 0xC1FFFFFF), GFP=0, nBYTES=32768KB, NAME="ddr"
************************ boot slave ok ********************************
HISI_PCI-MF @Hi3520v100R001_C_0_2_0 (201010081336)2010-06-29 22:34:31
hi3520_pci_driver.c: v0.0
is_host 8192
************************ load pci trans ok ********************************
hal_dev->slot = 2
local id = 0
PCI: slot 3
PCI: host communicate hw layer setup!
************************ load pci mcc ok ********************************
*** Board tools : ver0.0.1_20060106  ***
[debug]: {source/utils/cmdshell.c:166}cmdstr:himm
0x20110104: 0x00009654 --> 0x00009654
*** Board tools : ver0.0.1_20060106  ***
[debug]: {source/utils/cmdshell.c:166}cmdstr:himm
0x20110100: 0x00000886 --> 0x00000886
*** Board tools : ver0.0.1_20060106  ***
[debug]: {source/utils/cmdshell.c:166}cmdstr:himm
0x2011010c: 0x00000002 --> 0x00000002
*** Board tools : ver0.0.1_20060106  ***
[debug]: {source/utils/cmdshell.c:166}cmdstr:himm
0x20110110: 0x00000006 --> 0x00000006
*** Board tools : ver0.0.1_20060106  ***
[debug]: {source/utils/cmdshell.c:166}cmdstr:himm
0x20110114: 0x00000007 --> 0x00000007
*** Board tools : ver0.0.1_20060106  ***
[debug]: {source/utils/cmdshell.c:166}cmdstr:himm
0x20110118: 0x00000006 --> 0x00000006
*** Board tools : ver0.0.1_20060106  ***
[debug]: {source/utils/cmdshell.c:166}cmdstr:himm
0x2011011c: 0x00000007 --> 0x00000007
*** Board tools : ver0.0.1_20060106  ***
[debug]: {source/utils/cmdshell.c:166}cmdstr:himm
0x20110128: 0x00010020 --> 0x00010020
*** Board tools : ver0.0.1_20060106  ***
[debug]: {source/utils/cmdshell.c:166}cmdstr:himm
0x2011012c: 0x000103A1 --> 0x000103A1
*** Board tools : ver0.0.1_20060106  ***
[debug]: {source/utils/cmdshell.c:166}cmdstr:himm
0x20110130: 0x00000005 --> 0x00000005
*** Board tools : ver0.0.1_20060106  ***
[debug]: {source/utils/cmdshell.c:166}cmdstr:himm
0x20110134: 0x00000005 --> 0x00000005
*** Board tools : ver0.0.1_20060106  ***
[debug]: {source/utils/cmdshell.c:166}cmdstr:himm
0x20110138: 0x00000004 --> 0x00000004
*** Board tools : ver0.0.1_20060106  ***
[debug]: {source/utils/cmdshell.c:166}cmdstr:himm
0x2011013c: 0x00000004 --> 0x00000004
*** Board tools : ver0.0.1_20060106  ***
[debug]: {source/utils/cmdshell.c:166}cmdstr:himm
0x20050078: 0x00008002 --> 0x00008002
*** Board tools : ver0.0.1_20060106  ***
[debug]: {source/utils/cmdshell.cHisilicon Media Memory Zone Manager
:166}cmdstr:himm
0x20120100: 0x00000444 --> 0x00000444
*** Board tools : ver0.0.1_20060106  ***
[debug]: {source/utils/cmdshell.c:166}cmdstr:himm
0x20120104: 0x00009654 --> 0x00009654
*** Board tools : ver0.0.1_20060106  ***
[debug]: {source/utils/cmdshell.c:166}cmdstr:himm
0x2012010c: 0x00010640 --> 0x00010640
*** Board tools : ver0.0.1_20060106  ***
[debug]: {source/utils/cmdshell.c:166}cmdstr:himm
0x20120110: 0x00000003 --> 0x00000003
*** Board tools : ver0.0.1_20060106  ***
[debug]: {source/utils/cmdshell.c:166}cmdstr:himm
0x20120114: 0x00000004 --> 0x00000004
*** Board tools : ver0.0.1_20060106  ***
[debug]: {source/utils/cmdshell.c:166}cmdstr:himm
0x20120118: 0x00000001 --> 0x00000001
*** Board tools : ver0.0.1_20060106  ***
[debug]: {source/utils/cmdshell.c:166}cmdstr:himm
0x2012011c: 0x00000002 --> 0x00000002
*** Board tools : ver0.0.1_20060106  ***
[debug]: {source/utils/cmdshell.c:166}cmdstr:himm
0x20120128: 0x00000005 --> 0x00000005
*** Board tools : ver0.0.1_2[ipcm_vdd_init, 422]: local_cpu_id = 36

0060106  ***
[[ipcm_vdd_close, 268]: handle  0xc8baed60

debug]: {source/[ipcm_vdd_init, 455]: IPCM hardware initialized successfully 0

utils/cmdshell.c:166}cmdstr:himm
0x2012012c: 0x00000005 --> 0x00000005
*** Board tools : ver0.0.1_20060106  ***
[debug]: {source/utils/cmdshell.c:166}cmdstr:himm
0x20120130: 0x00000005 --> 0x00000005
*** Board tools : ver0.0.1_20060106  ***
[debug]: {source/utils/cmdshell.c:166}cmdstr:himm
0x20120134: 0x00000005 --> 0x00000005
*** Board tools : ver0.0.1_20060106  ***
[debug]: {source/utils/cmdshell.c:166}cmdstr:himm
0x20120138: 0x00000005 --> 0x00000005
*** Board tools : ver0.0.1_20060106  ***
[debug]: {source/utils/cmdshell.c:166}cmdstr:himm
0x2012013c: 0x00000005 --> 0x00000005
i2c version : 201008131741
mdin240 version: 201003301820
mdin240 input is 1080i50
mdin240 output is 1080p50
m240 no exist
mdin240 [mdin240_init ,468]: mdin240 device init fail,deregister it!
insmod: cannot insert `extdrv/m240.ko': Operation not permitted (-1): Operation not permitted
norm:2,chips:4===> 201009021655
current tw2864 addr 50, id 6b,0, valild 1
current tw2864 addr 52, id 6b,0, valild 1
current tw2864 addr 54, id 6b,0, valild 1
current tw2864 addr 56, id 6b,0, valild 1
tw2864 0x50 init ok !
tw2864 0x52 init ok !
tw2864 0x54 init ok !
tw2864 0x56 init ok !
tw2864 driver init successful!
current chip perhaps is TW2864 chip

insmod: cannot insert `extdrv/nvp1104a.ko': Operation not permitted (-1): Operation not permitted
aic23 driver init successful 201008101636!
2408  rtc Device Driver 201004131024 v1.0.0
TVT 35xx CryptoMemory Device Driver v1.0.0: May  9 2010 06:35:40
hifb: module license 'Proprietary' taints kernel.
hifb info: HIFB_MAIN_VERSION[v1.0.0.2] Build Time[Aug 11 2010, 16:31:43]
hifb info: video:vram0_size=2073600,vram1_size=16588800,vram2_size=1024,vram3_size=10485760,vram4_size=1024
hifb info: succeed in registering the fb0: ovl0 frame buffer device
hifb info: succeed in registering the fb1: ovl1 frame buffer device
hifb info: succeed in registering the fb2: ovl2 frame buffer device
hifb info: succeed in registering the fb3: ovl3 frame buffer device
hifb info: succeed in registering the fb4: ovl4 frame buffer device
TDE_MAIN_VERSION[v2.0.0.0] Build Time[Aug 11 2010, 16:31:46]
TDE_ADP_VERSION[hi3520adp v2.0.0.0] Build Time[Aug 11 2010, 16:31:46]
tde run on master arm
tde run for graphic service
tde map reg:basePhyAddr:20140000 baseVirAddr:ca09c000 size:3000
Hisilicon UMAP device driver interface: v3.00
Chip Version: Hi35200100
load vd.ko ....OK!
load simd.ko OK
load vdec.ko ....OK
load vpp.ko ....OK!
load md.ko....OK!
modprobe: module nls_iso8859-2 not found.
modprobe: failed to load module nls_iso8859-2
modprobe: module scsi_mod not found.
modprobe: failed to load module scsi_mod
modprobe: module nls_base not found.
modprobe: failed to load module nls_base
modprobe: module nls_cp437 not found.
modprobe: failed to load module nls_cp437
modprobe: module nls_iso8859-1 not found.
modprobe: failed to load module nls_iso8859-1
modprobe: module libata not found.
modprobe: failed to load module libata
modprobe: module scsi_mod not found.
modprobe: failed to load module scsi_mod
insmod: cannot insert `/lib/modules/2.6.24-rt1-hi3520v100/kernel/drivers/usb/host/ohci-hcd.ko': File exists (-1): File exists
modprobe: failed to load module ohci-hcd
insmod: cannot insert `/lib/modules/2.6.24-rt1-hi3520v100/kernel/drivers/usb/host/ehci-hcd.ko': File exists (-1): File exists
modprobe: failed to load module ehci-hcd
insmod: cannot insert `/lib/modules/2.6.24-rt1-hi3520v100/kernel/drivers/usb/storage/usb-storage.ko': File exists (-1): File exists
modprobe: failed to load module usb-storage
modprobe: module sg not found.
modprobe: failed to load module sg
modprobe: module cdrom not found.
modprobe: failed to load module cdrom
modprobe: module sr_mod not found.
modprobe: failed to load module sr_mod
io scheduler anticipatory registered
./load_master: ./load_master: 299: cannot create /sys/block/sda/queue/scheduler: Directory nonexistent
./load_master: ./load_master: 299: cannot create /sys/block/sdb/queue/scheduler: Directory nonexistent
./load_master: ./load_master: 299: cannot create /sys/block/sdc/queue/scheduler: Directory nonexistent
./load_master: ./load_master: 299: cannot create /sys/block/sdd/queue/scheduler: Directory nonexistent
./load_master: ./load_master: 299: cannot create /sys/block/sde/queue/scheduler: Directory nonexistent
./load_master: ./load_master: 299: cannot create /sys/block/sdf/queue/scheduler: Directory nonexistent
./load_master: ./load_master: 299: cannot create /sys/block/sdg/queue/scheduler: Directory nonexistent
./load_master: ./load_master: 299: cannot create /sys/block/sdh/queue/scheduler: Directory nonexistent
************************ load hi3520 mpp ok ********************************
************************ load hi3520 mpp ok ********************************
rm: cannot remove `/mnt/mtd/preupgrade.sh': No such file or directory
rm: cannot remove `/mnt/mtd/productcheck': No such file or directory
mkdir: Cannot create directory `/mnt/backup': File exists
yaffs: dev is 32505860 name is "mtdblock4"
yaffs: passed flags ""
yaffs: Attempting MTD mount on 31.4, "mtdblock4"
yaffs: restored from checkpoint
yaffs_read_super: isCheckpointed 1
Auto login as root ...
Jan  1 00:00:17 login[800]: root login  on `ttyS000'



BusyBox v1.1.2 (2010.03.12-05:40+0000) Built-in shell (ash)
Enter 'help' for a list of built-in commands.

Welcome to HiLinux.
None of nfsroot found in cmdline.
~ $ xdvr.cpp, 464, pid = 803
check OK!
LocalDevice.cpp,2768,old crytoinfo
------------current param type == 2
productID:702,subProductID:0
xdvr.cpp,502,programeId:0,subProductID:0.xdvr.cpp,521,g_bProIdequeSubProdID:1
product Item (Product.cpp,307)from programe
------------current param type == 1
Initial product manager succ!
------------current param type == 7
------------current param type == 6
LocalDevice.cpp,2714,GetKeyBoardNameFromFlash:------
xdvr.cpp,582, no need ChangeKeyBoardType
xdvr.cpp,584,local keyboardtype;0
PHY: 0:01 - Link is Down
Intial CLanguagePack succ!
------------current param type == 5
Initial ReadDDdns ok
Inital config manager succ
Mcu8952.cpp, 396, pid = 812
check OK!
***==0==***cryptomemory ok
------------current param type == 1026
 DVR SDK VERSION : *** 201101211501 ***
current alloc buf variant len = 1327072
set default value = 1000
current jiffts value = 1000
alloc m_pb_buf_addr = 40528000, 4194304
alloc m_compress_buf_addr 40930000, 39845888
all used mem len 45187072

alloc var buffer add 40311730, len 347032
Current TD2516HE DVR Product Param Init
current decode chip number = 4
get current decode chip type 1001
tw2864 select playback audio out
set_audio_mix_out ok
[          IPCM_Check, 222]: remote not ready, now connect and wait ...
[          IPCM_Check, 252]: remote connected
cur device 1 baseaddr b8000000
open pci device number = 3
open msg port, s32TgtId:3, port:81
open msg port, s32TgtId:3, port:82
open msg port, s32TgtId:3, port:83
start check pci target id:3  ... ... ...


dede
Специалист
Сообщения: 1957
Зарегистрирован: 22 мар 2017, 15:02
Откуда: Луганск

Re: Дамп нонейм регистратора 2516he

Сообщение dede » 02 май 2017, 18:25

Ой ё... так у вас и флеш и нанд.

В любом случае, если вот такие вот логи у вас сейчас выводятся, а не до экспериментов, но все в порядке, просто побился раздел с конфигурацией, отформатировать его и всё заработает, скорее всего

ivavictor
Новичок
Сообщения: 20
Зарегистрирован: 28 апр 2017, 10:33

Re: Дамп нонейм регистратора 2516he

Сообщение ivavictor » 04 май 2017, 09:48

Откуда такие мысли?

dede
Специалист
Сообщения: 1957
Зарегистрирован: 22 мар 2017, 15:02
Откуда: Луганск

Re: Дамп нонейм регистратора 2516he

Сообщение dede » 04 май 2017, 17:19

как откуда? хотя бы из ваших логов. вы же понимаете что ваш нор флеш объёмом 16 Мбит и прошивка туда никак не поместится. там всего лишь первый бут находится, который уже грузит с нанда второй бут

Ответить

Вернуться в «Восстановление и настройка»