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.

Booting via TFTP and using NFS for root file system



Hello,

I'm using the ti-glsdk_omap5-uevm_6_00_00_07 SDK and the OMAP5432 EVM ver. 2.0.

After installing and running the setup script, it configures my host computer with TFTP and NFS to boot the evaluation board.

How how do I boot this configuration? The OMAP5432 EVM reference guide description of the SYSBOOT switch does not list a network boot option.

The eMMC booting method used by the evaluation board. How is it configured? The setup script created/updated the files MLO,  u-boot.img  and u-boot.map. From some of the documentation I found, these files are read by the x-loader and u-boot loaders. However, it is not clear how one does it with this evaluation board.

Thank you for your patience and help.

Rafael

  • For GLSDK, SD card boot is validated. For Android eMMC boot is validated.

    Other boot modes are not validated.

  • Hi Rafael,

    The u-boot version available with GLSDK does not support ethernet (at least the one that I have), and therefore does not support TFTP mode for loading the kernel. You can load the kernel from SDCard or emmc. After that you can use NFS for the root file system by changing the bootargs in u-boot:

    You need to modify the bootargs so that 'root' argument shows nfs:

    For ex:

    Original bootargs (rootfs is on SDCard): 

    OMAP5430 EVM # print bootargs
    bootargs=console=ttyO2,115200n8 root=/dev/mmcblk0p2 rw rootdelay=3 

    New bootargs:

    OMAP5430 EVM # print bootargs
    bootargs=console=ttyO2,115200n8 root=/dev/nfs nfsroot=<my-ip-address>/home/komalp/targetfs rw rootdelay=3
    OMAP5430 EVM # saveenv

  • Thank you.

    From the reference guide for the OMAP 5432 it does not seem like it supports TFTP. However, the setup SDK script configures your host for TFTP.

    By copying the NFS configured board-support/prebuilt-images/boot.scr.nfs file to the FAT partition in the SD card I was able to boot the board with the rootfs in my development host.

    Cheers,

    Rafael