booting embinux android without mmc
shivap
my board's mmc interface is not working. i have managed to run kernel
with busybox based minimal rootfs. once the kernel boots up, using
OTG, folder sharing is possible. now my requirement is to boot android
without using mmc. is it possible to nfsboot using OTG ? is nandboot
possible with embinux? or any other method is available?
please reply
thanks
shivap
Harishkumar V
use NFS booting..
--
Follow us on Twitter - http://twitter.com/embinux
Follow us on Youtube - http://www.youtube.com/user/embinuxteam
Websites - http://embinux.com http://labs.embinux.org
To post to this group, send email to labs-e...@googlegroups.com
To unsubscribe from this group, send email to labs-embinux...@googlegroups.com
--
Thanks and Regards,
Harish Kumar. V
shivap
can u please point me where can i get info on nfsbooting
thanks
shivap
On Feb 18, 4:41 pm, Harishkumar V <harishpres...@gmail.com> wrote:
> Hi,
>
> use NFS booting..
>
>
>
> On Wed, Feb 17, 2010 at 8:34 PM, shivap <sshiremath2...@gmail.com> wrote:
> > hi all
>
> > my board's mmc interface is not working. i have managed to run kernel
> > with busybox based minimal rootfs. once the kernel boots up, using
> > OTG, folder sharing is possible. now my requirement is to boot android
> > without using mmc. is it possible to nfsboot using OTG ? is nandboot
> > possible with embinux? or any other method is available?
>
> > please reply
>
> > thanks
> > shivap
>
> > --
> > Follow us on Twitter -http://twitter.com/embinux
> > Follow us on Youtube -http://www.youtube.com/user/embinuxteam
> > Websites -http://embinux.comhttp://labs.embinux.org
>
> > To post to this group, send email to labs-e...@googlegroups.com
> > To unsubscribe from this group, send email to
> > labs-embinux...@googlegroups.com<labs-embinux%2Bunsu...@googlegroups.com>
shivap
i found a solution. i used ubifs for android rootfs and flashed at
nand partition mtd4 and flashed kernel to mtd3. with proper bootargs
now i am able to boot without mmc or nfs.
thanks
shivap
On Feb 18, 6:41 am, Harishkumar V <harishpres...@gmail.com> wrote:
> Hi,
>
> use NFS booting..
>
>
>
> On Wed, Feb 17, 2010 at 8:34 PM, shivap <sshiremath2...@gmail.com> wrote:
> > hi all
>
> > my board's mmc interface is not working. i have managed to run kernel
> > with busybox based minimal rootfs. once the kernel boots up, using
> > OTG, folder sharing is possible. now my requirement is to boot android
> > without using mmc. is it possible to nfsboot using OTG ? is nandboot
> > possible with embinux? or any other method is available?
>
> > please reply
>
> > thanks
> > shivap
>
> > --
> > Follow us on Twitter -http://twitter.com/embinux
> > Follow us on Youtube -http://www.youtube.com/user/embinuxteam
> > Websites -http://embinux.comhttp://labs.embinux.org
>
> > To post to this group, send email to labs-e...@googlegroups.com
> > To unsubscribe from this group, send email to
> > labs-embinux...@googlegroups.com<labs-embinux%2Bunsu...@googlegroups.com>
shivdas.gujare
Can you please, post your kernel dmesg?
Thanks and Regards,
Shivdas Gujare
On Sun, 21 Feb 2010 19:45:37 -0800 (PST), shivap
<sshirem...@gmail.com>
wrote:
shivap
i am using beagleboard rev c3. pls give me some time. the board is in
my office. i wil post the
dmesg as soon as possible.
thanks
shivap
On Feb 22, 12:37 pm, "shivdas.gujare" <shivdas.guj...@embinux.com>
wrote:
> Whats the platform you are using? Is it a beagleboard?
> Can you please, post your kernel dmesg?
>
> Thanks and Regards,
> Shivdas Gujare
>
> On Sun, 21 Feb 2010 19:45:37 -0800 (PST), shivap
shivap
the dmesg is given below,
NAND read: device 0 offset 0x280000, size 0x400000
4194304 bytes read: OK
## Booting kernel from Legacy Image at 80200000 ...
Image Name: Linux-2.6.29-omap1
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 2182984 Bytes = 2.1 MB
Load Address: 80008000
Entry Point: 80008000
Verifying Checksum ... OK
Loading Kernel Image ... OK
OK
Starting kernel ...
Uncompressing
Linux................................................................................
Linux version 2.6.29-omap1 (root@dd) (gcc version 4.4.1 (Sourcery G++
Lite 2009q3-67) ) #12 Thu Fe0
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 0xd7000000 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 androidboot.console=ttyS2
init=/init omapdss.def_disp=s
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: 112568KB available (4032K code, 724K data, 144K init)
Calibrating delay loop... 504.17 BogoMIPS (lpj=1970176)
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
net_namespace: 520 bytes
regulator: core version 0.5
NET: Registered protocol family 16
Found NAND on CS0
Registering NAND on CS0
OMAP DMA hardware revision 4.0
bio: create slab <bio-0> at 0
OMAP DSS rev 2.0
OMAP DISPC rev 3.0
OMAP VENC rev 2
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: 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
musb_hdrc: version 6.0, musb-dma, otg (peripheral+host), debug=0
musb_hdrc: USB OTG mode controller at d80ab000 using DMA, IRQ 92
NET: Registered protocol family 2
IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
TCP established hash table entries: 4096 (order: 3, 32768 bytes)
TCP bind hash table entries: 4096 (order: 2, 16384 bytes)
TCP: Hash tables configured (established 4096 bind 4096)
TCP reno registered
NET: Registered protocol family 1
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.
msgmni has been set to 220
alg: No test for stdrng (krng)
io scheduler noop registered
io scheduler anticipatory registered (default)
io scheduler deadline registered
io scheduler cfq registered
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
brd: module loaded
loop: module loaded
usbcore: registered new interface driver asix
usbcore: registered new interface driver cdc_ether
usbcore: registered new interface driver net1080
usbcore: registered new interface driver cdc_subset
usbcore: registered new interface driver zaurus
i2c /dev entries driver
Driver 'sd' needs updating - please use bus_type methods
omap2-nand driver initializing
NAND device: Manufacturer ID: 0x2c, Chip ID: 0xba (Micron NAND 256MiB
1,8V 16-bit)
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"
UBI: attaching mtd4 to ubi0
UBI: physical eraseblock size: 131072 bytes (128 KiB)
UBI: logical eraseblock size: 129024 bytes
UBI: smallest flash I/O unit: 2048
UBI: sub-page size: 512
UBI: VID header offset: 512 (aligned 512)
UBI: data offset: 2048
UBI: attached mtd4 to ubi0
UBI: MTD device name: "File System"
UBI: MTD device size: 249 MiB
UBI: number of good PEBs: 1994
UBI: number of bad PEBs: 2
UBI: max. allowed volumes: 128
UBI: wear-leveling threshold: 4096
UBI: number of internal volumes: 1
UBI: number of user volumes: 1
UBI: available PEBs: 0
UBI: total number of reserved PEBs: 1994
UBI: number of PEBs reserved for bad PEB handling: 19
UBI: max/mean erase counter: 2/1
usbmon: debugfs is not available
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
ehci-omap ehci-omap.0: OMAP-EHCI Host Controller
UBI: background thread "ubi_bgt0d" started, PID 375
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
usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
usb usb1: Product: OMAP-EHCI Host Controller
usb usb1: Manufacturer: Linux 2.6.29-omap1 ehci_hcd
usb usb1: SerialNumber: ehci-omap.0
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 cdc_acm
cdc_acm: v0.26:USB Abstract Control Model driver for USB modems and
ISDN adapters
Initializing USB Mass Storage driver...
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
g_ether gadget: using random self ethernet address
g_ether gadget: using random host ethernet address
usb0: MAC 06:83:c5:97:34:6d
usb0: HOST MAC 82:bb:82:86:5c:24
g_ether gadget: Ethernet Gadget, version: Memorial Day 2008
g_ether gadget: g_ether ready
musb_hdrc musb_hdrc: MUSB HDRC host driver
musb_hdrc musb_hdrc: new USB bus registered, assigned bus number 2
usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
usb usb2: Product: MUSB HDRC host driver
usb usb2: Manufacturer: Linux 2.6.29-omap1 musb-hcd
usb usb2: SerialNumber: musb_hdrc
usb usb2: configuration #1 chosen from 1 choice
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 1 port detected
twl4030_rtc twl4030_rtc: rtc core: registered twl4030_rtc as rtc0
twl4030_rtc twl4030_rtc: Power up reset detected.
twl4030_rtc twl4030_rtc: Enabling TWL4030-RTC.
mmci-omap-hs mmci-omap-hs.0: Failed to get debounce clock
usbcore: registered new interface driver usbhid
usbhid: v2.6:USB HID core driver
logger: created 64K log 'log_main'
logger: created 256K log 'log_events'
logger: created 64K log 'log_radio'
Advanced Linux Sound Architecture Driver Version 1.0.18a.
No device for DAI AD73311
No device for DAI AK4535
No device for DAI CS4270
No device for DAI PCM3008 HiFi
No device for DAI SSM2602
No device for DAI tlv320aic23
No device for DAI tlv320aic3x
No device for DAI twl4030
No device for DAI UDA134X
No device for DAI UDA1380
No device for DAI UDA1380
No device for DAI UDA1380
No device for DAI WM8510 HiFi
No device for DAI WM8580 PAIFRX
No device for DAI WM8580 PAIFTX
No device for DAI WM8728
No device for DAI WM8731
No device for DAI WM8750
No device for DAI WM8753 DAI 0
No device for DAI WM8753 DAI 1
No device for DAI WM8971
No device for DAI WM8990 ADC/DAC Primary
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
TWL4030 Audio Codec 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
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
Power Management for TI OMAP3.
VFP support v0.3: implementor 41 architecture 3 part 30 variant c rev
1
fbcvt: 1024x768@60: CVT Name - .786M3-R
Console: switching to colour frame buffer device 128x48
clock: clksel_round_rate_div: dpll4_m4_ck target_rate 86400000
clock: new_div = 5, new_rate = 86400000
twl4030_rtc twl4030_rtc: setting system clock to 2000-01-01 00:00:00
UTC (946684800)
g_ether gadget: high speed config #1: CDC Ethernet (ECM)
UBIFS: recovery needed
UBIFS: recovery completed
UBIFS: mounted UBI device 0, volume 0, name "rootfs"
UBIFS: file system size: 252887040 bytes (246960 KiB, 241 MiB, 1960
LEBs)
UBIFS: journal size: 9033728 bytes (8822 KiB, 8 MiB, 71 LEBs)
UBIFS: media format: 4 (latest is 4)
UBIFS: default compressor: lzo
UBIFS: reserved for root: 0 bytes (0 KiB)
VFS: Mounted root (ubifs filesystem) on device 253:1.
Freeing init memory: 144K
Warning: unable to open an initial console.
init: cannot open '/initlogo.rle'
init: cannot find '/system/bin/playmp3', disabling 'bootsound'
# warning: `rild' uses 32-bit capabilities (legacy support in use)
#
shivdas.gujare
was interested to know kernel version & ubifs initialization. I think, it
seems that
as you have mentioned previously, you use RevC2 BB, hence you didn't got
any nand related error's similar to
uncorrectable error : <3>end_request: I/O error, dev mtdblock0, sector 16
Buffer I/O error on device mtdblock0, logical block 2
end_request: I/O error, dev mtdblock0, sector 24
have you seen error's similar to above any time with your BB during use of
nand?
Did you created ubifs images or used any prebuilt images?
Thanks and Regards,
Shivdas Gujare
On Wed, 24 Feb 2010 08:47:29 -0800 (PST), shivap
<sshirem...@gmail.com>
wrote:
shivap
the error u mentioned was occuring when i was using angstrom rootfs
with kevin's omap pm kernel. but not with embinux. my board is not rev
C2, its rev C3 (i mentioned it my last post). and its working on both
rev C3 and B4 (sorry i forgot to mention). i created ubifs images
taking help from mtdutils website.
thanks
shivap
On Feb 25, 2:09 am, "shivdas.gujare" <shivdas.guj...@embinux.com>
wrote:
> Thanks for sharing dmesg.
>
> was interested to know kernel version & ubifs initialization. I think, it
> seems that
> as you have mentioned previously, you use RevC2 BB, hence you didn't got
> any nand related error's similar to
>
> uncorrectable error : <3>end_request: I/O error, dev mtdblock0, sector 16
> Buffer I/O error on device mtdblock0, logical block 2
> end_request: I/O error, dev mtdblock0, sector 24
>
> have you seen error's similar to above any time with your BB during use of
> nand?
> Did you created ubifs images or used any prebuilt images?
>
> Thanks and Regards,
> Shivdas Gujare
>
> On Wed, 24 Feb 2010 08:47:29 -0800 (PST), shivap
> ...
>
> read more »