• State
  • Locked Locked
  • Replies 4 replies
  • Subscribers 101 subscribers
  • Views 4277 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

TFTP and NFS with the Beaglebone

José Sacerio
Intellectual 370 points

Is there a workaround to get the Beaglebone to boot from TFTP and the mount the NFS?

The uEnv.txt file that is generated by the setup.sh script in the 05.06.00.00 vesrion of teh sdk does not work.

Thanks for your help

  • 0
    TI__Expert 5450 points

    Jose,


    Have you updated the MLO and U-Boot on your SD card as well with the 05.06.00.00 versions?  There was a change to the variable naming conventions in this release so if you are using an older version of the bootloaders, the default variables the uEnv.txt file is trying to use would be incorrect.

    It would also be helpful if you posted a log and the output of doing a "printenv" in u-boot.

    Chase

  • 0 in reply to Chase Maupin
    Expert 1530 points

    Chase,

    Couldn't the problem for NFS/Tftp arise from the VMware NIC configuration?

    If VMware/Linux is behind NAT, would the Bbone be able to access it from the "public" LAN?

    (I'm a nearly novice in this area, and absolute unsure, sorry)



  • 0
    Prodigy 100 points

    Oddly I'm having the same issue... I allowed Setup.sh to re-program my BOOT partition and now I'm kicking myself because I did not save the existing copy. So right now, there is an older copy of the SDK on the SDCard (05.03) but the BOOT partition is setup for (05.06).

    I tried to enable TFTP and NFS mounting on the Beaglebone and now nothing works. The Host is a Linux laptop Ubuntu 12.04 (no virtual machine). And both host and target are connected to the office LAN with a DHCP service on it.

    I don't want to go Off topic from the original poster, but maybe this will help as I can show here what the current Stage 1 & 2 loaders are trying to do... here is a copy of the uEnv.txt file that Startup.sh created;

    ---

    serverip=192.168.168.116

    rootpath=/home/devel/ti-sdk-am335x-evm-05.06.00.00/targetNFS

    bootfile=uImage-am335x-evm.bin

    ip_method=dhcp

    tftp_nfs_boot=echo Booting from network...; dhcp ${loadaddr} ${bootfile}; run netargs; bootm ${loadaddr}

    uenvcmd=run tftp_nfs_boot

    ---

    And here is what the bootloader dumps to the serial port;

    ---

    U-Boot SPL 2011.09 (Nov 04 2011 - 21:43:12)
    Texas Instruments Revision detection unimplemented
    No AC power, disabling frequency switch
    OMAP SD/MMC: 0
    reading u-boot.img
    reading u-boot.img


    U-Boot 2011.09 (Nov 04 2011 - 21:39:19)

    I2C:   ready
    DRAM:  256 MiB
    WARNING: Caches not enabled
    No daughter card present
    NAND:  HW ECC Hamming Code selected
    nand_get_flash_type: second ID read did not match 11,11 against 10,10
    No NAND device found!!!
    0 MiB
    MMC:   OMAP SD/MMC: 0
    *** Warning - readenv() failed, using default environment

    Net:   cpsw
    Hit any key to stop autoboot:  0
    SD/MMC found on device 0
    reading uEnv.txt

    263 bytes read
    Loaded environment from uEnv.txt
    Importing environment from mmc ...
    Running uenvcmd ...
    Booting from network...
    link up on port 0, speed 100, full duplex
    BOOTP broadcast 1
    DHCP client bound to address 192.168.169.169
    Using cpsw device
    TFTP from server 255.255.255.255; our IP address is 192.168.169.169; sending through gateway 192.168.168.254
    Filename 'Boot\x86\wdsnbp.com'.
    Load address: 0x82000000
    Loading: *
    TFTP error: 'File not found or No Access' (1)
    Not retrying...

    TFTP error: 'File not found.' (1)
    Not retrying...

    TFTP error: 'File not found' (1)
    Not retrying...
    ## Error: "netargs" not defined
    Wrong Image Format for bootm command
    ERROR: can't get kernel image!
    reading Bootx86wdsnbp.com

    ** Unable to read "Bootx86wdsnbp.com" from mmc 0:1 **
    Booting from nand ...

    no devices available
    Wrong Image Format for bootm command
    ERROR: can't get kernel image!

    ---

    Any links to info on reverting uEnv.txt back to a non-network bootup, or how to put the new (05.06) build into the flash SD card would be appreciated.

     - Richard

  • 0 in reply to Richard Willis
    Intellectual 705 points

    Hi,

    I had a similar issue with my AM335x starter kit and 05.07 SDK. The uEnv.txt generated by setup.sh for TFTP and NFS boot threw a similar "Wrong Image Format / Can't get kernel Image" Message.

    Here is a file that actually sets up TFTP boot and NFS root file system

    serverip=192.168.2.32
    rootpath=/home/rammy/ti-sdk-am335x-evm-05.07.00.00/targetNFS
    bootfile=uImage
    ipaddr=192.168.2.31
    loadaddr=0x82000000
    tftp_nfs_boot=echo Booting from network...; tftp ${loadaddr} ${bootfile}; bootm ${loadaddr}
    uenvcmd=run tftp_nfs_boot

    I modified the board to use static ip, which can be changed to dhcp also. tftp command loads the file to the loadaddr. Then we boot from loadaddr. NFS is configured with rootpath.

    In case you want to revert back to SDCard boot, use the following file

    bootargs=console=ttyO0,115200n8 root=/dev/mmcblk0p2 mem=128M rootwait
    bootcmd=mmc rescan; fatload mmc 0 0x82000000 uImage; bootm 0x82000000
    uenvcmd=boot

    NOTE: The above files are for AM335x Starter Kit. Please adjust accordingly for other boards.

    Hope this helps.

    Ram