This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

UBIFS Error after running long time

Other Parts Discussed in Thread: DM388, DM385, TPS65910

Hi

Platform: DM388 IPNC

S/W: IPNC RDK Ver 3.8

I am running custom  firmware  simultaneously on 4 DM388 IPNCs. One of the camera  failed after running  successfully for 12 days. A reboot doesn't help to recover. Upon checking the logs, I see  the below error: (Attached full log)

 [host] Loaded file ./firmware/ipnc_rdk_fw_m3video.xem3 on slave procId 0.
UBIFS error (pid 334): ubifs_decompress: cannot decompress 2325 bytes, compressor lzo, error -22
UBIFS error (pid 334): read_block: bad data node (block 628, inode 3514)
UBIFS error (pid 334): do_readpage: cannot read page 628 of inode 3514, error -22


The other 3 cameras  have no problem even after 12 days.

The commands I used for making the image is given below.

mtd-utils/32bit/mkfs.ubifs -q -r filesys -m 2048 -e 126976 -c 840 -F -x lzo -o ubifs.img
mtd-utils/32bit/ubinize -o dm388_svc_3Layer_Ver2.4_21072015_smp_TI4.img -m 2048 -p 128KiB -s 2048 -O 2048 ubinize.cfg

 


Below  is the  contents of ubinize.cfg file

[ubifs]
mode=ubi
image=ubifs.img
vol_id=0
vol_size=100MiB
vol_type=dynamic
vol_name=filesys
vol_flags=autoresize

Image size is 60M only.

Can someone look into this issue ?

Best regards

JK

Full Log

=======

 

 done, booting the kernel.
Linux version 2.6.37_DM385_IPNC_3.50.00 (root@localhost.localdomain) (gcc version 4.5.3 20110311 (prerelease) (GCC) ) #6 Tue Jan 22 15:25:19 CST 2013
 CPU: ARMv7 Processor [413fc082] revision 2 (ARMv7), cr=10c53c7f
 CPU: VIPT nonaliasing data cache, VIPT aliasing instruction cache
 Machine: dm385ipnc
 vram size = 4194304 at 0x0
 bootconsole [earlycon0] enabled
 ti81xx_reserve: ### Reserved DDR region @84f00000
 reserved size = 4194304 at 0x0
 FB: Reserving 4194304 bytes SDRAM for VRAM
 Memory policy: ECC disabled, Data cache writeback
 OMAP chip is DM385 1.0
 SRAM: Mapped pa 0x402f1000 to va 0xfe400000 size: 0xf000
 Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 19040
 Kernel command line: console=ttyO0,115200n8 rootwait=1 rw ubi.mtd=4,2048 rootfstype=ubifs root=ubi0:filesys init=/init mem=80M vram=4M notifyk.vpssm3_sva=0xBFD00000 ip=192.168.1.227 cmemk.phys_start=0x85000000 cmemk.phys_end=0x89000000 cmemk.allowOverlap=1 eth=00:0C:0C:02:50:8F earlyprintk
 cpsw: kernel boot params Ethernet address: 00:0C:0C:02:50:8F
 PID hash table entries: 512 (order: -1, 2048 bytes)
 Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
 Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
 Memory: 74MB 1MB = 75MB total
 Memory: 70676k/70676k available, 11244k reserved, 0K highmem
 Virtual kernel memory layout:
     vector  : 0xffff0000 - 0xffff1000   (   4 kB)
     fixmap  : 0xfff00000 - 0xfffe0000   ( 896 kB)
     DMA     : 0xffc00000 - 0xffe00000   (   2 MB)
     vmalloc : 0xc5800000 - 0xf8000000   ( 808 MB)
     lowmem  : 0xc0000000 - 0xc5000000   (  80 MB)
     pkmap   : 0xbfe00000 - 0xc0000000   (   2 MB)
     modules : 0xbf000000 - 0xbfe00000   (  14 MB)
       .init : 0xc0008000 - 0xc003e000   ( 216 kB)
       .text : 0xc003e000 - 0xc04ba000   (4592 kB)
       .data : 0xc04ba000 - 0xc04fabc0   ( 259 kB)
 SLUB: Genslabs=11, HWalign=64, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
 NR_IRQS:375
 IRQ: Found an INTC at 0xfa200000 (revision 5.0) with 128 interrupts
 Total of 128 interrupts on 1 active controller
 GPMC revision 6.0
 Trying to install interrupt handler for IRQ368
 Trying to install interrupt handler for IRQ369
 Trying to install interrupt handler for IRQ370
 Trying to install interrupt handler for IRQ371
 Trying to install interrupt handler for IRQ372
 Trying to install interrupt handler for IRQ373
 Trying to install interrupt handler for IRQ374
 Trying to install type control for IRQ375
 Trying to set irq flags for IRQ375
 OMAP clockevent source: GPTIMER1 at 20000000 Hz
 Console: colour dummy device 80x30
 Calibrating delay loop... 599.65 BogoMIPS (lpj=2998272)
 pid_max: default: 32768 minimum: 301
 Security Framework initialized
 Mount-cache hash table entries: 512
 CPU: Testing write buffer coherency: ok
 devtmpfs: initialized
 TI81XX: Map 0x84f00000 to 0xfe500000 for dram barrier
 TI81XX: Map 0x40300000 to 0xfe600000 for sram barrier
 omap_voltage_early_init: voltage driver support not added
 regulator: core version 0.5
 regulator: dummy:  
 NET: Registered protocol family 16
 omap_voltage_domain_lookup: Voltage driver init not yet happened.Faulting!
 omap_voltage_add_dev: VDD specified does not exist!
 OMAP GPIO hardware version 0.1
 OMAP GPIO hardware version 0.1
 OMAP GPIO hardware version 0.1
 OMAP GPIO hardware version 0.1
 omap_mux_init: Add partition: #1: core, flags: 4
 Cannot clk_get ck_32
 Debugfs: Only enabling/disabling deep sleep and wakeup timer is supported now
 registered ti81xx_vpss device
 registered ti81xx_vidout device
 registered ti81xx on-chip HDMI device
 registered ti81xx_fb device
 PWM0 init success.
 PWM1 init success.
 bio: create slab <bio-0> at 0
 SCSI subsystem initialized
 omap2_mcspi: probe of omap2_mcspi.3 failed with error -2
 omap2_mcspi: probe of omap2_mcspi.4 failed with error -2
 USBSS revision 4ea2080b
 registerd cppi-dma Intr @ IRQ 17
 Cppi41 Init Done
 omap_i2c omap_i2c.1: bus 1 rev4.0 at 100 kHz
 tps65910 1-002d: read from reg 3f failed
 tps65910 1-002d: read from reg 1e failed
 set_machine_constraints: failed to enable VRTC
 tps65910 1-002d: failed to register tps65910-pmic regulator
 tps65910-pmic: probe of tps65910-pmic failed with error -121
 tps65911-rtc tps65911-rtc: rtc core: registered tps65911-rtc as rtc0
 tps65910 1-002d: No interrupt support, no core IRQ
 Advanced Linux Sound Architecture Driver Version 1.0.23.
 Switching to clocksource gp timer
 musb-hdrc: version 6.0, peripheral, debug=0
 musb-hdrc musb-hdrc.0: dma type: dma-cppi41
 MUSB controller-0 revision 4ea20800
 usb2phy: computed values rxcalib(15)DACs(23 13 15)
 usb2phy: override computed values rxcalib(15)DACs(23 13 15)
 usb2phy_config: musb(0) rxcalib done, rxcalib read value 6f6bdb7e
 musb-hdrc musb-hdrc.0: USB Peripheral mode controller at c581e000 using DMA, IRQ 18
 NET: Registered protocol family 2
 IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
 TCP established hash table entries: 4096 (order: 3, 32768 bytes)
 TCP bind hash table entries: 4096 (order: 2, 16384 bytes)
 TCP: Hash tables configured (established 4096 bind 4096)
 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.
 NetWinder Floating Point Emulator V0.97 (double precision)
 PMU: registered new PMU device of type 0
 omap-iommu omap-iommu.0: ducati registered
 omap-iommu omap-iommu.1: sys registered
 JFFS2 version 2.2. (NAND) © 2001-2006 Red Hat, Inc.
 msgmni has been set to 138
 io scheduler noop registered
 io scheduler deadline registered
 io scheduler cfq registered (default)
 CMEMK module: built on Jan 11 2013 at 15:41:27
   Reference Linux version 2.6.37
   File /opt/workdir/IPNC_DM385_IMX136_v3.5/Source/ti_tools/linuxutils_3_23_00_01/packages/ti/sdo/linuxutils/cmem/src/module/cmemk.c
 allocated heap buffer 0xc7000000 of size 0x4000000
 cmemk initialized
 Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
 omap_uart.0: ttyO0 at MMIO 0x48020000 (irq = 72) is a OMAP UART0
 console [ttyO0] enabled, bootconsole disabled
console [ttyO0] enabled, bootconsole disabled
 omap_uart.1: ttyO1 at MMIO 0x48022000 (irq = 73) is a OMAP UART1
omap_uart.2: ttyO2 at MMIO 0x48024000 (irq = 74) is a OMAP UART2
brd: module loaded
loop: module loaded
omap2-nand driver initializing
NAND device: Manufacturer ID: 0x2c, Chip ID: 0xba (Micron )
Creating 8 MTD partitions on "omap2-nand.0":
0x000000000000-0x000000020000 : "U-Boot-min"
0x000000020000-0x000000260000 : "U-Boot"
0x000000260000-0x000000280000 : "U-Boot Env"
0x000000280000-0x0000006c0000 : "Kernel"
0x0000006c0000-0x000006fc0000 : "File System"
0x000006fc0000-0x000007bc0000 : "Data"
0x000007bc0000-0x00000b0c0000 : "File System2"
0x00000b0c0000-0x000010000000 : "Reserved"
UBI: attaching mtd4 to ubi0
UBI: physical eraseblock size:   131072 bytes (128 KiB)
UBI: logical eraseblock size:    126976 bytes
UBI: smallest flash I/O unit:    2048
UBI: sub-page size:              512
UBI: VID header offset:          2048 (aligned 2048)
UBI: data offset:                4096
UBI: max. sequence number:       281
UBI: attached mtd4 to ubi0
UBI: MTD device name:            "File System"
UBI: MTD device size:            105 MiB
UBI: number of good PEBs:        840
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: 840
UBI: number of PEBs reserved for bad PEB handling: 8
UBI: max/mean erase counter: 3/0
UBI: image sequence number:  858157907
UBI: background thread "ubi_bgt0d" started, PID 41
davinci_mdio davinci_mdio.0: davinci mdio revision 1.6
davinci_mdio davinci_mdio.0: detected phy mask fffffffe
davinci_mdio.0: probed
davinci_mdio davinci_mdio.0: phy[0]: device 0:00, driver unknown
mice: PS/2 mouse device common for all mice
i2c /dev entries driver
Linux video capture interface: v2.00
OMAP Watchdog Timer Rev 0x00: initial timeout 60 sec
notify_shm_drv: no DSP present (MULTIPROC_INVALIDID)
notify_init : notify drivercreated  for  remote proc id 1 at physical Address 0xbfd00000
cm: Module associated with clock hdmi_i2s_fck didn't enable in 100000 tries
asoc: tlv320aic3x-hifi <-> davinci-mcasp.1 mapping ok
asoc: HDMI-DAI-CODEC <-> hdmi-dai mapping ok
ALSA device list:
  #0: TI81XX EVM
nf_conntrack version 0.5.0 (1104 buckets, 4416 max)
ip_tables: (C) 2000-2006 Netfilter Core Team
TCP cubic registered
NET: Registered protocol family 17
Bridge firewalling registered
lib80211: common routines for IEEE802.11 drivers
Registering the dns_resolver key type
VFP support v0.3: implementor 41 architecture 3 part 30 variant c rev 3
omap_voltage_late_init: Voltage driver support not added
Power Management for TI81XX.
Detected MACID=0:c:c:2:50:8f
tps65911-rtc tps65911-rtc: hctosys: unable to read the hardware clock
 
CPSW phy found : id is : 0x4dd074
PHY 0:01 not found
IP-Config: Guessing netmask 255.255.255.0
IP-Config: Complete:
     device=eth0, addr=192.168.1.227, mask=255.255.255.0, gw=255.255.255.255,
     host=192.168.1.227, domain=, nis-domain=(none),
     bootserver=255.255.255.255, rootserver=255.255.255.255, rootpath=
UBIFS: recovery needed
UBIFS: recovery completed
UBIFS: mounted UBI device 0, volume 0, name "filesys"
UBIFS: file system size:   103739392 bytes (101308 KiB, 98 MiB, 817 LEBs)
UBIFS: journal size:       9023488 bytes (8812 KiB, 8 MiB, 72 LEBs)
UBIFS: media format:       w4/r0 (latest is w4/r0)
UBIFS: default compressor: lzo
UBIFS: reserved for root:  0 bytes (0 KiB)
VFS: Mounted root (ubifs filesystem) on device 0:13.
devtmpfs: mounted
Freeing init memory: 216K
Failed to execute /init.  Attempting defaults...
 INIT: version 2.86 booting  
Please wait: booting...
Starting udev
Root filesystem already rw, not remounting
Caching udev devnodes
root: mount: mounting /dev/root on / failed: No such file or directory
Configuring network interfaces... done.
Setting up IP spoofing protection: rp_filter.
rm: cannot remove '/tmp': Device or resource busy
hwclock: RTC_RD_TIME: Remote I/O error
Fri Nov  9 13:44:00 GMT-8 2012
hwclock: RTC_SET_TIME: Remote I/O error
 inside finish.sh  
UBI: attaching mtd5 to ubi1
UBI: physical eraseblock size:   131072 bytes (128 KiB)
UBI: logical eraseblock size:    126976 bytes
UBI: smallest flash I/O unit:    2048
UBI: sub-page size:              512
UBI: VID header offset:          2048 (aligned 2048)
UBI: data offset:                4096
UBI: max. sequence number:       196
UBI: attached mtd5 to ubi1
UBI: MTD device name:            "Data"
UBI: MTD device size:            12 MiB
UBI: number of good PEBs:        96
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: 96
UBI: number of PEBs reserved for bad PEB handling: 2
UBI: max/mean erase counter: 4/2
UBI: image sequence number:  -4315179
UBI: background thread "ubi_bgt1d" started, PID 274
UBI device number 1, total 96 LEBs (12189696 bytes, 11.6 MiB), available 0 LEBs (0 bytes), LEB size 126976 bytes (124.0 KiB)
UBIFS: recovery needed
UBIFS: recovery completed
UBIFS: mounted UBI device 1, volume 0, name "ubifs_volume"
UBIFS: file system size:   10285056 bytes (10044 KiB, 9 MiB, 81 LEBs)
UBIFS: journal size:       1015809 bytes (992 KiB, 0 MiB, 6 LEBs)
UBIFS: media format:       w4/r0 (latest is w4/r0)
UBIFS: default compressor: lzo
UBIFS: reserved for root:  485787 bytes (474 KiB)
UBI: attaching mtd7 to ubi2
UBI: physical eraseblock size:   131072 bytes (128 KiB)
UBI: logical eraseblock size:    126976 bytes
UBI: smallest flash I/O unit:    2048
UBI: sub-page size:              512
UBI: VID header offset:          2048 (aligned 2048)
UBI: data offset:                4096
UBI: max. sequence number:       42
PHY: 0:00 - Link is Up - 1000/Full
UBI: attached mtd7 to ubi2
UBI: MTD device name:            "Reserved"
UBI: MTD device size:            79 MiB
UBI: number of good PEBs:        634
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: 634
UBI: number of PEBs reserved for bad PEB handling: 6
UBI: max/mean erase counter: 7/5
UBI: image sequence number:  2071392193
UBI: background thread "ubi_bgt2d" started, PID 287
UBI device number 2, total 634 LEBs (80502784 bytes, 76.8 MiB), available 0 LEBs (0 bytes), LEB size 126976 bytes (124.0 KiB)
UBIFS: recovery needed
UBIFS: recovery completed
UBIFS: mounted UBI device 2, volume 0, name "ubifs_volume"
UBIFS: file system size:   78090240 bytes (76260 KiB, 74 MiB, 615 LEBs)
UBIFS: journal size:       3936256 bytes (3844 KiB, 3 MiB, 31 LEBs)
UBIFS: media format:       w4/r0 (latest is w4/r0)
UBIFS: default compressor: lzo
UBIFS: reserved for root:  3688395 bytes (3601 KiB)
numid=1,iface=MIXER,name='PCM Playback Volume'
  ; type=INTEGER,access=rw---R--,values=2,min=0,max=127,step=0
  : values=127,127
  | dBscale-min=-63.50dB,step=0.50dB,mute=0
 [c6xdsp ] Remote Debug Shared Memory @ 0xbff00000
 [m3video] Remote Debug Shared Memory @ 0xbff05020
 [m3vpss ] Remote Debug Shared Memory @ 0xbff0a040
SysLink version : 2.21.02.10
SysLink module created on Date:Jan 29 2015 Time:17:22:51
Trace enabled
Trace SetFailureReason enabled
/dev/mem opened.
             Phy Addr : 0x48181560 Data : 0x00000002
          Unhandled fault: external abort on non-linefetch (0x1018) at 0x4021e0e4
   Phy Addr : 0x48180f10 Data : 0x00000000
             Phy Addr : 0x48180508 Data : 0x00000302
             Phy Addr : 0x48180520 Data : 0x00000002
             Phy Addr : 0x48180524 Data : 0x00000002
             Phy Addr : 0x48180528 Data : 0x00000002
             Phy Addr : 0x4c0000e4 Data : 0x00170209
Bus error
 
  [host]  Setting DMM priority for [ISS     ] to [0] ( 0x4e000634 = 0x00080000 )
 
  [host]  Setting L3 bandwidth regulator for [ISS     ] to [press=[3,3] BW=400, WM Cycles=2500]
 
  [host]  Setting L3 bandwidth regulator for [HDVICP0 ] to [press=[0,0] BW=900, WM Cycles=2500]
Creat queue id:0
queue id:0
FileMngThread created
Creat queue id:32769
queue id:32769
AlramThread created
Share memory init success
IPNC_3.50.00 (root@localhost.localdomain) (gcc version 4.5.3 20110311 (p  
 
  [host]  Setting DMM priority for [HDVICP0 ] to [1] ( 0x4e000634 = 0x00000009 )
Creat queue id:65538
queue id:65538
Creat queue id:98307
queue id:98307
queue id:32769
 [c6xdsp ] Remote Debug Shared Memory @ 0xbff00000
 [m3video] Remote Debug Shared Memory @ 0xbff05020
 [m3vpss ] Remote Debug Shared Memory @ 0xbff0a040
 
  [host] Attached to slave procId 1.
UBIFS error (pid 346): ubifs_decompress: cannot decompress 2325 bytes, compressor lzo, error -22
UBIFS error (pid 346): read_block: bad data node (block 628, inode 3514)
UBIFS error (pid 346): do_readpage: cannot read page 628 of inode 3514, error -22
 
  [host] Attached to slave procId 0.
 
  [host] Loaded file ./firmware/ipnc_rdk_fw_m3vpss.xem3 on slave procId 1.
 
  [host] Started slave procId 1.
 
  [host] After Ipc_loadcallback status [0x00000000]
 
  [host] Loaded file ./firmware/ipnc_rdk_fw_m3video.xem3 on slave procId 0.
 
  [host] Started slave procId 0.
 
  [host] After Ipc_loadcallback status [0x00000000]
 [m3video] ***** SYSTEM  : Frequency <ORG> - 200000000, <NEW> - 200000000
 [m3video]   
 [m3video]  *** UTILS: CPU KHz = 400000 Khz ***
 [m3video]   
 [m3video]  69: SYSTEM  : System Common Init in progress !!!
 [m3video]  75: SYSTEM: IPC init in progress !!!
 [m3video]  79: SYSTEM: Attaching to [HOST] ...  
 [m3video]  134: SYSTEM: Attaching to [HOST] ...  
 [m3video]  168: SYSTEM: Attaching to [HOST] ... SUCCESS !!!
 
  [host] After Ipc_startcallback status [0x00000000]
 [m3video]  174: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  229: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  284: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  339: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  394: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  449: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  504: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  559: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  614: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  669: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  724: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  779: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  834: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  889: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  944: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  999: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  1054: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  1109: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  1164: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  1219: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  1274: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  1329: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  1384: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  1439: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  1494: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  1549: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  1604: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  1659: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  1714: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  1769: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  1824: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  1879: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  1934: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  1989: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  2044: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  2099: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  2154: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  2209: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  2264: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  2319: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  2374: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  2429: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  2484: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  2539: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  2594: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  2649: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  2704: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  2759: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  2814: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  2869: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  2924: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  2979: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  3034: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  3089: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  3144: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  3199: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  3254: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  3309: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  3364: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  3419: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  3474: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  3529: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  3584: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  3639: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  3694: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  3749: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  3804: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  3859: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  3914: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  3969: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  4024: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  4079: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  4134: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  4189: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  4244: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  4299: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  4354: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  4409: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  4464: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  4519: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  4574: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  4629: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  4684: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  4739: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  4794: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  4849: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  4904: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  4959: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  5014: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  5069: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  5124: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  5179: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  5234: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  5289: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  5344: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  5399: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  5454: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  5509: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  5564: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  5619: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  5674: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  5729: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  5784: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  5839: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  5894: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  5949: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  6004: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  6059: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  6114: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  6169: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  6224: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  6279: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  6334: SYSTEM: Attaching to [VPSS-M3] ...  
JK: inside autorun  
 [m3video]  6389: SYSTEM: Attaching to [VPSS-M3] INIT: Entering runlevel: 5  
 sbulla: unknown partition table
 [m3video]  6444: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  6499: SYSTEM: Attaching to [VPSS-M3] ...  
Starting telnet daemon [m3video]  6554: SYSTEM: Attaching to [VPSS-M3] ...  
 sbulla: unknown partition table
 [m3video]  6609: SYSTEM: Attaching to [VPSS-M3] ...  
.
 [m3video]  6664: SYSTEM: Attaching to [VPSS-M3] ...  
Starting syslogd/klogd:  [m3video]  6719: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  6774: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  6829: SYSTEM: Attaching to [VPSS-M3] ...  
done
 [m3video]  6884: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  6939: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  6994: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  7049: SYSTEM: Attaching to [VPSS-M3] ...  
c
 _____                    _____           _         _    
|  _  |___ ___ ___ ___   |  _  |___ ___  |_|___ ___| |_  
|     |  _| .'| . | . |  |   __|  _| . | | | -_|  _|  _|
|__|__|_| |__,|_  |___|  |__|  |_| |___|_| |___|___|_|   
              |___|                    |___|             
 
Arago Project http://arago-project.org dm814x-evm ttyO0
 
Arago 2011.09 dm814x-evm ttyO0
 
dm814x-evm login: root (automatic login)
 [m3video]  7104: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  7159: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  7214: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  7269: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  7324: SYSTEM: Attaching to [VPSS-M3] ...  
root@dm814x-evm:~#  [m3video]  7379: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  7434: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  7489: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  7544: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  7599: SYSTEM: Attaching to [VPSS-M3] ...  
mkdosfs 3.0.12 (29 Oct 2011)
 [m3video]  7654: SYSTEM: Attaching to [VPSS-M3] ...  
unable to get drive geometry, using default 255/63
/dev/sbulla has 255 heads and 63 sectors per track,
logical sector size is 512,
using 0xf8 media descriptor, with 1024 sectors;
file system has 2 12-bit FATs and 4 sectors per cluster.
FAT size is 1 sector, and provides 247 clusters.
There is 1 reserved sector.
Root directory contains 512 slots and uses 32 sectors.
Volume ID is 8300adae, no volume label.
 [m3video]  7709: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  7764: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  7819: SYSTEM: Attaching to [VPSS-M3] ...  
g_file_storage gadget: No serial-number string provided!
 [m3video]  7874: SYSTEM: Attachg_file_storage gadget: File-backed Storage Gadget, version: 1 September 2010
ing to [VPSS-M3]g_file_storage gadget: Number of LUNs=1
 ...  
g_file_storage gadget-lun0: ro=0, nofua=0, file: /dev/sbulla
 [m3video]  7929: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  7984: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  8039: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  8094: SYSTEM: Attaching to [VPSS-M3] ...  
Simple mixer control 'PGA',0
  Capabilities: cvolume cswitch penum
  Capture channels: Front Left - Front Right
  Limits: Capture 0 - 119
  Front Left: Capture 80 [67%] [40.00dB] [on]
  Front Right: Capture 80 [67%] [40.00dB] [on]
 [m3video]  8149: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  8204: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  8259: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  8314: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  8369: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  8424: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  8479: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  8534: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  8589: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  8644: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  8699: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  8754: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  8809: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  8864: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  8919: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  8974: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  9029: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  9084: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  9139: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  9194: SYSTEM: Attaching to [VPSS-M3] ...  
queue id:0
 [m3video]  9249: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  9304: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  9359: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  9414: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  9469: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  9524: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  9579: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  9634: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  9689: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  9744: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  9799: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  9854: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  9909: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  9964: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  10019: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  10074: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  10129: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  10184: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  10239: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  10294: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  10349: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  10404: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  10459: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  10514: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  10569: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  10624: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  10679: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  10734: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  10789: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  10844: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  10899: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  10954: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  11009: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  11064: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  11119: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  11174: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  11229: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  11284: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  11339: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  11394: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  11449: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  11504: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  11559: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  11614: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  11669: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  11724: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  11779: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  11834: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  11889: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  11944: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  11999: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  12054: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  12109: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  12164: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  12219: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  12274: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  12329: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  12384: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  12439: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  12494: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  12549: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  12604: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  12659: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  12714: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  12769: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  12824: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  12879: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  12934: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  12989: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  13044: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  13099: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  13154: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  13209: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  13264: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  13319: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  13374: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  13429: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  13484: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  13539: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  13594: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  13649: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  13704: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  13759: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  13814: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  13869: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  13924: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  13979: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  14034: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  14089: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  14144: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  14199: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  14254: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  14309: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  14364: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  14419: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  14474: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  14529: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  14584: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  14639: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  14694: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  14749: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  14804: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  14859: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  14914: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  14969: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  15024: SYSTEM: Attaching to [VPSS-M3] ...  
 
 
U-Boot 2010.06 (Jun 23 2014 - 19:04:06) DM388_IPNC_3.80.00
 
DM385-GP rev 1.1
 
ARM clk: 600MHz
DDR clk: 533MHz
L3 clk:  200MHz
IVA clk: 450MHz
ISS clk: 400MHz
DSP Default OFF
DSS Default OFF
 
DRAM:  1 GiB
DCACHE:  Off
NAND:  HW ECC BCH8 Selected
256 MiB
Using default environment
 
The 2nd stage U-Boot will now be auto-loaded
Please do not interrupt the countdown till DM385_IPNC prompt if 2nd stage is already flashed
Hit any key to stop autoboot:  0  
 
NAND read: device 0 offset 0x20000, size 0x40000
 262144 bytes read: OK
## Starting application at 0x81000000 ...
 
 
U-Boot 2010.06 (Jun 23 2014 - 19:06:46) DM388_IPNC_3.80.00
 
DM385-GP rev 1.1
 
ARM clk: 600MHz
DDR clk: 533MHz
L3 clk:  200MHz
IVA clk: 450MHz
ISS clk: 400MHz
DSP Default OFF
DSS Default OFF
 
I2C:   ready
DRAM:  1 GiB
DCACHE:  On
NAND:  HW ECC BCH8 Selected
256 MiB
MMC:   OMAP SD/MMC: 0, ON-BOARD SDIO: 1
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@@                                                               @@
@@                                                               @@
@@                                                               @@
@@                                                               @@
@@       _______   __       __   ______    ______    ______      @@
@@      /       \ /  \     /  | /      \  /      \  /      \     @@
@@      $$$$$$$  |$$  \   /$$ |/$$$$$$  |/$$$$$$  |/$$$$$$  |    @@
@@      $$ |  $$ |$$$  \ /$$$ |$$ ___$$ |$$ \__$$ |$$ \__$$ |    @@
@@      $$ |  $$ |$$$$  /$$$$ |  /   $$< $$    $$< $$    $$<     @@
@@      $$ |  $$ |$$ $$ $$/$$ | _$$$$$  | $$$$$$  | $$$$$$  |    @@
@@      $$ |__$$ |$$ |$$$/ $$ |/  \__$$ |$$ \__$$ |$$ \__$$ |    @@
@@      $$    $$/ $$ | $/  $$ |$$    $$/ $$    $$/ $$    $$/     @@
@@      $$$$$$$/  $$/      $$/  $$$$$$/   $$$$$$/   $$$$$$/      @@
@@                                                               @@
@@                                                               @@
@@                                                               @@
@@                                                               @@
@@                                                               @@
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
 
Net:   Ethernet clocking: 0x52
Detected MACID:0:c:c:a0:ff:fa
cpsw
Hit any key to stop autoboot:  3 2 1 0  
 
Loading from nand0, offset 0x280000
   Image Name:   Linux-2.6.37_DM385_IPNC_3.50.00
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2483368 Bytes = 2.4 MiB
   Load Address: 80008000
   Entry Point:  80008000
## Booting kernel from Legacy Image at 81000000 ...
   Image Name:   Linux-2.6.37_DM385_IPNC_3.50.00
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2483368 Bytes = 2.4 MiB
   Load Address: 80008000
   Entry Point:  80008000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK
OK
 
Starting kernel ...
 
Uncompressing Linux... done, booting the kernel.
Linux version 2.6.37_DM385_IPNC_3.50.00 (root@localhost.localdomain) (gcc version 4.5.3 20110311 (prerelease) (GCC) ) #6 Tue Jan 22 15:25:19 CST 2013
 CPU: ARMv7 Processor [413fc082] revision 2 (ARMv7), cr=10c53c7f
 CPU: VIPT nonaliasing data cache, VIPT aliasing instruction cache
 Machine: dm385ipnc
 vram size = 4194304 at 0x0
 bootconsole [earlycon0] enabled
 ti81xx_reserve: ### Reserved DDR region @84f00000
 reserved size = 4194304 at 0x0
 FB: Reserving 4194304 bytes SDRAM for VRAM
 Memory policy: ECC disabled, Data cache writeback
 OMAP chip is DM385 1.0
 SRAM: Mapped pa 0x402f1000 to va 0xfe400000 size: 0xf000
 Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 19040
 Kernel command line: console=ttyO0,115200n8 rootwait=1 rw ubi.mtd=4,2048 rootfstype=ubifs root=ubi0:filesys init=/init mem=80M vram=4M notifyk.vpssm3_sva=0xBFD00000 ip=192.168.1.227 cmemk.phys_start=0x85000000 cmemk.phys_end=0x89000000 cmemk.allowOverlap=1 eth=00:0C:0C:02:50:8F earlyprintk
 cpsw: kernel boot params Ethernet address: 00:0C:0C:02:50:8F
 PID hash table entries: 512 (order: -1, 2048 bytes)
 Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
 Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
 Memory: 74MB 1MB = 75MB total
 Memory: 70676k/70676k available, 11244k reserved, 0K highmem
 Virtual kernel memory layout:
     vector  : 0xffff0000 - 0xffff1000   (   4 kB)
     fixmap  : 0xfff00000 - 0xfffe0000   ( 896 kB)
     DMA     : 0xffc00000 - 0xffe00000   (   2 MB)
     vmalloc : 0xc5800000 - 0xf8000000   ( 808 MB)
     lowmem  : 0xc0000000 - 0xc5000000   (  80 MB)
     pkmap   : 0xbfe00000 - 0xc0000000   (   2 MB)
     modules : 0xbf000000 - 0xbfe00000   (  14 MB)
       .init : 0xc0008000 - 0xc003e000   ( 216 kB)
       .text : 0xc003e000 - 0xc04ba000   (4592 kB)
       .data : 0xc04ba000 - 0xc04fabc0   ( 259 kB)
 SLUB: Genslabs=11, HWalign=64, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
 NR_IRQS:375
 IRQ: Found an INTC at 0xfa200000 (revision 5.0) with 128 interrupts
 Total of 128 interrupts on 1 active controller
 GPMC revision 6.0
 Trying to install interrupt handler for IRQ368
 Trying to install interrupt handler for IRQ369
 Trying to install interrupt handler for IRQ370
 Trying to install interrupt handler for IRQ371
 Trying to install interrupt handler for IRQ372
 Trying to install interrupt handler for IRQ373
 Trying to install interrupt handler for IRQ374
 Trying to install type control for IRQ375
 Trying to set irq flags for IRQ375
 OMAP clockevent source: GPTIMER1 at 20000000 Hz
 Console: colour dummy device 80x30
 Calibrating delay loop... 599.65 BogoMIPS (lpj=2998272)
 pid_max: default: 32768 minimum: 301
 Security Framework initialized
 Mount-cache hash table entries: 512
 CPU: Testing write buffer coherency: ok
 devtmpfs: initialized
 TI81XX: Map 0x84f00000 to 0xfe500000 for dram barrier
 TI81XX: Map 0x40300000 to 0xfe600000 for sram barrier
 omap_voltage_early_init: voltage driver support not added
 regulator: core version 0.5
 regulator: dummy:  
 NET: Registered protocol family 16
 omap_voltage_domain_lookup: Voltage driver init not yet happened.Faulting!
 omap_voltage_add_dev: VDD specified does not exist!
 OMAP GPIO hardware version 0.1
 OMAP GPIO hardware version 0.1
 OMAP GPIO hardware version 0.1
 OMAP GPIO hardware version 0.1
 omap_mux_init: Add partition: #1: core, flags: 4
 Cannot clk_get ck_32
 Debugfs: Only enabling/disabling deep sleep and wakeup timer is supported now
 registered ti81xx_vpss device
 registered ti81xx_vidout device
 registered ti81xx on-chip HDMI device
 registered ti81xx_fb device
 PWM0 init success.
 PWM1 init success.
 bio: create slab <bio-0> at 0
 SCSI subsystem initialized
 omap2_mcspi: probe of omap2_mcspi.3 failed with error -2
 omap2_mcspi: probe of omap2_mcspi.4 failed with error -2
 USBSS revision 4ea2080b
 registerd cppi-dma Intr @ IRQ 17
 Cppi41 Init Done
 omap_i2c omap_i2c.1: bus 1 rev4.0 at 100 kHz
 tps65910 1-002d: read from reg 3f failed
 tps65910 1-002d: read from reg 1e failed
 set_machine_constraints: failed to enable VRTC
 tps65910 1-002d: failed to register tps65910-pmic regulator
 tps65910-pmic: probe of tps65910-pmic failed with error -121
 tps65911-rtc tps65911-rtc: rtc core: registered tps65911-rtc as rtc0
 tps65910 1-002d: No interrupt support, no core IRQ
 Advanced Linux Sound Architecture Driver Version 1.0.23.
 Switching to clocksource gp timer
 musb-hdrc: version 6.0, peripheral, debug=0
 musb-hdrc musb-hdrc.0: dma type: dma-cppi41
 MUSB controller-0 revision 4ea20800
 usb2phy: computed values rxcalib(15)DACs(23 13 15)
 usb2phy: override computed values rxcalib(15)DACs(23 13 15)
 usb2phy_config: musb(0) rxcalib done, rxcalib read value 6f6bdb7e
 musb-hdrc musb-hdrc.0: USB Peripheral mode controller at c581e000 using DMA, IRQ 18
 NET: Registered protocol family 2
 IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
 TCP established hash table entries: 4096 (order: 3, 32768 bytes)
 TCP bind hash table entries: 4096 (order: 2, 16384 bytes)
 TCP: Hash tables configured (established 4096 bind 4096)
 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.
 NetWinder Floating Point Emulator V0.97 (double precision)
 PMU: registered new PMU device of type 0
 omap-iommu omap-iommu.0: ducati registered
 omap-iommu omap-iommu.1: sys registered
 JFFS2 version 2.2. (NAND) © 2001-2006 Red Hat, Inc.
 msgmni has been set to 138
 io scheduler noop registered
 io scheduler deadline registered
 io scheduler cfq registered (default)
 CMEMK module: built on Jan 11 2013 at 15:41:27
   Reference Linux version 2.6.37
   File /opt/workdir/IPNC_DM385_IMX136_v3.5/Source/ti_tools/linuxutils_3_23_00_01/packages/ti/sdo/linuxutils/cmem/src/module/cmemk.c
 allocated heap buffer 0xc7000000 of size 0x4000000
 cmemk initialized
 Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
 omap_uart.0: ttyO0 at MMIO 0x48020000 (irq = 72) is a OMAP UART0
 console [ttyO0] enabled, bootconsole disabled
console [ttyO0] enabled, bootconsole disabled
 omap_uart.1: ttyO1 at MMIO 0x48022000 (irq = 73) is a OMAP UART1
omap_uart.2: ttyO2 at MMIO 0x48024000 (irq = 74) is a OMAP UART2
brd: module loaded
loop: module loaded
omap2-nand driver initializing
NAND device: Manufacturer ID: 0x2c, Chip ID: 0xba (Micron )
Creating 8 MTD partitions on "omap2-nand.0":
0x000000000000-0x000000020000 : "U-Boot-min"
0x000000020000-0x000000260000 : "U-Boot"
0x000000260000-0x000000280000 : "U-Boot Env"
0x000000280000-0x0000006c0000 : "Kernel"
0x0000006c0000-0x000006fc0000 : "File System"
0x000006fc0000-0x000007bc0000 : "Data"
0x000007bc0000-0x00000b0c0000 : "File System2"
0x00000b0c0000-0x000010000000 : "Reserved"
UBI: attaching mtd4 to ubi0
UBI: physical eraseblock size:   131072 bytes (128 KiB)
UBI: logical eraseblock size:    126976 bytes
UBI: smallest flash I/O unit:    2048
UBI: sub-page size:              512
UBI: VID header offset:          2048 (aligned 2048)
UBI: data offset:                4096
UBI: max. sequence number:       285
UBI: attached mtd4 to ubi0
UBI: MTD device name:            "File System"
UBI: MTD device size:            105 MiB
UBI: number of good PEBs:        840
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: 840
UBI: number of PEBs reserved for bad PEB handling: 8
UBI: max/mean erase counter: 3/0
UBI: image sequence number:  858157907
UBI: background thread "ubi_bgt0d" started, PID 41
davinci_mdio davinci_mdio.0: davinci mdio revision 1.6
davinci_mdio davinci_mdio.0: detected phy mask fffffffe
davinci_mdio.0: probed
davinci_mdio davinci_mdio.0: phy[0]: device 0:00, driver unknown
mice: PS/2 mouse device common for all mice
i2c /dev entries driver
Linux video capture interface: v2.00
OMAP Watchdog Timer Rev 0x00: initial timeout 60 sec
notify_shm_drv: no DSP present (MULTIPROC_INVALIDID)
notify_init : notify drivercreated  for  remote proc id 1 at physical Address 0xbfd00000
cm: Module associated with clock hdmi_i2s_fck didn't enable in 100000 tries
asoc: tlv320aic3x-hifi <-> davinci-mcasp.1 mapping ok
asoc: HDMI-DAI-CODEC <-> hdmi-dai mapping ok
ALSA device list:
  #0: TI81XX EVM
nf_conntrack version 0.5.0 (1104 buckets, 4416 max)
ip_tables: (C) 2000-2006 Netfilter Core Team
TCP cubic registered
NET: Registered protocol family 17
Bridge firewalling registered
lib80211: common routines for IEEE802.11 drivers
Registering the dns_resolver key type
VFP support v0.3: implementor 41 architecture 3 part 30 variant c rev 3
omap_voltage_late_init: Voltage driver support not added
Power Management for TI81XX.
Detected MACID=0:c:c:2:50:8f
tps65911-rtc tps65911-rtc: hctosys: unable to read the hardware clock
 
CPSW phy found : id is : 0x4dd074
PHY 0:01 not found
IP-Config: Guessing netmask 255.255.255.0
IP-Config: Complete:
     device=eth0, addr=192.168.1.227, mask=255.255.255.0, gw=255.255.255.255,
     host=192.168.1.227, domain=, nis-domain=(none),
     bootserver=255.255.255.255, rootserver=255.255.255.255, rootpath=
UBIFS: recovery needed
UBIFS: recovery completed
UBIFS: mounted UBI device 0, volume 0, name "filesys"
UBIFS: file system size:   103739392 bytes (101308 KiB, 98 MiB, 817 LEBs)
UBIFS: journal size:       9023488 bytes (8812 KiB, 8 MiB, 72 LEBs)
UBIFS: media format:       w4/r0 (latest is w4/r0)
UBIFS: default compressor: lzo
UBIFS: reserved for root:  0 bytes (0 KiB)
VFS: Mounted root (ubifs filesystem) on device 0:13.
devtmpfs: mounted
Freeing init memory: 216K
Failed to execute /init.  Attempting defaults...
 INIT: version 2.86 booting  
Please wait: booting...
Starting udev
Root filesystem already rw, not remounting
Caching udev devnodes
root: mount: mounting /dev/root on / failed: No such file or directory
Configuring network interfaces... done.
Setting up IP spoofing protection: rp_filter.
rm: cannot remove '/tmp': Device or resource busy
hwclock: RTC_RD_TIME: Remote I/O error
Fri Nov  9 13:44:00 GMT-8 2012
hwclock: RTC_SET_TIME: Remote I/O error
 inside finish.sh  
UBI: attaching mtd5 to ubi1
UBI: physical eraseblock size:   131072 bytes (128 KiB)
UBI: logical eraseblock size:    126976 bytes
UBI: smallest flash I/O unit:    2048
UBI: sub-page size:              512
UBI: VID header offset:          2048 (aligned 2048)
UBI: data offset:                4096
UBI: max. sequence number:       200
UBI: attached mtd5 to ubi1
UBI: MTD device name:            "Data"
UBI: MTD device size:            12 MiB
UBI: number of good PEBs:        96
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: 96
UBI: number of PEBs reserved for bad PEB handling: 2
UBI: max/mean erase counter: 4/2
UBI: image sequence number:  -4315179
UBI: background thread "ubi_bgt1d" started, PID 272
UBI device number 1, total 96 LEBs (12189696 bytes, 11.6 MiB), available 0 LEBs (0 bytes), LEB size 126976 bytes (124.0 KiB)
UBIFS: recovery needed
UBIFS: recovery completed
UBIFS: mounted UBI device 1, volume 0, name "ubifs_volume"
UBIFS: file system size:   10285056 bytes (10044 KiB, 9 MiB, 81 LEBs)
UBIFS: journal size:       1015809 bytes (992 KiB, 0 MiB, 6 LEBs)
UBIFS: media format:       w4/r0 (latest is w4/r0)
UBIFS: default compressor: lzo
UBIFS: reserved for root:  485787 bytes (474 KiB)
UBI: attaching mtd7 to ubi2
UBI: physical eraseblock size:   131072 bytes (128 KiB)
UBI: logical eraseblock size:    126976 bytes
UBI: smallest flash I/O unit:    2048
UBI: sub-page size:              512
UBI: VID header offset:          2048 (aligned 2048)
UBI: data offset:                4096
UBI: max. sequence number:       43
PHY: 0:00 - Link is Up - 1000/Full
UBI: attached mtd7 to ubi2
UBI: MTD device name:            "Reserved"
UBI: MTD device size:            79 MiB
UBI: number of good PEBs:        634
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: 634
UBI: number of PEBs reserved for bad PEB handling: 6
UBI: max/mean erase counter: 7/5
UBI: image sequence number:  2071392193
UBI: background thread "ubi_bgt2d" started, PID 285
UBI device number 2, total 634 LEBs (80502784 bytes, 76.8 MiB), available 0 LEBs (0 bytes), LEB size 126976 bytes (124.0 KiB)
UBIFS: recovery needed
UBIFS: recovery completed
UBIFS: mounted UBI device 2, volume 0, name "ubifs_volume"
UBIFS: file system size:   78090240 bytes (76260 KiB, 74 MiB, 615 LEBs)
UBIFS: journal size:       3936256 bytes (3844 KiB, 3 MiB, 31 LEBs)
UBIFS: media format:       w4/r0 (latest is w4/r0)
UBIFS: default compressor: lzo
UBIFS: reserved for root:  3688395 bytes (3601 KiB)
numid=1,iface=MIXER,name='PCM Playback Volume'
  ; type=INTEGER,access=rw---R--,values=2,min=0,max=127,step=0
  : values=127,127
  | dBscale-min=-63.50dB,step=0.50dB,mute=0
 [c6xdsp ] Remote Debug Shared Memory @ 0xbff00000
 [m3video] Remote Debug Shared Memory @ 0xbff05020
 [m3vpss ] Remote Debug Shared Memory @ 0xbff0a040
SysLink version : 2.21.02.10
SysLink module created on Date:Jan 29 2015 Time:17:22:51
Trace enabled
Trace SetFailureReason enabled
/dev/mem opened.
             Phy Addr : 0x48181560 Data : 0x00000002
          Unhandled fault: external abort on non-linefetch (0x1018) at 0x4021b0e4
   Phy Addr : 0x48180f10 Data : 0x00000000
             Phy Addr : 0x48180508 Data : 0x00000302
             Phy Addr : 0x48180520 Data : 0x00000002
             Phy Addr : 0x48180524 Data : 0x00000002
             Phy Addr : 0x48180528 Data : 0x00000002
             Phy Addr : 0x4c0000e4 Data : 0x00170209
Bus error
Creat queue id:0
queue id:0
FileMngThread created
Creat queue id:32769
queue id:32769
AlramThread created
Share memory init success
IPNC_3.50.00 (root@localhost.localdomain) (gcc version 4.5.3 20110311 (p  
 
  [host]  Setting DMM priority for [ISS     ] to [0] ( 0x4e000634 = 0x00080000 )
 
  [host]  Setting L3 bandwidth regulator for [ISS     ] to [press=[3,3] BW=400, WM Cycles=2500]
queue id:32769
Creat queue id:65538
queue id:65538
Creat queue id:98307
queue id:98307
 
  [host]  Setting L3 bandwidth regulator for [HDVICP0 ] to [press=[0,0] BW=900, WM Cycles=2500]
 
  [host]  Setting DMM priority for [HDVICP0 ] to [1] ( 0x4e000634 = 0x00000009 )
 [c6xdsp ] Remote Debug Shared Memory @ 0xbff00000
 
  [host] Attached to slave procId 0.
 [m3video] Remote Debug Shared Memory @ 0xbff05020
 [m3vpss ] Remote Debug Shared Memory @ 0xbff0a040
 
  [host] Attached to slave procId 1.
 
  [host] Loaded file ./firmware/ipnc_rdk_fw_m3video.xem3 on slave procId 0.
UBIFS error (pid 334): ubifs_decompress: cannot decompress 2325 bytes, compressor lzo, error -22
UBIFS error (pid 334): read_block: bad data node (block 628, inode 3514)
UBIFS error (pid 334): do_readpage: cannot read page 628 of inode 3514, error -22
 
  [host] Started slave procId 0.
 
  [host] After Ipc_loadcallback status [0x00000000]
 
  [host] Loaded file ./firmware/ipnc_rdk_fw_m3vpss.xem3 on slave procId 1.
 
  [host] Started slave procId 1.
 
  [host] After Ipc_loadcallback status [0x00000000]
 [m3video] ***** SYSTEM  : Frequency <ORG> - 200000000, <NEW> - 200000000
 [m3video]   
 [m3video]  *** UTILS: CPU KHz = 400000 Khz ***
 [m3video]   
 [m3video]  75: SYSTEM  : System Common Init in progress !!!
 [m3video]  81: SYSTEM: IPC init in progress !!!
 [m3video]  86: SYSTEM: Attaching to [HOST] ...  
 [m3video]  140: SYSTEM: Attaching to [HOST] ...  
 [m3video]  161: SYSTEM: Attaching to [HOST] ... SUCCESS !!!
 
  [host] After Ipc_startcallback status [0x00000000]
 [m3video]  167: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  222: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  277: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  332: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  387: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  442: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  497: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  552: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  607: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  662: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  717: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  772: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  827: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  882: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  937: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  992: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  1047: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  1102: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  1157: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  1212: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  1267: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  1322: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  1377: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  1432: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  1487: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  1542: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  1597: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  1652: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  1707: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  1762: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  1817: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  1872: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  1927: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  1982: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  2037: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  2092: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  2147: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  2202: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  2257: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  2312: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  2367: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  2422: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  2477: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  2532: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  2587: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  2642: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  2697: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  2752: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  2807: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  2862: SYSTEM: Attaching to [VPSS-M3] ...  
 [m3video]  2917: SYSTEM: Attaching to [VPSS-M3] ...  
 
 
U-Boot 2010.06 (Jun 23 2014 - 19:04:06) DM388_IPNC_3.80.00
 
DM385-GP rev 1.1
 
ARM clk: 600MHz
DDR clk: 533MHz
L3 clk:  200MHz
IVA clk: 450MHz
ISS clk: 400MHz
DSP Default OFF
DSS Default OFF
 
DRAM:  1 GiB
DCACHE:  Off
NAND:  HW ECC BCH8 Selected
256 MiB
Using default environment
 
The 2nd stage U-Boot will now be auto-loaded
Please do not interrupt the countdown till DM385_IPNC prompt if 2nd stage is already flashed
Hit any key to stop autoboot:  0  
 
NAND read: device 0 offset 0x20000, size 0x40000
 262144 bytes read: OK
## Starting application at 0x81000000 ...
 
 
U-Boot 2010.06 (Jun 23 2014 - 19:06:46) DM388_IPNC_3.80.00
 
DM385-GP rev 1.1
 
ARM clk: 600MHz
DDR clk: 533MHz
L3 clk:  200MHz
IVA clk: 450MHz
ISS clk: 400MHz
DSP Default OFF
DSS Default OFF
 
I2C:   ready
DRAM:  1 GiB
DCACHE:  On
NAND:  HW ECC BCH8 Selected
256 MiB
MMC:   OMAP SD/MMC: 0, ON-BOARD SDIO: 1
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@@                                                               @@
@@                                                               @@
@@                                                               @@
@@                                                               @@
@@       _______   __       __   ______    ______    ______      @@
@@      /       \ /  \     /  | /      \  /      \  /      \     @@
@@      $$$$$$$  |$$  \   /$$ |/$$$$$$  |/$$$$$$  |/$$$$$$  |    @@
@@      $$ |  $$ |$$$  \ /$$$ |$$ ___$$ |$$ \__$$ |$$ \__$$ |    @@
@@      $$ |  $$ |$$$$  /$$$$ |  /   $$< $$    $$< $$    $$<     @@
@@      $$ |  $$ |$$ $$ $$/$$ | _$$$$$  | $$$$$$  | $$$$$$  |    @@
@@      $$ |__$$ |$$ |$$$/ $$ |/  \__$$ |$$ \__$$ |$$ \__$$ |    @@
@@      $$    $$/ $$ | $/  $$ |$$    $$/ $$    $$/ $$    $$/     @@
@@      $$$$$$$/  $$/      $$/  $$$$$$/   $$$$$$/   $$$$$$/      @@
@@                                                               @@
@@                                                               @@
@@                                                               @@
@@                                                               @@
@@                                                               @@
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
 
Net:   Ethernet clocking: 0x52
Detected MACID:0:c:c:a0:ff:fa
cpsw
Hit any key to stop autoboot:  3 0  
DM388_IPNC#  
DM388_IPNC#  
DM388_IPNC#

 

 

 

  • Hi Jayakrishnan,

    According the beginning of your issue description - "A reboot doesn't help to recover" I suspect some problem with a flash memory chip or some thermal issue. Could you try to power off (not restart only) and wait for some period of time enough for temperature going down and then test again. If the problem still exists the thermal reason will be ignored.

    BR
    Tsvetolin Shulev