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.

Linux: NFS mount issue with my AM5718 Custom Board

Other Parts Discussed in Thread: AM5718, BEAGLEBOARD-X15

Tool/software: Linux

Hi,

We have developed a custom board with AM5718 processor and we are using ti-processor-sdk-linux-am57xx-evm-02.00.01.07 SDK. We are having some booting issues with SD card boot. So for testing I want to use NFS method for complete board testing. I have done changes in the u-boot for Ethernet, as I am using RMII interface in custom board. I have tested ethernet basic command ping working from u-boot. I have run setup-targetfs-nfs.sh to enable NFS server in my host. Also verified in host with the command

sudo service nfs-kernel-server restart

 * Stopping NFS kernel daemon                                                                                                           [ OK ]
 * Unexporting directories for NFS kernel daemon...                                                                                     [ OK ]
 * Exporting directories for NFS kernel daemon...                                                                                       [ OK ]
 * Starting NFS kernel daemon                                                                                                           [ OK ]

So, the basic communication between PC and Board is OK. The NFS server is also running in the host.

But I am getting NFS mount error,

U-Boot# nfs
cpsw Waiting for PHY auto negotiation to complete...user interrupt!
Using cpsw device
File transfer via NFS from server 192.168.127.27; our IP address is 192.168.127.29
Filename 'zImage/'.
Load address: 0x82000000
Loading: T T T T T T T
Abort

Please help me with this issue?

Best Regards,

Ganesh

  • Hi Ganesh,

    Have you followed this guide:
    processors.wiki.ti.com/.../AM335x_U-Boot_User's_Guide

    Did you perform the described u-boot networ settings:
    processors.wiki.ti.com/.../AM335x_U-Boot_User's_Guide
    before trying the nfs boot. These are:
    setenv serverip <tftp server in your network>
    netmask 255.255.255.0
    dhcp
    saveenv

    Best Regards,
    Yordan
  • Hi Yordan,

    I set ipaddr static.

    U-Boot# print ipaddr
    ipaddr=192.168.1.3
    U-Boot# print serverip
    serverip=192.168.1.1


    My environment variables are:

    U-Boot# printenv
    arch=arm
    args_mmc=run finduuid;setenv bootargs console=${console} ${optargs} root=PARTUUID=${uuid} rw rootfstype=${mmcrootfstype}
    baudrate=115200
    board=BeagleBoard-X15
    board-name=am57xx-evm
    board_name=BeagleBoard-X15
    bootargs=console=ttyO0,115200n8 elevator=noop root=/dev/mmcblk0p2 rw rootwait
    bootcmd=if test ${dofastboot} -eq 1; then echo Boot fastboot requested, resetting dofastboot ...;setenv dofastboot 0; saveenv;echo Booting int;
    bootdelay=1
    bootdir=/boot
    bootenv=uEnv.txt
    bootfile=zImage
    bootm_size=0x10000000
    bootpart=0:2
    bootscript=echo Running bootscript from mmc${mmcdev} ...; source ${loadaddr}
    console=ttyO0,115200n8
    cpu=armv7
    dfu_alt_info_emmc=rawemmc raw 0 3751936;boot part 1 1;rootfs part 1 2;MLO fat 1 1;MLO.raw raw 0x100 0x100;u-boot.img.raw raw 0x300 0x400;spl-o1
    dfu_alt_info_mmc=boot part 0 1;rootfs part 0 2;MLO fat 0 1;MLO.raw raw 0x100 0x100;u-boot.img.raw raw 0x300 0x400;spl-os-args.raw raw 0x80 0x81
    dfu_alt_info_ram=kernel ram 0x80200000 0x4000000;fdt ram 0x80f80000 0x80000;ramdisk ram 0x81000000 0x4000000
    dfu_bufsiz=0x10000
    dofastboot=0
    eth1addr=74:da:ea:0c:dc:a3
    ethact=cpsw
    ethaddr=74:da:ea:0c:dc:a2
    fdt_addr_r=0x88000000
    fdtaddr=0x88000000
    fdtfile=am57xx-beagle-x15.dtb
    fileaddr=82000000
    filesize=330ef0
    findfdt=if test $board_name = omap5_uevm; then setenv fdtfile omap5-uevm.dtb; fi; if test $board_name = dra7xx; then setenv fdtfile dra7-evm.d
    finduuid=part uuid mmc 0:2 uuid
    importbootenv=echo Importing environment from mmc${mmcdev} ...; env import -t ${loadaddr} ${filesize}
    ipaddr=192.168.1.3
    kernel_addr_r=0x82000000
    loadaddr=0x82000000
    loadbootenv=fatload mmc ${mmcdev} ${loadaddr} ${bootenv}
    loadbootscript=fatload mmc ${mmcdev} ${loadaddr} boot.scr
    loadfdt=load mmc ${bootpart} ${fdtaddr} ${bootdir}/${fdtfile};
    loadimage=load mmc ${bootpart} ${loadaddr} ${bootdir}/${bootfile}
    mmcargs=part uuid mmc 0:2 uuid
    mmcboot=mmc dev ${mmcdev}; if mmc rescan; then echo SD/MMC found on device ${mmcdev};if run loadbootenv; then echo Loaded environment from ${b;
    mmcdev=0
    mmcrootfstype=ext4 rootwait
    netargs=setenv bootargs console=${console} ${optargs} root=/dev/nfs nfsroot=${serverip}:${rootpath},${nfsopts} rw ip=dhcp
    netboot=echo Booting from network ...; setenv autoload no; dhcp; run netloadimage; run netloadfdt; run netargs; bootz ${loadaddr} - ${fdtaddr}
    netloadfdt=tftp ${fdtaddr} ${fdtfile}
    netloadimage=tftp ${loadaddr} ${bootfile}
    netmask=255.255.255.0
    nfsopts=nolock
    partitions=uuid_disk=${uuid_gpt_disk};name=rootfs,start=2MiB,size=-,uuid=${uuid_gpt_rootfs}
    ramdisk_addr_r=0x88080000
    rdaddr=0x88080000
    rootpath=/export/rootfs
    scsidevs=0
    serverip=192.168.1.1
    soc=omap5
    static_ip=${ipaddr}:${serverip}:${gatewayip}:${netmask}:${hostname}::off
    stderr=serial
    stdin=serial
    stdout=serial
    usbtty=cdc_acm
    uuid=18e1dc9e-02
    vendor=ti
    ver=U-Boot 2015.07-00080-g4523775-dirty (Feb 06 2017 - 11:30:50 +0530)
    vram=16M



    Best Regards,
    Ganesh
  • Hi Ganesh,

    I'm a bit confused, you say that you set:
    U-Boot# print ipaddr
    ipaddr=192.168.1.3
    U-Boot# print serverip
    serverip=192.168.1.1

    However in your first post the addresses are different:
    File transfer via NFS from server 192.168.127.27; our IP address is 192.168.127.29

    Can you verify that you use static IPs on both the host PC & your custom board?

    Best Regards,
    Yordan
  • Hi Yordan,


    Previously I tested with eth0 interface of PC. Later I changed to eth1 of PC. Hence previous post and first post ip address differs. And both are static only.


    Best Regards,
    Ganesh