ep440xs board boot problem
Hello, All, I am new to the list. I am still newbie to embedded linux. I have bought an ep440xs board which is similar to sequoia board. u-boot is working. I am trying to make it run linux. I have the following problems and need your help. Thank you very much: I am using linux kernel 2.6.30.4. I encounter 2 problems: 1. After console_init() is called inside start_kernel(), the console starts printing garbage like: Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled serial8250.0: ttyS0 at MMIO 0x1ef600300 (irq = 16) is a 16550A �� � �� �. 2. It pakics when mounting the root file system(NFS): (gdb) bt #0 panic (fmt=0xc0290e94 "VFS: Unable to mount root fs on %s") at kernel/panic.c:70 #1 0xc02d8ce0 in mount_block_root (name=0xc0290de4 "/dev/root", flags=0x8001) at init/do_mounts.c:272 #2 0xc02d9084 in prepare_namespace () at init/do_mounts.c:415 #3 0xc02d81ec in kernel_init (unused=) at init/main.c:885 #4 0xc000de60 in kernel_thread () There is a patch for Sequoia board to delete /chosen part in sequoia.dts, is /chosen required? Allan ___ Linuxppc-dev mailing list Linuxppc-dev@lists.ozlabs.org https://lists.ozlabs.org/listinfo/linuxppc-dev
EP440XS board boot problem(Note:similart to Sequoia)
I resend my message since my last message has wrong coding. I am new to the list. I am still newbie to embedded linux. I have bought an ep440xs board which is similar to sequoia board. u-boot is working. I am trying to make it run linux. I have the following problems and need your help. Thank you very much: I am using linux kernel 2.6.30.4. I encounter 2 problems: 1. After console_init() is called inside start_kernel(), the console starts printing garbage like: Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled serial8250.0: ttyS0 at MMIO 0x1ef600300 (irq = 16) is a 16550A �� � �� �. 2. It pakics when mounting the root file system(NFS): (gdb) bt #0 panic (fmt=0xc0290e94 "VFS: Unable to mount root fs on %s") at kernel/panic.c:70 #1 0xc02d8ce0 in mount_block_root (name=0xc0290de4 "/dev/root", flags=0x8001) at init/do_mounts.c:272 #2 0xc02d9084 in prepare_namespace () at init/do_mounts.c:415 #3 0xc02d81ec in kernel_init (unused=) at init/main.c:885 #4 0xc000de60 in kernel_thread () There is a patch for Sequoia board to delete /chosen part in sequoia.dts, is /chosen required? Allan ___ Linuxppc-dev mailing list Linuxppc-dev@lists.ozlabs.org https://lists.ozlabs.org/listinfo/linuxppc-dev
Re: EP440XS board boot problem(Note:similart to Sequoia)
Hello, Mr Denk, Thank you for your help. My answer to your questions are between the lines. Attached is the dts file I use. Best regards, Allan - Original Message From: Wolfgang Denk To: Allan Wang Cc: linuxppc-dev@lists.ozlabs.org Sent: Tue, December 1, 2009 6:10:22 PM Subject: Re: EP440XS board boot problem(Note:similart to Sequoia) Dear Allan Wang, In message <401793.31718...@web52903.mail.re2.yahoo.com> you wrote: > > I am new to the list. I am still newbie to embedded linux. I have > bought an ep440xs board which is similar to sequoia board. u-boot is > working. I am trying to make it run linux. I have the following > problems and need your help. Thank you very much: Which exact version of U-Boot are you running on this board? => version U-Boot 1.1.6 (Oct 25 2009 - 13:26:41) I guess this is a out-of-tree port, i. e. not part of the mainline U-Boot repository - so are you sure that device tree support is enabled in your version of U-Boot? The device tree is not enabled in u-boot. I am building cuImage, so the device tree is supported in kernel(2.6.30.4). > > I am using linux kernel 2.6.30.4. I encounter 2 problems: > 1. After console_init() is called inside start_kernel(), the console starts > printing garbage like: > Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled > serial8250.0: ttyS0 at MMIO 0x1ef600300 (irq = 16) is a 16550A > ������������������������������ ... What is your exact boot command? I tftp the cuImage to address 0x20 and bootm to boot. Which boot arguments do you pass to the kernel? bootargs=$(bootargs) console=ttyS0,$(baudrate) What is ytour console baud rate in U-Boot, and what sort of "console=" boot argument do you pass to the Linux kernel? The u-boot sets it to 115.2k. the dts file is set to 115.2k. Here is the boot parameter: baudrate=115200 What does your device tree look like? I attached my dts file. > 2. It pakics when mounting the root file system(NFS): > (gdb) bt > #0 panic (fmt=0xc0290e94 "VFS: Unable to mount root fs on %s") So what is the "%s" argument here? Which sort of root file system are you trying to mount - NFS, ramdisk, UBIFS, ... ? I try to use NFS for the root file system. Best regards, Wolfgang Denk -- DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: w...@denx.de "He only drinks when he gets depressed." "Why does he get depressed?" "Sometimes it's because he hasn't had a drink." - Terry Pratchett, _Men at Arms_ ___ Linuxppc-dev mailing list Linuxppc-dev@lists.ozlabs.org https://lists.ozlabs.org/listinfo/linuxppc-dev
Re: EP440XS board boot problem(Note:similart to Sequoia)
Hello, Mr. Denk,
I forgot to give you the uboot printenv output.
=> printenv
bootcmd=run flash_self
bootdelay=5
baudrate=115200
loads_echo=1
preboot=run setup_phys;echo;echo Type "run flash_nfs" to mount root filesystem
over NFS;echo
netdev=eth0
hostname=ep440xs
nfsargs=setenv bootargs root=/dev/nfs rw nfsroot=$(serverip):$(rootpath)
ramargs=setenv bootargs ramdisk=65536 root=/dev/ram rw
addip=setenv bootargs $(bootargs)
ip=$(ipaddr):$(serverip):$(gatewayip):$(netmask):$(hostname):$(netdev):off
panic=1
addtty=setenv bootargs $(bootargs) console=ttyS0,$(baudrate)
flash_nfs=run nfsargs addip addtty;bootm $(kernel_addr)
flash_self=run ramargs addip addtty;bootm $(kernel_addr) $(ramdisk_addr)
net_nfs=tftp 20 $(bootfile);run nfsargs addip addtty;bootm
kernel_addr=fe00
ramdisk_addr=fe18
load=tftp 0x20 u-boot.bin
update=protect off 0xfff6 0x;era 0xfffa 0x;cp.b
0x20 fffa 6
upd=run load;run update
usbact=hostdev
fixedip=setenv bootargs $(bootargs)
ip=$(ipaddr):$(serverip):$(gatewayip):$(netmask):$(hostname):$(netdev):off
panic=1
dhcp=setenv bootargs $(bootargs) ip=dhcp
initphy=mii w ${phy} 14 e3;mii w ${phy} 18 4101;mii w ${phy} 9 e00;mii w ${phy}
4 1e1;mii w ${phy} 0 9140;mii w ${phy} 0 1140
setup_phys=setenv phy 0;run initphy;setenv phy 1;run initphy;setenv phy
progee=mw 0x10 0x87788252;mw 0x14 0x0957a030;mw 0x18 0x40082350;mw
0x1c 0x0d05;eeprom write 0x54 0x10 0x0 0x10
diags=cp.b 0xFFF4 0x4 0x2;go 0x40004
dhcp_user-class-id=u-boot_test
rootpath=/opt/ppc/ppc_4xx
bootfile=cuImage.ep440xs
ipaddr=192.168.0.201
netmask=255.255.255.0
ethaddr=00:01:ec:01:12:83
eth1addr=00:01:ec:81:12:83
ethact=ppc_4xx_eth0
gateway=192.168.0.1
bootargs=$(bootargs) console=ttyS0,$(baudrate)
serverip=192.168.0.196
gatewayip=192.168.0.1
stdin=serial
stdout=serial
stderr=serial
ver=U-Boot 1.1.6 (Oct 25 2009 - 13:26:41)
Thanks,
Allan
___
Linuxppc-dev mailing list
Linuxppc-dev@lists.ozlabs.org
https://lists.ozlabs.org/listinfo/linuxppc-dev
/dev does not have the devices I have configured with initramfs as my root file system
Hello, All,
Happy New Year to everyone!
I am running ppc440epx board which is similar Sequoia board. I have configured
a I2C RTC device. From the console debug message, it is working, but I do not
see /dev/rtc0 file. My kernel version is 2.6.30.4. I use initramfs as my root
file system. Here is my initramfs.txt:
dir /dev 755 0 0
dir /bin 755 1000 1000
dir /proc 755 0 0
slink /bin/sh busybox 777 0 0
file /bin/busybox /home/awang/proj/linux-2.6.30.4/usr/busybox 755 0 0
dir /sys 755 0 0
dir /usr 755 0 0
dir /usr/bin 755 0 0
dir /usr/sbin 755 0 0
dir /sbin 755 0 0
dir /mnt 755 0 0
dir /etc 755 0 0
dir /var 755 0 0
file /init /home/awang/proj/linux-2.6.30.4/usr/init.sh 755 0 0
Here is my init.sh:
#!/bin/sh
/bin/busybox echo " "
/bin/busybox echo "Hello, I am alive"
busybox mkdir /mnt/flash
busybox mount -t proc /proc /proc
busybox mount -t sysfs none /sys
busybox mount -t jffs2 mtd2 /mnt/flash
busybox sleep 2
/bin/busybox --install -s
#start a shell
ifconfig eth0 192.168.0.201
/bin/sh
Here is my configurations:
RTC kernel configuration:
CONFIG_RTC_LIB=y
CONFIG_RTC_CLASS=y
CONFIG_RTC_HCTOSYS=y
CONFIG_RTC_HCTOSYS_DEVICE="rtc0"
CONFIG_RTC_DEBUG=y
#
# RTC interfaces
#
CONFIG_RTC_INTF_SYSFS=y
CONFIG_RTC_INTF_PROC=y
CONFIG_RTC_INTF_DEV=y
dts configuration:
IIC0: i...@ef600700 {
#address-cells = <1>;
#size-cells = <0>;
compatible = "ibm,iic-440epx", "ibm,iic";
reg = <0xef600700 0x0014>;
interrupt-parent = <&UIC0>;
interrupts = <0x2 0x4>;
r...@68 {
compatible = "stm,m41t80";
reg = <0x68>;
};
eepr...@50 {
compatible = "eeprom";
reg = <0x50>;
};
eepr...@54 {
compatible = "eeprom";
reg = <0x54>;
};
};
The debug messages:
i2c /dev entries driver
rtc-m41t80 1-0068: chip found, driver version 0.05
rtc-m41t80 1-0068: rtc core: registered m41t80 as rtc0
ibm-iic 1ef600700.i2c: using standard (100 kHz) mode
TCP cubic registered
NET: Registered protocol family 17
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
TIPC: Activated (version 1.6.4 compiled Jan 3 2010 12:21:35)
NET: Registered protocol family 30
TIPC: Started in single node mode
rtc-m41t80 1-0068: setting system clock to 2010-01-03 19:43:06 UTC (1262547786)
I have struggled for a few days. Thank you very much.
Allan
___
Linuxppc-dev mailing list
Linuxppc-dev@lists.ozlabs.org
https://lists.ozlabs.org/listinfo/linuxppc-dev
