Have you enabled NAND support in your kernel? Regards, Amit Pundir
On Thu, Sep 1, 2011 at 11:01 AM, venkat k raju <[email protected]> wrote: > > > On Thu, Sep 1, 2011 at 11:00 AM, venkat k raju <[email protected]>wrote: > >> Hi Tiago Maluta, >> >> thanks for your response. >> >> i am using beagletouch board. >> >> i made some changes in my boot argument like this >> >> >> there are my environment variable >> bootcmd=nand read 0x80300000 280000 400000 ; bootm 0x80300000 >> bootargs=console=ttyS2,115200n8 root=/dev/mtdblock4 rootfstype=jffs2 ro >> rootwait nohz=off init=/init omapfb.mode=lcd:480x270MR-24@60 >> bootdelay=2 >> >> now there is no Kernel panic error, but it's not mounting filesystem. >> please check my log message. >> >> >> >> boot >> >> NAND read: device 0 offset 0x280000, size 0x400000 >> 4194304 bytes read: OK >> ## Booting kernel from Legacy Image at 80300000 ... >> Image Name: Linux-2.6.32 >> Image Type: ARM Linux Kernel Image (uncompressed) >> Data Size: 2806004 Bytes = 2.7 MiB >> Load Address: 80008000 >> Entry Point: 80008000 >> Verifying Checksum ... OK >> Loading Kernel Image ... OK >> OK >> >> Starting kernel ... >> >> Uncompressing >> Linux.................................................................................................................................................... >> Linux version 2.6.32 ([email protected]) (gcc version >> 4.4.0 (GCC) ) #87 Thu Aug 18 12:36:50 IST 2011 >> CPU: ARMv7 Processor [411fc083] revision 3 (ARMv7), cr=10c53c7f >> CPU: VIPT nonaliasing data cache, VIPT nonaliasing instruction cache >> Machine: OMAP3 Beagle Board >> Memory policy: ECC disabled, Data cache writeback >> OMAP3430/3530 ES3.1 (l2cache iva sgx neon isp 720m ) >> SRAM: Mapped pa 0x40200000 to va 0xfe400000 size: 0x100000 >> Reserving 4194304 bytes SDRAM for VRAM >> Built 1 zonelists in Zone order, mobility grouping on. Total pages: 65024 >> Kernel command line: console=ttyS2,115200n8 root=/dev/mtdblock4 >> rootfstype=jffs2 ro rootwait nohz=off init=/init >> omapfb.mode=lcd:480x270MR-24@60 >> PID hash table entries: 1024 (order: 0, 4096 bytes) >> Dentry cache hash table entries: 32768 (order: 5, 131072 bytes) >> Inode-cache hash table entries: 16384 (order: 4, 65536 bytes) >> Memory: 128MB 128MB = 256MB total >> Memory: 249472KB available (4932K code, 867K data, 172K init, 0K highmem) >> Hierarchical RCU implementation. >> NR_IRQS:402 >> Clocking rate (Crystal/Core/MPU): 26.0/332/500 MHz >> Reprogramming SDRC clock to 332000000 Hz >> GPMC revision 5.0 >> IRQ: Found an INTC at 0xfa200000 (revision 4.0) with 96 interrupts >> Total of 96 interrupts on 1 active controller >> OMAP GPIO hardware version 2.5 >> OMAP clockevent source: GPTIMER12 at 32768 Hz >> Console: colour dummy device 80x30 >> Calibrating delay loop... 477.86 BogoMIPS (lpj=1863680) >> Mount-cache hash table entries: 512 >> CPU: Testing write buffer coherency: ok >> regulator: core version 0.5 >> NET: Registered protocol family 16 >> Found NAND on CS0 >> Registering NAND on CS0 >> Unable to get DVI reset GPIO >> OMAP DMA hardware revision 4.0 >> bio: create slab <bio-0> at 0 >> SCSI subsystem initialized >> usbcore: registered new interface driver usbfs >> usbcore: registered new interface driver hub >> usbcore: registered new device driver usb >> i2c_omap i2c_omap.1: bus 1 rev3.12 at 2600 kHz >> twl4030: PIH (irq 7) chaining IRQs 368..375 >> twl4030: power (irq 373) chaining IRQs 376..383 >> twl4030: gpio (irq 368) chaining IRQs 384..401 >> regulator: VUSB1V5: 1500 mV normal standby >> regulator: VUSB1V8: 1800 mV normal standby >> regulator: VUSB3V1: 3100 mV normal standby >> twl4030_usb twl4030_usb: Initialized TWL4030 USB module >> regulator: VMMC1: 1850 <--> 3150 mV normal standby >> regulator: VDAC: 1800 mV normal standby >> regulator: VPLL2: 1800 mV normal standby >> regulator: VSIM: 1800 <--> 3000 mV normal standby >> i2c_omap i2c_omap.2: bus 2 rev3.12 at 400 kHz >> i2c_omap i2c_omap.3: bus 3 rev3.12 at 100 kHz >> Switching to clocksource 32k_counter >> musb_hdrc: version 6.0, musb-dma, otg (peripheral+host), debug=0 >> musb_hdrc: USB OTG mode controller at fa0ab000 using DMA, IRQ 92 >> NET: Registered protocol family 2 >> IP route cache hash table entries: 2048 (order: 1, 8192 bytes) >> TCP established hash table entries: 8192 (order: 4, 65536 bytes) >> TCP bind hash table entries: 8192 (order: 3, 32768 bytes) >> TCP: Hash tables configured (established 8192 bind 8192) >> TCP reno registered >> UDP hash table entries: 256 (order: 0, 4096 bytes) >> UDP-Lite hash table entries: 256 (order: 0, 4096 bytes) >> NET: Registered protocol family 1 >> RPC: Registered udp transport module. >> RPC: Registered tcp transport module. >> RPC: Registered tcp NFSv4.1 backchannel transport module. >> omap-iommu omap-iommu.0: isp registered >> NetWinder Floating Point Emulator V0.97 (double precision) >> ashmem: initialized >> VFS: Disk quotas dquot_6.5.2 >> Dquot-cache hash table entries: 1024 (order 0, 4096 bytes) >> JFFS2 version 2.2. (NAND) �© 2001-2006 Red Hat, Inc. >> yaffs Aug 18 2011 12:32:48 Installing. >> msgmni has been set to 487 >> alg: No test for stdrng (krng) >> io scheduler noop registered >> io scheduler deadline registered >> io scheduler cfq registered (default) >> OMAP DSS rev 2.0 >> OMAP DISPC rev 3.0 >> OMAP VENC rev 2 >> cmel_oled43_panel: init panel >> cmel_oled43_panel: requesting GPIOs >> Registered led device: lcd-backlight >> cmel_oled43_panel: done >> Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled >> serial8250.0: ttyS0 at MMIO 0x4806a000 (irq = 72) is a ST16654 >> serial8250.1: ttyS1 at MMIO 0x4806c000 (irq = 73) is a ST16654 >> serial8250.2: ttyS2 at MMIO 0x49020000 (irq = 74) is a ST16654 >> console [ttyS2] enabled >> brd: module loaded >> loop: module loaded >> usbcore: registered new interface driver asix >> usbcore: registered new interface driver cdc_ether >> usbcore: registered new interface driver cdc_eem >> usbcore: registered new interface driver dm9601 >> usbcore: registered new interface driver smsc95xx >> usbcore: registered new interface driver gl620a >> usbcore: registered new interface driver net1080 >> usbcore: registered new interface driver plusb >> usbcore: registered new interface driver rndis_host >> usbcore: registered new interface driver cdc_subset >> usbcore: registered new interface driver zaurus >> usbcore: registered new interface driver MOSCHIP usb-ethernet driver >> ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver >> ehci-omap ehci-omap.0: OMAP-EHCI Host Controller >> ehci-omap ehci-omap.0: new USB bus registered, assigned bus number 1 >> ehci-omap ehci-omap.0: irq 77, io mem 0x48064800 >> ehci-omap ehci-omap.0: USB 2.0 started, EHCI 1.00 >> hub 1-0:1.0: USB hub found >> hub 1-0:1.0: 3 ports detected >> Initializing USB Mass Storage driver... >> usbcore: registered new interface driver usb-storage >> USB Mass Storage support registered. >> android init >> android_probe pdata: c053748c >> android_bind >> android_usb gadget: android_usb ready >> musb_hdrc musb_hdrc: MUSB HDRC host driver >> musb_hdrc musb_hdrc: new USB bus registered, assigned bus number 2 >> hub 2-0:1.0: USB hub found >> hub 2-0:1.0: 1 port detected >> f_adb init >> android_register_function adb >> adb_bind_config >> f_mass_storage init >> android_register_function usb_mass_storage >> mice: PS/2 mouse device common for all mice >> input: gpio-keys as /devices/platform/gpio-keys/input/input0 >> input: TSC2007 Touchscreen as /devices/virtual/input/input1 >> i2c /dev entries driver >> Linux video capture interface: v2.00 >> omap-iommu omap-iommu.0: isp: version 1.1 >> gspca: main v2.8.0 registered >> usbcore: registered new interface driver conex >> conex: registered >> usbcore: registered new interface driver etoms >> etoms: registered >> usbcore: registered new interface driver finepix >> finepix: registered >> usbcore: registered new interface driver jeilinj >> jeilinj: registered >> usbcore: registered new interface driver mars >> mars: registered >> usbcore: registered new interface driver mr97310a >> mr97310a: registered >> usbcore: registered new interface driver ov519 >> ov519: registered >> usbcore: registered new interface driver ov534 >> ov534: registered >> usbcore: registered new interface driver pac207 >> pac207: registered >> usbcore: registered new interface driver pac7302 >> pac7302: registered >> usbcore: registered new interface driver pac7311 >> pac7311: registered >> usbcore: registered new interface driver sn9c20x >> sn9c20x: registered >> usbcore: registered new interface driver sonixb >> sonixb: registered >> usbcore: registered new interface driver sonixj >> sonixj: registered >> usbcore: registered new interface driver spca500 >> spca500: registered >> usbcore: registered new interface driver spca501 >> spca501: registered >> usbcore: registered new interface driver spca505 >> spca505: registered >> usbcore: registered new interface driver spca506 >> spca506: registered >> usbcore: registered new interface driver spca508 >> spca508: registered >> usbcore: registered new interface driver spca561 >> spca561: registered >> usbcore: registered new interface driver sq905 >> sq905: registered >> usbcore: registered new interface driver sq905c >> sq905c: registered >> usbcore: registered new interface driver sunplus >> sunplus: registered >> usbcore: registered new interface driver stk014 >> stk014: registered >> usbcore: registered new interface driver stv0680 >> stv0680: registered >> usbcore: registered new interface driver t613 >> t613: registered >> usbcore: registered new interface driver tv8532 >> tv8532: registered >> usbcore: registered new interface driver vc032x >> vc032x: registered >> usbcore: registered new interface driver zc3xx >> zc3xx: registered >> usbcore: registered new interface driver ALi m5602 >> ALi m5602: registered >> usbcore: registered new interface driver STV06xx >> STV06xx: registered >> gspca_gl860: driver startup - version 0.9d10 >> usbcore: registered new interface driver gspca_gl860 >> gspca_gl860: driver registered >> usbcore: registered new interface driver uvcvideo >> USB Video Class driver (v0.1.0) >> OMAP Watchdog Timer Rev 0x31: initial timeout 60 sec >> mmci-omap-hs mmci-omap-hs.1: err -16 configuring card detect >> Registered led device: beagleboard::usr0 >> Registered led device: beagleboard::usr1 >> Registered led device: beagleboard::pmu_stat >> usbcore: registered new interface driver usbhid >> usbhid: USB HID core driver >> logger: created 64K log 'log_main' >> logger: created 256K log 'log_events' >> logger: created 64K log 'log_radio' >> logger: created 64K log 'log_system' >> Advanced Linux Sound Architecture Driver Version 1.0.21. >> usbcore: registered new interface driver snd-usb-audio >> No device for DAI omap-mcbsp-dai-0 >> No device for DAI omap-mcbsp-dai-1 >> No device for DAI omap-mcbsp-dai-2 >> No device for DAI omap-mcbsp-dai-3 >> No device for DAI omap-mcbsp-dai-4 >> OMAP3 Beagle SoC init >> asoc: twl4030 <-> omap-mcbsp-dai-0 mapping ok >> ALSA device list: >> #0: omap3beagle (twl4030) >> TCP cubic registered >> NET: Registered protocol family 17 >> NET: Registered protocol family 15 >> Power Management for TI OMAP3. >> SmartReflex driver initialized >> VFP support v0.3: implementor 41 architecture 3 part 30 variant c rev 1 >> fbcvt: 480x270@60: CVT Name - .129M9-R >> Console: switching to colour frame buffer device 60x33 >> cmel_oled43_panel: panel_enable begin >> cmel_oled43_panel: Setting brightness to 100 percent >> cmel_oled43_panel: panel_enable end >> regulator_init_complete: incomplete constraints, leaving VDVI on >> regulator_init_complete: incomplete constraints, leaving VDAC on >> drivers/rtc/hctosys.c: unable to open rtc device (rtc0) >> omapdss DPI error: display already enabled >> omap_vout omap_vout: 'lcd' Display already enabled >> omapdss DPI error: display already enabled >> omap_vout omap_vout: 'lcd' Display already enabled >> omap_vout omap_vout: Buffer Size = 3686400 >> omap_vout omap_vout: : registered and initialized video device 0 >> omap_vout omap_vout: Buffer Size = 3686400 >> omap_vout omap_vout: : registered and initialized video device 1 >> Waiting for root device /dev/mtdblock4.. // here it self stopping >> >> >> please suggest me . >> >> thanks in advacne. >> >> >> >> >> >> On Wed, Aug 31, 2011 at 11:56 PM, Tiago Maluta <[email protected]>wrote: >> >>> On Wed, Aug 31, 2011 at 5:56 AM, venkat k raju <[email protected]> >>> wrote: >>> > Hi all, >>> > >>> > i have been trying to flash the x-load,u-boot,uimage,rootfs.jffs2 to >>> nand >>> > using windows flash tool Flash v1.5 tool. >>> > >>> > running the following are no problem those are executing properly. >>> > x-loader,u-boot,uImage >>> > >>> > but rootfs.jffs2 mounting time i got some error like this >>> > >>> > Root-NFS: No NFS server available, giving up. >>> > VFS: Unable to mount root fs via NFS, trying floppy. >>> > List of all partitions: >>> > No filesystem could mount root, tried: jffs2 >>> > Kernel panic - not syncing: VFS: Unable to mount root fs on >>> > unknown-block(2,0) >>> > >>> > here may be problem with "boot arguments" and mount point like from >>> where >>> > to mount the rootfs. >>> > >>> > please suggest me how to set the boot arguments, and i don't know how >>> to >>> > create mount point from that flash tool or any other approach to solve >>> my >>> > problem. >>> > >>> >>> what's in your u-boot environment vars? (use "printenv" command) >>> >>> --tm >>> >> >> >> >> -- >> thanks&Regards >> k.v.raju >> > > > > -- > thanks&Regards > k.v.raju > > -- > You received this message because you are subscribed to the Google Groups > "rowboat" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/rowboat?hl=en. > -- unsubscribe: [email protected] website: http://groups.google.com/group/android-porting
