Using remote Linux host with AM37x EVM

The telnet is for the console interface to the target system. You have two options to move the SW built on the remote system, one is NFS the other is FTP. Where are you planning to have your root file system?

Could you explain your question. I don't know what you mean by "Where are you planning to have your root file system?"

I planned to do the development on the remote linux host and then transfer the files to the EVM.

The root file system or sometimes you could call the target filesystem can run on the host in a network connection called NFS. This diagram shows an NFS connection:

http://processors.wiki.ti.com/index.php/Installing_the_AM37x_SDK

If the filesystem is running local it could mounted as a ramdisk or on the MMC card or USB. So depending on where the target is has it's filesystem there are different options for placing SW built on the host into the target file system.  Are you familiar with the NFS method for mounting a remote file system?

My configuration is the same as shown in the diagram except for the serial connection, but it appears that is used for the Serial Console Window?

I'm not familiar with NFS but, according to the diagram, the Target file system could run on my host (this is a remote host). 

Which of the options would be best for my situation NFS, ramdisk or on the MMC card or USB?

NFS would be a better option is your developing an application. Your application could be moved into the NFS server and the target would be able to access it.

The diagram has the linux host being located next to the target running a terminal emulator called minicom connected via serial cable. If you can't connect the serial port to the target do you have another PC that you can connect?

Yes I have a PC that can connect to the serial port.

Hi,

I now have the AM37x EVM and both the Ethernet and USB main menu items display "Coming soon". Does this mean that USB and Ethernet are not  supported and I need to connect with the serial cable?

Thanks,

Dave

Ethernet and USB are supported. There just aren't any sample applications integrated into the main menu...yet.

Steve K.

Hi Steve,

How do I determine the IP address so that I can telnet to the board?

The PC and the board are connected to a router

Thanks,

Dave

PC IP: 192.168.15.100

Subnet: 255.255.255.0

Gateway : 192.168.15.1

If you have PC that you can connect to the serial port there a couple of programs that you can use as a terminal emulator, hyper term or tera term. We recommend tera term. If you have not used any terminal emulators before here is a link on how to download and use them.

http://processors.wiki.ti.com/index.php/OMAP35x_Wireless_Connectivity_Getting_Started_Guide#Tools_.28Terminal_Emulator.2C_TFTP_server_and_client.29

Once you set up the serial terminal emulator re-boot the board, after it boots you should get a login prompt, login in as root, no password is required on the target board.

After you log in, type "ifconfig -a" at the command prompt. The ip address should be displayed that you can log in via telnet.

Hi,

Here is the output from "ifconfig -a"

I don't see an IP address to use with telnet

root@dm3730-am3715-evm:~# ifconfig -a
eth4      Link encap:Ethernet  HWaddr 00:50:C2:7E:93:27
          BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
          Interrupt:80

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

usb0      Link encap:Ethernet  HWaddr 2A:AD:CA:BB:57:25
          BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

This is not what we expected. Assuming that the ethernet cable plugged between the board and the network is good, could you please capture the output on the terminal and post that? Please restart the terminal emulator before booting the board.

The terminal output is attached:

Texas Instruments X-Loader 1.46 (May  6 2010 - 23:45:50)
Starting X-loader on MMC
Reading boot sector

212568 Bytes Read from MMC
Starting OS Bootloader from MMC...
Starting OS Bootloader...


U-Boot 2009.11 (May 06 2010 - 23:47:47)

OMAP34xx/35xx-GP ES1.0, CPU-OPP2 L3-165MHz
OMAP3 EVM board + LPDDR/NAND
I2C:   ready
DRAM:  128 MB
NAND:  512 MiB
In:    serial
Out:   serial
Err:   serial
Read back SMSC id 0x92200000
Die ID #03680000061000000156166b0a00b021
Net:   smc911x-0
Hit any key to stop autoboot:  0
mmc1 is available
reading boot.scr

420 bytes read
Running bootscript from mmc ...
## Executing script at 82000000
Saving Environment to NAND...
Erasing Nand...
Erasing at 0x260000 -- 100% complete.
Writing to Nand... done
***** Get kernel from SD card *****
*****
reading uImage

2396416 bytes read
***** Set bootargs to boot fs from SD card*****
*****
***** Boot
*****
## Booting kernel from Legacy Image at 82000000 ...
   Image Name:   Arago/2.6.32-psp3.0.1.6/dm3730-a
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2396352 Bytes =  2.3 MB
   Load Address: 80008000
   Entry Point:  80008000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK
OK

Starting kernel ...

Uncompressing Linux.............................................................
................................................................................
.......... done, booting the kernel.
Linux version 2.6.32 (denis@elrond) (gcc version 4.3.3 (Sourcery G++ Lite 2009q1
-203) ) #1 Fri May 7 12:51:40 EDT 2010
CPU: ARMv7 Processor [413fc082] revision 2 (ARMv7), cr=10c53c7f
CPU: VIPT nonaliasing data cache, VIPT nonaliasing instruction cache
Machine: OMAP3 EVM
Memory policy: ECC disabled, Data cache writeback
OMAP3630/DM3730 ES1.0 (l2cache iva sgx neon isp 192mhz_clk )
SRAM: Mapped pa 0x40200000 to va 0xfe400000 size: 0x100000
Reserving 4194304 bytes SDRAM for VRAM
Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 32512
Kernel command line: console=ttyS0,115200n8 mem=128M noinitrd root=/dev/mmcblk0p
2 rootfstype=ext3 rw rootwait mpurate=1000
PID hash table entries: 512 (order: -1, 2048 bytes)
Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
Memory: 128MB = 128MB total
Memory: 120832KB available (4184K code, 372K data, 172K init, 0K highmem)
Hierarchical RCU implementation.
NR_IRQS:402
Clocking rate (Crystal/Core/MPU): 26.0/400/600 MHz
Reprogramming SDRC clock to 400000000 Hz
GPMC revision 5.0
IRQ: Found an INTC at 0xfa200000 (revision 4.0) with 96 interrupts
Total of 96 interrupts on 1 active controller
OMAP GPIO hardware version 2.5
OMAP clockevent source: GPTIMER1 at 32768 Hz
Console: colour dummy device 80x30
Calibrating delay loop... 597.64 BogoMIPS (lpj=2334720)
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
regulator: core version 0.5
NET: Registered protocol family 16
Target VDD1 OPP = 4, VDD2 OPP = 2
omap3evmdc: Driver registration complete
OMAP DMA hardware revision 5.0
bio: create slab <bio-0> at 0
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
i2c_omap i2c_omap.1: bus 1 rev4.0 at 2600 kHz
twl4030: PIH (irq 7) chaining IRQs 368..375
twl4030: power (irq 373) chaining IRQs 376..383
twl4030: gpio (irq 368) chaining IRQs 384..401
regulator: VMMC1: 1850 <--> 3150 mV normal standby
regulator: VDAC: 1800 mV normal standby
regulator: VAUX2_4030: 2800 mV normal standby
regulator: VPLL2: 1800 mV normal standby
regulator: VSIM: 1800 <--> 3000 mV normal standby
i2c_omap i2c_omap.2: bus 2 rev4.0 at 400 kHz
i2c_omap i2c_omap.3: bus 3 rev4.0 at 400 kHz
Switching to clocksource 32k_counter
musb_hdrc: version 6.0, musb-dma, otg (peripheral+host), debug=0
musb_hdrc: USB OTG mode controller at fa0ab000 using DMA, IRQ 92
NET: Registered protocol family 2
IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
TCP established hash table entries: 4096 (order: 3, 32768 bytes)
TCP bind hash table entries: 4096 (order: 2, 16384 bytes)
TCP: Hash tables configured (established 4096 bind 4096)
TCP reno registered
UDP hash table entries: 256 (order: 0, 4096 bytes)
UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
NET: Registered protocol family 1
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
omap-iommu omap-iommu.0: isp registered
AM37x/DM37x  Linux PSP version 03.00.01.06 (OMAP3EVM)
NetWinder Floating Point Emulator V0.97 (double precision)
VFS: Disk quotas dquot_6.5.2
Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
JFFS2 version 2.2. (NAND) © 2001-2006 Red Hat, Inc.
msgmni has been set to 236
alg: No test for stdrng (krng)
io scheduler noop registered
io scheduler deadline registered
io scheduler cfq registered (default)
OMAP DSS rev 2.0
OMAP DISPC rev 3.0
OMAP VENC rev 2
OMAP DSI rev 1.0
Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
serial8250.0: ttyS0 at MMIO 0x4806a000 (irq = 72) is a ST16654
console [ttyS0] enabled
serial8250.1: ttyS1 at MMIO 0x4806c000 (irq = 73) is a ST16654
serial8250.2: ttyS2 at MMIO 0x49020000 (irq = 74) is a ST16654
brd: module loaded
loop: module loaded
omap2-nand driver initializing
NAND device: Manufacturer ID: 0xad, Chip ID: 0xbc (Hynix NAND 512MiB 1,8V 16-bit
)
Creating 5 MTD partitions on "omap2-nand.0":
0x000000000000-0x000000080000 : "xloader-nand"
0x000000080000-0x000000240000 : "uboot-nand"
0x000000240000-0x000000280000 : "params-nand"
0x000000280000-0x000000780000 : "linux-nand"
0x000000780000-0x000020000000 : "jffs2-nand"
OneNAND driver initializing
omap2-onenand omap2-onenand: Cannot request GPMC CS
omap2-onenand: probe of omap2-onenand failed with error -16
smsc911x: Driver version 2008-10-21.
smsc911x-mdio: probed
eth0: attached PHY driver [Generic PHY] (mii_bus:phy_addr=ffffffff:01, irq=-1)
net eth0: MAC Address: 00:50:c2:7e:93:27
usbcore: registered new interface driver cdc_ether
usbcore: registered new interface driver dm9601
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
ehci-omap ehci-omap.0: OMAP-EHCI Host Controller
ehci-omap ehci-omap.0: new USB bus registered, assigned bus number 1
ehci-omap ehci-omap.0: irq 77, io mem 0x48064800
ehci-omap ehci-omap.0: USB 2.0 started, EHCI 1.00
usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
usb usb1: Product: OMAP-EHCI Host Controller
usb usb1: Manufacturer: Linux 2.6.32 ehci_hcd
usb usb1: SerialNumber: ehci-omap.0
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 3 ports detected
Initializing USB Mass Storage driver...
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
usbcore: registered new interface driver usbtest
g_ether gadget: using random self ethernet address
g_ether gadget: using random host ethernet address
usb0: MAC 2a:ad:ca:bb:57:25
usb0: HOST MAC 2e:5e:38:7e:7f:04
g_ether gadget: Ethernet Gadget, version: Memorial Day 2008
g_ether gadget: g_ether ready
musb_hdrc musb_hdrc: MUSB HDRC host driver
musb_hdrc musb_hdrc: new USB bus registered, assigned bus number 2
usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
usb usb2: Product: MUSB HDRC host driver
usb usb2: Manufacturer: Linux 2.6.32 musb-hcd
usb usb2: SerialNumber: musb_hdrc
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 1 port detected
input: TWL4030 Keypad as /devices/platform/i2c_omap.1/i2c-1/1-004a/twl4030_keypa
d/input/input0
ads7846 spi1.0: touchscreen, irq 335
input: ADS7846 Touchscreen as /devices/platform/omap2_mcspi.1/spi1.0/input/input
1
twl_rtc twl_rtc: rtc core: registered twl_rtc as rtc0
i2c /dev entries driver
Linux video capture interface: v2.00
tvp514x 3-005c: Registered to v4l2 master omap34xxcam!!
omap-iommu omap-iommu.0: isp: version 1.1
usbcore: registered new interface driver uvcvideo
USB Video Class driver (v0.1.0)
OMAP Watchdog Timer Rev 0x31: initial timeout 60 sec
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
Advanced Linux Sound Architecture Driver Version 1.0.21.
usbcore: registered new interface driver snd-usb-audio
No device for DAI omap-mcbsp-dai-0
No device for DAI omap-mcbsp-dai-1
No device for DAI omap-mcbsp-dai-2
No device for DAI omap-mcbsp-dai-3
No device for DAI omap-mcbsp-dai-4
OMAP3 EVM SoC init
asoc: twl4030 <-> omap-mcbsp-dai-0 mapping ok
ALSA device list:
  #0: omap3evm (twl4030)
TCP cubic registered
NET: Registered protocol family 17
NET: Registered protocol family 15
Power Management for TI OMAP3.
Switched to new clocking rate (Crystal/Core/MPU): 26.0/400/1000 MHz
IVA2 clocking rate: 800 MHz
SmartReflex driver initialized
VFP support v0.3: implementor 41 architecture 3 part 30 variant c rev 3
twl_rtc twl_rtc: setting system clock to 2010-05-13 00:34:28 UTC (1273710868)
tvp514x 3-005c: tvp5146m2 found at 0xb8 (OMAP I2C adapter)
omapdss DPI error: display already enabled
omap_vout omap_vout: 'lcd' Display already enabled
omapdss DPI error: display already enabled
omap_vout omap_vout: 'lcd' Display already enabled
omap_vout omap_vout: Buffer Size = 3686400
omap_vout omap_vout: : registered and initialized video device 1
omap_vout omap_vout: Buffer Size = 3686400
omap_vout omap_vout: : registered and initialized video device 2
Waiting for root device /dev/mmcblk0p2...
mmc0: new SDHC card at address 947d
mmcblk0: mmc0:947d SD04G 3.69 GiB
 mmcblk0: p1 p2 p3
kjournald starting.  Commit interval 5 seconds
EXT3-fs (mmcblk0p2): warning: maximal mount count reached, running e2fsck is rec
ommended
EXT3-fs (mmcblk0p2): using internal journal
EXT3-fs (mmcblk0p2): recovery complete
EXT3-fs (mmcblk0p2): mounted filesystem with writeback data mode
VFS: Mounted root (ext3 filesystem) on device 179:2.
Freeing init memory: 172K
INIT: version 2.86 booting
Please wait: booting...
Starting udev
udevd[534]: unable to move watches dir '/dev/.udev/watch', old watches will not
be restored: Directory not empty
Remounting root file system...
Caching udev devnodes
Populating dev cachemv: cannot rename '/tmp/uname': No such file or directory
logger: mount: mount point /proc/bus/usb does not exist
ALSA: Restoring mixer settings...
kjournald starting.  Commit interval 5 seconds
EXT3-fs (mmcblk0p3): warning: maximal mount count reached, running e2fsck is rec
ommended
EXT3-fs (mmcblk0p3): using internal journal
EXT3-fs (mmcblk0p3): recovery complete
EXT3-fs (mmcblk0p3): mounted filesystem with writeback data mode
Configuring network interfaces... ifconfig: SIOCGIFFLAGS: No such device
done.
Setting up IP spoofing protection: rp_filter.
INIT: Entering runlevel: 5
Starting system message bus: dbus.
Starting telnet daemon.
Starting syslogd/klogd: done
Starting thttpd.
Starting PVR
Starting Matrix GUI application.

 _____                    _____           _         _
|  _  |___ ___ ___ ___   |  _  |___ ___  |_|___ ___| |_
|     |  _| .'| . | . |  |   __|  _| . | | | -_|  _|  _|
|__|__|_| |__,|_  |___|  |__|  |_| |___|_| |___|___|_|
              |___|                    |___|

Arago Project http://arago-project.org dm3730-am3715-evm ttyS0

Arago 2010.05 dm3730-am3715-evm ttyS0

dm3730-am3715-evm login:

This device does not look to be attempting to get an IP address. Is the board connected on ethernet to a good network connection? What is the platform you're using here? DM3730?

We need you to capture your u-boot parameters. This is done by starting the board and pressing the space bar on the terninal when you see a countdown to boot being printed. Type "printenv", capture the output and please post that to this forum.

Platform: Mistral OMAP EVM MAIN BOARD REV G

TMDXEVM3715

u-boot parameters:

Texas Instruments X-Loader 1.46 (May  6 2010 - 23:45:50)
Starting X-loader on MMC
Reading boot sector

212568 Bytes Read from MMC
Starting OS Bootloader from MMC...
Starting OS Bootloader...


U-Boot 2009.11 (May 06 2010 - 23:47:47)

OMAP34xx/35xx-GP ES1.0, CPU-OPP2 L3-165MHz
OMAP3 EVM board + LPDDR/NAND
I2C:   ready
DRAM:  128 MB
NAND:  512 MiB
In:    serial
Out:   serial
Err:   serial
Read back SMSC id 0x92200000
Die ID #03680000061000000156166b0a00b021
Net:   smc911x-0
Hit any key to stop autoboot:  0
OMAP3_EVM #

OMAP3_EVM # printenv
bootcmd=if mmc init; then if run loadbootscript; then run bootscript; else if ru
n loaduimage; then run mmcboot; else run nandboot; fi; fi; else run nandboot; fi
baudrate=115200
bootfile=uImage
loadaddr=0x82000000
usbtty=cdc_acm
console=ttyS2,115200n8
mmcargs=setenv bootargs console=${console} root=/dev/mmcblk0p2 rw rootfstype=ext
3 rootwait
nandargs=setenv bootargs console=${console} root=/dev/mtdblock4 rw rootfstype=jf
fs2
loadbootscript=fatload mmc 0 ${loadaddr} boot.scr
bootscript=echo Running bootscript from mmc ...; source ${loadaddr}
loaduimage=fatload mmc 0 ${loadaddr} uImage
mmcboot=echo Booting from mmc ...; run mmcargs; bootm ${loadaddr}
nandboot=echo Booting from nand ...; run nandargs; onenand read ${loadaddr} 2800
00 400000; bootm ${loadaddr}
dieid#=03680000061000000156166b0a00b021
ethact=smc911x-0
filesize=1A4
bootdelay=3
stdin=serial
stdout=serial
stderr=serial

Environment size: 886/131068 bytes

I want to make that you can get an ip address.

Please again re-boot the board and stop inside u-boot, press the space bar during the countdown. Type "dhcp" at the prompt, please capture the output and post.

Texas Instruments X-Loader 1.46 (May  6 2010 - 23:45:50)
Starting X-loader on MMC
Reading boot sector

212568 Bytes Read from MMC
Starting OS Bootloader from MMC...
Starting OS Bootloader...


U-Boot 2009.11 (May 06 2010 - 23:47:47)

OMAP34xx/35xx-GP ES1.0, CPU-OPP2 L3-165MHz
OMAP3 EVM board + LPDDR/NAND
I2C:   ready
DRAM:  128 MB
NAND:  512 MiB
In:    serial
Out:   serial
Err:   serial
Read back SMSC id 0x92200000
Die ID #03680000061000000156166b0a00b021
Net:   smc911x-0
Hit any key to stop autoboot:  0
OMAP3_EVM #
OMAP3_EVM # dhcp
smc911x: detected LAN9220 controller
smc911x: phy initialized
smc911x: MAC 00:50:c2:7e:93:27
BOOTP broadcast 1
BOOTP broadcast 2
DHCP client bound to address 192.168.15.102
Using smc911x-0 device
TFTP from server 0.0.0.0; our IP address is 192.168.15.102; sending through gate
way 192.168.15.1
Filename 'uImage'.
Load address: 0x82000000
Loading: T T T T T T T T T T
Retry count exceeded; starting again
smc911x: detected LAN9220 controller
smc911x: phy initialized
smc911x: MAC 00:50:c2:7e:93:27
BOOTP broadcast 1
DHCP client bound to address 192.168.15.102
Using smc911x-0 device
TFTP from server 0.0.0.0; our IP address is 192.168.15.102; sending through gate
way 192.168.15.1
Filename 'uImage'.
Load address: 0x82000000
Loading: T T T T T T T T T T
Retry count exceeded; starting again
smc911x: detected LAN9220 controller
smc911x: phy initialized
smc911x: MAC 00:50:c2:7e:93:27
BOOTP broadcast 1
DHCP client bound to address 192.168.15.102
Using smc911x-0 device
TFTP from server 0.0.0.0; our IP address is 192.168.15.102; sending through gate
way 192.168.15.1
Filename 'uImage'.
Load address: 0x82000000
Loading: T T T T T T T T T T
Retry count exceeded; starting again
smc911x: detected LAN9220 controller
smc911x: phy initialized
smc911x: MAC 00:50:c2:7e:93:27
BOOTP broadcast 1
DHCP client bound to address 192.168.15.102
Using smc911x-0 device
TFTP from server 0.0.0.0; our IP address is 192.168.15.102; sending through gate
way 192.168.15.1
Filename 'uImage'.
Load address: 0x82000000
Loading: T T T T T

Your ip address will be 192.168.15.102

Let the board boot, from serial console after you log in type "ifconfig eth4 up" after this completes type "ifconfig -a", you should see the above ip address. You should be able to telnet to the target board at this point. If you can't please post the ifconfig -a results.

C:\Documents and Settings\>telnet 192.168.15.102
Connecting To 192.168.15.102...Could not open connection to the host, on port 23
: Connect failed

dm3730-am3715-evm login: root
root@dm3730-am3715-evm:~# ifconfig eth4 up
net eth4: SMSC911x/921x identified at 0xc8860000, IRQ: 336
root@dm3730-am3715-evm:~# ifconfig -a
eth4      Link encap:Ethernet  HWaddr 00:50:C2:7E:93:27
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
          Interrupt:80

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

usb0      Link encap:Ethernet  HWaddr 2A:AD:CA:BB:57:25
          BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

root@dm3730-am3715-evm:~#

Seeing eth4 makes me wonder why it is not eth0.  Can you look in your target root file system at the etc/udev/rules.d directory and edit the file 70-persistent-net.rules. Make sure you only have one entry in there for the MAC address that matches your Ethernet MAC.  From your other posts, I think it should look like this

SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:50:c2:7e:93:27", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"

Steve K.

Does 70-persistent-net.rules need to  be modified on the SD card before booting?

root@dm3730-am3715-evm:/etc/udev/rules.d# more 70-persistent-net.rules
# This file was automatically generated by the /lib/udev/write_net_rules
# program, run by the persistent-net-generator.rules rules file.
#
# You can modify it, as long as you keep each rule on a single
# line, and change only the value of the NAME= key.

# net device ()
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:50:c2:7e:8e:7
0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"

# net device ()
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:50:c2:7e:8d:2
2", ATTR{type}=="1", KERNEL=="eth*", NAME="eth1"

# net device ()
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:50:c2:7e:93:1
6", ATTR{type}=="1", KERNEL=="eth*", NAME="eth2"

# net device ()
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:50:c2:7e:93:2
9", ATTR{type}=="1", KERNEL=="eth*", NAME="eth3"

# net device ()
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:50:c2:7e:93:2
7", ATTR{type}=="1", KERNEL=="eth*", NAME="eth4"
root@dm3730-am3715-evm:/etc/udev/rules.d#

Yes.  Actually you can delete the file and then boot the board. The udevd will re-create the file correctly.

Steve K.

After deleting /etc/udev/rules.d/70-persistent-net.rules and rebooting the board,

I am now able to telnetto 192.168.15.102

Could you give us some history on the SD card that is in your board? We would like to know if the SD card that you are currently using came with the board and has not been in another board.

The SD card came with the board.

Hai steve

I delete the file(70-persistent-net.rules) for the every boot on various board.If i delete this file it automatically regenerated steve.Is there any other option to delete the file without manually via a script or another program.If we write a program for the file deletion,it will be happens while on booting.is it possible? Is it,How can steve????\

Thanks in advance.