• State
  • Locked Locked
  • Replies 14 replies
  • Subscribers 100 subscribers
  • Views 2075 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

DM355 and NFS Problem

Alex5208
Intellectual 570 points
Other Parts Discussed in Thread: TMS320DM355

Hello,

I have a problem with booting via NFS File System.

Here is the "printenv":

bootdelay=3

baudrate=115200

bootfile="uImage"

ip=192.168.0.20

ipaddr=192.168.0.20

nfshost=192.168.0.1

rootpath=/home/koa/workdir/filesys

bootcmd=nboot 0x80700000 0 0x400000;bootm

bootargs=console=ttyS0,115200n8 noinitrd rw ip=dhcp root=/dev/nfs nfsroot=192.168.0.1:/home/koa/workdir/filesys,nolock mem=116m

stdin=serial

stdout=serial

stderr=serial

videostd=pal

Environment size: 361/16380 bytes

DM355 EVM #

 

Here is the Boot-Log:

UBL: detected valid U-Boot magic number

UBL: booting to U-Boot

 

 

U-Boot 1.2.0 (Oct 17 2007 - 15:38:02)

 

DRAM: 128 MB

NAND: NAND device: Manufacturer ID: 0x2c, Chip ID: 0xd3 (Micron NAND 1GiB 3,3V 8-bit)

Bad block table found at page 524224, version 0x01

Bad block table found at page 524160, version 0x01

nand_read_bbt: Bad block at 0x0ff00000

nand_read_bbt: Bad block at 0x180a0000

nand_read_bbt: Bad block at 0x1b3e0000

nand_read_bbt: Bad block at 0x267c0000

nand_read_bbt: Bad block at 0x2cd60000

nand_read_bbt: Bad block at 0x30980000

nand_read_bbt: Bad block at 0x309a0000

nand_read_bbt: Bad block at 0x30a40000

nand_read_bbt: Bad block at 0x30c80000

nand_read_bbt: Bad block at 0x30ca0000

nand_read_bbt: Bad block at 0x313c0000

nand_read_bbt: Bad block at 0x313e0000

nand_read_bbt: Bad block at 0x31480000

nand_read_bbt: Bad block at 0x314a0000

nand_read_bbt: Bad block at 0x315c0000

nand_read_bbt: Bad block at 0x315e0000

nand_read_bbt: Bad block at 0x318c0000

nand_read_bbt: Bad block at 0x318e0000

nand_read_bbt: Bad block at 0x31980000

nand_read_bbt: Bad block at 0x319a0000

nand_read_bbt: Bad block at 0x31bc0000

nand_read_bbt: Bad block at 0x31be0000

nand_read_bbt: Bad block at 0x31e80000

nand_read_bbt: Bad block at 0x31ea0000

nand_read_bbt: Bad block at 0x31f40000

nand_read_bbt: Bad block at 0x31f60000

nand_read_bbt: Bad block at 0x32180000

nand_read_bbt: Bad block at 0x321a0000

nand_read_bbt: Bad block at 0x32240000

nand_read_bbt: Bad block at 0x32260000

nand_read_bbt: Bad block at 0x32500000

nand_read_bbt: Bad block at 0x32520000

nand_read_bbt: Bad block at 0x32740000

nand_read_bbt: Bad block at 0x32760000

nand_read_bbt: Bad block at 0x32980000

nand_read_bbt: Bad block at 0x32c40000

nand_read_bbt: Bad block at 0x3a6e0000

nand_read_bbt: Bad block at 0x3cfe0000

NAND device: Manufacturer ID: 0x2c, Chip ID: 0xd3 (Micron NAND 1GiB 3,3V 8-bit)

Bad block table found at page 524224, version 0x01

Bad block table found at page 524160, version 0x01

nand_read_bbt: Bad block at 0x04060000

nand_read_bbt: Bad block at 0x0bdc0000

nand_read_bbt: Bad block at 0x11960000

nand_read_bbt: Bad block at 0x13f80000

nand_read_bbt: Bad block at 0x144e0000

nand_read_bbt: Bad block at 0x1d320000

nand_read_bbt: Bad block at 0x2acc0000

nand_read_bbt: Bad block at 0x397e0000

2048 MiB

In: serial

Out: serial

Err: serial

ARM Clock :- 216MHz

DDR Clock :- 171MHz

Hit any key to stop autoboot: 0

 

Loading from NAND 1GiB 3,3V 8-bit, offset 0x400000

Image Name: Linux-2.6.10_mvl401

Image Type: ARM Linux Kernel Image (uncompressed)

Data Size: 1585240 Bytes = 1.5 MB

Load Address: 80008000

Entry Point: 80008000

## Booting image at 80700000 ...

Image Name: Linux-2.6.10_mvl401

Image Type: ARM Linux Kernel Image (uncompressed)

Data Size: 1585240 Bytes = 1.5 MB

Load Address: 80008000

Entry Point: 80008000

Verifying Checksum ... OK

OK

 

Starting kernel ...

 

Linux version 2.6.10_mvl401 (a0270758@gtmatrix) (gcc version 3.4.3 (MontaVista 3.4.3-25.0.104.0600975 2006-07-06)) #1 Wed Oct 17 15:44:12 EDT 2007

CPU: ARM926EJ-Sid(wb) [41069265] revision 5 (ARMv5TEJ)

CPU0: D VIVT write-back cache

CPU0: I cache: 16384 bytes, associativity 4, 32 byte lines, 128 sets

CPU0: D cache: 8192 bytes, associativity 4, 32 byte lines, 64 sets

Machine: DaVinci DM355 EVM

Memory policy: ECC disabled, Data cache writeback

DM0350

Built 1 zonelists

Kernel command line: console=ttyS0,115200n8 noinitrd rw ip=dhcp root=/dev/nfs nfsroot=192.168.0.1:/home/koa/workdir/filesys,nolock mem=116m

PID hash table entries: 512 (order: 9, 8192 bytes)

Console: colour dummy device 80x30

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

Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)

Memory: 116MB = 116MB total

Memory: 114176KB available (2762K code, 585K data, 164K init)

Mount-cache hash table entries: 512 (order: 0, 4096 bytes)

CPU: Testing write buffer coherency: ok

spawn_desched_task(00000000)

desched cpu_callback 3/00000000

ksoftirqd started up.

desched cpu_callback 2/00000000

desched thread 0 started up.

NET: Registered protocol family 16

Registering platform device 'serial8250.0'. Parent at platform

Registering platform device 'nand_davinci.0'. Parent at platform

Registering platform device 'dm9000.0'. Parent at platform

Registering platform device 'mmc.0'. Parent at platform

Registering platform device 'mmc.1'. Parent at platform

DaVinci I2C DEBUG: 15:42:09 Oct 17 2007

Registering platform device 'i2c'. Parent at platform

SCSI subsystem initialized

usbcore: registered new driver usbfs

usbcore: registered new driver hub

musb_hdrc: version 2.2a/db-0.4.8 [pio] [host] [debug=0]

Registering platform device 'musb_hdrc'. Parent at platform

musb_hdrc: USB Host mode controller at c7800000 using PIO, IRQ 12

musb_hdrc musb_hdrc: new USB bus registered, assigned bus number 1

hub 1-0:1.0: USB hub found

hub 1-0:1.0: 1 port detected

arch/arm/mach-davinci/spi_platform_init.c:dm355_spi_board_init:123 dm355_spi_board_init

arch/arm/mach-davinci/spi_platform_init.c:dm355_spi_board_init:129 REG BOARD ret 0

Registering platform device 'dm_spi.0'. Parent at platform

arch/arm/mach-davinci/spi_platform_init.c:dm355_spi_board_init:136 REGISTER DEVICE ret 0

NetWinder Floating Point Emulator V0.97 (double precision)

JFFS2 version 2.2. (NAND) (C) 2001-2003 Red Hat, Inc.

yaffs Oct 17 2007 15:41:45 Installing.

Initializing Cryptographic API

Registering platform device 'dm355fb.0'. Parent at platform

Console: switching to colour frame buffer device 90x30

watchdog: TI DaVinci Watchdog Timer: timer margin 64 sec

Registering platform device 'davinci_pwm0.0'. Parent at platform

Registering platform device 'davinci_pwm1.1'. Parent at platform

Registering platform device 'davinci_pwm2.2'. Parent at platform

Registering platform device 'davinci_pwm3.3'. Parent at platform

Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing disabled

Registering platform device 'serial8250'. Parent at platform

ttyS0 at MMIO 0x1c20000 (irq = 40) is a 16550A

ttyS1 at MMIO 0x1c20400 (irq = 41) is a 16550A

ttyS2 at MMIO 0x1e06000 (irq = 14) is a 16550A

io scheduler noop registered

io scheduler anticipatory registered

RAMDISK driver initialized: 1 RAM disks of 32768K size 1024 blocksize

loop: loaded (max 8 devices)

dm9000 Ethernet Driver

eth0: dm9000 at c7862000,c7864002 IRQ 45 MAC: 00:0e:99:02:c2:5b

i2c /dev entries driver

Linux video capture interface: v1.00

Registering platform device 'vpfe.1'. Parent at platform

vpfe vpfe.1: DaVinci v4l2 capture driver V1.0 loaded

ipipe major#: 253, minor# 0

Registering platform device 'dm355_ipipe.2'. Parent at platform

ipipe driver registered

af major#: 252, minor# 0

Registering platform device 'dm355_af.2'. Parent at platform

aew major#: 251, minor# 0

Registering platform device 'dm355_aew.2'. Parent at platform

elevator: using anticipatory as default io scheduler

at25xxA_spi_eeprom init

nand_davinci nand_davinci.0: Using 4-bit hardware ECC

NAND device: Manufacturer ID: 0x2c, Chip ID: 0xd3 (Micron NAND 1GiB 3,3V 8-bit)

2 NAND chips detected

nand_bbt: ECC error while reading bad block table

nand_bbt: ECC error while reading bad block table

Creating 5 MTD partitions on "nand_davinci.0":

0x00000000-0x003c0000 : "bootloader"

0x003c0000-0x00400000 : "params"

0x00400000-0x00800000 : "kernel"

0x00800000-0x20800000 : "filesystem1"

0x20800000-0x80000000 : "filesystem2"

nand_davinci nand_davinci.0: hardware revision: 2.3

scan_boardinfo:<NULL>:-1067858964

modias <NULL> irq 2000000 max_speed 65535 bus_num 0 chip_select 0 mode -1068867824

drivers/spi/spi.cat25xxA_spi_eeprom device register Succeeded

dm_spi.0: dm355 SPI Controller driver at 0xc7866000 (irq = 42)

Initializing USB Mass Storage driver...

usbcore: registered new driver usb-storage

USB Mass Storage support registered.

usbcore: registered new driver usbhid

drivers/usb/input/hid-core.c: v2.0:USB HID core driver

mice: PS/2 mouse device common for all mice

mmc mmc.0: Supporting 4-bit mode

mmc mmc.0: Using DMA mode

mmc mmc.1: Supporting 4-bit mode

mmc mmc.1: Using DMA mode

Registering platform device 'davinci-audio.0'. Parent at platform

NET: Registered protocol family 2

IP: routing cache hash table of 512 buckets, 4Kbytes

TCP: Hash tables configured (established 8192 bind 16384)

Initializing XFRM netlink socket

NET: Registered protocol family 1

NET: Registered protocol family 10

IPv6 over IPv4 tunneling driver

NET: Registered protocol family 17

eth0: link down

Sending DHCP requests ., OK

IP-Config: Got DHCP answer from 0.0.0.0, my address is 192.168.0.10

IP-Config: Complete:

device=eth0, addr=192.168.0.10, mask=255.255.255.0, gw=255.255.255.255,

host=192.168.0.10, domain=lan, nis-domain=(none),

bootserver=0.0.0.0, rootserver=192.168.0.1, rootpath=

Looking up port of RPC 100003/2 on 192.168.0.1

eth0: link up, 100Mbps, full-duplex, lpa 0x45E1

portmap: server 192.168.0.1 not responding, timed out

Root-NFS: Unable to get nfsd port number from server, using default

Looking up port of RPC 100005/1 on 192.168.0.1

portmap: server 192.168.0.1 not responding, timed out

Root-NFS: Unable to get mountd port number from server, using default

mount: server 192.168.0.1 not responding, timed out

Root-NFS: Server returned error -5 while mounting /home/koa/workdir/filesys

VFS: Unable to mount root fs via NFS, trying floppy.

VFS: Cannot open root device "nfs" or unknown-block(2,0)

Please append a correct "root=" boot option

Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(2,0)

 

I am Using Fedora Core 9 at the Host Station and i can mount the "/home/koa/workdir/filesys" path with nfs mount at the host station using "mount nfs 192.168.0.1:/home/koa/workdir/filesys /mnt".

So i think nfs is working... but i am not sure, because i am very new to Linux...

It would be very nice if anybody could help me out with this...

Thanx alot Alex!

  • 0
    TI__Mastermind 37340 points

    Hi Alex,

    Three things come to mind after analyzing your boot log.

    1) should u-boot environment variable "ip" be "serverip" (see Getting Started Guide)?

    2) is the ip address you are using to set bootargs the address ip address of your Linux host? it should be

    3) on the host side, have you specified the directory you are trying to nfs mount in the /etc/exports file (see Getting Started Guide)?

    Also, I would try loading Linux Kernel via TFTP as well (See Getting Started Guide); this is because the dhcp servers in certain routers can cause network issues.  If you can TFTP successfully, then we can rule out network issue and focus on NFS issue.

    I hope these suggestions help.

  • 0 in reply to Juan Gonzales
    Intellectual 570 points

    Hi and thx for fast answering...

    1) oh no this is kind of old var... i tried booting without dhcp and now i dont know how to delete these Vars... These Vars also 192.168.0.20 should be the ip of the Board, but now i have changed them to 10 cause this is the ip the board is getting from the dhcp. (No it shouldnt be "serverip")

    2) if you mean nfsroot=192.168.0.1 ?? Yes this is the ip of the host and of the dhcp server

    3)yes i have i will post you the line, its like the tutorial from the Getting Started Guide...

    /home/koa/workdir/filesys *(rw,no_root_squash,no_all_squash,sync)

    I dont think there are network issues, cause if i am opening http://192.168.0.10 i can see the Page of the Board from the Demo Software.

     

    I also changed the host.allow and host.deny files and inserted the Ip´s of Host(192.168.0.1) and Board(192.168.0.10) as Allowed IP´s. In the Deny file i denied everything.

    Like This (Deny File)

    lockd:ALL

    mountd:ALL

    rquotad:ALL

    statd:ALL

    Alsmost the same for the Allowfile...

    lockd: 192.168.0.10 , 192.168.0.1

    mountd: 192.168.0.10 , 192.168.0.1

    rquotad: 192.168.0.10 , 192.168.0.1

    statd: 192.168.0.10 , 192.168.0.1

    portmap: 192.168.0.10 , 192.168.0.1

     

    I also booted the board from the Flash and did from my Host Station a "rpcinfo -p 192.168.0.10" so there is conection refused..

    If i start portmap manually at the Board after booting from Flash i got an answer at the Host Station. "Port 111 TCP/UDP portmapper Vers. 2 programm 100000"

    I tried to "rpcinfo" from the Board with "rpcinfo -p 192.168.0.1" to check the connection to Host Station... But there is no rpc-info at the Board???

    so far i hope u have some other ideas..

     

  • 0 in reply to Alex5208
    TI__Mastermind 37340 points

    1) To clear a variable in u-boot, simply type "setenv <variable name>"; if nothing follows the variable name, it will clear it.

    2) Can you ping (linux ping command is "ping <ip-address>" ) the host for the target u-boot prompt?

  • 0 in reply to Juan Gonzales
    Intellectual 570 points

    1) thx i have deleted them

    2) yes i can

    host --> board works fine ~ 0,4ms ping

    and if i boot from nand flash and log in with root i can ping the host...

    board --> host works fine ~ 0,5ms ping

  • 0 in reply to Alex5208
    TI__Mastermind 37340 points

    regarding #2, the ip address "192.168.0.1" looks odd to me; is this the ip address your host returns if you type 'ifconfig' Linux command on your host.  Also, for good measure, I would restart nfs service per Getting Started Guide.

  • 0 in reply to Juan Gonzales
    Intellectual 570 points

    yes this ist the address...

    maybe its "even"er to you if i say, that i am only have my latop with fedorce c9 and the board wired over a ethernet switch running?

    I will change now the ip of my laptop from 192.168.0.1 to 192.168.1.9 and change my dhcp and try restarting the nfs service.

  • 0 in reply to Alex5208
    TI__Mastermind 41665 points

    I think the line 'portmap: server 192.168.0.1 not responding, timed out' is indicating that there is some problem with the board contacting the host, the first thing this brings to mind to me is if you have a active firewall on the host pc, so the first thing I would do is double check that your firewall is not active.

    I also found an entry on the Davinci Linux open source list where this error came up, where it was also suggested to make sure that your portmap daemon is running on the host with 'rpcinfo -p'. http://www.mail-archive.com/davinci-linux-open-source@linux.davincidsp.com/msg06110.html

  • 0 in reply to Bernie Thompson TI
    Intellectual 570 points

    Hi

    the firewall is disabled due i am alone in this small network.

    I found the rpcinfo -p hint too and tried it... @ mom i cant test it again cause my laptop is still doing again the getting started guide. and i cant check for changes with the changed ip adresses...

    but about 1 hour ago i testest:

    1) rpcinfo -p (@ host station) ---> a long list with a large list of services (portmapper, nfs, mountd, nlockmgr, rquatad, etc..)

    2) rpcinfo -p 192.168.0.10 (@host station asking for board) --> con refused

    3) starting portmap at the board

    rpcinfo -p 192.168.0.10 (@host station asking for board) --> two entries for portmapper

     

  • 0 in reply to Alex5208
    Intellectual 570 points

    Hi its me again

    I changed now the IP adress of my Laptop to 192.168.1.9 (Its the Host Station AND the DHCP/NFS Server)

    The Board is getting 192.168.1.10 from the DHCP during booting...

    if i check rpcinfo its the same like with old ip´s...  Host as a large List, and the Board has only a list if i boot from nand and start portmapper manually. Then i am able to se the portmapper on the board if i type "rpcinfo -p 192.168.1.10" into the console.

    There is no firewall active, i have free access to the webpage of the Board (if i am booting from flash). 

    There are stille the same errors like with old adresses. I hope you have some other good ideas...

     

    i forgot something to say ;)

    i did the getting started manual for the nfs again with nothing new to report, still the same problem

  • 0 in reply to Alex5208
    TI__Mastermind 41665 points

    Just to be sure you may try running '/etc/init.d/iptables status' to make sure the firewall is disabled, if it is not 'etc/init.d/iptables stop' will halt it. Note that just because you can access the web page on the board it does not mean you have no firewall, most Linux distributions seem to come with the firewall enabled by default but configured such that you can still open web pages.

  • 0 in reply to Alex5208
    TI__Mastermind 37340 points

    Another thing you can try is getting rid of all routers/switches and useing static IPs; see the following document for more details

    http://focus.ti.com/lit/an/spraaq0/spraaq0.pdf

    This was written for the DM6446, but should apply to DM355 as well. 

  • 0 in reply to Bernie Thompson TI
    Intellectual 570 points

    Bernie Thompson said:

    Just to be sure you may try running '/etc/init.d/iptables status' to make sure the firewall is disabled, if it is not 'etc/init.d/iptables stop' will halt it. Note that just because you can access the web page on the board it does not mean you have no firewall, most Linux distributions seem to come with the firewall enabled by default but configured such that you can still open web pages.

     

    Hey Thanx!

    You were right. i did iptables status and it shows me some entries, id did iptables stop and it works!

    Are there two different firewalls? Cause in the Controllcenter of Fedore was also an entry for firewall and there i disabled the firewall...

    thx a lot Alex

    p.s. i will be back for more questions :)

  • 0 in reply to Alex5208
    TI__Mastermind 41665 points

    Alex said:
    Are there two different firewalls?

    This I am not sure of, it may be that the GUI firewall control is not as in depth as the iptables command, what the GUI firewall control does probably varies from distribution to distribution. I believe that on the Red Hat Enterprise 4 images we use that the GUI firewall disabling is enough, but if you run into issues like this it is always worth checking the iptables command.

  • 0 in reply to Juan Gonzales
    Expert 1335 points

    hi,

    I am unable to mount root file system for DM355 and also unable to SSH.

    I follow the steps given in TMS320DM355 DVEVMv1.30 Getting Started Guide.

    Thanks and regards,

    Mohammed asif