TI814X based hanging with android 2.3 devkit 2.0

Prashant Dhumal

Intellectual 590 points

Other Parts Discussed in Thread: PMP

I have TI814X based own board with 1GB of RAM. The details of main processor chip are as follows-:

TI8148-GP rev 2.1;;;;; part no is:: X8148X3874BCYE 1CZDCL9

I am trying to evaluate Android 2.3 devkit 2.0 on this board.

I have successfully build all the components and prepared the SD card.

The kernel booted successfully. but while loading hdvpss firmware the board just hanged up. Please find the serial port booting logs in attached file.

So I tried to load the frmware by command line by interrupting normal android booting sequence. The board still hanged up.

Following are the serial port debug messages of the command I have executed.

/system/bin/syslink/procmgrapp_release 2 /system/bin/syslink/c6a814x_hdvpss.xem3 0

ProcMgrApp sample application
Entered SysLinkSamples_startup
SysLinkSamples_osStartup
Entered ProcMgrApp_startup
ProcMgr_attach status: [0x0]
After attach: ProcMgr_getState
 state [0x1]
ProcMgr_load status: [0x3046000]
After load: ProcMgr_getState
 state [0x3]
ProcMgr_start passed [0x6a85000]

(board hanged after this)

Please note that I have successfully run ezsdk_dm814x-evm_5_03_01_15 on this board and seen matrix GUI on HDMI display.

Can somebody suggest me what is going wrong.

Regards,

Prashant.

over 13 years ago

0 Pankaj Bharadiya over 13 years ago

TI__Expert 5400 points

HI Prashant,

Can you quickly download prebuilt image from below link and check wether board is booting fine?

http://software-dl.ti.com/dsps/dsps_public_sw/sdo_tii/TI_Android_DevKit/TI_Android_GingerBread_2_3_DevKit_2_0/index_FDS.html

Regards,

Pankaj Bharadiya

0 Prashant Dhumal over 13 years ago in reply to Pankaj Bharadiya

Intellectual 590 points

Thanks Pankaj,

There are no prebuilt images available for TI814X for download on the link provided by you.

But i found prebuilt images in the Devkit tarball and I booted the board with those images but the board is still hanging.

As I mentioned in my previous posts that the board is hanging while loading hdvpss firmware.

and it is hanging in the startcallback done by procmgr binary which is done after loading the firmware.

I suspect the problem is with the shared memory region between media controller and main cortexa8 processor.

If you can provide me the memory map for Android like the one for EZSDK then it will help to diagnose the problem fast.

Pankaj other thing is firmware for HDVPSS is just a elf file and there is absolutely no docs about it like its main functions, its resource utilization,

issues with the firmware. It will be nice if TI make it available, this wll help to solve the issues like this.

Regards,

Prashant.

0 Satish Patel over 13 years ago in reply to Prashant Dhumal

TI__Expert 4390 points

Hi Prashant,

I have already recommend to use latest sources for ti81xx family. ( pardon me if it was not you)

http://code.google.com/p/rowboat/wiki/TI81xxWithMultimediaAcceleration

Sources are verified for both ti814x and ti81xx. Kindly work on that to have better HDVPSS components.

BR,

satish

0 Prashant Dhumal over 13 years ago in reply to Satish Patel

Intellectual 590 points

HI satish,

I downloaded the source from link provided by you and booted the board with compiled sources but still the board is hanging at the same point.

HDVICP2 firmware is getting loaded successfully. Board hangs while loading HDVPSS firmware.

Please note that I have tried with default kernel command line too(which is part of source code).

Pls find the booting logs below.

U-Boot 2010.06 (Feb 11 2012 - 16:01:55)

TI8148-GP rev 2.1

ARM clk: 600MHz
DDR clk: 400MHz

DRAM: 2 GiB
Using default environment

The 2nd stage U-Boot will now be auto-loaded
Please do not interrupt the countdown till TI8148_EVM prompt if 2nd stage is already flashed
Hit any key to stop autoboot: 0
mmc1 is available
reading u-boot.bin

179928 bytes read
## Starting application at 0x80800000 ...

U-Boot 2010.06 (Feb 11 2012 - 16:06:28)

TI8148-GP rev 2.1

ARM clk: 600MHz
DDR clk: 400MHz

I2C:   ready
DRAM: 2 GiB
NAND: HW ECC Hamming Code selected
No NAND device found!!!
0 MiB
*** Warning - bad CRC or NAND, using default environment

                          .:;rrr;;.
                    ,5#@@@@#####@@@@@@#2,
                 ,A@@@hi;;;r5;;;;r;rrSG@@@A,
               r@@#i;:;s222hG;rrsrrrrrr;ri#@@r
             :@@hr:r;SG3ssrr2r;rrsrsrsrsrr;rh@@:
            B@H;;rr;3Hs;rrr;sr;;rrsrsrsrsrsr;;H@B
           @@s:rrs;5#;;rrrr;r#@H:;;rrsrsrsrsrr:s@@
          @@;;srs&X#9;r;r;;,2@@@rrr:;;rrsrsrsrr;;@@
         @@;;rrsrrs@MB#@@@@@###@@@@@@#rsrsrsrsrr;;@@
        G@r;rrsrsr;#X;SX25Ss#@@#M@#9H9rrsrsrsrsrs;r@G
        @9:srsrsrs;2@;:;;:.X@@@@@H::;rrsrsrsrsrsrr:3@
       X@;rrsrsrsrr;XAi;;:&@@#@Bs:rrsrsrsrsrsrsrsrr;@X
       @#;rsrsrsrsrr;r2ir@@@###::rrsrsrsrsrsrsrsrsr:@@
       @A:rrsrsrsrr;:2@29@@M@@@;:;rrrrsrsrsrsrsrsrs;H@
       @&;rsrsrsrr;A@@@@@@###@@@s::;:;;rrsrsrsrsrsr;G@
       @#:rrsrsrsr;G@5Hr25@@@#@@@#9XG9s:rrrrsrsrsrs:#@
       M@;rsrsrsrs;r@&#;::S@@@@@@@M@@@@Grr:;rsrsrsr;@#
       :@s;rsrsrsrr:M#Msrr;;&#@@@@@@@@@@H@@5;rsrsr;s@,
        @@:rrsrsrsr;S@rrrsr;:;r3MH@@#@M5,S@@irrsrr:@@
         @A:rrsrsrsrrrrrsrsrrr;::;@##@r:;rH@h;srr:H@
         ;@9:rrsrsrsrrrsrsrsrsr;,S@Hi@i:;s;MX;rr:h@;
          r@B:rrrrsrsrsrsrsrr;;sA@#i,i@h;r;S5;r:H@r
           ,@@r;rrrsrsrsrsrr;2BM3r:;r:G@:rrr;;r@@,
             B@Mr;rrrrsrsrsr@@S;;;rrr:5M;rr;rM@H
              .@@@i;;rrrrsrs2i;rrrrr;r@M:;i@@@.
                .A@@#5r;;;r;;;rrr;r:r#AsM@@H.
                   ;&@@@@MhXS5i5SX9B@@@@G;
                       :ihM#@@@@@##hs,

Net:   <ethaddr> not set. Reading from E-fuse
Detected MACID:0:18:32:39:7:9c
cpsw
Hit any key to stop autoboot: 0
mmc1 is available
reading boot.scr

384 bytes read
Running bootscript from MMC/SD to set the ENV...
## Executing script at 80900000
mmc1 is available
reading uImage

2581408 bytes read
## Booting kernel from Legacy Image at 80009000 ...
   Image Name:   Linux-2.6.37+
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2581344 Bytes = 2.5 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+ (demo@demo-laptop) (gcc version 4.4.3 (GCC) ) #1 Sat Feb 11 13:57:06 IST 2012
CPU: ARMv7 Processor [413fc082] revision 2 (ARMv7), cr=10c53c7f
CPU: VIPT nonaliasing data cache, VIPT aliasing instruction cache
Machine: ti8148evm
vram size = 52428800 at 0
reserved size = 52428800 at 0
FB: Reserving 52428800 bytes SDRAM for VRAM
Memory policy: ECC disabled, Data cache writeback
OMAP chip is TI8148 2.0
Built 1 zonelists in Zone order, mobility grouping on. Total pages: 52224
Kernel command line: console=ttyO0,115200n8 androidboot.console=ttyO0 rootwait noinitrd init=/init rw mem=256M earlyprintk notifyk.vpssm3_sva=0xBF900000 vram=50M ti81f
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: 206MB = 206MB total
Memory: 202756k/202756k available, 59388k reserved, 0K highmem
Virtual kernel memory layout:
    vector : 0xffff0000 - 0xffff1000   (   4 kB)
    fixmap : 0xfff00000 - 0xfffe0000   ( 896 kB)
    DMA     : 0xffc00000 - 0xffe00000   (   2 MB)
    vmalloc : 0xd0800000 - 0xf8000000   ( 632 MB)
    lowmem : 0xc0000000 - 0xd0000000   ( 256 MB)
    modules : 0xbf000000 - 0xc0000000   ( 16 MB)
      .init : 0xc0008000 - 0xc0038000   ( 192 kB)
      .text : 0xc0038000 - 0xc04d6000   (4728 kB)
      .data : 0xc04d6000 - 0xc0519860   ( 271 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
omap_voltage_early_init: voltage driver support not added
regulator: core version 0.5
regulator: dummy:
NET: Registered protocol family 16
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
registered ti814x_vpss device
registered TI814x on-chip HDMI device
pm_dbg_init: only OMAP3 supported
Registered ti81xx_fb device
bio: create slab <bio-0> at 0
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
omap_i2c omap_i2c.1: bus 1 rev4.0 at 100 kHz
pcf857x: probe of 1-0021 failed with error -121
i2c i2c-1: Failed to register i2c client PCF_8575 at 0x21 (-16)
i2c i2c-1: Can't create device at 0x21
Advanced Linux Sound Architecture Driver Version 1.0.23.
Switching to clocksource gp timer
musb-hdrc: version 6.0, host, debug=0
musb-hdrc musb-hdrc.0: dma type: dma-cppi41
registerd cppi-dma Intr @ IRQ 17
Cppi41 Init Done
musb-hdrc musb-hdrc.0: MUSB HDRC host driver
musb-hdrc musb-hdrc.0: new USB bus registered, assigned bus number 1
usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
usb usb1: Product: MUSB HDRC host driver
usb usb1: Manufacturer: Linux 2.6.37+ musb-hcd
usb usb1: SerialNumber: musb-hdrc.0
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 1 port detected
musb-hdrc musb-hdrc.0: USB Host mode controller at d080c000 using DMA, IRQ 18
musb-hdrc musb-hdrc.1: dma type: dma-cppi41
musb-hdrc musb-hdrc.1: MUSB HDRC host driver
musb-hdrc musb-hdrc.1: new USB bus registered, assigned bus number 2
usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
usb usb2: Product: MUSB HDRC host driver
usb usb2: Manufacturer: Linux 2.6.37+ musb-hcd
usb usb2: SerialNumber: musb-hdrc.1
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 1 port detected
musb-hdrc musb-hdrc.1: USB Host mode controller at d081e800 using DMA, IRQ 19
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.
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
ashmem: initialized
JFFS2 version 2.2. (NAND) �© 2001-2006 Red Hat, Inc.
msgmni has been set to 396
io scheduler noop registered
io scheduler deadline registered
io scheduler cfq registered (default)
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
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
omap_uart.3: ttyO3 at MMIO 0x481a6000 (irq = 44) is a OMAP UART3
omap_uart.4: ttyO4 at MMIO 0x481a8000 (irq = 45) is a OMAP UART4
omap_uart.5: ttyO5 at MMIO 0x481aa000 (irq = 46) is a OMAP UART5
brd: module loaded
loop: module loaded
ahci ahci.0: forcing PORTS_IMPL to 0x1
ahci ahci.0: AHCI 0001.0300 32 slots 1 ports 3 Gbps 0x1 impl platform mode
ahci ahci.0: flags: ncq sntf pm led clo only pmp pio slum part ccc apst
scsi0 : ahci_platform
ata1: SATA max UDMA/133 mmio [mem 0x4a140000-0x4a150fff] port 0x100 irq 16
omap2-nand driver initializing
No NAND device found.
No NAND device found.
davinci_mdio davinci_mdio.0: davinci mdio revision 1.6
davinci_mdio davinci_mdio.0: detected phy mask fffffffc
davinci_mdio.0: probed
davinci_mdio davinci_mdio.0: phy[0]: device 0:00, driver unknown
davinci_mdio davinci_mdio.0: phy[1]: device 0:01, driver unknown
usbcore: registered new interface driver cdc_ether
usbcore: registered new interface driver dm9601
Initializing USB Mass Storage driver...
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
mice: PS/2 mouse device common for all mice
qt602240_ts 1-004a: __qt602240_read_reg: i2c transfer failed
qt602240_ts: probe of 1-004a failed with error -5
i2c /dev entries driver
Linux video capture interface: v2.00
usbcore: registered new interface driver uvcvideo
USB Video Class driver (v1.0.0)
OMAP Watchdog Timer Rev 0x00: initial timeout 60 sec
device-mapper: ioctl: 4.18.0-ioctl (2010-06-29) initialised: dm-devel@redhat.com
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
logger: created 64K log 'log_main'
logger: created 256K log 'log_events'
logger: created 64K log 'log_radio'
logger: created 64K log 'log_system'
notify_init : notify drivercreated for remote proc id 2 at physical Address 0xbf900000
usbcore: registered new interface driver snd-usb-audio
asoc: tlv320aic3x-hifi <-> davinci-mcasp.2 mapping ok
ALSA device list:
#0: TI81XX EVM
TCP cubic registered
NET: Registered protocol family 17
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
Detected MACID=0:0:0:0:0:0
drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
mmc0: new SDHC card at address e624
mmcblk0: mmc0:e624 SD08G 7.40 GiB
mmcblk0: p1 p2 p3
ata1: SATA link down (SStatus 0 SControl 300)
EXT3-fs: barriers not enabled
kjournald starting. Commit interval 5 seconds
EXT3-fs (mmcblk0p2): using internal journal
EXT3-fs (mmcblk0p2): mounted filesystem with writeback data mode
VFS: Mounted root (ext3 filesystem) on device 179:2.
devtmpfs: mounted
Freeing init memory: 192K
init (1): /proc/1/oom_adj is deprecated, please use /proc/1/oom_score_adj instead.
init: cannot find '/system/etc/install-recovery.sh', disabling 'flash_recovery'
# SysLink version : 2.00.02.80
SysLink module created on Date:Feb 11 2012 Time:14:56:44

#
#
#

Please let me know if I am missing on something.

Regards,

Prashant.

384 bytes read
Running bootscript from MMC/SD to set the ENV...
## Executing script at 80900000
mmc1 is available
reading uImage

2581408 bytes read
## Booting kernel from Legacy Image at 80009000 ...
   Image Name:   Linux-2.6.37+
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2581344 Bytes = 2.5 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+ (demo@demo-laptop) (gcc version 4.4.3 (GCC) ) #1 Sat Feb 11 13:57:06 IST 2012
CPU: ARMv7 Processor [413fc082] revision 2 (ARMv7), cr=10c53c7f
CPU: VIPT nonaliasing data cache, VIPT aliasing instruction cache
Machine: ti8148evm
vram size = 52428800 at 0
reserved size = 52428800 at 0
FB: Reserving 52428800 bytes SDRAM for VRAM
Memory policy: ECC disabled, Data cache writeback
OMAP chip is TI8148 2.0
Built 1 zonelists in Zone order, mobility grouping on. Total pages: 52224
Kernel command line: console=ttyO0,115200n8 androidboot.console=ttyO0 rootwait noinitrd init=/init rw mem=256M earlyprintk notifyk.vpssm3_sva=0xBF900000 vram=50M ti81f
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: 206MB = 206MB total
Memory: 202756k/202756k available, 59388k reserved, 0K highmem
Virtual kernel memory layout:
    vector : 0xffff0000 - 0xffff1000   (   4 kB)
    fixmap : 0xfff00000 - 0xfffe0000   ( 896 kB)
    DMA     : 0xffc00000 - 0xffe00000   (   2 MB)
    vmalloc : 0xd0800000 - 0xf8000000   ( 632 MB)
    lowmem : 0xc0000000 - 0xd0000000   ( 256 MB)
    modules : 0xbf000000 - 0xc0000000   ( 16 MB)
      .init : 0xc0008000 - 0xc0038000   ( 192 kB)
      .text : 0xc0038000 - 0xc04d6000   (4728 kB)
      .data : 0xc04d6000 - 0xc0519860   ( 271 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
omap_voltage_early_init: voltage driver support not added
regulator: core version 0.5
regulator: dummy:
NET: Registered protocol family 16
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
registered ti814x_vpss device
registered TI814x on-chip HDMI device
pm_dbg_init: only OMAP3 supported
Registered ti81xx_fb device
bio: create slab <bio-0> at 0
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
omap_i2c omap_i2c.1: bus 1 rev4.0 at 100 kHz
pcf857x: probe of 1-0021 failed with error -121
i2c i2c-1: Failed to register i2c client PCF_8575 at 0x21 (-16)
i2c i2c-1: Can't create device at 0x21
Advanced Linux Sound Architecture Driver Version 1.0.23.
Switching to clocksource gp timer
musb-hdrc: version 6.0, host, debug=0
musb-hdrc musb-hdrc.0: dma type: dma-cppi41
registerd cppi-dma Intr @ IRQ 17
Cppi41 Init Done
musb-hdrc musb-hdrc.0: MUSB HDRC host driver
musb-hdrc musb-hdrc.0: new USB bus registered, assigned bus number 1
usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
usb usb1: Product: MUSB HDRC host driver
usb usb1: Manufacturer: Linux 2.6.37+ musb-hcd
usb usb1: SerialNumber: musb-hdrc.0
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 1 port detected
musb-hdrc musb-hdrc.0: USB Host mode controller at d080c000 using DMA, IRQ 18
musb-hdrc musb-hdrc.1: dma type: dma-cppi41
musb-hdrc musb-hdrc.1: MUSB HDRC host driver
musb-hdrc musb-hdrc.1: new USB bus registered, assigned bus number 2
usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
usb usb2: Product: MUSB HDRC host driver
usb usb2: Manufacturer: Linux 2.6.37+ musb-hcd
usb usb2: SerialNumber: musb-hdrc.1
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 1 port detected
musb-hdrc musb-hdrc.1: USB Host mode controller at d081e800 using DMA, IRQ 19
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.
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
ashmem: initialized
JFFS2 version 2.2. (NAND) �© 2001-2006 Red Hat, Inc.
msgmni has been set to 396
io scheduler noop registered
io scheduler deadline registered
io scheduler cfq registered (default)
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
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
omap_uart.3: ttyO3 at MMIO 0x481a6000 (irq = 44) is a OMAP UART3
omap_uart.4: ttyO4 at MMIO 0x481a8000 (irq = 45) is a OMAP UART4
omap_uart.5: ttyO5 at MMIO 0x481aa000 (irq = 46) is a OMAP UART5
brd: module loaded
loop: module loaded
ahci ahci.0: forcing PORTS_IMPL to 0x1
ahci ahci.0: AHCI 0001.0300 32 slots 1 ports 3 Gbps 0x1 impl platform mode
ahci ahci.0: flags: ncq sntf pm led clo only pmp pio slum part ccc apst
scsi0 : ahci_platform
ata1: SATA max UDMA/133 mmio [mem 0x4a140000-0x4a150fff] port 0x100 irq 16
omap2-nand driver initializing
No NAND device found.
No NAND device found.
davinci_mdio davinci_mdio.0: davinci mdio revision 1.6
davinci_mdio davinci_mdio.0: detected phy mask fffffffc
davinci_mdio.0: probed
davinci_mdio davinci_mdio.0: phy[0]: device 0:00, driver unknown
davinci_mdio davinci_mdio.0: phy[1]: device 0:01, driver unknown
usbcore: registered new interface driver cdc_ether
usbcore: registered new interface driver dm9601
Initializing USB Mass Storage driver...
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
mice: PS/2 mouse device common for all mice
qt602240_ts 1-004a: __qt602240_read_reg: i2c transfer failed
qt602240_ts: probe of 1-004a failed with error -5
i2c /dev entries driver
Linux video capture interface: v2.00
usbcore: registered new interface driver uvcvideo
USB Video Class driver (v1.0.0)
OMAP Watchdog Timer Rev 0x00: initial timeout 60 sec
device-mapper: ioctl: 4.18.0-ioctl (2010-06-29) initialised: dm-devel@redhat.com
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
logger: created 64K log 'log_main'
logger: created 256K log 'log_events'
logger: created 64K log 'log_radio'
logger: created 64K log 'log_system'
notify_init : notify drivercreated for remote proc id 2 at physical Address 0xbf900000
usbcore: registered new interface driver snd-usb-audio
asoc: tlv320aic3x-hifi <-> davinci-mcasp.2 mapping ok
ALSA device list:
#0: TI81XX EVM
TCP cubic registered
NET: Registered protocol family 17
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
Detected MACID=0:0:0:0:0:0
drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
mmc0: new SDHC card at address e624
mmcblk0: mmc0:e624 SD08G 7.40 GiB
mmcblk0: p1 p2 p3
ata1: SATA link down (SStatus 0 SControl 300)
EXT3-fs: barriers not enabled
kjournald starting. Commit interval 5 seconds
EXT3-fs (mmcblk0p2): using internal journal
EXT3-fs (mmcblk0p2): mounted filesystem with writeback data mode
VFS: Mounted root (ext3 filesystem) on device 179:2.
devtmpfs: mounted
Freeing init memory: 192K
init (1): /proc/1/oom_adj is deprecated, please use /proc/1/oom_score_adj instead.
init: cannot find '/system/etc/install-recovery.sh', disabling 'flash_recovery'
# SysLink version : 2.00.02.80
SysLink module created on Date:Feb 11 2012 Time:14:56:44

#
#
#
CTRL-A Z for help |115200 8N1 | NOR | Minicom 2.4    | VT102 |      Offline

0 Prashant Dhumal over 13 years ago in reply to Satish Patel

Intellectual 590 points

Hi TI team,

This is regarding Android on TI8148 custom board with 1GB RAM.

I have downloaded source code from the repository mentioned in the link http://code.google.com/p/rowboat/wiki/TI81xxWithMultimediaAcceleration with rowboat-gingerbread-ti81xx-mc-dsp-snapshot-GMT20110926200120.xml as a software manifest file.

It did compiled successfully and able to prepare a SD card. But when I tried to boot the board, it just hanged while loading hdvpss-M3 firmware, the logs of which I have already posted on e2e forum.

Then I have downloaded syslink_2_10_02_17 which is the latest syslink version tested with Android TI814x platform(as mentioned in the release notes).

I compiled this with android kernel and bionic libc.

WIth this syslink I am able load hdvpss firmware(version 05_02_00_30), ALL the other modules too get loaded successfully.

but somehow Virtual machine is shutting down . Nothing gets displayed on TV screen.

My kernel command line looks like:

setenv bootargs console=ttyO0,115200n8 androidboot.console=ttyO0 rootwait noinitrd init=/init rw mem=364M mem=324M@0x9f900000 earlyprintk notifyk.vpssm3_sva=0xBF900000 vram=50M ti814xfb.vram=0:24M,1:16M,2:6M root=/dev/mmcblk0p2 rootfstype=ext3 ip=off

please find the logcat messages in the attached file.

I will be grateful if anyone can suggest what could be the reason.

Regards,

Prashant.

0 Satish Patel over 13 years ago in reply to Prashant Dhumal

TI__Expert 4390 points

Hi Prashant,

Couple of things...

1. From the logcat, I could see multiple things that would cause this problem. First have you modified any source in android software stack ? specifically increased dalvik virtual memory or so ???

2. Second, which toolchain are you using ?

3. After integrating new HDVPSS and syslink, have you fully done clean build and generated fresh file system ? Because from the logs it says bad magic number, which means some mismatched dalvik VM is running ( with past timestamp). We have obsereved this in one or two times in past.

Kindly try to run clean build and flash fresh sd card and give try

4. Audio flinger is getting died, am not sure issue with audio or because of VM shutting down. But you can test the same by disabling AUDIO flags in /device/ti/ti814xevm/BoardConfig.mk file

BR,

satish

0 Prashant Dhumal over 13 years ago in reply to Satish Patel

Intellectual 590 points

Thanks for the reply.

First have you modified any source in android software stack ? specifically increased dalvik virtual memory or so ???

Ans:- I did couple of things:

1) I integrated syslink_2_10_02_17 into the downloaded source code.

2) I changed boot args to increase linux memory. Th exact command line is-:

console=ttyO0,115200n8 androidboot.console=ttyO0 rootwait noinitrd init=/init rw mem=364M mem=324M@0x9f900000 earlyprintk notifyk.vpssm3_sva=0xBF900000 vram=50M ti814xfb.vram=0:24M,1:16M,2:6M root=/dev/mmcblk0p2 rootfstype=ext3 ip=off

Specifically I did not touch any dalvik specific code.

which toolchain are you using ?

Ans: The toolchain which I have used is part of source code.

arm-eabi- with GCC version of 4.4.3.

I will try to clean the build and regenerate the whole filesystem again.

Regards,

Prashant.

0 Prashant Dhumal over 13 years ago in reply to Satish Patel

Intellectual 590 points

Hi Satish,

We did cleaned up source and recompiled the complete code.

With the new images we are able to boot the board and see the boot animation.

But after that nothing comes up on the screen. From the serial port dump it seems that

mediaserver is crashing. Please find the attached serial port dump.

The build components are as follows-:

syslink-: 2_10_02_17

UBOOT-:2010.06-psp04.01.00.06.patch1(as taken from EZSDK 5_03_01_15)

kernel -: Same as downloaded from the repository.

HDVPSS firmware version is 05_02_00_30(as taken from EZSDK 5_03_01_15)

HDVICP-: not loaded.

Please let me know what could be problem.

Regards,

prashant.

0 Satish Patel over 13 years ago in reply to Prashant Dhumal

TI__Expert 4390 points

Hi Prashant,

First good news.. atleast you are one step ahead.

1. Could your provide full logcat details ? Is is showing some memory issues ?

2. You mentioned - "HDVICP is not loaded" - could clarify the same

3. Are you using LCD output or HDMI out for display...

BR,

satish

0 Prashant Dhumal over 13 years ago in reply to Satish Patel

Intellectual 590 points

Thanks satish,

I had complete android successful boot now.

I am using HDMI out for display

But one thing the starting image is just a CIF size(just) its not fullscreen

Can you tell me how to I make it fullscreen.

Regards,

Prashant.

0 Satish Patel over 13 years ago in reply to Prashant Dhumal

TI__Expert 4390 points

Hi Prashant,

Do you mean by boot up logo ? if yes then you can refer below link to change it

http://www.addictivetips.com/mobile/how-to-change-customize-create-android-boot-animation-guide/

http://e2e.ti.com/support/embedded/android/f/509/t/127718.aspx

BR,

satish

0 Hong0820 over 13 years ago in reply to Prashant Dhumal

Prodigy 95 points

Hi Prashant,

I'm using TI81xxWithMultimediaAcceleration on my DM8148 evm,
following the steps as it says, everything works fine.

Unfortunately when I trying to use the second segment of memory and add parameters into bootags as below,

setenv bootargs console=ttyO0,115200n8 androidboot.console=ttyO0 rootwait noinitrd init=/init rw mem=364M mem=324@0x9f900000 earlyprintk notifyk.vpssm3_sva=0xBF900000 vram=16M root=/dev/mmcblk0p2 rootfstype=ext3 ip=off

I always got a core dump druing kernel booting...

SysLink version : 2.00.02.80
SysLink module created on Date:Mar 27 2012 Time:16:11:19
HDMI W1 rev 4.0
warning: `zygote' uses 32-bit capabilities (legacy support in use)
alarm_set_rtc: no RTC, time will be lost on reboot
vmap allocation for size 197136384 failed: use vmalloc=<size> to increase size.
Unable to handle kernel paging request at virtual address 40000000
pgd = ef190000
[40000000] *pgd=af16e031, *pte=00000000, *ppte=00000000
Internal error: Oops: 17 [#1]
last sysfs file: /sys/power/state
Modules linked in: omaplfb pvrsrvkm ti81xxhdmi ti81xxvo ti81xxfb vpss syslink
CPU: 0 Not tainted (2.6.37+ #4)
PC is at HeapMemMP_openByAddr+0x1f4/0x2f0 [syslink]
LR is at SharedRegion_isCacheEnabled+0x144/0x17c [syslink]
pc : [<bf0501fc>] lr : [<bf0379f0>] psr: 60000013
sp : ee831e00 ip : 00000000 fp : ee831e3c
r10: f0abf000 r9 : 00000048 r8 : ee831ec8
r7 : 00000000 r6 : 40000000 r5 : f0abf068 r4 : bf0bf804
r3 : 00000000 r2 : bf0a19e9 r1 : 00000000 r0 : 00000000
Flags: nZCv IRQs on FIQs on Mode SVC_32 ISA ARM Segment user
Control: 10c5387d Table: af190019 DAC: 00000015

SP: 0xee831d80:
1d80 bf03354c bf029990 00000000 f0ac5000 bf0ef7e4 f0ac5000 ffffffff ee831dec
1da0 40000000 00000000 ee831e3c ee831db8 c03a0cac c0038274 00000000 00000000
1dc0 bf0a19e9 00000000 bf0bf804 f0abf068 40000000 00000000 ee831ec8 00000048
1de0 f0abf000 ee831e3c 00000000 ee831e00 bf0379f0 bf0501fc 60000013 ffffffff
1e00 f0abf068 00000000 ee831e3c 00000000 00000000 40000000 00000000 00000000
1e20 f0abf048 00000002 00000000 00000000 ee831e94 ee831e40 bf039e88 bf050014
1e40 ee831ec8 c00a1880 4f200000 00000000 bf0ef7e4 00000000 40000000 bf0ef7e4
1e60 ee831e94 ee831e70 bf02aa84 406bfa54 c024f2a0 c024f2a0 00000016 00000000

FP: 0xee831dbc:
1dbc 00000000 bf0a19e9 00000000 bf0bf804 f0abf068 40000000 00000000 ee831ec8
1ddc 00000048 f0abf000 ee831e3c 00000000 ee831e00 bf0379f0 bf0501fc 60000013
1dfc ffffffff f0abf068 00000000 ee831e3c 00000000 00000000 40000000 00000000
1e1c 00000000 f0abf048 00000002 00000000 00000000 ee831e94 ee831e40 bf039e88
1e3c bf050014 ee831ec8 c00a1880 4f200000 00000000 bf0ef7e4 00000000 40000000
1e5c bf0ef7e4 ee831e94 ee831e70 bf02aa84 406bfa54 c024f2a0 c024f2a0 00000016
1e7c 00000000 ee830000 00000000 ee831f0c ee831e98 bf07c2d4 bf039b54 c024f2a0
1e9c 406bfa54 ee831ed4 ee831eb0 c0063a70 c01b6994 ef8385b0 00013e7d 00013a7d

Then I realize I should set HIGHMEM support in kernel menuconfig first,
but I just got another problem and there's nothing on my screen

ALSA device list:
#0: TI81XX EVM
TCP cubic registered
NET: Registered protocol family 17
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
Detected MACID=0:0:0:0:0:0
drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
usb 1-1: new high speed USB device using musb-hdrc and address 2
mmc0: new SDHC card at address e624
mmcblk0: mmc0:e624 SD04G 3.69 GiB
mmcblk0: p1 p2 p3
ata1: SATA link down (SStatus 0 SControl 300)
EXT3-fs: barriers not enabled
kjournald starting. Commit interval 5 seconds
EXT3-fs (mmcblk0p2): warning: maximal mount count reached, running e2fsck is recommended
usb 1-1: New USB device found, idVendor=1a40, idProduct=0101
usb 1-1: New USB device strings: Mfr=0, Product=1, SerialNumber=0
usb 1-1: Product: USB 2.0 Hub
hub 1-1:1.0: USB hub found
hub 1-1:1.0: 4 ports detected
EXT3-fs (mmcblk0p2): using internal journal
EXT3-fs (mmcblk0p2): mounted filesystem with writeback data mode
VFS: Mounted root (ext3 filesystem) on device 179:2.
devtmpfs: mounted
Freeing init memory: 192K
init (1): /proc/1/oom_adj is deprecated, please use /proc/1/oom_score_adj instead.
usb 1-1.2: new full speed USB device using musb-hdrc and address 3
usb 1-1.2: New USB device found, idVendor=046d, idProduct=c52b
usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
usb 1-1.2: Product: USB Receiver
usb 1-1.2: Manufacturer: Logitech
input: Logitech USB Receiver as /devices/platform/musb-ti81xx.0/musb-hdrc.0/usb1/1-1/1-1.2/1-1.2:1.0/input/input0
generic-usb 0003:046D:C52B.0001: input: USB HID v1.11 Keyboard [Logitech USB Receiver] on usb-musb-hdrc.0-1.2/input0
input: Logitech USB Receiver as /devices/platform/musb-ti81xx.0/musb-hdrc.0/usb1/1-1/1-1.2/1-1.2:1.1/input/input1
generic-usb 0003:046D:C52B.0002: input: USB HID v1.11 Mouse [Logitech USB Receiver] on usb-musb-hdrc.0-1.2/input1
generic-usb 0003:046D:C52B.0003: claimed by neither input, hiddev nor hidraw
init: cannot find '/system/etc/install-recovery.sh', disabling 'flash_recovery'
# SysLink version : 2.00.02.80
SysLink module created on Date:Mar 27 2012 Time:16:11:19
HDMI W1 rev 4.0
pvrsrvkm: disagrees about version of symbol __alloc_pages_nodemask
pvrsrvkm: Unknown symbol __alloc_pages_nodemask (err -22)
pvrsrvkm: disagrees about version of symbol contig_page_data
pvrsrvkm: Unknown symbol contig_page_data (err -22)
omaplfb: Unknown symbol PVRGetDisplayClassJTable (err 0)
warning: `zygote' uses 32-bit capabilities (legacy support in use)
alarm_set_rtc: no RTC, time will be lost on reboot
request_suspend_state: wakeup (3->0) at 17737466503 (1970-01-02 00:00:00.878852200 UTC)
init: untracked pid 61 exited
request_suspend_state: wakeup (0->0) at 24263015403 (1970-01-02 00:00:07.404401550 UTC)
init: untracked pid 107 exited
request_suspend_state: wakeup (0->0) at 29758139853 (1970-01-02 00:00:12.899526300 UTC)
init: untracked pid 123 exited
request_suspend_state: wakeup (0->0) at 35293960503 (1970-01-02 00:00:18.435346700 UTC)
init: untracked pid 139 exited

I Found you have set all linux memory in use,

could you help me to figure out that's going on here? Thank you in advance.

Hong

0 Vishveshwar Bhat over 13 years ago in reply to Hong0820

TI__Genius 10210 points

Hong0820 said:

pvrsrvkm: disagrees about version of symbol __alloc_pages_nodemask
pvrsrvkm: Unknown symbol __alloc_pages_nodemask (err -22)
pvrsrvkm: disagrees about version of symbol contig_page_data
pvrsrvkm: Unknown symbol contig_page_data (err -22)
omaplfb: Unknown symbol PVRGetDisplayClassJTable (err 0)
warning: `zygote' uses 32-bit capabilities (legacy support in use)

This is probably because you did not rebuild SGX components after rebuilding the kernel.

Please rebuild SGX and other kernel modules against the updated kernel build and try again.

0 Prashant Dhumal over 13 years ago in reply to Hong0820

Intellectual 590 points

Your problem seems to be of vmalloc allocation because of which you are getting oops.

try to use following kernel command line.(If You have 1GB of RAM)

console=ttyO0,115200n8 androidboot.console=ttyO0 rootwait noinitrd init=/init rw mem=364M mem=256M@0x9f900000 earlyprintk notifyk.vpssm3_sva=0xBF900000 vram=50M ti814xfb.vram=0:24M,1:16M,2:6M vmalloc=500M root=/dev/mmcblk0p2 rootfstype=ext3 ip=off

With vmalloc=500. you may not be able to use actual RAM completely, in that case you have to enable HIGHMEM support.

But with HIGHMEM I am not sure all your application behave properly.

So my suggestion is first disable HIGHMEM and use above bootargs your first error (vmalloc allocation failed) will vanish.

Then you need to compile your prvsrvkm driver properly as suggested by Mr. Bhat.

With these two things u should be able to see atleast boot animation.

Then you can carefully can experiment with HIGHMEM.

Regards,

Prashant.

0 Hong0820 over 13 years ago in reply to Prashant Dhumal

Prodigy 95 points

Hi,

Thank you for your quick responses.
After following your hints, my board can now have more memory and seems work fine.
I use bootargs as Prashant provided and build kernel with HIGHMEM,
Now I can have memory up to 572MB.

# cat /proc/meminfo
MemTotal:         572520 kB
MemFree:          305768 kB
Buffers:            2964 kB
Cached:           100492 kB
SwapCached:            0 kB

But I just don't know how vmalloc effect the system memory,
when I build kernel without HIGHMEM,
the system memory comes back to 363MB even I have vmalloc=500M in bootargs

# cat /proc/meminfo
MemTotal:         363676 kB
MemFree:          136188 kB
Buffers:            2128 kB
Cached:            73836 kB
SwapCached:            0 kB

My experience in setting up Ubuntu on DM8148EVM,
using mem=364 mem=324@0x9f900000 and without vmalloc=500 in bootargs,
I can have total memory about 700MB.
Is it just because the difference between Android and Ubuntu?

Another question, I just want to run a problem on Andorid,
not matter how I setup the memory(572MB or 363MB),
the results all lead to OOM as message below...

I/dalvikvm-heap( 394): Grow heap (frag case) to 7.125MB for 606224-byte allocation
D/dalvikvm( 394): GC_FOR_MALLOC freed 0K, 61% free 3550K/9095K, external 1308K/1820K, paused 28ms
D/dalvikvm( 394): GC_CONCURRENT freed 0K, 61% free 3550K/9095K, external 1308K/1820K, paused 3ms+3ms
D/dalvikvm( 394): GC_FOR_MALLOC freed 1185K, 68% free 2959K/9095K, external 947K/1228K, paused 27ms
D/dalvikvm( 394): GC_CONCURRENT freed 396K, 68% free 2992K/9095K, external 737K/1228K, paused 3ms+4ms
D/dalvikvm( 394): GC_EXTERNAL_ALLOC freed 100K, 68% free 2959K/9095K, external 716K/1228K, paused 37ms
D/dalvikvm( 394): GC_FOR_MALLOC freed <1K, 68% free 2958K/9095K, external 4772K/5959K, paused 27ms
I/dalvikvm-heap( 394): Forcing collection of SoftReferences for 4153456-byte allocation
D/dalvikvm( 394): GC_FOR_MALLOC freed <1K, 68% free 2958K/9095K, external 4772K/5959K, paused 27ms
E/dalvikvm-heap( 394): Out of memory on a 4153456-byte allocation.
I/dalvikvm( 394): "GLThread 12" prio=5 tid=11 RUNNABLE
I/dalvikvm( 394):   | group="main" sCount=0 dsCount=0 obj=0x406d94c0 self=0x215858
I/dalvikvm( 394):   | sysTid=404 nice=0 sched=0/0 cgrp=[fopen-error:2] handle=2185616
I/dalvikvm( 394):   at com.ansca.corona.NativeToJavaBridge.getBitmapAsset(NativeToJavaBridge.java:~759)
I/dalvikvm( 394):   at com.ansca.corona.NativeToJavaBridge.callGetBitmapAsset(NativeToJavaBridge.java:985)
I/dalvikvm( 394):   at com.ansca.corona.JavaToNativeShim.nativeResize(Native Method)
I/dalvikvm( 394):   at com.ansca.corona.JavaToNativeShim.resize(JavaToNativeShim.java:147)
I/dalvikvm( 394):   at com.ansca.corona.CoronaRenderer.onSurfaceChanged(CoronaRenderer.java:37)
I/dalvikvm( 394):   at android.opengl.derived.SwapGLSurfaceView$GLThread.guardedRun(SwapGLSurfaceView.java:908)
I/dalvikvm( 394):   at android.opengl.derived.SwapGLSurfaceView$GLThread.run(SwapGLSurfaceView.java:773)
I/dalvikvm( 394):
I/System.out( 394): getBitmapAsset: Ran out of memory in the Java VM loading an image (slot/sim_anim01.png) of size 1018x1020
I/Corona ( 394): Lua Runtime Error: lua_pcall failed with status: 2, error message is: ERROR: Invalid parameter passed to sprite.newSpriteSheetFromData(). Frame overlaps sprite sheet.

Could you help to give me some hints?
Still have no any idea about this. Thank you again.

Hong

0 Prashant Dhumal over 13 years ago in reply to Hong0820

Intellectual 590 points

Hi,

Your problem seems to be that dalvik vm is not getting sufficient heap.

I will suggest you to remove all unnecessary application which you dont need.

Secondly, try adding following lines in build.prop file.

dalvik.vm.heapstartsize=5m
dalvik.vm.heapgrowthlimit=16m
dalvik.vm.heapsize=64m

This will help, but increasing heap of dalvik vm has some disadvantages.

To understand points related to RAM utilization and HIGHMEM support following link will be helpful.

http://processors.wiki.ti.com/index.php/DM814x_AM387x_PSP_04.01.00.07_Feature_Performance_Guide

Regards,

Prashant.

Processors

Processors forum

TI814X based hanging with android 2.3 devkit 2.0