[Ltib] RE: Linux 2.6.34 for FDI board and NFS issue

[Kevin Wells]

Hi Jorge,

did you create the /dev/ttyTX0 device node in the root filesystem tree?
        mknod ./ltib/rootfs/dev/ttyTX0 c 204 196

That will allow getty to work so you can get your console. You can also try
ssh'ing into the board at the IP address 192.168.100.115.

I'm not sure what to say about the network related issues. Maybe someone else
can offer some suggestions?

thanks,
Kevin


> -----Original Message-----
> From: Jorge A. Castro [mailto:address@hidden
> Sent: Tuesday, September 28, 2010 2:07 PM
> To: address@hidden; Kevin Wells
> Subject: Linux 2.6.34 for FDI board and NFS issue
> 
> Greetings to all in LTIB mailing list!
> 
> For those who don't know, Linux 2.6.34 for the Future Design Inc board
> (or FDI board) with LPC3250 is available and also some upgrades to the
> 2.6.27.8 according to http://www.lpclinux.com/Main/WebHome. Thanks to
> Kevin Well and the guys of LPCLinux.
> 
> Now I'm trying to implement the 2.6.34 version on my FDI3250. I
> configured it similar than the 2.6.27.8 version. It compiled ok, but I
> have problems when mounting the roofs by nfs. Seems that is mounted but
> I got something like:
> 
> rtc-lpc32xx rtc-lpc32xx: setting system clock to 1970-01-01 00:34:55 UTC
> (2095)
> Sending DHCP requests .., OK
> IP-Config: Got DHCP answer from 0.0.0.0, my address is 192.168.100.115
> IP-Config: Complete:
> device=eth0, addr=192.168.100.115, mask=255.255.255.0, gw=192.168.100.50,
> host=192.168.100.115, domain=, nis-domain=(none),
> bootserver=0.0.0.0, rootserver=192.168.100.84, rootpath=
> Warning: unable to open an initial console.
> Looking up port of RPC 100003/2 on 192.168.100.84
> Looking up port of RPC 100005/1 on 192.168.100.84
> VFS: Mounted root (nfs filesystem) on device 0:11.
> Freeing init memory: 124K
> nfs: server 192.168.100.84 not responding, still trying
> nfs: server 192.168.100.84 not responding, still trying
> nfs: server 192.168.100.84 OK
> nfs: server 192.168.100.84 OK
> 
> And I never got access to the system. I expirience something like this
> in the past and I fixed with the configuration of bootargs in the u-boot
> with wsize=1500,rsize=1500 parameters to the nfs root, like:
> 
> bootargs=console=ttyTX0,115200n81 root=/dev/nfs
> nfsroot=192.168.100.84:/tftpboot/rootfs,wsize=1500,rsize=1500 rw noinitrd
> ip
> 
> 
> Nevertheless, this is not working now. Kevin, or any one else, have any
> idea what can I be missing? I don't know if a need some especial
> configuration in the u-boot or in the LTIB. Any idea will be welcome,
> because I have spend a lot of time without success.
> 
> Thanks and best regards.
> 
> 
> P.S.: Here I put the entire boot output and the u-boot parameters that I
> have set.
> 
> ---------------------------
> boot output
> ---------------------------
> 
> uboot> FDI3250 Kickstart v1.00
> NAND Flash Initialized
> Running Stage 1 Loader ...
> Using default system configuration
> 
> Future Designs, Inc. DK-xTS-LPC3250 Board
> Build date: Jul 20 2010 17:15:04
> Autoboot in progress, press any key to stop
> 
> 
> U-Boot 2009.03-rc1 (Sep 16 2010 - 09:50:06)
> 
> DRAM: 32 MB
> NAND: 256 MiB
> In: serial
> Out: serial
> Err: serial
> Hit any key to stop autoboot: 0
> HW MAC address: 00:1A:F1:00:00:00
> ENET:auto-negotiation complete#$
> ENET:HALF DUPLEX
> ENET:100MBase
> TFTP from server 192.168.100.84; our IP address is 192.168.100.85
> Filename 'uImage'.
> Load address: 0x80100000
> Loading: #################################################################
> #################################################################
> #################################################################
> #################################################################
> #################################################################
> ###############################################
> done
> Bytes transferred = 1901884 (1d053c hex)
> ## Booting kernel from Legacy Image at 80100000 ...
> Image Name: Linux-2.6.34
> Image Type: ARM Linux Kernel Image (uncompressed)
> Data Size: 1901820 Bytes = 1.8 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.34 (address@hidden) (gcc version 4.1.2) #13 PREEMPT
> Tue Sep 28 14:08:03 CST 2010
> CPU: ARM926EJ-S [41069264] revision 4 (ARMv5TEJ), cr=00053177
> CPU: VIVT data cache, VIVT instruction cache
> Machine: Future Designs board with the LPC3250 Microcontroller
> Memory policy: ECC disabled, Data cache writeback
> Built 1 zonelists in Zone order, mobility grouping on. Total pages: 8128
> Kernel command line: console=ttyTX0,115200n8 root=/dev/nfs rw
> nfsroot=192.168.100.84:/tftpboot/rootfs,wsize=1500,rsize=1500 ethadd
> r=${ethaddr} ip=dhcp init=/sbin/init
> PID hash table entries: 128 (order: -3, 512 bytes)
> Dentry cache hash table entries: 4096 (order: 2, 16384 bytes)
> Inode-cache hash table entries: 2048 (order: 1, 8192 bytes)
> Memory: 32MB = 32MB total
> Memory: 28476k/28476k available, 4292k reserved, 0K highmem
> Virtual kernel memory layout:
> vector : 0xffff0000 - 0xffff1000 ( 4 kB)
> fixmap : 0xfff00000 - 0xfffe0000 ( 896 kB)
> DMA : 0xffc00000 - 0xffe00000 ( 2 MB)
> vmalloc : 0xc2800000 - 0xf0000000 ( 728 MB)
> lowmem : 0xc0000000 - 0xc2000000 ( 32 MB)
> modules : 0xbf000000 - 0xc0000000 ( 16 MB)
> .init : 0xc0008000 - 0xc0027000 ( 124 kB)
> .text : 0xc0027000 - 0xc03a1000 (3560 kB)
> .data : 0xc03a2000 - 0xc03c6e40 ( 148 kB)
> Hierarchical RCU implementation.
> NR_IRQS:96
> Console: colour dummy device 80x30
> Calibrating delay loop... 133.12 BogoMIPS (lpj=665600)
> Mount-cache hash table entries: 512
> CPU: Testing write buffer coherency: ok
> NET: Registered protocol family 16
> LPC32XX unique ID: 00000000000000000000000000000000
> 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
> Switching to clocksource lpc32xx_clksrc
> NET: Registered protocol family 2
> IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
> TCP established hash table entries: 1024 (order: 1, 8192 bytes)
> TCP bind hash table entries: 1024 (order: 0, 4096 bytes)
> TCP: Hash tables configured (established 1024 bind 1024)
> 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)
> JFFS2 version 2.2. (NAND) (SUMMARY) �© 2001-2006 Red Hat, Inc.
> msgmni has been set to 55
> alg: No test for stdrng (krng)
> io scheduler noop registered
> io scheduler deadline registered
> io scheduler cfq registered (default)
> Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
> serial8250.0: ttyS0 at MMIO 0x40090000 (irq = 9) is a 16550A
> lpc32xx_hsuart.0: ttyTX0 at MMIO 0x40014000 (irq = 26) is a lpc32xx_hsuart
> console [ttyTX0] enabled
> brd: module loaded
> loop: module loaded
> NAND device: Manufacturer ID: 0x2c, Chip ID: 0xda (Micron NAND 256MiB
> 3,3V 8-bit)
> Scanning device for bad blocks
> Bad eraseblock 515 at 0x000004060000
> Bad eraseblock 593 at 0x000004a20000
> Bad eraseblock 898 at 0x000007040000
> Bad eraseblock 954 at 0x000007740000
> Bad eraseblock 1347 at 0x00000a860000
> Bad eraseblock 1369 at 0x00000ab20000
> Bad eraseblock 1410 at 0x00000b040000
> Creating 4 MTD partitions on "lpc32xx_nand":
> 0x000000000000-0x000000320000 : "fdi3250-boot"
> 0x000000320000-0x000000fe0000 : "fdi3250-uboot"
> 0x000000fe0000-0x0000013e0000 : "fdi3250-kernel"
> 0x0000013e0000-0x000010000000 : "fdi3250-jffs2"
> lpc_mii_bus: probed
> eth0: using RMII interface
> eth0: LPC mac at 0x31060000 irq 29
> eth0: attached PHY driver [Generic PHY] (mii_bus:phy_addr=0:00, irq=-1)
> usbmon: debugfs is not available
> ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
> ISP1301 Vendor ID : 0x04cc
> ISP1301 Product ID : 0x1301
> ISP1301 Version ID : 0x0210
> usb-ohci usb-ohci: at 0xf3120000, irq 0
> usb-ohci usb-ohci: pnx4008 OHCI
> usb-ohci usb-ohci: new USB bus registered, assigned bus number 1
> usb-ohci usb-ohci: irq 59, io mem 0xf3120000
> usb usb1: New USB device found, idVendor=1d6b, idProduct=0001
> usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
> usb usb1: Product: pnx4008 OHCI
> usb usb1: Manufacturer: Linux 2.6.34 ohci_hcd
> usb usb1: SerialNumber: usb-ohci
> hub 1-0:1.0: USB hub found
> hub 1-0:1.0: 2 ports detected
> 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
> rtc-lpc32xx rtc-lpc32xx: rtc core: registered rtc-lpc32xx as rtc0
> i2c /dev entries driver
> PNX4008-WDT: PNX4008 Watchdog Timer: heartbeat 19 sec
> cpuidle: using governor ladder
> cpuidle: using governor menu
> sdhci: Secure Digital Host Controller Interface driver
> sdhci: Copyright(c) Pierre Ossman
> TCP cubic registered
> NET: Registered protocol family 17
> ssp-pl022 dev:ssp0: ARM PL022 driver, device ID: 0x00041022
> pl022: mapped registers from 0x20084000 to c2882000
> CLCD: Okaya 3.5 inch LCD hardware, VGA portrait display
> Console: switching to colour frame buffer device 80x30
> VFP support v0.3: implementor 41 architecture 1 part 10 variant 9 rev 1
> rtc-lpc32xx rtc-lpc32xx: setting system clock to 1970-01-01 00:34:55 UTC
> (2095)
> Sending DHCP requests .., OK
> IP-Config: Got DHCP answer from 0.0.0.0, my address is 192.168.100.115
> IP-Config: Complete:
> device=eth0, addr=192.168.100.115, mask=255.255.255.0, gw=192.168.100.50,
> host=192.168.100.115, domain=, nis-domain=(none),
> bootserver=0.0.0.0, rootserver=192.168.100.84, rootpath=
> Warning: unable to open an initial console.
> Looking up port of RPC 100003/2 on 192.168.100.84
> Looking up port of RPC 100005/1 on 192.168.100.84
> VFS: Mounted root (nfs filesystem) on device 0:11.
> Freeing init memory: 124K
> nfs: server 192.168.100.84 not responding, still trying
> nfs: server 192.168.100.84 not responding, still trying
> nfs: server 192.168.100.84 OK
> nfs: server 192.168.100.84 OK
> nfs: server 192.168.100.84 not responding, still trying
> nfs: server 192.168.100.84 not responding, still trying
> nfs: server 192.168.100.84 OK
> nfs: server 192.168.100.84 OK
> nfs: server 192.168.100.84 not responding, still trying
> nfs: server 192.168.100.84 not responding, still trying
> nfs: server 192.168.100.84 not responding, still trying
> nfs: server 192.168.100.84 OK
> nfs: server 192.168.100.84 OK
> nfs: server 192.168.100.84 not responding, still trying
> nfs: server 192.168.100.84 OK
> nfs: server 192.168.100.84 not responding, still trying
> nfs: server 192.168.100.84 OK
> nfs: server 192.168.100.84 OK
> nfs: server 192.168.100.84 not responding, still trying
> nfs: server 192.168.100.84 not responding, still trying
> nfs: server 192.168.100.84 not responding, still trying
> nfs: server 192.168.100.84 OK
> nfs: server 192.168.100.84 OK
> nfs: server 192.168.100.84 OK
> nfs: server 192.168.100.84 not responding, still trying
> nfs: server 192.168.100.84 not responding, still trying
> nfs: server 192.168.100.84 not responding, still trying
> nfs: server 192.168.100.84 OK
> nfs: server 192.168.100.84 OK
> nfs: server 192.168.100.84 OK
> nfs: server 192.168.100.84 not responding, still trying
> nfs: server 192.168.100.84 not responding, still trying
> nfs: server 192.168.100.84 not responding, still trying
> nfs: server 192.168.100.84 OK
> nfs: server 192.168.100.84 OK
> nfs: server 192.168.100.84 not responding, still trying
> nfs: server 192.168.100.84 OK
> nfs: server 192.168.100.84 not responding, still trying
> nfs: server 192.168.100.84 OK
> nfs: server 192.168.100.84 OK
> nfs: server 192.168.100.84 not responding, still trying
> nfs: server 192.168.100.84 not responding, still trying
> nfs: server 192.168.100.84 not responding, still trying
> nfs: server 192.168.100.84 OK
> nfs: server 192.168.100.84 OK
> nfs: server 192.168.100.84 OK
> nfs: server 192.168.100.84 not responding, still trying
> nfs: server 192.168.100.84 not responding, still trying
> nfs: server 192.168.100.84 OK
> nfs: server 192.168.100.84 OK
> nfs: server 192.168.100.84 not responding, still trying
> nfs: server 192.168.100.84 not responding, still trying
> 
> 
> -------------------------
> u-boot
> -------------------------
> 
> uboot> printenv
> baudrate=115200
> ethaddr=00:1a:f1:00:00:00
> bootcmd=tftpboot; bootm
> bootfile=uImage
> loadaddr=0x80100000
> bootdelay=2
> serverip=192.168.100.84
> ipaddr=192.168.100.85
> gatewayip=192.168.100.50
> netmask=255.255.255.0
> bootargs=console=ttyTX0,115200n81 root=/dev/nfs
> nfsroot=192.168.100.84:/tftpboot/rootfs,wsize=1500,rsize=1500 rw noinitrd
> ip
> =dhcp init=/sbin/init
> stdin=serial
> stdout=serial
> stderr=serial
> 
> Environment size: 394/262140 bytes
> 
> --
> Jorge A. Castro
> Canam-Technology, Inc.