My IPC254EB-DX22GK-I0 is damaged?

Revo2Maxx

Revo2Maxx

IPCT+ Member
Jan 1, 2024
970
483
USA
So I moved my camera a few nights ago and after the move I logged in and made some camera adjustments with the Zoom lens. I setup a Preset and called it a night. Now to be honest it was close focused on a very close thing so i didn't use the camera the last few days and didn't even look. Well now not raining last night so I got on the NVR it was connected to and when I brought up the Live view the camera was tweaked out. So Tweaked out? Well I think the cameras chip is damaged or something because the camera knows what it is, but the camera is no longer bringing up the PTZ menu and when I go to the cameras WebUI there is no option and the camera is now showing that it is a 720P camera? WTF?

I have never had a camera do this.. Camera is showing as a 720P and will not let me make any changes over that option? I have access to WebUI, I reset the camera on the NVR first time. Still nothing. That was software reset, So I took it down, Big camera hard to reset mounted. So Took it down connected using POE+ Switch and after logging into the NVRs set IP I software reset again. and again only 720P.. So I took the 4 screws out of the back and did a Switch Reset and again 720P is only option? No lens movement and while the WebUI shows Focus info on image page where I can change from 22x to 3xx+x Optical and Digital but there is no action.. Did a log export and looking at data from it with data from one I did in Last year and earlier this year I don't see anything that says why it is doing this. I guess I am not looking in the right log file?

Anyone know how to take this camera apart? Repair I did only needed to take out the main PCB so didn't have to take out the lens part. The PCB sits at the back of the camera behind the camera/lens. That is held in place by some type of lip at the bottom of the camera that makes it so the camera will not slide all the way out but I don't see how to remove that plate that blocks and I don't see anything outside of the back of the camera to take camera apart? I need to get to the lens to see if I can maybe get it to a point where the camera lens will move. Might be hardware damaged because there was something in the last logs that says the lens was ok. So either that is because the chip is bad and not able to report a fail or camera is just not as smart as it pretends to be lol..

Oh yeah and camera no longer has Ai options in WebUI.. it is like a dumb 720 motion only camera now?
 

Attachments

  • Screenshot (443).png
    Screenshot (443).png
    384.2 KB · Views: 0
  • Screenshot (444).png
    Screenshot (444).png
    60.6 KB · Views: 0
So how to take apart lol.. Geez I would rather work on any of the PTZ cameras I have ever had to work on.. First the plastic part in the front comes off. Unlike my other cameras either with a top cap that needs to be removed to access a little clip or the ones that have a slot in the top of the lens cover this camera has no access point. Looking at the front there don't seem to be anyway to remove it from the camera so I personally thought at first it was Epoxy or glued on.. it isn't it is just well fitted.. Pressed with 2 clips on the top right and left. Pull down the hood little bit while you pull out and give it a Tug.. Then it will show 4 screws Using an H2.5 was able to remove them. Now that will give you access to the lens but you will need to take the back out, Remove 4 screws that hold the back to the power PCB plate.. Remove the wires that are on the PCB. Power, Ethernet and Alarm/Audio wires.. Then remove the plate. Once that is done the whole camera will pull out the front..

I almost started to cut the Rivets off the PCB plate. I had pulled the PCB once before so I took it off again. Was like dumb that it would be built this way lol.. I was like last option. Then I found that the front came off.. So much easier lol.. Other way would have worked as well. But while I was looking over the thing I was like That dumb front has to come off. There is mount there for another type of camera setup so this front has to come off. I mean I guess they could have used long screw driver to mount the other camera to front but it just didn't seem right they would setup without front coming off..

Right now only motor that is working is the Iris. That still don't explain why the camera is only working in 720P. Thought it might have been that the NVR kept connecting seeing the NVR changed IP to meet the local Lan IP and I didn't notice this until I started looking at different images settings in the camera I noticed the NVR Ip was still showing even though I didn't change the NVR for the Lan Ip it noticed the IP change and reconnected seeing I was using the same password I was using while connected to NVR Poe.. After another Reset again 720P so that wasn't why..

I am sure the camera would reject it but anyone have any Uniview API for zoom? I would like to manually see if I can get the lens out of being stuck. It might be that part of keeping the camera working in bad hardware that it down samples to 720P? no fun right now.. This camera is built like my Amcrest cameras have to take the whole thing apart from the cage. to get access to the Cameras PCB..
 
OMG This camera is going to tick me off lol.. Anyone ever have an issue where the camera works but has changed the output of the Main and Sub channels to something that it isn't?

So today I thought lets check maybe the lens is stuck. So I took the camera apart. removed the motor from the lens and when I connected the camera back to power after putting it all back together because this camera gets really hot I didn't to run it without the cage and chip cooling pads in place.. Anyway as soon as I added power back the Lens went back down into the case where it was stuck at and didn't come back.. so I know the motors are working. The chip works to make the motors move. Hall effect must work and that is why the lens went back to where it was broken at?

Anyone ever see what a Zoom lens motor connection looks like in the lens? I don't know if you have ever looked in side of one or not but they are Direct Screw drive. There is a long tight threaded rod that snaps into a plastic clip that rides up and down the rod for zoom and focus.. This camera has a removable battery lol.. OMG like you have to take the whole camera apart why the heck would they put in a replaceable battery lol? I have ordered a new one seeing this one is only running 2.2v and it is a 3v battery so should be replaced.. Factory reset via software and button isn't changing the cameras lens info. This isn't normal.. Factory reset should set all values back to default and means the lens should be in a normal state not being returned to a broke area?

Well looked in the logs and you can see between the 2 one on the left is from yesterday and the one on the right is from December GRRRRR.. In the logs shows the camera is damaged.. Now have a costly paper weight.. Wonder if it is because I had it connected to my Alibi NVR? I mean should not have mattered I would have guessed but normally have it connected to a POE+ Switch and the NVR however since April I have had it connected to my NVRs POE switch and not the LANs..
 

Attachments

  • Screenshot (445).png
    Screenshot (445).png
    288.8 KB · Views: 0
No option or I forgot how lol.. I mean I thought I knew how. But after I log in and press the keys nothing happens? So either I forgot how or it isn't working?
 
ok I was able to access it this time but still seems messed up? Not sure how to get Uniview to send me a FW to add back in and see if that works.. Looking in the logs on the export things keep saying the FW needs to be reloaded..
 
Still sees it as the right camera? I just don't understand why it is not working or how the thing over heated and killed the current running FW with all the export info it can do crazy that it don't have a good FW that someone could use to fix when they have an issue like this?
 

Attachments

  • Screenshot (448).png
    Screenshot (448).png
    83.7 KB · Views: 0
  • Screenshot (449).png
    Screenshot (449).png
    82.6 KB · Views: 0
Thank you, That list doesn't have a FW for my camera.. I will try Email and see if I get the same answer I got the last time I asked them for some help lol.. I hope they will provide a FW to reset the camera..

Strange that Button Reset and software reset does nothing lol. I mean it resets the cameras password and that is it. I have reset the camera a few times and I always thought that the camera on Reset was loading a fresh image off a ROM or some other type FW storage chip..
 
The failure is very strange, these cameras do not have a backup firmware, so if you corrupt the flash, the camera normally just wont boot, and you'd have to use the serial interface to try to restore it (I think it would tftp firmware from the local network once you have the IP configured).
 
Undstand, that is why it is odd that this camera is like this.. I have access to the Cameras WebUI, I have access to everything as if the camera was working besides what makes the camera what it is.. Being stuck in 720P and no Ai and no access to zoom controls from WebUI or from my Alibi NVR is very odd that the camera is in this mode. Almost like the old Limp Mode of cars some years ago.. It is like it is in limp mode.. Before, last day that I looked at the camera it was out of focus from what I had it pointed to so I hit the focus and then a few days later after the rain was over I thought Ok lets make some adjustments to the cameras installed area to make sure it would view what I wanted and noticed it was all messed up.. For a couple of days it just sat there connected to the POE port of the NVR and was only difference from how I normally have it connected.. POE+ Switch wasn't in area of the camera but my NVR was so thought I would just use that for power.. Other cameras connected to NVR from Dahua and Hikvision are all working as they did before only one with odd issue is the Uniview.. Not only is the camera in this odd state the lens is in an odd state that makes it so there is no focus. I mean if I take it and point it at lights on my switch you can see the shape of the Iris and the color of the lights but no ability to focus it.. That was main reason I took the camera apart so I could get access to the zoom lens and thought if I could get it out of the funk it was in that it might correct it self but as soon as I gave power to the camera again it just moved the cameras lens back to the area it was before I took it apart lol. So think the out of focus right now is because the camera is set at 720P and large sensor with the Iris just makes it.. Heck I don't know.. If no FW or if the fW don't correct it I will have a costly paper weight..
 
In the restricted shell, you might want to see if IR cut on/off helps. I doubt it tho, but probably wouldn't hurt to try.

Screenshot from 2025-05-30 21-55-20.png

Does your camera require POE+ or POE++? My camera requires POE++, and it works fine as long as the IRs are off, or if the PTZ controls are not being used. With 23W of power, it always crashes when I try to do more than a few things. So I've just been using the 24V power brick that it comes with and it works very well.

Also if POE++, you need to make sure you are using 23AWG ethernet cable that is using pure copper cables, not CCA (copper clad aluminum). The voltage drop with ACC causes the camera to reset even if your POE++ supply is good. Ask me how I know. :)
 
Understand, i am CCA free. All against the idea of people being taken advantage of saying cable is TIA/ANSI with CCA when it couldn't be certified and all the havoc it can take on cameras. So many people out there just don't know. Like most of the ones that have there devices exposed to internet loads of them have no clue and feel bad for them.

Anyway, not sure about the info you have there in the picture. I will look into it.

About POE? It's only +, i do have BT injector that for kicks i tested to see if i was having a power issue, same result.

Thank you for your help
 
Well that didn't work, lol. I asked Uniview for FW for my camera, they were nice enough to send me one dated 2025, mine was from 2023, but thought they knew what they were doing.

Now camera is dead. Powers on, shows network data but now iris is closed and never opens or anything happens when you give it power. Now only thing it does it turn on heater and keeps it running so camera module gets very hot. Taking heater off power board, keeps heat down but camera never comes alive and no finding it in search with EzTools or it's static ip that I setup before update. I set in my router.

Now will have to try different repair method.. Thought it might work. Oh well. 3k paper weight.
 
Well darn.. Not sure how to recover it now lol.. Data below is from Putty, It cycles every 3 to 5 minutes.. I can not stop it from doing the full cycle and nothing happen from key presses.

Code: 
[WDT] Enalbe WAT                                                                                                                                                             CHDOG 0x0000012c s

IPL 21e8c1c
D-b7
HW Reset
MCP32_1866_4X 6L
== miu settings for 6 layer board ==
miupll_400MHz
1024MB
BIST0_0001-OK
Load IPL_CUST from SPINAND

 BlSize 000064f0
Checksum OK
JMP+++
IPL_CUST 21e8c1c
_IPLCustSNandOp
 ECCSTATUS ERR_SPINAND_ECC_1_3_CORRECTED
 ECCSTATUS ERR_SPINAND_ECC_1_3_CORRECTED
 ECCSTATUS ERR_SPINAND_ECC_1_3_CORRECTED
 ECCSTATUS ERR_SPINAND_ECC_1_3_CORRECTED
 ECCSTATUS ERR_SPINAND_ECC_1_3_CORRECTED
 ECCSTATUS ERR_SPINAND_ECC_1_3_CORRECTED
 ECCSTATUS ERR_SPINAND_ECC_1_3_CORRECTED
Load BL from SPINAND
  decomp_size=0x00076c0c


U-Boot 2015.01-svn375556 (Dec 07 2021 - 17:42:10), Build: jenkins-CMO-Compile_64                                                                                                                                                             兼32位_tags(10.222.192.18)-452

Version: I6E#g#######
I2C:   ready
DRAM:
WARNING: Caches not enabled
###SD GPIO INIT###
###SENSOR RESET INIT###
SPINAND_I:  SPINAND: _MDrv_SPINAND_GET_INFO: Found SPINAND INFO
(0x98) (0xCB)
SPINAND: board_nand_init: CIS contains part info
256 MiB
MMC:   MStar SD/MMC: 0
=====DDR SIZE: 0xa0
=====DDR SIZE: 1G tmp_tst :0xa0
*** Warning - bad CRC, using default environment

In:    serial
Out:   serial
Err:   serial
Detected MACID:6c:f1:7e:92:1b:d7
Net:   [HAL_HWI2C_XferWrite(2473)] Bus[0] Write ERROR: Slave dev NAK, Addr: 0xb8                                                                                                                                                             , Data: 0x49 0x2
[HAL_HWI2C_XferRead(2325)] Read ERROR: Slave dev NAK, Addr: 0xb9, Data: 0x0 0x0                                                                                                                                                             
[HAL_HWI2C_XferRead(2325)] Read ERROR: Slave dev NAK, Addr: 0xb9, Data: 0x0 0x0                                                                                                                                                             
[HAL_HWI2C_XferWrite(2473)] Bus[0] Write ERROR: Slave dev NAK, Addr: 0xb8, Data:                                                                                                                                                              0x0 0x0
MAC Address 6C:F1:7E:92:1B:D7
Auto-Negotiation...
Link Status Speed:100 Full-duplex:1
sstar_emac
Press Ctrl+B to abort autoboot in 2 seconds

NAND read: device 0 offset 0x400000, size 0x500000
Time:966706 us, speed:5423 KB/s
 5242880 bytes read: OK
Wrong Image Format for bootm command
ERROR: can't get kernel image!
uboot # [WDT] Enalbe WATCHDOG 0x0000012c s

IPL 21e8c1c
D-b7
HW Reset
MCP32_1866_4X 6L
== miu settings for 6 layer board ==
miupll_400MHz
1024MB
BIST0_0001-OK
Load IPL_CUST from SPINAND

 BlSize 000064f0
Checksum OK
JMP+++
IPL_CUST 21e8c1c
_IPLCustSNandOp
 ECCSTATUS ERR_SPINAND_ECC_1_3_CORRECTED
 ECCSTATUS ERR_SPINAND_ECC_1_3_CORRECTED
 ECCSTATUS ERR_SPINAND_ECC_1_3_CORRECTED
 ECCSTATUS ERR_SPINAND_ECC_1_3_CORRECTED
 ECCSTATUS ERR_SPINAND_ECC_1_3_CORRECTED
 ECCSTATUS ERR_SPINAND_ECC_1_3_CORRECTED
 ECCSTATUS ERR_SPINAND_ECC_1_3_CORRECTED
Load BL from SPINAND
  decomp_size=0x00076c0c


U-Boot 2015.01-svn375556 (Dec 07 2021 - 17:42:10), Build: jenkins-CMO-Compile_64                                                                                                                                                             兼32位_tags(10.222.192.18)-452

Version: I6E#g#######
I2C:   ready
DRAM:
WARNING: Caches not enabled
###SD GPIO INIT###
###SENSOR RESET INIT###
SPINAND_I:  SPINAND: _MDrv_SPINAND_GET_INFO: Found SPINAND INFO
(0x98) (0xCB)
SPINAND: board_nand_init: CIS contains part info
256 MiB
MMC:   MStar SD/MMC: 0
=====DDR SIZE: 0xa0
=====DDR SIZE: 1G tmp_tst :0xa0
*** Warning - bad CRC, using default environment

In:    serial
Out:   serial
Err:   serial
Detected MACID:6c:f1:7e:92:1b:d7
Net:   [HAL_HWI2C_XferWrite(2473)] Bus[0] Write ERROR: Slave dev NAK, Addr: 0xb8                                                                                                                                                             , Data: 0x49 0x2
[HAL_HWI2C_XferRead(2325)] Read ERROR: Slave dev NAK, Addr: 0xb9, Data: 0x0 0x0                                                                                                                                                             
[HAL_HWI2C_XferRead(2325)] Read ERROR: Slave dev NAK, Addr: 0xb9, Data: 0x0 0x0                                                                                                                                                             
[HAL_HWI2C_XferWrite(2473)] Bus[0] Write ERROR: Slave dev NAK, Addr: 0xb8, Data:                                                                                                                                                              0x0 0x0
MAC Address 6C:F1:7E:92:1B:D7
Auto-Negotiation...
Link Status Speed:100 Full-duplex:1
sstar_emac
Press Ctrl+B to abort autoboot in 2 seconds

NAND read: device 0 offset 0x400000, size 0x500000
Time:966705 us, speed:5423 KB/s
 5242880 bytes read: OK
Wrong Image Format for bootm command
ERROR: can't get kernel image!
uboot # [WDT] Enalbe WATCHDOG 0x0000012c s

IPL 21e8c1c
D-b7
HW Reset
MCP32_1866_4X 6L
== miu settings for 6 layer board ==
miupll_400MHz
1024MB
BIST0_0001-OK
Load IPL_CUST from SPINAND

 BlSize 000064f0
Checksum OK
JMP+++
IPL_CUST 21e8c1c
_IPLCustSNandOp
 ECCSTATUS ERR_SPINAND_ECC_1_3_CORRECTED
 ECCSTATUS ERR_SPINAND_ECC_1_3_CORRECTED
 ECCSTATUS ERR_SPINAND_ECC_1_3_CORRECTED
 ECCSTATUS ERR_SPINAND_ECC_1_3_CORRECTED
 ECCSTATUS ERR_SPINAND_ECC_1_3_CORRECTED
 ECCSTATUS ERR_SPINAND_ECC_1_3_CORRECTED
 ECCSTATUS ERR_SPINAND_ECC_1_3_CORRECTED
Load BL from SPINAND
  decomp_size=0x00076c0c


U-Boot 2015.01-svn375556 (Dec 07 2021 - 17:42:10), Build: jenkins-CMO-Compile_64兼32位_tags(10.222.192.18)-452

Version: I6E#g#######
I2C:   ready
DRAM:
WARNING: Caches not enabled
###SD GPIO INIT###
###SENSOR RESET INIT###
SPINAND_I:  SPINAND: _MDrv_SPINAND_GET_INFO: Found SPINAND INFO
(0x98) (0xCB)
SPINAND: board_nand_init: CIS contains part info
256 MiB
MMC:   MStar SD/MMC: 0
=====DDR SIZE: 0xa0
=====DDR SIZE: 1G tmp_tst :0xa0
*** Warning - bad CRC, using default environment

In:    serial
Out:   serial
Err:   serial
Detected MACID:6c:f1:7e:92:1b:d7
Net:   [HAL_HWI2C_XferWrite(2473)] Bus[0] Write ERROR: Slave dev NAK, Addr: 0xb8, Data: 0x49 0x2
[HAL_HWI2C_XferRead(2325)] Read ERROR: Slave dev NAK, Addr: 0xb9, Data: 0x0 0x0
[HAL_HWI2C_XferRead(2325)] Read ERROR: Slave dev NAK, Addr: 0xb9, Data: 0x0 0x0
[HAL_HWI2C_XferWrite(2473)] Bus[0] Write ERROR: Slave dev NAK, Addr: 0xb8, Data: 0x0 0x0
MAC Address 6C:F1:7E:92:1B:D7
Auto-Negotiation...
Link Status Speed:100 Full-duplex:1
sstar_emac
Press Ctrl+B to abort autoboot in 2 seconds

NAND read: device 0 offset 0x400000, size 0x500000
Time:966687 us, speed:5423 KB/s
 5242880 bytes read: OK
Wrong Image Format for bootm command
ERROR: can't get kernel image!
uboot # [WDT] Enalbe WATCHDOG 0x0000012c s

IPL 21e8c1c
D-b7
HW Reset
MCP32_1866_4X 6L
== miu settings for 6 layer board ==
miupll_400MHz
1024MB
BIST0_0001-OK
Load IPL_CUST from SPINAND

 BlSize 000064f0
Checksum OK
JMP+++
IPL_CUST 21e8c1c
_IPLCustSNandOp
 ECCSTATUS ERR_SPINAND_ECC_1_3_CORRECTED
 ECCSTATUS ERR_SPINAND_ECC_1_3_CORRECTED
 ECCSTATUS ERR_SPINAND_ECC_1_3_CORRECTED
 ECCSTATUS ERR_SPINAND_ECC_1_3_CORRECTED
 ECCSTATUS ERR_SPINAND_ECC_1_3_CORRECTED
 ECCSTATUS ERR_SPINAND_ECC_1_3_CORRECTED
 ECCSTATUS ERR_SPINAND_ECC_1_3_CORRECTED
Load BL from SPINAND
  decomp_size=0x00076c0c


U-Boot 2015.01-svn375556 (Dec 07 2021 - 17:42:10), Build: jenkins-CMO-Compile_64兼32位_tags(10.222.192.18)-452

Version: I6E#g#######
I2C:   ready
DRAM:
WARNING: Caches not enabled
###SD GPIO INIT###
###SENSOR RESET INIT###
SPINAND_I:  SPINAND: _MDrv_SPINAND_GET_INFO: Found SPINAND INFO
(0x98) (0xCB)
SPINAND: board_nand_init: CIS contains part info
256 MiB
MMC:   MStar SD/MMC: 0
=====DDR SIZE: 0xa0
=====DDR SIZE: 1G tmp_tst :0xa0
*** Warning - bad CRC, using default environment

In:    serial
Out:   serial
Err:   serial
Detected MACID:6c:f1:7e:92:1b:d7
Net:   [HAL_HWI2C_XferWrite(2473)] Bus[0] Write ERROR: Slave dev NAK, Addr: 0xb8, Data: 0x49 0x2
[HAL_HWI2C_XferRead(2325)] Read ERROR: Slave dev NAK, Addr: 0xb9, Data: 0x0 0x0
[HAL_HWI2C_XferRead(2325)] Read ERROR: Slave dev NAK, Addr: 0xb9, Data: 0x0 0x0
[HAL_HWI2C_XferWrite(2473)] Bus[0] Write ERROR: Slave dev NAK, Addr: 0xb8, Data: 0x0 0x0
MAC Address 6C:F1:7E:92:1B:D7
Auto-Negotiation...
Link Status Speed:100 Full-duplex:1
sstar_emac
Press Ctrl+B to abort autoboot in 2 seconds

NAND read: device 0 offset 0x400000, size 0x500000
Time:966696 us, speed:5423 KB/s
 5242880 bytes read: OK
Wrong Image Format for bootm command
ERROR: can't get kernel image!
uboot # [WDT] Enalbe WATCHDOG 0x0000012c s

IPL 21e8c1c
D-b7
HW Reset
MCP32_1866_4X 6L
== miu settings for 6 layer board ==
miupll_400MHz
1024MB
BIST0_0001-OK
Load IPL_CUST from SPINAND

 BlSize 000064f0
Checksum OK
JMP+++
IPL_CUST 21e8c1c
_IPLCustSNandOp
 ECCSTATUS ERR_SPINAND_ECC_1_3_CORRECTED
 ECCSTATUS ERR_SPINAND_ECC_1_3_CORRECTED
 ECCSTATUS ERR_SPINAND_ECC_1_3_CORRECTED
 ECCSTATUS ERR_SPINAND_ECC_1_3_CORRECTED
 ECCSTATUS ERR_SPINAND_ECC_1_3_CORRECTED
 ECCSTATUS ERR_SPINAND_ECC_1_3_CORRECTED
 ECCSTATUS ERR_SPINAND_ECC_1_3_CORRECTED
Load BL from SPINAND
  decomp_size=0x00076c0c


U-Boot 2015.01-svn375556 (Dec 07 2021 - 17:42:10), Build: jenkins-CMO-Compile_64兼32位_tags(10.222.192.18)-452

Version: I6E#g#######
I2C:   ready
DRAM:
WARNING: Caches not enabled
###SD GPIO INIT###
###SENSOR RESET INIT###
SPINAND_I:  SPINAND: _MDrv_SPINAND_GET_INFO: Found SPINAND INFO
(0x98) (0xCB)
SPINAND: board_nand_init: CIS contains part info
256 MiB
MMC:   MStar SD/MMC: 0
=====DDR SIZE: 0xa0
=====DDR SIZE: 1G tmp_tst :0xa0
*** Warning - bad CRC, using default environment

In:    serial
Out:   serial
Err:   serial
Detected MACID:6c:f1:7e:92:1b:d7
Net:   [HAL_HWI2C_XferWrite(2473)] Bus[0] Write ERROR: Slave dev NAK, Addr: 0xb8, Data: 0x49 0x2
[HAL_HWI2C_XferRead(2325)] Read ERROR: Slave dev NAK, Addr: 0xb9, Data: 0x0 0x0
[HAL_HWI2C_XferRead(2325)] Read ERROR: Slave dev NAK, Addr: 0xb9, Data: 0x0 0x0
[HAL_HWI2C_XferWrite(2473)] Bus[0] Write ERROR: Slave dev NAK, Addr: 0xb8, Data: 0x0 0x0
MAC Address 6C:F1:7E:92:1B:D7
Auto-Negotiation...
Link Status Speed:100 Full-duplex:1
sstar_emac
Press Ctrl+B to abort autoboot in 2 seconds

NAND read: device 0 offset 0x400000, size 0x500000
Time:966706 us, speed:5423 KB/s
 5242880 bytes read: OK
Wrong Image Format for bootm command
ERROR: can't get kernel image!
uboot #
 
Well this is fun.. I have not repaired any Uniview cameras with bad Uboot and methods that work on other cameras just caused me to hard brick this camera.. I no longer even have a uboot shell anymore lol.. Well this is really fun. So right in the middle of downing a image update that I thought would take care of the cameras issues over TFTP I get a call. Not paying attention to the data on the screen I went form uploading the image to the camera it failed. Because of the Watchdog. I didn't notice that and moved on to the next step. I cleared the old Firmware from the chip and when I went to add back in the new image it wasn't there.. So at this point it was soft Bricked Well hard soft bricked LOL anyway oddly at that same time my connection failed and no longer had the ability to move any images. Come to find out after trying to xmodem the Uboot back onto the device I found that the camera don't like the U-Boot.bin because it is Encrypted lol.. Geez they don't make it easy to fix these things..

What is the likely hood that Uniview would send me a clean program.bin and u-boot.bin file so I can fix this camera if it is infact fixable.. Should have taken pictures of the camera when I had it apart so I knew what Mstar chip was on the machine so I could maybe locate my own U-boot and at least get the Shell back..
 
You must log in or register to reply here.
Top Bottom