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 Blaze tablet 2 NFS/TFTP boot setup

HI,

   I am using OMAP4 blaze tablet 2 for my development.I am able to boot from eMMC with prebuilt binaries.Now i wish to configure NFS/TFTP boot for Blaze tablet 2.I followed below link

http://www.omappedia.org/wiki/Android_Getting_Started#Installing_Android

and set the bootargs to below value.

setenv bootargs 'console=ttyO2,115200n8 mem=1G vmalloc=768M androidboot.console=ttyO2 omap_wdt.timer_margin=30 ip=dhcp root=/dev/nfs rw nfsroot=172.21.128.138:/home/senthil/blaze_nfs/,nolock,wsize=1024,rsize=1024 init=/init rootfstype=ext4 rootwait'

After changing the bootargs,It is booting and mounts eMMC partitions as filesystem.I commented some lines in  init.omap4blazeboard.rc  file at nfs root folder.Please find the changes below.

on fs
        mkdir /factory 0775 radio radio
#       mount ext4 /dev/block/platform/omap/omap_hsmmc.1/by-name/system /system wait ro
        setprop ro.crypto.tmpfs_options size=128m,mode=0771,uid=1000,gid=1000
#       mount ext4 /dev/block/platform/omap/omap_hsmmc.1/by-name/userdata /data wait noatime nosuid nodev nomblk_io_submit
#       mount ext4 /dev/block/platform/omap/omap_hsmmc.1/by-name/cache /cache wait noatime nosuid nodev nomblk_io_submit
#       mount ext4 /dev/block/platform/omap/omap_hsmmc.1/by-name/efs /factory wait ro
        setprop ro.crypto.fuse_sdcard true

Now tablet boots and stuck with log message

[   27.745452] nfs: server 172.21.128.138 not responding, still trying

Please suggest.

Regards

Senthikumar R

Regards

Senthilkumar R

  • Hi Senthil Kumar,

    Which Android codebase are you using for this? Also is there any specific reason why you want to use the TFTP boot?

    Regards, Satheesh.

  • Hi Senthikumar R,

          In my personal opinion you don't have to worry about your modifications to init.omap4blazeboard.rc, the message said it all, it can reach your NFS server. and this problem prevents it from seeing anything you could modify on the filesystem. You should check your NFS settings, and easy test is to mount you NFS share in another machine. Could you specify which release android are you using? this will help me to reproduce your problem and provide a better solutions to your inquires, If I can suggest use our latest release,

    http://omappedia.com/wiki/4AI.1.4_OMAP4_Icecream_Sandwich_Release_Notes

    Regards,

    Rodrigo

  • Hi,

      If i didnt modify the init script, it remounts the root filesystem from eMMC block and bootup fine.Thatswhy i commented it.NFS/TFTP boot is required for applicatoin development,which reduce installation time of new files in the filesystem either in SD card or eMMC.

    My host machine is working fine.As you suggested i have already mounted nfs file share into another machine.It is working fine.

    Currently i am using exactly the same4AI.1.4  release for my development.But prebuilt kernel uImage is not enabled with CONFIG_NFS_ROOT,i enabled it and rebuild the kernel.It seems like this relase(4AI.1.4) is not build with NFS support.Please suggest.

    Regards

    Senthilkumar R

  • Senthil,

    As I have pointed out we normally do not use tftpboot and NFS for our development so it is very much possible that the support is disabled in the default release.

    If you are just want to reduce installation time you can as well use adb debug support which is very much handy for copying libs, installing apps and lot of other feature as well.

    Regards,

    Chintan