Si4

Up ! Please

Good evening everyone, it restarts continuously. Any Ideas ? NAND read: device 0 offset 0xc80000, size 0x00580000 5767168 bytes read: OK ## Booting kernel from Legacy Image at c2000000 ... Image Name: Linux-2.6.38.8 Created: 2014-12-05 7:39:45 UTC Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 2546892 Bytes = 2.4 MiB Load Address: c0208000 Entry Point: c0208000 Verifying Checksum ... OK Loading Kernel Image ...OK OK Starting kernel ... Linux version 2.6.38.8 (jenkins@jenkins127) (gcc version 4.6.1 (Sourcery CodeBench Lite 2011.09-70) ) #1 PREEMPT Fri Dec 5 15:39:42 CST 2014 CPU: ARMv6-compatible processor [4117b365] revision 5 (ARMv6TEJ), cr=00c5387f CPU: VIPT nonaliasing data cache, VIPT nonaliasing instruction cache Machine: Coconut appauto=0 dh_keyboard=0 ethaddr0=4c:11:bf:cd:0:2d ethaddr1=0:0:0:0:0:0 lip0=192.168.1.108 lip1=0.0.0.0 id=1G010A9PAU00397 U-Boot 0x100000 0x200000 0x0 hwid 0x100000 0x300000 0x0 updateflag 0x100000 0x400000 0x0 partition 0x100000 0x500000 0x0 custom 0x340000 0x600000 0x0 product 0x340000 0x940000 0x0 Kernel 0x580000 0xc80000 0x0 romfs 0x800000 0x1200000 0x0 web 0x800000 0x1a00000 0x0 user 0x1980000 0x2200000 0x0 syslog 0x400000 0x7200000 0x0 config 0x400000 0x7600000 0x0 backup 0x400000 0x7a00000 0x0 gLogRamRes: start=0xc837e000;size=0x80000 mem_relimitAddr:0xc83fe000 init gLogRamRes: start=0xc837e000;size=0x80000 init mem_relimitAddr:0xc83fe000 Memory policy: ECC disabled, Data cache writeback Ambarella: AHB = 0x60000000[0xf0000000],0x01000000 0 Ambarella: APB = 0x70000000[0xf1000000],0x01000000 0 Ambarella: PPM = 0xc0000000[0xe0000000],0x00200000 9 Ambarella: BSB = 0xc8400000[0xe8400000],0x00400000 9 Ambarella: DSP = 0xc8800000[0xe8800000],0x07800000 9 Ambarella: HAL = 0xc00a0000[0xfee00000],0x0000e708 9 bootmem_init: high_memory = 0xc8200000 Built 1 zonelists in Zone order, mobility grouping on. Total pages: 33020 Kernel command line: console=ttyS0 ubi.mtd=romfs root=ubi0:romfs ro rootfstype=ubifs init=/linuxrc video=amb0fb:720x480,720x480,1,0 lpj=2392064 mem=130M PID hash table entries: 1024 (order: 0, 4096 bytes) Dentry cache hash table entries: 32768 (order: 5, 131072 bytes) Inode-cache hash table entries: 16384 (order: 4, 65536 bytes) Memory: 130MB = 130MB total Memory: 126388k/126388k available, 6732k reserved, 0K highmem Virtual kernel memory layout: vector : 0xffff0000 - 0xffff1000 ( 4 kB) fixmap : 0xfff00000 - 0xfffe0000 ( 896 kB) DMA : 0xfe600000 - 0xfee00000 ( 8 MB) vmalloc : 0xc8800000 - 0xe0000000 ( 376 MB) lowmem : 0xc0000000 - 0xc8200000 ( 130 MB) modules : 0xbf000000 - 0xc0000000 ( 16 MB) .init : 0xc0008000 - 0xc002c000 ( 144 kB) .text : 0xc002c000 - 0xc0483000 (4444 kB) .data : 0xc0484000 - 0xc04ac750 ( 162 kB) Preemptable hierarchical RCU implementation. RCU-based detection of stalled CPUs is disabled. Verbose stalled-CPUs detection is disabled. NR_IRQS:224 Console: colour dummy device 80x30 console [ttyS0] enabled Calibrating delay loop (skipped) preset value.. 478.41 BogoMIPS (lpj=2392064) pid_max: default: 32768 minimum: 301 Mount-cache hash table entries: 512 CPU: Testing write buffer coherency: ok devtmpfs: initialized NET: Registered protocol family 16 Ambarella Coconut: chip id: 5100 board type: 3 board revision: 10 chip name: a5m HAL version: 207871 reference clock: 24000000 system configuration: 0x043804ea boot type: 0x00000002 hif type: 0x00000000 bio: create slab at 0 NET: Registered protocol family 2 IP route cache hash table entries: 2048 (order: 1, 8192 bytes) TCP established hash table entries: 8192 (order: 4, 65536 bytes) TCP bind hash table entries: 8192 (order: 3, 32768 bytes) TCP: Hash tables configured (established 8192 bind 8192) TCP reno registered UDP hash table entries: 256 (order: 0, 4096 bytes) UDP-Lite hash table entries: 256 (order: 0, 4096 bytes) NET: Registered protocol family 1 RPC: Registered udp transport module. RPC: Registered tcp transport module. RPC: Registered tcp NFSv4.1 backchannel transport module. JFFS2 version 2.2. (NAND) © 2001-2006 Red Hat, Inc. msgmni has been set to 246 io scheduler noop registered io scheduler deadline registered (default) io scheduler cfq registered [serial_ambarella_probe]:700--devId:0;keyboard:0;Console:0;nr:2;total:2 ambarella-uart.0: ttyS0 at MMIO 0x70005000 (irq = 9) is a ambuart [serial_ambarella_probe]:700--devId:1;keyboard:0;Console:0;nr:2;total:2 brd: module loaded loop: module loaded NAND device: Manufacturer ID: 0x92, Chip ID: 0xf1 (Unknown NAND 128MiB 3,3V 8-bit) ambarella_nand_config_flash: 0x00000000, 0x02c00140 Scanning device for bad blocks Creating 13 MTD partitions on "ambnand": 0x000000200000-0x000000300000 : "U-Boot" 0x000000300000-0x000000400000 : "hwid" 0x000000400000-0x000000500000 : "updateflag" 0x000000500000-0x000000600000 : "partition" 0x000000600000-0x000000940000 : "custom" 0x000000940000-0x000000c80000 : "product" 0x000000c80000-0x000001200000 : "Kernel" 0x000001200000-0x000001a00000 : "romfs" 0x000001a00000-0x000002200000 : "web" 0x000002200000-0x000003b80000 : "user" 0x000007200000-0x000007600000 : "syslog" 0x000007600000-0x000007a00000 : "config" 0x000007a00000-0x000007e00000 : "backup" UBI: attaching mtd7 to ubi0 UBI: physical eraseblock size: 131072 bytes (128 KiB) UBI: logical eraseblock size: 129024 bytes UBI: smallest flash I/O unit: 2048 UBI: sub-page size: 512 UBI: VID header offset: 512 (aligned 512) UBI: data offset: 2048 UBI: max. sequence number: 2 UBI: attached mtd7 to ubi0 UBI: MTD device name: "romfs" UBI: MTD device size: 8 MiB UBI: number of good PEBs: 64 UBI: number of bad PEBs: 0 UBI: number of corrupted PEBs: 0 UBI: max. allowed volumes: 128 UBI: wear-leveling threshold: 4096 UBI: number of internal volumes: 1 UBI: number of user volumes: 1 UBI: available PEBs: 0 UBI: total number of reserved PEBs: 64 UBI: number of PEBs reserved for bad PEB handling: 2 UBI: max/mean erase counter: 1/0 UBI: image sequence number: 1792439432 UBI: background thread "ubi_bgt0d" started, PID 679 PPP generic driver version 2.4.2 NET: Registered protocol family 24 tun: Universal TUN/TAP device driver, 1.6 tun: © 1999-2004 Max Krasnyansky console [netcon0] enabled netconsole: network logging started mousedev: PS/2 mouse device common for all mice TCP bic registered NET: Registered protocol family 10 IPv6 over IPv4 tunneling driver NET: Registered protocol family 17 drivers/rtc/hctosys.c: unable to open rtc device (rtc0) UBIFS: mounted UBI device 0, volume 0, name "romfs" UBIFS: mounted read-only UBIFS: file system size: 6193152 bytes (6048 KiB, 5 MiB, 48 LEBs) UBIFS: journal size: 1419264 bytes (1386 KiB, 1 MiB, 11 LEBs) UBIFS: media format: w4/r0 (latest is w4/r0) UBIFS: default compressor: zlib UBIFS: reserved for root: 0 bytes (0 KiB) VFS: Mounted root (ubifs filesystem) readonly on device 0:15. devtmpfs: mounted Freeing init memory: 144K UBI: attaching mtd9 to ubi1 UBI: physical eraseblock size: 131072 bytes (128 KiB) UBI: logical eraseblock size: 129024 bytes UBI: smallest flash I/O unit: 2048 UBI: sub-page size: 512 UBI: VID header offset: 512 (aligned 512) UBI: data offset: 2048 UBI: max. sequence number: 6 UBI: attached mtd9 to ubi1 UBI: MTD device name: "user" UBI: MTD device size: 25 MiB UBI: number of good PEBs: 204 UBI: number of bad PEBs: 0 UBI: number of corrupted PEBs: 0 UBI: max. allowed volumes: 128 UBI: wear-leveling threshold: 4096 UBI: number of internal volumes: 1 UBI: number of user volumes: 1 UBI: available PEBs: 0 UBI: total number of reserved PEBs: 204 UBI: number of PEBs reserved for bad PEB handling: 2 UBI: max/mean erase counter: 2/0 UBI: image sequence number: 1757773083 UBI: background thread "ubi_bgt1d" started, PID 727 UBI device number 1, total 204 LEBs (26320896 bytes, 25.1 MiB), available 0 LEBs (0 bytes), LEB size 129024 bytes (126.0 KiB) UBIFS: mounted UBI device 1, volume 0, name "user" UBIFS: mounted read-only UBIFS: file system size: 24256512 bytes (23688 KiB, 23 MiB, 188 LEBs) UBIFS: journal size: 3612672 bytes (3528 KiB, 3 MiB, 28 LEBs) UBIFS: media format: w4/r0 (latest is w4/r0) UBIFS: default compressor: zlib UBIFS: reserved for root: 0 bytes (0 KiB) UBI: attaching mtd4 to ubi2 UBI: physical eraseblock size: 131072 bytes (128 KiB) UBI: logical eraseblock size: 129024 bytes UBI: smallest flash I/O unit: 2048 UBI: sub-page size: 512 UBI: VID header offset: 512 (aligned 512) UBI: data offset: 2048 UBI: max. sequence number: 6 UBI: attached mtd4 to ubi2 UBI: MTD device name: "custom" UBI: MTD device size: 3 MiB UBI: number of good PEBs: 26 UBI: number of bad PEBs: 0 UBI: number of corrupted PEBs: 0 UBI: max. allowed volumes: 128 UBI: wear-leveling threshold: 4096 UBI: number of internal volumes: 1 UBI: number of user volumes: 1 UBI: available PEBs: 0 UBI: total number of reserved PEBs: 26 UBI: number of PEBs reserved for bad PEB handling: 2 UBI: max/mean erase counter: 2/0 UBI: image sequence number: 1339771508 UBI: background thread "ubi_bgt2d" started, PID 734 UBI device number 2, total 26 LEBs (3354624 bytes, 3.2 MiB), available 0 LEBs (0 bytes), LEB size 129024 bytes (126.0 KiB) UBIFS: mounted UBI device 2, volume 0, name "custom" UBIFS: mounted read-only UBIFS: file system size: 1548288 bytes (1512 KiB, 1 MiB, 12 LEBs) UBIFS: journal size: 903169 bytes (882 KiB, 0 MiB, 6 LEBs) UBIFS: media format: w4/r0 (latest is w4/r0) UBIFS: default compressor: zlib UBIFS: reserved for root: 0 bytes (0 KiB) UBI: attaching mtd5 to ubi3 UBI: physical eraseblock size: 131072 bytes (128 KiB) UBI: logical eraseblock size: 129024 bytes UBI: smallest flash I/O unit: 2048 UBI: sub-page size: 512 UBI: VID header offset: 512 (aligned 512) UBI: data offset: 2048 UBI: max. sequence number: 2 UBI: attached mtd5 to ubi3 UBI: MTD device name: "product" UBI: MTD device size: 3 MiB UBI: number of good PEBs: 26 UBI: number of bad PEBs: 0 UBI: number of corrupted PEBs: 0 UBI: max. allowed volumes: 128 UBI: wear-leveling threshold: 4096 UBI: number of internal volumes: 1 UBI: number of user volumes: 1 UBI: available PEBs: 0 UBI: total number of reserved PEBs: 26 UBI: number of PEBs reserved for bad PEB handling: 2 UBI: max/mean erase counter: 1/0 UBI: image sequence number: 1843318292 UBI: background thread "ubi_bgt3d" started, PID 741 UBI device number 3, total 26 LEBs (3354624 bytes, 3.2 MiB), available 0 LEBs (0 bytes), LEB size 129024 bytes (126.0 KiB) UBIFS: mounted UBI device 3, volume 0, name "pd" UBIFS: mounted read-only UBIFS: file system size: 1548288 bytes (1512 KiB, 1 MiB, 12 LEBs) UBIFS: journal size: 903169 bytes (882 KiB, 0 MiB, 6 LEBs) UBIFS: media format: w4/r0 (latest is w4/r0) UBIFS: default compressor: zlib UBIFS: reserved for root: 0 bytes (0 KiB) UBI: attaching mtd8 to ubi4 UBI: physical eraseblock size: 131072 bytes (128 KiB) UBI: logical eraseblock size: 129024 bytes UBI: smallest flash I/O unit: 2048 UBI: sub-page size: 512 UBI: VID header offset: 512 (aligned 512) UBI: data offset: 2048 UBI: max. sequence number: 2 UBI: attached mtd8 to ubi4 UBI: MTD device name: "web" UBI: MTD device size: 8 MiB UBI: number of good PEBs: 64 UBI: number of bad PEBs: 0 UBI: number of corrupted PEBs: 0 UBI: max. allowed volumes: 128 UBI: wear-leveling threshold: 4096 UBI: number of internal volumes: 1 UBI: number of user volumes: 1 UBI: available PEBs: 0 UBI: total number of reserved PEBs: 64 UBI: number of PEBs reserved for bad PEB handling: 2 UBI: max/mean erase counter: 1/0 UBI: image sequence number: 1061606274 UBI: background thread "ubi_bgt4d" started, PID 748 UBI device number 4, total 64 LEBs (8257536 bytes, 7.9 MiB), available 0 LEBs (0 bytes), LEB size 129024 bytes (126.0 KiB) UBIFS: mounted UBI device 4, volume 0, name "web" UBIFS: mounted read-only UBIFS: file system size: 6193152 bytes (6048 KiB, 5 MiB, 48 LEBs) UBIFS: journal size: 1419264 bytes (1386 KiB, 1 MiB, 11 LEBs) UBIFS: media format: w4/r0 (latest is w4/r0) UBIFS: default compressor: zlib UBIFS: reserved for root: 0 bytes (0 KiB) UBI: attaching mtd10 to ubi5 UBI: physical eraseblock size: 131072 bytes (128 KiB) UBI: logical eraseblock size: 129024 bytes UBI: smallest flash I/O unit: 2048 UBI: sub-page size: 512 UBI: VID header offset: 512 (aligned 512) UBI: data offset: 2048 UBI: max. sequence number: 4158 UBI: attached mtd10 to ubi5 UBI: MTD device name: "syslog" UBI: MTD device size: 4 MiB UBI: number of good PEBs: 32 UBI: number of bad PEBs: 0 UBI: number of corrupted PEBs: 0 UBI: max. allowed volumes: 128 UBI: wear-leveling threshold: 4096 UBI: number of internal volumes: 1 UBI: number of user volumes: 1 UBI: available PEBs: 6 UBI: total number of reserved PEBs: 26 UBI: number of PEBs reserved for bad PEB handling: 2 UBI: max/mean erase counter: 225/130 UBI: image sequence number: -1353015733 UBI: background thread "ubi_bgt5d" started, PID 755 UBI device number 5, total 32 LEBs (4128768 bytes, 3.9 MiB), available 6 LEBs (774144 bytes, 756.0 KiB), LEB size 129024 bytes (126.0 KiB) UBI error: ubi_create_volume: cannot create volume 1, error -17 ubimkvol: error!: cannot UBI create volume error 17 (File exists) UBIFS: recovery needed UBIFS: recovery completed UBIFS: mounted UBI device 5, volume 0, name "syslog" UBIFS: file system size: 1548288 bytes (1512 KiB, 1 MiB, 12 LEBs) UBIFS: journal size: 903169 bytes (882 KiB, 0 MiB, 5 LEBs) UBIFS: media format: w4/r0 (latest is w4/r0) UBIFS: default compressor: lzo UBIFS: reserved for root: 73129 bytes (71 KiB) UBI: attaching mtd11 to ubi6 UBI: physical eraseblock size: 131072 bytes (128 KiB) UBI: logical eraseblock size: 129024 bytes UBI: smallest flash I/O unit: 2048 UBI: sub-page size: 512 UBI: VID header offset: 512 (aligned 512) UBI: data offset: 2048 UBI: max. sequence number: 4786 UBI: attached mtd11 to ubi6 UBI: MTD device name: "config" UBI: MTD device size: 4 MiB UBI: number of good PEBs: 32 UBI: number of bad PEBs: 0 UBI: number of corrupted PEBs: 0 UBI: max. allowed volumes: 128 UBI: wear-leveling threshold: 4096 UBI: number of internal volumes: 1 UBI: number of user volumes: 1 UBI: available PEBs: 6 UBI: total number of reserved PEBs: 26 UBI: number of PEBs reserved for bad PEB handling: 2 UBI: max/mean erase counter: 192/150 UBI: image sequence number: -2049343821 UBI: background thread "ubi_bgt6d" started, PID 764 UBI device number 6, total 32 LEBs (4128768 bytes, 3.9 MiB), available 6 LEBs (774144 bytes, 756.0 KiB), LEB size 129024 bytes (126.0 KiB) UBI error: ubi_create_volume: cannot create volume 1, error -17 ubimkvol: error!: cannot UBI create volume error 17 (File exists) UBIFS: recovery needed UBIFS: recovery completed UBIFS: mounted UBI device 6, volume 0, name "config" UBIFS: file system size: 1548288 bytes (1512 KiB, 1 MiB, 12 LEBs) UBIFS: journal size: 903169 bytes (882 KiB, 0 MiB, 5 LEBs) UBIFS: media format: w4/r0 (latest is w4/r0) UBIFS: default compressor: lzo UBIFS: reserved for root: 73129 bytes (71 KiB) UBI: attaching mtd12 to ubi7 UBI: physical eraseblock size: 131072 bytes (128 KiB) UBI: logical eraseblock size: 129024 bytes UBI: smallest flash I/O unit: 2048 UBI: sub-page size: 512 UBI: VID header offset: 512 (aligned 512) UBI: data offset: 2048 UBI: max. sequence number: 4108 UBI: attached mtd12 to ubi7 UBI: MTD device name: "backup" UBI: MTD device size: 4 MiB UBI: number of good PEBs: 32 UBI: number of bad PEBs: 0 UBI: number of corrupted PEBs: 0 UBI: max. allowed volumes: 128 UBI: wear-leveling threshold: 4096 UBI: number of internal volumes: 1 UBI: number of user volumes: 1 UBI: available PEBs: 6 UBI: total number of reserved PEBs: 26 UBI: number of PEBs reserved for bad PEB handling: 2 UBI: max/mean erase counter: 191/128 UBI: image sequence number: -1069271739 UBI: background thread "ubi_bgt7d" started, PID 773 UBI device number 7, total 32 LEBs (4128768 bytes, 3.9 MiB), available 6 LEBs (774144 bytes, 756.0 KiB), LEB size 129024 bytes (126.0 KiB) UBI error: ubi_create_volume: cannot create volume 1, error -17 ubimkvol: error!: cannot UBI create volume error 17 (File exists) UBIFS: recovery needed UBIFS: recovery completed UBIFS: mounted UBI device 7, volume 0, name "backup" UBIFS: file system size: 1548288 bytes (1512 KiB, 1 MiB, 12 LEBs) UBIFS: journal size: 903169 bytes (882 KiB, 0 MiB, 5 LEBs) UBIFS: media format: w4/r0 (latest is w4/r0) UBIFS: default compressor: lzo UBIFS: reserved for root: 73129 bytes (71 KiB) [m [m[0;32;32m[OSA-DRV] OSA Build on Dec 5 2014 at 14:54:50. [m[0;32;32m[OSA-DRV] SVN NUM: 2560. [m[0;35m[OSA-DRV] Monitor Task pid=804 tid=804 [m[m [m[0;32;32m[LOG-DRV] LOG Build on Dec 5 2014 at 14:57:01. [m[0;32;32m[LOG-DRV] SVN NUM: 6090. [m[0;32;32m[LOG-DRV] ramStart:0xc837e000;ramSize:0x80000;select:1 [m[0;32;32m[OSA-DRV] Char device create OK ! [m[0;32;32m[LOG-DRV] coreId = 0, logLevel = 2 [m[0;32;32m[LOG-DRV] coreId = 1, logLevel = 2 [m[0;32;32m[LOG-DRV] coreId = 2, logLevel = 2 [m[0;32;32m[LOG-DRV] coreId = 3, logLevel = 2 [m[0;32;32m[LOG-DRV] coreId = 4, logLevel = 2 [m[0;32;32m[LOG-DRV] coreId = 5, logLevel = 2 [m[0;32;32m00:00:09|[binder] Binder.ko Build on Dec 5 2014 at 14:27:35. [m[0;32;32m00:00:09|[binder] SVN NUM: 1236. [m[0;32;32m00:00:09|[binder] NameServer Initial OK ! [m[0;32;32m00:00:09|[binder] Binder Initial OK ! [m[0;32;32m00:00:09|[OSA-DRV] Char device create OK ! [m[0;32;32m00:00:09|[binder] SR driver initial OK ! [m[0;32;32m00:00:09|[OSA-DRV] Char device create OK ! [m[0;32;32m00:00:09|[binder] NS driver initial OK ! [m[0;32;32m00:00:09|[OSA-DRV] Char device create OK ! [m[0;32;32m00:00:09|[binder] Binder driver initial OK ! [m[0;32;32m00:00:09|[sPF] SPF Build on Dec 5 2014 at 15:13:39. [m[0;32;32m00:00:09|[sPF] SVN NUM: 4486. [m[0;32;32m00:00:09|[sPF] SIL initial OK ! [m[0;32;32m00:00:09|[sPF] SPF initial ok ! [m[0;32;32m00:00:09|[OSA-DRV] Char device create OK ! [m[0;32;32m00:00:09|[sPF] SPF Proc Create OK!!! [m[0;32;32m00:00:09|[sPF] SPF driver initial ok ! [m[0;32;32m00:00:09|[prc] PRC Driver Build on Dec 5 2014 at 15:11:42. [m[0;32;32m00:00:09|[prc] SVN NUM: 3122. [m[0;32;32m00:00:09|[prc] Start to init module! [m[0;32;32m00:00:09|[sPF] Dai 2 register OK ! [m[0;32;32m00:00:09|[prc] Success to init module! [m[0;32;32m00:00:10|[pdc] PDC Build on Dec 5 2014 at 14:59:55. [m[0;32;32m00:00:10|[pdc] SVN NUM: 4916. [0;32;31m00:00:10|[prc] ERROR (/home/jenkins/jk_slave/workspace/IPC_DH3.S0507_IPCAmbarella2.420/tmp_build_dir/PRC_A5S/build/platbuild/../../src/module/submod/i2c/prc_i2c.c|I2C_isr|475): I2C0 dev0x68 wait ack timeout [m [m[0;36m00:00:10|[pdc] BASE_LINE: 240 [m[0;32;32m00:00:10|[pdc] OSA_kProcCreate OK [m[0;32;32m00:00:10|[OSA-DRV] Char device create OK ! [m[0;36m00:00:10|[pdc] PDC_PartionInit ok!! [m[0;32;32m00:00:10|[pdc] HWID : IPC-HFW4300S:01:02:02:1F:0A:00:01:00:00:00:00:210:00:00:02:00:00:00:00:00:100 [m[0;32;32m00:00:10|[OSA-DRV] Char device create OK ! [m[0;36m00:00:10|[pdc] binderFlag: 0x3, funcap: 0x18538b,0x0,0x0,0x0 [m[0;36m00:00:10|[pdc] SenCfg Match OK,pCfgParams->pCfg: bf10e734 [m[0;32;32m00:00:10|[pdc] Find Product: IPC-HFW4300S. [m[0;32;32m00:00:10|[pdc] Config size 2528 ! [m[0;36m00:00:10|[pdc] SenCfgSize: 212 Bytes [m[0;32;32m00:00:10|[pdc] Init spiBus1 Successed! [m[0;32;32m00:00:10|[pdc] Init I2CBus0 Successed! [m[0;32;32m00:00:10|[pdc] PDC_MODULE_RESET_STATE [m[0;32;32m00:00:10|[OSA-DRV] Char device create OK ! [m[0;36m00:00:10|[pdc] OSA_kProcAddFile:pdcIris OK! [m[0;32;32m00:00:10|[pdc] ircut types = [0] [m[0;32;32m00:00:10|[pdc] ircut types = [1] [m[0;32;32m00:00:10|[OSA-DRV] Char device create OK ! [m[1;37m00:00:10|[pdc] Dev has No shutDown Cfg! [m[0;36m00:00:10|[pdc] PDC_pinInit As Usual! [m[0;36m00:00:10|[pdc] Get reset pin: 7 OK ! [m[0;32;32m00:00:10|[pdc] Get comPort Cfg ok !0sa [m[0;32;32m00:00:10|[pdc] PDC_comInit OK! [m[0;32;32m00:00:10|[pdc] PDC_MODULE_SENSOR [m[0;36m00:00:10|[pdc] Try RtcDev:DS1338 [m[0;32;31m00:00:10|[prc] ERROR (/home/jenkins/jk_slave/workspace/IPC_DH3.S0507_IPCAmbarella2.420/tmp_build_dir/PRC_A5S/build/platbuild/../../src/module/submod/i2c/prc_i2c.c|I2C_socTransfer|1032): I2C0 dev0x68 wait ack timeout [m[0;32;31m00:00:10|[prc] ERROR (/home/jenkins/jk_slave/workspace/IPC_DH3.S0507_IPCAmbarella2.420/tmp_build_dir/PRC_A5S/build/platbuild/../../src/module/submod/i2c/prc_i2c.c|PRC_i2cTransfer|1106): I2C0 transfer fail! [m[0;32;31m00:00:10|[pdc] ERROR (DS_read|143): Fail to write [m[0;32;31m00:00:10|[pdc] ERROR (DS_enableRtc|364): Fail to read RTC register [m[0;32;31m00:00:10|[pdc] ERROR (DS_open|421): Fail to enable RTC [m[0;36m00:00:10|[pdc] Try RtcDev: SocRtc [m[1;33m00:00:10|[prc] WARN (/home/jenkins/jk_slave/workspace/IPC_DH3.S0507_IPCAmbarella2.420/tmp_build_dir/PRC_A5S/build/platbuild/../../src/module/submod/rtc/prc_rtc.c|PRC_rtcCreate|460): =====PRC_rtcCreate OK===== [m[0;32;32m00:00:10|[pdc] phyaddr = c83fe000, memLen = 2000 [m[0;32;32m00:00:10|[pdc] phyaddr = c83fe000, memLen = 2000 [m[0;32;32m00:00:10|[pdc] A B OK [m[0;32;32m00:00:10|[pdc] Both of Chief and Backup File CRC check OK! [m[0;32;32m00:00:10|[pdc] phyaddr = c83fe000, memLen = 2000 [m[0;32;32m00:00:10|[pdc] Both of Chief and Backup File CRC check OK! [m[0;32;32m00:00:10|[pdc] phyaddr = c83fe000, memLen = 2000 [m[0;36m00:00:10|[pdc] Choose RtcType: 4 -> SocRtc [m[0;32;32m00:00:10|[OSA-DRV] Char device create OK ! [m[0;36m00:00:10|[pdc] OSA_kProcAddFile:pdcRtc OK! [m[0;32;32m00:00:10|[pdc] Wifi init: powerGpioCfg = 54 [m[0;32;32m00:00:10|[pdc] irqGpioCfg = 75 [m[0;32;32m00:00:10|[pdc] powerGpioCfg = 65535 [m[0;32;32m00:00:10|[pdc] enGpio = 65535 [m[0;32;32m00:00:10|[pdc] intGpio = 6553[0;32;32m00:00:10|[pdc] SramFile_devRelease OK! [m5 [m[0;32;32m00:00:10|[pdc] hasWps = 0 [m[0;32;32m00:00:10|[pdc] wpsGpio = 65535 [m[0;32;32m00:00:10|[pdc] resetDefaultGpio = 7 [m[0;32;32m00:00:10|[pdc] wpsKeyLevel = 1 [m[1;37m00:00:10|[pdc] Dev has No shutDown Cfg! [m[0;36m00:00:10|[pdc] isWpsResetComm: 0 ! [m[0;32;32m00:00:10|[pdc] PDC_MODULE_WIFI [m[0;32;32m00:00:10|[pdc] smartIr light count:1 [m[0;32;32m00:00:10|[OSA-DRV] Char device create OK ! [m[0;36m00:00:10|[pdc] SmartIR init pwmId: 0,mode: 0,activeLevel: 1 [m[0;36m00:00:10|[pdc] OSA_kProcAddFile:pdcSmartIR OK! [m[0;32;32m00:00:10|[OSA-DRV] Char device create OK ! [m[0;32;32m00:00:10|[pdc] WDT proc Add OSA_kProcAddFile ok! [m[0;32;32m00:00:10|[pdc] sclGpio = [6], sdaGpio = [5] [m[0;36m00:00:10|[pdc] PDC_keyScanGpioInit OK [m[1;37m00:00:10|[pdc] Dev has No Key Cfg! [m[0;32;32m00:00:10|[OSA-DRV] Char device create OK ! [m[0;32;32m00:00:10|[OSA-DRV] Char device create OK ! [m[0;32;32m00:00:10|[pdc] SramFile init ok ! [m[0;32;32m00:00:10|[pdc] Both of Chief and Backup File CRC check OK! [m[0;32;32m00:00:10|[OSA-DRV] Char device create OK ! [m[0;32;32m00:00:10|[pdc] PDC Driver Initial OK ! [m[0;35m00:00:10|[OSA-DRV] recordTsk Task pid=844 tid=844 [mCATEGORY = 2 IPC Device [0;32;32m00:00:10|[crypt]

I need Help U-Boot 2010.06-svn503 (Dec 05 2014 - 14:11:35) DRAM: 254 MiB NAND: 128 MiB state:ff,err_count:02 Net: Detected MACID:4c:11:bf:cd:00:2d PHY:0x00221513,addr:0x00 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: 0xc5000000 Loading: 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: 0xc2000000 Loading: Retry count exceeded; starting again NAND read: device 0 offset 0xc80000, size 0x00580000 5767168 bytes read: OK ## Booting kernel from Legacy Image at c2000000 ... Image Name: Linux-2.6.38.8 Created: 2014-12-05 7:39:45 UTC Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 2546892 Bytes = 2.4 MiB Load Address: c0208000 Entry Point: c0208000 Verifying Checksum ... OK Loading Kernel Image ...OK OK

Hello everyone ! I post may not be in the right séction but it is a fact similar to Brick. Sorry in advance for my English, I do not speak it at all. (Google Taduction) French site and no one talks about my problem. Recently, we had a power outage. One of my cameras is delivered zero ... It is a Dahua Ipc-Hfw4300s (Recente, 1 month, China) On my router, I see Connected (IP: 192.168.1.108) Whereas before the power failure was 192.168.1.109. The indicator on the camera is on but not connected me with a browser. I made a ping to this IP, 100% or 50% of success, it varies. I tried the reset button on the camera, she restarts well but still the same problem. Unable to me connected with General ConfigTool. I do not have time to test all ports the camera, no doubt, restarts ... Is that connecting it in another way, I have a chance of the recovered? If yes, what equipment do I need? or find it? Thank you in advance. Many greetings !

Hello everyone ! I post may not be in the right séction but it is a fact similar to Brick. Sorry in advance for my English, I do not speak it at all. (Google Taduction) French site and no one talks about my problem. Recently, we had a power outage. One of my cameras is delivered zero ... It is a Dahua Ipc-Hfw4300s (Recente, 1 month, China) On my router, I see Connected (IP: 192.168.1.108) Whereas before the power failure was 192.168.1.109. The indicator on the camera is on but not connected me with a browser. I made a ping to this IP, 100% or 50% of success, it varies. I tried the reset button on the camera, she restarts well but still the same problem. Unable to me connected with General ConfigTool. I do not have time to test all ports the camera, no doubt, restarts ... Is that connecting it in another way, I have a chance of the recovered? If yes, what equipment do I need? or find it? Thank you in advance. Many greetings ! U-Boot 2010.06-svn503 (Dec 05 2014 - 14:11:35) DRAM: 254 MiB NAND: 128 MiB state:ff,err_count:02 Net: Detected MACID:4c:11:bf:cd:00:2d PHY:0x00221513,addr:0x00 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: 0xc5000000 Loading: 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: 0xc2000000 Loading: Retry count exceeded; starting again NAND read: device 0 offset 0xc80000, size 0x00580000 5767168 bytes read: OK ## Booting kernel from Legacy Image at c2000000 ... Image Name: Linux-2.6.38.8 Created: 2014-12-05 7:39:45 UTC Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 2546892 Bytes = 2.4 MiB Load Address: c0208000 Entry Point: c0208000 Verifying Checksum ... OK Loading Kernel Image ...OK OK

Hello everyone ! I post may not be in the right séction but it is a fact similar to Brick. Sorry in advance for my English, I do not speak it at all. (Google Taduction) French site and no one talks about my problem. Recently, we had a power outage. One of my cameras is delivered zero ... It is a Dahua Ipc-Hfw4300s (Recente, 1 month, China) On my router, I see Connected (IP: 192.168.1.108) Whereas before the power failure was 192.168.1.109. The indicator on the camera is on but not connected me with a browser. I made a ping to this IP, 100% or 50% of success, it varies. I tried the reset button on the camera, she restarts well but still the same problem. Unable to me connected with General ConfigTool. I do not have time to test all ports the camera, no doubt, restarts ... Is that connecting it in another way, I have a chance of the recovered? If yes, what equipment do I need? or find it? Thank you in advance. Many greetings !