Network connection

ryuichi morishima

Prodigy 120 points

Other Parts Discussed in Thread: PCF8575, PMP

HI, friends.

I purchased TMDXEVM8148 and am trying to connect it to PC over ethernet.

We are having the following problem.

--WE cannot download kernel over ethernet.

Bootloader from SDCARD is working correctly(we think)

but, letters"T T T T T T T " is displayed on terminal window.

and we are asked if we would retry after some amount of time.

We can set IPADDR, and SERVERIP using setenv command .

When we use ping command to　check ethernet connection, message "host IP_ADDRSS is alive ."is displayed.

Can you help us solve the problem?

over 13 years ago

0 Anil over 13 years ago

TI__Expert 6655 points

Hi Ryuichi,

What are the bootargs you are using? and provide the boot log as well.

Make sure that tftp server is running properly (if you are using tftp boot)

Regards

AnilKumar

Please mark this Forum post as answered via the Verify Answer button below if it helps answer your question. Thanks!

0 ryuichi morishima over 13 years ago in reply to Anil

Prodigy 120 points

Hi Anil,

Thank you for replying.

We entered command "setenv bootargs",and the teminal displays "bootargs not defined".

So we implemented the following command on the manual "DM814x AM387x PSP U-Boot"

-p.27 Enviroment Settings for Ramdisk (in case of SD)

-p.28 Enviroment Settings for JFFS2 Filesystem

-p.29 Enviroment Settings for NFS Filesystem

But we don't successfuly boot.

The terminal displays the following messege, and u-boot hangs.

************************************************************************

TI8148_EVM#boot
reading uImage

2570080 bytes read
## Booting kernel from Legacy Image at 81000000 ...
   Image Name:   Arago/2.6.37-psp04.01.00.06/dm81
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2570016 Bytes = 2.5 MiB
   Load Address: 80008000
   Entry Point: 80008000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK
OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.

************************************************************************

Best Regards

Ryuichi

0 Anil over 13 years ago in reply to ryuichi morishima

TI__Expert 6655 points

Hi Ryuichi,

Details of environment variable settings can be found at

http://processors.wiki.ti.com/index.php/DM814x_AM387x_PSP_U-Boot#U-Boot_Environment_Variables

Follow below steps for taking the user defined environment variables from script file

http://processors.wiki.ti.com/index.php/DM814x_AM387x_PSP_U-Boot#ENV_on_SD_card_using_a_script

While setting the bootargs variable append earlyprintk (For printing the logs)

Ryuichi: We entered command "setenv bootargs",and the teminal displays "bootargs not defined".

Anil: If you are doing only "setenv bootargs" then bootargs variable is undefined. For printing the bootargs you have to use "print bootargs"

Regards

AnilKumar

Please mark this Forum post as answered via the Verify Answer button below if it helps answer your question. Thanks!

0 ryuichi morishima over 13 years ago in reply to Anil

Prodigy 120 points

Hi Anil,

We set the enviromental values reffering to

http://processors.wiki.ti.com/index.php/DM814x_AM387x_PSP_U-Boot#U-Boot_Environment_Variables

We enterted printenv command and the results are below

TI8148_EVM#printenv
verify=yes
ramdisk_file=ramdisk.gz
loadaddr=0x81000000
script_addr=0x80900000
loadbootscript=fatload mmc 0 ${script_addr} boot.scr
bootscript= echo Running bootscript from MMC/SD to set the ENV...; source ${scri
pt_addr}
ethaddr=40:5f:c2:40:f6:c1
ethact=cpsw
ip_addr=10.140.10.43
ip=addr 10.140.10.43
ipserver=10.140.19.128
ipaddr=10.140.10.43
gateway=10.140.104.21
hostname=dm8148
dnsip=10.207.104.101
gatewayip=10.140.104.21
nfsserver=10.140.19.128
dnsip2=10.202.104.4
netmask=255.255.0.0
bootdelay=4
baudrate=115200
oldbootargs=console=ttyO0 115200n8 rootwait rw mem=256M earlyprintk notifyk.vpss
m3_sva=0xBF900000 vram=50M ti814xfv.vram0:16M,2:6Mroot=/dev/nfs nfsroot=10.140.1
9.128:/home/top10015/targetfs ip=10.140.10.43:10.140.19.128:10.140.104.21:255.25
5.0.0:dm8148:eth0:off
autoload=no
oldserverip=10.140.19.128
oldbootfile=uImage-dm814x-evm.bin
bootfile=uImage-dm814x-evm.bin
oldbootcmd=setenv serverip 10.140.19.128;tftpboot;bootm
nfsroot=10.140.19.128:/home/top10015/targetfs ip=10.140.10.43:10.140.19.128:10.140.104.21:255.255.0.0:dm8148:eth0:off
serverip=10.140.19.128
addip=setenv bootargs console=ttyO0,115200n8 rootdely=4 rw mem=256M earlyprintk.vpssm3_sva=0xBF900000 vram=50M ti814xfv.vram0:16M,2:6M root=/dev/nfs ip=10.140.10.43:10.140.19.128:10.140.104.21:255.255.0.0:dm8148:eth0:off
bootargs=console=ttyO0,115200n8 rootdely=4 rw mem=256M earlyprintk.vpssm3_sva=0xBF900000 vram=50M ti814xfv.vram0:16M,2:6M root=/dev/nfs ip=10.140.10.43:10.140.19.128:10.140.104.21:255.255.0.0:dm8148:eth0:off
rootpath=/home/top10015/targetfs
bootcmd=run addip;tftp 81000000 uImage;bootm
stdin=serial
stdout=serial
stderr=serial

Environment size: 1628/8188 bytes

But we don't successfuly boot,the terminal displays the following messege

TI8148_EVM#boot
link up on port 0, speed 100, full duplex
Using cpsw device
TFTP from server 10.140.19.128; our IP address is 10.140.10.43
Filename 'uImage'.
Load address: 0x81000000
Loading: T T T T T T T T T T T T T T T T T T T T
Retry count exceeded; starting again
link up on port 0, speed 100, full duplex

(We entered "Ctrl + C")
Abort
## Booting kernel from Legacy Image at 81000000 ...
   Image Name:   Arago/2.6.37-psp04.01.00.06/dm81
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2570016 Bytes = 2.5 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 20
09q1-203) ) #1 Thu Nov 10 23:48:02 IST 2011
CPU: ARMv7 Processor [413fc082] revision 2 (ARMv7), cr=10c53c7f
CPU: VIPT nonaliasing data cache, VIPT aliasing instruction cache
Machine: ti8148evm
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.0
Built 1 zonelists in Zone order, mobility grouping on. Total pages: 52224
Kernel command line: console=ttyO0,115200n8 rootdely=4 rw mem=256M earlyprintk.v
pssm3_sva=0xBF900000 vram=50M ti814xfv.vram0:16M,2:6M root=/dev/nfs ip=10.140.10
.43:10.140.19.128:10.140.104.21:255.255.0.0:dm8148:eth0:off
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: 203148k/203148k available, 58996k 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 - 0xc003a000   ( 200 kB)
      .text : 0xc003a000 - 0xc04de000   (4752 kB)
      .data : 0xc04de000 - 0xc0526300   ( 289 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 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
registered ti814x_vpss device
registered TI814x on-chip HDMI device
NOR: Can't request GPMC CS
registered ti81xx_vidout device
Debugfs: Only enabling/disabling deep sleep and wakeup timer is supported now
Registered ti81xx_fb 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
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
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-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-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 396
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
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
NAND device: Manufacturer ID: 0x2c, Chip ID: 0xca (Micron )
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"
usb 1-1: new low speed USB device using musb-hdrc and address 2
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
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 adapter
s
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
usb 1-1: New USB device found, idVendor=04f3, idProduct=0234
usb 1-1: New USB device strings: Mfr=0, Product=2, SerialNumber=0
usb 1-1: Product: OM
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/i2
c-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
input: OM as /devices/platform/omap/ti81xx-usbss/musb-hdrc.0/usb1/1-1/1-1:1.0/in
put/input1
generic-usb 0003:04F3:0234.0001: input: USB HID v1.11 Mouse [OM] on usb-musb-hdr
c.0-1/input0
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
usbcore: registered new interface driver snd-usb-audio
asoc: tlv320aic3x-hifi <-> davinci-mcasp.2 mapping ok
ALSA device list:
#0: TI81XX EVM
TCP cubic registered
NET: Registered protocol family 17
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:40:f6:c1
omap_rtc omap_rtc: setting system clock to 2000-01-01 00:00:00 UTC (946684800)
mmc0: new high speed SDHC card at address e624
mmcblk0: mmc0:e624 SD08G 7.40 GiB
mmcblk0: p1 p2 p3

CPSW phy found : id is : 0x4dd074

CPSW phy found : id is : 0x4dd074
IP-Config: Complete:
     device=eth0, addr=10.140.10.43, mask=255.255.0.0, gw=10.140.104.21,
     host=dm8148, domain=, nis-domain=(none),
     bootserver=10.140.19.128, rootserver=10.140.19.128, rootpath=
PHY: 0:01 - Link is Up - 0/Half
PHY: 0:01 - Link is Down
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; here are the available partitions:
1f00             128 mtdblock0 (driver?)
1f01            2304 mtdblock1 (driver?)
1f02             128 mtdblock2 (driver?)
1f03            4352 mtdblock3 (driver?)
1f04          204928 mtdblock4 (driver?)
1f05           50304 mtdblock5 (driver?)
b300         7761920 mmcblk0 driver: mmcblk
b301           40131 mmcblk0p1 00000000-0000-0000-0000-000000000mmcblk0p1
b302          883575 mmcblk0p2 00000000-0000-0000-0000-000000000mmcblk0p2
b303         6835657 mmcblk0p3 00000000-0000-0000-0000-000000000mmcblk0p3
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(2,0)
Backtrace:
[<c0048b70>] (dump_backtrace+0x0/0x110) from [<c039dac0>] (dump_stack+0x18/0x1c)
r7:ccb52000 r6:00000000 r5:c002d9cc r4:c0526a90
[<c039daa8>] (dump_stack+0x0/0x1c) from [<c039db24>] (panic+0x60/0x17c)
[<c039dac4>] (panic+0x0/0x17c) from [<c0009258>] (mount_block_root+0x1e0/0x220)
r3:00000000 r2:00000000 r1:cc82bf58 r0:c04613ac
[<c0009078>] (mount_block_root+0x0/0x220) from [<c0009344>] (mount_root+0xac/0xc
c)
[<c0009298>] (mount_root+0x0/0xcc) from [<c00094d4>] (prepare_namespace+0x170/0x
1d4)
r4:c0526364
[<c0009364>] (prepare_namespace+0x0/0x1d4) from [<c0008784>] (kernel_init+0x114/
0x154)
r5:c0008670 r4:c0526300
[<c0008670>] (kernel_init+0x0/0x154) from [<c006e694>] (do_exit+0x0/0x5e4)
r5:c0008670 r4:00000000

Regards

Ryuichi

0 Norman Wong over 13 years ago in reply to ryuichi morishima

Guru 26430 points

The bootarg rootdely=4 should be rootdelay=4.

0 Anil over 13 years ago in reply to Norman Wong

TI__Expert 6655 points

Hi Ryuichi,

Prerequisite:-
1. Make sure that NFS server (filesystem) is running on machine having ipaddress = 10.140.19.128
2. Make sure that tftp server is running on 10.140.19.128 and the server is pointing the folder where uImage is located

Use any of these two sets

DHCP:-
1. setenv bootargs 'console=ttyO0,115200n8 root=/dev/nfs nfsroot=10.140.19.128:/home/top10015/targetfs,nolock rw mem=128M ip=dhcp earlyprintk rootdelay=4'
2. setenv bootcmd 'dhcp;tftp 81000000 uImage;bootm'
3. set the serverip 10.140.19.128
4. setenv ipaddr
5. boot

Static ip:-
1. setenv bootargs 'console=ttyO0,115200n8 root=/dev/nfs nfsroot=10.140.19.128:/home/top10015/targetfs,nolock rw mem=128M earlyprintk rootdelay=4'
2. setenv addip 'setenv bootargs ${bootargs} ip=${ipaddr}:${nfsserver}:${gatewayip}:${netmask}:${hostname}:eth0:off'
3. setenv bootcmd 'run addip;tftp 81000000 uImage;bootm'
4. set the serverip 10.140.19.128
5. boot

Regards

AnilKumar

Please mark this Forum post as answered via the Verify Answer button below if it helps answer your question. Thanks!

0 ryuichi morishima over 13 years ago in reply to Anil

Prodigy 120 points

Hi Anil,Norman

We set the enviromental values.

TI8148_EVM#printenv
verify=yes
ramdisk_file=ramdisk.gz
loadaddr=0x81000000
script_addr=0x80900000
loadbootscript=fatload mmc 0 ${script_addr} boot.scr
bootscript= echo Running bootscript from MMC/SD to set the ENV...; source ${script_addr}
ethaddr=40:5f:c2:40:f6:c1
ethact=cpsw
ip_addr=10.140.10.43
ip=addr 10.140.10.43
ipserver=10.140.19.128
ipaddr=10.140.10.43
gateway=10.140.104.21
hostname=dm8148
dnsip=10.207.104.101
gatewayip=10.140.104.21
nfsserver=10.140.19.128
dnsip2=10.202.104.4
netmask=255.255.0.0
bootdelay=4
baudrate=115200
oldbootargs=console=ttyO0 115200n8 rootwait rw mem=256M earlyprintk notifyk.vpssm3_sva=0xBF900000 vram=50M ti814xfv.vram0:16M,2:6Mroot=/dev/nfs nfsroot=10.140.19.128:/home/top10015/targetfs ip=10.140.10.43:10.140.19.128:10.140.104.21:255.255.0.0:dm8148:eth0:off
autoload=no
oldserverip=10.140.19.128
oldbootfile=uImage-dm814x-evm.bin
bootfile=uImage-dm814x-evm.bin
oldbootcmd=setenv serverip 10.140.19.128;tftpboot;bootm
nfsroot=10.140.19.128:/home/top10015/targetfs ip=10.140.10.43:10.140.19.128:10.140.104.21:255.255.0.0:dm8148:eth0:off
serverip=10.140.19.128
rootpath=/home/top10015/targetfs
bootcdm=run addip;tftp 81000000 uImage;boot
stdin=serial
stdout=serial
stderr=serial
addip=setenv bootargs console=ttyO0,115200n8 root=/dev/nfs nfsroot=10.140.19.128:/home/top10015/targetfs,nolock rw mem=128M earlyprintk rootdelay=4 ip=10.140.10.43:10.140.19.128:10.140.104.21:255.255.0.0:dm8148:eth0:off
bootcmd=run addip;tftp 81000000 uImage;bootm
the=serverip 10.140.19.128
bootargs=console=ttyO0,115200n8 root=/dev/nfs nfsroot=10.140.19.128:/home/top10015/targetfs,nolock rw mem=128M earlyprintk rootdelay=4 ip=10.140.10.43:10.140.19.128:10.140.104.21:255.255.0.0:dm8148:eth0:off

Environment size: 1697/8188 bytes

We enterted printenv command and the results are below

TI8148_EVM#boot
link up on port 0, speed 100, full duplex
Using cpsw device
TFTP from server 10.140.19.128; our IP address is 10.140.10.43
Filename 'uImage'.
Load address: 0x81000000
Loading: T T T T T T T T T T T T T T T T T T T T
Retry count exceeded; starting again
link up on port 0, speed 100, full duplex

uImage locates in the host PC folder:/tftpboot.
How can we check whether tftp server is pointing tftpboot?

We check the tftp and nfs running.

top10015@top10015:~$ chkconfig --list nfs-kernel-server tftp
nfs-kernel-server         0:off 1:off 2:on   3:on   4:on   5:on   6:off
xinetd based services:
        tftp:               on

Do we need any other settings for tftp and nfs?

Regards

Ryuichi

0 Norman Wong over 13 years ago in reply to ryuichi morishima

Guru 26430 points

To check the TFTP server, try to TFTP the file uImage from some other machine that is not the target nor the server. For example, from a Windows machine:
tftp -i 10.140.19.128 get uImage
I can't remember the syntax from a Linux machine.
To check the network connectivity, try the ping command in U-Boot:
ping 10.140.19.128
If you have a DHCP server, you can also try the dhcp command. DO NOT saveenv after that command. If dhcp is successful, a lot of envrionment variables will get overwritten.

Odd thing is that in some of your posts, the Linux kernel must have be loaded into memory at 81000000. Are those SD Card bootups?

There appear to be a lot of mistyped U-Boot environment variables. Confusing. Might be possible to remove those that are not used? Use setenv with no value to remove variable.

Otherwise the U-Boot environment variables look good. This is one of the few times that I have seen such large subnet, ie 255.255.0.0. Check you network cables. Check for a Link LED on the target and the network switch. Is the MAC address unique on your subnet? Is the network switch full duplex?

Some U-Boot Reference
http://www.denx.de/wiki/view/DULG/TFTPTimeout
http://www.denx.de/wiki/view/DULG/UBootCmdGroupEnvironment
http://www.denx.de/wiki/view/DULG/UBootEnvVariables

0 ryuichi morishima over 13 years ago in reply to Norman Wong

Prodigy 120 points

Hi,

We were able to boot the kernel over the tftp

But the boot hangs.

The teminal displays below:

TI8148_EVM#boot
link up on port 0, speed 100, full duplex
Using cpsw device
TFTP from server 10.140.10.207; our IP address is 10.140.10.43
Filename 'uImage'.
Load address: 0x81000000
Loading: #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         ###############################################
done
Bytes transferred = 2570084 (273764 hex)
## Booting kernel from Legacy Image at 81000000 ...
   Image Name:   Linux-2.6.37
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2570020 Bytes = 2.5 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 (top10015@top10015) (gcc version 4.3.3 (Sourcery G++ Lite 2
009q1-203) ) #1 Thu Jan 19 14:13:13 JST 2012
CPU: ARMv7 Processor [413fc082] revision 2 (ARMv7), cr=10c53c7f
CPU: VIPT nonaliasing data cache, VIPT aliasing instruction cache
Machine: ti8148evm
bootconsole [earlycon0] enabled
reserved size = 52428800 at 0x0
FB: Reserving 52428800 bytes SDRAM for VRAM
Memory policy: ECC disabled, Data cache writeback
OMAP chip is TI8148 2.0
Built 1 zonelists in Zone order, mobility grouping on. Total pages: 19712
Kernel command line: console=ttyO0,115200n8 root=/dev/nfs nfsroot=10.140.10.207:
/home/top10015/targetfs,nolock rw mem=128M earlyprintk rootdelay=4 ip=10.140.10.
43:10.140.10.207:10.140.104.21:255.255.0.0:dm8148:eth0:off
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: 78MB = 78MB total
Memory: 73200k/73200k available, 57872k reserved, 0K highmem
Virtual kernel memory layout:
    vector : 0xffff0000 - 0xffff1000   (   4 kB)
    fixmap : 0xfff00000 - 0xfffe0000   ( 896 kB)
    DMA     : 0xffc00000 - 0xffe00000   (   2 MB)
    vmalloc : 0xc8800000 - 0xf8000000   ( 760 MB)
    lowmem : 0xc0000000 - 0xc8000000   ( 128 MB)
    pkmap   : 0xbfe00000 - 0xc0000000   (   2 MB)
    modules : 0xbf000000 - 0xbfe00000   ( 14 MB)
      .init : 0xc0008000 - 0xc003a000   ( 200 kB)
      .text : 0xc003a000 - 0xc04de000   (4752 kB)
      .data : 0xc04de000 - 0xc0526300   ( 289 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 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
registered ti814x_vpss device
registered TI814x on-chip HDMI device
NOR: Can't request GPMC CS
registered ti81xx_vidout device
Debugfs: Only enabling/disabling deep sleep and wakeup timer is supported now
Registered ti81xx_fb device
ti81xx_pcie: Invoking PCI BIOS...
ti81xx_pcie: Setting up Host Controller...
ti81xx_pcie: Register base mapped @0xc8820000
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
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
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-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 c881e000 using DMA, IRQ 18
musb-hdrc musb-hdrc.1: dma type: dma-cppi41
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 c8826800 using DMA, IRQ 19
NET: Registered protocol family 2
IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
TCP established hash table entries: 4096 (order: 3, 32768 bytes)
TCP bind hash table entries: 4096 (order: 2, 16384 bytes)
TCP: Hash tables configured (established 4096 bind 4096)
TCP reno registered
UDP hash table entries: 256 (order: 0, 4096 bytes)
UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
NET: Registered protocol family 1
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
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 142
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
NAND device: Manufacturer ID: 0x2c, Chip ID: 0xca (Micron )
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
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 adapter
s
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/i2
c-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
usbcore: registered new interface driver snd-usb-audio
asoc: tlv320aic3x-hifi <-> davinci-mcasp.2 mapping ok
ALSA device list:
#0: TI81XX EVM
TCP cubic registered
NET: Registered protocol family 17
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:40:f6:c1
omap_rtc omap_rtc: setting system clock to 2000-01-01 00:00:00 UTC (946684800)
mmc0: new high speed SDHC card at address e624
mmcblk0: mmc0:e624 SD08G 7.40 GiB
mmcblk0: p1 p2 p3

CPSW phy found : id is : 0x4dd074

CPSW phy found : id is : 0x4dd074
IP-Config: Complete:
     device=eth0, addr=10.140.10.43, mask=255.255.0.0, gw=10.140.104.21,
     host=dm8148, domain=, nis-domain=(none),
     bootserver=10.140.10.207, rootserver=10.140.10.207, rootpath=
Waiting 4sec before mounting root device...
PHY: 0:01 - Link is Up - 0/Half
PHY: 0:01 - Link is Down
PHY: 0:00 - Link is Up - 100/Full
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; here are the available partitions:
1f00             128 mtdblock0 (driver?)
1f01            2304 mtdblock1 (driver?)
1f02             128 mtdblock2 (driver?)
1f03            4352 mtdblock3 (driver?)
1f04          204928 mtdblock4 (driver?)
1f05           50304 mtdblock5 (driver?)
b300         7761920 mmcblk0 driver: mmcblk
b301           40131 mmcblk0p1 00000000-0000-0000-0000-000000000mmcblk0p1
b302          883575 mmcblk0p2 00000000-0000-0000-0000-000000000mmcblk0p2
b303         6835657 mmcblk0p3 00000000-0000-0000-0000-000000000mmcblk0p3
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(2,0)
Backtrace:
[<c0048b70>] (dump_backtrace+0x0/0x110) from [<c039dac0>] (dump_stack+0x18/0x1c)
r7:c4b39000 r6:00000000 r5:c002d9cc r4:c0526a90
[<c039daa8>] (dump_stack+0x0/0x1c) from [<c039db24>] (panic+0x60/0x17c)
[<c039dac4>] (panic+0x0/0x17c) from [<c0009258>] (mount_block_root+0x1e0/0x220)
r3:00000000 r2:00000000 r1:c4825f58 r0:c04613ac
[<c0009078>] (mount_block_root+0x0/0x220) from [<c0009344>] (mount_root+0xac/0xc
c)
[<c0009298>] (mount_root+0x0/0xcc) from [<c00094d4>] (prepare_namespace+0x170/0x
1d4)
r4:c0526364
[<c0009364>] (prepare_namespace+0x0/0x1d4) from [<c0008784>] (kernel_init+0x114/
0x154)
r5:c0008670 r4:c0526300
[<c0008670>] (kernel_init+0x0/0x154) from [<c006e694>] (do_exit+0x0/0x5e4)
r5:c0008670 r4:00000000

We missed the setting of nfs?

Regards.

Ryuichi

0 ryuichi morishima over 13 years ago in reply to Norman Wong

Prodigy 120 points

Hi,

We were able to boot the kernel over the tftp

But the boot hangs.

The teminal displays below:

We missed the setting of nfs?

I8148_EVM#printenv
verify=yes
ramdisk_file=ramdisk.gz
loadaddr=0x81000000
script_addr=0x80900000
loadbootscript=fatload mmc 0 ${script_addr} boot.scr
bootscript= echo Running bootscript from MMC/SD to set the ENV...; source ${scri
pt_addr}
ethaddr=40:5f:c2:40:f6:c1
ethact=cpsw
gateway=10.140.104.21
hostname=dm8148
dnsip=10.207.104.101
gatewayip=10.140.104.21
dnsip2=10.202.104.4
netmask=255.255.0.0
bootdelay=4
baudrate=115200
oldbootargs=console=ttyO0 115200n8 rootwait rw mem=256M earlyprintk notifyk.vpssm3_sva=0xBF900000 vram=50M ti814xfv.vram0:16M,2:6Mroot=/dev/nfs nfsroot=10.140.19.128:/home/top10015/targetfs ip=10.140.10.43:10.140.19.128:10.140.104.21:255.255.0.0:dm8148:eth0:off
autoload=no
oldserverip=10.140.19.128
bootfile=uImage-dm814x-evm.bin
rootpath=/home/top10015/targetfs
bootcmd=run addip;tftp 81000000 uImage;bootm
ipaddr=10.140.10.43
serverip=10.140.10.207
bootargs=console=ttyO0,115200n8 root=/dev/nfs nfsroot=10.140.10.207:/home/top10015/targetfs,nolock rw mem=128M earlyprintk rootdelay=4 ip=10.140.10.43:10.140.10.207:10.140.104.21:255.255.0.0:dm8148:eth0:off
addip=setenv bootargs console=ttyO0,115200n8 root=/dev/nfs nfsroot=10.140.10.207:/home/top10015/targetfs,nolock rw mem=128M earlyprintk rootdelay=4 ip=10.140.10.43:10.140.10.207:10.140.104.21:255.255.0.0:dm8148:eth0:off
nfsserver=10.140.10.207
stdin=serial
stdout=serial
stderr=serial

Regards.

Ryuichi

0 Anil over 13 years ago in reply to ryuichi morishima

TI__Expert 6655 points

Hi Ryuichi,

Use these boot args "make sure that all the addresses are proper"

setenv serverip 10.140.10.207
setenv ipaddr 10.140.10.43
setenv nfsserver 10.140.10.207
setenv gatewayip 10.140.104.21
setenv netmask 255.255.0.0
setenv bootargs 'console=ttyO0,115200n8 root=/dev/nfs nfsroot=10.140.19.207:/home/top10015/targetfs,nolock rw mem=128M earlyprintk rootdelay=4'
setenv addip 'setenv bootargs ${bootargs} ip=${ipaddr}:${nfsserver}:${gatewayip}:${netmask}:${hostname}:eth0:off'
setenv bootcmd 'run addip;tftp 81000000 uImage;bootm'
saveenv
boot

Regards

AnilKumar

Please mark this Forum post as answered via the Verify Answer button below if it helps answer your question. Thanks!

0 ryuichi morishima over 13 years ago in reply to Anil

Prodigy 120 points

Hi,

We were confirmed the IP address.

I think that they were proper.

TI8148_EVM#printenv
verify=yes
ramdisk_file=ramdisk.gz
loadaddr=0x81000000
script_addr=0x80900000
loadbootscript=fatload mmc 0 ${script_addr} boot.scr
bootscript= echo Running bootscript from MMC/SD to set the ENV...; source ${scri
pt_addr}
ethaddr=40:5f:c2:40:f6:c1
ethact=cpsw
hostname=dm8148
dnsip=10.207.104.101
gatewayip=10.140.104.21
netmask=255.255.0.0
bootdelay=4
baudrate=115200
oldbootargs=console=ttyO0 115200n8 rootwait rw mem=256M earlyprintk notifyk.vpssm3_sva=0xBF900000 vram=50M ti814xfv.vram0:16M,2:6Mroot=/dev/nfs nfsroot=10.140.19.128:/home/top10015/targetfs ip=10.140.10.43:10.140.19.128:10.140.104.21:255.255.0.0:dm8148:eth0:off
autoload=no
oldserverip=10.140.19.128
oldbootfile=uImage-dm814x-evm.bin
bootfile=uImage-dm814x-evm.bin
oldbootcmd=setenv serverip 10.140.19.128;tftpboot;bootm
rootpath=/home/top10015/targetfs
bootcmd=run addip;tftp 81000000 uImage;bootm
ipaddr=10.140.10.43
serverip=10.140.10.207
bootargs=console=ttyO0,115200n8 root=/dev/nfs nfsroot=10.140.10.207:/home/top10015/targetfs,nolock rw mem=128M earlyprintk rootdelay=4 ip=10.140.10.43:10.140.10.207:10.140.104.21:255.255.0.0:dm8148:eth0:off
addip=setenv bootargs console=ttyO0,115200n8 root=/dev/nfs nfsroot=10.140.10.207:/home/top10015/targetfs,nolock rw mem=128M earlyprintk rootdelay=4 ip=10.140.10.43:10.140.10.207:10.140.104.21:255.255.0.0:dm8148:eth0:off
nfsserver=10.140.10.207
stdin=serial
stdout=serial
stderr=serial

We run Ubuntu in VirtualBox on Windows.

Our IPaddresses are

-EVN:10.140.10.43

-Windows:10.140.19.128

-Ubuntu:10.140.10.207

We allocate "serverip" and "nfsserver" to address of Ubuntu.

Regards.

Ryuichi

0 Qmax over 13 years ago in reply to ryuichi morishima

Expert 2280 points

Check your NFS setup:

- rootfs must be in /home/top10015/targetfs folder on Ubuntu virtual machine
- NFS server must be running on Ubuntu, and that folder exported (look at /etc/exports)
- look at NFS network packets (with wireshark) to see what happens between NFS client and server

Regards, Max

0 Norman Wong over 13 years ago in reply to ryuichi morishima

Guru 26430 points

These lines look odd. The network appears to be renegotiating at the last moment:

Waiting 4sec before mounting root device...
PHY: 0:01 - Link is Up - 0/Half
PHY: 0:01 - Link is Down
PHY: 0:00 - Link is Up - 100/Full

Perhaps try a longer rootdelay. Maybe rootdelay=10. You would get timeout errors if the NFS server is reachable but is not setup correctly. Since TFTP to the same server worked from U-Boot, we can assume the network is connected properly?

0 Mugunthan V N over 13 years ago in reply to Norman Wong

TI__Intellectual 2750 points

PHY: 0:01 - Link is Up - 0/Half
PHY: 0:01 - Link is Down
PHY: 0:00 - Link is Up - 100/Full

These lines are proper, this is the first time CPSW driver is negotiating the Phy's link. So no issues with the deivce. Can you check the NFS server setting. You can also verify the NFS server by mounting the targetfs to different Linux PC and by navigating through the targetfs file system.

Also try to capture packets in NFS server machine using wireshark whether any packets from the device to the NFS server

with regards

Mugunthan V N

0 ryuichi morishima over 13 years ago in reply to Norman Wong

Prodigy 120 points

Hi,

We were able to run the kernerl via the TFTP.

Thank you.

Regards,

Ryuichi

0 Manisha Kalita over 13 years ago in reply to ryuichi morishima

Prodigy 70 points

Hi Ryuichi,

I am currently facing the same issue while trying to boot DM814x via TFTP from a host-linux m/c.

It is stuck in

VFS: Unable to mount root fs via NFS, trying floppy.
VFS: Cannot open root device "nfs" or unknown-block(2,0)

Both the board & linux m/c are having static IP.

Can you please let me know how you solved the same?

I checked the NFS server is running properly in the linux host m/c.

Thanks in advance,

Manisha.

0 Krunal Patil over 13 years ago in reply to Manisha Kalita

Genius 3120 points

Hi Manish,

From the behaviour you mentioned it seems, your filesystem is unable to mount from NFS.

Make sure NFS server is running on your host machine.
Did you set your filesystem path in /etc/exports of host machine? If not, set below is the example and export them using "exportfs -a" or restarting the nfs service.

/etc/exportfs extry example:

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

Also, above doesn't work for you post bootargs you are using.

Regards,

Krunal

0 Manisha Kalita over 13 years ago in reply to Krunal Patil

Prodigy 70 points

Hi Krunal,

Thanks for the response.

I updated rootpath today in the morning with setenv; & currently I am out of that mount problem but stuck in the following part.

####################################################################################

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:40:44:59
omap_rtc omap_rtc: setting system clock to 2000-01-01 00:00:00 UTC (946684800)
mmc0: new high speed SDHC card at address e624
mmcblk0: mmc0:e624 SD08G 7.40 GiB
mmcblk0: p1 p2 p3

CPSW phy found : id is : 0x4dd074

CPSW phy found : id is : 0x4dd074
IP-Config: Complete:
device=eth0, addr=192.168.10.1, mask=255.255.254.0, gw=192.168.10.10,
host=harris, domain=, nis-domain=(none),
bootserver=192.168.10.2, rootserver=192.168.10.2, rootpath=
Waiting 8sec before mounting root device...
PHY: 0:01 - Link is Up - 0/Half
PHY: 0:01 - Link is Down
PHY: 0:00 - Link is Up - 100/Full
VFS: Mounted root (nfs filesystem) on device 0:14.
devtmpfs: mounted
Freeing init memory: 200K
/bin/sh: can't open nolock
Kernel panic - not syncing: Attempted to kill init!
Backtrace:
[<c0048b70>] (dump_backtrace+0x0/0x110) from [<c039dac0>] (dump_stack+0x18/0x1c)
r7:c4822000 r6:c4822000 r5:00094e9c r4:c0526a90
[<c039daa8>] (dump_stack+0x0/0x1c) from [<c039db24>] (panic+0x60/0x17c)
[<c039dac4>] (panic+0x0/0x17c) from [<c006e708>] (do_exit+0x74/0x5e4)
r3:c04f8390 r2:c4825f38 r1:c48220fc r0:c046ca6e
[<c006e694>] (do_exit+0x0/0x5e4) from [<c006ecfc>] (do_group_exit+0x84/0xb4)
[<c006ec78>] (do_group_exit+0x0/0xb4) from [<c006ed44>] (sys_exit_group+0x18/0x20)
r5:00094e9c r4:00094ec0
[<c006ed2c>] (sys_exit_group+0x0/0x20) from [<c0044da0>] (ret_fast_syscall+0x0/0x30)

##################################################################################

Setup:

I have connected my board & Host m/c in an isolated NW and gave the static IP to both of them as 192.168.10.1 & 192.168.10.2 respectively

I checked NFS server in the host m/c using rpcinfo -p command and I could see nfs running for udp & tcp.

As for the /etc/exports; I could see that I have the entry as

/home/harris/targetfs *(rw,no_root_squash,no_all_squash,sync)

All the env params are as follows:

#printenv

baudrate=115200

verify=yes

bootfile=uImage

ramdisk_file=ramdisk.gz

loadaddr=0x81000000

script_addr=0x80900000

loadbootscript=fatload mmc 0 ${script_addr} boot.scr

bootscript= echo Running bootscript from MMC/SD to set the ENV...; source ${script_addr}

stdin=serial

stdout=serial

stderr=serial

ethaddr=40:5f:c2:40:44:59

ethact=cpsw

bootdelay=4

autoload=no

hostname=harris

ipaddr=192.168.10.1

nfsserver=192.168.10.2

serverip=192.168.10.2

netmask=255.255.254.0

gatewayip=192.168.10.10

addip=setenv bootargs ${bootargs} ip=${ipaddr}:${nfsserver}:${gatewayip}:${netmask}:${hostname}:eth0:off

bootcmd=run addip;tftp 81000000 uImage;bootm

rootpath=/home/harris/targetfs

bootargs=console=ttyO0,115200n8 root=/dev/nfs nfsroot=192.168.10.2:/home/harris/targetfs, nolock rw mem=256M,earlyprintk rootdelay=8 ip=192.168.10.1:192.168.10.2:192.168.10.10:255.255.254.0:harris:eth0:off

Environment size: 869/8188 bytes

Interestingly, I found a different error for 1 time, with the same environment variables as follows. However, after running 2/3 times more, I found the error for nolock continuously. So I did not check the following error in details.

###########################################################

CPSW phy found : id is : 0x4dd074

IP-Config: Complete:

device=eth0, addr=192.168.10.1, mask=255.255.254.0, gw=192.168.10.10,

host=harris, domain=, nis-domain=(none),

bootserver=192.168.10.2, rootserver=192.168.10.2, rootpath=

Waiting 4sec before mounting root device...

PHY: 0:01 - Link is Up - 0/Half

PHY: 0:01 - Link is Down

PHY: 0:00 - Link is Up - 100/Full

VFS: Mounted root (nfs filesystem) on device 0:14.

devtmpfs: mounted

Freeing init memory: 200K

/bin/sh:Acan't access tty; job control turned off

#######################################################

Let me know if I am missing something somewhere.

Thanks in advance for help.

Manisha.

0 Krunal Patil over 13 years ago in reply to Manisha Kalita

Genius 3120 points

Hi,

Seems like it is not able to find init inside your filesystem. This might be because of corrupted filesystem.

Try below:

Explicitly pass init process in bootargs: "init=/sbin/init"
Extract prebuild filesystem available insize ezsdk package.

Regards,

Krunal

0 Qmax over 13 years ago in reply to Manisha Kalita

Expert 2280 points

Env var bootargs sounds nok. You posted:

bootargs=console=ttyO0,115200n8 root=/dev/nfs nfsroot=192.168.10.2:/home/harris/targetfs, nolock rw mem=256M,earlyprintk rootdelay=8

Try remove space before nolock, it is an option of nfsroot boot parameter so should be: nfsroot=192.168.10.2:/home/harris/targetfs,nolock.

I suppose also should be mem=256M earlyprintk.

Regards, Max

0 Manisha Kalita over 13 years ago in reply to Qmax

Prodigy 70 points

Hi Max,

Yes!! Removing space before nolock solved the problem. Thank you very much :-)

Now NFS is mounted and I can access the host m/c & tried executing the helloworld too!!

However, I have 2 doubts. Excuse me if it sounds too novice

1. Before the prompt; I see the following message

devtmpfs: mounted
Freeing init memory: 200K
/bin/sh: can't aã; job control turned off

I did not understand this.

2. Also, after booting from tftp; do not we expect to see anything on the display?

Thanks again,

Manisha.

0 Qmax over 13 years ago in reply to Manisha Kalita

Expert 2280 points

Everybody is a novice before being something else (if ever).

1) Sounds not good: what do you see after the "turned off" line? Init scripts should be run, are they? Check if exported file system is corrupted. Check also serial console configuration. The prompt you got after that is a "fully-functional" shell or something "basic"?

2) I do not use DM814x so cannot give exact answer, but I suppose it should work as booting in other ways. But look at first issue: if init scripts have not been run, a lot of initialization steps are missing, so system won't work as expected.

Max

0 Manisha Kalita over 13 years ago in reply to Qmax

Prodigy 70 points

Thanks Max for the response.

a) what do you see after the "turned off" line?

- After "/bin/sh: can't accÍ; job control turned off"; I could see the command prompt.

b) Init scripts should be run, are they?

- Did not see anything related to init script.

c) Check if exported file system is corrupted.

- When I did 'ls' its showing the files present in rootpath (which I set to /home/harris/targetfs). Also, I tried a basic helloworld program and compiled with the EZSDK provided cross-compiler and then executed in the board.

d) Check also serial console configuration.

- Did not get where to check serial console configuration

e) . The prompt you got after that is a "fully-functional" shell or something "basic"?

- it looks basic as followis

######################################

VFS: Mounted root (nfs filesystem) on device 0:14.
devtmpfs: mounted
Freeing init memory: 200K
/bin/sh: can't accå; job control turned off
/ #
/ # ls
bin dev home linuxrc mnt proc srv tmp
boot etc lib media opt sbin sys usr

/ # pwd
/

/ # cd home/
/home # ls
root work_dir
/home # cd work_dir/
/home/work_dir # ls
a.c a.out helloworld helloworld.c makefile
/home/work_dir #

###################################

One more thing, I have not updated/modified the kernel & used it as it was provided (uImage).

Is there anything to be done specifically to run init script?

Thanks,

Manisha.

Processors

Processors forum

Network connection