android on beagle/OMAP35x? - Beagle Board

Message from discussion android on beagle/OMAP35x?

Rupesh Gujare

More options Nov 15 2008, 8:15 am

From: Rupesh Gujare <rupeshguj...@gmail.com>

Date: Sat, 15 Nov 2008 05:15:39 -0800 (PST)

Local: Sat, Nov 15 2008 8:15 am

Subject: Re: android on beagle/OMAP35x?

  Reply to author
  |
  Forward
  | Print
  | View thread
  | Show original
  | Report this message
  | Find messages by this author
  

Hi All,

We have successfully ported (custom) open source Android to beagle
board. This is very initial version. We have tested it on MMC card
and on NFS.
Please find below link for uImage and root filesystem.

http://embdroid.homeftp.net/ANDROID.tar.bz2

You can watch Beagle board booting Android here:-
http://in.youtube.com/watch?v=3cetZMUWBHY

I will get back with more details and update very soon.
Enjoy Androing...

Regards,

--
Rupesh Gujare
http://embinux.com

On Oct 23, 8:00 pm, kapare <kevyn.alexandre.p...@gmail.com> wrote:

> android-is-now-open-source since Posted by Jason Chen on 21 October
> 2008 at 7:58 AM

> http://android-developers.blogspot.com/2008/10/android-is-now-open-so...

> source.android.com

> I'm compiling the code right now !

> kap

> On Oct 22, 8:05 am, vincent326.li...@gmail.com wrote:

> > I've already ported the android kernel to beagleboard(2.6.22) with
> > full android kernel m5_rc20 patches,
> > and I can boot from android emulator with appropriate kernel config
> > (goldfish and qemu). I think this steps
> > will make sure the kernel is okay. But now, I have some problem with
> > android file system.

> > I do the following test (refer to "Android on OMAP" article):
> > 1. boot from the startard file system(ext2) of beagle board and switch
> > the control to android system.
> > I meet "segmemntation fault" while executing the "/init" command.

> > 2. apply yaffs2 file system on /dev/mtdblock4, and copy the android's
> > stuff to it. After that,
> > modify the boot argument (root=/dev/mtdblock4 rootfstype=yaffs2
> > init=/init ...), but the boot procedure
> > stop at the following point.
> > ... ...
> > <6>yaffs: dev is 32505860 name is "mtdblock4"
> > yaffs: dev is 32505860 name is "mtdblock4"
> > <6>yaffs: passed flags ""
> > yaffs: passed flags ""
> > yaffs: Attempting MTD mount on 31.4, "mtdblock4"
> > yaffs: Attempting MTD mount on 31.4, "mtdblock4"
> > VFS: Mounted root (yaffs2 filesystem).
> > VFS: Mounted root (yaffs2 filesystem).
> > <6>Freeing init memory: 132K
> > Freeing init memory: 132K

> > it seems to be the "/init" issue as well. (I make sure that I can
> > beagleboard file system on yaffs2)
> > I have no idea about it, and i can't go on. any suggestion is
> > applicated.

> > On 9月24日, 下午8時34分, "Weihua Sheng" <weihua.sh...@gmail.com> wrote:

> > > Re-read the mail, much sorry about the confusion the newbie created earlier...
> > > I'd like to see if one can boot upandroidon omap35x hardware. I readhttp://elinux.org/Android_on_OMAP, my understanding is that kernel
> > > source + patch + a proper FS would do, though not sure about the TLS
> > > issue. Would like to poll if there's a work-around for that, or any
> > > experience regarding makingandroidrun on beagle.

> > > Any suggestions/hints are appreciated.

Reply to author Forward