car-dvr.info

Car-DVR – English Speaking Forums => BlackVue => BlackVue DR500GW-HD WiFi - in English => Тема начата: neoncek от 05 Ноября 2014, 13:57:48

Название: DR500GW-HD self bricked?
Отправлено: neoncek от 05 Ноября 2014, 13:57:48

Hello guys, greetings from Slovakia  ~))

I am dealing some problem with my DR500GW-HD already discussed at dashcamtalk forum, so I`ll copy-paste some info here as I am lost in ideas how to recover it.
Link to discussion:
http://goo.gl/Iz3RdE (https://car-dvr.info/forum/go.php?url=aHR0cDovL2dvby5nbC9JejNSZEU=)

Issue description:
Everything was ok untill yesterday, I stopped at the petrol station and once I moved, camera repeated some some non-english sound. I guess russian. Several times I removed power cord to restart, no success.
At home I removed card, used SDformat tool, made surface scan and copied them fresh-downloaded firmware v2.002. Same software version was on SD card before.
All LED blinked once, then GPS (blue) LED s ON for 6 seconds,
then Security LED (in front) & REC LED (in red) & WiFi LED blinked once,
REC LED (in green) keep ON for 11 seconds.
During this time there is no recording detected on microSD card.
Once started without SD card, same behavior as described above but green REC LED keeps ON untill powered.
I have tested 2 microSD cards fresh formated to FAT32:
- 16GB MicroSDHC from Pittasoft
- 64GB MicroSDXC Kingston
Car voltage checked, it gives me 11,89V DC, at home I use 12V/1,5A; 12V/5A and 12V/300mA power supplies.
Several monkey-snatch tried with reset and WiFi button, no success too.
Battery was changed 2 months ago, I have tried to install firmware v1.005E on SD card, but no success, it just ignore SDcard.
I guess I will need to use some UART cable..
Or is there any way for deeper troubleshooting?
I am open to all possible options to recover my only dashcam.
May I kindly ask you for guidance please?

My video for better view...
[youtube]YPSuR2kzLTw[/youtube]

Thank you in advance for your advices.

Название: Re: DR500GW-HD self bricked?
Отправлено: alexsoll от 05 Ноября 2014, 14:06:31

neoncek, put an empty memory card and turn on the DVR
what going on?

Название: Re: DR500GW-HD self bricked?
Отправлено: MiO_970 от 05 Ноября 2014, 14:33:21

without sd card - turns on,  wifi start?

Название: Re: DR500GW-HD self bricked?
Отправлено: neoncek от 05 Ноября 2014, 22:22:15

Hello, at the first --> thank you for reply  ;)

I have run my dashcam without SD --> no WiFi found, REC LED stayed green untill power off
I fresh formated my Pittasoft SD 16GB using SD formatter (FAT32 32kB), put to the cam switched on my power supply
 --> no WiFi found BUT I got a sound I heared in the car as described above
 --> https://dl.dropboxusercontent.com/u/5654133/DR500GW-HD.m4a (https://car-dvr.info/forum/go.php?url=aHR0cHM6Ly9kbC5kcm9wYm94dXNlcmNvbnRlbnQuY29tL3UvNTY1NDEzMy9EUjUwMEdXLUhELm00YQ==)

Название: Re: DR500GW-HD self bricked?
Отправлено: neoncek от 07 Ноября 2014, 13:41:34

Any other steps I need to do?

Название: Re: DR500GW-HD self bricked?
Отправлено: MiO_970 от 07 Ноября 2014, 14:46:09

Only connect UART
 )O(

Название: Re: DR500GW-HD self bricked?
Отправлено: hillbilly от 07 Ноября 2014, 15:04:38

 Read the post by darthmarx down the page a bit

Название: Re: DR500GW-HD self bricked?
Отправлено: neoncek от 07 Ноября 2014, 21:05:08

OK so, I need UART cable at the first. Would this be applicable?: http://goo.gl/1d8kBx (https://car-dvr.info/forum/go.php?url=aHR0cDovL2dvby5nbC8xZDhrQng=)
 ..--.. Is there any procedure/guide how to push the firmware there?
Thanks in advance for your advices.

Название: Re: DR500GW-HD self bricked?
Отправлено: DenisSharifulin от 07 Ноября 2014, 21:29:42

Сообщение от neoncek

Would this be applicable?: [url]http://goo.gl/1d8kBx[/url] ([url]https://car-dvr.info/forum/go.php?url=aHR0cDovL2dvby5nbC8xZDhrQng=[/url])

Yes

Название: Re: DR500GW-HD self bricked?
Отправлено: neoncek от 10 Ноября 2014, 13:51:31

Thanks for reply, I ordered it already. Delivery will take some time...
So if I want to push custom firmware from http://goo.gl/DRvKKG, (https://car-dvr.info/forum/go.php?url=aHR0cDovL2dvby5nbC9EUnZLS0cs) how to connect UART (pins) and which file to push to DR500GW-HD?

Название: Re: DR500GW-HD self bricked?
Отправлено: DenisSharifulin от 10 Ноября 2014, 19:04:11

neoncek, http://car-dvr.info/forum/index.php?topic=212.0 (http://car-dvr.info/forum/index.php?topic=212.0)

Название: Re: DR500GW-HD self bricked?
Отправлено: neoncek от 11 Ноября 2014, 16:37:22

 )ooo( Great, thank you guys, Gtranslator gave me text in english so I can go on once I receive UART  )ooo(
Based on picture from Delorm`s first post of mentioned topic, I should connect to 16PIN slim connector.
Guess I can write down some steps in english afterwards...  |||

Название: Re: DR500GW-HD self bricked?
Отправлено: alexsoll от 11 Ноября 2014, 16:56:23

neoncek,

(кликните для показа/скрытия)

---

---

1. CP2102 Module USB to USART(UART) 3.3V TTL USB To COM (http://www.ebay.com/itm/170946368201?_trksid=p2055119.m1438.l2649&ssPageName=STRK%3AMEBIDX%3AIT)
Driver, etc. is on the purchase page.
(http://ipic.su/actco.png)

was complete with wires:

(http://ipic.su/acteA.png)

---

---

2. FFC/FPC connector 16pin pitch 0.5mm (http://www.ebay.com/itm/170967974356?_trksid=p2055119.m1438.l2649&ssPageName=STRK%3AMEBIDX%3AIT)

(http://ipic.su/actbS.png)

---

---

3. FPC 16pin/15cm , 0.5mm (http://www.ebay.com/itm/181063544128?_trksid=p2055119.m1438.l2649&ssPageName=STRK%3AMEBIDX%3AIT)

(http://ipic.su/actcj.png)

---

---

Название: Re: DR500GW-HD self bricked?
Отправлено: neoncek от 13 Декабря 2014, 04:35:12

Hello guys,

I have just received UART and cannot wait so I connected cables, installed driver for UART, started dashcam without SD, holding "d" while I got a prompt:
DR500GW-HD>loadb 0x82000000
I have pushed file "cramfsImage_DR500GW" (from DR500GW-HD_v2.002E) over HyperTerminal which took some time..
DR500GW-HD>nand erase 0xa00000 0xdd0000
DR500GW-HD>nand write 0x82000000 0xa00000 0xdd0000
...reboot, no WiFi detected, no alarm from dashcam...
Welcome to MontaVista(R) Linux(R) Professional Edition 5.0.0 (0702774).
console login root/pt
Inserted SD with patch_DR500GW.bin at root
# cd /
# mount -t vfat /dev/mmcblk0p1 /mnt/mmc
# rm -rf /mnt/nand/*
# tar -xvzf /mnt/mmc/patch_DR500GW.bin -C /
mnt/
mnt/nand/
mnt/nand/default/
tar: can't make dir mnt/nand/default: Read-only file system
mnt/nand/default/config_chn/
tar: can't create directory 'mnt/nand/default': Read-only file system
tar: can't make dir mnt/nand/default/config_chn: No such file or directory
mnt/nand/default/config_chn/config.ini
tar: can't create directory 'mnt/nand/default/': Read-only file system
tar: can't open 'mnt/nand/default/': Is a directory

Any guru's idea please? Thx in advance.

(кликните для показа/скрытия)

---

---

DM36x initialization passed!
TI UBL Base Version: 1.50
Boot Loader BootMode = NAND
Starting NAND Copy...
Valid magicnum, 0xA1ACED66, found in block 0x00000008.
Boot Mode Task Completed

IPNC UBL Version: 1.1.0
Platform: DM368

Jumping to entry point at 0x81080000

U-Boot 1.3.4 (Dec 13 2012 - 15:36:20) DM368-IPNC-1.1.1

I2C:   ready
DRAM:  256 MB
NAND:  NAND device: Manufacturer ID: 0xec, Chip ID: 0xf1 (Samsung NAND 128MiB 3,3V 8-bit)
Bad block table found at page 65472, version 0x01
Bad block table found at page 65408, version 0x01
128 MiB
*** Warning - bad CRC or NAND, using default environment

In:    serial
Out:   serial
Err:   serial
ARM Clock :- 432MHz
DDR Clock :- 340MHz
Ethernet PHY: GENERIC @ 0x00
Press "d" or " " to abort autoboot in 1 seconds

NAND read: device 0 offset 0x500000, size 0x500000
 5242880 bytes read: OK
## Booting kernel from Legacy Image at 82000000 ...
   Image Name:   Linux-2.6.18_pro500-davinci_IPNC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2044048 Bytes =  1.9 MB
   Load Address: 80008000
   Entry Point:  80008000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK
OK

Starting kernel ...

Linux version 2.6.18_pro500-davinci_IPNC_DM368_2.6.0 (root@ubuntu26-TI) (gcc version 4.2.0 (MontaVista 4.2.0-16.0.32.0801914 2008-08-30)) #1 PREEMPT Wed May 8 22:14:04 KST 2013
CPU: ARM926EJ-S [41069265] revision 5 (ARMv5TEJ), cr=00053177
Machine: DaVinci DM368 IPNC
Memory policy: ECC disabled, Data cache writeback
DaVinci DM0365 variant 0x8
PLL0: fixedrate: 24000000, commonrate: 170000000, vpssrate: 340000000
PLL0: vencrate_sd: 75555555, ddrrate: 340000000 mmcsdrate: 48571428
PLL1: armrate: 432000000, voicerate: 20571428, vencrate_hd: 27000000
CPU0: D VIVT write-back cache
CPU0: I cache: 16384 bytes, associativity 4, 32 byte lines, 128 sets
CPU0: D cache: 8192 bytes, associativity 4, 32 byte lines, 64 sets
Built 1 zonelists.  Total pages: 32768
Kernel command line: mem=128M console=ttyS1,115200 root=/dev/mtdblock3 rootfstype=cramfs,squashfs ip=off mtdparts=nand_davinci.0:0x300000(boot),0x200000(env),0x500000(kernel),0x3000000(rootfs),0x4000000(data1),-(data2) eth=96:a6:6c:45:e2:c0 board=DR500T
TI DaVinci EMAC: kernel boot params Ethernet address: 96:a6:6c:45:e2:c0
PID hash table entries: 1024 (order: 10, 4096 bytes)
Clock event device timer0_0 configured with caps set: 07
Console: colour dummy device 80x30
Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
Memory: 128MB = 128MB total
Memory: 125440KB available (3341K code, 907K data, 184K init)
Security Framework v1.0.0 initialized
Capability LSM initialized
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
NET: Registered protocol family 16
DaVinci: 104 gpio irqs
MUX: initialized GPIO20
MUX: initialized I2C_SCL
MUX: initialized CLKOUT1
Generic PHY: Registered new driver
ch0 default output "COMPOSITE", mode "NTSC"
VPBE Encoder Initialized
SCSI subsystem initialized
usbcore: registered new driver usbfs
usbcore: registered new driver hub
NET: Registered protocol family 2
IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
TCP established hash table entries: 4096 (order: 2, 16384 bytes)
TCP bind hash table entries: 2048 (order: 1, 8192 bytes)
TCP: Hash tables configured (established 4096 bind 2048)
TCP reno registered
VFS: Disk quotas dquot_6.5.1
Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
squashfs: version 3.1 (2006/08/19) Phillip Lougher
JFFS2 version 2.2. (NAND) (SUMMARY)  (C) 2001-2006 Red Hat, Inc.
yaffs May  8 2013 22:11:55 Installing.
Initializing Cryptographic API
io scheduler noop registered
io scheduler anticipatory registered (default)
io scheduler deadline registered
io scheduler cfq registered
 sbulla:<5>Req dev 0 dir 0 sec 0, nr 8 f 944
 unknown partition table
LTT : ltt-facilities init
LTT : ltt-facility-core init in kernel
LTT : ltt-facility-statedump init in kernel
LTT : ltt-relay init
ltt-control init
LTT : ltt-facility-statedump init
DAVINCI-WDT: DaVinci Watchdog Timer: heartbeat 60 sec
Serial: 8250/16550 driver $Revision: 1.90 $ 2 ports, IRQ sharing disabled
serial8250.0: ttyS0 at MMIO map 0x1c20000 mem 0xfbc20000 (irq = 40) is a 16550A
serial8250.0: ttyS1 at MMIO map 0x1d06000 mem 0xfbd06000 (irq = 41) is a 16550A
RAMDISK driver initialized: 1 RAM disks of 32768K size 1024 blocksize
loop: loaded (max 8 devices)
PPP generic driver version 2.4.2
PPP Deflate Compression module registered
tun: Universal TUN/TAP device driver, 1.6
tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
rtw driver version=v3.4.3_4369.20120622
Build at: May  8 2013 22:12:41
usbcore: registered new driver rtl8192cu
Davinci EMAC MII Bus: probed
MAC address is 96:a6:6c:45:e2:c0
TI DaVinci EMAC Linux version updated 4.0
netconsole: not configured, aborting
Linux video capture interface: v2.00
Trying to register davinci display video device.
layer=c06a7c00,layer->video_dev=c06a7d60
Trying to register davinci display video device.
layer=c06a7a00,layer->video_dev=c06a7b60
davinci_init:DaVinci V4L2 Display Driver V1.0 loaded
i2c /dev entries driver
nand_davinci nand_davinci.0: Using 4-bit hardware ECC
NAND device: Manufacturer ID: 0xec, Chip ID: 0xf1 (Samsung NAND 128MiB 3,3V 8-bit)
6 cmdlinepart partitions found on MTD device nand_davinci.0
Creating 6 MTD partitions on "nand_davinci.0":
0x00000000-0x00300000 : "boot"
0x00300000-0x00500000 : "env"
0x00500000-0x00a00000 : "kernel"
0x00a00000-0x03a00000 : "rootfs"
0x03a00000-0x07a00000 : "data1"
0x07a00000-0x08000000 : "data2"
nand_davinci nand_davinci.0: hardware revision: 2.3
musb_hdrc: version 6.0/dbg, pio, host, debug=1
musb_hdrc: USB Host mode controller at c88e6000 using PIO, IRQ 12
musb_hdrc musb_hdrc: MUSB HDRC host driver
musb_hdrc musb_hdrc: new USB bus registered, assigned bus number 1
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 1 port detected
[drivers/rtc/rtc-pcf8563.c:pcf8563_probe:288]kind(-1) return
pcf8563 0-0051: chip found, driver version 0.4.2
pcf8563 0-0051: rtc intf: proc
pcf8563 0-0051: rtc intf: dev (254:0)
pcf8563 0-0051: rtc core: registered pcf8563 as rtc0
davinci-mmc davinci-mmc.0: Supporting 4-bit mode
davinci-mmc davinci-mmc.0: Using DMA mode
Advanced Linux Sound Architecture Driver Version 1.0.12rc1 (Thu Jun 22 13:55:50 2006 UTC).
>>>[mmc_setup:1426] power_mode:MMC_POWER_OFF[0]
ASoC version 0.13.1
MUX: initialized MCBSP_BDX
MUX: initialized MCBSP_X
MUX: initialized MCBSP_BFSX
MUX: initialized MCBSP_BDR
MUX: initialized MCBSP_R
MUX: initialized MCBSP_BFSR
wm8960: WM8960 Audio Codec 0.2
asoc: WM8960 <-> davinci-i2s mapping ok
ALSA device list:
  #0: DaVinci DM365 WM8960 (WM8960)
IPv4 over IPv4 tunneling driver
GRE over IPv4 tunneling driver
Initializing XFRM netlink socket
NET: Registered protocol family 1
NET: Registered protocol family 17
NET: Registered protocol family 15
ieee80211: 802.11 data/management/control stack, git-1.1.13
ieee80211: Copyright (C) 2004-2005 Intel Corporation <jketreno@linux.intel.com>
Time: timer0_1 clocksource has been installed.
Clock event device timer0_0 configured with caps set: 08
Switched to high resolution mode on CPU 0
pcf8563 0-0051: low voltage detected, date/time is not reliable.
pcf8563 0-0051: setting the system clock to 2010-01-11 01:50:45 (1263174645)
VFS: Mounted root (cramfs filesystem) readonly.
Freeing init memory: 184K
INIT: version 2.86 booting
0
mkdir: can't create directory '/dev/.test': Read-only file system
Done /etc/rc.d/rcS.d/S03mountvirtfs..
Starting the hotplug events dispatcher: udevd.
Synthesizing the initial hotplug events...done.
Waiting for /dev to be fully populated...done.
Done /etc/rc.d/rcS.d/S04udev..
Starting Dropbear SSH server: yaffs: dev is 32505860 name is "mtdblock4"
dropbear.
Done yaffs: passed flags ""
/etc/rc.d/rcS.d/yaffs: Attempting MTD mount on 31.4, "mtdblock4"
S36dropbear..
Done /etc/rc.d/rcS.d/S41portmap..
###############################################
###############################################
### application start...                 ######
###############################################
###############################################
Mount patch area at nand flash...
nand_davinci_4bit_compare_ecc Too many errors to be corrected!
yaffs tragedy: Bad object type, -78143499 != 11, for object 129994303 at chunk 4990 during scan
yaffs tragedy: Bad object type, -201344001 != 7, for object 228585082 at chunk 4989 during scan
yaffs tragedy: Bad object type, 2147450878 != 1, for object 237862910 at chunk 4988 during scan
CSL: Module install successful, device major num = 253
mount: wrong fs CSL: Module version 0.10.00, built on Mar 13 2014 17:15:34
type, bad option, bad superblock on /dev/mtdblock4,
       missing codepage or other error
       In some cases useful info is found in syslog - try
       dmesg | tail  or so

I2C: Module install successful, device major num = 252
DMA: Module install successful, device major num = 251
DRV: Module install successful
DRV: Module built on Mar 13 2014 17:15:36
DRV: EDMACC.QUEPRI  = 00000777
DRV: SYSTEM.MSTPRI0 = 00440022
DRV: SYSTEM.MSTPRI1 = 00000244
DRV: ISP.BCR        = 00000002
DRV: SYSTEM.MISC    = 00000319
CMEMK module: built on Mar 27 2013 at 18:15:50
  Reference Linux version 2.6.18
  File /home/sejung/project/DR500/dvsdk_2_10_01_18/linuxutils_2_24_03/packages/ti/sdo/linuxutils/cmem/src/module/cmemk.c
allocated heap buffer 0xc9000000 of size 0x8000000
CMEM Range Overlaps Kernel Physical - allowing overlap
CMEM phys_start (0x1000) overlaps kernel (0x80000000 -> 0x88000000)
cmemk initialized
EDMAK module: built on Mar 27 2013 at 18:15:52
  Reference Linux version 2.6.18
  File /home/sejung/project/DR500/dvsdk_2_10_01_18/linuxutils_2_24_03/packages/ti/sdo/linuxutils/edma/src/module/edmak.c
IRQK module: built on Mar 27 2013 at 18:15:53
  Reference Linux version 2.6.18
  File /home/sejung/project/DR500/dvsdk_2_10_01_18/linuxutils_2_24_03/packages/ti/sdo/linuxutils/irq/src/module/irqk.c
irqk initialized
[JC:82] CSL_gpioSet[flag:1]
wlan0 waitting... 1/5 sec.
usb 1-1: new high speed USB device using musb_hdrc and address 2
usb 1-1: configuration #1 chosen from 1 choice
CHIP TYPE: RTL8188C_8192C

usb_endpoint_descriptor(0):
bLength=7
bDescriptorType=5
bEndpointAddress=81
wMaxPacketSize=200
bInterval=0
RT_usb_endpoint_is_bulk_in = 1

usb_endpoint_descriptor(1):
bLength=7
bDescriptorType=5
bEndpointAddress=2
wMaxPacketSize=200
bInterval=0
RT_usb_endpoint_is_bulk_out = 2

usb_endpoint_descriptor(2):
bLength=7
bDescriptorType=5
bEndpointAddress=3
wMaxPacketSize=200
bInterval=0
RT_usb_endpoint_is_bulk_out = 3

usb_endpoint_descriptor(3):
bLength=7
bDescriptorType=5
bEndpointAddress=84
wMaxPacketSize=40
bInterval=1
RT_usb_endpoint_is_int_in = 4, Interval = 1
nr_endpoint=4, in_num=2, out_num=2

USB_SPEED_HIGH
Chip Version ID: VERSION_NORMAL_TSMC_CHIP_88C.
RF_Type is 3!!
EEPROM type is E-FUSE
====> ReadAdapterInfo8192C
Boot from EFUSE, Autoload OK !
EEPROMVID = 0x0bda
EEPROMPID = 0x8176
EEPROMCustomerID : 0x00
EEPROMSubCustomerID: 0x00
RT_CustomerID: 0x00
_ReadMACAddress MAC Address from EFUSE = 00:25:42:e0:86:a1
EEPROMRegulatory = 0x0
_ReadBoardType(0)
BT Coexistance = disable
RT_ChannelPlan: 0x0a
_ReadPSSetting...bHWPwrPindetect(0)-bHWPowerdown(0) ,bSupportRemoteWakeup(0)
### PS params=>  power_mgnt(0),usbss_enable(0) ###
### AntDivCfg(0)
readAdapterInfo_8192CU(): REPLACEMENT = 1
<==== ReadAdapterInfo8192C in 110 ms
rtw_macaddr_cfg MAC Address  = 00:25:42:e0:86:a1
MAC Address from pnetdev->dev_addr= 00:25:42:e0:86:a1
bDriverStopped:1, bSurpriseRemoved:0, bup:0, hw_init_completed:0
+871x_drv - drv_open, bup=0
wlan found..1/5 sec..==> [ wlan0     Link encap: ===> FirmwareDownload91C() fw:Rtl819XFwImageArray_TSMC
Ethernet  HWaddrFirmwareDownload92C accquire FW from embedded image
 00:25:42:E0:86:fw_ver=v80, fw_subver=0, sig=0x88c0
A1   ]
fw download ok!
Set RF Chip ID to RF_6052 and RF type to 1T1R.
IQK:Start!!!
Path A IQK Success!!
Path A IQK Success!!
IQK: final_candidate is 0
IQK: RegE94=100 RegE9C=a RegEA4=fe RegEAC=2 RegEB4=0 RegEBC=0 RegEC4=0 RegECC=0
 Path A IQ Calibration Success !
pdmpriv->TxPowerTrackControl = 1
MAC Address from REG_MACID = 00:25:42:e0:86:a1
rtl8192cu_hal_init in 550ms
MAC Address = 00:25:42:e0:86:a1
-871x_drv - drv_open, bup=1
wlan up!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
survey done event(15)
wlan scanning..!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
best channel copying...!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
nand app not exists...
Factory Test Starting...
INIT: Entering runlevel: 3
Starting telnet daemon.
Starting INET services: done.
Starting syslogd/klogd: #### pittaTest mode Not recording !!! :-) JCH.
done
Simple mixer control 'ADC PCM',0
  Capabilities: cvolume
  Capture channels: Front Left - Front Right
  Limits: Capture 0 - 127
  Front Left: Capture 53 [42%]
  Front Right: Capture 53 [42%]

MontaVista(R) Linux(R) Professional Edition 5.0.0 (0702774)

localhost login: [01:51:00][readConfig:3601]EOUT7-0
[01:51:00][main:1194]EOUT0-8
[01:51:00]End System - 0
[01:51:00]End System umount
umount: /mnt/mmc: not mounted
[main:1377]
[01:51:00]Cancel button_thread
[01:51:00]caught SIGSEGV: exit, backtrace size:1
[01:51:00]0:[(nil)]

MontaVista(R) Linux(R) Professional Edition 5.0.0 (0702774)

localhost login:

(кликните для показа/скрытия)

---

---

DM36x initialization passed!
TI UBL Base Version: 1.50
Boot Loader BootMode = NAND
Starting NAND Copy...
Valid magicnum, 0xA1ACED66, found in block 0x00000008.
Boot Mode Task Completed

IPNC UBL Version: 1.1.0
Platform: DM368

Jumping to entry point at 0x81080000

U-Boot 1.3.4 (Dec 13 2012 - 15:36:20) DM368-IPNC-1.1.1

I2C:   ready
DRAM:  256 MB
NAND:  NAND device: Manufacturer ID: 0xec, Chip ID: 0xf1 (Samsung NAND 128MiB 3,                                                                                                                               3V 8-bit)
Bad block table found at page 65472, version 0x01
Bad block table found at page 65408, version 0x01
128 MiB
*** Warning - bad CRC or NAND, using default environment

In:    serial
Out:   serial
Err:   serial
ARM Clock :- 432MHz
DDR Clock :- 340MHz
Ethernet PHY: GENERIC @ 0x00
Press "d" or " " to abort autoboot in 1 seconds

NAND read: device 0 offset 0x500000, size 0x500000
 5242880 bytes read: OK
## Booting kernel from Legacy Image at 82000000 ...
   Image Name:   Linux-2.6.18_pro500-davinci_IPNC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2044048 Bytes =  1.9 MB
   Load Address: 80008000
   Entry Point:  80008000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK
OK

Starting kernel ...

Linux version 2.6.18_pro500-davinci_IPNC_DM368_2.6.0 (root@ubuntu26-TI) (gcc version 4.2.0 (MontaVista 4.2.0-16.0.32.0801914 2008-08-30)) #1 PREEMPT Wed May 8 22:14:04 KST 2013
CPU: ARM926EJ-S [41069265] revision 5 (ARMv5TEJ), cr=00053177
Machine: DaVinci DM368 IPNC
Memory policy: ECC disabled, Data cache writeback
DaVinci DM0365 variant 0x8
PLL0: fixedrate: 24000000, commonrate: 170000000, vpssrate: 340000000
PLL0: vencrate_sd: 75555555, ddrrate: 340000000 mmcsdrate: 48571428
PLL1: armrate: 432000000, voicerate: 20571428, vencrate_hd: 27000000
CPU0: D VIVT write-back cache
CPU0: I cache: 16384 bytes, associativity 4, 32 byte lines, 128 sets
CPU0: D cache: 8192 bytes, associativity 4, 32 byte lines, 64 sets
Built 1 zonelists.  Total pages: 32768
Kernel command line: mem=128M console=ttyS1,115200 root=/dev/mtdblock3 rootfstype=cramfs,squashfs ip=off mtdparts=nand_davinci.0:0x300000(boot),0x200000(env),0x500000(kernel),0x3000000(rootfs),0x4000000(data1),-(data2) eth=96:a6:6c:45:e2:c0 board=DR500T
TI DaVinci EMAC: kernel boot params Ethernet address: 96:a6:6c:45:e2:c0
PID hash table entries: 1024 (order: 10, 4096 bytes)
Clock event device timer0_0 configured with caps set: 07
Console: colour dummy device 80x30
Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
Memory: 128MB = 128MB total
Memory: 125440KB available (3341K code, 907K data, 184K init)
Security Framework v1.0.0 initialized
Capability LSM initialized
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
NET: Registered protocol family 16
DaVinci: 104 gpio irqs
MUX: initialized GPIO20
MUX: initialized I2C_SCL
MUX: initialized CLKOUT1
Generic PHY: Registered new driver
ch0 default output "COMPOSITE", mode "NTSC"
VPBE Encoder Initialized
SCSI subsystem initialized
usbcore: registered new driver usbfs
usbcore: registered new driver hub
NET: Registered protocol family 2
IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
TCP established hash table entries: 4096 (order: 2, 16384 bytes)
TCP bind hash table entries: 2048 (order: 1, 8192 bytes)
TCP: Hash tables configured (established 4096 bind 2048)
TCP reno registered
VFS: Disk quotas dquot_6.5.1
Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
squashfs: version 3.1 (2006/08/19) Phillip Lougher
JFFS2 version 2.2. (NAND) (SUMMARY)  (C) 2001-2006 Red Hat, Inc.
yaffs May  8 2013 22:11:55 Installing.
Initializing Cryptographic API
io scheduler noop registered
io scheduler anticipatory registered (default)
io scheduler deadline registered
io scheduler cfq registered
 sbulla:<5>Req dev 0 dir 0 sec 0, nr 8 f 944
 unknown partition table
LTT : ltt-facilities init
LTT : ltt-facility-core init in kernel
LTT : ltt-facility-statedump init in kernel
LTT : ltt-relay init
ltt-control init
LTT : ltt-facility-statedump init
DAVINCI-WDT: DaVinci Watchdog Timer: heartbeat 60 sec
Serial: 8250/16550 driver $Revision: 1.90 $ 2 ports, IRQ sharing disabled
serial8250.0: ttyS0 at MMIO map 0x1c20000 mem 0xfbc20000 (irq = 40) is a 16550A
serial8250.0: ttyS1 at MMIO map 0x1d06000 mem 0xfbd06000 (irq = 41) is a 16550A
RAMDISK driver initialized: 1 RAM disks of 32768K size 1024 blocksize
loop: loaded (max 8 devices)
PPP generic driver version 2.4.2
PPP Deflate Compression module registered
tun: Universal TUN/TAP device driver, 1.6
tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
rtw driver version=v3.4.3_4369.20120622
Build at: May  8 2013 22:12:41
usbcore: registered new driver rtl8192cu
Davinci EMAC MII Bus: probed
MAC address is 96:a6:6c:45:e2:c0
TI DaVinci EMAC Linux version updated 4.0
netconsole: not configured, aborting
Linux video capture interface: v2.00
Trying to register davinci display video device.
layer=c06a7c00,layer->video_dev=c06a7d60
Trying to register davinci display video device.
layer=c06a7a00,layer->video_dev=c06a7b60
davinci_init:DaVinci V4L2 Display Driver V1.0 loaded
i2c /dev entries driver
nand_davinci nand_davinci.0: Using 4-bit hardware ECC
NAND device: Manufacturer ID: 0xec, Chip ID: 0xf1 (Samsung NAND 128MiB 3,3V 8-bit)
6 cmdlinepart partitions found on MTD device nand_davinci.0
Creating 6 MTD partitions on "nand_davinci.0":
0x00000000-0x00300000 : "boot"
0x00300000-0x00500000 : "env"
0x00500000-0x00a00000 : "kernel"
0x00a00000-0x03a00000 : "rootfs"
0x03a00000-0x07a00000 : "data1"
0x07a00000-0x08000000 : "data2"
nand_davinci nand_davinci.0: hardware revision: 2.3
musb_hdrc: version 6.0/dbg, pio, host, debug=1
musb_hdrc: USB Host mode controller at c88e6000 using PIO, IRQ 12
musb_hdrc musb_hdrc: MUSB HDRC host driver
musb_hdrc musb_hdrc: new USB bus registered, assigned bus number 1
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 1 port detected
[drivers/rtc/rtc-pcf8563.c:pcf8563_probe:288]kind(-1) return
pcf8563 0-0051: chip found, driver version 0.4.2
pcf8563 0-0051: rtc intf: proc
pcf8563 0-0051: rtc intf: dev (254:0)
pcf8563 0-0051: rtc core: registered pcf8563 as rtc0
davinci-mmc davinci-mmc.0: Supporting 4-bit mode
davinci-mmc davinci-mmc.0: Using DMA mode
Advanced Linux Sound Architecture Driver Version 1.0.12rc1 (Thu Jun 22 13:55:50 2006 UTC).
>>>[mmc_setup:1426] power_mode:MMC_POWER_OFF[0]
ASoC version 0.13.1
MUX: initialized MCBSP_BDX
MUX: initialized MCBSP_X
MUX: initialized MCBSP_BFSX
MUX: initialized MCBSP_BDR
MUX: initialized MCBSP_R
MUX: initialized MCBSP_BFSR
wm8960: WM8960 Audio Codec 0.2
asoc: WM8960 <-> davinci-i2s mapping ok
mmcblk0: mmc0:0007 SD64G 61882368KiB
 mmcblk0: p1
ALSA device list:
  #0: DaVinci DM365 WM8960 (WM8960)
IPv4 over IPv4 tunneling driver
GRE over IPv4 tunneling driver
Initializing XFRM netlink socket
NET: Registered protocol family 1
NET: Registered protocol family 17
NET: Registered protocol family 15
ieee80211: 802.11 data/management/control stack, git-1.1.13
ieee80211: Copyright (C) 2004-2005 Intel Corporation <jketreno@linux.intel.com>
Time: timer0_1 clocksource has been installed.
Clock event device timer0_0 configured with caps set: 08
Switched to high resolution mode on CPU 0
pcf8563 0-0051: low voltage detected, date/time is not reliable.
pcf8563 0-0051: setting the system clock to 2010-01-11 01:54:46 (1263174886)
VFS: Mounted root (cramfs filesystem) readonly.
Freeing init memory: 184K
INIT: version 2.86 booting
0
mkdir: can't create directory '/dev/.test': Read-only file system
Done /etc/rc.d/rcS.d/S03mountvirtfs..
Starting the hotplug events dispatcher: udevd.
Synthesizing the initial hotplug events...done.
Waiting for /dev to be fully populated...done.
Done /etc/rc.d/rcS.d/S04udev..
Starting Dropbear SSH server: dropbear.
Done /etc/rc.d/rcS.d/S36dropbear..
Done /etc/rc.d/rcS.d/S41portmap..
###############################################
###############################################
### application start...                 ######
###############################################
###############################################
/dev/mmcblk0p1 mount....
Mount patch area at nand flash...
yaffs: dev is 32505860 name is "mtdblock4"
yaffs: passed flags ""
yaffs: Attempting MTD mount on 31.4, "mtdblock4"
yaffs tragedy: Bad object type, -78143499 != 11, for object 129994303 at chunk 4990 during scan
yaffs tragedy: Bad object type, -201344003 != 7, for object 228585082 at chunk 4989 during scan
yaffs tragedy: Bad object type, 2147450878 != 1, for object 237862910 at chunk 4988 during scan
mount: wrong fs type, bad option, bad superblock on /dev/mtdblock4,
       missing codepage or other error
       In some cases useful info is found in syslog - try
       dmesg | tail  or so

CSL: Module install successful, device major num = 253
CSL: Module version 0.10.00, built on Mar 13 2014 17:15:34
I2C: Module install successful, device major num = 252
DMA: Module install successful, device major num = 251
DRV: Module install successful
DRV: Module built on Mar 13 2014 17:15:36
DRV: EDMACC.QUEPRI  = 00000777
DRV: SYSTEM.MSTPRI0 = 00440022
DRV: SYSTEM.MSTPRI1 = 00000244
DRV: ISP.BCR        = 00000002
DRV: SYSTEM.MISC    = 00000319
CMEMK module: built on Mar 27 2013 at 18:15:50
  Reference Linux version 2.6.18
  File /home/sejung/project/DR500/dvsdk_2_10_01_18/linuxutils_2_24_03/packages/ti/sdo/linuxutils/cmem/src/module/cmemk.c
allocated heap buffer 0xc9000000 of size 0x8000000
CMEM Range Overlaps Kernel Physical - allowing overlap
CMEM phys_start (0x1000) overlaps kernel (0x80000000 -> 0x88000000)
cmemk initialized
EDMAK module: built on Mar 27 2013 at 18:15:52
  Reference Linux version 2.6.18
  File /home/sejung/project/DR500/dvsdk_2_10_01_18/linuxutils_2_24_03/packages/ti/sdo/linuxutils/edma/src/module/edmak.c
IRQK module: built on Mar 27 2013 at 18:15:53
  Reference Linux version 2.6.18
  File /home/sejung/project/DR500/dvsdk_2_10_01_18/linuxutils_2_24_03/packages/ti/sdo/linuxutils/irq/src/module/irqk.c
irqk initialized
[JC:82] CSL_gpioSet[flag:1]
wlan0 waitting... 1/5 sec.
usb 1-1: new high speed USB device using musb_hdrc and address 2
usb 1-1: configuration #1 chosen from 1 choice
CHIP TYPE: RTL8188C_8192C

usb_endpoint_descriptor(0):
bLength=7
bDescriptorType=5
bEndpointAddress=81
wMaxPacketSize=200
bInterval=0
RT_usb_endpoint_is_bulk_in = 1

usb_endpoint_descriptor(1):
bLength=7
bDescriptorType=5
bEndpointAddress=2
wMaxPacketSize=200
bInterval=0
RT_usb_endpoint_is_bulk_out = 2

usb_endpoint_descriptor(2):
bLength=7
bDescriptorType=5
bEndpointAddress=3
wMaxPacketSize=200
bInterval=0
RT_usb_endpoint_is_bulk_out = 3

usb_endpoint_descriptor(3):
bLength=7
bDescriptorType=5
bEndpointAddress=84
wMaxPacketSize=40
bInterval=1
RT_usb_endpoint_is_int_in = 4, Interval = 1
nr_endpoint=4, in_num=2, out_num=2

USB_SPEED_HIGH
Chip Version ID: VERSION_NORMAL_TSMC_CHIP_88C.
RF_Type is 3!!
EEPROM type is E-FUSE
====> ReadAdapterInfo8192C
Boot from EFUSE, Autoload OK !
EEPROMVID = 0x0bda
EEPROMPID = 0x8176
EEPROMCustomerID : 0x00
EEPROMSubCustomerID: 0x00
RT_CustomerID: 0x00
_ReadMACAddress MAC Address from EFUSE = 00:25:42:e0:86:a1
EEPROMRegulatory = 0x0
_ReadBoardType(0)
BT Coexistance = disable
RT_ChannelPlan: 0x0a
_ReadPSSetting...bHWPwrPindetect(0)-bHWPowerdown(0) ,bSupportRemoteWakeup(0)
### PS params=>  power_mgnt(0),usbss_enable(0) ###
### AntDivCfg(0)
readAdapterInfo_8192CU(): REPLACEMENT = 1
<==== ReadAdapterInfo8192C in 110 ms
rtw_macaddr_cfg MAC Address  = 00:25:42:e0:86:a1
MAC Address from pnetdev->dev_addr= 00:25:42:e0:86:a1
bDriverStopped:1, bSurpriseRemoved:0, bup:0, hw_init_completed:0
+871x_drv - drv_open, bup=0
wlan found..1/5 sec..==> [ wlan0     Link encap: ===> FirmwareDownload91C() fw:Rtl819XFwImageArray_TSMC
Ethernet  HWaddrFirmwareDownload92C accquire FW from embedded image
 00:25:42:E0:86:fw_ver=v80, fw_subver=0, sig=0x88c0
A1   ]
fw download ok!
Set RF Chip ID to RF_6052 and RF type to 1T1R.
IQK:Start!!!
Path A IQK Success!!
Path A IQK Success!!
IQK: final_candidate is 0
IQK: RegE94=100 RegE9C=b RegEA4=fe RegEAC=2 RegEB4=0 RegEBC=0 RegEC4=0 RegECC=0
 Path A IQ Calibration Success !
pdmpriv->TxPowerTrackControl = 1
MAC Address from REG_MACID = 00:25:42:e0:86:a1
rtl8192cu_hal_init in 540ms
MAC Address = 00:25:42:e0:86:a1
-871x_drv - drv_open, bup=1
wlan up!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
survey done event(16)
wlan scanning..!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
best channel copying...!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
nand app not exists...
Factory Upgrade Starting...
Running new_upgrade!!
killall: telnetd: no process killed
killall: inetd: no process killed

• /mnt/mmc/BlackVue/System/new_upgrade [1]system_start
[JC:led_set:639] LED_ALL_OFF
#### I am called by system_start!!! :-) JCH.
Simple mixer control 'Left PCM',0
  Capabilities: pswitch
  Playback channels: Front Left - Front Right
  Mono:
  Front Left: Playback

[on]
  Front Right: Playback [on]
>>>>>>>>>>>>>>>>>>[new_upgrade:main:1357] START<<<<<<<<<<<<<<<<<<<<
cp: can't stat '/mnt/mmc/BlackVue/System/model_info_different.wav': No such file or directory
NAND filesystem : /mnt/mmc/BlackVue/System/model_info_different.wav
Kernel not have yaffs2 filesystems upgrade plz...
sue OK /mnt/mmc/BlackVue/System/upgrade/patch_DR500GW.bin:/mnt/mmc/BlackVue/System/upgrade/patch_DR500GW.sue
▒▒ġ▒▒▒▒ ▒▒׷▒▒̵▒ ▒▒▒▒ but!! kernel/rootfs upgrade plz..[/mnt/mmc/BlackVue/System/upgrade/patch_DR500GW.bin]
sue OK /mnt/mmc/BlackVue/System/upgrade/uImage_DR500GW:/mnt/mmc/BlackVue/System/upgrade/uImage_DR500GW.sue
Ŀ▒▒ ▒▒׷▒▒̵▒ ▒▒▒▒..ok [/mnt/mmc/BlackVue/System/upgrade/uImage_DR500GW]
sue OK /mnt/mmc/BlackVue/System/upgrade/cramfsImage_DR500GW:/mnt/mmc/BlackVue/System/upgrade/cramfsImage_DR500GW.sue
▒▒Ʈ▒▒▒Ͻý▒▒▒ ▒▒׷▒▒̵▒ ▒▒▒▒..ok [/mnt/mmc/BlackVue/System/upgrade/cramfsImage_DR500GW]
[main:1523]img_ok:6, patch_ok:0
[get_version_info:781]app_version:[2.002]
[get_version_info:785]app_model:[500GW]
[get_version_info:789]app_language:[English]
[get_version_info:796]cli_version:[2.220]
[get_version_info:800]cli_model:[500GW]
[get_version_info:804]cli_language:[English]
[get_version_info:811]cfg_version:[1.040]
[get_version_info:815]cfg_model:[500GW]
[get_version_info:819]/mnt/mmc/BlackVue/Config/version.bin read End
INIT: Entering runlevel: 3
Starting telnet daemon.
Starting INET services: done.
Starting syslogd/klogd: done

MontaVista(R) Linux(R) Professional Edition 5.0.0 (0702774)

localhost login:

Название: Re: DR500GW-HD self bricked?
Отправлено: neoncek от 21 Декабря 2014, 02:03:52

Did I do any wrong step?
I am not sure about following:
DR500GW-HD>loadb 0x82000000
DR500GW-HD>nand erase 0xa00000 0xdd0000
DR500GW-HD>nand write 0x82000000 0xa00000 0xdd0000

Any advice please?  ))O((

Название: Re: DR500GW-HD self bricked?
Отправлено: neoncek от 28 Декабря 2014, 16:13:48

 |O I have my hands tied, I don`t want to brick my dashcam... ideas pleeease?

Название: Re: DR500GW-HD self bricked?
Отправлено: MiO_970 от 28 Декабря 2014, 22:12:40

(кликните для показа/скрытия)

1. The need to run a terminal program that allows you to upload files via Serial protocol Kermit (eg, ZOC or Microsoft HyperTerm).

1.1 Run the registrar at the beginning of hold down "d" - and enter the boot command line.

================================================== ========
2. Restore the root filesystem
================================================== ========

1) Shipping filesystem in memory registrar protocol KERMIT:

To do this, the boot command line typed the following command

loadb 0x82000000

immediately afterwards in the menu file transfer terminal program elects to Kermit protocol and file in the root file system "cramfsImage_DR500GW"

begins loading the file in the recorder. We are waiting for from 30 minutes to 1.5 hours (if ship via HyperTerm).

2) If the preceding paragraph is completed successfully, then type in the boot command line command

nand erase 0xa00000 0xdd0000

3); Ideas command at the boot loader command to write the file system of the NAND flash memory in the logger

nand write 0x82000000 0xa00000 0xdd0000

================================================== ========
3. Restore partition with application software
================================================== ========

0) to SD-card in the root file write patch_DR500GW.bin
1) Reboot the registrar. We go through the UART terminal program and the operating sictemu
superuser (login: root, password: pt)

2) on the command line to submit the following commands in sequence:

           cd /
           mount -t vfat / dev / mmcblk0p1 / mnt / mmc
   or if does not work, you have to dial
           mount -t vfat / dev / mmcblk0 / mnt / mmc
   further
           rm -rf / mnt / nand / *
           tar -xvzf /mnt/mmc/patch_DR500GW.bin -C /
           sync

Restarting the recorder.

Everything !!!

Название: Re: DR500GW-HD self bricked?
Отправлено: neoncek от 30 Декабря 2014, 19:52:39

it gives me an error:

# cd /
# mount -t vfat /dev/mmcblk0
mmcblk0    mmcblk0p1
# mount -t vfat /dev/mmcblk0p1 /mnt/mmc/
mount: /dev/mmcblk0p1 already mounted or /mnt/mmc/ busy
mount: according to mtab, /dev/mmcblk0p1 is mounted on /mnt/mmc
# mount -t vfat /dev/mmcblk0 /mnt/mmc/
mount: /dev/mmcblk0 already mounted or /mnt/mmc/ busy
# rm -rf /mnt/nand/*
# tar -xvzf /mnt/mmc/patch_DR500GW.bin -C /
mnt/
mnt/nand/
mnt/nand/default/
tar: can't make dir mnt/nand/default: Read-only file system
mnt/nand/default/config_chn/
tar: can't create directory 'mnt/nand/default': Read-only file system
tar: can't make dir mnt/nand/default/config_chn: No such file or directory
mnt/nand/default/config_chn/config.ini
tar: can't create directory 'mnt/nand/default/': Read-only file system
tar: can't open 'mnt/nand/default/': Is a directory
# sync

 ..--..

After I send a file via HyperTerminal, it gives me this output:
## Total Size      = 0x00b99000 = 12161024 Bytes
## Start Addr      = 0x82000000
DR500GW-HD>
I just cannot do anything with /mnt/nand as it is read-only filesystem

Название: Re: DR500GW-HD self bricked?
Отправлено: MiO_970 от 30 Декабря 2014, 21:56:09

error

Сообщение от neoncek

tar: can't make dir mnt/nand/default: Read-only file system
mnt/nand/default/config_chn/
tar: can't create directory 'mnt/nand/default': Read-only file system
tar: can't make dir mnt/nand/default/config_chn: No such file or directory
mnt/nand/default/config_chn/config.ini
tar: can't create directory 'mnt/nand/default/': Read-only file system
tar: can't open 'mnt/nand/default/': Is a directory

Try this

(кликните для показа/скрытия)

Код: [Выделить]

cd /
umount /mnt/nand
/usr/sbin/flash_eraseall    /dev/mtd4
mount  -t  yaffs2  /dev/mtdblock4  /mnt/nand

tar -xvzf  /mnt/mmc/patch_DR500GW.bin -C /

Название: Re: DR500GW-HD self bricked?
Отправлено: neoncek от 31 Декабря 2014, 00:52:07

I have got it done!!! uff, finally, thank you very much!!!
 o)(o o)(o o)(o o)(o o)(o

...now I am going to lookup for some donate button...

(кликните для показа/скрытия)

1. The need to run a terminal program that allows you to upload files via Serial protocol Kermit (eg, ZOC or Microsoft HyperTerm).

1.1 Run the registrar at the beginning of hold down "d" - and enter the boot command line.

================================================== ========
2. Restore the root filesystem
================================================== ========

1) Shipping filesystem in memory registrar protocol KERMIT:

To do this, the boot command line typed the following command

loadb 0x82000000

immediately afterwards in the menu file transfer terminal program elects to Kermit protocol and file in the root file system "cramfsImage_DR500GW"

begins loading the file in the recorder. We are waiting for from 30 minutes to 1.5 hours (if ship via HyperTerm).

2) If the preceding paragraph is completed successfully, then type in the boot command line command

nand erase 0xa00000 0xdd0000

3); Ideas command at the boot loader command to write the file system of the NAND flash memory in the logger

nand write 0x82000000 0xa00000 0xdd0000

================================================== ========
3. Restore partition with application software
================================================== ========

0) to SD-card in the root file write patch_DR500GW.bin
1) Reboot the registrar. We go through the UART terminal program and the operating sictemu
superuser (login: root, password: pt)

2) on the command line to submit the following commands in sequence:

2.A)
           cd /
           mount -t vfat / dev / mmcblk0p1 / mnt / mmc
   or if does not work, you have to dial
           mount -t vfat / dev / mmcblk0 / mnt / mmc
   further
           rm -rf / mnt / nand / *
           tar -xvzf /mnt/mmc/patch_DR500GW.bin -C /
           sync
2.B)
cd /
umount /mnt/nand
/usr/sbin/flash_eraseall    /dev/mtd4
mount  -t  yaffs2  /dev/mtdblock4  /mnt/nand
tar -xvzf  /mnt/mmc/patch_DR500GW.bin -C /
sync

Restarting the recorder.

Everything !!!

...DONATE done...
You can assign this topic as RESOLVED, thanks again!!!

Название: Re: DR500GW-HD self bricked?
Отправлено: MiO_970 от 31 Декабря 2014, 09:23:45

 0)))

Название: Re: DR500GW-HD self bricked?
Отправлено: netbootdisk от 05 Февраля 2015, 06:42:12

Hello from Australia!

I also had my Blackvue self-brick, with it booting to the Korean "upgrade failed" error message. I think it bricked after the Blackvue was powered off whilst it was still originally booting up & it corrupted itself. (I only moved my car from driveway to garage)

Thanks to your instructions I've now fixed my dashcam!!! )ooo(

I had a little trouble with translations & following the instructions/process above, so below is the consolidated steps which fixed my unit...

1. Connect serial console to computer at 115200/8/N & no flow control.
2. Power on Blackvue, boot status should appear
3. Soon after powering on (or resetting), press the 'd' key to enter the boot loader config.
---Restore Root File System---
4. At the boot prompt type: loadb 0x82000000
5. Then immediately use your terminal program to KERMIT send the cramfsImage_DR500GW file from the BlackVue\System\upgrade folder within the firmware download ZIP. (I used Terra-Term, File Menu > Transfer > Send > Kermit command. It took hours!)
6. The terminal should then say that the transfer was OK
7. At the boot prompt type: nand erase 0xa00000 0xdd0000
8. Then to "write the file system of the NAND flash memory", type: nand write 0x82000000 0xa00000 0xdd0000

---Restore system software---
9. Copy patch_DR500GW.bin file to root of SD card & Reboot the Blackvue
10. Blackvue will boot up - and in my case still got stuck looping the korean 'upgrade failed' error message. Press CONTROL+C
11. Login as username = root & password = pt
12. Enter these commands... (I *think* this is what worked for me, I had some confusion with the original forum thread with these instructions; see http://car-dvr.info/forum/index.php?topic=801.0 (http://car-dvr.info/forum/index.php?topic=801.0) for clarification
# cd /
# mount -t vfat /dev/mmcblk0
# umount /mnt/nand
# /usr/sbin/flash_eraseall    /dev/mtd4
# mount  -t  yaffs2  /dev/mtdblock4  /mnt/nand
# tar -xvzf  /mnt/mmc/patch_DR500GW.bin -C /
# sync
# reboot
13. The Blackvue should then boot 'normally' again and reformat the SD card!

Hopefully that helps others out as I thought mine was dead until I found this info :D

Название: Re: DR500GW-HD self bricked?
Отправлено: JohnnyBravo от 12 Февраля 2015, 19:41:32

Hi!

I have a similar problem with my camera.
I looks like the firmware is corrupted and it doesn't boot.
When I plug it in, all the LEDs light up, except the blue GPS LED, and all stay lit. No blinking.
When I unplug it, all goes out.
No voice messages.

In the link below, you can find a short film with the camera.
What do you think, is it software related or hardware?

I've tried re-installing the firmware with no result.
Also tried with another SD card and without any card. Nothing happened.

[youtube]9nm8T9FGz3Q[/youtube]

Would that UART interface help?

Thank you!

Название: Re: DR500GW-HD self bricked?
Отправлено: MiO_970 от 17 Февраля 2015, 15:02:20

enable them without SD
Write that will be

Название: Re: DR500GW-HD self bricked?
Отправлено: JohnnyBravo от 17 Февраля 2015, 20:37:35

I have tried without the SD card. The same thing happens.

Название: Re: DR500GW-HD self bricked?
Отправлено: JohnnyBravo от 19 Февраля 2015, 18:07:45

I have this UART cable.
(http://s7.postimg.org/lsupoh80r/20150217_231833.jpg) (https://car-dvr.info/forum/go.php?url=aHR0cDovL3Bvc3RpbWFnZS5vcmcv)

How can I use it to reprogram the camera?
Where do I have to connect it?

I see there is a 3 pin connector on one board and a ribbon connector on the other. Which is the right connector for reprogramming?

(http://s2.postimg.org/faye82nzt/20150217_231700.jpg) (https://car-dvr.info/forum/go.php?url=aHR0cDovL3Bvc3RpbWFnZS5vcmcv)
(http://s12.postimg.org/6tf4lmlzh/20150217_231714.jpg) (https://car-dvr.info/forum/go.php?url=aHR0cDovL3Bvc3RpbWFnZS5vcmcv)


Thank you!

Название: Re: DR500GW-HD self bricked?
Отправлено: DenisSharifulin от 19 Февраля 2015, 18:28:33

JohnnyBravo,
(http://car-dvr.info/forum/public/media/ScreenShooter/BBWSV8.png)

TX -> connect to PC RX
RX -> connect to PC TX
GND -> connect to PC GND
Параметры порта 115200/8n1

(http://car-dvr.info/forum/public/media/ScreenShooter/BBGGAI.png)

Название: Re: DR500GW-HD self bricked?
Отправлено: negon от 05 Октября 2015, 01:05:15

Would the procedure above work on a DR550GW-2ch? If not can anybody help me on a procedure to unbrick my dashcam. Thanks.

Название: Re: DR500GW-HD self bricked?
Отправлено: DenisSharifulin от 05 Октября 2015, 13:47:58

negon, What's wrong with your dashcam.

Название: Re: DR500GW-HD self bricked?
Отправлено: negon от 05 Октября 2015, 17:11:54

Сообщение от DenisSharifulin

negon, What's wrong with your dashcam.

I think I bricked my DR550gw-2ch.
First i have ulgraded the FW to the latest korean FW 2.010. I have put the upload folder on the root directory of the sd card and upgrade cgi on the config folder. The blackvue changed to english but it says that the version information is different so I tried to return it back to 2.010 korean FW. It changed back to speaking korean and it seems that it is still saying that the version information is different. Hope that someone can help me.

Название: Re: DR500GW-HD self bricked?
Отправлено: negon от 07 Октября 2015, 04:58:56

Can I use this UART? http://www.lazada.com.ph/usb-20-to-uart-ttl-6pin-connector-module-serial-converter-cp2012-1466915.html

Название: Re: DR500GW-HD self bricked?
Отправлено: DenisSharifulin от 07 Октября 2015, 14:35:03

negon, Yes
http://car-dvr.info/forum/index.php?topic=317.0

Название: Re: DR500GW-HD self bricked?
Отправлено: negon от 08 Октября 2015, 04:46:17

Thank you very much for the response. I do have another question, is the procedure outlined in the link specifically for PC or would it work on a mac? thanks again.

Название: Re: DR500GW-HD self bricked?
Отправлено: DenisSharifulin от 08 Октября 2015, 08:19:26

PC

Название: Re: DR500GW-HD self bricked?
Отправлено: Saj от 20 Декабря 2020, 19:58:55

neoncek, hi hope you are well. I have bricked my blackvue and come across your instructions etc, which UART cable did you get?