latest firmware for DS-2CD2XX1、DS-2CD2xx5、DS-2CD2xx6、DS-2CD2xx7

Ok can you help me to update firmware in this camera and to have still multilanguafe or english firmware ? Please explaine me points in my previus post....

And tell me is any chance to change in this camera value of region in serial number from CH to WR ?

And can you share me extracted firmware G0 IPC_G0_CN_STD_5.5.53_180716 ?
 
pepeEL said:
Ok can you help me to update firmware in this camera and to have still multilanguafe or english firmware ? Please explaine me points in my previus post....
Click to expand...
I have provided very many indications of how this could be approached.
It seems that you have ignored them, or not understood them.
It's actually a complex technical subject that requires research and understanding, best gained from taking the time to explore Linux technical resources on the internet.
pepeEL said:
And tell me is any chance to change in this camera value of region in serial number from CH to WR ?
Click to expand...
I just explained why this is not possible, in the previous post. The 'secure chip designed to be tamper-proof'.
 
Can you help me and share me firmware extracted G0 IPC_G0_CN_STD_5.5.53_180716??

And please confir me and more explaine me this:

1.It is ok understand
printenv

2. It is ok understand
Use the following commands to set the camera IP address and the TFTP server IP address:

setenv ipadrs <your_choice_for_the_camera>
setenv serverip <your_TFTP_server_address>
saveenv

3. It is ok understand
Then the kernel bootargs need to be changed to get the kernel to boot into a debug mode:

setenv bootargs console=ttyAMA0,115200 init=/bin/sh rootfs=0x82000000 rootfstype=initrd debug single loglevel=9
saveenv

4. It is ok understand- copy file uImage from extract new firmware to directory of root TFTP server ???????????
-------------------------------------------------------------
Copy the kernel image uImage to your tftp root folder.

Boot over tftp and the camera should end up at a shell prompt, hopefully not a psh prompt.

tftp uImage
bootm

-----------------------------------------------------------
5. It is ok understand-- addres like 192.168.1.201 is your NAS with NFS name CCTV1 ????????????????????
It's really handy to be able to copy / paste command lines from a text file (eg via Notepad) into the PuTTY command line.
These can be done singly or in multiple.
If the modified bootargs do boot into an ash shell, that's great as it will provide the access to do the needed work.
But at that point, the environment is not yet complete.
These commands are needed to take it a few steps further:
Adjust the IP addresses to match your network and your NAS for the NFS share and sharename.

/bin/mount -t proc proc /proc
/bin/mount -t sysfs none /sys
/bin/mount -t ramfs ramfs /home

/etc/S_udev

ifconfig eth0 192.168.1.64 up

mount -t nfs -o nolock 192.168.1.201:/cctv1 /mnt/nfs00

cd /mnt/nfs00

----------------------------------------------------------------
6. Can you explaine me more this point step by step ?
At this point there is a fully usable linux environment.
The uImage kernel can be applied to mtdblock5 & 6 (sys0, sys1) and all the remaining files from the unpacked firmware copied into /dav both when it's mounted from mtdblock7 and also mtdblock8 (app0 and app1).
Finally - reboot, interrupt the bootloader with Control-U and put the bootargs environment variable back the way it was to begin with so that the camera no longer boots into a shell in debug mode.
 
pepeEL said:
6. Can you explaine me more this point step by step ?
At this point there is a fully usable linux environment.
The uImage kernel can be applied to mtdblock5 & 6 (sys0, sys1) and all the remaining files from the unpacked firmware copied into /dav both when it's mounted from mtdblock7 and also mtdblock8 (app0 and app1).
Finally - reboot, interrupt the bootloader with Control-U and put the bootargs environment variable back the way it was to begin with so that the camera no longer boots into a shell in debug mode.
Click to expand...
It's not realistic to do this sort of work by rote, step by step, as giving the steps simply expands the areas where there is no understanding.
Doing it without the understanding that comes from studying the topic will create problems.
As I've said - there are loads of Linux blogs and tutorials around, a wealth of information to read and study.

However - for this very last item you have again asked to be explained, here is a sample transcript from one I did last year :
Code: 
#
# /bin/mount -t proc proc /proc
# /bin/mount -t sysfs none /sys
# /bin/mount -t ramfs ramfs /home
# /etc/S_udev
Starting udev:      [ OK ]
# ifconfig eth0 192.168.1.64 up
#
# mount -t nfs -o nolock 192.168.1.201:/cctv1 /mnt/nfs00

[   68.760320] PHY: mdio0:03 - Link is Up - 100/Full
[   68.765142] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
# cd /mnt/nfs00
#
# ls -al
drwxrwxrwx   10 root     root          4096 Oct 20 18:38 .
drwxrwxrwx   13 root     root             0 May  2  2013 ..
drwxrwxrwx    2 root     root          4096 Sep 30 15:42 .streams
drwxrwxrwx   16 root     100           4096 Oct 17 19:50 @Recycle
drwxr-xr-x    5 root     root          4096 Oct 19 22:34 contents_CN540
drwxrwxrwx    2 503      100           4096 Oct 20 18:38 contents_updated
drwxrwxrwx    2 root     root         12288 Feb 21  2018 datadir0
drwxrwxrwx    2 root     root         12288 Feb 21  2018 datadir1
drwxrwxrwx    2 root     root         12288 Feb 21  2018 datadir2
drwxr-xr-x    2 root     root          4096 Sep 30 15:53 extract
-rw-r--r--    1 root     root            68 Sep 30 15:52 info.bin
-rw-rw-rw-    1 503      100        4038800 Oct 17 19:18 uImage
# cd ../contents_u*
# ls -al
drwxrwxrwx    2 503      100           4096 Oct 20 18:38 .
drwxrwxrwx   10 root     root          4096 Oct 20 18:38 ..
-rw-rw-rw-    1 503      100        3612761 Oct  5  2017 IEfile.tar.gz
-rw-rw-rw-    1 503      100          98059 Oct 17 19:18 SoftwareLicense.txt
-rw-rw-rw-    1 503      100            660 Oct 17 19:18 _cfgUpgClass
-rw-rw-rw-    1 503      100        1623124 Oct 17 19:18 ant_army
-rw-rw-rw-    1 503      100        9021594 Oct 13  2017 g0_app.tar.gz
-rw-rw-rw-    1 503      100         736700 Oct 17 19:18 g0_modules.tgz
-rw-rw-rw-    1 503      100         232954 Oct 17 19:18 help.tar.gz
-rw-rw-rw-    1 503      100           7858 Oct  6  2017 initrun.sh
-rw-rw-rw-    1 503      100        1103398 Oct 17 19:18 mpp_modules.tgz
-rw-rw-rw-    1 503      100           2298 Oct 17 19:18 r7_app.tar.gz
#
# mount
rootfs on / type rootfs (rw)
proc on /proc type proc (rw,relatime)
none on /sys type sysfs (rw,relatime)
ramfs on /home type ramfs (rw,relatime)
udev on /dev type tmpfs (rw,relatime)
devpts on /dev/pts type devpts (rw,relatime,mode=600)
192.168.1.201:/cctv1 on /mnt/nfs00 type nfs (rw,relatime,vers=3,rsize=32768,wsize=32768,namlen=255,hard,nolock,proto=tcp,port=2049,timeo=70,retrans=3,sec=sys,local_lock=all,addr=192.168.1.201)
#
# mount -t yaffs2 /dev/mtdblock7 /dav
[  142.914217] yaffs: dev is 32505863 name is "mtdblock7" rw
[  142.919623] yaffs: passed flags ""
[  142.923078] yaffs: yaffs: Attempting MTD mount of 31.7,"mtdblock7"
[  142.929580] yaffs: checking block 0 bad
[  142.937743] yaffs: yaffs_read_super: is_checkpointed 1
# ls -al /dav
drwxr-xr-x    1 root     root          2048 Oct 20 18:42 .
drwxrwxrwx   18 root     root             0 Oct 20 18:41 ..
-rw-------    1 root     root           496 Jan  1  1970 _cfgUpgClass
-rw-------    1 root     root      11789733 Jan  1  1970 g0_app.tar.gz
-rw-------    1 root     root        585325 Jan  1  1970 g0_modules.tgz
-rw-------    1 root     root          6241 Jan  1  1970 initrun.sh
drwx------    1 root     root          2048 Oct 20 18:42 lost+found
-rw-------    1 root     root       1075897 Jan  1  1970 mpp_modules.tgz
# rm /dav/*
rm: /dav/lost+found: is a directory
# ls -al /dav/lost*
drwx------    1 root     root          2048 Oct 20 18:42 .
drwxr-xr-x    1 root     root          2048 Oct 20 18:43 ..
# cp * /dav
# ls -al /dav
drwxr-xr-x    1 root     root          2048 Oct 20 18:44 .
drwxrwxrwx   18 root     root             0 Oct 20 18:41 ..
-rw-r--r--    1 root     root       3612761 Oct 20 18:44 IEfile.tar.gz
-rw-r--r--    1 root     root         98059 Oct 20 18:44 SoftwareLicense.txt
-rw-r--r--    1 root     root           660 Oct 20 18:44 _cfgUpgClass
-rw-r--r--    1 root     root       1623124 Oct 20 18:44 ant_army
-rw-r--r--    1 root     root       9021594 Oct 20 18:44 g0_app.tar.gz
-rw-r--r--    1 root     root        736700 Oct 20 18:44 g0_modules.tgz
-rw-r--r--    1 root     root        232954 Oct 20 18:44 help.tar.gz
-rw-r--r--    1 root     root          7858 Oct 20 18:44 initrun.sh
drwx------    1 root     root          2048 Oct 20 18:42 lost+found
-rw-r--r--    1 root     root       1103398 Oct 20 18:44 mpp_modules.tgz
-rw-r--r--    1 root     root          2298 Oct 20 18:44 r7_app.tar.gz
# ls -al ../uImage
-rw-rw-rw-    1 503      100        4038800 Oct 17 19:18 ../uImage
# cat ../uImage > /dev/mtdblock5
# reboot
The system is going down NOW!
Sent SIGTERM to all processes
Terminated
Sent SIGKILL to all processes
Requesting system reboot
[  370.091791] Restarting system.
 
But can you share me extracted IPC_G0_CN_STD_5.5.53_180716 ?

And tell me in step 4 i must copy to tftp file uImage from new extracted firmware ?
 
alastairstevenson said:
Sorry, I don't have the coding for that version.
Click to expand...

But how i can extract it ?

And how you extract firmware when yo do your operation with platform G0 ?



And tell me how do it:
"Finally - reboot, interrupt the bootloader with Control-U and put the bootargs environment variable back the way it was to begin with so that the camera no longer boots into a shell in debug mode." ?
 
Hi
I download CN version firmware fo g0:
IPC_G0_CN_STD_5.5.53_180716

and also version EN:
IPC_G0_EN_STD_V5.5.2_Build170920

and also your @alastairstevenson for g0 which you send me on priv. I try extract this all three firmware by soft hikpack_2.5 but only your alastairstevenson i can extract.
Version CN and EN generate error like on screen.

But tell me what version you send me ? I dont know why i can not extract it...
 

Attachments

  • IMG_20190102_165705.jpg
    IMG_20190102_165705.jpg
    5.7 MB · Views: 14
Batch Configurator does indeed allow setting ssh access on.
But it seems that they have removed the normal bash shell and replaced it with custom commands that are NOT much help.
Is there a guide for the new shell commands in the 5.4.x firmware? $ help is not very informative.
 
You must log in or register to reply here.
Top Bottom