DS-2cd2t52-i5 bricked, but can't find a working solution...

[kispista]

for the erase command, according to the help, there where 2 options for configuration partition..

I erased both..

HKVS # erase cfg_pri
erase cfg_pri ... done
HKVS # erase cfg_sec
erase cfg_sec ... done

after booting, the same..

but, there is a diag command from the main sw.. it gives a lot of information, but i can't find any problem.. but i'm a beginner in hikvision theme

 

[kispista]

I made an experiment. I used the phyton update tool, not the hikvision tftp tool to upgrade the fw,but i made a log file from serial too..

interesting for me is:

Default method to init without VIN drivers...
Cat this file to find out what VIN can be supported.
Default init without lens driver
Use default settings
/home/script/init.sh: line 553: which: not found



cp: can't stat '/dav/libutils.so': No such file or directory

-------Goint to init_database-1665749030
davinci enter init_database
shared memory address is: 0x76817000, sizeof(DEVICECONFIG) = 1159944
davinci init_shared_memory success.
[setMultiCfgFactoryDefault]:SW_MULTI_CCDPARAM_SUP not sup
powerLineFrequencyMode = 0
[10-14 12:03:50][pid:591][UNI_IF][ERROR]stream request out range 3(2)
[10-14 12:03:50][pid:591][OTHER][ERROR]set_default_stream_qos_param npq not supported yet.
After set_devcfg_default, database need to init
S: cmd_get_capa_data ,ack 1 --sizeof(ret)= 4

[10-14 12:03:50][pid:576][DATABASE][ERROR]communicaite_to_davinci 65574 : service_result 1
going to init database:1
[10-14 12:03:50][pid:576][DATABASE][ERROR]db /davinci/ipc_db does not exist--errno = 2
Davinci wait for init dababase
[10-14 12:03:50][pid:576][DATABASE][ERROR]db /config/ipc_db_backup does not exist--errno = 2
sqlite3_get_table:1, no such table: db_version
[10-14 12:03:50][pid:576][DATABASE][ERROR]db version = -1
sqlite3_get_table:1, no such table: sec_lock_auth_db_info
[10-14 12:03:50][pid:576][DATABASE][ERROR]db_query_open_v2 error: 1

config is missing, great, i deleted them but the database is missing too.. what kind of database, and how to solve this? why is it missing, and why was it not created automatically??

the full log is attached..

 

[watchful_ip]

I've noticed that in both of the logs you posted that had a ps process listing command, that

  615 admin     2244 S    sh -c modprobe ov5658_mipi
  616 admin     2244 D    modprobe ov5658_mipi

is always shown.

If you boot the camera, leave for 5 minutes, and run the ps command again - is that modprobe still running?

If so, I think that is the problem.

 

[kispista]

YOU ARE A GENEIUS!!!! Solved. camera works!!!!

i googled for the modprobe ov5658_mipi.. nothing.. but for the ov5658, there where some resoults.. It is the camera module used in this device.. hmm..

OV5658 - OmniVision Technologies | CMOS Image Sensor

www.gophotonics.com

i disconnected the flat cable, and under the microscope, i found 10-15 cold soldering points.. resoldered them, now, it works great

i got this unit from a friend, who upgraded the firmware.. now.. it's clear, why.. becouse of picture problems...

Thank You guys!

i learned so much in the last days!

great forum, great members!!!

 

[watchful_ip]

That is great news - well done on your perseverance.

Well done on your micro soldering skills.

 

[alastairstevenson]

Well, scratch that theory about the configuration maybe being a cause of the bootloop..
Both pri and sec were erased and rebuilt with default values.

I still can't see why the bootloop is happening.
Somehow, though, I feel that this
=====prtHardInfo=====
connect failre errno=2
must be significant.

Davinci has an extensive initiallisation process - in the logs you've shared, it seems that does not complete.
When davinci is ready to service requests, this message should appear :
===Davinci Init Finish...
S: cmd_get_enable_list
But no such message.

 

[watchful_ip]

Well, scratch that theory about the configuration maybe being a cause of the bootloop..
Both pri and sec were erased and rebuilt with default values.

I still can't see why the bootloop is happening.
Somehow, though, I feel that this
=====prtHardInfo=====
connect failre errno=2
must be significant.

Davinci has an extensive initiallisation process - in the logs you've shared, it seems that does not complete.
When davinci is ready to service requests, this message should appear :
===Davinci Init Finish...
S: cmd_get_enable_list
But no such message.

Refresh the thread

 

[alastairstevenson]

If you boot the camera, leave for 5 minutes, and run the ps command again - is that modprobe still running?

If so, I think that is the problem.

Well spotted!
It just shows you what an eye for detail can do.

 

[alastairstevenson]

Refresh the thread

Yes, I was puzzling over the logs and didn't notice the thread had been updated.
With a good result!

 

[watchful_ip]

Well spotted!
It just shows you what an eye for detail can do.

Team effort

 

[kispista]