2009-01-23 05:19:38 init: exec rc failed
Lakhaa J (INDIA)
Message: 68280
Hi,
I am using IP04 IP-PBX. I am getting boot error. I am a newbie to Blackfin, can anyone help me to get out of this problem.
The following is the log message:
U-Boot 1.1.5 (May 5 2007 - 05:46:05)
CPU: ADSP BF532 Rev.: 0.5
Board: IP04 IP-PBX
http://www.rowetel.com/ucasterisk/ip04.html
Clock: VCO: 400 MHz, Core: 400 MHz, System: 133 MHz
SDRAM: 64 MB
In: serial
Out: serial
Err: serial
256 MiB
DM9000#0
starting from spi flash
Hit any key to stop autoboot: 0
Loading from device 0: NAND 256MiB 3,3V 8-bit (offset 0x0)
Image Name: uClinux Kernel and ext2
Image Type: Blackfin Linux Kernel Image (gzip compressed)
Data Size: 2126307 Bytes = 2 MB
Load Address: 00001000
Entry Point: 00001000
Automatic boot of image at addr 0x02000000 ...
## Booting image at 02000000 ...
Image Name: uClinux Kernel and ext2
Image Type: Blackfin Linux Kernel Image (gzip compressed)
Data Size: 2126307 Bytes = 2 MB
Load Address: 00001000
Entry Point: 00001000
Verifying Checksum ... OK
Uncompressing Kernel Image ... OK
Starting Kernel at = 1000
Linux version 2.6.19.3-ADI-2007R1.1-svn (david@bunny) (gcc version 4.1.1 (ADI 07
R1)) #3 Mon Mar 10
Blackfin support (C) 2004-2007 Analog Devices, Inc.
Compiled for ADSP-BF532 Rev 0.5
Blackfin Linux support by http://blackfin.uclinux.org/
Processor Speed: 400 MHz core clock and 133 Mhz System Clock
Board Memory: 64MB
Kernel Managed Memory: 64MB
Memory map:
text = 0x00001000-0x001665d0
init = 0x00167000-0x001790c8
data = 0x0017b1a4-0x001bf8c4
stack = 0x0017c000-0x0017e000
bss = 0x001bf8d0-0x001cf52c
available = 0x001cf52c-0x03c00000
rootfs = 0x03c00000-0x03f00000
DMA Zone = 0x03f00000-0x04000000
Instruction Cache Enabled
Data Cache Enabled (write-back)
Hardware Trace Enabled
Built 1 zonelists. Total pages: 15240
Kernel command line: root=/dev/mtdblock2 rw ethaddr=02:80:ad:20:31:b8
Configuring Blackfin Priority Driven Interrupts
PID hash table entries: 256 (order: 8, 1024 bytes)
Dentry cache hash table entries: 8192 (order: 3, 32768 bytes)
Inode-cache hash table entries: 4096 (order: 2, 16384 bytes)
Physical pages: 3c00
Memory available: 58940k/64019k RAM, (72k init co
, 1024k dma)
Blackfin Scratchpad data SRAM: 4 KB
Blackfin Instruction SRAM: 32 KB
Security Framework v1.0.0 initialized
Mount-cache hash table entries: 512
NET: Registered protocol family 16
Blackfin GPIO Controller
Blackfin DMA Controller
bf1_init(): chip_id=527A50CB,dspid=E5040005
bf1_init(): registering device resources
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: 512 (order: -1, 2048 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
yaffs Mar 10 2008 06:57:22 Installing.
io scheduler noop registered
io scheduler anticipatory registered (default)
io scheduler cfq registered
Dynamic Power Management Controller Driver v0.1: major=10, minor = 254
Serial: Blackfin serial driver
bfin-uart.1: ttyBF0 at MMIO 0xffc00400 (irq = 21) is a BFIN-UART
RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize
dm9000 Ethernet Driver
eth0: dm9000 at 20100000,20100002 IRQ 48 MAC: 02:80:ad:20:31:b8
dm9000: read wrong id 0x2b2a2908
dm9000: read wrong id 0x2b2a2928
dm9000: wrong id: 0x2b2a2928
dm9000: not found (0).
BF5xx flash: probing 16-bit flash bus
uclinux[mtd]: RAM probe address=0x3c00000 size=0x300000
Creating 1 MTD partitions on "RAM":
0x00000000-0x00300000 : "ROMfs"
uclinux[mtd]: set ROMfs:EXT2 to be root filesystem
Generic platform RAM MTD, (c) 2004 Simtec Electronics
NAND device: Manufacturer ID: 0xec, Chip ID: 0xda (Samsung NAND 256MiB 3,3V 8-bi
t)
Scanning device for bad blocks
Creating 2 MTD partitions on "NAND 256MiB 3,3V 8-bit":
0x00000000-0x00800000 : "linux kernel"
0x00800000-0x10000000 : "file system"
usbmon: debugfs is not available
driver isp1362-hcd, 2005-04-04
isp1362-hcd isp1362-hcd.0: ISP1362 Host Controller
isp1362-hcd isp1362-hcd.0: new USB bus registered,
isp1362_hc_reset:
Clock not ready after 20ms
isp1362-hcd isp1362-hcd.0: can't setup
isp1362-hcd isp1362-hcd.0: USB bus 1 deregistered
init error, -19
Initializing USB Mass Storage driver...
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
ip_conntrack version 2.4 (480 buckets, 3840 max) - 208 bytes per conntrack
ip_tables: (C) 2000-2006 Netfilter Core Team
TCP cubic registered
NET: Registered protocol family 1
NET: Registered protocol family 17
drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
yaffs: dev is 32505858 name is "mtdblock2"
yaffs: Attempting MTD mount on 31.2, "mtdblock2"
yaffs: auto selecting yaffs2
VFS: Mounted root (yaffs filesystem).
Freeing unused kernel memory: 72k freed (0x167000 - 0x178000)
dma_alloc_init: dma_page @ 0x00176000 - 256 pages at 0x03f00000
init: exec rc failed
init: Booting to single user mode
init: exec of single user shell failed
user shell failed
init: -/bin/sh exec failed
init: -/bin/sh exec failedfailed
Booting to single user mode
init: exec of single user shell failed
init: -/bin/sh exec failed
Thanks & Regards,
Lakhaa
QuoteReplyEditDelete
2009-01-23 05:29:52 Re: init: exec rc failed
Appalayagari Sreedhar (INDIA)
Message: 68281
Hi,
Check whether this suggestion will help.
Check whether the application binary you have given the executable permissions and also see whether you have given the exact path of the executing application binary. similar kind of problems i too faced.
Best Regards, Sreedhar
QuoteReplyEditDelete
2009-01-23 06:00:52 Re: init: exec rc failed
Mike Frysinger (UNITED STATES)
Message: 68285
if you're building FDPIC, make sure all the right libraries are installed in /lib in the romfs dir
QuoteReplyEditDelete
2009-01-23 06:36:20 Re: init: exec rc failed
Lakhaa J (INDIA)
Message: 68289
Hi............
Thanks for the suggestions. I managed to auto boot. I am getting u-boot prompt now.
U-Boot 1.1.5 (May 5 2007 - 05:46:05)
CPU: ADSP BF532 Rev.: 0.5
Board: IP04 IP-PBX
http://www.rowetel.com/ucasterisk/ip04.html
Clock: VCO: 400 MHz, Core: 400 MHz, System: 133 MHz
SDRAM: 64 MB
In: serial
Out: serial
Err: serial
256 MiB
DM9000#0
starting from spi flash
Hit any key to stop autoboot: 0
ip04>
But still I get the following error on auto boot
init: exec rc failed
init: Booting to single user mode
init: exec of single user shell failed
user shell failed
init: -/bin/sh exec failed
init: -/bin/sh exec failedfailed
Booting to single user mode
Can you tell me the steps to solve the error
Thanks
Lakhaa
QuoteReplyEditDelete
2009-01-23 10:53:24 Re: init: exec rc failed
Yi Li (CHINA)
Message: 68295
Please check whether you have "/etc/rc" in your rootfs.