Serial Uart Connection problem

[Waltraudharror]

Hello,

after messing with my fw-update with the VTHCH1550chw2 Intercom with a ip camera the system does not boot up anymore.

I managed to set up a UART connection between USB to Serial Connection and I can see the bootloader starting loading linux but!

In the terminal program my keystrokes are not beeing shown correctly so I get something like

g1h/j+k)

if I type "g" "h".

I have already connected the ground pin, but still remains weired keys.

I have this converter

http://wiki.in-circuit.de/images/6/68/305000068A_USB_RS485_Bridge.pdf

Also there can be some switches set. I have already tried every combination which results in a different key interpretation but still not usable.

Maybe the wrong connector?

Thank You for Your ideas

 

[0blar]

try different speed communication

 

[alastairstevenson]

I have this converter

http://wiki.in-circuit.de/images/6/68/305000068A_USB_RS485_Bridge.pdf

That's an RS-485 convertor - is that actually what the device requires? Where did you get that info?
Usually the serial console presents as TTL serial, requiring a TTL serial to USB convertor.
But I'm not familiar with your device.

 

[0blar]

can you download putty Download PuTTY: latest release (0.70)
and configure it to use serial connexion with correct port
and see what you get

 

[Waltraudharror]

Thank You very much for Your reply - I have bought a usb serial ttl converter - maybe this will do.

USB 2.0 CH340G TTL Konverter Adapter CP2102 PL2303 UART FTDI Arduino 5V + 3.3V | eBay

Thank You

 

[Waltraudharror]

Connection via putty works fine with same result. If a press some keys they result weird inputs:

 

[alastairstevenson]

OK, it's a Dahua device.
Just as an off-the-wall suggestion:
Interrupt the bootloader by keeping * pressed as you power it on.
Press return a couple of times.
Check that typing something such as
printenv
echoes your characters OK.
Make a record of what they are, just in case you forget what you changed.

If it does - try this command:
setenv dh_keyboard 0
saveenv
reset

And see what happens.
To get any command access, you may also have to use :
setenv appauto 0
saveenv

*edit* And usually the serial interface settings are 115200baud, 8 bits no parity.

 

[0blar]

you can also setup keyboard effect in putty

also setup serial interface as alastairstevenson advise

 

[alastairstevenson]

you can also setup keyboard effect in putty

The dahua bootloader environment variable 'dh_keyboard' is used to inhibit the serial interface changeover from 'serial console mode' to 'application mode' when the kernel boots. Usually that means the output simply stops.
The 2 modes may have differing baudrate settings that would manifest as 'odd characters'.
But I'm still a bit suspicious of whether it needs an RS-485 interface, though I have no knowledge of the device itself.

 

[Waltraudharror]

Thank You very much. I can not stop the booting process eventhoúgh I send a lot of stars

UBL Version: 1.46t(DM365)09:30:17 Sep 2 2014
Oscillator: 24MHZ
ARM Rate: 432 MHZ
DDR Rate: 340 MHZ
BootMode: SPI
Starting SPI Memory Copy...
DONE
U-Boot 1.3.6 (jerry) (Sep 2 2014 - 09:44:01)
DRAM: 128 MB
SF: Got idcode c2 20 18 c2 20
In: serial
Out: serial
Err: serial
Ethernet PHY: GENERIC @ 0x05,id:221513
total gio 2
gio[22]=1
gio[25]=1
davinci_eth_open:no link
TFTP from server 192.168.254.254; our IP address is 192.168.1.108; sending through gateway 192.168.1.1
Filename 'upgrade_info_7db780a713a4.txt'.
Load address: 0x80100000
Loading: WARN: emac_send_packet: No link
*
Retry count exceeded; starting again
Fail to get info file!
Init error!
TFTP from server 192.168.254.254; our IP address is 192.168.1.108; sending through gateway 192.168.1.1
Filename 'failed.txt'.
Load address: 0x80200000
*oading: *
Retry count exceeded; starting again
==>use default images
..*..
## Booting kernel from Legacy Image at 80007fc0 ...
Image Name: Linux-2.6.18_pro500-davinci_evm-
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 1685312 Bytes = 1.6 MB
Load Address: 80008000
Entry Point: 80008000
Verifying Checksum ... OK
XIP Kernel Image ... OK
OK
Starting kernel ...
.......................................... done, booting the kernel.
*
# *5**5*5*5*55*5**5*5*5*55*5***********************************************
Checking DDR......OK
UBL Version: 1.46t(DM365)09:30:17 Sep 2 2014
Oscillator: 24MHZ
ARM Rate: 432 MHZ
DDR Rate: 340 MHZ
Bo▒tMode: SPI
Starting SPI Memory Copy...
***DONE
U-Boot 1.3.6 (jerry) (Sep 2 2014 - 09:44:01)
DRAM: 128 MB
SF: Got idcode c2 20 18 c2 20
*In: serial
Out: serial
Err: serial
*Ethernet PHY: GENERIC @ 0x05,id:221513
*total gio 2
gio[22]=1
gio[25]=1
********************************************************************************************davinci_eth_open:no link
TF*▒ from server 192.168.254.254; our IP address is 192.168.1.108; sending through gateway 192.168.1.1
Filename 'upgrade_info_7db780a713a4.txt'.
Load address: 0x80100000
Loading: WARN: emac_send_packet: No link
*****************************
Retry count exceeded; starting again
Fail to get info file!
Init error!
********************************************************************************************davinci_eth_open:no link
TFTP from server 192.168.254.254; our IP address is 192.168.1.108; sending through gateway 192.168.1.1
Filename 'failed.txt'.
Load address: 0x80200000
Loading: WIYN: emac_send_packet: No link
****************************
Retry count exceeded; starting again
==>use default images
****.*****.****.****.****.****.****.
## Booting kernel from Legacy Image at 80007fc0 ...
Image Name: Linux-2.6.18_pro500-davinci_evm-
Image Type: ARM Linux Kernel Image (un#empressed)
Data Size: 1685312 Bytes = 1.6 MB
Load Address: 80008000
Entry Point: 80008000
Verifying Checksum ... *************OK
XIP Kernel Image ... OK
OK
Starting kernel ...
Uncompressing Linux...*......*.....*.....*.....*.....*.....*.....*......*....*.....*.....*.....*.....*.....*.....*.....R▒.....*......*.......*.....*....... done, booting the kernel.
******
# *5*5

 

[Waltraudharror]

Maybe it is just the wrong connector?

 

[0blar]

Better using usb serial rs232 ttl converter
I think rs485 you have will not work properly

 

[tangent]

just wait until you get the ttl serial adapter. if you keep trying to use the rs-485 adapter you might break something.

 

[Waltraudharror]

Finaly the new adaptor did it! That was the problem and managed to stop at the bootloader prompt.

Can You tell me how to get the fw on the device? I have downloaded the fw-zip file which contain the files below. Normally I guess the network can be activated, but in my case I have a 2 Wire connection to the network device. I guess I have to transfer the fw with the ttl-connection.

I will post the fw Files, a photo and the log:

printenv
bootcmd=fsload
bootdelay=3
baudrate=115200
eth1addr=00:01:5b:00:55:66
eth2addr=00:01:5b:00:77:88
ipaddr=192.168.1.108
serverip=192.168.1.1
netmask=255.255.255.0
bootfile="uImage"
dh_keyboard=1
appauto=1
single=0
da=protect off all;tftp 81a00000 dm365_ubl_boot_16M.bin.img;flwrite
dc=tftp 81a00000 custom-x.cramfs.img; flwrite
dr=tftp 81a00000 romfs-x.cramfs.img; flwrite
du=tftp 81a00000 user-x.cramfs.img; flwrite
dd=tftp 81a00000 data-x.cramfs.img; flwrite
dw=tftp 81a00000 web-x.cramfs.img; flwrite
dg=tftp 81a00000 gui-x.cramfs.img; flwrite
dk=tftp 81a00000 kernel-x.cramfs.img; flwrite
up=tftp 81a00000 update.img; flwrite
tk=tftp 80800000 uImage; bootm 80800000
gionum=22.25
gioval=1.1
dh_com=0
autosip=192.168.254.254
autolip=192.168.1.108
autogw=192.168.1.1
autonm=255.255.255.0
ID=3M0236EPAN00002
ethaddr=14:A7:8B:0D:72:FD
HWID=VTH1510CH:0:4:2:0:5:4:1:9:3:3:1:1B0:0:0:0:6:0:0:1
bootargs=console=ttyS0,115200n8 root=/dev/mtdblock4 rootfstype=cramfs,nolock mem=90M newmem=96M video=davincifb:vid0=OFF:vid1=OFFsd0=OFFsd1=OFF
stdin=serial
stdout=serial
stderr=serial
ver=U-Boot 1.3.6 (jerry) (Sep 2 2014 - 09:44:01)
Environment size: 1126/16380 bytes
DHBOOT# <INTERRUPT>
DHBOOT#


the fw-files




Thank You - Nils