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.

dm8148 - ping: sendto: Network is unreachable

Other Parts Discussed in Thread: PCF8575, TPS65910, PMP

Dear Experts,

I am new and using ti-ezsdk_dm814x-evm_5_05_01_04 and 8148evm board.

I use the prebuilt-images and ezsdk-dm814x-evm-rootfs.tar.gz.
After booting from SD card. (uboot/kernel/rooffs all in SD card)
I can not use "ping" command.
Is there anything should be modified to enable network working correctly ?

Below is my booting parameters and booting message.

------------ uboot ------------
uboot>>mmcinfo 0
uboot>>setenv bootargs 'console=ttyO0,115200n8 rootwait root=/dev/mmcblk0p2 rw mem=256M earlyprintk notifyk.vpssm3_sva=0xBF900000 vram=50M ti814xfb.vram=0:16M,1:16M,2:6M ip=off noinitrd'
uboot>>fatload mmc 0 0x80009000 uImage
uboot>>bootm 0x80009000

------------ Kernel ------------
root@dm814x-evm:~# ifconfig
eth0      Link encap:Ethernet  HWaddr 40:5F:C2:23:06:DD
          inet6 addr: fe80::425f:c2ff:fe23:6dd/64 Scope:Link
          UP BROADCAST RUNNING ALLMULTI MULTICAST  MTU:1500  Metric:1
          RX packets:44161 errors:0 dropped:15011 overruns:0 frame:0
          TX packets:617 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:4938183 (4.7 MiB)  TX bytes:352782 (344.5 KiB)
          Interrupt:40

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:6 errors:0 dropped:0 overruns:0 frame:0
          TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:340 (340.0 B)  TX bytes:340 (340.0 B)

root@dm814x-evm:~# ping 172.17.14.9
PING 172.17.14.9 (172.17.14.9): 56 data bytes
ping: sendto: Network is unreachable


------------ ------------ ------------

Booting message:
## Booting kernel from Legacy Image at 80009000 ...
   Image Name:   Arago/2.6.37-psp04.04.00.01/dm81
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2796356 Bytes = 2.7 MiB
   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.37 (x0029463@swubn01) (gcc version 4.3.3 (Sourcery G++ Lite 2009q1-203) ) #1 Wed Oct 10 14:02:40 IST 2012

CPU: ARMv7 Processor [413fc082] revision 2 (ARMv7), cr=10c53c7f

CPU: VIPT nonaliasing data cache, VIPT aliasing instruction cache

Machine: ti8148evm

bootconsole [earlycon0] enabled

vram size = 52428800 at 0x0

reserved size = 52428800 at 0x0

FB: Reserving 52428800 bytes SDRAM for VRAM

Memory policy: ECC disabled, Data cache writeback

OMAP chip is TI8148 2.1

SRAM: Mapped pa 0x402f1000 to va 0xfe400000 size: 0xf000

Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 52224

Kernel command line: console=ttyO0,115200n8 rootwait root=/dev/mmcblk0p2 rw mem=256M earlyprintk notifyk.vpssm3_sva=0xBF900000 vram=50M ti814xfb.vram=0:16M,1:16M,2:6M ip=off noinitrd

PID hash table entries: 1024 (order: 0, 4096 bytes)

Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)

Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)

Memory: 206MB = 206MB total

Memory: 202680k/202680k available, 59464k reserved, 0K highmem

Virtual kernel memory layout:

    vector  : 0xffff0000 - 0xffff1000   (   4 kB)

    fixmap  : 0xfff00000 - 0xfffe0000   ( 896 kB)

    DMA     : 0xffc00000 - 0xffe00000   (   2 MB)

    vmalloc : 0xd0800000 - 0xf8000000   ( 632 MB)

    lowmem  : 0xc0000000 - 0xd0000000   ( 256 MB)

    pkmap   : 0xbfe00000 - 0xc0000000   (   2 MB)

    modules : 0xbf000000 - 0xbfe00000   (  14 MB)

      .init : 0xc0008000 - 0xc003d000   ( 212 kB)

      .text : 0xc003d000 - 0xc0549000   (5168 kB)

      .data : 0xc054a000 - 0xc05970c0   ( 309 kB)

SLUB: Genslabs=11, HWalign=64, Order=0-3, MinObjects=0, CPUs=1, Nodes=1

NR_IRQS:407

IRQ: Found an INTC at 0xfa200000 (revision 5.0) with 128 interrupts

Total of 128 interrupts on 1 active controller

GPMC revision 6.0

Trying to install interrupt handler for IRQ400

Trying to install interrupt handler for IRQ401

Trying to install interrupt handler for IRQ402

Trying to install interrupt handler for IRQ403

Trying to install interrupt handler for IRQ404

Trying to install interrupt handler for IRQ405

Trying to install interrupt handler for IRQ406

Trying to install type control for IRQ407

Trying to set irq flags for IRQ407

OMAP clockevent source: GPTIMER1 at 20000000 Hz

Console: colour dummy device 80x30

Calibrating delay loop... 599.65 BogoMIPS (lpj=2998272)

pid_max: default: 32768 minimum: 301

Security Framework initialized

Mount-cache hash table entries: 512

CPU: Testing write buffer coherency: ok

devtmpfs: initialized

omap_voltage_early_init: voltage driver support not added

regulator: core version 0.5

regulator: dummy:

NET: Registered protocol family 16

omap_voltage_domain_lookup: Voltage driver init not yet happened.Faulting!

omap_voltage_add_dev: VDD specified does not exist!

OMAP GPIO hardware version 0.1

OMAP GPIO hardware version 0.1

OMAP GPIO hardware version 0.1

OMAP GPIO hardware version 0.1

omap_mux_init: Add partition: #1: core, flags: 4

NOR: Can't request GPMC CS

Debugfs: Only enabling/disabling deep sleep and wakeup timer is supported now

registered ti81xx_vpss device

registered ti81xx_vidout device

registered ti81xx on-chip HDMI device

registered ti81xx_fb device

registered ti81xx_vin device

ti81xx_pcie: Invoking PCI BIOS...

ti81xx_pcie: Setting up Host Controller...

ti81xx_pcie: Register base mapped @0xd0820000

ti81xx_pcie: Starting PCI scan...

PCI: bus0: Fast back to back transfers enabled

bio: create slab <bio-0> at 0

vgaarb: loaded

SCSI subsystem initialized

usbcore: registered new interface driver usbfs

usbcore: registered new interface driver hub

usbcore: registered new device driver usb

USBSS revision 4ea2080b

registerd cppi-dma Intr @ IRQ 17

Cppi41 Init Done

omap_i2c omap_i2c.1: bus 1 rev4.0 at 100 kHz

pcf857x 1-0021: gpios 128..143 on a pcf8575

regulator: VRTC: 1800 mV

regulator: VIO: 1500 mV

regulator: VDD1: 600 <--> 1500 mV at 1200 mV

regulator: VDD2: 600 <--> 1500 mV at 1200 mV

regulator: VDDCTRL: 600 <--> 1400 mV at 1200 mV

regulator: LDO1: 1100 <--> 3300 mV at 1800 mV

regulator: LDO2: 1100 <--> 3300 mV at 1800 mV

regulator: LDO3: 1100 <--> 3300 mV at 3300 mV

regulator: LDO4: 1100 <--> 3300 mV at 1800 mV

regulator: LDO5: 1100 <--> 3300 mV at 3300 mV

regulator: LDO6: 1100 <--> 3300 mV at 3300 mV

regulator: LDO7: 1100 <--> 3300 mV at 3300 mV

regulator: LDO8: 1100 <--> 3300 mV at 1800 mV

tps65910 1-002d: No interrupt support, no core IRQ

omap_i2c omap_i2c.3: bus 3 rev4.0 at 100 kHz

Advanced Linux Sound Architecture Driver Version 1.0.23.

Switching to clocksource gp timer

musb-hdrc: version 6.0, host, debug=0

musb-hdrc musb-hdrc.0: dma type: dma-cppi41

MUSB controller-0 revision 4ea20800

musb-hdrc musb-hdrc.0: MUSB HDRC host driver

musb-hdrc musb-hdrc.0: new USB bus registered, assigned bus number 1

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: MUSB HDRC host driver

usb usb1: Manufacturer: Linux 2.6.37 musb-hcd

usb usb1: SerialNumber: musb-hdrc.0

hub 1-0:1.0: USB hub found

hub 1-0:1.0: 1 port detected

musb-hdrc musb-hdrc.0: USB Host mode controller at d081e000 using DMA, IRQ 18

musb-hdrc musb-hdrc.1: dma type: dma-cppi41

MUSB controller-1 revision 4ea20800

musb-hdrc musb-hdrc.1: MUSB HDRC host driver

musb-hdrc musb-hdrc.1: 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.37 musb-hcd

usb usb2: SerialNumber: musb-hdrc.1

hub 2-0:1.0: USB hub found

hub 2-0:1.0: 1 port detected

musb-hdrc musb-hdrc.1: USB Host mode controller at d0826800 using DMA, IRQ 19

NET: Registered protocol family 2

IP route cache hash table entries: 2048 (order: 1, 8192 bytes)

TCP established hash table entries: 8192 (order: 4, 65536 bytes)

TCP bind hash table entries: 8192 (order: 3, 32768 bytes)

TCP: Hash tables configured (established 8192 bind 8192)

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.

NetWinder Floating Point Emulator V0.97 (double precision)

PMU: registered new PMU device of type 0

omap-iommu omap-iommu.0: ducati registered

omap-iommu omap-iommu.1: sys registered

JFFS2 version 2.2. (NAND) c 2001-2006 Red Hat, Inc.

msgmni has been set to 395

io scheduler noop registered

io scheduler deadline registered

io scheduler cfq registered (default)

Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled

omap_uart.0: ttyO0 at MMIO 0x48020000 (irq = 72) is a OMAP UART0

console [ttyO0] enabled, bootconsole disabled
console [ttyO0] enabled, bootconsole disabled

omap_uart.1: ttyO1 at MMIO 0x48022000 (irq = 73) is a OMAP UART1
omap_uart.2: ttyO2 at MMIO 0x48024000 (irq = 74) is a OMAP UART2
omap_uart.3: ttyO3 at MMIO 0x481a6000 (irq = 44) is a OMAP UART3
omap_uart.4: ttyO4 at MMIO 0x481a8000 (irq = 45) is a OMAP UART4
omap_uart.5: ttyO5 at MMIO 0x481aa000 (irq = 46) is a OMAP UART5
brd: module loaded
loop: module loaded
ahci ahci.0: forcing PORTS_IMPL to 0x1
ahci ahci.0: AHCI 0001.0300 32 slots 1 ports 3 Gbps 0x1 impl platform mode
ahci ahci.0: flags: ncq sntf pm led clo only pmp pio slum part ccc apst
scsi0 : ahci_platform
ata1: SATA max UDMA/133 mmio [mem 0x4a140000-0x4a150fff] port 0x100 irq 16
omap2-nand driver initializing
ONFI flash detected
ONFI param page 0 valid
NAND device: Manufacturer ID: 0x2c, Chip ID: 0xca (Micron NAND 256MiB 3,3V 16-bit)
Creating 6 MTD partitions on "omap2-nand.0":
0x000000000000-0x000000020000 : "U-Boot-min"
0x000000020000-0x000000260000 : "U-Boot"
0x000000260000-0x000000280000 : "U-Boot Env"
0x000000280000-0x0000006c0000 : "Kernel"
0x0000006c0000-0x00000cee0000 : "File System"
0x00000cee0000-0x000010000000 : "Reserved"
davinci_mdio davinci_mdio.0: davinci mdio revision 1.6
davinci_mdio davinci_mdio.0: no live phy, scanning all
davinci_mdio: probe of davinci_mdio.0 failed with error -5
CAN device driver interface
CAN bus driver for Bosch D_CAN controller 1.0
d_can d_can: d_can device registered (irq=52, irq_obj=53)
usbcore: registered new interface driver cdc_ether
usbcore: registered new interface driver dm9601
usbcore: registered new interface driver cdc_acm
cdc_acm: v0.26:USB Abstract Control Model driver for USB modems and ISDN adapters
Initializing USB Mass Storage driver...
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
mice: PS/2 mouse device common for all mice
ata1: SATA link down (SStatus 0 SControl 300)
qt602240_ts 1-004a: Family ID: 128 Variant ID: 1 Version: 22 Build: 171
qt602240_ts 1-004a: Matrix X Size: 18 Matrix Y Size: 12 Object Num: 17
input: AT42QT602240/ATMXT224 Touchscreen as /devices/platform/omap/omap_i2c.1/i2c-1/1-004a/input/input0
omap_rtc omap_rtc: rtc core: registered omap_rtc as rtc0
i2c /dev entries driver
Linux video capture interface: v2.00
usbcore: registered new interface driver uvcvideo
USB Video Class driver (v1.0.0)
OMAP Watchdog Timer Rev 0x00: initial timeout 60 sec
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
notify_init : notify drivercreated  for  remote proc id 2 at physical Address 0xbf900000
usbcore: registered new interface driver snd-usb-audio
asoc: tlv320aic3x-hifi <-> davinci-mcasp.2 mapping ok
ALSA device list:
  #0: TI81XX EVM
nf_conntrack version 0.5.0 (3166 buckets, 12664 max)
ip_tables: (C) 2000-2006 Netfilter Core Team
TCP cubic registered
NET: Registered protocol family 17
can: controller area network core (rev 20090105 abi 8)
NET: Registered protocol family 29
can: raw protocol (rev 20090105)
can: broadcast manager protocol (rev 20090105 t)
Registering the dns_resolver key type
VFP support v0.3: implementor 41 architecture 3 part 30 variant c rev 3
omap_voltage_late_init: Voltage driver support not added
Power Management for TI81XX.
Detected MACID=40:5f:c2:23:6:dd
omap_rtc omap_rtc: setting system clock to 2000-01-01 00:00:00 UTC (946684800)
Waiting for root device /dev/mmcblk0p2...
mmc0: new high speed SD card at address 0007
mmcblk0: mmc0:0007 SD02G 1.86 GiB
 mmcblk0: p1 p2
EXT3-fs: barriers not enabled
kjournald starting.  Commit interval 5 seconds
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.
devtmpfs: mounted
Freeing init memory: 212K

INIT: version 2.86 booting

Error opening /dev/fb0: No such file or directory
Please wait: booting...
Starting udev
udevd (79): /proc/79/oom_adj is deprecated, please use /proc/79/oom_score_adj instead.
Remounting root file system...
Caching udev devnodes
NET: Registered protocol family 10
ALSA: Restoring mixer settings...
No state is present for card EVM
Configuring network interfaces... Found hardware: "" "" "" "" ""
Hardware is initialized using a generic method
No state is present for card EVM
PHY 0:00 not found
PHY 0:01 not found
ADDRCONF(NETDEV_UP): eth0: link is not ready
eth0      no wireless extensions.

udhcpc (v1.13.2) started
Sending discover...
Sending discover...
Sending discover...
No lease, forking to background
done.
Setting up IP spoofing protection: rp_filter.
Wed Oct 10 15:52:00 UTC 2012

INIT: Entering runlevel: 5

Loading HDVICP2 Firmware
DM814X prcm_config_app version: 2.0.0.1
Doing PRCM settings...
    PRCM for IVHD0 is in Progress, Please wait.....  
            BW Phy Addr : 0x48180600 Data : 0x00000001
            AW Phy Addr : 0x48180600 Data : 0x00000002
            Phy Addr : 0x48180c04 Data : 0x00000037
            BW Phy Addr : 0x48180620 Data : 0x00070000
            AW Phy Addr : 0x48180620 Data : 0x00050002
            BW Phy Addr : 0x48180624 Data : 0x00030000
            AW Phy Addr : 0x48180624 Data : 0x00010002
            Phy Addr : 0x48180600 Data : 0x00000102
            BW Phy Addr : 0x48180c10 Data : 0x00000007
            AW Phy Addr : 0x48180c10 Data : 0x00000003
            Phy Addr : 0x48180c14 Data : 0x00000004
            BW Phy Addr : 0x58088000 Data : 0x47c54a20
            AW Phy Addr : 0x58088000 Data : 0xeafffffe
            BW Phy Addr : 0x58098000 Data : 0x351e65af
            AW Phy Addr : 0x58098000 Data : 0xeafffffe
            BW Phy Addr : 0x48180c10 Data : 0x00000003
            AW Phy Addr : 0x48180c10 Data : 0x00000000
            Phy Addr : 0x48180c14 Data : 0x00000007
    PRCM for IVHD0 is Done Successfully  
PRCM Initialization completed
SysLink version : 2.20.00.14
SysLink module created on Date:Oct 10 2012 Time:14:49:49
FIRMWARE: I2cInit will be done by M3
FIRMWARE: Memory map bin file not passed
Usage : firmware_loader <Processor Id> <Location of Firmware> <start|stop> [-mmap <memory_map_file>] [-i2c <0|1>]
===Mandatory arguments===
<Processor Id>         0: DSP, 1: Video-M3, 2: Vpss-M3
<Location of Firmware> firmware binary file
<start|stop>           to start/stop the firmware
===Optional arguments===
-mmap                  input memory map bin file name
-i2c                   0: i2c init not done by M3, 1(default): i2c init done by M3
FIRMWARE: isI2cInitRequiredOnM3: 1
FIRMWARE: Default memory configuration is used
Firmware Loader debugging not configured
Default FL_DEBUG: warning
Allowed FL_DEBUG levels: error, warning, info, debug, log
MemCfg: DCMM (Dynamically Configurable Memory Map) Version :  2.1.2.1
FIRMWARE: 1 start Successful
Loading HDVPSS Firmware
FIRMWARE: I2cInit will be done by M3
FIRMWARE: Memory map bin file not passed
Usage : firmware_loader <Processor Id> <Location of Firmware> <start|stop> [-mmap <memory_map_file>] [-i2c <0|1>]
===Mandatory arguments===
<Processor Id>         0: DSP, 1: Video-M3, 2: Vpss-M3
<Location of Firmware> firmware binary file
<start|stop>           to start/stop the firmware
===Optional arguments===
-mmap                  input memory map bin file name
-i2c                   0: i2c init not done by M3, 1(default): i2c init done by M3
FIRMWARE: isI2cInitRequiredOnM3: 1
FIRMWARE: Default memory configuration is used
Firmware Loader debugging not configured
Default FL_DEBUG: warning
Allowed FL_DEBUG levels: error, warning, info, debug, log
MemCfg: DCMM (Dynamically Configurable Memory Map) Version :  2.1.2.1
FIRMWARE: 2 start Successful
Configuring fb0 to LCD
HDMI W1 rev 4.0
HDMI CEC Spec version 1.2
I2C No Ack


Starting system message bus: dbus.
Starting Dropbear SSH server: dropbear.
Starting telnet daemon.
Starting network benchmark server: netserver.
Starting syslogd/klogd: done
Starting thttpd.
Starting PVR
/dev/mem opened.
Memory mapped at address 0x402c4000.
Read at address  0x48180F04 (0x402c4f04): 0x00000001
Write at address 0x48180F04 (0x402c4f04): 0x00000000, readback 0x00000000
/dev/mem opened.
Memory mapped at address 0x40110000.
Read at address  0x48180900 (0x40110900): 0x00000102
Write at address 0x48180900 (0x40110900): 0x00000002, readback 0x00000002
/dev/mem opened.
Memory mapped at address 0x4023c000.
Read at address  0x48180920 (0x4023c920): 0x00040002
Write at address 0x48180920 (0x4023c920): 0x00000002, readback 0x00000002
Starting Matrix GUI application.

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

Arago Project http://arago-project.org dm814x-evm ttyO0

Arago 2011.09 dm814x-evm ttyO0

dm814x-evm login:

--------------------------------

thx ~

HB

  • Hello,

    Please, try

    root@dm814x-evm:~# ifconfig eth0 XXX.XXX.XXX.XXX up

    (enter the desired IP address of the board instead of "X").

    OR edit your /etc/network/interfaces file (search the Internet for /etc/network/interfaces to find examples).

    OR alternatively change the bootargs: instead of " ip=off", use something like ip=XXX.XXX.XXX.XXX (or you could use the more elaborate template ip=<my-ip>:<serv-ip>:<gw-ip>:<netmask>:<name>:<dev>:<auto>).

    BR

    Vladimir

  • Dear Vladimir,

    I change bootags as

    "setenv bootargs 'console=ttyO0,115200n8 rootwait root=/dev/mmcblk0p2 rw mem=256M earlyprintk notifyk.vpssm3_sva=0xBF900000 vram=50M ti814xfb.vram=0:16M,1:16M,2:6M ip=dhcp noinitrd'"

    but booting process can't get DHCP ip address. (DHCP server is no problem)

    After enter kernel, I try ifconfig command as below, I still can not ping correctly.

    ===== ifconfig eth0 ======================

    root@dm814x-evm:~# ifconfig eth0 172.17.14.85 up
    root@dm814x-evm:~# ifconfig
    eth0      Link encap:Ethernet  HWaddr 40:5F:C2:23:06:DD
              inet addr:172.17.14.85  Bcast:172.17.255.255  Mask:255.255.0.0
              inet6 addr: fe80::425f:c2ff:fe23:6dd/64 Scope:Link
              UP BROADCAST RUNNING ALLMULTI MULTICAST  MTU:1500  Metric:1
              RX packets:1153 errors:0 dropped:716 overruns:0 frame:0
              TX packets:25 errors:0 dropped:0 overruns:0 carrier:0
              collisions:0 txqueuelen:1000
              RX bytes:136231 (133.0 KiB)  TX bytes:11678 (11.4 KiB)
              Interrupt:40

    lo        Link encap:Local Loopback
              inet addr:127.0.0.1  Mask:255.0.0.0
              inet6 addr: ::1/128 Scope:Host
              UP LOOPBACK RUNNING  MTU:16436  Metric:1
              RX packets:6 errors:0 dropped:0 overruns:0 frame:0
              TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
              collisions:0 txqueuelen:0
              RX bytes:340 (340.0 B)  TX bytes:340 (340.0 B)

    root@dm814x-evm:~# ping 172.17.14.9
    PING 172.17.14.9 (172.17.14.9): 56 data bytes

    --- 172.17.14.9 ping statistics ---
    47 packets transmitted, 0 packets received, 100% packet loss
    root@dm814x-evm:~#

    =======================================

    And I checked /etc/network/interfaces, this file should configure to DHCP.

    ==== interfaces ========================

    # /etc/network/interfaces -- configuration file for ifup(8), ifdown(8)
     
    # The loopback interface
    auto lo
    iface lo inet loopback


    # Wireless interfaces
    #
    # Example of an unencrypted (no WEP or WPA) wireless connection
    # that connects to any available access point:
    #
    iface wlan0 inet dhcp
        wireless_mode managed
        wireless_essid any

    iface tiwlan0 inet dhcp
        wireless_mode managed
        wireless_essid any
    #
    #
    # Same as above but locked to a specific access point:
    #
    #iface wlan0 inet dhcp 
    #    wireless_mode managed
    #    wireless-essid some-essid
    #
    # A WEP encrypted connection locked to a specific access point:
    #
    #iface wlan0 inet dhcp 
    #    wireless-essid some-essid
    #    wireless-key s:My-PlainText-Password
    #    wireless-mode managed                 
    #
    # A WPA1 or WPA2 encrypted connection locked to a specific access point.
    # This is the best option for non-roaming, single-network usage.
    # Note that your card may require a firmware update to use WPA.
    # Some distributions install a temporary volatile firmware update on ifup.
    #
    #iface wlan0 inet dhcp                                                  
    #    wpa-essid some-essid                                         
    #    wpa-psk My-PlainText-Password                                             
    #
    # A WPA1 or WPA2 encrypted connection using an external configuration file
    # for wpa-supplicant. This is the way to go if you need to configure multiple
    # networks with different keys and / or WPA settings and roaming support.
    #
    # iface wlan0 inet dhcp
    #    wpa-conf /etc/wpa_supplicant.conf
    #    wpa-driver hostap



    iface atml0 inet dhcp

    # Wired or wireless interfaces
    auto eth0
    iface eth0 inet dhcp
            pre-up /bin/grep -v -e "ip=[0-9]\+\.[0-9]\+\.[0-9]\+\.[0-9]\+" /proc/cmdline > /dev/null

    iface eth1 inet dhcp

    # Ethernet/RNDIS gadget (g_ether)
    # ... or on host side, usbnet and random hwaddr
    iface usb0 inet dhcp

    # Zaurus 2.4 Lineo net_fd; obsolete
    iface usbd0 inet static
        address 192.168.129.201
        netmask 255.255.255.0
        network 192.168.129.0
        gateway 192.168.129.200

    # iPAQ 2.4 mach-sa1100/usb-eth
    # (192.168.0.202 is the iPAQ's IP, 192.168.0.200 is the host's IP)
    iface usbf inet static
            address 192.168.0.202
            netmask 255.255.255.0
            network 192.168.0.0
            gateway 192.168.0.200

    # Bluetooth networking
    iface bnep0 inet dhcp

    ========================

    I still have no idea how to resolve this issue ~

    plz help ~

    thx ~

    HB

  • Dear Experts,

    I try uImage of DVR_RDK1.09,DVR_RDK2.0,DVR_RDK2.8, DVR_RDK3.0, and EZSDK_5_05_01_04,

    only DVRRDK1.09 and DVR_RDK2.0 uImage can get DHCP address druing booting process.

    (same bootargs)

    I need to use DVR_RDK3.0's uImage.

    Is there any version problem between uImage and hardware version ??

    The version of my 8148EVM is REV C ~

    thx ~

    HB

  • Hello,

    You are saying that you have verified the DHCP server from another PC, right?

    How do you connect the board? Can you try with crossover cable to a Host PC, if you have?

    BR

    Vladimir

  • Dear Vladimir,

    I connect EVM board to my office network, there is a DHCP Server in this network.

    I try these uImages to get DHCP IP address from office network, and ony DVRRDK1.09 and DVRRDK2.0 can get IP address.

    Do you suggest to build a DHCP server on my HOST PC, and directly connect to EVM board using crossover cable ??

    If this method works, how can I modify kernel to get DHCP IP address from office network (public network) ??

    HB

  • HB,

    No, I suggested this in order to exclude the possibility that something is wrong with the DHCP server.

    Earlier today I even tried it again. With no ip=... in the bootargs and no modifications in the default /etc/network/interfaces file, I simply boot up the DM814x EVM with EZSDK 5.05 (entering no commands in the Linux shell) and plug the cable, and I was given an IP. It is working.

    Double check what is on the SD card in the DM814x EVM. Are you flashing it with the mksd-ti814x.sh script?

    There could be a hardware issue. Check the connectors, does they fit well? Check the LED indication of the Ethernet port.

    BR

    Vladimir

  • Dear Vladimir,

    I flash SD card by mksd-ti814x.sh script, and LED indication of the Ethernet port is working.

    Yesterday, I build a DHCP Server on my Host PC. Connect EVM board to my HOST PC to get DHCP IP address.

    Both uImages of DVRRDK1.09 and DVRRDK3.0 can get DHCP IP address from my HOST PC.

    But If I connect EVM to my office network to get DHCP IP address, only DVRRDK1.09 can get.

    The MAC address is the same, thus I thought this is kernel issue.

    Is there any difference between these two pre-built uImages to get DHCP IP address ?

    Any kernel option or driver will cause this problem ?

    thx ~

    HB

  • HB,

    No problem, we will try to get to the bottom of this. You are talking about DVRRDK images, but you said that you are using EZSDK. In my previous post I was using this one

    <EZSDK_5.05_HOME>/board-support/prebuilt-images/uImage

    It was working. Can you try it out, please?

    I don't know; if you are using EZSDK distribution with DVRRDK kernel image, this definitely is not recommended.

    If you are using DVRRDK, I personally don't have it and I cannot reproduce anything. If really that pre-built image is corrupted somehow, you could try to build your own, checking the kernel configuration before that. You could try to run something like tcpdump to check what is actually happening. There could various differences between two pre-built images; we could hardly know.

    BR

    Vladimir

  • Dear Vladimir,

    Both pre-built uImage of EZSDK_5.05 or DVRRDK3.0 can't get DHCP IP address.

    Actually, I try the pre-built uImage of EZSDK_5.05, DVRRDK3.0, DVRRDK1.09, DVRRDK2.0, and DVRRDK2.8.

    Only DVRRDK1.09, DVRRDK2.0 can get DHCP IP address.

    Thus I merge 8148_evm_default_config file  from DVRRDK1.09 to DVRRDK3.0 to check whether it is kernel option problem,

    but finally the built uImage of DVRRDK3.0 still can't get DHCP IP address.

    I guess there might be some network function problem during version change.

    HB

  • Pls ensure you use the uboot associated with the release .For example if using DVR RDK 3.0 make sure you flash your board with uboot part of RDK 3.0 as well

  • Dear Badri Narayanan,

    But I can get DHCP IP address from my Host PC DHCP Server even I use other version uboot.

    However, in this discussion, I flash DVRRDK3.0 uImage and corresponding uboot into SD card (I built them at same time).

    HB

  • Dear Experts,

    I don't have the right to control my office network.

    Thus I use wireshark to log DHCP process of DVRRDK1.09 and EZSDK5.

    However, I can't figure out what's the difference between these two pcap files.

    Hope these two files could help someone to know what's the problem of this issue.

    Log files:

    https://dl.dropbox.com/u/27415803/dvrrdk109.pcap

    https://dl.dropbox.com/u/27415803/ezsdk5_boot_dhcp.pcap

    The DHCP process:  Connect EVM Board to my Host PC DHCP Server, set bootags ip=dhcp, boot the EVM kernel by using DVRRDK109/EZSDK5.0.

    When connect to my Host PC DHCP Server, these two uImages can both get DHCP IP address.

    But when connect to office network, only DVRRDK109 can get DHCP IP address.

    I flash the SD card by mksd-ti814x.sh script in EZSDK, the uboot and kernel are pre-built.

    HB

  • Hello HB,

    Is this one still open? Did you manage to solve that?

    Thank you.

    BR

    Vladimir

  • Dear Vladimir,

    yes, still open.

    I can't get the solution to resolve this problem ~

    I thought this should be kernel problem, I am waiting your response if possible ~

    thx ~

    HB

  • Hello HB,

    We have compared these two logs and we think in both cases the procedure of obtaining IP through DHCP is normal.

    You can filter the essential part and check the similarities with something like this:

    (udp.port == 68 || udp.port == 69)&&(eth.src==40:5f:c2:23:06:dd || eth.dst == 40:5f:c2:23:06:dd || eth.dst == ff:ff:ff:ff:ff:ff)

    In other words these logs doesn't tell us what could be the cause of the issue.

    You say :

    "But when connect to office network, only DVRRDK109 can get DHCP IP address".

    How exactly the EZSDK image doesn't work? You boot up the boards to the Linux shell and ifconfig show that there is no IP in place?

    Also what happens when you try to obtain the dhcp from the u-boot prompt like this:

    TI8148_EVM# setenv serverip <server in your network>

    TI8148_EVM# saveenv

    TI8148_EVM# dhcp

    ?

    BR

    Vladimir

  • Dear Vladimir,

    I used the pre-built-image in EZSDK \ti-ezsdk_dm814x-evm_5_05_01_04\board-support\prebuilt-images.

    make sd card by : sudo ./mksd-ti814x.sh /dev/sdd MLO u-boot.bin uImage-2.6.37 ezsdk-dm814x-evm-rootfs.tar.gz

    In uboot prompt, I can get dhcp.

    TI8148_EVM#dhcp
    link up on port 0, speed 100, full duplex
    BOOTP broadcast 1
    DHCP client bound to address 172.17.14.85
    Using cpsw device
    TFTP from server 0.0.0.0; our IP address is 172.17.14.85; sending through gateway 172.17.15.254

    But when get into kernel booting process, I can't get dhcp address

    ....
    CPSW phy found : id is : 0x4dd074

    CPSW phy found : id is : 0x4dd074
    Sending DHCP requests .
    PHY: 0:01 - Link is Up - 0/Half
    PHY: 0:01 - Link is Down
    PHY: 0:00 - Link is Up - 100/Full
    ..... timed out!
    IP-Config: Reopening network devices...
    .....

    
    U-Boot 2010.06 (Oct 10 2012 - 14:09:17)
    
    TI8148-GP rev 2.1
    
    ARM clk: 600MHz
    DDR clk: 400MHz
    
    DRAM:  2 GiB
    MMC:   OMAP SD/MMC: 0
    Using default environment
    
    The 2nd stage U-Boot will now be auto-loaded
    Please do not interrupt the countdown till TI8148_EVM prompt if 2nd stage is already flashed
    Hit any key to stop autoboot:  0 
    reading u-boot.bin
    
    210400 bytes read
    ## Starting application at 0x80800000 ...
    
    
    U-Boot 2010.06 (Oct 10 2012 - 14:05:13)
    
    TI8148-GP rev 2.1
    
    ARM clk: 600MHz
    DDR clk: 400MHz
    
    I2C:   ready
    DRAM:  2 GiB
    NAND:  HW ECC BCH8 Selected
    NAND device: Manufacturer ID: 0x2c, Chip ID: 0xca (Micron NAND 256MiB 3,3V 16-bit)
    NAND bus width 8 instead 16 bit
    No NAND device found!!!
    0 MiB
    MMC:   OMAP SD/MMC: 0
    *** Warning - bad CRC or NAND, using default environment
    
                              .:;rrr;;.                   
                        ,5#@@@@#####@@@@@@#2,             
                     ,A@@@hi;;;r5;;;;r;rrSG@@@A,          
                   r@@#i;:;s222hG;rrsrrrrrr;ri#@@r        
                 :@@hr:r;SG3ssrr2r;rrsrsrsrsrr;rh@@:      
                B@H;;rr;3Hs;rrr;sr;;rrsrsrsrsrsr;;H@B     
               @@s:rrs;5#;;rrrr;r#@H:;;rrsrsrsrsrr:s@@    
              @@;;srs&X#9;r;r;;,2@@@rrr:;;rrsrsrsrr;;@@   
             @@;;rrsrrs@MB#@@@@@###@@@@@@#rsrsrsrsrr;;@@  
            G@r;rrsrsr;#X;SX25Ss#@@#M@#9H9rrsrsrsrsrs;r@G 
            @9:srsrsrs;2@;:;;:.X@@@@@H::;rrsrsrsrsrsrr:3@ 
           X@;rrsrsrsrr;XAi;;:&@@#@Bs:rrsrsrsrsrsrsrsrr;@X
           @#;rsrsrsrsrr;r2ir@@@###::rrsrsrsrsrsrsrsrsr:@@
           @A:rrsrsrsrr;:2@29@@M@@@;:;rrrrsrsrsrsrsrsrs;H@
           @&;rsrsrsrr;A@@@@@@###@@@s::;:;;rrsrsrsrsrsr;G@
           @#:rrsrsrsr;G@5Hr25@@@#@@@#9XG9s:rrrrsrsrsrs:#@
           M@;rsrsrsrs;r@&#;::S@@@@@@@M@@@@Grr:;rsrsrsr;@#
           :@s;rsrsrsrr:M#Msrr;;&#@@@@@@@@@@H@@5;rsrsr;s@,
            @@:rrsrsrsr;S@rrrsr;:;r3MH@@#@M5,S@@irrsrr:@@ 
             @A:rrsrsrsrrrrrsrsrrr;::;@##@r:;rH@h;srr:H@  
             ;@9:rrsrsrsrrrsrsrsrsr;,S@Hi@i:;s;MX;rr:h@;  
              r@B:rrrrsrsrsrsrsrr;;sA@#i,i@h;r;S5;r:H@r   
               ,@@r;rrrsrsrsrsrr;2BM3r:;r:G@:rrr;;r@@,    
                 B@Mr;rrrrsrsrsr@@S;;;rrr:5M;rr;rM@H      
                  .@@@i;;rrrrsrs2i;rrrrr;r@M:;i@@@.       
                    .A@@#5r;;;r;;;rrr;r:r#AsM@@H.         
                       ;&@@@@MhXS5i5SX9B@@@@G;            
                           :ihM#@@@@@##hs,                
    
    Net:   <ethaddr> not set. Reading from E-fuse
    Detected MACID:40:5f:c2:23:6:dd
    cpsw
    Hit any key to stop autoboot:  3  2  0 
    TI8148_EVM#dhcp
    
    link up on port 0, speed 100, full duplex
    BOOTP broadcast 1
    DHCP client bound to address 172.17.14.85
    Using cpsw device
    TFTP from server 0.0.0.0; our IP address is 172.17.14.85; sending through gateway 172.17.15.254
    Filename 'uImage'.
    Load address: 0x81000000
    Loading: *T T 
    Abort
    TI8148_EVM#mmcinfo 0
    
    Device: OMAP SD/MMC
    Manufacturer ID: 27
    OEM: 5048
    Name: SD02G 
    Tran Speed: 25000000
    Rd Block Len: 512
    SD version 2.0
    High Capacity: No
    Capacity: 2002780160
    Bus Width: 4-bit
    TI8148_EVM#fatls mmc 0
    
        68864   mlo 
       210400   u-boot.bin 
      2796420   uimage 
    
    3 file(s), 0 dir(s)
    
    TI8148_EVM#setenv bootargs 'console=ttyO0,115200n8 rootwait root=/dev/mmcblk0p2 rw mem=256M earlyprintk notifyk.vpssm3_sva=0xBF900000 vram=50M ti814xfb.vram=0:16M,1:16M,2:6M ip=dhcp noinitrd'
    
    TI8148_EVM#fatload mmc 0 0x80009000 uImage
    
    reading uImage
    
    2796420 bytes read
    TI8148_EVM#bootm 0x80009000
    
    ## Booting kernel from Legacy Image at 80009000 ...
       Image Name:   Arago/2.6.37-psp04.04.00.01/dm81
       Image Type:   ARM Linux Kernel Image (uncompressed)
       Data Size:    2796356 Bytes = 2.7 MiB
       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.37 (x0029463@swubn01) (gcc version 4.3.3 (Sourcery G++ Lite 2009q1-203) ) #1 Wed Oct 10 14:02:40 IST 2012
    
    CPU: ARMv7 Processor [413fc082] revision 2 (ARMv7), cr=10c53c7f
    
    CPU: VIPT nonaliasing data cache, VIPT aliasing instruction cache
    
    Machine: ti8148evm
    
    bootconsole [earlycon0] enabled
    
    vram size = 52428800 at 0x0
    
    reserved size = 52428800 at 0x0
    
    FB: Reserving 52428800 bytes SDRAM for VRAM
    
    Memory policy: ECC disabled, Data cache writeback
    
    OMAP chip is TI8148 2.1
    
    SRAM: Mapped pa 0x402f1000 to va 0xfe400000 size: 0xf000
    
    Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 52224
    
    Kernel command line: console=ttyO0,115200n8 rootwait root=/dev/mmcblk0p2 rw mem=256M earlyprintk notifyk.vpssm3_sva=0xBF900000 vram=50M ti814xfb.vram=0:16M,1:16M,2:6M ip=dhcp noinitrd
    
    PID hash table entries: 1024 (order: 0, 4096 bytes)
    
    Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
    
    Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
    
    Memory: 206MB = 206MB total
    
    Memory: 202680k/202680k available, 59464k reserved, 0K highmem
    
    Virtual kernel memory layout:
    
        vector  : 0xffff0000 - 0xffff1000   (   4 kB)
    
        fixmap  : 0xfff00000 - 0xfffe0000   ( 896 kB)
    
        DMA     : 0xffc00000 - 0xffe00000   (   2 MB)
    
        vmalloc : 0xd0800000 - 0xf8000000   ( 632 MB)
    
        lowmem  : 0xc0000000 - 0xd0000000   ( 256 MB)
    
        pkmap   : 0xbfe00000 - 0xc0000000   (   2 MB)
    
        modules : 0xbf000000 - 0xbfe00000   (  14 MB)
    
          .init : 0xc0008000 - 0xc003d000   ( 212 kB)
    
          .text : 0xc003d000 - 0xc0549000   (5168 kB)
    
          .data : 0xc054a000 - 0xc05970c0   ( 309 kB)
    
    SLUB: Genslabs=11, HWalign=64, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
    
    NR_IRQS:407
    
    IRQ: Found an INTC at 0xfa200000 (revision 5.0) with 128 interrupts
    
    Total of 128 interrupts on 1 active controller
    
    GPMC revision 6.0
    
    Trying to install interrupt handler for IRQ400
    
    Trying to install interrupt handler for IRQ401
    
    Trying to install interrupt handler for IRQ402
    
    Trying to install interrupt handler for IRQ403
    
    Trying to install interrupt handler for IRQ404
    
    Trying to install interrupt handler for IRQ405
    
    Trying to install interrupt handler for IRQ406
    
    Trying to install type control for IRQ407
    
    Trying to set irq flags for IRQ407
    
    OMAP clockevent source: GPTIMER1 at 20000000 Hz
    
    Console: colour dummy device 80x30
    
    Calibrating delay loop... 598.01 BogoMIPS (lpj=2990080)
    
    pid_max: default: 32768 minimum: 301
    
    Security Framework initialized
    
    Mount-cache hash table entries: 512
    
    CPU: Testing write buffer coherency: ok
    
    devtmpfs: initialized
    
    omap_voltage_early_init: voltage driver support not added
    
    regulator: core version 0.5
    
    regulator: dummy: 
    
    NET: Registered protocol family 16
    
    omap_voltage_domain_lookup: Voltage driver init not yet happened.Faulting!
    
    omap_voltage_add_dev: VDD specified does not exist!
    
    OMAP GPIO hardware version 0.1
    
    OMAP GPIO hardware version 0.1
    
    OMAP GPIO hardware version 0.1
    
    OMAP GPIO hardware version 0.1
    
    omap_mux_init: Add partition: #1: core, flags: 4
    
    NOR: Can't request GPMC CS
    
    Debugfs: Only enabling/disabling deep sleep and wakeup timer is supported now
    
    registered ti81xx_vpss device
    
    registered ti81xx_vidout device
    
    registered ti81xx on-chip HDMI device
    
    registered ti81xx_fb device
    
    registered ti81xx_vin device
    
    ti81xx_pcie: Invoking PCI BIOS...
    
    ti81xx_pcie: Setting up Host Controller...
    
    ti81xx_pcie: Register base mapped @0xd0820000
    
    ti81xx_pcie: Starting PCI scan...
    
    PCI: bus0: Fast back to back transfers enabled
    
    bio: create slab <bio-0> at 0
    
    vgaarb: loaded
    
    SCSI subsystem initialized
    
    usbcore: registered new interface driver usbfs
    
    usbcore: registered new interface driver hub
    
    usbcore: registered new device driver usb
    
    USBSS revision 4ea2080b
    
    registerd cppi-dma Intr @ IRQ 17
    
    Cppi41 Init Done
    
    omap_i2c omap_i2c.1: bus 1 rev4.0 at 100 kHz
    
    pcf857x 1-0021: gpios 128..143 on a pcf8575
    
    regulator: VRTC: 1800 mV 
    
    regulator: VIO: 1500 mV 
    
    regulator: VDD1: 600 <--> 1500 mV at 1200 mV 
    
    regulator: VDD2: 600 <--> 1500 mV at 1200 mV 
    
    regulator: VDDCTRL: 600 <--> 1400 mV at 1200 mV 
    
    regulator: LDO1: 1100 <--> 3300 mV at 1800 mV 
    
    regulator: LDO2: 1100 <--> 3300 mV at 1800 mV 
    
    regulator: LDO3: 1100 <--> 3300 mV at 3300 mV 
    
    regulator: LDO4: 1100 <--> 3300 mV at 1800 mV 
    
    regulator: LDO5: 1100 <--> 3300 mV at 3300 mV 
    
    regulator: LDO6: 1100 <--> 3300 mV at 3300 mV 
    
    regulator: LDO7: 1100 <--> 3300 mV at 3300 mV 
    
    regulator: LDO8: 1100 <--> 3300 mV at 1800 mV 
    
    tps65910 1-002d: No interrupt support, no core IRQ
    
    omap_i2c omap_i2c.3: bus 3 rev4.0 at 100 kHz
    
    Advanced Linux Sound Architecture Driver Version 1.0.23.
    
    Switching to clocksource gp timer
    
    musb-hdrc: version 6.0, host, debug=0
    
    musb-hdrc musb-hdrc.0: dma type: dma-cppi41
    
    MUSB controller-0 revision 4ea20800
    
    musb-hdrc musb-hdrc.0: MUSB HDRC host driver
    
    musb-hdrc musb-hdrc.0: new USB bus registered, assigned bus number 1
    
    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: MUSB HDRC host driver
    
    usb usb1: Manufacturer: Linux 2.6.37 musb-hcd
    
    usb usb1: SerialNumber: musb-hdrc.0
    
    hub 1-0:1.0: USB hub found
    
    hub 1-0:1.0: 1 port detected
    
    musb-hdrc musb-hdrc.0: USB Host mode controller at d081e000 using DMA, IRQ 18
    
    musb-hdrc musb-hdrc.1: dma type: dma-cppi41
    
    MUSB controller-1 revision 4ea20800
    
    musb-hdrc musb-hdrc.1: MUSB HDRC host driver
    
    musb-hdrc musb-hdrc.1: 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.37 musb-hcd
    
    usb usb2: SerialNumber: musb-hdrc.1
    
    hub 2-0:1.0: USB hub found
    
    hub 2-0:1.0: 1 port detected
    
    musb-hdrc musb-hdrc.1: USB Host mode controller at d0826800 using DMA, IRQ 19
    
    NET: Registered protocol family 2
    
    IP route cache hash table entries: 2048 (order: 1, 8192 bytes)
    
    TCP established hash table entries: 8192 (order: 4, 65536 bytes)
    
    TCP bind hash table entries: 8192 (order: 3, 32768 bytes)
    
    TCP: Hash tables configured (established 8192 bind 8192)
    
    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.
    
    NetWinder Floating Point Emulator V0.97 (double precision)
    
    PMU: registered new PMU device of type 0
    
    omap-iommu omap-iommu.0: ducati registered
    
    omap-iommu omap-iommu.1: sys registered
    
    JFFS2 version 2.2. (NAND) © 2001-2006 Red Hat, Inc.
    
    msgmni has been set to 395
    
    io scheduler noop registered
    
    io scheduler deadline registered
    
    io scheduler cfq registered (default)
    
    Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
    
    omap_uart.0: ttyO0 at MMIO 0x48020000 (irq = 72) is a OMAP UART0
    
    console [ttyO0] enabled, bootconsole disabled
    console [ttyO0] enabled, bootconsole disabled
    
    omap_uart.1: ttyO1 at MMIO 0x48022000 (irq = 73) is a OMAP UART1
    omap_uart.2: ttyO2 at MMIO 0x48024000 (irq = 74) is a OMAP UART2
    omap_uart.3: ttyO3 at MMIO 0x481a6000 (irq = 44) is a OMAP UART3
    omap_uart.4: ttyO4 at MMIO 0x481a8000 (irq = 45) is a OMAP UART4
    omap_uart.5: ttyO5 at MMIO 0x481aa000 (irq = 46) is a OMAP UART5
    brd: module loaded
    loop: module loaded
    ahci ahci.0: forcing PORTS_IMPL to 0x1
    ahci ahci.0: AHCI 0001.0300 32 slots 1 ports 3 Gbps 0x1 impl platform mode
    ahci ahci.0: flags: ncq sntf pm led clo only pmp pio slum part ccc apst 
    scsi0 : ahci_platform
    ata1: SATA max UDMA/133 mmio [mem 0x4a140000-0x4a150fff] port 0x100 irq 16
    omap2-nand driver initializing
    ONFI flash detected
    ONFI param page 0 valid
    NAND device: Manufacturer ID: 0x2c, Chip ID: 0xca (Micron NAND 256MiB 3,3V 16-bit)
    Creating 6 MTD partitions on "omap2-nand.0":
    0x000000000000-0x000000020000 : "U-Boot-min"
    0x000000020000-0x000000260000 : "U-Boot"
    0x000000260000-0x000000280000 : "U-Boot Env"
    0x000000280000-0x0000006c0000 : "Kernel"
    0x0000006c0000-0x00000cee0000 : "File System"
    0x00000cee0000-0x000010000000 : "Reserved"
    davinci_mdio davinci_mdio.0: davinci mdio revision 1.6
    davinci_mdio davinci_mdio.0: detected phy mask fffffffc
    davinci_mdio.0: probed
    davinci_mdio davinci_mdio.0: phy[0]: device 0:00, driver unknown
    davinci_mdio davinci_mdio.0: phy[1]: device 0:01, driver unknown
    CAN device driver interface
    CAN bus driver for Bosch D_CAN controller 1.0
    d_can d_can: d_can device registered (irq=52, irq_obj=53)
    usbcore: registered new interface driver cdc_ether
    usbcore: registered new interface driver dm9601
    usbcore: registered new interface driver cdc_acm
    cdc_acm: v0.26:USB Abstract Control Model driver for USB modems and ISDN adapters
    Initializing USB Mass Storage driver...
    usbcore: registered new interface driver usb-storage
    USB Mass Storage support registered.
    mice: PS/2 mouse device common for all mice
    ata1: SATA link down (SStatus 0 SControl 300)
    qt602240_ts 1-004a: Family ID: 128 Variant ID: 1 Version: 22 Build: 171
    qt602240_ts 1-004a: Matrix X Size: 18 Matrix Y Size: 12 Object Num: 17
    input: AT42QT602240/ATMXT224 Touchscreen as /devices/platform/omap/omap_i2c.1/i2c-1/1-004a/input/input0
    omap_rtc omap_rtc: rtc core: registered omap_rtc as rtc0
    i2c /dev entries driver
    Linux video capture interface: v2.00
    usbcore: registered new interface driver uvcvideo
    USB Video Class driver (v1.0.0)
    OMAP Watchdog Timer Rev 0x00: initial timeout 60 sec
    usbcore: registered new interface driver usbhid
    usbhid: USB HID core driver
    notify_init : notify drivercreated  for  remote proc id 2 at physical Address 0xbf900000
    usbcore: registered new interface driver snd-usb-audio
    asoc: tlv320aic3x-hifi <-> davinci-mcasp.2 mapping ok
    ALSA device list:
      #0: TI81XX EVM
    nf_conntrack version 0.5.0 (3166 buckets, 12664 max)
    ip_tables: (C) 2000-2006 Netfilter Core Team
    TCP cubic registered
    NET: Registered protocol family 17
    can: controller area network core (rev 20090105 abi 8)
    NET: Registered protocol family 29
    can: raw protocol (rev 20090105)
    can: broadcast manager protocol (rev 20090105 t)
    Registering the dns_resolver key type
    VFP support v0.3: implementor 41 architecture 3 part 30 variant c rev 3
    omap_voltage_late_init: Voltage driver support not added
    Power Management for TI81XX.
    Detected MACID=40:5f:c2:23:6:dd
    omap_rtc omap_rtc: setting system clock to 2000-01-01 00:00:00 UTC (946684800)
    mmc0: new high speed SD card at address 0007
    mmcblk0: mmc0:0007 SD02G 1.86 GiB 
     mmcblk0: p1 p2
    
    CPSW phy found : id is : 0x4dd074
    
    CPSW phy found : id is : 0x4dd074
    Sending DHCP requests .
    PHY: 0:01 - Link is Up - 0/Half
    PHY: 0:01 - Link is Down
    PHY: 0:00 - Link is Up - 100/Full
    ..... timed out!
    IP-Config: Reopening network devices...
    
    CPSW phy found : id is : 0x4dd074
    
    CPSW phy found : id is : 0x4dd074
    Sending DHCP requests .
    PHY: 0:00 - Link is Up - 100/Full
    ..... timed out!
    IP-Config: Auto-configuration of network failed.
    EXT3-fs: barriers not enabled
    kjournald starting.  Commit interval 5 seconds
    EXT3-fs (mmcblk0p2): using internal journal
    EXT3-fs (mmcblk0p2): mounted filesystem with writeback data mode
    VFS: Mounted root (ext3 filesystem) on device 179:2.
    devtmpfs: mounted
    Freeing init memory: 212K
    
    INIT: version 2.86 booting
    
    Error opening /dev/fb0: No such file or directory
    Please wait: booting...
    Starting udev
    WARNING: -e needs -E or -F
    udevd (86): /proc/86/oom_adj is deprecated, please use /proc/86/oom_score_adj instead.
    Remounting root file system...
    Caching udev devnodes
    Undefined users:
    Skipping /etc/default/volatiles/99_hal
    ALSA: Restoring mixer settings...
    No state is present for card EVM
    Found hardware: "" "" "" "" ""
    Hardware is initialized using a generic method
    No state is present for card EVM
    Configuring update-modules.
    Configuring omap3-sgx-modules.
    Configuring hicolor-icon-theme.
    # GdkPixbuf Image Loader Modules file
    # Automatically generated file, do not edit
    # Created by gdk-pixbuf-query-loaders from gtk+-2.20.1
    #
    g_module_open() failed for /--update-cache: /--update-cache.so: cannot open shared object file: No such file or directory
    Configuring pango-module-basic-x.
    Configuring pango-module-basic-fc.
    Configuring ttf-dejavu-common.
    Configuring ttf-dejavu-sans.
    Configuring gdk-pixbuf-loader-png.
    Configuring gdk-pixbuf-loader-jpeg.
    Configuring gdk-pixbuf-loader-gif.
    Configuring gdk-pixbuf-loader-xpm.
    Configuring dbus.
     Adding system startup for /etc/init.d/dbus-1.
    Configuring hal.
    Configuring policykit.
    Configuring gnome-keyring.
    Configuring ti-cmem-module.
    Configuring ti-syslink-module.
    Configuring kernel-module-tunnel4.
    Configuring kernel-module-sit.
    Configuring kernel-module-xfrm6-mode-beet.
    Configuring kernel-module-xfrm6-mode-tunnel.
    Configuring kernel-module-xfrm6-mode-transport.
    Configuring kernel-module-scsi-wait-scan.
    Configuring kernel-module-ssb.
    Configuring kernel-module-vpss.
    Configuring kernel-module-ti81xxhdmi.
    Configuring kernel-module-tlc59108.
    Configuring kernel-module-ti81xxfb.
    Configuring kernel-module-tvp7002.
    Configuring kernel-module-ti81xxvo.
    Configuring kernel-module-ti81xxvin.
    Configuring wpa-supplicant.
    Configuring kernel-image-2.6.37.
    Configuring ti-compat-wireless-wl12xx.
    NET: Registered protocol family 10
    Configuring network interfaces... 
    CPSW phy found : id is : 0x4dd074
    
    CPSW phy found : id is : 0x4dd074
    ADDRCONF(NETDEV_UP): eth0: link is not ready
    eth0      no wireless extensions.
    
    udhcpc (v1.13.2) started
    Sending discover...
    PHY: 0:00 - Link is Up - 100/Full
    ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
    Sending discover...
    Sending discover...
    No lease, forking to background
    done.
    Setting up IP spoofing protection: rp_filter.
    Wed Oct 10 15:52:00 UTC 2012
    
    INIT: Entering runlevel: 5
    
    Loading HDVICP2 Firmware
    DM814X prcm_config_app version: 2.0.0.1
    Doing PRCM settings...
    	PRCM for IVHD0 is in Progress, Please wait.....  
    			BW Phy Addr : 0x48180600 Data : 0x00000001
    			AW Phy Addr : 0x48180600 Data : 0x00000002
    			Phy Addr : 0x48180c04 Data : 0x00000037
    			BW Phy Addr : 0x48180620 Data : 0x00070000
    			AW Phy Addr : 0x48180620 Data : 0x00050002
    			BW Phy Addr : 0x48180624 Data : 0x00030000
    			AW Phy Addr : 0x48180624 Data : 0x00010002
    			Phy Addr : 0x48180600 Data : 0x00000102
    			BW Phy Addr : 0x48180c10 Data : 0x00000007
    			AW Phy Addr : 0x48180c10 Data : 0x00000003
    			Phy Addr : 0x48180c14 Data : 0x00000004
    			BW Phy Addr : 0x58088000 Data : 0x06c54220
    			AW Phy Addr : 0x58088000 Data : 0xeafffffe
    			BW Phy Addr : 0x58098000 Data : 0x351d44af
    			AW Phy Addr : 0x58098000 Data : 0xeafffffe
    			BW Phy Addr : 0x48180c10 Data : 0x00000003
    			AW Phy Addr : 0x48180c10 Data : 0x00000000
    			Phy Addr : 0x48180c14 Data : 0x00000007
    	PRCM for IVHD0 is Done Successfully  
    PRCM Initialization completed 
    SysLink version : 2.20.00.14
    SysLink module created on Date:Oct 10 2012 Time:14:49:49
    FIRMWARE: I2cInit will be done by M3
    FIRMWARE: Memory map bin file not passed
    Usage : firmware_loader <Processor Id> <Location of Firmware> <start|stop> [-mmap <memory_map_file>] [-i2c <0|1>]
    ===Mandatory arguments=== 
    <Processor Id>         0: DSP, 1: Video-M3, 2: Vpss-M3 
    <Location of Firmware> firmware binary file 
    <start|stop>           to start/stop the firmware 
    ===Optional arguments=== 
    -mmap                  input memory map bin file name 
    -i2c                   0: i2c init not done by M3, 1(default): i2c init done by M3 
    FIRMWARE: isI2cInitRequiredOnM3: 1
    FIRMWARE: Default memory configuration is used
    Firmware Loader debugging not configured
    Default FL_DEBUG: warning
    Allowed FL_DEBUG levels: error, warning, info, debug, log
    MemCfg: DCMM (Dynamically Configurable Memory Map) Version :  2.1.2.1
    FIRMWARE: 1 start Successful
    Loading HDVPSS Firmware
    FIRMWARE: I2cInit will be done by M3
    FIRMWARE: Memory map bin file not passed
    Usage : firmware_loader <Processor Id> <Location of Firmware> <start|stop> [-mmap <memory_map_file>] [-i2c <0|1>]
    ===Mandatory arguments=== 
    <Processor Id>         0: DSP, 1: Video-M3, 2: Vpss-M3 
    <Location of Firmware> firmware binary file 
    <start|stop>           to start/stop the firmware 
    ===Optional arguments=== 
    -mmap                  input memory map bin file name 
    -i2c                   0: i2c init not done by M3, 1(default): i2c init done by M3 
    FIRMWARE: isI2cInitRequiredOnM3: 1
    FIRMWARE: Default memory configuration is used
    Firmware Loader debugging not configured
    Default FL_DEBUG: warning
    Allowed FL_DEBUG levels: error, warning, info, debug, log
    MemCfg: DCMM (Dynamically Configurable Memory Map) Version :  2.1.2.1
    FIRMWARE: 2 start Successful
    Configuring fb0 to LCD
    HDMI W1 rev 4.0
    HDMI CEC Spec version 1.2
    I2C No Ack
    
    
    Starting system message bus: dbus.
    Creating Dropbear SSH server RSA host key.
    Will output 1024 bit rsa secret key to '/etc/dropbear/dropbear_rsa_host_key'
    Generating key, this may take a while...
    Public key portion is:
    ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAAAgwC6XJUeQ9im2TQT/bu2jFOCOGfoT6AyvCcM247I8EVtzH8kY7e2Bu7dmRX0034RwFZhso5GxP0FwYP85y8HS8qeN1/6iYFnU8YnJcLoJj0tImdL8TDoSGPMjcITOc1NHD2NQiOtn0viSuJRnses56NulZ4PiF0c4+JRqfk5CA2isQ99 root@dm814x-evm
    Fingerprint: md5 3b:a0:19:c7:0d:15:70:e1:c2:e7:7f:04:bc:ee:8f:45
    Starting Dropbear SSH server: dropbear.
    Starting telnet daemon.
    Starting network benchmark server: netserver.
    Starting syslogd/klogd: done
    Starting thttpd.
    Starting PVR
    /dev/mem opened.
    Memory mapped at address 0x4023e000.
    Read at address  0x48180F04 (0x4023ef04): 0x00000001
    Write at address 0x48180F04 (0x4023ef04): 0x00000000, readback 0x00000000
    /dev/mem opened.
    Memory mapped at address 0x402db000.
    Read at address  0x48180900 (0x402db900): 0x00000102
    Write at address 0x48180900 (0x402db900): 0x00000002, readback 0x00000002
    /dev/mem opened.
    Memory mapped at address 0x40279000.
    Read at address  0x48180920 (0x40279920): 0x00040002
    Write at address 0x48180920 (0x40279920): 0x00000002, readback 0x00000002
    Starting SGX fixup for ES6.x
    Calibrating touchscreen (first time only)xres = 800, yres = 480
    Took 13 samples...
    Top left : X =   53 Y =   47
    Took 7 samples...
    Top right : X =   40 Y =   39
    Took 17 samples...
    Bot right : X =  773 Y =  407
    Took 11 samples...
    Bot left : X =   53 Y =  401
    Took 3 samples...
    Center : X =  418 Y =  226
    369.884399 0.878846 -0.914677
    4.646423 -0.009437 1.061951
    Calibration constants: 24240744 57596 -59944 304508 -618 69596 65536 
    .
    Starting Matrix GUI application.
    
     _____                    _____           _         _   
    |  _  |___ ___ ___ ___   |  _  |___ ___  |_|___ ___| |_ 
    |     |  _| .'| . | . |  |   __|  _| . | | | -_|  _|  _|
    |__|__|_| |__,|_  |___|  |__|  |_| |___|_| |___|___|_|  
                  |___|                    |___|            
    
    Arago Project http://arago-project.org dm814x-evm ttyO0
    
    Arago 2011.09 dm814x-evm ttyO0
    
    dm814x-evm login: root
    root@dm814x-evm:~# ifconfig
    eth0      Link encap:Ethernet  HWaddr 40:5F:C2:23:06:DD  
              inet6 addr: fe80::425f:c2ff:fe23:6dd/64 Scope:Link
              UP BROADCAST RUNNING ALLMULTI MULTICAST  MTU:1500  Metric:1
              RX packets:980 errors:0 dropped:635 overruns:0 frame:0
              TX packets:21 errors:0 dropped:0 overruns:0 carrier:0
              collisions:0 txqueuelen:1000 
              RX bytes:109237 (106.6 KiB)  TX bytes:9318 (9.0 KiB)
              Interrupt:40 
    
    lo        Link encap:Local Loopback  
              inet addr:127.0.0.1  Mask:255.0.0.0
              inet6 addr: ::1/128 Scope:Host
              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)
    
    root@dm814x-evm:~# udhcpc
    udhcpc (v1.13.2) started
    Sending discover...
    Sending discover...
    Sending discover...
    Sending discover...
    Sending discover...
    Sending discover...
    
    root@dm814x-evm:~# 

    Plz help ~ thx ~

    HB

  • Hi HB,

    I recently tried a router with dhcp and with EZSDK 5_05_01 and I have obtained IP normally.

    So I cannot tell what could be the problem on your side. It could be something strange particularly with your router.

    You could try to speak with your system administrator to try to connect your board to the Internet through your Host PC.

    Sorry that you had to face this issue.

    BR

    Vladimir

  • Dear Vladimir,

    thx a lot ~

    I will try to discuss this problem with our system administrator ~

    HB