Recent content by fritzycat1

Glad you found the post useful. I agree - stupid place for that button. Good luck with the camera reset!

Also, this is the first time I received an email notification that someone replied to my original post?!. My (belated) thanks to everyone who took the time to reply back in February.

No Problem. Good luck getting it working again!

Yes. I found the reset button - thanks for the reminder to update this post. Reset button is found on top of the camera module. To access: Remove 4 black plugs over the screws holding the dome on. Remove 4 screws holding the dome on. Remove one screw on camera shroud (just below the lens)...

I originally posted this on the CCTVForum site, but didn't see much interest in the post there. Thought I would try here too: Does anybody know where I can find the reset button on the Hikvision DS-2DE4A425IW-DE PTZ Camera? I removed the dome and found the Micro-SD slot, and the serial (debug)...

Yup. I see the exact same problem and it isn't something I saw in previous versions of IVMS-4200. I don't have a solution for it either. I'll update this post if I figure it out. For reference, I'm using Version: V3.1.0.4 build 20190513

Should a Hikvision NVR automatically re-connect to NAS storage if that storage is temporarily unavailable? I recently configured my Hikvision DS-7616NI-I2 NVR to use NAS Storage in addition to the two local hard drives. It took a fair amount of hair pulling, consternation and a few choice...

I'll check out that tool. Thanks.

I'm all out of ideas too. I'll probably put this aside for a while unless some new ideas come up. Thanks again for all the help - it's been a good educational exercise for me. I did have a question though - how did you extract the uImage file from the firmware file?

Thanks for the additional suggestions. I tried that and got the same result: HKVS # tftp 0x80007fc0 uImage link up on port 0, speed 100, full duplex Using cpsw device TFTP from server 192.0.0.128; our IP address is 192.0.0.64 Filename 'uImage'. Load address: 0x80007fc0 Loading...

Thanks for your continued support @alastairstevenson and welcome to the party @rearanger ! I ran a test by changing one byte and confirmed the cmp command detected the difference: Step1: Set the memory to all 0xff values, and run the comparison: HKVS # mw.b 0x81000000 0xff 0x2e0000 HKVS #...

Instead of using the 'md' command to display the contents of memory, I tried using the 'cmp' command to compare the first half of that memory block to the second half. Also, I read that the U-Boot memory commands accept modifiers to define the size of the memory object, so I executed all...

I ran the mw and md commands as specified. I enabled logging on putty in hopes of catching all of the output to the putty log. The mw command executed in less than a second. It appears to have worked, as the md command floods the screen with the memory contents (000000ff). After about 10...

Thanks I'll try out the mw command and see what I come up with... FYI, here is the help output for mw: ..and the md command:

Thanks again. I encountered the same 'unexpected EOF' error when using the uImage you provided. Here is the output from the commands you suggested: HKVS # printenv bootargs=console=ttyS0,115200n8 mem=128M bootcmd=loadk;bootm 0x80007fc0 bootdelay=2 baudrate=115200 netmask=255.255.255.0...