[android-porting] beagleboard - rowboat-eclair kernel panic
I need your help. I got below kernel panic with Rowboat eclair built image. All build procedure had successfully ended. But, mmcblk0p2 never be mounted. Could someone please help me out ? Jooil - Texas Instruments X-Loader 1.4.2 (Feb 19 2009 - 12:01:24) Reading boot sector Loading u-boot.bin from nand U-Boot 2009.08 (Sep 14 2009 - 13:47:24) OMAP3530-GP ES3.0, CPU-OPP2 L3-165MHz OMAP3 Beagle board + LPDDR/NAND DRAM: 256 MB NAND: 256 MiB In:serial Out: serial Err: serial Board revision C Die ID #5f5304013f7906006017 Hit any key to stop autoboot: 5 \0x08\0x08\0x08 4 \0x08\0x08\0x08 3 \0x08\0x08\0x08 2 \0x08\0x08\0x08 1 \0x08\0x08\0x08 0 mmc1 is available reading boot.scr 377 bytes read Running bootscript from mmc ... ## Executing script at 8200 reading uImage 2413092 bytes read * Kernel: /dev/mmcblk0p1/uImage.bin * * RootFS: /dev/mmcblk0p2 * ## Booting kernel from Legacy Image at 8020 ... Image Name: Linux-2.6.32 Image Type: ARM Linux Kernel Image (uncompressed) Data Size:2413028 Bytes = 2.3 MB Load Address: 80008000 Entry Point: 80008000 Verifying Checksum ... OK Loading Kernel Image ... OK OK Starting kernel ... Uncompressing Linux... done, booting the kernel. Linux version 2.6.32 (r...@eepee-desktop) (gcc version 4.4.0 (GCC) ) #1 Tue Jul 20 18:31:24 KST 2010 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.0 (l2cache iva sgx neon isp ) SRAM: Mapped pa 0x4020 to va 0xfe40 size: 0x10 Reserving 4194304 bytes SDRAM for VRAM Built 1 zonelists in Zone order, mobility grouping on. Total pages: 65024 Kernel command line: androidboot.console=ttyS2 console=tty0 console=ttyS2,115200n8 root=/dev/mmcblk0p2 rw init=/init rootwait omapfb.video_mode=640x480mr...@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: 250240KB available (4152K code, 814K 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 33200 Hz GPMC revision 5.0 IRQ: Found an INTC at 0xfa20 (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 console [tty0] enabled Calibrating delay loop... 496.77 BogoMIPS (lpj=1937408) 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 musb_hdrc musb_hdrc: MUSB HDRC host driver musb_hdrc musb_hdrc: new USB bus registered, assigned bus number 1 hub 1-0:1.0: USB hub found hub 1-0:1.0: 1 port detected 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:
[android-porting] Re: Building SQLite
Is there a reason you feel the need to build it, rather than just taking a copy of one from a Google-provided emulator image? I don't know what needs to be done to build the version that comes with Android sources under Windows, but if you don't mind doing things manually, start by going to http://www.sqlite.org/download.html and downloading the top source code item on that page (the amalgamation package). I've succesfully used the Makefile pasted below this message to build this. You will need to edit the setting of the ANDROID_NDK variable, to point to the root of where you've installed the NDK. You will also need to make sure tabs are in place, etc., as is typical when copying/pasting a Makefile. Note that this Makefile will not work (without modification) on a Linux build host. The Linux version of the NDK uses some different internal paths. START OF MAKEFILE # Set 'ANDROID_NDK' to the location your NDK is installed ANDROID_NDK = C://android-ndk-1.6_r1 # determine the tools directory based on Windows install paths TOOLDIR=$(ANDROID_NDK)/build/prebuilt/windows/arm-eabi-4.2.1/bin # set tools based on TOOLDIR CC = $(TOOLDIR)/arm-eabi-gcc CPP = $(TOOLDIR)/arm-eabi-g++ STRIP = $(TOOLDIR)/arm-eabi-strip # prepare the NDK include path and library paths/options INCLUDES +=-I $(ANDROID_NDK)/build/platforms/android-3/arch-arm/usr/ include \ LIBS += -Wl,-rpath-link=$(ANDROID_NDK)/build/platforms/android-3/arch- arm/usr/lib \ -L$(ANDROID_NDK)/build/platforms/android-3/arch-arm/usr/lib \ -lc -lm -lstdc++ -Wl,--no-undefined -ldl \ -Wl,--gc-sections -Bdynamic -Wl,-z,nocopyreloc \ -Wl,-dynamic-linker,/system/bin/linker \ -Wl,-T,$(ANDROID_NDK)/build/prebuilt/windows/arm-eabi-4.2.1/arm- eabi/lib/ldscripts/armelf.x -Wl -nostdlib \ $(ANDROID_NDK)/build/platforms/android-3/arch-arm/usr/lib/ crtbegin_dynamic.o \ $(ANDROID_NDK)/build/platforms/android-3/arch-arm/usr/lib/ crtend_android.o CFLAGS += $(INCLUDES) CPPFLAGS += $(CFLAGS) LFLAGS = $(LIBS) APP = sqlite3 OBJS = shell.o sqlite3.o $(APP): $(OBJS) $(CC) -o $(APP) $(OBJS) $(LIBS) $(STRIP) $(APP) clean: rm -f $(OBJS) $(APP) END OF MAKEFILE On Jul 20, 3:54 pm, joec185 joec...@gmail.com wrote: Thanks for your response. I am trying to build it for android. My development machine is windows and I am running cygwin and the cygwin tools (i.e. gnu make). I have been able to build the native portion of the hello-jni sample for Android but have not been able to get very far building sqlite using the NDK. -- unsubscribe: android-porting+unsubscr...@googlegroups.com website: http://groups.google.com/group/android-porting
[android-porting] Re: Problem porting Android to OMAP
G2 grego...@... writes: Hello, I'm using Android on an OMAP3530 board and I have a problem as described by the log below. The same rootfs (Android 1.6) was working on my previous custom 2.6.29 kernel. Since I upgraded to 2.6.32, the system resets itself because of servicemanager is killed by the death of console. I ported all my custom 2.6.29 Android patches to my custom 2.6.32 tree. I have all the usual staging android drivers. My question is more: how can I debug more the situation in order to figure out what I'm missing? As it's the same rootfs and only the kernel has changed, I suspect something missing there. Thanks in advance for any pointer, Gregoire Uncompressing Hi Gregoire, Even we are facing the same problem. In the mean time could you resolve this issue or you are still facing the same ? It would be of great help if you could share the solution to this issue. Thanks, Shailesh -- unsubscribe: android-porting+unsubscr...@googlegroups.com website: http://groups.google.com/group/android-porting
[android-porting] Why are there thousands of warnings when building Android?!
Why are there thousands of warnings when building Android? I don't understand it. Is it because of the wide variety of compilers out there that people use that results in different output when building? Or is it because the code is so poorly written and developers just don't really give a damn? I know for a fact that when my team or me individually build(s) an application, we/I are/am sure to have clean code with no warnings about comparison between signed and unsigned..., x may have no been declared, format not a string literal and no formatting characters, expected type1 but argument is of type2... etc. I, for one, am very troubled by these thousands of warning when building Android. Can someone please enlighten me and explain to me why this is the case? Thank you, sws-vinpa. -- unsubscribe: android-porting+unsubscr...@googlegroups.com website: http://groups.google.com/group/android-porting
