targetNFS and linux-devkit on ti-sdk-beagleboard-05.03.02.00

Preioni:

NFS means Network File Server.  This is when the root file system is physically located on the Linux host PC and

the target board accesses the file system via Ethernet.

On Linux host change to the Beagleboard SDK install directory, for the current Beableboard SDK release this would be:

{$HOME}/ti-sdk-beagleboard-05.03.02.00

Then you can run the setup script:

./setup.sh

The script will prompt you to create a minicom script.  Enter Y.

The script will prompt you yo run the script now.  Enter N.

This will generate a minicom script in the SDK install folder.

For kernel and file system via Ethernet it would be named:

setup_uimage-tftp_fs-nfs.minicom

 To run the script:

minicom -S setup_uimage-tftp_fs-nfs.minicom

Minicom will start in script mode waiting for "Press a key to stop autoboot" msg.

Power-cycle the Beagleboard now.

After the script runs minicom will exit.

Since the Beagleboard xM has no NAND flash the script cannot save uboot params

so you would need to rerun the script after a boot / power-cycle.

regards,

michael T

Thanks for the answer

now it's more clear.

but I try to follow your instruction and the boot is blocked with this write:

Welcome to minicom 2.4

OPTIONS: I18n
Compiled on Jan 25 2010, 06:49:09.
Port /dev/ttyS0

Press CTRL-A Z for help on special keys



Texas Instruments X-Loader 1.4.4ss (Aug 19 2010 - 02:49:27)
Beagle xM Rev A
Reading boot sector
Loading u-boot.bin from mmc


U-Boot 2010.03-dirty (Aug 20 2010 - 20:50:46)

OMAP3630/3730-GP ES2.0, CPU-OPP2, L3-165MHz,
OMAP3 Beagle board + LPDDR/NAND
I2C:   ready
DRAM:  512 MB
NAND:  0 MiB                                                                                            
*** Warning - bad CRC or NAND, using default environment                                                
                                                                                                        
In:    serial                                                                                           
Out:   serial                                                                                           
Err:   serial                                                                                           
                                                                                                        
Probing for expansion boards, if none are connected you'll see a harmless I2C error.                    
                                                                                                        
No EEPROM on expansion board                                                                            
Beagle xM Rev A                                                                                         
Die ID #57dc00011ff00000015739eb0b02a017                                                                
Hit any key to stop autobo 0                                                                            
OMAP3 beagleboard.org #setenv bootdelay 3                                                               
OMAP3 beagleboard.org #setenv baudrate 115200                                                           
## Switch baudrate to 115200 bps and press ENTER ...OMAP3 beagleboard.org #setenv oldbootargs ${bootarg}
OMAP3 beagleboard.org #ip=dhcp                                                                          
OMAP3 beagleboard.org #setenv autoload no                                                               
OMAP3 beagleboard.org #setenv oldserverip ${serverip}                                                   
OMAP3 beagleboard.org #setenv serverip 10.0.0.216                                                       
OMAP3 beagleboard.org #setenv oldbootfile ${bootfile}                                                   
OMAP3 beagleboard.org #setenv bootfile uImage-beagleboard.bin                                           
OMAP3 beagleboard.org #setenv oldbootcmd ${bootcmd}                                                     
setenv - set environment variables                                                                      
                                                                                                        
Usage:                                                                                                  
setenv name value ...                                                                                   
    - set environment variable 'name' to 'value ...'                                                    
setenv name                                                                                             
    - delete environment variable 'name'                                                                
OMAP3 beagleboard.org #setenv bootcmd 'dcache off;usb start;dhcp;setenv serverip 10.0.0.216;tftpboot;bo'
OMAP3 beagleboard.org #saveenv                                                                          
Saving Environment to NAND...                                                                           
Erasing Nand...           

My doubt: which files Im ust put on the SD card for the correct but from target NFS?  

How I connect the ethernet cable? directly or via router?

Best regards

Paolo Preioni

Paolo:

The Beagleboard EZSDK 05.03.02 actually supports the Beagleboard-xM board (which does not have NAND). 

That EZSDK has PSP 04.06.00.03, Linux kernel 3.0.8-r109a and SPL/U-Boot 2011-09.  SPL replaces x-loader.

Your log shows that you are running much older software.

With SPL/U-Boot 2011.09 you need to have MLO and u-boot.img in boot partition of SD-Card.  MLO must be copied to SD Card first.

If you run the EZSDK installer and setup.sh script it will setup your linux host as required for NFS file system to work.

I am not familiar with the bootcmd you have shown. 

A typical bootargs for NFS would be: (fill in IP address and path to targetNFS folder)

setenv bootargs console=ttyO2,115200n8 rw noinitrd root=/dev/nfs nfsroot=<Linux host IP address>:<path to targetNFS>,nolock,rsize=1024,wsize=1024 omap_vout.vid1_static_vrfb_alloc=y ip=dhcp

Bootcmd would depend on if kernel ir read from SD Card or via Ethernet.

Regards,

Michael T

I don't understand why my software is old:

I download ti-sdk-beagleboard-05.03.02.00-Linux-x86-Install   and install it.

I execute the script

I put in the beagleboard the SD card "xm test" and follow your instruction.

If I understand right, I must format a new SD card and put the MLO and u-boot.img: where are these files? in the targetNFS directory?

Paolo

paolo:

They would be under the SDK install directory at

./board-support/prebuilt-images/

Reards,

Michael T