nfs.tar.gz?

Binh,

Where did you download the PSP from?  The directions in the Wiki article you point to assumes that you have the complete Linux EZSDK installation.  In case you don't know U-Boot is used to configure target system and bring up the Linux kernel. 

The PSP is packaged with our Linux distribution and designed to work with a Linux based system.  Not sure why it is distributed separately.  I think if you install the EZSDK from this site: http://www.ti.com/tool/linuxezsdk-davinci you will have the packages you need. 

Regards.

Tommy,

• I downloaded the PSP 04.00.02.14 from here: http://software-dl.ti.com/dsps/dsps_public_sw/psp/LinuxPSP/DM816x_04_00/ 
• I installed EZSDK 5.03.01.15 but still couldn't find nfs.tar.gz. However, I found the "targetfs" folder. Does this folder contain the same thing in the nfs.tar.gz file?
• Does EZSDK 5.03.01.15 include PSP 04.00.02.14? How can I verify this? I need the latest PSP since the Video User Guide (http://processors.wiki.ti.com/index.php/DM816X_AM389X_VPSS_Video_Driver_User_Guide) requires this version of PSP.

• Having failed to find the "nfs.tar.gz" file, I tried the Ethernet route. At the last step in setup.sh from the EZSDK, it asked me to change SW4 to ON for NAND and power on the Eval board with Ethernet & Serial connected so that it can set up a minicom script. I did as instructed but nothing seems to happen (minicom was launched automatically but I saw nothing come up). What does this step actually do? Does it try to write something to the NAND flash on the board?
• The setup.sh script sets up a TFTP server on the Linux host. But it does not seem to do anything about a DHCP server, which I had to manually set up. Then I changed the SW3 on the Eval board to boot from Ethernet (MBOOT[4:0] = 00111] and took out the SDCard. The eval board was able to boot up with BOOTP but when it came to TFTP, it tried to fetch whatever boot file name that is specified in the DHCP reply packet from the DHCP server. Which boot file name should I set up in the DHCP server configuration? Is it "MLO", "u-boot", or "uImage"? The setup.sh script only put the "uImage-dm816x-evm.bin" file in /tftpboot/. What is supposed to be the exact boot sequence over the Ethernet?

Thanks

Binh