Hi Cindy, Dont use these bootargs as these are specifically for beagle.
Use these bootargs :- setenv bootargs mem=128M console=ttyS0,115200n8 noinitrd rw root=/dev/nfs nfsroot=<android root filesysetm path> ,nolock,wsize=1024,rsize=1024 ip=dhcp init=/init data/target is the path of the rootfilesystem placed on ur host machine from where u r mounting the android root filesystem. 2.Dose it need to write a shell for booting android NO, its not necessary. Regards Nimit 2009/4/17 cindy_king_1024 <cindy_king_1...@126.com> > Hi， Nimit > In the links： > > http://labs.embinux.org/index.php/Android_Porting_Guide_to_Beagle_Board > > console=ttyS2,115200n8 root=/dev/nfs rw nfsroot=192.168.1.5:/data/target > ip=192.168.1.1::255.255.255.0 nolock,rsize=1024,wsize=1024 rootdelay=2 > video=omapfb:mode:1280x...@50 init=/init > 1.what dose the directory mean－－－:/data/target mean？How does it relate to > Android_rfs > > 2.Dose it need to write a shell for booting android > > 在2009-04-17 12:42:33，"Nimit Manglick" <nimitandr...@gmail.com> 写道： > > Hi Cindy, > > First of all the filesystem which you have used once with nfs cant work > directly on SD / MMC card as once that filesystem has been used on nfs so > while booting android creats so many cache files. > > So If u r booting via SD / MMC card then ur SD / MMC card shall be > containing two partitions :- first ext3 (for filesystem) second vfat (for > uImage and media files) > > To create a filesystem out of the source follow the steps from this link > under the title (Root file System of Android > <http://labs.embinux.org/index.php?title=Root_file_System_of_Android&action=edit&redlink=1>) > :- > > http://labs.embinux.org/index.php/Android_Porting_Guide_to_Beagle_Board > > You dont need to touch init.goldfish.rc that is emant only for QEMU > emulator. > > So you just need to have a look on init.rc. To modify init.rc follow the > steps from the above link only. > > So other than that what u want to modify in that ?? > > Regards > Nimit > > > > 2009/4/17 Anil Sasidharan <anil...@gmail.com> > >> Hi, >> >> Android has already been ported to OMAP3EVM from Mistral. In >> fact this initiative has been very active for approximately a year. We will >> be uploading the demo-images to our public repository. You can visit the URL >> http://www.mistralsolutions.com/technology/android_omap.php for more >> info. >> >> Warm Regards, >> Anil >> >> 2009/4/17 cindy_king_1024 <cindy_king_1...@126.com>: >> >> > Hi,Nimit >> > Sorry,I have forget .If boot from SD card ,how to make the filesystem? >> The >> > content of the SD contain all the things in the NFS filesystem: >> > data dev init.goldfish.rc sbin system >> > default.prop init init.rc proc sys >> > >> > 在2009-04-16 14:08:18，"Nimit Manglick" <nimitandr...@gmail.com> 写道： >> > >> > Hi Cindy, >> > >> > Its the problem in ur filesystem... >> > >> > and I am not sure about ur booatargs as well.... >> > >> > Please use my bootargs which i mentioned earlier.. The bootargs u r >> using >> > that might be specific to beagle board I suppose. >> > >> > Or else try to boot it via SD / MMC card. >> > >> > Regards >> > NImit >> > >> > 2009/4/15 cindy_king_1024 <cindy_king_1...@126.com> >> >> >> >> Hi Nimit， >> >> I enter the command about nfs boot，it come with the same error，what >> about >> >> yours？have you seen such setences： >> >> >> >> <6>Waiting 2sec before mounting root device... >> >> Waiting 2sec before mounting root device... >> >> <5>Looking up port of RPC 100003/2 on 10.86.76.68 >> >> Looking up port of RPC 100003/2 on 10.86.76.68 >> >> <5>Looking up port of RPC 100005/1 on 10.86.76.68 >> >> Looking up port of RPC 100005/1 on 10.86.76.68 >> >> VFS: Mounted root (nfs filesystem). >> >> VFS: Mounted root (nfs filesystem). >> >> <6>Freeing init memory: 144K >> >> Freeing init memory: 144K >> >> <4>Warning: unable to open an initial console. >> >> Warning: unable to open an initial console. >> >> <0>Kernel panic - not syncing: Attempted to kill init! >> >> Kernel panic - not syncing: Attempted to kill init! >> >> >> >> the nfs bootargs： >> >> setenv console=ttyS0,115200n8 noinitrd rw root=/dev/nfs >> >> nfsroot=10.86.76.68:/home/Android_rfs ip=dhcp >> nolock,rsize=1024,wsize=1024 >> >> rootdelay=2 video=omapfb:mode:640x...@50 init=/init mem=128M >> >> >> >> Kernel command line: 在2009-04-15 12:38:36，"Nimit Manglick" >> >> <nimitandr...@gmail.com> 写道： >> >> >> >> Hi Cindy, >> >> >> >> 1.what do you mean about cupcake branch？ >> >> >> >> Cupcake is the new android branch which has just been merged to master >> >> branch. >> >> Means to say that it is the latest android code drop branch. >> >> So In that currently alsa (for audio support ) is breaking, but first >> of >> >> all ur basic android should boot. >> >> >> >> 2.Boot from nfs >> >> >> >> Try with the following nfs bootargs :- >> >> >> >> setenv bootargs mem=128M console=ttyS0,115200n8 noinitrd rw >> root=/dev/nfs >> >> nfsroot=<path to ur filesystem on ur host machine> >> >> ,nolock,wsize=1024,rsize=1024 ip=dhcp init=/init >> >> >> >> Please make sure you have run all the services like nfs-server etc on >> ur >> >> host machine >> >> and made a entry in ur /etc/exports >> >> >> >> Hope it helps. >> >> >> >> Regards >> >> Nimit >> >> >> >> >> >> 2009/4/14 cindy_king_1024 <cindy_king_1...@126.com> >> >>> >> >>> Dear Nimit， >> >>> I'm glad to hear from you，as you discript： >> >>> 1.what do you mean about cupcake branch？ >> >>> >> >>> 2.Boot from nfs ，the inviaronment variable was that： >> >>> setenv console=ttyS0,115200n8 ip=dhcp rw root=/dev/nfs >> >>> nfsroot=10.86.76.92:/home/jennifer/Android_rfs,nolock mem=88M >> >>> video=omapfb:mode:640x...@50 init=/init >> >>> >> >>> 3.Without the patch to the nfs filesystem，it aborted with the >> following >> >>> sentence： >> >>> >> >>> IP-Config: Got DHCP answer from 0.0.0.0, IP-Config: Got DHCP answer >> from >> >>> 0.0.0.0, my address is 10.8 >> >>> 6.76.115 >> >>> my address is 10.86.76.115 >> >>> IP-Config: Complete:IP-Config: Complete: >> >>> device=eth0 >> >>> device=eth0, addr=10.86.76.115, addr=10.86.76.115, >> >>> mask=255.255.255.0, mask=255.255.255.0, gw=1 >> >>> 0.86.76.249, gw=10.86.76.249, >> >>> host=10.86.76.115, domain=, nis-domain=(none), >> >>> host=10.86.76.115, domain=, nis-domain=(none), >> >>> bootserver=0.0.0.0, >> >>> bootserver=0.0.0.0, rootserver=10.86.76.92, >> rootserver=10.86.76.92, >> >>> rootpath=, rootpath= >> >>> >> >>> <5>Looking up port of RPC 100003/2 on 10.86.76.92 >> >>> Looking up port of RPC 100003/2 on 10.86.76.92 >> >>> <5>Looking up port of RPC 100005/1 on 10.86.76.92 >> >>> Looking up port of RPC 100005/1 on 10.86.76.92 >> >>> >> >>> VFS: Mounted root (nfs filesystem). >> >>> VFS: Mounted root (nfs filesystem). >> >>> <6>Freeing init memory: 144K >> >>> Freeing init memory: 144K >> >>> <4>Warning: unable to open an initial console. >> >>> Warning: unable to open an initial console. >> >>> <0>Kernel panic - not syncing: Attempted to kill init! >> >>> Kernel panic - not syncing: Attempted to kill init! >> >>> >> >>> >> >>> >> >>> >> >>> >> >>> >> >>> >> >>> 在2009-04-14 17:28:50，"Nimit Manglick" <nimitandr...@gmail.com> 写道： >> >>> >> >>> Hi Cindy, >> >>> >> >>> Ya you can follow the below link. tell me at what step you are stucked >> >>> now. >> >>> >> >>> Anywaz basic steps for porting are :- >> >>> >> >>> 1. Make ur kernel (Follow any link available on net ) This link will >> give >> >>> you teh kernel for beagle board. So Dont check out this kernel. >> >>> >> >>> 2. Build your android (Dont apply the patches as mentioned if you are >> >>> going to work on cupcake branch) >> >>> >> >>> 3. make ur filesystem. >> >>> >> >>> 4. With your own set of booatargs for EVM.. run android. >> >>> >> >>> Hope this helps. If you are stucking somewhere let me know. I will try >> to >> >>> help you out. >> >>> >> >>> Regards >> >>> Nimit >> >>> >> >>> 2009/4/13 cindy_king_1024 <cindy_king_1...@126.com> >> >>>> >> >>>> Hi,Nimit >> >>>> Can you give me some detailed steps about android porting. >> >>>> I have follow the steps in the following link: >> >>>> >> http://labs.embinux.org/index.php/Android_Porting_Guide_to_Beagle_Board >> >>>> but it comes with this : >> >>>> <6>eth0: link down >> >>>> eth0: link down >> >>>> <5>Sending DHCP requests .Sending DHCP requests .<6>eth0: link up, >> >>>> 100Mbps, full-duplex, lpa 0x05E1 >> >>>> <6>eth0: link up, 100Mbps, full-duplex, lpa 0x05E1 >> >>>> ..,, OK >> >>>> OK >> >>>> IP-Config: Got DHCP answer from 0.0.0.0, IP-Config: Got DHCP answer >> from >> >>>> 0.0.0.0, my address is 192. >> >>>> 168.1.104 >> >>>> my address is 192.168.1.104 >> >>>> IP-Config: Complete:IP-Config: Complete: >> >>>> device=eth0 >> >>>> device=eth0, addr=192.168.1.104, addr=192.168.1.104, >> >>>> mask=255.255.255.0, mask=255.255.255.0, gw >> >>>> =192.168.1.1, gw=192.168.1.1, >> >>>> host=192.168.1.104, domain=domain, nis-domain=(none), >> >>>> host=192.168.1.104, domain=domain, nis-domain=(none), >> >>>> bootserver=0.0.0.0, >> >>>> bootserver=0.0.0.0, rootserver=192.168.1.105, >> >>>> rootserver=192.168.1.105, rootpath=, rootpath= >> >>>> <6>Waiting 2sec before mounting root device... >> >>>> Waiting 2sec before mounting root device... >> >>>> <5>Looking up port of RPC 100003/2 on 192.168.1.105 >> >>>> Looking up port of RPC 100003/2 on 192.168.1.105 >> >>>> <5>Looking up port of RPC 100005/1 on 192.168.1.105 >> >>>> Looking up port of RPC 100005/1 on 192.168.1.105 >> >>>> VFS: Mounted root (nfs filesystem). >> >>>> VFS: Mounted root (nfs filesystem). >> >>>> <6>Freeing init memory: 144K >> >>>> Freeing init memory: 144K >> >>>> <4>Warning: unable to open an initial console. >> >>>> Warning: unable to open an initial console. >> >>>> <3>init: cannot open '/initlogo.rle' >> >>>> init: cannot open '/initlogo.rle' >> >>>> <3>init: Unable to open persistent property directory /data/property >> >>>> errno: 2 >> >>>> init: Unable to open persistent property directory /data/property >> errno: >> >>>> 2 >> >>>> <3>init: cannot find '/system/bin/playmp3', disabling 'bootsound' >> >>>> init: cannot find '/system/bin/playmp3', disabling 'bootsound' >> >>>> sh: can't access tty; job control turned off >> >>>> # <6>warning: `rild' uses 32-bit capabilities (legacy support in use) >> >>>> warning: `rild' uses 32-bit capabilities (legacy support in use) >> >>>> <6>request_suspend_state: wakeup (3->0) at 23607482910 (1970-01-01 >> >>>> 00:00:23.607482910 UTC) >> >>>> request_suspend_state: wakeup (3->0) at 23607482910 (1970-01-01 >> >>>> 00:00:23.607482910 UTC) >> >>>> <6>request_suspend_state: wakeup (0->0) at 24186004638 (1970-01-01 >> >>>> 00:00:24.186004638 UTC) >> >>>> request_suspend_state: wakeup (0->0) at 24186004638 (1970-01-01 >> >>>> 00:00:24.186004638 UTC) >> >>>> <6>request_suspend_state: wakeup (0->0) at 29410034179 (1970-01-01 >> >>>> 00:00:29.410034179 UTC) >> >>>> request_suspend_state: wakeup (0->0) at 29410034179 (1970-01-01 >> >>>> 00:00:29.410034179 UTC) >> >>>> <6>request_suspend_state: wakeup (0->0) at 35350250244 (1970-01-01 >> >>>> 00:00:35.350219726 UTC) >> >>>> request_suspend_state: wakeup (0->0) at 35350250244 (1970-01-01 >> >>>> 00:00:35.350219726 UTC) >> >>>> <6>request_suspend_state: wakeup (0->0) at 40411346435 (1970-01-01 >> >>>> 00:00:40.411315917 UTC) >> >>>> request_suspend_state: wakeup (0->0) at 40411346435 (1970-01-01 >> >>>> 00:00:40.411315917 UTC) >> >>>> <6>request_suspend_state: wakeup (0->0) at 45559783935 (1970-01-01 >> >>>> 00:00:45.559783935 UTC) >> >>>> request_suspend_state: wakeup (0->0) at 45559783935 (1970-01-01 >> >>>> 00:00:45.559783935 UTC) >> >>>> <6>request_suspend_state: wakeup (0->0) at 50434753417 (1970-01-01 >> >>>> 00:00:50.434722900 UTC) >> >>>> request_suspend_state: wakeup (0->0) at 50434753417 (1970-01-01 >> >>>> 00:00:50.434722900 UTC) >> >>>> >> >>>> >> >>>> Thanks >> >>>> >> >>>> >> >>>> ________________________________ >> >>>> 网易邮箱，中国第一大电子邮件服务商 >> >>>> >> >>>> ________________________________ >> >>>> 网易邮箱，中国第一大电子邮件服务商 >> >>> >> >>> >> >>> ________________________________ >> >>> 网易邮箱，中国第一大电子邮件服务商 >> >> >> >> >> >> ________________________________ >> >> 网易邮箱，中国第一大电子邮件服务商 >> > >> > 网易邮箱，中国第一大电子邮件服务商 >> >> > > 网易邮箱，中国第一大电子邮件服务商 <http://email.163.com>> > --~--~---------~--~----~------------~-------~--~----~ unsubscribe: android-porting+unsubscr...@googlegroups.com website: http://groups.google.com/group/android-porting -~----------~----~----~----~------~----~------~--~---
