LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Embedded & Single-board computer (http://www.linuxquestions.org/questions/linux-embedded-and-single-board-computer-78/)
-   -   Not able run commands on console (http://www.linuxquestions.org/questions/linux-embedded-and-single-board-computer-78/not-able-run-commands-on-console-771679/)

ravi_chobey 11-26-2009 06:00 AM

Not able run commands on console
 
Hi All,

I am able to port and run Embedded linux on my ARM,EP9307 board from cirrus logic.But the problem is that,i am getting the # prompt but i am not able to run any commands on to that.I have properly configured and cross compiled busysbox for that board.Please support me in solving this issue.

Thanks and Regards,
Ravi Chobey

cyent 11-26-2009 07:37 PM

By "not run" do you mean...

* You type away and nothing appears?
* You type a command and you get something like "Bad command"? (Umm. Exactly what do you get?)
* You type a command and nothing happens?
* Does a fierce dog prevent you from approaching the keyboard, hence you can't run any commands? :-)

How are you connecting to the device? Serial port? USB? Ethernet?

Busy box has a built in "help" command.

What happens when you type help?

What happens when you type ls?

What happens when you type
echo $PATH

ravi_chobey 11-27-2009 01:55 AM

hi cyent,

Thx for ur reply,

* You type away and nothing appears?
yes when tried to type command nothing appears on my serial console. Even command I am typing is not getting echoed on terminal
i.e "system is hanged state"

I am connecting my device through serial port "/dev/ttyAM"


Regards,
Ravi

business_kid 11-29-2009 12:01 PM

Quote:

Originally Posted by ravi_chobey (Post 3770190)
I am able to port and run Embedded linux on my ARM,EP9307 board from cirrus logic.

So all this is taking place on an arm based board?

Quote:

Originally Posted by ravi_chobey (Post 3770190)
But the problem is that,i am getting the # prompt but i am not able to run any commands on to that.

Exactly what is unable to run arm code? Are you trying to run arm code on a pc? We cannot see what you are doing - you have to tell us.

I have properly configured and cross compiled busysbox for that board.Please support me in solving this issue.[/QUOTE]

If you know busybox is compiled right, has it all it's libs?

ldd /path/to/busybox

cyent 11-29-2009 03:06 PM

Things to double check (triple check)
* Baud rate / stop bits of embedded device and PC.
* Swap out cable with another. Sad to say, in my experience bad connections are often a problem.
* Does anything appear before the # or just the #? (If something meaningful does appear then it probably isn't baud rate. :0)
* Is that the only serial port on the device?
* Give as much info as possible on versions and config settings you have. You are giving us extremely little to go on here. The probability we solve it with this much info is near zero.
* Swap out arm board with another.
* Swap out arm board with another PC / port on the same PC. Verify comms.

ravi_chobey 12-03-2009 02:18 AM

Hi Cyent,

Thanks for your reply.
I am able to boot linux on my ARM9 board.I am able to type some commands on that board.But after that the system is going into hang state.When i am rebooting the system again,it is giving me CRC error,base address related errors and Freeing init:128 k related error.
I want to know whether it is a software or Firmware related error.

Regards,
Ravi

cyent 12-03-2009 04:10 PM

Copy and paste the full/exact error messages into your replies.

Does it hang after a specific class of commands (eg. accessing a disk device, or network, or particular drive)?

Don't be shy...

The faster you poke at the thing and the more info you give us the better chance we have of helping you.

How are you accessing it? Via serial port? Ethernet?

Can you ping it even after the hang?

What's the output of "dmesg"?

ravi_chobey 12-03-2009 10:12 PM

Dear cyent,

i am not able to ping after hang condition.

i am able to run one or two commands like "ls" and "cd",after that system is coming under hang condition.Please go through the logs:

1> After port and executing:

Using base address 0x00800000 and length 0x00140270
Uncompressing Linux............................................................................................... ....................... done, booting the kernel.
Linux version 2.6.20.4 (root@localhost.localdomain) (gcc version 4.1.1) #1 PREEMPT Wed Nov 11 21:36:34 IST 2009
CPU: ARM920T [41129200] revision 0 (ARMv4T), cr=c0007177
Machine: Cirrus Logic EDB9307A Evaluation Board
Memory policy: ECC disabled, Data cache writeback
CPU0: D VIVT write-back cache
CPU0: I cache: 16384 bytes, associativity 64, 32 byte lines, 8 sets
CPU0: D cache: 16384 bytes, associativity 64, 32 byte lines, 8 sets
Built 1 zonelists. Total pages: 16192
Kernel command line: root=/dev/ram console=ttyAM video=ep93xxfb:vout=0,vmode=2,depth=16
PID hash table entries: 256 (order: 8, 1024 bytes)
Console: colour dummy device 80x30
Dentry cache hash table entries: 8192 (order: 3, 32768 bytes)
Inode-cache hash table entries: 4096 (order: 2, 16384 bytes)
Memory: 32MB 32MB = 64MB total
Memory: 46664KB available (3404K code, 329K data, 128K init)
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
NET: Registered protocol family 16
ep93xx: PLL1 running at 399 MHz, PLL2 at 192 MHz
ep93xx: FCLK 199 MHz, HCLK 99 MHz, PCLK 49 MHz
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: 2048 (order: 1, 8192 bytes)
TCP bind hash table entries: 1024 (order: 0, 4096 bytes)
TCP: Hash tables configured (established 2048 bind 1024)
TCP reno registered
checking if image is initramfs...it isn't (no cpio magic); looks like an initrd
Freeing initrd memory: 14336K
NetWinder Floating Point Emulator V0.97 (extended precision)
audit: initializing netlink socket (disabled)
audit(1.580:1): initialized
JFFS2 version 2.2. (NAND) (C) 2001-2006 Red Hat, Inc.
io scheduler noop registered (default)
io scheduler anticipatory registered
Console: switching to colour frame buffer device 80x30
fb0: EP93xx frame buffer at 640x480x16bpp
ep93xx_wdt: EP93XX watchdog, driver version 0.3 (nCS1 disable detected)
Serial: AMBA driver $Revision: 1.41 $
apb:uart1: ttyAM0 at MMIO 0x808c0000 (irq = 52) is a AMBA
apb:uart2: ttyAM1 at MMIO 0x808d0000 (irq = 54) is a AMBA
apb:uart3: ttyAM2 at MMIO 0x808e0000 (irq = 55) is a AMBA
RAMDISK: wrong blocksize 8096, reverting to defaults
RAMDISK driver initialized: 2 RAM disks of 32768K size 1024 blocksize
loop: loaded (max 8 devices)
nbd: registered device at major 43
PPP generic driver version 2.4.2
PPP Deflate Compression module registered
PPP BSD Compression module registered
SLIP: version 0.8.4-NET3.019-NEWTTY (dynamic channels, max=256).
CSLIP: code copyright 1989 Regents of the University of California.
physmap platform flash device: 02000000 at 60000000
physmap-flash.0: Found 1 x16 devices at 0x0 in 16-bit bank
Amd/Fujitsu Extended Query Table at 0x0040
physmap-flash.0: 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.
cmdlinepart partition parsing not available
Searching for RedBoot partition table in physmap-flash.0 at offset 0x1fe0000
6 RedBoot partitions found on MTD device physmap-flash.0
Creating 6 MTD partitions on "physmap-flash.0":
0x00000000-0x00040000 : "RedBoot"
0x00040000-0x00180000 : "zImage"
0x00180000-0x00980000 : "ramdisk"
0x00980000-0x00fe0000 : "unallocated"
0x00fe0000-0x00fff000 : "FIS directory"
mtd: partition "FIS directory" doesn't end on an erase block -- force read-only
0x00fff000-0x01000000 : "RedBoot config"
mtd: partition "RedBoot config" doesn't start on an erase block boundary -- force read-only
ep93xx-usb ep93xx-usb: EP93xx OHCI
ep93xx-usb ep93xx-usb: new USB bus registered, assigned bus number 1
ep93xx-usb ep93xx-usb: irq 56, io mem 0x80020000
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 3 ports detected
usbcore: registered new interface driver hiddev
usbcore: registered new interface driver usbhid
drivers/usb/input/hid-core.c: v2.6:USB HID core driver
drivers/usb/net/rtl8150.c: rtl8150 based usb-ethernet driver v0.6.2 (2004/08/27)
usbcore: registered new interface driver rtl8150
usbcore: registered new interface driver usbserial
drivers/usb/serial/usb-serial.c: USB Serial Driver core
drivers/usb/serial/usb-serial.c: USB Serial support registered for pl2303
usbcore: registered new interface driver pl2303
drivers/usb/serial/pl2303.c: Prolific PL2303 USB to serial adaptor driver
ep93xx_udc: version 17-10-2006
USB Device Controller Chip ID :0 test chipID is wrong
Are you sure the USB2 Slave Daughter Board Link on EDB931X?
ep93xx-udc: probe of ep93xx-udc failed with error -16
mice: PS/2 mouse device common for all mice
i2c /dev entries driver
**WARNING** I2C adapter driver [EP93XX I2C bit-bang interface] forgot to specify physical device; fix it!
Advanced Linux Sound Architecture Driver Version 1.0.14rc1 (Tue Jan 09 09:56:17 2007 UTC).
snd_ep93xx_probe - enter
Cirrus Logic ep93xx i2s audio initialized
ALSA device list:
#0: Cirrus Logic I2S Audio with CS4271
TCP cubic registered
NET: Registered protocol family 1
NET: Registered protocol family 10
NET: Registered protocol family 17
NET: Registered protocol family 15
drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
RAMDISK: Compressed image found at block 0
VFS: Mounted root (ext2 filesystem).
Freeing init memory: 128K
NETDEV WATCHDOG: eth0: transmit timed out

Please press Enter to activate this console.


BusyBox v1.1.3 (2009.10.29-20:05+0000) Built-in shell (ash)
Enter 'help' for a list of built-in commands.

/ # ls
bin home lost+found opt sys var
dev lib media proc tmp
etc linuxrc mnt sbin usr
/ # cd bin
/bin # ls
ash dumpkmap gzip mount run-parts umount
busybox echo hostname mv sed uname
cat egrep kill netstat sh uncompress
chmod false ln pidof sleep usleep
cp fbset ls ping stty vi
date fgrep mkdir ps sync watch
dd getopt mknod pwd tar zcat
df grep mktemp rm touch
dmesg gunzip more rmdir true
/bin #

2> after rebooting my system:

Go through this log:

RedBoot(tm) bootstrap and debug environment [ROMRAM]
Non-certified release, version UNKNOWN - built 21:36:55, Nov 18 2009

Platform: Cirrus Logic EDB9307A Board (ARM920T) Rev A
Copyright (C) 2000, 2001, 2002, 2003, 2004 Red Hat, Inc.
Copyright (C) 2003, 2004, 2005, 2006 eCosCentric Limited

RAM: 0x00000000-0x04000000, [0x000433a0-0x03fdd000] available
FLASH: 0x60000000 - 0x61000000, 128 blocks of 0x00020000 bytes each.
== Executing boot script in 1.000 seconds - enter ^C to abort
RedBoot> fis load zImage
RedBoot> fis load ramdisk
RedBoot> exec -r 0x800000 -s 0xe00000 -c "root=/dev/ram console=ttyAM video=ep93xxfb:vout=0,vmode=2,depth=16" 0xc0080000
Using base address 0x00800000 and length 0x00800000

If you need any more information please ask me.On my board there is no LAN port.


Ravi

cyent 12-03-2009 11:13 PM

Hmm. I don't really know...

Items in that log output I'd worry about are...

RAMDISK: wrong blocksize 8096, reverting to defaults
RAMDISK driver initialized: 2 RAM disks of 32768K size 1024 blocksize

These look as though the partition / flash layout isn't aligning with flash block boundaries. May be a problem.

mtd: partition "FIS directory" doesn't end on an erase block -- force read-only
0x00fff000-0x01000000 : "RedBoot config"
mtd: partition "RedBoot config" doesn't start on an erase block boundary -- force read-only

Seems a bit strange..
USB Device Controller Chip ID :0 test chipID is wrong
Are you sure the USB2 Slave Daughter Board Link on EDB931X?
ep93xx-udc: probe of ep93xx-udc failed with error -16

i2c /dev entries driver
**WARNING** I2C adapter driver [EP93XX I2C bit-bang interface] forgot to specify physical device; fix it!

In the category of getting desperate and clutching at straws...

If you have another one of these devices lying around... can you install the same set up on it and get it working?

Put a volt meter on your power supply, is it correct?

What patterns do you notice?

Does it take the same time to die each time? Try five times and measure number of seconds to death.
Or same number of commands? Or same number of characters? Or same set of commands?

ravi_chobey 12-06-2009 11:06 PM

Dear Cyent,

I am having two boards,but on one board i am getting "system halted" error.The second board on which i am working currently, is not able to work properly,i am not able to enter,when i am executing "ls" command,it is executing,but when i am trying to execute some more work,it is coming under hang condition.I don't know whether the system is hanged or keyboard is hanged.I am forwarding the log:


FIRST BOOTLOG


+Emsys : flash int
Emsys : flash_get_limits
EP93xx - no EEPROM, static ESA, or RedBoot config option.
No network interfaces found

RedBoot(tm) bootstrap and debug environment [ROMRAM]
Non-certified release, version UNKNOWN - built 21:36:55, Nov 18 2009

Platform: Cirrus Logic EDB9307A Board (ARM920T) Rev A
Copyright (C) 2000, 2001, 2002, 2003, 2004 Red Hat, Inc.
Copyright (C) 2003, 2004, 2005, 2006 eCosCentric Limited

RAM: 0x00000000-0x04000000, [0x000433a0-0x03fdd000] available
FLASH: 0x60000000 - 0x61000000, 128 blocks of 0x00020000 bytes each.
== Executing boot script in 1.000 seconds - enter ^C to abort
RedBoot> fis load zImage
RedBoot> fis load ramdisk
RedBoot> exec -r 0x800000 -s 0xe00000 -c "root=/dev/ram console=ttyAM video=ep93xxfb:vout=0,vmode=2,depth=16" 0xc0080000
Using base address 0x00800000 and length 0x00800000
Uncompressing Linux.................................................................... done, booting the kernel.
Linux version 2.6.20.4 (root@localhost.localdomain) (gcc version 4.1.1) #3 PREEMPT Sat Dec 5 11:23:49 IST 2009
CPU: ARM920T [41129200] revision 0 (ARMv4T), cr=c0007177
Machine: Cirrus Logic EDB9307A Evaluation Board
Memory policy: ECC disabled, Data cache writeback
CPU0: D VIVT write-back cache
CPU0: I cache: 16384 bytes, associativity 64, 32 byte lines, 8 sets
CPU0: D cache: 16384 bytes, associativity 64, 32 byte lines, 8 sets
Built 1 zonelists. Total pages: 16192
Kernel command line: root=/dev/ram console=ttyAM video=ep93xxfb:vout=0,vmode=2,depth=16
PID hash table entries: 256 (order: 8, 1024 bytes)
Console: colour dummy device 80x30
Dentry cache hash table entries: 8192 (order: 3, 32768 bytes)
Inode-cache hash table entries: 4096 (order: 2, 16384 bytes)
Memory: 32MB 32MB = 64MB total
Memory: 48340KB available (1880K code, 214K data, 92K init)
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
ep93xx: PLL1 running at 399 MHz, PLL2 at 192 MHz
ep93xx: FCLK 199 MHz, HCLK 99 MHz, PCLK 49 MHz
checking if image is initramfs...it isn't (no cpio magic); looks like an initrd
Freeing initrd memory: 14336K
NetWinder Floating Point Emulator V0.97 (extended precision)
JFFS2 version 2.2. (NAND) (C) 2001-2006 Red Hat, Inc.
io scheduler noop registered (default)
io scheduler anticipatory registered
Console: switching to colour frame buffer device 80x30
fb0: EP93xx frame buffer at 640x480x16bpp
ep93xx_wdt: EP93XX watchdog, driver version 0.3 (nCS1 disable detected)
Serial: AMBA driver $Revision: 1.41 $
apb:uart1: ttyAM0 at MMIO 0x808c0000 (irq = 52) is a AMBA
apb:uart2: ttyAM1 at MMIO 0x808d0000 (irq = 54) is a AMBA
apb:uart3: ttyAM2 at MMIO 0x808e0000 (irq = 55) is a AMBA
RAMDISK: wrong blocksize 8096, reverting to defaults
RAMDISK driver initialized: 2 RAM disks of 32768K size 1024 blocksize
loop: loaded (max 8 devices)
physmap platform flash device: 02000000 at 60000000
physmap-flash.0: Found 1 x16 devices at 0x0 in 16-bit bank
Amd/Fujitsu Extended Query Table at 0x0040
physmap-flash.0: 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.
cmdlinepart partition parsing not available
Searching for RedBoot partition table in physmap-flash.0 at offset 0x1fe0000
6 RedBoot partitions found on MTD device physmap-flash.0
Creating 6 MTD partitions on "physmap-flash.0":
0x00000000-0x00040000 : "RedBoot"
0x00040000-0x00180000 : "zImage"
0x00180000-0x00980000 : "ramdisk"
0x00980000-0x00fe0000 : "unallocated"
0x00fe0000-0x00fff000 : "FIS directory"
mtd: partition "FIS directory" doesn't end on an erase block -- force read-only
0x00fff000-0x01000000 : "RedBoot config"
mtd: partition "RedBoot config" doesn't start on an erase block boundary -- force read-only
mice: PS/2 mouse device common for all mice
drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
RAMDISK: Compressed image found at block 0
VFS: Mounted root (ext2 filesystem).
Freeing init memory: 92K
Jan 1 00:00:03 udhcpc[187]: udhcpc (v0.9.9-pre) started

Jan 1 00:00:03 udhcpc[187]: socket failed!: Function not implemented


Please press Enter to activate this console.


BusyBox v1.1.3 (2009.12.05-05:58+0000) Built-in shell (ash)
Enter 'help' for a list of built-in commands.

/ # l

/*-------------------------SECOND BOOT LOG------------------------------------*/

+Emsys : flash int
Emsys : flash_get_limits
EP93xx - no EEPROM, static ESA, or RedBoot config option.
No network interfaces found

RedBoot(tm) bootstrap and debug environment [ROMRAM]
Non-certified release, version UNKNOWN - built 21:36:55, Nov 18 2009

Platform: Cirrus Logic EDB9307A Board (ARM920T) Rev A
Copyright (C) 2000, 2001, 2002, 2003, 2004 Red Hat, Inc.
Copyright (C) 2003, 2004, 2005, 2006 eCosCentric Limited

RAM: 0x00000000-0x04000000, [0x000433a0-0x03fdd000] available
FLASH: 0x60000000 - 0x61000000, 128 blocks of 0x00020000 bytes each.
== Executing boot script in 1.000 seconds - enter ^C to abort
RedBoot> fis load zImage
RedBoot> fis load ramdisk
RedBoot> exec -r 0x800000 -s 0xe00000 -c "root=/dev/ram console=ttyAM video=ep93xxfb:vout=0,vmode=2,depth=16" 0xc0080000
Using base address 0x00800000 and length 0x00800000
Uncompressing Linux.................................................................... done, booting the kernel.
Linux version 2.6.20.4 (root@localhost.localdomain) (gcc version 4.1.1) #3 PREEMPT Sat Dec 5 11:23:49 IST 2009
CPU: ARM920T [41129200] revision 0 (ARMv4T), cr=c0007177
Machine: Cirrus Logic EDB9307A Evaluation Board
Memory policy: ECC disabled, Data cache writeback
CPU0: D VIVT write-back cache
CPU0: I cache: 16384 bytes, associativity 64, 32 byte lines, 8 sets
CPU0: D cache: 16384 bytes, associativity 64, 32 byte lines, 8 sets
Built 1 zonelists. Total pages: 16192
Kernel command line: root=/dev/ram console=ttyAM video=ep93xxfb:vout=0,vmode=2,depth=16
PID hash table entries: 256 (order: 8, 1024 bytes)
Console: colour dummy device 80x30
Dentry cache hash table entries: 8192 (order: 3, 32768 bytes)
Inode-cache hash table entries: 4096 (order: 2, 16384 bytes)
Memory: 32MB 32MB = 64MB total
Memory: 48340KB available (1880K code, 214K data, 92K init)
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
ep93xx: PLL1 running at 399 MHz, PLL2 at 192 MHz
ep93xx: FCLK 199 MHz, HCLK 99 MHz, PCLK 49 MHz
checking if image is initramfs...it isn't (no cpio magic); looks like an initrd
Freeing initrd memory: 14336K
NetWinder Floating Point Emulator V0.97 (extended precision)
JFFS2 version 2.2. (NAND) (C) 2001-2006 Red Hat, Inc.
io scheduler noop registered (default)
io scheduler anticipatory registered
Console: switching to colour frame buffer device 80x30
fb0: EP93xx frame buffer at 640x480x16bpp
ep93xx_wdt: EP93XX watchdog, driver version 0.3 (nCS1 disable detected)
Serial: AMBA driver $Revision: 1.41 $
apb:uart1: ttyAM0 at MMIO 0x808c0000 (irq = 52) is a AMBA
apb:uart2: ttyAM1 at MMIO 0x808d0000 (irq = 54) is a AMBA
apb:uart3: ttyAM2 at MMIO 0x808e0000 (irq = 55) is a AMBA
RAMDISK: wrong blocksize 8096, reverting to defaults
RAMDISK driver initialized: 2 RAM disks of 32768K size 1024 blocksize
loop: loaded (max 8 devices)
physmap platform flash device: 02000000 at 60000000
physmap-flash.0: Found 1 x16 devices at 0x0 in 16-bit bank
Amd/Fujitsu Extended Query Table at 0x0040
physmap-flash.0: 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.
cmdlinepart partition parsing not available
Searching for RedBoot partition table in physmap-flash.0 at offset 0x1fe0000
6 RedBoot partitions found on MTD device physmap-flash.0
Creating 6 MTD partitions on "physmap-flash.0":
0x00000000-0x00040000 : "RedBoot"
0x00040000-0x00180000 : "zImage"
0x00180000-0x00980000 : "ramdisk"
0x00980000-0x00fe0000 : "unallocated"
0x00fe0000-0x00fff000 : "FIS directory"
mtd: partition "FIS directory" doesn't end on an erase block -- force read-only
0x00fff000-0x01000000 : "RedBoot config"
mtd: partition "RedBoot config" doesn't start on an erase block boundary -- force read-only
mice: PS/2 mouse device common for all mice
drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
RAMDISK: Compressed image found at block 0
VFS: Mounted root (ext2 filesystem).
Freeing init memory: 92K
Jan 1 00:00:03 udhcpc[187]: udhcpc (v0.9.9-pre) started

Jan 1 00:00:03 udhcpc[187]: socket failed!: Function not implemented


Please press Enter to activate this console.


BusyBox v1.1.3 (2009.12.05-05:58+0000) Built-in shell (ash)
Enter 'help' for a list of built-in commands.

/ #

THIRD BOOT LOG

+Emsys : flash int
Emsys : flash_get_limits
EP93xx - no EEPROM, static ESA, or RedBoot config option.
No network interfaces found

RedBoot(tm) bootstrap and debug environment [ROMRAM]
Non-certified release, version UNKNOWN - built 21:36:55, Nov 18 2009

Platform: Cirrus Logic EDB9307A Board (ARM920T) Rev A
Copyright (C) 2000, 2001, 2002, 2003, 2004 Red Hat, Inc.
Copyright (C) 2003, 2004, 2005, 2006 eCosCentric Limited

RAM: 0x00000000-0x04000000, [0x000433a0-0x03fdd000] available
FLASH: 0x60000000 - 0x61000000, 128 blocks of 0x00020000 bytes each.
== Executing boot script in 1.000 seconds - enter ^C to abort
RedBoot> fis load zImage
RedBoot> fis load ramdisk
RedBoot> exec -r 0x800000 -s 0xe00000 -c "root=/dev/ram console=ttyAM video=ep93xxfb:vout=0,vmode=2,depth=16" 0xc0080000
Using base address 0x00800000 and length 0x00800000
Uncompressing Linux.................................................................... done, booting the kernel.
Linux version 2.6.20.4 (root@localhost.localdomain) (gcc version 4.1.1) #3 PREEMPT Sat Dec 5 11:23:49 IST 2009
CPU: ARM920T [41129200] revision 0 (ARMv4T), cr=c0007177
Machine: Cirrus Logic EDB9307A Evaluation Board
Memory policy: ECC disabled, Data cache writeback
CPU0: D VIVT write-back cache
CPU0: I cache: 16384 bytes, associativity 64, 32 byte lines, 8 sets
CPU0: D cache: 16384 bytes, associativity 64, 32 byte lines, 8 sets
Built 1 zonelists. Total pages: 16192
Kernel command line: root=/dev/ram console=ttyAM video=ep93xxfb:vout=0,vmode=2,depth=16
PID hash table entries: 256 (order: 8, 1024 bytes)
Console: colour dummy device 80x30
Dentry cache hash table entries: 8192 (order: 3, 32768 bytes)
Inode-cache hash table entries: 4096 (order: 2, 16384 bytes)
Memory: 32MB 32MB = 64MB total
Memory: 48340KB available (1880K code, 214K data, 92K init)
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
ep93xx: PLL1 running at 399 MHz, PLL2 at 192 MHz
ep93xx: FCLK 199 MHz, HCLK 99 MHz, PCLK 49 MHz
checking if image is initramfs...it isn't (no cpio magic); looks like an initrd
Freeing initrd memory: 14336K
NetWinder Floating Point Emulator V0.97 (extended precision)
JFFS2 version 2.2. (NAND) (C) 2001-2006 Red Hat, Inc.
io scheduler noop registered (default)
io scheduler anticipatory registered
Console: switching to colour frame buffer device 80x30
fb0: EP93xx frame buffer at 640x480x16bpp
ep93xx_wdt: EP93XX watchdog, driver version 0.3 (nCS1 disable detected)
Serial: AMBA driver $Revision: 1.41 $
apb:uart1: ttyAM0 at MMIO 0x808c0000 (irq = 52) is a AMBA
apb:uart2: ttyAM1 at MMIO 0x808d0000 (irq = 54) is a AMBA
apb:uart3: ttyAM2 at MMIO 0x808e0000 (irq = 55) is a AMBA
RAMDISK: wrong blocksize 8096, reverting to defaults
RAMDISK driver initialized: 2 RAM disks of 32768K size 1024 blocksize
loop: loaded (max 8 devices)
physmap platform flash device: 02000000 at 60000000
physmap-flash.0: Found 1 x16 devices at 0x0 in 16-bit bank
Amd/Fujitsu Extended Query Table at 0x0040
physmap-flash.0: 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.
cmdlinepart partition parsing not available
Searching for RedBoot partition table in physmap-flash.0 at offset 0x1fe0000
6 RedBoot partitions found on MTD device physmap-flash.0
Creating 6 MTD partitions on "physmap-flash.0":
0x00000000-0x00040000 : "RedBoot"
0x00040000-0x00180000 : "zImage"
0x00180000-0x00980000 : "ramdisk"
0x00980000-0x00fe0000 : "unallocated"
0x00fe0000-0x00fff000 : "FIS directory"
mtd: partition "FIS directory" doesn't end on an erase block -- force read-only
0x00fff000-0x01000000 : "RedBoot config"
mtd: partition "RedBoot config" doesn't start on an erase block boundary -- force read-only
mice: PS/2 mouse device common for all mice
drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
RAMDISK: Compressed image found at block 0
VFS: Mounted root (ext2 filesystem).
Freeing init memory: 92K
Jan 1 00:00:03 udhcpc[187]: udhcpc (v0.9.9-pre) started

Jan 1 00:00:03 udhcpc[187]: socket failed!: Function not implemented


Please press Enter to activate this console.

cyent,if you have any suggestions.Please let me know that.

Regards,
Ravi

cyent 12-07-2009 06:46 PM

Notes....

* The logs are the same.(Diff'ed them)

* Since hardware different but same problem, probably not a hardware fault. (Unless using a common power supply perhaps)

* Ram, start and length, as detected by redboot is weird.
RAM: 0x00000000-0x04000000, [0x000433a0-0x03fdd000] available

Where are those numbers coming from? Are they correct?

* This log message worries me...
RAMDISK: wrong blocksize 8096, reverting to defaults
where is that block size coming from? Can you fix it?

ravi_chobey 12-08-2009 10:15 PM

Dear Cyent,

Finally i was able to run linux on my board.The changes which i have done was,i have removed drivers of USB,Networking(ethernet port is not there) and watchdog timer.Also i have partition related settings in MTD drivers for -1 to 0.

Thanks for your support Cyent.

Regards,
Ravi Chobey

cyent 12-08-2009 11:16 PM

Progress, but you haven't in any way solved the problem.

Now put things back one by one and find out what broke it.

And then take them all out again and put them back in one by one in a different order to prove whether it was one of those things that broke it, or you ran over some boundary or you had some noxious interaction between those subsystems.


All times are GMT -5. The time now is 12:31 AM.