Home 
Forum
Forum
| Welcome to AT91SAM Community Forum http://www.at91.com/samphpbb/ |
|
| AT91SAM9G20 - Kernel panic - not syncing: No init found http://www.at91.com/samphpbb/viewtopic.php?f=12&t=19516 |
Page 1 of 1 |
| Author: | ssu2kor [ Mon Aug 30, 2010 6:37 am ] |
| Post subject: | AT91SAM9G20 - Kernel panic - not syncing: No init found |
Hello All, Even though there are several posts on the net on the same, I could not find a concrete solution for the same. I am using the prebuilt binaries from the www.AT91.com for AT91SAM9G20 linux kernel and jffs2 file system. I strongly feel if there is an issue with the bootargs and hence the U-boot environment is also available below. Please help me to solve this problem. U-Boot> printenv bootcmd=nand read 0x22000000 0xA0000 0x200000; bootm bootdelay=3 baudrate=115200 ethact=macb0 ethaddr=3e:36:65:ba:6f:be ipaddr=199.63.247.50 serverip=199.63.247.100 stdin=serial stdout=serial stderr=serial bootargs=mem=64M console=ttyS0,115200 root=mtd2 rw rootfstype=jffs2 Environment size: 274/131067 bytes U-Boot> tftp 0x21400000 genericfs.arm_nofpu.jffs2 macb0: link up, 100Mbps full-duplex (lpa: 0xc5e1) Using macb0 device TFTP from server 199.63.247.100; our IP address is 199.63.247.50 Filename 'genericfs.arm_nofpu.jffs2'. Load address: 0x21400000 Loading: ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ######################################## done Bytes transferred = 12985524 (c624b4 hex) U-Boot> nand write.jffs2 0x21400000 0x2A0000 0xc624b4 NAND write: device 0 offset 0x2a0000, size 0xc624b4 Writing data at 0xf02000 -- 100% complete. 12985524 bytes written: OK U-Boot> tftp 0x21400000 linux-2.6.27.bin macb0: link up, 100Mbps full-duplex (lpa: 0xc5e1) Using macb0 device TFTP from server 199.63.247.100; our IP address is 199.63.247.50 Filename 'linux-2.6.27.bin'. Load address: 0x21400000 Loading: ################################################################# ###################################### done Bytes transferred = 1498980 (16df64 hex) U-Boot> bootm ## Booting kernel from Legacy Image at 21400000 ... Image Name: linux-2.6 Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 1498916 Bytes = 1.4 MB Load Address: 20008000 Entry Point: 20008000 Verifying Checksum ... OK Loading Kernel Image ... OK OK Starting kernel ... Uncompressing Linux................................................................................................. done, booting the kernel. Linux version 2.6.27 (nferre@bendor) (gcc version 4.2.0 20070413 (prerelease) (CodeSourcery Sourcery G++ Lite 2007q1-10)) #1 Thu Sep 24 17:26:24 CEST 2009 CPU: ARM926EJ-S [41069265] revision 5 (ARMv5TEJ), cr=00053177 Machine: Atmel AT91SAM9G20-EK Memory policy: ECC disabled, Data cache writeback Clocks: CPU 396 MHz, master 132 MHz, main 18.432 MHz CPU0: D VIVT write-back cache CPU0: I cache: 32768 bytes, associativity 4, 32 byte lines, 256 sets CPU0: D cache: 32768 bytes, associativity 4, 32 byte lines, 256 sets Built 1 zonelists in Zone order, mobility grouping on. Total pages: 16256 Kernel command line: mem=64M console=ttyS0,115200 root=mtd2 rw rootfstype=jffs2 AT91: 96 gpio irqs in 3 banks PID hash table entries: 256 (order: 8, 1024 bytes) Console: colour dummy device 80x30 console [ttyS0] enabled Dentry cache hash table entries: 8192 (order: 3, 32768 bytes) Inode-cache hash table entries: 4096 (order: 2, 16384 bytes) Memory: 64MB = 64MB total Memory: 61760KB available (2756K code, 225K data, 120K init) Calibrating delay loop... 197.83 BogoMIPS (lpj=989184) Mount-cache hash table entries: 512 CPU: Testing write buffer coherency: ok net_namespace: 288 bytes NET: Registered protocol family 16 AT91: Power Management AT91: Starting after general reset 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: 2, 16384 bytes) TCP bind hash table entries: 2048 (order: 1, 8192 bytes) TCP: Hash tables configured (established 2048 bind 2048) TCP reno registered NET: Registered protocol family 1 NetWinder Floating Point Emulator V0.97 (double precision) JFFS2 version 2.2. (NAND) (SUMMARY) © 2001-2006 Red Hat, Inc. msgmni has been set to 120 io scheduler noop registered io scheduler anticipatory registered (default) atmel_usart.0: ttyS0 at MMIO 0xfefff200 (irq = 1) is a ATMEL_SERIAL atmel_usart.1: ttyS1 at MMIO 0xfffb0000 (irq = 6) is a ATMEL_SERIAL atmel_usart.2: ttyS2 at MMIO 0xfffb4000 (irq = 7) is a ATMEL_SERIAL brd: module loaded loop: module loaded ssc ssc.0: Atmel SSC device at 0xc4870000 (irq 14) MACB_mii_bus: probed eth0: Atmel MACB at 0xfffc4000 irq 21 (3e:36:65:ba:6f:be) eth0: attached PHY driver [Generic PHY] (mii_bus:phy_addr=ffffffff:00, irq=-1) Driver 'sd' needs updating - please use bus_type methods NAND device: Manufacturer ID: 0xec, Chip ID: 0xda (Samsung NAND 256MiB 3,3V 8-bit) AT91 NAND: 8-bit, Software ECC Scanning device for bad blocks Bad eraseblock 740 at 0x05c80000 Creating 3 MTD partitions on "atmel_nand": 0x00000000-0x00400000 : "Bootstrap" 0x00400000-0x04000000 : "Partition 1" 0x04000000-0x10000000 : "Partition 2" usbmon: debugfs is not available at91_ohci at91_ohci: AT91 OHCI at91_ohci at91_ohci: new USB bus registered, assigned bus number 1 at91_ohci at91_ohci: irq 20, io mem 0x00500000 usb usb1: configuration #1 chosen from 1 choice 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. udc: at91_udc version 3 May 2006 mice: PS/2 mouse device common for all mice input: gpio-keys as /class/input/input0 rtc-at91sam9 at91_rtt.0: rtc core: registered at91_rtt as rtc0 rtc-at91sam9 at91_rtt.0: rtc0: SET TIME! i2c /dev entries driver i2c-gpio i2c-gpio: using pins 55 (SDA) and 56 (SCL) Registered led device: ds5 Registered led device: ds1 usbcore: registered new interface driver usbhid usbhid: v2.6:USB HID core driver Advanced Linux Sound Architecture Driver Version 1.0.17. ASoC version 0.13.2 WM8731 Audio Codec 0.13<6>asoc: WM8731 <-> atmel-ssc0 mapping ok ALSA device list: #0: WM8731 (WM8731) TCP cubic registered NET: Registered protocol family 17 RPC: Registered udp transport module. RPC: Registered tcp transport module. rtc-at91sam9 at91_rtt.0: hctosys: unable to read the hardware clock VFS: Mounted root (jffs2 filesystem). Freeing init memory: 120K Warning: unable to open an initial console. Kernel panic - not syncing: No init found. Try passing init= option to kernel. Regards Sandeep Suresh |
|
| Author: | kamejoko80 [ Thu Sep 02, 2010 11:35 am ] |
| Post subject: | Re: AT91SAM9G20 - Kernel panic - not syncing: No init found |
Hi, I think this is wrong Quote: nand write.jffs2 0x21400000 0x2A0000 0xc624b4 Try this command nand write.jffs2 0x21400000 0x400000 <size of image in hex> regards |
|
| Author: | falingtrea [ Thu Sep 02, 2010 8:02 pm ] |
| Post subject: | Re: AT91SAM9G20 - Kernel panic - not syncing: No init found |
Usually when you see a kernel panic after mounting the JFFS2 file, it is because there is some issue with the RFS format. The size of the RFS does not look right. It needs to be a multiple of the erase page size of the NAND flash you are using, typically 128k bytes. So your RFS does not look like it was padded to the next 128k boundary. |
|
| Page 1 of 1 | All times are UTC + 1 hour [ DST ] |
| Powered by phpBB © 2000, 2002, 2005, 2007 phpBB Group http://www.phpbb.com/ |
|
