Network quit working on DM6467T EVM

Helmut Forren

Other Parts Discussed in Thread: ASH, PCF8574A, THS7303, THS8200, THS7353, TVP7002

Last week I got my network connectivity on my DM6467T EVM working. But this week, it no longer works.

Before, after logging into Arago Linux on the EVM as root, I could "ping 192.168.123.33" and hear back from my router. Now, I get the error message "Network is unreachable".

At this point, I should have out-of-the-box conditions for the most part on the EVM. Below is a terminal session. I don't recall having needed to do anything else before hand, but I must have forgotten something. Note that when I "ifconfig eth0 192.168.123.19 mask 255.255.255.0", I no longer get network unreachable, but then the ping still doesn't work. This ...19 ip address is the one my router was assigning to the board in the past.

Your advice on where to look or what to do is greatly appreciated.

-Helmut

ping 192.168.123.33

PING 192.168.123.33 (192.168.123.33): 56 data bytes

ping: sendto: Network is unreachable

root@dm6467t-evm:/# set

EDITOR='/bin/vi'

HISTFILE='/home/root/.ash_history'

HOME='/home/root'

IFS='

LOGNAME='root'

OLDPWD='/home/root'

OPTIND='1'

PATH='/usr/local/bin:/usr/bin:/bin:/usr/local/sbin:/usr/sbin:/sbin:'

PPID='1'

PS1='\u@\h:\w\$ '

PS2='> '

PS4='+ '

PWD='/'

SHELL='/bin/sh'

TERM='linux'

TSLIB_TSDEVICE='/dev/input/touchscreen0'

TZ='UTC'

USER='root'

_='192.168.123.33'

root@dm6467t-evm:/#

over 14 years ago

0 Michael T over 14 years ago

TI__Expert 6735 points

Helmut:

Are you certain that the router you are using is indeed a router and not an Ethernet switch and that it provides DHCP server capability?

If not, the IPADDR of the EVM can change when you bring up the system. That is all right, if you have your UBOOT configuration setup

to handle that.

What happens if you interrupt the boot process and type the dhcp command? Could you send the output from the UBOOT printenv command?

Regards,

Michael T

0 Helmut Forren over 14 years ago in reply to Michael T

Mastermind 6805 points

Michael,

Thanks for jumping in.

I believe the answer is that what I have is "both". Linksys WRT610N. It definitely provides DHCP.

Note that in the past, when interrupting U-Boot before Linux is loaded, I tried to follow instructions for flashing NAND. They all wanted to use the "dhcp" command of U-Boot. They didn't work. I found I had to manually set the ipaddr (and perhaps other things), then run tftpboot myself, rather than running dhcp. I got this working fine. I saved my env var settings. Even right now, U-Boot can successfully ping my router.

Remember, ...19 is the address that my router suggested. Whether or not I rely on the router directly or hard code this has changed through time.

Below is my terminal session running ping successfully:

Using DaVinci EMAC device

host 192.168.123.33 is alive

DM6467 EVM > ping 192.168.123.33

Using DaVinci EMAC device

host 192.168.123.33 is alive

DM6467 EVM >

Using DaVinci EMAC device

host 192.168.123.33 is alive

DM6467 EVM > printenv

bootcmd=nboot 0x80700000 0 0x160000; bootm

bootdelay=3

addclk=setenv bootargs ${bootargs} clkref=${clkref}

ethaddr=00:0e:99:02:b7:78

ethact=DaVinci EMAC

ipaddr=192.168.123.19

old_bootargs=mem=112M console=ttyS0,115200n8 root=/dev/hda1 rw ip=off vpif_display.ch2_numbuffers=0 vpif_display.ch3_numbuffers=0

new_bootargs=mem=76M console=ttyS0,115200n8 root=/dev/nfs nfsroot=$(nfshost):$(rootpath),nolock ip=192.168.123.19 vpif_display.ch2_numbuffers=0 vpif_display.ch3_numbuffers=0

nfshost=192.168.123.18

serverip=192.168.123.18

bootfile=uImage-dm6467t-evm.bin

baudrate=115200

gateway=192.168.123.33

newdhcp_bootargs=mem=76M console=ttyS0,115200n8 root=/dev/nfs nfsroot=$(nfshost):$(rootpath),nolock ip=dhcp vpif_display.ch2_numbuffers=0 vpif_display.ch3_numbuffers=0

hgf_bootargs=mem=76M console=ttyS0,115200n8 root=/dev/nfs nfsroot=192.168.123.18:/home/helmutforren/dvsdk/Shared_EVM_FS,nolock ip=dhcp vpif_display.ch2_numbuffers=0 vpif_display.ch3_numbuffers=0

rootpath=/home/helmutforren/dvsdk/Shared_EVM_FS

spec_bootargs=mem=76M console=ttyS0,115200n8 root=/dev/nfs nfsroot=$(nfshost):$(rootpath),nolock ip=192.168.123.19:192.168.123.18:192.168.123.33:255.255.255.0:dm6467:eth0: vpif_display.ch2_numbuffers=0 vpif_display.ch3_numbuffers=0

sss_bootargs=mem=76M console=ttyS0,115200n8 root=/dev/nfs nfsroot=192.168.123.18:/home/helmutforren/dvsdk/Shared_EVM_FS,nolock ip=192.168.123.19:192.168.123.18:192.168.123.33:255.255.255.0:Ubuntu:eth0:

bootargs=mem=112M console=ttyS0,115200n8 root=/dev/hda1 rw ip=off vpif_display.ch2_numbuffers=0 vpif_display.ch3_numbuffers=0

stdin=serial

stdout=serial

stderr=serial

ver=U-Boot 2009.08 (Jan 20 2010 - 15:27:59)

Environment size: 1653/16380 bytes

DM6467 EVM >

Below is the result of typing 'dhcp' with no arguments or other advance preparation.

DM6467 EVM >

DM6467 EVM > dhcp

BOOTP broadcast 1

DHCP client bound to address 192.168.123.19

Using DaVinci EMAC device

TFTP from server 192.168.123.33; our IP address is 192.168.123.19

Filename 'uImage-dm6467t-evm.bin'.

Load address: 0x80700000

Loading: *

TFTP error: 'File not found' (1)

Starting again

Abort

DM6467 EVM > I typed control-c to get "Abort"...

Please note that the whole dhcp thing has also prevented me from booting with NFS as my FS root. You can see some placeholder bootargs env vars further above. We could jump straight to this problem, which is what I really need in the end. Or we could continue along the line of figuring out why Arago Linux on the EVM can't find the network any more. Please note that I was booting Linux, and then attaching my NFS, simply not as root. At least then I could copy files back and forth between my Ubuntu/VMware/WindowsXP(machineB) and the EVM.

-Helmut

0 Michael T over 14 years ago in reply to Helmut Forren

TI__Expert 6735 points

Helmut:

1) First to change to use root file system via Network File Server:

setenv ipserver 192.168.123.18

setenv rootpath /home/helmutforren/dvsdk/Shared_EVM_FS

setenv hgf_bootargs 'setenv bootargs mem=76M console=ttyS0,115200n8 root=/dev/nfs nfsroot=${ipserver}:${rootpath},nolock ip=dhcp vpif_display.ch2_numbuffers=0 vpif_display.ch3_numbuffers=0'

setenv bootcmd dhcp\; run hgf_bootargs\; tftpboot; bootm

NOTES:

Need single quotes, "curly brackets" and "\;" as shown above.

2) Looks like system cannot get to the Linux kernal uImage file on Ubuntu host.

tftp server needs to be setup on Ubuntu host. We use Ubuntu 10.04 LTS, and it requires this:

1) Need a file at /etc/xinetd.d/tftp containing this:

service tftp
{
protocol = udp
port = 69
socket_type = dgram
wait = yes
user = nobody
server = /usr/sbin/in.tftpd
server_args = /tftpboot
disable = no
}

2) Edit file /etc/default/xinetd
Change this line from Yes to No:

INETD_COMPAT=No

3) Perform a stop/start on xinetd (should look like the following set of commands):

[prompt]:~$ sudo /etc/init.d/xinetd stop
* Stopping internet superserver xinetd [ OK ]

[prompt]:~$ sudo /etc/init.d/xinetd start
* Starting internet superserver xinetd [ OK ]

will need to enter your password when using the sudo command.

Which Ubuntu version are you using?

1) There are lots of teraterm scripts here that may help:

http://processors.wiki.ti.com/index.php/Teraterm_Scripts#Are_there_any_DM6467_examples.3F

2) This give directions on tftp server setup for older versions of Ubuntu.

http://processors.wiki.ti.com/index.php/Setting_Up_a_TFTP_Server#Using_atftp_in_Ubuntu_8.04_LTS

Best Regards,

Michael T

PS: Please mark this post as answered via the Verify Answer button below if you think it answers your question. Thanks!

0 Helmut Forren over 14 years ago in reply to Michael T

Mastermind 6805 points

Michael,

Thanks for the help. Please note that I've already got atftp running under Ubuntu, as well as nfs-kernel-server (I may have the wrong name here). In fact, tftpboot has been working and in the past so has the network file server, simply mounted after Arago Linux boots and as a file system OTHER than the root file system.

Nevertheless, I tried out your item (1) advice in your post. With my bootfile still set to a uImage... file on Ubuntu, your settings do indeed cause the EVM to download a new copy of that same image and then boot. So I did learn something new. However, such downloading from within U-Boot was not my problem.

My problem is that the NFS is not accessible for mounting as the root file system during boot BECAUSE the network is not accessible. So my problem is network access in general. Remember, not even "ping 192.168.123.33" to my router or "ping 192.168.123.18" to my Ubuntu/VMware/WindowsXP(MachineA) works. This means NFS is not part of the picture yet and things already fail.

Do please note that there has been some on-again off-again going on. Just now, the network WAS accessible from Arago Linux on the EVM. I did a "ping 192.168.123.33" and it worked. Seeing this, I immediately ran my little script to mount the NFS. This also worked and I can see the Ubuntu Shared_EVM_FS from the EVM when I type "ls -l /mnt". (It might not be mounted to the correct location/folder, but at least it works.)

So this PROVES that, for the moment at least, the NFS stuff is setup correctly on Ubuntu. Assuming this has been and remains the case, which presumably I have and I will verify from Ubuntu with the command "/etc/init.d/nfs-kernel-server status", then my problem lies on the EVM.

I just "shutdown -r 0" and now from Arago Linux the network is once again unreachable. I believe I got to the prior point through the same shutdown command, so everything should be the same on the evm, yet the network access is unreliable.

If I may, I would like to FORK THIS THREAD. I'd like to continue working on the Network Unreachable problem on this thread, and then work on the booting problem from a new thread at (I'll edit this parenthetical to add the link, reload this post on the web soon to see it, but now I'm thinking I must resolve unreachable on Arago problem first, so it may take a long time to fork this off). Remember, the weird thing is that U-Boot ping always works, but later ping from Arago Linux works sometimes, and again not at this time. This suggests to me that it's not a problem with my router, network, or anything other than the EVM running Arago Linux.

Now THIS REMINDS ME. When I do "ifconfig eth0 192.168.123.19 netmask 255.255.255.0" under Arago, the "Network is unreachable" error goes away and instead I just get timeouts no matter what I pinged. This suggests to me that the "Network is unreachable" error is a configuration problem. Arago is starting up, trying to configure the network, and only succeeding part of the time.

Below is a Tera Term Log from power up to failure. I interrupt in U-Boot to show ping works, then find ping doesn't work in Arago Linux, then try ifconfig that doesn't help.

Tera Term Log said:

Booting PSP Boot Loader

Starting NAND Copy

Booting Application @ 0x81080000

U-Boot 2009.08 (Jan 20 2010 - 15:27:59)

I2C: ready

DRAM: 256 MB

NAND: 128 MiB

In: serial

Out: serial

Err: serial

ARM Clock :- 495MHz

DDR Clock :- 396MHz

Net: Ethernet PHY: GENERIC @ 0x01

DaVinci EMAC

Hit any key to stop autoboot: 7 6 5 4 0

DM6467 EVM > printenv

addclk=setenv bootargs ${bootargs} clkref=${clkref}

ethaddr=00:0e:99:02:b7:78

ethact=DaVinci EMAC

ipaddr=192.168.123.19

old_bootargs=mem=112M console=ttyS0,115200n8 root=/dev/hda1 rw ip=off vpif_displ

ay.ch2_numbuffers=0 vpif_display.ch3_numbuffers=0

new_bootargs=mem=76M console=ttyS0,115200n8 root=/dev/nfs nfsroot=$(nfshost):$(r

ootpath),nolock ip=192.168.123.19 vpif_display.ch2_numbuffers=0 vpif_display.ch3

_numbuffers=0

nfshost=192.168.123.18

serverip=192.168.123.18

bootfile=uImage-dm6467t-evm.bin

baudrate=115200

gateway=192.168.123.33

newdhcp_bootargs=mem=76M console=ttyS0,115200n8 root=/dev/nfs nfsroot=$(nfshost)

:$(rootpath),nolock ip=dhcp vpif_display.ch2_numbuffers=0 vpif_display.ch3_numbu

ffers=0

hgf_bootargs=mem=76M console=ttyS0,115200n8 root=/dev/nfs nfsroot=192.168.123.18

:/home/helmutforren/dvsdk/Shared_EVM_FS,nolock ip=dhcp vpif_display.ch2_numbuffe

rs=0 vpif_display.ch3_numbuffers=0

spec_bootargs=mem=76M console=ttyS0,115200n8 root=/dev/nfs nfsroot=$(nfshost):$(

rootpath),nolock ip=192.168.123.19:192.168.123.18:192.168.123.33:255.255.255.0:d

m6467:eth0: vpif_display.ch2_numbuffers=0 vpif_display.ch3_numbuffers=0

sss_bootargs=mem=76M console=ttyS0,115200n8 root=/dev/nfs nfsroot=192.168.123.18

:/home/helmutforren/dvsdk/Shared_EVM_FS,nolock ip=192.168.123.19:192.168.123.18:

192.168.123.33:255.255.255.0:Ubuntu:eth0:

ipserver=192.168.123.18

rootpath=/home/helmutforren/dvsdk/Shared_EVM_FS

old_bootcmd=nboot 0x80700000 0 0x160000; bootm

mt_bootargs=mem=76M console=ttyS0,115200n8 root=/dev/nfs nfsroot=${ipserver}:${r

ootpath},nolock ip=192.168.123.19 vpif_display.ch2_numbuffers=0 vpif_display.ch3

_numbuffers=0

bootdelay=7

bootargs=mem=112M console=ttyS0,115200n8 root=/dev/hda1 rw ip=off vpif_display.c

h2_numbuffers=0 vpif_display.ch3_numbuffers=0

bootcmd=nboot 0x80700000 0 0x160000; bootm

stdin=serial

stdout=serial

stderr=serial

ver=U-Boot 2009.08 (Jan 20 2010 - 15:27:59)

Environment size: 1898/16380 bytes

DM6467 EVM > echo

DM6467 EVM >

DM6467 EVM >

DM6467 EVM >

DM6467 EVM >

DM6467 EVM >

DM6467 EVM >

DM6467 EVM >

DM6467 EVM > ping 192.168.123.33

Using DaVinci EMAC device

host 192.168.123.33 is alive

DM6467 EVM >

Using DaVinci EMAC device

host 192.168.123.33 is alive

DM6467 EVM >

Using DaVinci EMAC device

host 192.168.123.33 is alive

DM6467 EVM >

Using DaVinci EMAC device

host 192.168.123.33 is alive

DM6467 EVM > echo

DM6467 EVM >

DM6467 EVM >

DM6467 EVM > S echo SEE, NETWORK WORKING FROM U-BOOT

SEE, NETWORK WORKING FROM U-BOOT

DM6467 EVM > echo

DM6467 EVM >

DM6467 EVM >

DM6467 EVM >

DM6467 EVM > boot

Loading from NAND 128MiB 3,3V 8-bit, offset 0x160000

   Image Name: Arago/2.6.31+2.6.32-rc1-r31+gitr

   Image Type: ARM Linux Kernel Image (uncompressed)

   Data Size: 2061256 Bytes = 2 MB

   Load Address: 80008000

   Entry Point: 80008000

## Booting kernel from Legacy Image at 80700000 ...

   Image Name: Arago/2.6.31+2.6.32-rc1-r31+gitr

   Image Type: ARM Linux Kernel Image (uncompressed)

   Data Size: 2061256 Bytes = 2 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-rc2-davinci1 (denis@elrond) (gcc version 4.3.3 (Sourcery G+

+ Lite 2009q1-203) ) #1 PREEMPT Mon Jan 11 21:45:54 EST 2010

CPU: ARM926EJ-S [41069265] revision 5 (ARMv5TEJ), cr=00053177

CPU: VIVT data cache, VIVT instruction cache

Machine: DaVinci DM646x EVM

Memory policy: ECC disabled, Data cache writeback

DaVinci dm6467_rev3.x variant 0x1

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

Kernel command line: mem=112M console=ttyS0,115200n8 root=/dev/hda1 rw ip=off vp

if_display.ch2_numbuffers=0 vpif_display.ch3_numbuffers=0

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: 112MB = 112MB total

Memory: 109140KB available (3876K code, 335K data, 144K init, 0K highmem)

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

Hierarchical RCU implementation.

NR_IRQS:245

Console: colour dummy device 80x30

Calibrating delay loop... 246.57 BogoMIPS (lpj=1232896)

Mount-cache hash table entries: 512

CPU: Testing write buffer coherency: ok

DaVinci: 43 gpio irqs

NET: Registered protocol family 16

MUX: Setting register STSOMUX_DISABLE

PINMUX0 (0x00000000) = 0x00000000 -> 0x00000000

MUX: Setting register STSIMUX_DISABLE

PINMUX0 (0x00000000) = 0x00000000 -> 0x00000000

MUX: Setting register PTSOMUX_DISABLE

PINMUX0 (0x00000000) = 0x00000000 -> 0x00000000

MUX: Setting register PTSIMUX_DISABLE

PINMUX0 (0x00000000) = 0x00000000 -> 0x00000000

MUX: initialized CIR_UART2

MUX: Setting register CIR_UART2

PINMUX1 (0x00000004) = 0x00000000 -> 0x00000020

MUX: initialized ATAEN

MUX: Setting register ATAEN

PINMUX0 (0x00000000) = 0x00000000 -> 0x00000001

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

pcf857x 1-0038: gpios 145..152 on a pcf8574a

pcf857x 1-0038: setup --> -38

vpif vpif: vpif probe success

Switching to clocksource timer0_1

musb_hdrc: version 6.0, pio, peripheral, debug=0

musb_hdrc: USB Peripheral mode controller at fec64000 using PIO, IRQ 13

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

NET: Registered protocol family 1

RPC: Registered udp transport module.

RPC: Registered tcp transport module.

RPC: Registered tcp NFSv4.1 backchannel transport module.

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

msgmni has been set to 213

io scheduler noop registered

io scheduler anticipatory registered (default)

CIR device registered successfully (Major = 252, Minor =

0)

Serial: 8250/16550 driver, 3 ports, IRQ sharing disabled

serial8250.0: ttyS0 at MMIO 0x1c20000 (irq = 40) is a ST16654

console [ttyS0] enabled

serial8250 serial8250.0: unable to register port at index 1 (IO0 MEM1c20400 IRQ4

1): -22

serial8250 serial8250.0: unable to register port at index 2 (IO0 MEM1c20800 IRQ4

2): -22

brd: module loaded

loop: module loaded

at24 1-0050: 32768 byte 24c256 EEPROM (writable)

Read MAC addr from EEPROM: 00:0e:99:02:b7:78

Uniform Multi-Platform E-IDE driver

ide-gd driver 1.18

   ide0: MMIO-DMA

hda: TOSHIBA MK4032GAX, ATA DISK drive

hda: UDMA/100 mode selected

ide0 at 0xfec661f0-0xfec661f7,0xfec663f6 on irq 22

hda: max request size: 512KiB

hda: 78140160 sectors (40007 MB), CHS=16383/255/63

hda: cache flushes supported

hda: hda1 hda2

NAND device: Manufacturer ID: 0x20, Chip ID: 0xf1 (ST Micro NAND 128MiB 3,3V 8-b

it)

Scanning device for bad blocks

Creating 4 MTD partitions on "davinci_nand.0":

0x000000000000-0x000000020000 : "params"

0x000000020000-0x000000160000 : "bootloader"

0x000000160000-0x000000560000 : "kernel"

0x000000560000-0x000008000000 : "filesystem"

davinci_nand davinci_nand.0: controller rev. 2.2

spi_davinci spi_davinci.0: DaVinci SPI driver in EDMA mode

Using RX channel = 17 , TX channel = 16 and event queue = 3

at25 spi0.0: 32 KByte at25640a eeprom, pagesize 64

spi_davinci spi_davinci.0: Controller at 0xfec66800

PPP generic driver version 2.4.2

PPP Deflate Compression module registered

tun: Universal TUN/TAP device driver, 1.6

tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>

dm9000 Ethernet Driver, V1.31

console [netcon0] enabled

netconsole: network logging started

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 f6:ea:74:ec:0c:70

usb0: HOST MAC 56:be:c6:e7:05:1f

g_ether gadget: Ethernet Gadget, version: Memorial Day 2008

g_ether gadget: g_ether ready

i2c /dev entries driver

Linux video capture interface: v2.00

ths7303 1-002c: chip found @ 0x58 (DaVinci I2C adapter)

ths8200 1-0020: chip found @ 0x40 (DaVinci I2C adapter)

ths7353 1-002e: chip found @ 0x5c (DaVinci I2C adapter)

vpif_capture vpif_capture: registered sub device ths7353

tvp7002 1-005d: tvp7002 1-005d decoder driver registered !!

vpif_capture vpif_capture: registered sub device tvp7002

vpif_capture vpif_capture: DM646x VPIF Capture driver initialized

watchdog watchdog: heartbeat 60 sec

usbcore: registered new interface driver usbhid

usbhid: v2.6:USB HID core driver

Advanced Linux Sound Architecture Driver Version 1.0.21.

No device for DAI tlv320aic3x

asoc: tlv320aic3x <-> davinci-i2s mapping ok

asoc: DIT <-> davinci-dit mapping ok

ALSA device list:

  #0: DaVinci DM6467 EVM (tlv320aic3x)

TCP cubic registered

NET: Registered protocol family 17

Clocks: disable unused uart1

Clocks: disable unused emac

Clocks: disable unused timer1

emac-mii: probed

drivers/rtc/hctosys.c: unable to open rtc device (rtc0)

EXT3-fs warning: maximal mount count reached, running e2fsck is recommended

kjournald starting. Commit interval 5 seconds

EXT3 FS on hda1, internal journal

EXT3-fs: recovery complete.

EXT3-fs: mounted filesystem with writeback data mode.

VFS: Mounted root (ext3 filesystem) on device 3:1.

Freeing init memory: 144K

INIT: version 2.86 booting

Please wait: booting...

Starting udev

udev: starting version 141

udevd[1032]: inotify_add_watch(3, (null), 10) failed: Bad address

udevd[1032]: inotify_add_watch(3, (null), 10) failed: Bad address

udevd[1032]: inotify_add_watch(3, (null), 10) failed: Bad address

udevd[1032]: inotify_add_watch(3, (null), 10) failed: Bad address

udevd[1032]: inotify_add_watch(3, (null), 10) failed: Bad address

udevd[1032]: inotify_add_watch(3, (null), 10) failed: Bad address

udevd[1032]: inotify_add_watch(3, (null), 10) failed: Bad address

udevd[1032]: inotify_add_watch(3, (null), 10) failed: Bad address

udevd[1032]: inotify_add_watch(3, (null), 10) failed: Bad address

udevd[1032]: inotify_add_watch(3, (null), 10) failed: Bad address

udevd[1032]: inotify_add_watch(3, (null), 10) failed: Bad address

udevd[1032]: inotify_add_watch(3, (null), 10) failed: Bad address

snd_page_alloc: exports duplicate symbol snd_free_pages (owned by kernel)

soundcore: exports duplicate symbol sound_class (owned by kernel)

snd: module is already loaded

snd_timer: module is already loaded

ide_core: exports duplicate symbol generic_ide_ioctl (owned by kernel)

snd_pcm: module is already loaded

snd_soc_core: exports duplicate symbol snd_soc_unregister_codec (owned by kernel

)

ide_gd_mod: module is already loaded

snd_soc_tlv320aic3x: exports duplicate symbol soc_codec_dev_aic3x (owned by kern

el)

Remounting root file system...

EXT2-fs warning (device hda2): ext2_fill_super: mounting ext3 filesystem as ext2

EXT2-fs warning: mounting unchecked fs, running e2fsck is recommended

NET: Registered protocol family 10

root: mount: mounting rootfs on / failed: No such file or directory

Setting up IP spoofing protection: rp_filter.

Configuring network interfaces... eth0: attached PHY driver [ET1011C] (mii_bus:p

hy_addr=1:01, id=282f013)

ADDRCONF(NETDEV_UP): eth0: link is not ready

udhcpc (v1.13.2) started

Sending discover...

Sending discover...

PHY: 1:01 - Link is Up - 1000/Full

ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready

Sending discover...

No lease, failing

done.

Tue Jan 12 05:11:00 UTC 2010

INIT: Entering runlevel: 5

Starting telnet daemon.

Starting syslogd/klogd: done

Starting thttpd.

ERROR: Module cmemk does not exist in /proc/modules

ERROR: Module dsplinkk does not exist in /proc/modules

CMEMK module: built on Jan 13 2010 at 18:59:45

  Reference Linux version 2.6.32

  File /sim/scratch_a0850430/arago-install/dvsdk_3_10_00_11/linuxutils_2_25_01_0

6/packages/ti/sdo/linuxutils/cmem/src/module/cmemk.c

allocated heap buffer 0xcb000000 of size 0x8f000

cmemk initialized

DSPLINK Module (1.64) created on Date: Jan 13 2010 Time: 18:51:20

_____ _____ _ _

| _ |___ ___ ___ ___ | _ |___ ___ |_|___ ___| |_

| | _| .'| . | . | | __| _| . | | | -_| _| _|

|__|__|_| |__,|_ |___| |__| |_| |___|_| |___|___|_|

   |___| |___|

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

Arago 2009.11 dm6467t-evm ttyS0

dm6467t-evm login: root

root@dm6467t-evm:~# echo

root@dm6467t-evm:~#

root@dm6467t-evm:~#

root@dm6467t-evm:~#

root@dm6467t-evm:~#

root@dm6467t-evm:~#

root@dm6467t-evm:~#

root@dm6467t-evm:~#

root@dm6467t-evm:~# ping 192.168.123.33

PING 192.168.123.33 (192.168.123.33): 56 data bytes

ping: sendto: Network is unreachable

root@dm6467t-evm:~#

root@dm6467t-evm:~#

root@dm6467t-evm:~#

root@dm6467t-evm:~#

root@dm6467t-evm:~#

root@dm6467t-evm:~# echo SEE, NETWORK UNREACHABLE FROM ARAGO

SEE, NETWORK UNREACHABLE FROM ARAGO

root@dm6467t-evm:~# echo

root@dm6467t-evm:~#

root@dm6467t-evm:~#

root@dm6467t-evm:~#

root@dm6467t-evm:~#

root@dm6467t-evm:~#

root@dm6467t-evm:~# ip fconfig

eth0 Link encap:Ethernet HWaddr 00:0E:99:02:B7:78

   inet6 addr: fe80::20e:99ff:fe02:b778/64 Scope:Link

   UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1

   RX packets:24 errors:0 dropped:0 overruns:0 frame:0

   TX packets:7 errors:0 dropped:0 overruns:0 carrier:0

   collisions:0 txqueuelen:1000

   RX bytes:2243 (2.1 KiB) TX bytes:1058 (1.0 KiB)

   Interrupt:24

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@dm6467t-evm:~# echo

root@dm6467t-evm:~#

root@dm6467t-evm:~#

root@dm6467t-evm:~#

root@dm6467t-evm:~# ifconfig eth0 192.168.123.19

root@dm6467t-evm:~# ifconfig

eth0 Link encap:Ethernet HWaddr 00:0E:99:02:B7:78

   inet addr:192.168.123.19 Bcast:192.168.123.255 Mask:255.255.255.0

   inet6 addr: fe80::20e:99ff:fe02:b778/64 Scope:Link

   UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1

   RX packets:29 errors:0 dropped:0 overruns:0 frame:0

   TX packets:7 errors:0 dropped:0 overruns:0 carrier:0

   collisions:0 txqueuelen:1000

   RX bytes:2587 (2.5 KiB) TX bytes:1058 (1.0 KiB)

   Interrupt:24

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@dm6467t-evm:~# ping 192.168.123.33

PING 192.168.123.33 (192.168.123.33): 56 data bytes

--- 192.168.123.33 ping statistics ---

9 packets transmitted, 0 packets received, 100% packet loss

root@dm6467t-evm:~# echo G WAS GOING TO TIMEOUT SO CANCELLED

WAS GOING TO TIMEOUT SO CANCELLED

root@dm6467t-evm:~# echo

root@dm6467t-evm:~#

root@dm6467t-evm:~#

root@dm6467t-evm:~#

root@dm6467t-evm:~#

root@dm6467t-evm:~#

root@dm6467t-evm:~#

root@dm6467t-evm:~# echo SEE, WHEN I SET IP C INFO, NO LONGER SAYS UNERAC REACHABLE, BU

T DOESN'T WORK EITHER.

0 Sanjeev Premi over 14 years ago in reply to Helmut Forren

TI__Expert 4590 points

Helmut Forren said:

DaVinci dm6467_rev3.x variant 0x1

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

Kernel command line: mem=112M console=ttyS0,115200n8 root=/dev/hda1 rw ip=off vp if_display.ch2_numbuffers=0 vpif_display.ch3_numbuffers=0

I notice ip=off in your kernel command-line highlighted above. Then, later on:

Helmut Forren said:

NET: Registered protocol family 17

Clocks: disable unused uart1

Clocks: disable unused emac

Clocks: disable unused timer1

emac-mii: probed

The bootarg ip=off is ensuring the networking subsystem remains disabled! Can you remove this and try again?

0 Helmut Forren over 14 years ago in reply to Sanjeev Premi

Mastermind 6805 points

YEAH! THAT FIXE... oops, no, that did not fix it.

First, I neither created nor understood nor remember the origin of the "ip=off". It either came with the EVM, or I got it from some forum post or wiki.

Second, my board had been off all night. I turned it on, removed ip=off, and networking WORKED. I "shutdown -r 0" and when rebooted it worked AGAIN. Then I "shutdown 0" and turned the power off and on. Networking FAILED again. Note that I did *not* establish a baseline failure this morning before removing the ip=off.

In addition, the network did work at least once yesterday, with the ip=off present.

Anyway, the ip=off is not there right now, and networking still fails.

Huh? And now it's working again. I did leave the power switch off longer. I'm trying again... Works again. It was either the power not being off long enough (2 full seconds must not be long enough, tried 10 seconds), or there's just a little randomness still. But at least now I think it may work the MAJORITY of the time rather than RARELY.

Thanks VERY Much Sanjeev for analyzing this. I'll move on to actual NFS root file system next...

-Helmut

EDIT: RESULT = Not reliable but in general SOLVED FOR NOW.

Processors

Processors forum

Network quit working on DM6467T EVM