• State Resolved
  • Locked Locked
  • Replies 17 replies
  • Subscribers 97 subscribers
  • Views 1634 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

Android Hangs up after displaying "Android" image

vetri vel
Prodigy 170 points
Other Parts Discussed in Thread: DM3730

Hi,

We are porting Android froyo 2.2 on BeagleBoard XM Rev B.

We built system.img and created root filesystem using instruction in the TI site.

While booting, the system hangs up after displaying " ANDROID"  image.

Below is the log details,

Texas Instruments X-Loader 1.47 (Jan 14 2011 - 15:43:37)
Unsupported Chip!
Beagle xM Rev A
Starting X-loader on MMC
Reading boot sector

208660 Bytes Read from MMC
Starting OS Bootloader from MMC...
Starting OS Bootloader...


U-Boot 2010.06 (Jan 14 2011 - 15:46:27)

OMAP34xx/35xx-GP ES2.0, CPU-OPP2 L3-165MHz
OMAP3 Beagle board + LPDDR/NAND
I2C:   ready
DRAM:  384 MiB
NAND:  0 MiB
*** Warning - bad CRC or NAND, using default environment

In:    serial
Out:   serial
Err:   serial
Beagle xM Rev A
Die ID #1f8200011ff00000015739eb0a01e012
Hit any key to stop autoboot:  0
mmc1 is available
reading boot.scr

415 bytes read
Running bootscript from mmc ...
## Executing script at 82000000
reading uImage

2618432 bytes read
***** Kernel: /dev/mmcblk0p1/uImage *****
***** RootFS: /dev/mmcblk0p2 *****
## Booting kernel from Legacy Image at 80200000 ...
   Image Name:   Linux-2.6.32
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2618368 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.32 (a0393957@swubn01) (gcc version 4.4.0 (GCC) ) #4 Wed Jan 19 15:12:38 IST 2011
CPU: ARMv7 Processor [413fc082] revision 2 (ARMv7), cr=10c53c7f
CPU: VIPT nonaliasing data cache, VIPT nonaliasing instruction cache
Machine: OMAP3 Beagle Board
Memory policy: ECC disabled, Data cache writeback
OMAP3630/DM3730 ES1.0 (l2cache iva sgx neon isp 192mhz_clk )
SRAM: Mapped pa 0x40200000 to va 0xfe400000 size: 0x100000
Reserving 4194304 bytes SDRAM for VRAM
Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 65024
Kernel command line: console=ttyS2,115200n8 androidboot.console=ttyS2 mem=256M root=/dev/mmcblk0p2 r
w rootfstype=ext3 rootdelay=1 init=/init ip=off mpurate=800 omap_vout.vid1_static_vrfb_alloc=y
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: 256MB = 256MB total
Memory: 249856KB available (4532K code, 825K data, 172K init, 0K highmem)
Hierarchical RCU implementation.
NR_IRQS:402
Clocking rate (Crystal/Core/MPU): 26.0/664/600 MHz
Reprogramming SDRC clock to 664000000 Hz
dpll3_m2_clk rate change failed: -22
GPMC revision 5.0
IRQ: Found an INTC at 0xfa200000 (revision 4.0) with 96 interrupts
Total of 96 interrupts on 1 active controller
OMAP GPIO hardware version 2.5
OMAP clockevent source: GPTIMER12 at 32768 Hz
Console: colour dummy device 80x30
Calibrating delay loop... 506.27 BogoMIPS (lpj=1978368)
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
regulator: core version 0.5
NET: Registered protocol family 16
Found NAND on CS0
Registering NAND on CS0
Unable to get DVI reset GPIO
Target VDD1 OPP = 3, VDD2 OPP = 2
OMAP DMA hardware revision 5.0
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
i2c_omap i2c_omap.1: bus 1 rev4.0 at 2600 kHz
twl4030: PIH (irq 7) chaining IRQs 368..375
twl4030: power (irq 373) chaining IRQs 376..383
twl4030: gpio (irq 368) chaining IRQs 384..401
regulator: VUSB1V5: 1500 mV normal standby
regulator: VUSB1V8: 1800 mV normal standby
regulator: VUSB3V1: 3100 mV normal standby
twl4030_usb twl4030_usb: Initialized TWL4030 USB module
regulator: VMMC1: 1850 <--> 3150 mV normal standby
regulator: VDAC: 1800 mV normal standby
regulator: VPLL2: 1800 mV normal standby
regulator: VSIM: 1800 <--> 3000 mV normal standby
regulator: VAUX3: 1800 mV normal standby
regulator: VAUX4: 1800 mV normal standby
i2c_omap i2c_omap.2: bus 2 rev4.0 at 400 kHz
i2c_omap i2c_omap.3: bus 3 rev4.0 at 100 kHz
Switching to clocksource 32k_counter
musb_hdrc: version 6.0, musb-dma, otg (peripheral+host), debug=0
musb_hdrc: USB OTG mode controller at fa0ab000 using DMA, IRQ 92
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.
omap-iommu omap-iommu.0: isp registered
NetWinder Floating Point Emulator V0.97 (double precision)
ashmem: initialized
VFS: Disk quotas dquot_6.5.2
Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
JFFS2 version 2.2. (NAND) © 2001-2006 Red Hat, Inc.
yaffs Jan 19 2011 15:03:57 Installing.
msgmni has been set to 488
alg: No test for stdrng (krng)
io scheduler noop registered
io scheduler deadline registered
io scheduler cfq registered (default)
OMAP DSS rev 2.0
OMAP DISPC rev 3.0
OMAP VENC rev 2
Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
serial8250.0: ttyS0 at MMIO 0x4806a000 (irq = 72) is a ST16654
serial8250.1: ttyS1 at MMIO 0x4806c000 (irq = 73) is a ST16654
serial8250.2: ttyS2 at MMIO 0x49020000 (irq = 74) is a ST16654
console [ttyS2] enabled
brd: module loaded
loop: module loaded
usbcore: registered new interface driver asix
usbcore: registered new interface driver cdc_ether
usbcore: registered new interface driver cdc_eem
usbcore: registered new interface driver dm9601
usbcore: registered new interface driver smsc95xx
usbcore: registered new interface driver gl620a
usbcore: registered new interface driver net1080
usbcore: registered new interface driver plusb
usbcore: registered new interface driver rndis_host
usbcore: registered new interface driver cdc_subset
usbcore: registered new interface driver zaurus
usbcore: registered new interface driver MOSCHIP usb-ethernet driver
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
ehci-omap ehci-omap.0: OMAP-EHCI Host Controller
ehci-omap ehci-omap.0: new USB bus registered, assigned bus number 1
ehci-omap ehci-omap.0: irq 77, io mem 0x48064800
ehci-omap ehci-omap.0: USB 2.0 started, EHCI 1.00
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 3 ports detected
Initializing USB Mass Storage driver...
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
android init
android_probe pdata: c04d153c
android_bind
android_usb gadget: android_usb ready
musb_hdrc musb_hdrc: MUSB HDRC host driver
musb_hdrc musb_hdrc: new USB bus registered, assigned bus number 2
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 1 port detected
f_adb init
android_register_function adb
adb_bind_config
f_mass_storage init
android_register_function usb_mass_storage
mice: PS/2 mouse device common for all mice
input: gpio-keys as /devices/platform/gpio-keys/input/input0
i2c /dev entries driver
Linux video capture interface: v2.00
mt9v113 2-003c: Registered to v4l2 master omap34xxcam!!
omap-iommu omap-iommu.0: isp: version 1.1
OMAP Watchdog Timer Rev 0x31: initial timeout 60 sec
mmci-omap-hs mmci-omap-hs.1: err -16 configuring card detect
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'
Advanced Linux Sound Architecture Driver Version 1.0.21.
usbcore: registered new interface driver snd-usb-audio
usb 1-2: new high speed USB device using ehci-omap and address 2
No device for DAI omap-mcbsp-dai-0
No device for DAI omap-mcbsp-dai-1
No device for DAI omap-mcbsp-dai-2
No device for DAI omap-mcbsp-dai-3
No device for DAI omap-mcbsp-dai-4
OMAP3 Beagle SoC init
asoc: twl4030 <-> omap-mcbsp-dai-0 mapping ok
ALSA device list:
  #0: omap3beagle (twl4030)
TCP cubic registered
NET: Registered protocol family 17
NET: Registered protocol family 15
Power Management for TI OMAP3.
Unable to set L3 frequency (400000000)
Switched to new clocking rate (Crystal/Core/MPU): 26.0/664/800 MHz
IVA2 clocking rate: 660 MHz
SmartReflex driver initialized
omap3beaglelmb: Driver registration complete
VFP support v0.3: implementor 41 architecture 3 part 30 variant c rev 3
omapdss DPI: Could not find exact pixel clock. Requested 23500 kHz, got 24000 kHz
regulator_init_complete: incomplete constraints, leaving VAUX3 on
regulator_init_complete: incomplete constraints, leaving VDVI on
regulator_init_complete: incomplete constraints, leaving VDAC on
drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
mt9v113 2-003c: chip id mismatch read 0x0,                               expecting 0x2280
mt9v113 2-003c: Unable to detect decoder
mt9v113 2-003c: chip id mismatch read 0x0,                               expecting 0x2280
mt9v113 2-003c: Unable to detect decoder
mt9v113 2-003c: chip id mismatch read 0x0,                               expecting 0x2280
mt9v113 2-003c: Unable to detect decoder
mt9v113 2-003c: chip id mismatch read 0x0,                               expecting 0x2280
mt9v113 2-003c: Unable to detect decoder
omapdss DPI error: display already enabled
omap_vout omap_vout: 'dvi' Display already enabled
omapdss DPI error: display already enabled
omap_vout omap_vout: 'dvi' Display already enabled
omap_vout omap_vout: Buffer Size = 3686400
omap_vout omap_vout: : registered and initialized video device 0
omap_vout omap_vout: Buffer Size = 3686400
omap_vout omap_vout: : registered and initialized video device 1
hub 1-2:1.0: USB hub found
hub 1-2:1.0: 5 ports detected
Waiting 1sec before mounting root device...
mmc0: host does not support reading read-only switch. assuming write-enable.
mmc0: new high speed SDHC card at address e98d
mmcblk0: mmc0:e98d SU04G 3.69 GiB
 mmcblk0: p1 p2 p3
usb 1-2.1: new high speed USB device using ehci-omap and address 3
smsc95xx v1.0.4
usb0: register 'smsc95xx' at usb-ehci-omap.0-2.1, smsc95xx USB 2.0 Ethernet, 4a:48:d4:6a:9d:9e
usb 1-2.2: new low speed USB device using ehci-omap and address 4
input: GASIA GASIA USB KB Pro as /devices/platform/ehci-omap.0/usb1/1-2/1-2.2/1-2.2:1.0/input/input1
generic-usb 0003:0E8F:0021.0001: input: USB HID v1.10 Keyboard [GASIA GASIA USB KB Pro] on usb-ehci-
omap.0-2.2/input0
input: GASIA GASIA USB KB Pro as /devices/platform/ehci-omap.0/usb1/1-2/1-2.2/1-2.2:1.1/input/input2
generic-usb 0003:0E8F:0021.0002: input: USB HID v1.10 Device [GASIA GASIA USB KB Pro] on usb-ehci-om
ap.0-2.2/input1
kjournald starting.  Commit interval 5 seconds
EXT3-fs (mmcblk0p2): warning: maximal mount count reached, running e2fsck is recommended
EXT3-fs (mmcblk0p2): using internal journal
EXT3-fs (mmcblk0p2): recovery complete
EXT3-fs (mmcblk0p2): mounted filesystem with writeback data mode
VFS: Mounted root (ext3 filesystem) on device 179:2.
Freeing init memory: 172K
Warning: unable to open an initial console.
init: cannot open '/initlogo.rle'
init: cannot find '/system/bin/sgx/rc.pvr', disabling 'pvr'
init: cannot find '/system/etc/install-recovery.sh', disabling 'flash_recovery'
# warning: `rild' uses 32-bit capabilities (legacy support in use)
enabling adb
adb_open
request_suspend_state: wakeup (3->0) at 14060791018 (1970-01-01 00:00:14.060791018 UTC)
init: untracked pid 828 exited
request_suspend_state: wakeup (0->0) at 18278930667 (1970-01-01 00:00:18.278900149 UTC)
init: untracked pid 901 exited
request_suspend_state: wakeup (0->0) at 23293701175 (1970-01-01 00:00:23.293701175 UTC)
init: untracked pid 929 exited
request_suspend_state: wakeup (0->0) at 28292114260 (1970-01-01 00:00:28.292114260 UTC)
init: untracked pid 957 exited
request_suspend_state: wakeup (0->0) at 33269226077 (1970-01-01 00:00:33.269195560 UTC)
init: untracked pid 985 exited

 

we also attached logcat.

Please help.

 

Regards,

G.Vetrivel.

 

2313.android_error_3.txt

 

 

 

  • 0
    TI__Expert 5400 points

    Hi,

    Did you try with our prebuilt image?

    You can download prebuilt image from

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

    vetri vel said:
    init: cannot find '/system/bin/sgx/rc.pvr', disabling 'pvr'
    init: cannot find '/system/etc/install-recovery.sh', disabling 'flash_recovery

    I think you have not installed SGX libraries.

    Please install SGX libraries and try again and make sure that you are having following lines in your init.rc file.

        setprop hw.nobattery true
        setprop hw.nophone true

     

    Regards,

    Pankaj Bharadiya

  • 0 in reply to Pankaj Bharadiya
    Prodigy 170 points

    Dear Pankaj,

    Kindly guide us how to install SGX libraries.

     

    Regards,

    G.Vetrivel.

     

     

  • 0 in reply to vetri vel
    TI__Expert 5400 points

    Hi,

    As you are using FroYo2.2, you can follow procedure mentioned in below wiki page to install SGX libraries.

    http://code.google.com/p/rowboat/wiki/ConfigureAndBuild#Install_the_Android_Graphics_SGX_SDK_on_Host_Machine

     

    Regards,

    Pankaj Bharadiya

  • 0 in reply to Pankaj Bharadiya
    Prodigy 170 points

    Dear Pankaj,

     Thanks for your information. we have installed sgx library but still we are getting same error. we have attached log and log cat attachment.

    5140.logs.txt

    8030.logcat.txt

    Thanks and Regards,

    Vetrivel

  • 0 in reply to vetri vel
    TI__Expert 5400 points

    Hi Vetrivel,

    Your logcat output shows following error.

    I/SurfaceFlinger(  893): SurfaceFlinger's main thread ready to run. Initializing
     graphics H/W...
    E/FramebufferNativeWindow(  893): couldn't open framebuffer HAL (No such device)
    D/libEGL  (  893): loaded /system/lib/egl/libGLES_android.so
    D/libEGL  (  893): loaded /system/lib/egl/libEGL_POWERVR_SGX530_121.so

    Which means sgx libraries might not have installed properly.  

    What command are you using to install sgx libraries? For Beagleboard-XM, correct command is 
    $make install OMAPES=5.x

    Please provide output for lsmod command.

    Please try with our pre-built Image and let us know the result. You can download pre-built image from below link.
    http://software-dl.ti.com/dsps/dsps_public_sw/sdo_tii/TI_Android_DevKit/02_02_00/index_FDS.html


    Regards,
    Pankaj Bharadiya
  • 0 in reply to Pankaj Bharadiya
    TI__Expert 5400 points

     

    Pankaj Bharadiya said:
    What command are you using to install sgx libraries? For Beagleboard-XM, correct command is
    $make install OMAPES=3.x

    Command edited : Correct command is

    make install OMAPES=5.x

  • 0 in reply to Pankaj Bharadiya
    Prodigy 170 points

    Hi Pankaj,

    The prebuilt images from your site is working fine.

    While building the sgx library, the following error occurs,

    root@Ubundu-Android:/home/jasminuser/SGX_sdk/OMAP35x_Android_Graphics_SDK_3_01_00_03# make
    building the sgx kernel modules...
    make[1]: Entering directory `/home/jasminuser/SGX_sdk/OMAP35x_Android_Graphics_SDK_3_01_00_03/GFX_Linux_KM/eurasiacon/build/linux/omap3630_android/kbuild'
    +/home/jasminuser/SGX_sdk/OMAP35x_Android_Graphics_SDK_3_01_00_03/GFX_Linux_KM/services4/srvkm/env/linux
      Building modules, stage 2.
      MODPOST 1 modules
     Copying pvrsrvkm.ko to /home/jasminuser/SGX_sdk/OMAP35x_Android_Graphics_SDK_3_01_00_03/GFX_Linux_KM/eurasiacon/binary_omap3630_android_release
    +/home/jasminuser/SGX_sdk/OMAP35x_Android_Graphics_SDK_3_01_00_03/GFX_Linux_KM/services4/3rdparty/dc_omap3_linux
      CC [M]  /home/jasminuser/SGX_sdk/OMAP35x_Android_Graphics_SDK_3_01_00_03/GFX_Linux_KM/services4/3rdparty/dc_omap3_linux/kbuild/../omaplfb_linux.o
    /home/jasminuser/SGX_sdk/OMAP35x_Android_Graphics_SDK_3_01_00_03/GFX_Linux_KM/services4/3rdparty/dc_omap3_linux/kbuild/../omaplfb_linux.c: In function 'OMAPLFB_Init':
    /home/jasminuser/SGX_sdk/OMAP35x_Android_Graphics_SDK_3_01_00_03/GFX_Linux_KM/services4/3rdparty/dc_omap3_linux/kbuild/../omaplfb_linux.c:318: error: 'struct early_suspend' has no member named 'suspend'
    /home/jasminuser/SGX_sdk/OMAP35x_Android_Graphics_SDK_3_01_00_03/GFX_Linux_KM/services4/3rdparty/dc_omap3_linux/kbuild/../omaplfb_linux.c:319: error: 'struct early_suspend' has no member named 'resume'
    /home/jasminuser/SGX_sdk/OMAP35x_Android_Graphics_SDK_3_01_00_03/GFX_Linux_KM/services4/3rdparty/dc_omap3_linux/kbuild/../omaplfb_linux.c:320: error: 'struct early_suspend' has no member named 'level'
    make[4]: *** [/home/jasminuser/SGX_sdk/OMAP35x_Android_Graphics_SDK_3_01_00_03/GFX_Linux_KM/services4/3rdparty/dc_omap3_linux/kbuild/../omaplfb_linux.o] Error 1
    make[3]: *** [_module_/home/jasminuser/SGX_sdk/OMAP35x_Android_Graphics_SDK_3_01_00_03/GFX_Linux_KM/services4/3rdparty/dc_omap3_linux/kbuild] Error 2
    make[2]: *** [modules] Error 2
    make[1]: *** [all] Error 1
    make[1]: Leaving directory `/home/jasminuser/SGX_sdk/OMAP35x_Android_Graphics_SDK_3_01_00_03/GFX_Linux_KM/eurasiacon/build/linux/omap3630_android/kbuild'
    make: *** [buildkernel] Error 2

    is this the reason it is not installed properly?

    Then, lsmod command didn't produce any output.

     

    Regards,

    G.Vetrivel.

  • 0 in reply to vetri vel
    TI__Expert 5400 points

    Hi Vetrivel,

    You should not get any error wihile building and intalling sgx. As lsmod output does not list sgx related kernel modules your sgx modules are not installed.

    Please check with your rules.make file for appropriate paths. Alternatively you can following below entioned procedure

    1. Clone android sources (If you already have android sources then no need to clone) 

    2. Build android souces with following command.

       #> make TARGET_PRODUCT=beagleboard OMAPES=5.x -j8 
    This will build SGX modules along with Android sources
    3. Create a filesystem tarball.
    

    Please refer to below user guide for more details.
    

    http://processors.wiki.ti.com/index.php/TI-Android-FroYo-DevKit-V2.2_UserGuide#Building_Android_Sources
    

    

    Regards,
    

    Pankaj Bharadiya
    

    
			
    

		
		
		
		
	
    
	
    
		
    
			
		
    
	
    

	            
                 	
	
    
				
		                
                
                
                
                
                
                
        		
		
				
    
			
		
    
		
		 
		
		
     
    
	
    

    
			
    
			
    
		
    

		
    
	
    • 

		
	
  • 
		
    
			 


	
		
	
	









    
	
    
		
    
							
					
    
		
    
			
													0
							
			
				
									
							
						
				
			
			
			
												
						in reply to vetri vel
					
									
    
	
    
	                                    
                      
    
                        
                          TI__Expert
                        5400 points
                      
    
                          
                   		
		
    
					
    Hi Vetrivel,
    

    You should not get any error wihile building and intalling sgx. As lsmod output does not list sgx related kernel modules your sgx modules are not installed.
    

    Please check with your rules.make file for appropriate paths. Alternatively you can following below entioned procedure 
    

    1. Clone android sources (If you already have android sources then no need to clone) 
    

    2. Build android souces with following command.
    

       #> make TARGET_PRODUCT=beagleboard OMAPES=5.x
    

    This will build SGX modules along with Android sources
    

    3. Create a filesystem tarball.
    

    

    Please refer to below user guide for more details.
    

    http://processors.wiki.ti.com/index.php/TI-Android-FroYo-DevKit-V2.2_UserGuide#Building_Android_Sources
    

    

    Regards,
    

    Pankaj Bharadiya
    

    
			
    

		
		
		
		
	
    
	
    
		
    
			
		
    
	
    

	            
                 	
	
    
				
		                
                
                
                
                
                
                
        		
		
				
    
			
		
    
		
		 
		
		
     
    
	
    

    
			
    
			
    
		
    

		
    
	
    • 

		
	
  • 
		
    
			 


	
		
	
	









    
	
    
		
    
							
					
    
		
    
			
													0
							
			
				
									
							
						
				
			
			
			
												
						in reply to vetri vel
					
									
    
	
    
	                                    
                      
    
                        
                          TI__Expert
                        5400 points
                      
    
                          
                   		
		
    
					
    Hi Vetrivel,
    

    You should not get any error wihile building and intalling sgx. As lsmod output does not list sgx related kernel modules your sgx modules are not installed.
    

    Please check with your rules.make file for appropriate paths. Alternatively you can following below entioned procedure 
    

    1. Clone android sources (If you already have android sources then no need to clone) 
    

    2. Build android souces with following command.
    

       #> make TARGET_PRODUCT=beagleboard OMAPES=5.x
    

    This will build SGX modules along with Android sources
    

    3. Create a filesystem tarball.
    

    

    Please refer to below user guide for more details.
    

    http://processors.wiki.ti.com/index.php/TI-Android-FroYo-DevKit-V2.2_UserGuide#Building_Android_Sources
    

    

    Regards,
    

    Pankaj Bharadiya
    

    
			
    

		
		
		
		
	
    
	
    
		
    
			
		
    
	
    

	            
                 	
	
    
				
		                
                
                
                
                
                
                
        		
		
				
    
			
		
    
		
		 
		
		
     
    
	
    

    
			
    
			
    
		
    

		
    
	
    • 

		
	
  • 
		
    
			 


	
		
	
	









    
	
    
		
    
							
					
    
		
    
			
													0
							
			
				
									
							
						
				
			
			
			
												
						in reply to Pankaj Bharadiya
					
									
    
	
    
	                                    
                      
    
                        
                          Prodigy
                        170 points
                      
    
                          
                   		
		
    
					
    Hi pankaj,
    

    We didn't download the Android froyo source from gitorious repository  mentioned in the above link. Instead we downloaded the source from the android repository using following commands
    

    repo init -u git://android.git.kernel.org/platform/manifest.git -b froyo
    repo sync

    

    Then we created new product and built the root  filesystem.
    

    We have successfully built and installed sgx library into android filesystem with out any error.
    

    lsmod command gives the following output.
    

    lsmod
    omaplfb 8882 0 - Live 0xbf032000
    pvrsrvkm 137146 1 omaplfb, Live 0xbf000000
    

     
    

    But still we are getting the same error.
    

    We have attached logcat. There is fatal error related to PowerService manager which shows,
    

     
    

    

    

    E/ActivityThread(  907): Failed to find provider info for
settings
    

    E/AndroidRuntime(  907): *** FATAL EXCEPTION IN SYSTEM PROCESS:
PowerManagerService
    

    

    8304.logcat1.doc

    

     In init.rc file we have 
    

    # No battery hardware present
    
    setprop hw.nobattery true
    
    setprop hw.nophone true
    

    
# Power Management Patches
    
    setprop hw.nopm true
    



    Kindly let us know where we are going wrong.

    Regards,
    G.Vetrivel.

    

     
    

     
    
			
    

		
		
		
		
	
    
	
    
		
    
			
		
    
	
    

	            
                	
	
    
				
		                
                
                
                
                
                
                
        		
		
				
    
			
		
    
		
		 
		
		
     
    
	
    

    
			
    
			
    
		
    

		
    
	
    • 

		
	
  • 
		
    
			 


	
			
		
	









    
	
    
		
    
							
					
    
		
    
			
													0
							
			
				
									
							
						
				
			
			
			
												
						in reply to vetri vel
					
									
    
	
    
	                                    
                      
    
                        
                          TI__Expert
                        5400 points
                      
    
                          
                   		
		
    
					
    Hi Vetrivel,
    

     
    

    Creating a new product may not directly work with the google android sources. You will have to add TI related Hardware abstraction layer changes into it.
    

    As we already have working sources for beagleboard, I recommend you to use our android sources and follow build procedure mentioned in  my previous post link. 
    

     
    

    Regards,
    

    Pankaj Bharadiya
    
			
    

		
		
		
		
	
    
	
    
		
    
			
		
    
	
    

	            
                 	
	
    
				
		                
                
                
                
                
                
                
        		
		
				
    
			
		
    
		
		 
		
		
     
    
	
    

    
			
    
			
    
		
    

		
    
	
    • 

		
	
  • 
		
    
			 


	
		
	
	









    
	
    
		
    
							
					
    
		
    
			
													0
							
			
				
									
							
						
				
			
			
			
												
						in reply to Pankaj Bharadiya
					
									
    
	
    
	                                    
                      
    
                        
                          Prodigy
                        170 points
                      
    
                          
                   		
		
    
					
    Hi Pankaj,
    

    Thank you for the information.
    

    We tried to get android source from the  link mentioned in the previous post, but we are getting the following error,
    

    root@Ubundu-Android:/home/jasminuser/Rowboat# repo init -u git://gitorious.org/rowboat/manifest.git -m TI-Android-FroYo-DevKit-V2.2.xml
    Getting repo ...
       from git://android.git.kernel.org/tools/repo.git
    android.git.kernel.org[0: 199.6.1.173]: errno=Connection timed out
    fatal: unable to connect a socket (Connection timed out)
    

    Is there any other way we can download source directly from  your site.
    

    Regards,
    

    G.Vetrivel.
    

     
    

     
    
			
    

		
		
		
		
	
    
	
    
		
    
			
		
    
	
    

	            
                	
	
    
				
		                
                
                
                
                
                
                
        		
		
				
    
			
		
    
		
		 
		
		
     
    
	
    

    
			
    
			
    
		
    

		
    
	
    • 

		
	
  • 
		
    
			 


	
			
		
	









    
	
    
		
    
							
					
    
		
    
			
													0
							
			
				
									
							
						
				
			
			
			
												
						in reply to vetri vel
					
									
    
	
    
	                                    
                      
    
                        
                          TI__Expert
                        5400 points
                      
    
                          
                   		
		
    
					
    Hi Vetrivel,
    

    You are getting this error because www.android.git.kernel.org site is down.
    

    Edit your repo script and change REPO_URL to following and try.
    

    REPO_URL=""
    

    or
    

    REPO_URL='https://github.com/android/tools_repo.git'
    

    Let us know if you face any issues.
    

    We don't have FroYo souces on our release page. You can download Gingerbread2.3.4 sources from below link under TI_Andorid_GingerBread_2_3_4 Sources section.
    

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

     
    

    Regards,
    

    Pankaj Bharadiya
    
			
    

		
		
		
		
	
    
	
    
		
    
			
		
    
	
    

	            
                 	
	
    
				
		                
                
                
                
                
                
                
        		
		
				
    
			
		
    
		
		 
		
		
     
    
	
    

    
			
    
			
    
		
    

		
    
	
    • 

		
	
  • 
		
    
			 


	
		
	
	









    
	
    
		
    
							
					
    
		
    
			
													0
							
			
				
									
							
						
				
			
			
			
												
						in reply to Pankaj Bharadiya
					
									
    
	
    
	                                    
                      
    
                        
                          Prodigy
                        170 points
                      
    
                          
                   		
		
    
					
    Hi Pankaj,
    

    After changing REPO_URL we are able download TI_Android_Froyo source code.
    

    Thank you for support.
    

     
    

    Regards,
    

    G.Vetrivel.
    
			
    

		
		
		
		
	
    
	
    
		
    
			
		
    
	
    

	            
                	
	
    
				
		                
                
                
                
                
                
                
        		
		
				
    
			
		
    
		
		 
		
		
     
    
	
    

    
			
    
			
    
		
    

		
    
	
    • 

		
	
  • 
		
    
			 


	
		
	
	









    
	
    
		
    
							
					
    
		
    
			
													0
							
			
				
									
							
						
				
			
			
			
												
						in reply to Pankaj Bharadiya
					
									
    
	
    
	                                    
                      
    
                        
                          Prodigy
                        170 points
                      
    
                          
                   		
		
    
					
    Dear Pankaj,
    

              We have download the Android source code from TI repository. and we made a build as you mentioned.
    

              While building Android Source Code, following error occurs,
    

     Image arch/arm/boot/uImage is ready
    make[1]: Leaving directory `/home/jasminuser/TI_Froyo/kernel'
    make -C external/ti_android_sgx_sdk ANDROID_ROOT_DIR=`pwd` TOOLS_PREFIX=prebuilt/linux-x86/toolchain/arm-eabi-4.4.0/bin/arm-eabi-
    make[1]: Entering directory `/home/jasminuser/TI_Froyo/external/ti_android_sgx_sdk'
    Installing OMAP35x Android Graphics SDK...
    make[1]: ./internal_install_SDK.exp: Command not found
    make[1]: *** [prepare] Error 127
    make[1]: Leaving directory `/home/jasminuser/TI_Froyo/external/ti_android_sgx_sdk'
    make: *** [sgx] Error 2
    

    Thanks & Regards,
    

    Vetrivel
    

     
    

     
    
			
    

		
		
		
		
	
    
	
    
		
    
			
		
    
	
    

	            
                	
	
    
				
		                
                
                
                
                
                
                
        		
		
				
    
			
		
    
		
		 
		
		
     
    
	
    

    
			
    
			
    
		
    

		
    
	
    • 

		
	
  • 
		
    
			 


	
		
	
	









    
	
    
		
    
							
					
    
		
    
			
													0
							
			
				
									
							
						
				
			
			
			
												
						in reply to vetri vel
					
									
    
	
    
	                                    
                      
    
                        
                          TI__Expert
                        5400 points
                      
    
                          
                   		
		
    
					
    Hi Vetrivel,
    

    You need to install expect on your host machine. This is required for installing SGX SDK 
    Run following command to install expect and build again.
    

    $sudo apt-get install expect
    

    Regards,
    

    Pankaj Bharadiya
    
			
    

		
		
		
		
	
    
	
    
		
    
			
		
    
	
    

	            
                 	
	
    
				
		                
                
                
                
                
                
                
        		
		
				
    
			
		
    
		
		 
		
		
     
    
	
    

    
			
    
			
    
		
    

		
    
	
    •