Hi all, It gives the following error now!
Starting kernel ... Uncompressing Linux............................................................. .............................. done, booting the kernel. Linux version 2.6.29-omap1-g9985b01-dirty (js...@venux) (gcc version 4.4.1 (0xla b) ) #240 Mon Aug 10 20:01:27 CST 2009 CPU: ARMv7 Processor [411fc082] revision 2 (ARMv7), cr=10c5387f CPU: VIPT nonaliasing data cache, VIPT nonaliasing instruction cache Machine: OMAP3 Beagle Board Memory policy: ECC disabled, Data cache writeback OMAP3430 ES2.1 SRAM: Mapped pa 0x40200000 to va 0xe3000000 size: 0x100000 Reserving 12582912 bytes SDRAM for VRAM Built 1 zonelists in Zone order, mobility grouping on. Total pages: 32512 Kernel command line: console=ttyS2,115200n8 noinitrd root=/dev/mmcblk0p2 video=o mapfb.mode=dvi:1280x720mr...@50 init=/init rootfstype=ext3 rw rootdelay=1 nohz=o ff androidboot.console=ttyS2 Unknown boot option `androidboot.console=ttyS2': ignoring Clocking rate (Crystal/DPLL/ARM core): 26.0/332/500 MHz GPMC revision 5.0 IRQ: Found an INTC at 0xd8200000 (revision 4.0) with 96 interrupts Total of 96 interrupts on 1 active controller OMAP34xx GPIO hardware version 2.5 PID hash table entries: 512 (order: 9, 2048 bytes) OMAP clockevent source: GPTIMER12 at 32768 Hz Console: colour dummy device 80x30 Dentry cache hash table entries: 16384 (order: 4, 65536 bytes) Inode-cache hash table entries: 8192 (order: 3, 32768 bytes) Memory: 128MB = 128MB total Memory: 114588KB available (1504K code, 191K data, 1168K init) Calibrating delay loop... 320.37 BogoMIPS (lpj=1253376) Mount-cache hash table entries: 512 CPU: Testing write buffer coherency: ok regulator: core version 0.5 Found NAND on CS0 Registering NAND on CS0 OMAP DMA hardware revision 4.0 bio: create slab <bio-0> at 0 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 twl4030_mmc_init:362 twl4030_mmc_init:377 regulator: VMMC1: 1850 <--> 3150 mV normal standby regulator: VDAC: 1800 mV normal standby regulator: VUSB1V5: 1500 <--> 0 mV normal standby regulator: VUSB1V8: 1800 <--> 0 mV normal standby regulator: VUSB3V1: 3100 <--> 0 mV normal standby regulator: VPLL2: 1800 mV normal standby regulator: VSIM: 1800 <--> 3000 mV normal standby i2c_omap i2c_omap.3: bus 3 rev3.12 at 100 kHz SCSI subsystem initialized twl4030_usb twl4030_usb: Initialized TWL4030 USB module usbcore: registered new interface driver usbfs usbcore: registered new interface driver hub usbcore: registered new device driver usb omap-iommu omap-iommu.1: isp registered omap-iommu omap-iommu.2: msgmni has been set to 224 io scheduler noop registered io scheduler cfq registered (default) OMAP DSS rev 2.0 OMAP DISPC rev 3.0 OMAP VENC rev 2 Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled serial8250.0: ttyS0 at MMIO 0x4806a000 (irq = 72) is a ST16654 serial8250.0: ttyS1 at MMIO 0x4806c000 (irq = 73) is a ST16654 serial8250.0: ttyS2 at MMIO 0x49020000 (irq = 74) is a ST16654 console [ttyS2] enabled i2c /dev entries driver Driver 'sd' needs updating - please use bus_type methods omap2-nand driver initi NAND device: Manufacturer ID: 0x2c, Chip ID: 0xba (Micron NAND 256MiB 1,8V 16-bi t) cmdlinepart partition parsing not available Creating 5 MTD partitions on "omap2-nand": 0x000000000000-0x000000080000 : "X-Loader" 0x000000080000-0x000000260000 : "U-Boot" 0x000000260000-0x000000280000 : "U-Boot Env" 0x000000280000-0x000000680000 : "Kernel" 0x000000680000-0x000010000000 : "File System" VFP support v0.3: implementor 41 architecture 3 part 30 variant c rev 1 FIXME: no omap_set_dma_color_mode on 24xx DMA transaction error with device 0 Console: switching to colour frame buffer device 80x30 omapdss DPI: Could not find exact pixel clock. Requested 23500 kHz, got 24000 kH z Freeing init memory: 1168K mmc0: new high speed SD card at address b368 mmcblk0: mmc0:b368 SDC 970 MiB mmcblk0: p1 Welcome to 0xdroid Image Installer Mounting SD card... mount: mounting /dev/mmcblk0p1 on /mmcblk0p1 failed: Device or resource busy Press [Enter] to activate shell Erase NAND flash (File System) Input file is not page-aligned. Use the padding option. Data was only partially written due to error : Success /write_flash: exit: line 14: Illegal number: -1 Writing android-beagle.ubi into NAND flash... PLZ help!!!!!!!!!!!!!!!!!!!!! On Tue, Sep 15, 2009 at 7:42 PM, sanyanniesunney anniesunney < laurelsgal...@gmail.com> wrote: > Hi all, > > Which file is being referred here...i mean which file should be renamed? > how can i get a new position...is it through issuing the command given by > Pavan (i.e) > > > fatload mmc 0 80600000 <file_name> - to copy the contents of file > "file_name" from mmc device 0 to RAM address 80600000? > > here is filename uImage? > > Thanks a lot for your help.... > > > > On Tue, Sep 15, 2009 at 6:54 PM, Michael Trimarchi < > trimar...@gandalf.sssup.it> wrote: > >> >> Hi, >> >> sanyanniesunney anniesunney wrote: >> > Hi.... >> > I formatted my card such that it has only 1 partition and this >> > partition is of vfat type... >> > In this i copied the uImage(i had renamed as u suggested),MLO and >> > u-boot.bin >> > i also tried with the uImage and the binaries that they >> > provided,android-beagle.ubi and >> > 0xkernel-beagle.bin >> The uboot vfat subsystem has a series of BUG so if the uImage go in >> unreadeadble region just doesnt' >> work. Try to copy again and rename the oldfile, try to find some good >> position. Basically a fresh formatted >> partition gives no problem >> >> Michael >> > >> > >> > How can i verify whether i have formatted it correctly?i am sorry for >> > asking silly doubts but please help... >> > >> > thanks a lot! >> > >> > On Tue, Sep 15, 2009 at 6:17 PM, Jim Huang <jserv.tw >> > <http://jserv.tw>@gmail.com <http://gmail.com>> wrote: >> > >> > >> > 2009/9/15 sanyanniesunney anniesunney <laurelsgal...@gmail.com >> > <mailto:laurelsgal...@gmail.com>>: >> > > U-Boot 1.3.3 (Jul 10 2008 - 16:33:09) >> > > >> > > OMAP3530-GP rev 2, CPU-OPP2 L3-165MHz >> > > OMAP3 Beagle Board + LPDDR/NAND >> > > DRAM: 128 MB >> > > NAND: 256 MiB >> > > In: serial >> > > Out: serial >> > > Err: serial >> > > Audio Tone on Speakers ... complete >> > > Hit any key to stop autoboot: 0 >> > > reading uImage >> > > >> > >> > Ok, it recognizes the kernel image. >> > >> > > 693740 bytes read >> > > ## Booting kernel from Legacy Image at 80300000 ... >> > > Image Name: Linux-2.6.29-omap1-g9985b01-dirt >> > > Image Type: ARM Linux Kernel Image (uncompressed) >> > > Data Size: 1956720 Bytes = 1.9 MB >> > > Load Address: 80008000 >> > > Entry Point: 80008000 >> > > Verifying Checksum ... Bad Data CRC >> > > ERROR: can't get kernel image! >> > > >> > >> > Could you please clarify if your SD card is well formatted or not? >> > It usually comes with physical problem instead of software. >> > >> > Sincerely, >> > Jim Huang (jserv) >> > http://0xlab.org/ >> > >> > >> > >> > >> > > >> >> >> >> >> > --~--~---------~--~----~------------~-------~--~----~ unsubscribe: android-porting+unsubscr...@googlegroups.com website: http://groups.google.com/group/android-porting -~----------~----~----~----~------~----~------~--~---
