Помогите с дампом камеры Dahua DH-IPC-HDW1200SP-0360B

Danakkroid

Active member
Ищу дамп на данную камеру, доступ по uart есть , там камера в циклической перезагрузке, Спасибо заранее за помощь!
 

Danakkroid

Active member
Сделал как Вы посоветовали, вот что получилось:

DHBOOT# reset
Checking DDR......OK

UBL Version: 1.43t(DM368 12/25/2012)
Oscillator: 24MHZ
ARM Rate: 432 MHZ
DDR Rate: 340 MHZ
start watchdog
BootMode: SPI
Starting SPI Memory Copy...
DONE


U-Boot 1.3.6 (jerry) (Sep 1 2014 - 19:32:54)

DRAM: 128 MB
SF: Got idcode ef 40 17
SF: Detected W25Q64 with page size 256, total 8 MB
In: serial
Out: serial
Err: serial
Ethernet PHY: GENERIC @ 0x03,id:221513
total gio 2
gio[22]=1
gio[25]=1
Loading...
TFTP from server 192.168.254.254; our IP address is 192.168.1.108; sending through gateway 192.168.1.1
Filename 'upgrade_info_7db780a713a4.txt'.
Load address: 0x80100000
Loading: WARN: emac_send_packet: No link

Retry count exceeded; starting again
Fail to get info file!
Init error!
TFTP from server 192.168.254.254; our IP address is 192.168.1.108; sending through gateway 192.168.1.1
Filename 'failed.txt'.
Load address: 0x80200000
Loading: WARN: emac_send_packet: No link

Retry count exceeded; starting again
==>use default images
## Booting kernel from Legacy Image at 80800000 ...
Image Name: boot
Image Type: ARM Linux Kernel Image (lzma compressed)
Data Size: 1041397 Bytes = 1017 kB
Load Address: 80008000
Entry Point: 80008000
Verifying Checksum ... OK
Uncompressing Kernel Image ... OK

Starting kernel ...

init started: BusyBox v1.9.1 (2014-05-22 15:49:36 CST)
starting pid 129, tty '': '/etc/init.d/dnode'
mount: mounting devpts on /dev/pts failed: No such file or directory
mount: mounting none on /proc/bus/usb failed: No such file or directory
starting pid 148, tty '': '/etc/init.d/rcS'
[gpio] *
Tue Nov 30 00:18[gpio] Build on Nov 16 2013 at 16:27:42.
:07 1999 0.0000[gpio] SVN NUM: 3402.
00 seconds
[gpio] *
[gpio] dm365_gpio_init
[gpio] CMD=9, Setting product type: 40

[lib[gpio] CMD=4, Setting product fchip: 21
dvr] libdvr.so B[gpio] CMD=3, Setting hardware version: 0
uild on May 22 2014 at 14:23:12.
[libdvr] SVN NUM: 5830.
[libdvr] ...dataBuf[0] 26, dataBuf[1] 4
[libdvr] Real fchip type is 21
NET_getFlagFile read flag fail, status: 0
[gpio] IPC_HFW2200B_V2<6>MAC address is 4C:11:BF:B0:88:FB
TI DaVinci EMAC Linux version updated 4.0

[libdvr] libdvr.so Build on May 22 2014 at 14:23:12.
[libdvr] SVN NUM: 5830.
[libdvr] ...dataBuf[0] 26, dataBuf[1] 4
[libdvr] Real fchip type is 21
only init eth0
"netinit help" for help
eth0:
MAC: <4c:11:bf:b0:88:fb>
IP: <192.168.1.6> netmask: <255.255.255.0>
Gateway: <192.168.1.6>
[libdvr] set success

IPV6: only init eth0
"netinit6 help" for help
eth0:
MAC: <4c:11:bf:b0:88:fb>
IPV6: <2001:250:3000:1::1:2> preFixLen: <112>
[libdvr] WARN (../../src/net/network6.c|NetWorkDelIP|999): del ip failed:No such device or address
IPV6 Gateway: <2001:250:3000:1::1:1>


[libdvr] libdvr.so Build on May 22 2014 at 14:23:12.
[libdvr] SVN NUM: 5830.
[libdvr] ...dataBuf[0] 26, dataBuf[1] 4
[libdvr] Real fchip type is 21
type:40, Model=IPC-HFW2200B-V2

[libdvr] libdvr.so Build on May 22 2014 at 14:23:12.
[libdvr] SVN NUM: 5830.

[li[bd6735] bd6735.ko Build on Nov 16 2013 at 15:36:10.
bdvr] ...dataBuf[bd6735] SVN NUM: 3486.
[0] 26, dataBuf[1] 4
[libdvr] Real fchip type is 2[bd6735] IPC-HFW3101C class IR-CUT,control by IO port
1
IPC Device
[bd6735] <6>BD6735 MOTOR init:bd6735!
[bd6735] BD6735 Initial OK
[bd6735] ....turn into find ZERO.....

[libdvr] libdvr.so Build on May 22 2014 at 14:23:12.
[libdvr] SVN NUM: 5830.

[libdvr] libdvr.so Build on May 22 2014 at 14:23:12.
[libdvr] SVN NUM: 5830.
[libdvr] ...dataBuf[0] 26, dataBuf[1] 4
[libdvr] Real fchip type is 21
syshelper V1.13(no exit): startup time=120 s, appauto=1, hctosystime=1500,type=IPC-HFW2200B-V2
[libdvr] ...dataBuf[0] 26, dataBuf[1] 4
[libdvr] Real fchip type is 21
coremnt not found

[libdvr] libdvr.so Build on May 22 2014 at 14:23:12.
[libdvr] SVN NUM: 5830.
[libdvr] ...dataBuf[0] 26, dataBuf[1] 4
[libdvr] Real fchip type is 21

[libdvr] libdvr.so Build on May 22 2014 at 14:23:12.
[libdvr] SVN NUM: 5830.
[libdvr] ...dataBuf[0] 26, dataBuf[1] 4
[libdvr] Real fchip type is 21

[libdvr] libdvr.so Build on May 22 2014 at 14:23:12.
[libdvr] SVN NUM: 5830.
[libdvr] ...dataBuf[0] 26, dataBuf[1] 4
[libdvr] Real fchip type is 21

[libdvr] libdvr.so Build on May 22 2014 at 14:23:12.
[libdvr] SVN NUM: 5830.
[libdvr] ...dataBuf[0] 26, dataBuf[1] 4
[libdvr] Real fchip type is 21

[libdvr] libdvr.so Build on May 22 2014 at 14:23:12.
[libdvr] SVN NUM: 5830.
[libdvr] ...dataBuf[0] 26, dataBuf[1] 4
[libdvr] Real fchip type is 21

[libdvr] libdvr.so Build on May 22 2014 at 14:23:12.
[libdvr] SVN NUM: 5830.
[libdvr] ...dataBuf[0] 26, dataBuf[1] 4
[libdvr] Real fchip type is 21
IPC-HFW2200B-V2

[dm365_ad] dm365_ad.ko Build on Oct 14 2013 at 19:08:10.
[dm365_ad] SVN NUM: 10713.
[dm365_ad] ==Enable ADC PSC successfully!==
[dm365_ad] dm365_ad init:dm365_ad!
[spi] Build on Feb 25 2013 at 15:07:33.
[spi] SVN NUM: 2603.
[spi] kernel: spi module insmod. SPIPLLK = 18
[spi] Start to set PSC and enable spi
[spi] Start to set PSC and enable RTCIF
[spi] Set RTC PSC success
[spi] DH_PDT_ITC142_GB3A: Init PRTCSS Device
PERI_CLKCTL:0x640f04fc
[spi] pinmux4 is 0xaa800016
[spi] @@: SPI1 CLK Param :prescale = 11

[sensor] Sensor.ko Build on Jan 13 2015 at 16:31:49.
[sensor] SVN NUM: 4466.
[sensor] The Sensor Driver Version:Ver 2.0
[sensor] Found I2C Device (i2c addr 0x18)
[sensor] The AR0330 model ID is 0x2604
[sensor] ar0330 init ok!
[sensor] We found the sensor chip: ar0330 on i2c bus
[sensor] sensor device init success
[Crypt] platType = [0], DM36X = [0], A5S_CRYPT = [1], hi351x=[2].
[Crypt] major = [253], minor = [0]
[Crypt] CRYPT_setChipOps ......
[Crypt] GIO = [1], g_dh_hardware_encode = [2]
[Crypt] CRYPT_authenticate ......
error: write byte error
error: write_nbytes failed
error: authentication failed
error: authenticate failed
[Crypt] ERROR (/home/li_guang/DM368_driver/IPC_cryptDrv/crypt/P_2013.02.22_CryptoMemory_DM8127_IPC/build/../src/crypt.c|crypt_init|1250): CRYPT_authenticate failed!
[Crypt] ERROR (/home/li_guang/DM368_driver/IPC_cryptDrv/crypt/P_2013.02.22_CryptoMemory_DM8127_IPC/build/../src/crypt.c|crypt_init|1251): reboot........
 

Danakkroid

Active member
нашел данную тему,


там Вы предлагали пару прошивок на схожую камеру, но к сожалению не могу зарегистрироваться там на сайте, не принимает мой номер телефона, пожалуйста проверьте, подойдут ли мне данные прошивки? Спасибо!
 

Техпідтримка VidiMost.com

Спеціаліст
Команда форуму
Вам нужны спец прошивки для восстановления, поэтому качать там с сайта Видимоста нечего пока не восстановите.
 

Техпідтримка VidiMost.com

Спеціаліст
Команда форуму
https://support.vidimost.com/files/update.img_dm365_ubl_boot_dh_ipc-hx3(2)xxx_eng_p_8m_v2.420.0001.0.r.20161208.7z
кладите файлы в tftp каталог, останавливайте загрузку и пишите:
setenv ipaddr - айпи камеры
setenv serverip - айпи Вашего компа
run up
cfgRestore или
erasepart config
erasepart backup
saveenv
reset

если все ок, то остановите загрузку и напишите:
setenv dh_keyboard 1
saveenv
reset
 

Danakkroid

Active member
Спасибо, у меня ощущение что по данному оборудованию Дахуа вы единственный специалист, писал на многие форумы но результат 0, а вы за короткое время мне помогли с регистратором nvr5432 и ещё с камерой , спасибо за поддержку! Вечером попробую, о результате отпишусь!
 

Danakkroid

Active member
DHBOOT# cfgRestore
Unknown command 'cfgRestore' - try 'help'
DHBOOT# erasepart config
Unknown command 'erasepart' - try 'help'
DHBOOT# erasepart backup
Unknown command 'erasepart' - try 'help'

что делать дальше? run up прошла удачно, по окончании Done!
 

Danakkroid

Active member
DHBOOT# help
? - alias for 'help'
autoscr - run script from memory
base - print or set address offset
boot - boot default, i.e., run 'bootcmd'
bootd - boot default, i.e., run 'bootcmd'
bootm - boot application image from memory
bootp - boot image via network using BootP/TFTP protocol
cmp - memory compare
coninfo - print console devices and information
cp - memory copy
cpll - chang PLL multiplier
crc32 - checksum calculation
echo - echo args to console
erase - erase FLASH memory
flinfo - print FLASH memory information
flwrite - write data into FLASH memory
fsload - load binary file from a filesystem image
gpio init - set gionum to gioval
go - start application at address 'addr'
help - print online help
flwrite - write hwid into FLASH memory
id - set product id and save to flash
iminfo - print header information for application image
lip - set local ip address but not save to flash
loadb - load binary file over serial line (kermit mode)
loads - load S-Record file over serial line
loady - load binary file over serial line (ymodem mode)
loop - infinite loop on address range
mac - set mac address and save to flash
md - memory display
meminit - memset 0xcc
memsize - set mem size
mii - MII utility commands
mm - memory modify (auto-incrementing)
mtest - simple RAM test
mw - memory write (fill)
nm - memory modify (constant address)
ping - send ICMP ECHO_REQUEST to network host
printenv- print environment variables
protect - enable or disable FLASH write protection
rarpboot- boot image via network using RARP/TFTP protocol
recover default env
reset - Perform RESET of the CPU
run - run commands in an environment variable
saveenv - save environment variables to persistent storage
saves - save S-Record file over serial line
setenv - set environment variables
sf - spi and nor flash sub-system
probe [bus:]cs [hz] [mode] - init flash device on given SPI bus
and chip select
sf write addr offset len - write len' bytes from memory
at
addr' to flash at offset'
sf erase startaddr endaddr - erase bytes from
startaddr' to `endaddr'
sip - set server ip address but not save to flash
tftpboot- boot image via network using TFTP protocol
uartUp- update image via uart using uart1
version - print monitor version
DHBOOT#
 

Danakkroid

Active member
Предположил что команды следующего вида подойдут,
erase config
erase backup
saveenv
reset

и после получил следующее:

DHBOOT# erase config
DHBOOT# erase backup
DHBOOT# saveenv
Saving Environment to SPI Flash...
SPI Erasing:100%
SPI Writing:100%
done
DHBOOT# reset
Checking DDR......OK

UBL Version: 1.43t(DM368 12/25/2012)
Oscillator: 24MHZ
ARM Rate: 432 MHZ
DDR Rate: 340 MHZ
start watchdog
BootMode: SPI
Starting SPI Memory Copy...
DONE


U-Boot 1.3.6 (jerry) (Sep 1 2014 - 19:32:54)

DRAM: 128 MB
SF: Got idcode ef 40 17
SF: Detected W25Q64 with page size 256, total 8 MB
In: serial
Out: serial
Err: serial
Ethernet PHY: GENERIC @ 0x03,id:221513
total gio 2
gio[22]=1
gio[25]=1
Loading...
TFTP from server 192.168.254.254; our IP address is 192.168.1.108; sending through gateway 192.168.1.1
Filename 'upgrade_info_7db780a713a4.txt'.
Load address: 0x80100000
Loading: *
Retry count exceeded; starting again
Fail to get info file!
Init error!
TFTP from server 192.168.254.254; our IP address is 192.168.1.108; sending through gateway 192.168.1.1
Filename 'failed.txt'.
Load address: 0x80200000
Loading: *
Retry count exceeded; starting again
==>use default images
## Booting kernel from Legacy Image at 80800000 ...
Image Name: boot
Image Type: ARM Linux Kernel Image (lzma compressed)
Data Size: 1041397 Bytes = 1017 kB
Load Address: 80008000
Entry Point: 80008000
Verifying Checksum ... OK
Uncompressing Kernel Image ... OK

Starting kernel ...

init started: BusyBox v1.9.1 (2016-12-07 11:34:14 CST)
starting pid 129, tty '': '/etc/init.d/dnode'
mount: mounting devpts on /dev/pts failed: No such file or directory
mount: mounting none on /proc/bus/usb failed: No such file or directory
starting pid 148, tty '': '/etc/init.d/rcS'
[gpio] *
Tue Nov 30 01:03[gpio] Build on Nov 16 2013 at 16:27:42.
:54 1999 0.0000[gpio] SVN NUM: 3402.
00 seconds
[gpio] *
[gpio] dm365_gpio_init
[gpio] CMD=9, Setting product type: 40

[lib[gpio] CMD=4, Setting product fchip: 21
dvr] libdvr.so B[gpio] CMD=3, Setting hardware version: 0
uild on May 22 2014 at 14:23:12.
[libdvr] SVN NUM: 5830.
[libdvr] ...dataBuf[0] 26, dataBuf[1] 4
[libdvr] Real fchip type is 21
NET_getFlagFile read flag fail, status: 0
[gpio] IPC_HFW2200B_V2<6>MAC address is 4C:11:BF:B0:88:FB
TI DaVinci EMAC Linux version updated 4.0

[libdvr] libdvr.so Build on May 22 2014 at 14:23:12.
[libdvr] SVN NUM: 5830.
[libdvr] ...dataBuf[0] 26, dataBuf[1] 4
[libdvr] Real fchip type is 21
only init eth0
"netinit help" for help
eth0:
MAC: <4c:11:bf:b0:88:fb>
EthIndex=1!
NetSetDefaultEth eth0 ok!
IP: <192.168.1.6> netmask: <255.255.255.0>
Gateway: <192.168.1.6>
[libdvr] set success

IPV6: only init eth0
"netinit6 help" for help
eth0:
MAC: <4c:11:bf:b0:88:fb>
IPV6: <2001:250:3000:1::1:2> preFixLen: <112>
[libdvr] WARN (../../src/net/network6.c|NetWorkDelIP|999): del ip failed:No such device or address
IPV6 Gateway: <2001:250:3000:1::1:1>


[libdvr] libdvr.so Build on May 22 2014 at 14:23:12.
[libdvr] SVN NUM: 5830.
[libdvr] ...dataBuf[0] 26, dataBuf[1] 4
[libdvr] Real fchip type is 21
type:40, Model=IPC-HFW2200B-V2

[libdvr] libdvr.so Build on May 22 2014 at 14:23:12.
[libdvr] SVN NUM: 5830.

[li[bd6735] bd6735.ko Build on Nov 16 2013 at 15:36:10.
bdvr] ...dataBuf[bd6735] SVN NUM: 3486.
[0] 26, dataBuf[1] 4
[libdvr] Real fchip type is 2[bd6735] IPC-HFW3101C class IR-CUT,control by IO port
1
IPC Device
[bd6735] <6>BD6735 MOTOR init:bd6735!
[bd6735] BD6735 Initial OK
[bd6735] ....turn into find ZERO.....

[libdvr] libdvr.so Build on May 22 2014 at 14:23:12.
[libdvr] SVN NUM: 5830.

[libdvr] libdvr.so Build on May 22 2014 at 14:23:12.
[libdvr] SVN NUM: 5830.
[libdvr] ...dataBuf[0] 26, dataBuf[1] 4
[libdvr] Real fchip type is 21
syshelper V1.13(no exit): startup time=120 s, appauto=1, hctosystime=1500,type=IPC-HFW2200B-V2
[libdvr] ...dataBuf[0] 26, dataBuf[1] 4
[libdvr] Real fchip type is 21
coremnt not found

[libdvr] libdvr.so Build on May 22 2014 at 14:23:12.
[libdvr] SVN NUM: 5830.
[libdvr] ...dataBuf[0] 26, dataBuf[1] 4
[libdvr] Real fchip type is 21

[libdvr] libdvr.so Build on May 22 2014 at 14:23:12.
[libdvr] SVN NUM: 5830.
[libdvr] ...dataBuf[0] 26, dataBuf[1] 4
[libdvr] Real fchip type is 21

[libdvr] libdvr.so Build on May 22 2014 at 14:23:12.
[libdvr] SVN NUM: 5830.
[libdvr] ...dataBuf[0] 26, dataBuf[1] 4
[libdvr] Real fchip type is 21

[libdvr] libdvr.so Build on May 22 2014 at 14:23:12.
[libdvr] SVN NUM: 5830.
[libdvr] ...dataBuf[0] 26, dataBuf[1] 4
[libdvr] Real fchip type is 21

[libdvr] libdvr.so Build on May 22 2014 at 14:23:12.
[libdvr] SVN NUM: 5830.
[libdvr] ...dataBuf[0] 26, dataBuf[1] 4
[libdvr] Real fchip type is 21

[libdvr] libdvr.so Build on May 22 2014 at 14:23:12.
[libdvr] SVN NUM: 5830.
[libdvr] ...dataBuf[0] 26, dataBuf[1] 4
[libdvr] Real fchip type is 21
IPC-HFW2200B-V2

[dm365_ad] dm365_ad.ko Build on Oct 14 2013 at 19:08:10.
[dm365_ad] SVN NUM: 10713.
[dm365_ad] ==Enable ADC PSC successfully!==
[dm365_ad] dm365_ad init:dm365_ad!
[spi] Build on Feb 25 2013 at 15:07:33.
[spi] SVN NUM: 2603.
[spi] kernel: spi module insmod. SPIPLLK = 18
[spi] Start to set PSC and enable spi
[spi] Start to set PSC and enable RTCIF
[spi] Set RTC PSC success
[spi] DH_PDT_ITC142_GB3A: Init PRTCSS Device
PERI_CLKCTL:0x640f04fc
[spi] pinmux4 is 0xaa800016
[spi] @@: SPI1 CLK Param :prescale = 11

[sensor] Sensor.ko Build on Jul 3 2014 at 10:31:24.
[sensor] SVN NUM: 4335.
[sensor] The Sensor Driver Version:Ver 2.0
[sensor] Found I2C Device (i2c addr 0x18)
[sensor] The AR0330 model ID is 0x2604
[sensor] ar0330 init ok!
[sensor] We found the sensor chip: ar0330 on i2c bus
[sensor] sensor device init success
[Crypt] platType = [0], DM36X = [0], A5S_CRYPT = [1], hi351x=[2].
[Crypt] major = [253], minor = [0]
[Crypt] CRYPT_setChipOps ......
[Crypt] GIO = [1], g_dh_hardware_encode = [2]
[Crypt] CRYPT_authenticate ......
error: write byte error
error: write_nbytes failed
error: authentication failed
error: authenticate failed
[Crypt] ERROR (/home/li_guang/DM368_driver/IPC_cryptDrv/crypt/P_2013.02.22_CryptoMemory_DM8127_IPC/build/../src/crypt.c|crypt_init|1250): CRYPT_authenticate failed!
[Crypt] ERROR (/home/li_guang/DM368_driver/IPC_cryptDrv/crypt/P_2013.02.22_CryptoMemory_DM8127_IPC/build/../src/crypt.c|crypt_init|1251): reboot........

DHBOOT# printenv
bootdelay=3
baudrate=115200
wifiaddr=00:01:5b:00:77:88
bootfile="uImage"
appauto=1
single=0
dc=tftp 81a00000 custom-x.cramfs.img; flwrite
dr=tftp 81a00000 romfs-x.cramfs.img; flwrite
du=tftp 81a00000 user-x.cramfs.img; flwrite
dd=tftp 81a00000 data-x.cramfs.img; flwrite
dw=tftp 81a00000 web-x.cramfs.img; flwrite
up=tftp 81a00000 update.img; flwrite
tk=tftp 80800000 uImage; bootm 80800000
gionum=22.25
gioval=1.1
dh_com=0
autosip=192.168.254.254
autolip=192.168.1.108
autogw=192.168.1.1
autonm=255.255.255.0
BSN=1C0133CPAF02724
HWID=IPC-HFW2200B-V2:01:02:02:03:05:00:01:00:00:00:00:1B0:00:00:02:00:00:00:00:00:80
devalias=DH-IPC-HDW1200SP
bootcmd=fsload 0x80800000 0x00060000;bootm 0x80800000
bootargs=console=ttyS0,115200n8 root=/dev/mtdblock4 rootfstype=squashfs ,nolock mem=78M video=davincifb:vid0=OFF:vid1=OFF:eek:sd0=OFF:eek:sd1=OFF
da=protect off all;tftp 81a00000 dm365_ubl_boot_8M_spiflash.bin.img;flwrite
ID=1C038B2PAF00168
ethaddr=4C:11:BF:B0:88:FB
restore=1
 

Техпідтримка VidiMost.com

Спеціаліст
Команда форуму
Crypt] platType = [0], DM36X = [0], A5S_CRYPT = [1], hi351x=[2].
[Crypt] major = [253], minor = [0]
[Crypt] CRYPT_setChipOps ......
[Crypt] GIO = [1], g_dh_hardware_encode = [2]
[Crypt] CRYPT_authenticate ......
error: write byte error
error: write_nbytes failed
error: authentication failed
error: authenticate failed
[Crypt] ERROR (/home/li_guang/DM368_driver/IPC_cryptDrv/crypt/P_2013.02.22_CryptoMemory_DM8127_IPC/build/../src/crypt.c|crypt_init|1250): CRYPT_authenticate failed!
[Crypt] ERROR (/home/li_guang/DM368_driver/IPC_cryptDrv/crypt/P_2013.02.22_CryptoMemory_DM8127_IPC/build/../src/crypt.c|crypt_init|1251): reboot........
не нравится мне эта часть, видать крипточип навернулся....
@Oleglevsha @fobos гляньте глазком пожалуйста!
 

Danakkroid

Active member
Возможен вариант что HWID был изменен и поэтому ничего не выходит? отдавал ее человеку, что-то пытался залить, но после неудачи вернул обратно
 

Danakkroid

Active member
Наклейка камеры
1541
Пробовал говорит прошить но ничего не вышло, а как и чем шил не помнит, в общем очень печально получается.
 

fobos

Энтузиаст

Danakkroid

Active member
наклейку с камеры выложил, пожалуйста подскажите что мне теперь делать и что именно туда загрузить, спасибо!
 

fobos

Энтузиаст
я вам дал дамп, загрузчик, update.img...пробуйте под разные варианты использования
 
Зверху