Dahua VTO2000a with wrong MCU firmware
- Thread starter Droefelken
- Start date
riogrande75
Pulling my weight
This question does not fit in this thread - pls. find the correct one or open a new one!
Just how to get img files from bin firmware?
I found this VTO2000A-C Nachfolger: VTO4202F
Can't understand how to get img.
Unbrick vto4202f
Please help. How to unbrick vto4202 I found this thread VTO2000A-C Nachfolger: VTO4202F But can't understand how to get img files from bin firmware. I try to flash via tftp DH_VTOXXXXD-G_MultiLang_PN_SIP_V4.500.0000000.8.R.210203.bin as sign.bin dhboot # tftp 0x82000000 sign.bin; flwrite...
Last edited:
riogrande75
Pulling my weight
VDD was 3.3V in this case.
Hi everyone, I had kept a VTO2111D with 210 cpu. Unfortunately I made the mistake of trying to update the MCU and now it gives me an invalid date even though it works in P2P. I saw that the programmer is very expensive, can anyone give me advice on how to do it? The MCU file I have is for a 110, have any of you tried to reprogram it?
Hola. se pudo encontrar el archivo .hex?
were you able to find the hex file?
Do you have the firmware of VTO2000A in HEX file ? I need it to flash it
Do you have the firmware of VTO2000A in HEX file ? I need it to flash it
I only found bin files but its not possible to flash it with ST Visual Programmer, it only accepts HEX format (intel)
Yes, I have it, but I haven't been able to get it to work... it's something very strange and I gave up,
If you achieve it, you will tell me how.
Here I leave you the url of the hex
General_VTO2000A_MCU_V3.000.0000.0.R.20180316 (Slave devices only! .HEX file!)
http://www.mediafire.com/file/7eiis...ral_VTO2000A_MCU_V3.000.0000.0.R.20180316.zip[/QUOTE]
[/QUOTE]
ohhhh....I have that too, it was the only one I could find in HEX format, but it only works on a Slave/second unit. For ex. for the back door. You have the principal in the main door and one with this firmware for the second door.
It doesn't work as main unit
But many thanks for your reply
riogrande75
Pulling my weight
This tutorial is fantastic. But i'm stucked on difficult to STM32 ST-LINK Utility that gives me an error when connecting to the VTO (can not connect to target) .... and thats the key... because with STM32 ST-LINK Utility I can flash BIN files.
I tried with ST Visual Programmer and same dongle same connection ( VDD SWIM GND RST) it connects, can read and can write on the VTO, but.....only HEX files, and till today I never found a complete firmware in HEX format. I even tried to convert BIN file to Hex file but always without success, it appears to be because the first memory address that must start in 0x0008000. Can you help me, or with HEX file or how to bypass error of connecting with STM32 ST-LINK
THanks in advance
riogrande75 I can flash the HEX file (General_VTO2000A-MCU_V3.000.0000000.0.R.20181123.hex) but.... this is MCU file only... How can I flash the BIN file ?
After flash the HEX file the VTO still not available on the network.
And with STVP I cannot flash bin files only intel format HEX file
Help is needed.
Thanks in advance
riogrande75
Pulling my weight
There is a nice dahua unbricking thread here in this forum. Read it, understand it und you'll be good.
Hello Riogrande75 you make me dig and dig and dig in this forum.... but I feel you know more than me and no effort to help me
Here is my story:
My VTO2000A IP works fine till 2 months ago, what happened ? It started speaking English (normally portuguese). When in setup if I change language to portuguese in 1 minute it will become in English. If I knew... in English was OK
So I tried to flash different firmware trying to solve the issue.
By mistake...I flashed a 2-wire firmware and I lost the contact to the VTO.
Now I dont have access by network to the VTO.
Diging in this forum I bought a ST-Link V2 and following YOUR pdf instructions, I can read and write on the VTO but ONLY with "ST Visual Programmer". ST Visual Programmer only accepts HEX files, thats why I'm looking for the firmware in HEX file. The only file I found in HEX file is MCU file. I can flash it, but VTO dont boot after that.
Can you understand my point right now ?
Using STM32 ST-LINK Utility or Cube Programmer seems to be possible to flash BIN files, but I cant connect VTO with those two Utilitys because they send infinite connection errors.
Do you have any way to flash the VTO with the BIN file ?
Kind regards in advance
riogrande75
Pulling my weight
If you had searched more here, you would know that your problem is with the linux OS of the device not with the MCU.
Your MCU (responsible for some minor harware functions like button press, etc.) is (was) most likely not broken at all.
Read this thread, here you'll find the right answer: dahua-ipc-easy-unbricking-recovery-over-tftp
Your MCU (responsible for some minor harware functions like button press, etc.) is (was) most likely not broken at all.
Read this thread, here you'll find the right answer: dahua-ipc-easy-unbricking-recovery-over-tftp
RioGrande75
Thank you in advance for everything you posted on this forum and for any tips you may have given me. I actually managed to develop developments and techniques on the VTO but in reality I still don't have 100% back. Summary: The problem I have already explained previously. I started with ST-LINK V2 trying to reset the HEX file. I can read and write without any problem on the VTO (The last HEX file I loaded was the one available at General_VTO2000A-MCU_V3.000.0000000.0.R.20181123
Then I explained the problem again and RioGrande75 said to continue searching the forum and I did...many hours later and with the purchase of TTL UART Serial converter I can load the firmware I want with that technique of changing the first byte from DH to PK generate the various files etc etc and following the instructions I managed to gain access to the VTO again.
Current status: I can access the VTO via IP, I can see the VTO on my cell phone via P2P but...... I can't get the ring button to work, nor can I get the door relays to work. From VTH I can get it to detect the VTO via IP but I can't access the VTO image or open the doors. What could be happening?
(Firmware used General_Multi3_VTO2000A_EngItlFreGetDutSpaPor_P_16M_V3.200.0000.0.R.20190221 )