topic Re: MPC8313e-RDB booting problem in Other NXP Products

MPC8313e-RDB booting problem

robindev — Fri, 18 Sep 2009 21:52:40 GMT

Hello,

I am trying to load and run a new linux kernel(the board contains kernel 2.6.20, and i try to boot the one from the BSP iso) on the MPC8313e-RDB (ver 4A, with PPC8313e), but i ran into some problem.

I have used the kernel from the images folder in the ISO. I have set up a TFTP server to load it in the board(in ram). I issue the following commands to load and boot the new kernel:

setenv ethact TSEC1
setenv bootargs root=/dev/ram console=ttyS0,115200
tftp 200000 uImage
tftp 1000000 rootfs.ext2.gz.uboot
tftp 400000 mpc8313erdb.dtb
bootm 200000 1000000 400000

the kernel seems to boots fine,but then suddenly the terminal becomes unresponsive. Most of the time this hapens when i do something with the ethernet controller, like ifconfig or ping(ping does not work, and always hangs the board)

am i doing something wrong?

i tried both ethernet devices

(used run run_vscld1 to load the firmware)

could it be that the mpc8313erdb.dtb is for a different version of the board?

Thanks in advance!

full bootlog fromttyS0:

Hit any key to stop autoboot: 0
=> setenv ethact TSEC1
=> setenv bootargs root=/dev/ram console=ttyS0,115200
=> tftp 200000 uImage
Speed: 100, full duplex
Using TSEC1 device
TFTP from server 192.168.1.11; our IP address is 192.168.1.2
Filename 'uImage'.
Load address: 0x200000
Loading: #################################################################
         #################################################################
         #################################################################
         #################################################################
         ########################################################
done
Bytes transferred = 1617371 (18addb hex)
=> tftp 1000000 rootfs.ext2.gz.uboot
Speed: 100, full duplex
Using TSEC1 device
TFTP from server 192.168.1.11; our IP address is 192.168.1.2
Filename 'rootfs.ext2.gz.uboot'.
Load address: 0x1000000
Loading: #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #########################################
done
Bytes transferred = 3534356 (35ee14 hex)
=> tftp 400000 mpc8313erdb.dtb
Speed: 100, full duplex
Using TSEC1 device
TFTP from server 192.168.1.11; our IP address is 192.168.1.2
Filename 'mpc8313erdb.dtb'.
Load address: 0x400000
Loading: ###
done
Bytes transferred = 12288 (3000 hex)
=> bootm 200000 1000000 400000
## Booting image at 00200000 ...
   Image Name:   Linux-2.6.23
   Created:      2008-12-22   3:22:49 UTC
   Image Type:   PowerPC Linux Kernel Image (gzip compressed)
   Data Size:    1617307 Bytes = 1.5 MB
   Load Address: 00000000
   Entry Point: 00000000
   Verifying Checksum ... OK
   Uncompressing Kernel Image ... OK
## Loading RAMDisk Image at 01000000 ...
   Image Name:   uboot ext2 ramdisk rootfs
   Created:      2008-12-22   3:24:29 UTC
   Image Type:   PowerPC Linux RAMDisk Image (gzip compressed)
   Data Size:    3534292 Bytes = 3.4 MB
   Load Address: 00000000
   Entry Point: 00000000
   Verifying Checksum ... OK
   Booting using flat device tree at 0x400000
   Loading Ramdisk to 07c38000, end 07f96dd4 ... OK
Using MPC8313 RDB machine description
Linux version 2.6.23 (yhh@rock) (gcc version 4.1.2) #1 Mon Dec 22 11:22:46 CST 2008
Found initrd at 0xc7c38000:0xc7f96dd4
console [udbg0] enabled
setup_arch: bootmem
mpc8313_rdb_setup_arch()
Found MPC83xx PCI host bridge at 0x00000000e0008500. Firmware bus number: 0->0
arch: exit
Zone PFN ranges:
DMA             0 ->    32768
Normal      32768 ->    32768
Movable zone start PFN for each node
early_node_map[1] active PFN ranges
    0:        0 ->    32768
Built 1 zonelists in Zone order. Total pages: 32512
Kernel command line: root=/dev/ram console=ttyS0,115200
IPIC (128 IRQ sources) at fdef9700
PID hash table entries: 512 (order: 9, 2048 bytes)
Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
Memory: 122848k/131072k available (3188k kernel code, 8064k reserved, 148k data, 94k bss, 152k init)
Mount-cache hash table entries: 512
NET: Registered protocol family 16

PCI: Probing PCI hardware
Generic PHY: Registered new driver
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
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
checking if image is initramfs...it isn't (no cpio magic); looks like an initrd
Freeing initrd memory: 3451k freed
JFFS2 version 2.2. (NAND) Â© 2001-2006 Red Hat, Inc.
io scheduler noop registered
io scheduler anticipatory registered (default)
io scheduler deadline registered
io scheduler cfq registered
Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing disabled
serial8250.0: ttyS0 at MMIO 0xe0004500 (irq = 18) is a 16550A
console handover: boot [udbg0] -> real [ttyS0]
serial8250.0: ttyS1 at MMIO 0xe0004600 (irq = 19) is a 16550A
RAMDISK driver initialized: 16 RAM disks of 32768K size 1024 blocksize
loop: module loaded
Intel(R) PRO/1000 Network Driver - version 7.3.20-k2-NAPI
Copyright (c) 1999-2006 Intel Corporation.
Gianfar MII Bus: probed
eth0: Gianfar Ethernet Controller Version 1.3-skbr, 04:00:00:00:00:0a
GFAR: SKB Handler initialized at CPU#0(max=32)
eth0: MTU = 1500 (frame size=1526, truesize=1800)
eth0: Running with NAPI enabled
eth0: 64/64 RX/TX BD ring size
eth1: Gianfar Ethernet Controller Version 1.3-skbr, 00:e0:0c:00:7e:21
GFAR: SKB Handler initialized at CPU#0(max=32)
eth1: MTU = 1500 (frame size=1526, truesize=1800)
eth1: Running with NAPI enabled
eth1: 64/64 RX/TX BD ring size
e100: Intel(R) PRO/100 Network Driver, 3.5.23-k4-NAPI
e100: Copyright(c) 1999-2006 Intel Corporation
Marvell 88E1101: Registered new driver
Marvell 88E1112: Registered new driver
Marvell 88E1111: Registered new driver
Marvell 88E1145: Registered new driver
Fixed MDIO Bus: probed
nor: Found 1 x16 devices at 0x0 in 16-bit bank
Amd/Fujitsu Extended Query Table at 0x0040
nor: CFI does not contain boot bank location. Assuming top.
number of CFI chips: 1
cfi_cmdset_0002: Disabling erase-suspend-program due to code brokenness.
RedBoot partition parsing not available
physmap-flash nor: Using OF partition information
Creating 5 MTD partitions on "nor":
0x00000000-0x00100000 : "U-Boot"
0x00100000-0x00300000 : "Kernel"
0x00300000-0x00700000 : "rootfs"
0x00700000-0x00710000 : "DTB"
0x00710000-0x00800000 : "vsc-util"
Freescale eLBC NAND Driver (C) 2006-2007 Freescale
NAND device: Manufacturer ID: 0xec, Chip ID: 0x75 (Samsung NAND 32MiB 3,3V 8-bit)
Scanning device for bad blocks
fsl-elbc fsl-elbc.0: Using OF partition information
Creating 6 MTD partitions on "nand":
0x00000000-0x00100000 : "U-Boot-NAND"
0x00100000-0x00900000 : "JFFS2-NAND"
0x00900000-0x00d00000 : "Ramdisk-NAND"
0x00d00000-0x01d00000 : "Reserve-NAND"
0x01d00000-0x01f00000 : "Kernel-NAND"
0x01f00000-0x02000000 : "DTB-NAND"
mpc83xx_spi.0: MPC83xx SPI Controller driver at 0xc9066000 (irq = 21)
usbmon: debugfs is not available
fsl-ehci fsl-ehci.0: Freescale On-Chip EHCI Host Controller
fsl-ehci fsl-ehci.0: new USB bus registered, assigned bus number 1
fsl-ehci fsl-ehci.0: irq 38, io base 0xe0023000
fsl-ehci fsl-ehci.0: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 1 port detected
Initializing USB Mass Storage driver...
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
i2c /dev entries driver
rtc-ds1307 0-0068: rtc core: registered ds1339 as rtc0
WDT driver for MPC83xx initialized. mode:reset timeout=65535 (25 seconds)
mmc_spi spi28672.0: SD/MMC host mmc0, no DMA, no WP, no poweroff
TCP cubic registered
NET: Registered protocol family 1
NET: Registered protocol family 17
rtc-ds1307 0-0068: setting the system clock to 2000-01-03 00:38:06 (946859886)
RAMDISK: Compressed image found at block 0
VFS: Mounted root (ext2 filesystem) readonly.
Freeing unused kernel memory: 152k init
Setting the hostname to mpc8313erdb
Mounting filesystems
Running sysctl
Setting up networking on loopback device:
Setting up networking on eth0:
Adding static route for default gateway to 192.168.1.1:
Setting nameserver to 192.168.1.1 in /etc/resolv.conf:
Setting up networking on eth1:
Adding static route for default gateway to 192.168.1.1:
Setting nameserver to 192.168.1.1 in /etc/resolv.conf:
Starting inetd:

        Welcome to Freescale Semiconductor Embedded Linux Environment

!!!!! WARNING !!!!!!!

The default password for the root account is: root
please change this password using the 'passwd' command
and then edit this message (/etc/issue) to remove this message

mpc8313erdb login: PHY: 0:01 - Link is Up - 1000/Full
PHY: e0024520:04 - Link is Up - 100/Full

        Welcome to Freescale Semiconductor Embedded Linux Environment

!!!!! WARNING !!!!!!!

The default password for the root account is: root
please change this password using the 'passwd' command
and then edit this message (/etc/issue) to remove this message

mpc8313erdb login: root
Password:
login[809]: root login on `console'

~ # ifconfig eth0 192.168.1.2
~ # ping 192.168.1.11
PING 192.168.1.11 (192.168.1.11): 56 data bytes

this is where the board becomes unresponsive.

Re: MPC8313e-RDB booting problem

abartky — Sat, 19 Sep 2009 11:53:07 GMT

Robindev,

I'm not sure if this will fix the problem but it is worth a try. One thing that was not shown in your trace was your uboot configuration as it was my experience that you had to be real careful about making sure all the environment parameters were setup properly and stored prior to booting.

In particular, one thing that gave me grief was in not setting the ramdisk_size environment variable.

During the normal process of doing an ltib build at the end there is often a message at the end of the build such as this example:

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

Your ramdisk exceeds the old default size of 4096k, you may need to set the command line argument for ramdisk_size in your bootloader allowing 10% free this gives 9504k . For instance, for u-boot:

setenv bootargs root=/dev/ram rw ramdisksize=9504

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

This is a warning message you need to take seriously and add the environment variable. If you don't there are cases where linux will load and then crash when you try and run things in that the ramdisk is not large enough to even contain the set of files/programs created in the build process.

I got in the habit of setting the size to 128000 as there was usually still plenty of RAM left over for other things and this gave me enough size to allow most of my test software to be built without woring about running out of ramdisk.

Below is my uboot enviroment data I used on my board (this is an excerpt from one of my previous posts at:

http://forums.freescale.com/freescale/board/message?board.id=MCUCOMM&message.id=679#M679 )

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

=> print
flash_nfs=run nfsargs addip addtty;bootm ${kernel_addr}
flash_self=run ramargs addip addtty;bootm ${kernel_addr} ${ramdisk_addr}
net_nfs=tftp 200000 ${bootfile};run nfsargs addip addtty;bootm
load=tftp 100000 uboot_8313
update=protect off fe000000 fe04ffff; era fe000000 fe04ffff; cp.b 100000 fe00000
0 ${filesize}
upd=run load;run update
fdtaddr=400000
fdtfile=mpc8313erdb.dtb
vsc=cp.b fe050000 40000 12000;go 40004
bootcmd=protect on fe050000 fe07ffff;run vsc
ramargs=set bootargs root=/dev/ram rw ramdisk=128000
ethact=TSEC0
mtdids=nor0=nor,nand0=nand
rootpath=/tftpboot/192.168.2.192
filesize=119d
fileaddr=400000
gatewayip=192.168.2.1
netmask=255.255.255.0
ipaddr=192.168.2.192
serverip=192.168.2.129
bootargs=root=/dev/ram rw ramdisk=128000 console=ttyS0,115200
stdin=serial
stdout=serial
stderr=serial

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

Hope this helps,

Alan

Re: MPC8313e-RDB booting problem

robindev — Mon, 21 Sep 2009 19:23:52 GMT

Hi Alan,

I have tried your suggestion, but unfortunately it did not work. I think the downloaded iso is just not suited for the version of the board that I have. Too bad that freescale does not keep all the old board support .iso files available. I ordered a new(recent) board from freescale today, so I hope that the problem is solved that way.

Anyway, thank you very much for your swift and helpful reply! It maybe did not solve this problem, but it is certainly something that otherwise would have become a problem later on.

greets, Robin

Re: MPC8313e-RDB booting problem

robindev — Tue, 22 Sep 2009 18:03:56 GMT

I have put out a support request at freescale to provide me with the image of the correct cd, they provided me the download link within the hour. Now my problems are over. Guess i should have paid more attention to the version numbers... Annyway, thank you for your help!

Greets, Robin

Re: MPC8313e-RDB booting problem

hoverdsp — Sat, 07 Nov 2009 20:05:36 GMT

Robindev,

I guess your problem is you donot run the vsc firmware .As I know ,The TSEC1's is connected to VSC switch and TSEC2 is connected to 88E111.What's more ,under linux ,the ipaddr of the two TSEC cannot be the same netmask.

You can run ifconfig to see the ipaddr of eth0 &eth1. If their netmask is same , you can try ifconfig eth0 down .

If you want to use eth0 under linux ,you must first run the vsc firmware.