Hi Satish,
You can download pre-built Android images from our
website for OMAP3EVM Rev-D and Rev-G boards. Please check the
following URL.
http://www.mistralsolutions.com/assets/downloads/android.php
Try this image on your hardware and let me know if you still see
issues with USB cable.
Warm Regards,
Anil
On Thu, Jun 3, 2010 at 3:21 PM, PP <[email protected]> wrote:
> Hi Frank,
>
> Without the USB cable i am able to see the android home screen and
> play around like a normal android mobile, the kernel crashes only when
> i insert the usb cable.
> It is a Omap3530 EVM from Mistral solotions.
>
> Regards,
> Satish.
>
> On Jun 3, 12:38 pm, FrankG <[email protected]> wrote:
>> Hi Satish,
>>
>> an your hardware is from where ?
>>
>> What you see finally on the device without usb cable ?
>>
>> Good luck !
>>
>> Frank
>>
>> On 3 Jun., 06:02, PP <[email protected]> wrote:
>>
>> > Hi Frank,
>>
>> > Thanks for the reply.
>>
>> > The build did not crash without the USB cable. Without the USB cable
>> > connected to the host, i was able to get the Android boot screen.
>> > I got the prebuilt images from the site,http://code.google.com/p/rowboat/.
>> > Could there be some problem with the kernel image of the build?
>> > Should i download the source and rebuild it ?
>>
>> > Regrads,,
>> > Satish.
>>
>> > On Jun 2, 1:30 pm, FrankG <[email protected]> wrote:
>>
>> > > Did it crash without the cable ?
>>
>> > > From someone you got the flash tool, the details how to flash the
>> > > devise and I assume
>> > > also a orginal complete working build for this device.
>>
>> > > I would suggest you to a) run the device with the orginal build and
>> > > save the kernel messages and then b) run your own build and save
>> > > them and after that compare them to see what can be the problem.
>>
>> > > You should also check with modinfo the Kernel Objects (*.ko), maybe
>> > > "vermagic"
>> > > is modified through your Source Control System ?
>>
>> > > Good luck ! Frank
>>
>> > > On 1 Jun., 12:54, PP <[email protected]> wrote:
>>
>> > > > Hi All,
>>
>> > > > I haveOmap3530evm running Android 2.1. I want to install application
>> > > > on the evm, so i connected the evm to the host through the USB OTG
>> > > > cable, but the kernel is crashing. Kindly help me out in sorting this
>> > > > issue. Find the log below:
>>
>> > > > OMAP3_EVM #
>> > > > OMAP3_EVM #
>> > > > OMAP3_EVM # setenv bootargs 'init=/init console=ttyS0,115200n8 root=/
>> > > > dev/mmcblk
>> > > > 0p2 rw rootwait mem=256M noinitrd androidboot.console=ttyS0
>> > > > mpurate=720'
>> > > > OMAP3_EVM # setenv bootcmd 'mmcinit; fatload mmc 0 0x80100000 uImage;
>> > > > bootm 0x80
>> > > > 100000'
>> > > > OMAP3_EVM # boot
>> > > > reading uImage
>>
>> > > > 2489828 bytes read
>> > > > ## Booting kernel from Legacy Image at 80100000 ...
>> > > > Image Name: Linux-2.6.32
>> > > > Image Type: ARM Linux Kernel Image (uncompressed)
>> > > > Data Size: 2489764 Bytes = 2.4 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...@khasim-laptop) (gcc version 4.4.0 (GCC) )
>> > > > #2 Thu May
>> > > > 20 18:31:19 IST 2010
>> > > > CPU: ARMv7 Processor [411fc083] revision 3 (ARMv7), cr=10c53c7f
>> > > > CPU: VIPT nonaliasing data cache, VIPT nonaliasing instruction cache
>> > > > Machine: OMAP3 EVM
>> > > > 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: init=/init console=ttyS0,115200n8 root=/dev/
>> > > > mmcblk0p2 rw ro
>> > > > otwait mem=256M noinitrd androidboot.console=ttyS0 mpurate=720
>> > > > 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: 256MB = 256MB total
>> > > > Memory: 250112KB available (4292K code, 825K data, 176K 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: GPTIMER1 at 32768 Hz
>> > > > Console: colour dummy device 80x30
>> > > > Calibrating delay loop... 499.92 BogoMIPS (lpj=1949696)
>> > > > Mount-cache hash table entries: 512
>> > > > CPU: Testing write buffer coherency: ok
>> > > > regulator: core version 0.5
>> > > > NET: Registered protocol family 16
>> > > > Target VDD1 OPP = 6, VDD2 OPP = 3
>> > > > omap3evmdc: Driver registration complete
>> > > > 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: VMMC1: 1850 <--> 3150 mV normal standby
>> > > > regulator: VDAC: 1800 mV normal standby
>> > > > regulator: VAUX2_4030: 2800 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 400 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
>> > > > 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: MUSB HDRC host driver
>> > > > usb usb1: Manufacturer: Linux 2.6.32 musb-hcd
>> > > > usb usb1: SerialNumber: musb_hdrc
>> > > > 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
>> > > > OMAP35x Linux PSP version 03.00.00.05 (OMAP3EVM)
>> > > > 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 488
>> > > > 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
>> > > > OMAP DSI rev 1.0
>> > > > Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
>> > > > serial8250.0: ttyS0 at MMIO 0x4806a000 (irq = 72) is a ST16654
>> > > > console [ttyS0] enabled
>> > > > serial8250.1: ttyS1 at MMIO 0x4806c000 (irq = 73) is a ST16654
>> > > > serial8250.2: ttyS2 at MMIO 0x49020000 (irq = 74) is a ST16654
>> > > > brd: module loaded
>> > > > loop: module loaded
>> > > > omap2-nand driver initializing
>> > > > NAND device: Manufacturer ID: 0x2c, Chip ID: 0xba (Micron NAND 256MiB
>> > > > 1,8V 16-bi
>> > > > t)
>> > > > Creating 5 MTD partitions on "omap2-nand.0":
>> > > > 0x000000000000-0x000000080000 : "xloader-nand"
>> > > > 0x000000080000-0x000000240000 : "uboot-nand"
>> > > > 0x000000240000-0x000000280000 : "params-nand"
>> > > > 0x000000280000-0x000000780000 : "linux-nand"
>> > > > 0x000000780000-0x000010000000 : "jffs2-nand"
>> > > > OneNAND driver initializing
>> > > > omap2-onenand omap2-onenand: Cannot request GPMC CS
>> > > > omap2-onenand: probe of omap2-onenand failed with error -16
>> > > > smsc911x: Driver version 2008-10-21.
>> > > > smsc911x-mdio: probed
>> > > > eth0: attached PHY driver [Generic PHY] (mii_bus:phy_addr=ffffffff:01,
>> > > > irq=-1)
>> > > > net eth0: MAC Address: 00:50:c2:7e:91:4a
>> > > > usbcore: registered new interface driver cdc_ether
>> > > > usbcore: registered new interface driver dm9601
>> > > > 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 2
>> > > > ehci-omap ehci-omap.0: irq 77, io mem 0x48064800
>> > > > ehci-omap ehci-omap.0: USB 2.0 started, EHCI 1.00
>> > > > 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: OMAP-EHCI Host Controller
>> > > > usb usb2: Manufacturer: Linux 2.6.32 ehci_hcd
>> > > > usb usb2: SerialNumber: ehci-omap.0
>> > > > hub 2-0:1.0: USB hub found
>> > > > hub 2-0:1.0: 3 ports detected
>> > > > Initializing USB Mass Storage driver...
>> > > > usbcore: registered new interface driver usb-storage
>> > > > USB Mass Storage support registered.
>> > > > usbcore: registered new interface driver usbtest
>> > > > android init
>> > > > f_acm init
>> > > > android_register_function acm
>> > > > f_adb init
>> > > > android_register_function adb
>> > > > f_mass_storage init
>> > > > android_register_function usb_mass_storage
>> > > > f_rndis init
>> > > > android_register_function rndis
>> > > > input: TWL4030 Keypad as /devices/platform/i2c_omap.1/i2c-1/1-004a/
>> > > > twl4030_keypa
>> > > > d/input/input0
>> > > > ads7846 spi1.0: touchscreen, irq 335
>> > > > input: ADS7846 Touchscreen as
>>
>> ...
>>
>> read more »
>
> --
> You received this message because you are subscribed to the Google
> Groups "Android Developers" 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/android-developers?hl=en
--
You received this message because you are subscribed to the Google
Groups "Android Developers" 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/android-developers?hl=en
