IP Dome DF8223I-AEL cannot boot after upgrade

[JFK]

Maybe the connector next to the SD card is a candidate - is it 4 pins, 1.5mm pitch? What is it labelled as?

^^ah indeed, it is a 4pins 1.5mm. ^^then I need an adaptor because my 4 pins are too big to fit. ... ok I ll try to find that and test it again.

 

[alastairstevenson]

I need an adaptor because my 4 pins are too big to fit.

If it's the usual Hikvision variety, then you need a 4-pin 1.5mm JST ZH wired connector. Usually sold in 10-packs.

 

[JFK]

If it's the usual Hikvision variety, then you need a 4-pin 1.5mm JST ZH wired connector. Usually sold in 10-packs.

ok I've ordered it. I hope to finally get out of it

 

[Pierrre]

Don't know if this is any help and it will be a bit vague as it was a month or so ago.

I had one of the smart-tracking domes that would reset itself randomly and it sometimes took all the other cameras offline as well. Decided to update the firmware while I was talking to the customer & drinking tea - it wouldnt reboot afterwards. I checked the 24v psu and it was putting out 18ish volts so I swapped it out and the dome came back.

I knew the dome would work until the IR came on as when I installed it I got a picture just on the NVR's POE , but after updating the firmware it wouldnt work at all without the 24v supply.

TLDR : have you tried powering it separately?

 

[JFK]

Hello @alastairstevenson,
Here is what I have in loop:


U-Boot code: 80700000 -> 8070F>?T
>Net: Detgcte>x>eH 0
Trying eth0
+kon port 0, speed 100, full duplex
9U1ethaddr| not found tftpserver
booting from sec partition...
/nand/uImage to 0x80007fc0... B+ʪu5
## Booting kernel from Legacy Image at 80007fc0 ...
Image Name: Linux-2.6.37_DM81??OK
Loading Kernel Imagge done, booting the kernel.
CZ+started: BusyBox v1.19.3 (2017-11-15 19:39:07 CST)
starting pid 53, tty '': '/etc/iny>d?St [ OK ]
[0 is non-existentmount ... OK
diagnose_way = 10, repair_way = 1, interval = 60
cp: can't stat '/devinfo/gammx<: 81888?infd read End
Unix bus 0 .
Caɽ́Infomation:
version: 5.10.2 [20:30:28-Jul 18 2017]
Path: /Camera/Platform/Trunk/F>[10-03 18:04:44][pid:318][IPUO׵Gǿ[10-03 18:04:45][pid:318][IPC_UNIX]{G?App Start ...
{1?[10-03 18:04:49}{p?da[lib][38231]pDspInitPara->tim>davinci receive cmd_query_davinci_param.
S: cmd_query_davinci_aram Dec 1 2017 10:23:53 ==>davinci receive cmd_query_>Dec 1 2017 10:23:53 =?.d~[10-03 18:05:00][pid:343][HW_I~]IOOOOO*ᕍok.
=====>start wait over.
check if need upgrade motor mcu.
[10-03 18:05:01][pid:343][UNI_IF][ERROR]
########motor app only one,no need <[10->aappweb: 1: S~>0.a:8010a20,b:80020

any tips ?
Rgds;

 

[alastairstevenson]

Your serial console transcript is somewhat corrupt.
Is it possible the Windows VM cannot keep up with the virtual COM port speed?

But there is no reboot showing or bootloop.
If you are using PuTTY, it has a large scrollback capability, allowing the transcript to be conveniently pasted in to a text editor for review / extracts etc.
Also - for posting large amounts of text on the forum - the code tags, under the '+' in the edit bar, are convenient for all.

 

[JFK]

[10-03 19:21:22][pid:343][UNI_IF][ERROR]
�b�8002000���[10-�a���appweb: 1: Starting host named: "::"

U-Boot 2010.06-143514 (Aug 27 2015 - 15:08:47)

U-Boot code: 80700000 />?0�>¿ ����>
����?Net:   Detected }A�������>�����H 0
Trying eth0
+�k��on port 0, speed 100, full duplex
9U1�ethaddr| not found tftpserver
booting from sec partition...
��/nand/uImage to 0x80007fc0... B+�ʪu5
                                      ## Booting kernel from Legacy Image at 80007fc0 ...
   Image Name:   Linux-�>6>��?�OK
   Loading Kernel I��V��> ?�get mi� �������� done, booting the kernel.
CZ+��started: BusyBox v1.19.3 (2017-11-15 19:39:07 CST)
starting pid 53, tty '': '/etc/��������St��|����[ OK ���[������0 is non-existentmount ... OK
diagnose_way = 10, repair_way = 1, interval = 60
cp: can't stat '?d�~�������8188���8�>a���������infd read End
Unix bus   0 .
Ca���ɽ���́Infomation:
version: 5.10.2 [20:30:28-Jul 18 2017]
Path: /Camera/Platform/Trunk/FSP_n���o��������[10-03 19:22:24][pid:318][IPC_UNIX][E��O��������[10-03 19:22:25][pid:318][IPC_UNIXW�'=�������App Start ...
star��������[10-����[10-03 19:22>29][p��:3����H��d����[1���ښ����� ���?0��[lib][38288]pDspI~t����>��>���davinci receive cmd_query_davinci_param.
S: cm�\��v������Dec  1 2017 10:23:53 ==>start_dsp(699): start COR��V<
                                                                     ������davinci receivg cmd���������Dec  1 2017 10:23:53 ==>start_dsp(704): start CORE_VP� xxx���������[10-03 19:22:40][pid:343][HW_IF][ERROR]Set HAL_SET_PHY��w��� �OOOOO*ᕍ�ok.
=====>start wait over.
check if need  upgrade motor mcu.
[10-03 19:22:41][pid:343][UNI_IF][ERROR]
########motor app onl���� ��[?0��ap�������      ��

U-Boot 2010.06-143514 (Aug 27 2015 - 15:08:47)

��� Net:   Dete�|� ������H� 0 ���Th�>�>�
Trying eth0
+�k��on port 0, speed 100, full duplex
9U1�ethaddr| not found tftpserver
booting from sec partition...
��/nand/uImage to 0x80007fc0... B+�ʪu5
                                      ## Booting kernel from Legacy Image at 80007fc0 ...
   Image Name:   Linux-2.6.37_DM8127_IPNC�3.����������OK
   Loading Kernel Image ..> O�H��get�m����>� done, booting the kernel.
CZ+��started: BusyBox v1.19.3 (2017-11-15 19:39:07 CST)
starting pid 53, tty '': '/etc/init.d?��Sta�t������ [ OK ]
[������0 is non-existentmount ... OK
diagnose_way = 10, repair_way = 1, interval = 60
cp: can't st�t�����������818��8�������=�infd read End
Unix bus   0 .

 

[JFK]

@alastairstevenson this is what I have ... i am hearing the camera booting and it is stuck like that. The bootloop last few seconds
after the message

[10-03 19:22:41][pid:343][UNI_IF][ERROR]
########motor app onl���� ��[?0��ap������� ��

camera switchs off alone

 

[alastairstevenson]

this is what I have

OK, that's better, the bootloop now shows.

But you might be missing large chunks of the serial console output.
It is seriously corrupted.
Do you have any other computer you could run the serial terminal on?

 

[JFK]

Hi alastairstevenson,
Same status here for me. How could I get out of this ? flashing the Rom ?
any tips ?
Rgds,

 

[alastairstevenson]

How could I get out of this ?

It's not clear - the serial console log is badly corrupt, it's not possible to interpret it.