Account Options

  1. Sign in
The old Google Groups will be going away soon.
Switch to the new Google Groups.
Google Groups Home
« Groups Home
android-porting
Home
+ new post
About this group
Join this group
Problem booting Android on Zoom2
Options
There are currently too many topics in this group that display first. To make this topic appear first, remove this option from another topic.
There was an error processing your request. Please try again.
flag
   8 messages - Collapse all  -  Translate all to Translated (View all originals)
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
eternity  
View profile  
 More options Feb 17 2010, 3:08 am
From: eternity <gtir...@gmail.com>
Date: Wed, 17 Feb 2010 00:08:22 -0800 (PST)
Local: Wed, Feb 17 2010 3:08 am
Subject: Problem booting Android on Zoom2
Print | Individual message | Show original | Report this message | Find messages by this author
Hi,

I am having two (downloaded) workspace for Omap Android which are
RLS25.14 and eclair. Both are built with arm-2008q3 i.e gcc 4.3
toochain.

Now when I am trying to boot AFS ( for both) on Zoom2 board:

1. for RLS25.14, the Zoom2 is booting fine
but
2. for eclair I am getting the following error on hyperterminal:

EXT3 FS on mmcblk0p2, internal journal
EXT3-fs: recovery complete.
EXT3-fs: mounted filesystem with ordered data mode.
VFS: Mounted root (ext3 filesystem) on device 179:2.
Freeing init memory: 184K
Warning: unable to open an initial console.
init: cannot open '/initlogo.rle'
yaffs: dev is 32505860 name is "mtdblock4"
yaffs: passed flags ""
yaffs: Attempting MTD mount on 31.4, "mtdblock4"
yaffs_read_super: isCheckpointed 0
yaffs: dev is 32505861 name is "mtdblock5"
yaffs: passed flags ""
yaffs: Attempting MTD mount on 31.5, "mtdblock5"
yaffs_read_super: isCheckpointed 0
**>> Block 2 needs retiring
**>> Block 2 retired
**>> Block 3 needs retiring
**>> Block 3 retired
**>> Block 4 needs retiring
**>> Block 4 retired
         :
         :
         :
         :
**>> Block 247 needs retiring
**>> Block 247 retired
**>> Block 248 needs retiring
**>> Block 248 retired
**>> yaffs write required 247 attempts
page 64 in gc has no object: 0 0 0
**>> Erasure failed 1
**>> Block 1 retired
Block 1 is in state 9 after gc, should be erased
yaffs tragedy: no more erased blocks
yaffs tragedy: no more erased blocks
yaffs tragedy: no more erased blocks
!!!!!!!!! Allocator out !!!!!!!!!!!!!!!!!
yaffs tragedy: no more erased blocks
yaffs tragedy: no more erased blocks
yaffs tragedy: no more erased blocks
!!!!!!!!! Allocator out !!!!!!!!!!!!!!!!!
yaffs tragedy: no more erased blocks
yaffs tragedy: no more erased blocks
yaffs tragedy: no more erased blocks
!!!!!!!!! Allocator out !!!!!!!!!!!!!!!!!
yaffs tragedy: no more erased blocks
yaffs tragedy: no more erased blocks
yaffs tragedy: no more erased blocks
!!!!!!!!! Allocator out !!!!!!!!!!!!!!!!!
yaffs tragedy: no more erased blocks
yaffs tragedy: no more erased blocks
yaffs tragedy: no more erased blocks
!!!!!!!!! Allocator out !!!!!!!!!!!!!!!!!
yaffs tragedy: no more erased blocks
yaffs tragedy: no more erased blocks
yaffs tragedy: no more erased blocks
!!!!!!!!! Allocator out !!!!!!!!!!!!!!!!!
yaffs tragedy: no more erased blocks
yaffs tragedy: no more erased blocks
yaffs tragedy: no more erased blocks
!!!!!!!!! Allocator out !!!!!!!!!!!!!!!!!
init: Unable to open persistent property directory /data/property
errno: 2
init: cannot find '/system/bin/sh', disabling 'console'
init: cannot find '/system/bin/cexec.out', disabling 'baseimage'
init: cannot find '/system/bin/OMXPolicyManager', disabling 'omx_pm'
init: cannot find '/system/bin/OMXResourceManager', disabling 'omx_rm'
init: cannot find '/system/bin/gsm0710muxd', disabling 'mux'
init: cannot find '/system/bin/servicemanager', disabling
'servicemanager'
init: cannot find '/system/bin/vold', disabling 'vold'
init: cannot find '/system/bin/debuggerd', disabling 'debuggerd'
init: cannot find '/system/bin/sh', disabling 'pvrsrv'
init: cannot find '/system/bin/rild', disabling 'ril-daemon'
init: cannot find '/system/bin/app_process', disabling 'zygote'
init: cannot find '/system/bin/mediaserver', disabling 'media'
init: cannot find '/system/bin/fw3a', disabling 'fw3a'
init: cannot find '/system/bin/playmp3', disabling 'bootsound'
init: cannot find '/system/bin/dbus-daemon', disabling 'dbus'
init: cannot find '/system/xbin/uim', disabling 'uim'
init: cannot find '/system/bin/installd', disabling 'installd'
init: cannot find '/system/bin/flash_image', disabling
'flash_recovery'
omapdss DISPC error: SYNC_LOST, disabling LCD

Any idea why this AFS is not working. But very surely those binaries
are there in /system/bin and the same SD card I am using for both AFS
(so, its not a SDCARD problem).
Any help will be appreciated!!!!!!!!!!!11

Thanks in advance


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
eternity  
View profile  
 More options Feb 17 2010, 4:28 am
From: eternity <gtir...@gmail.com>
Date: Wed, 17 Feb 2010 01:28:45 -0800 (PST)
Local: Wed, Feb 17 2010 4:28 am
Subject: Re: Problem booting Android on Zoom2
Print | Individual message | Show original | Report this message | Find messages by this author
With help of a good guy, I found that init.rc in eclair AFS, was
trying to do these following lines:

mount yaffs2 mtd@system /system
mount yaffs2 mtd@system /system ro remount
mount yaffs2 mtd@userdata /data nosuid nodev
mount yaffs2 mtd@cache /cache nosuid nodev

So, I commented those lines and found that no more such errors are
coming.

But still UI is not coming on zoom2 screen. It got stuck in "black
screen with small white android" but I am getting android shell in my
hyperterminal.

I got the eclair branch using :

repo init -u git://git.omapzoom.org/platform/omapmanifest.git -b
eclair
repo sync

Is this branch is not stable??

regards,

On Feb 17, 1:08 pm, eternity <gtir...@gmail.com> wrote:


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Deva R  
View profile  
 More options Feb 17 2010, 5:09 am
From: Deva R <r.deva...@gmail.com>
Date: Wed, 17 Feb 2010 15:39:21 +0530
Local: Wed, Feb 17 2010 5:09 am
Subject: Re: [android-porting] Re: Problem booting Android on Zoom2
Print | Individual message | Show original | Report this message | Find messages by this author

Hi,
Thats a good call to comment yaffs.. i guess you boot via MMC and not NAND.
Default mode of android boot for RLS25 is from nand and hence yaffs is kept
enabled for NAND boot.

btw - regarding no UI coming up, i booted the same tree y'day and was ok..
attached my boot log till UI. check against yours.

Regards
Deva

  android-boot-ok-log.txt
15K Download

 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Deva R  
View profile  
 More options Feb 17 2010, 5:14 am
From: Deva R <r.deva...@gmail.com>
Date: Wed, 17 Feb 2010 15:44:29 +0530
Local: Wed, Feb 17 2010 5:14 am
Subject: Re: [android-porting] Re: Problem booting Android on Zoom2
Print | Individual message | Show original | Report this message | Find messages by this author

Also, i used below bootargs.
set bootargs 'console=ttyS3,115200n8 root=/dev/mmcblk0p2 rw rootdelay=1
mem=256M init=/init stdin=serial stdout=serial stderr=serial
omap_vout.vid1_static_vrfb_alloc=y omapfb.vram="0:4M" '
set bootcmd 'mmcinit;fatload mmc 0 0x80300000 uImage;bootm 0x80300000'


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Tirtha Kanti Ghosh  
View profile  
 More options Feb 17 2010, 5:27 am
From: Tirtha Kanti Ghosh <gtir...@gmail.com>
Date: Wed, 17 Feb 2010 15:57:12 +0530
Local: Wed, Feb 17 2010 5:27 am
Subject: Re: [android-porting] Re: Problem booting Android on Zoom2
Print | Individual message | Show original | Report this message | Find messages by this author

>Also, i used below bootargs.
>set bootargs 'console=ttyS3,115200n8 root=/dev/mmcblk0p2 rw rootdelay=1

mem=256M init=/init stdin=serial >stdout=serial stderr=serial
omap_vout.vid1_static_vrfb_alloc=y omapfb.vram="0:4M" '

>set bootcmd 'mmcinit;fatload mmc 0 0x80300000 uImage;bootm 0x80300000'

I am using almost same bootargs but my memory address is 0x81c00000 as
mentioned in http://omappedia.org/wiki/Android_Getting_Started .

>btw - regarding no UI coming up, i booted the same tree y'day and was ok..

do u mean, keep trying until it boots up???

>attached my boot log till UI. check against yours.

thanks a lot.

regards,


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
eternity  
View profile  
 More options Feb 18 2010, 7:07 am
From: eternity <gtir...@gmail.com>
Date: Thu, 18 Feb 2010 04:07:33 -0800 (PST)
Local: Thurs, Feb 18 2010 7:07 am
Subject: Re: Problem booting Android on Zoom2
Print | Individual message | Show original | Report this message | Find messages by this author
So finally I found as posted by Deva R

my bootargs was missing <omapfb.vram="0:4M"> which is mandatory for
eclair.

according to http://wiki.davincidsp.com/index.php/Dual_Frame_Buffer_on_OMAP35x
omapfb.vram allocate buffer for /dev/fb1.

But I saw in kernel .config, CONFIG_FB_OMAP2_NUM_FBS=1 only, even to
make sure after android boots up I checked there is only one frame
buffer in sysfs (/dev/graphics/fb0)

so, why that parameter is required???
any guess??

On Feb 17, 3:27 pm, Tirtha Kanti Ghosh <gtir...@gmail.com> wrote:


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Deva R  
View profile  
 More options Feb 18 2010, 9:35 am
From: Deva R <r.deva...@gmail.com>
Date: Thu, 18 Feb 2010 20:05:46 +0530
Local: Thurs, Feb 18 2010 9:35 am
Subject: Re: [android-porting] Re: Problem booting Android on Zoom2
Print | Individual message | Show original | Report this message | Find messages by this author

great that its resolved..

> omapfb.vram="0:4M"

btw, its just single fb., and right now not sure why its mandatory to
explicitly quote 4M size.
will post, once i get update on it..


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Deva  
View profile  
 More options Feb 22 2010, 4:14 am
From: Deva <r.deva...@gmail.com>
Date: Mon, 22 Feb 2010 01:14:47 -0800 (PST)
Local: Mon, Feb 22 2010 4:14 am
Subject: Re: Problem booting Android on Zoom2
Print | Individual message | Show original | Report this message | Find messages by this author
Hi,
This's regarding why we need to explicitly mention fb0 size in
bootargs

By default, kernel allocates memory for fb as below
864 X 480 X 4 (width X height X bpp)

When the application needs more memory, it can be sent through
bootargs.
0:4 M allocate 4MB memory to fb.

To suffice eclair requirement, we allocate 4MB for fb0. if not, we'll
run into issues you faced.

reagards,
Deva

On Feb 18, 7:35 pm, Deva R <r.deva...@gmail.com> wrote:


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
End of messages
« Back to Discussions « Newer topic     Older topic »

Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
©2012 Google