• Locked Locked
  • Replies 1 reply
  • Subscribers 97 subscribers
  • Views 222 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.

upgrade via tftp?

TimothyAr
Prodigy 20 points

hi,

i'm having a few issues with my 6446 and RHEL5. first with the board, i went to enable NFS, NFS boot failed because my settings in the host were initially incorrect. i think my boot arguments/environment is wrong and now i can't seem to go back to booting in standalone mode. the only way i was able to get the OSD was via tftp boot (getting uImage from the tftp server).

i need to update my board to the latest version and from everything i've read, NFS is the ideal way to do so. however, because tftp is the only way my system boots to montavista, i'm thinking of updating via tftp.

from reading the GSG and other resources, NFS seems like a way to map a hosts folder locally. so if NFS is meant to transfer files, then why can't i use tftp as well? i'm thinking of 1) updating the host by following the GSG 2) boot the EVM via tftp 3) telnet to EVM and then transfer the updated files from the host.

sounds like a good idea? if i can resolve the NFS issue, then i can continue upgrading by following the GSG.

thanks,
tim

  • TI__Guru 64470 points

    TimothyAr said:

    i'm having a few issues with my 6446 and RHEL5. first with the board, i went to enable NFS, NFS boot failed because my settings in the host were initially incorrect. i think my boot arguments/environment is wrong and now i can't seem to go back to booting in standalone mode. the only way i was able to get the OSD was via tftp boot (getting uImage from the tftp server).

    i need to update my board to the latest version and from everything i've read, NFS is the ideal way to do so. however, because tftp is the only way my system boots to montavista, i'm thinking of updating via tftp.

    What are you updating?  Is it the linux kernel itself?  If so, the TFTP method seems most appropriate to me, especially initially.  TFTP can be used by the bootloader, u-boot, to retrieve the Linux kernel from a remote server, copy it into the DM6446 memory (RAM) and run.  At that point, once the Linux kernel has started, then NFS comes into play as it can be used by Linux for its filesystem.  The Networked File System can reside on the same remote server to enable easier development.  TFTP and NFS are attempting to solve two different things.

    In my view, you would be using both TFTP and NFS for your early development.  TFTP to retrieve a newly built kernel (in case you are making any driver changes, or patches to the kernel) and NFS to mount a remote file system, rather than have one built and put into the flash on your target hardware.

    TimothyAr said:


    from reading the GSG and other resources, NFS seems like a way to map a hosts folder locally. so if NFS is meant to transfer files, then why can't i use tftp as well? i'm thinking of 1) updating the host by following the GSG 2) boot the EVM via tftp 3) telnet to EVM and then transfer the updated files from the host.

    NFS is not meant to "transfer" files per se.  It provides a facility to the Linux kernel to mount a root filesystem from a remote server via ethernet.