Hello,
Do any pre-built image archives work on the BeagleBoard XM Rev C?
I recently obtained a BeagleBoard XM Rev C and cannot find a pre-built Android or Angstrom image that works. Symptoms are either that the USB keyboard and mouse inputs do not work, or nothing visible on the DVI display output (Gingerbread 2.3.4).
Regards,
WilB
bought from Digikey?? didnt you get a bootable microSD.
There are downloadable images here
http://www.circuitco.com/support/index.php?title=Circuitco_Support_Wiki
http://circuitco.com/support/files/Beagleboard/ImageFiles/beagle-rev-c5-3.2GB-r1.img.zip
from, http://www.circuitco.com/support/index.php?title=Main_Page#BEAGLEBOARD_IMAGE_FILES
Regards
Joel
Hi,
Please post on the beagle list
Hi Joel,
Thanks for your reply. These image at the link seems to reflect the test Angstrom image that came with the board that works fine but has very limited functionality.
I would like a fully functional pre-built OS image of Angstrom, Android, or Ubuntu that works on the BeagleBoard XM Rev C. The images I have tried either lack USB input or DVI Video.
Regards,
Wil Blake
I have an image referenced here [1] that works on the -xM Rev C.
–Mark
Hi Mark,
Is the image a Test image with limited functionality or a full operating system image? I have the pre-built test image working fine, however it has very limited functionality and just confirms that the board works.
Perhaps I ought to change the subject from "pre-built image" to "fully functional pre-built OS Image for Android, Angstrom, or Ubuntu."
Thank you,
Wil
Angstrom:
http://narcissus.angstrom-distribution.org/ and pick what you want for
features in the selection
Ubuntu:
http://elinux.org/BeagleBoardUbuntu#Demo_Image and install what you
want after it's booted..
Android:
build it on your own with rowboat, it should now work the
"rowboat-gingerbread.xml" manifest
Regards,
Go Find the Android or Ubuntu image on TI website for best expeience
— On Wed, 8/17/11, Wil Blake wblake@emsys.net wrote:
> From: Wil Blake wblake@emsys.net
> Subject: Re: [beagleboard] BeagleBoard XM Rev C - do any pre-built images work?
> To: beagleboard@googlegroups.com
> Date: Wednesday, August 17, 2011, 10:52 AM
>
> Hi Mark,
>
> Is the image a Test image with limited functionality or a full operating system image? I have the pre-built test image working fine, however it has very limited functionality and just confirms that the board works.
>
> Perhaps I ought to change the subject from “pre-built image” to “fully functional pre-built OS Image for Android, Angstrom, or Ubuntu.”
>
> Thank you,
> Wil
>
> On 8/17/2011 11:26 AM, Mark A. Yoder wrote:
> > I have an image referenced here [1] that works on the -xM Rev C.
> >
> > --Mark
> >
> > [1] http://elinux.org/Getting_a_Workshop_SD_Image
>
> – You received this message because you are subscribed to the Google Groups “Beagle Board” group.
> To post to this group, send email to beagleboard@googlegroups.com.
> To unsubscribe from this group, send email to beagleboard+unsubscribe@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/beagleboard?hl=en.
|
Hi Joel,
Thanks for your reply. These image at the link seems to reflect the test Angstrom image that came with the board that works fine but has very limited functionality.
I would like a fully functional pre-built OS image of Angstrom, Android, or Ubuntu that works on the BeagleBoard XM Rev C. The images I have tried either lack USB input or DVI Video.
Android pre-built image for Beagle-XM http://software-dl.ti.com/dsps/dsps_public_sw/sdo_tii/TI_Android_DevKit/TI_Android_GingerBread_2_3_4_DevKit_2_1/exports/beagleboard-xm.tar.gz
User guide http://processors.wiki.ti.com/index.php/TI-Android-GingerBread-2.3.4-DevKit-2.1_UserGuide
Regards,
Amit Pundir
Hi Mark,
Is the image a Test image with limited functionality or a full operating system image? I have the pre-built test image working fine, however it has very limited functionality and just confirms that the board works.
Perhaps I ought to change the subject from “pre-built image” to “fully functional pre-built OS Image for Android, Angstrom, or Ubuntu.”
Fully functional pre-built Android image http://software-dl.ti.com/dsps/dsps_public_sw/sdo_tii/TI_Android_DevKit/TI_Android_GingerBread_2_3_4_DevKit_2_1/exports/beagleboard-xm.tar.gz
User guide http://processors.wiki.ti.com/index.php/TI-Android-GingerBread-2.3.4-DevKit-2.1_UserGuide
Regards,
Amit Pundir
Amit,
I have unsuccessfully tried several times to use the pre-built XM Rev C GingerBread 2.3.4 image via the mkmmc-android.sh script. The resulting image never generates DVI output but I attached the console / adb output.
Regards,
Wil Blake
hw-breakpoint: debug architecture 0x4 unsupported.
OMAP DMA hardware revision 5.0
bio: create slab at 0
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
omap_device: omap_i2c.1: new worst case activate latency 0: 30517
omap_i2c omap_i2c.1: bus 1 rev4.0 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 at 3000 mV normal standby
regulator: VDAC: 1800 mV normal standby
regulator: VDVI: 1800 mV normal standby
regulator: VSIM: 1800 <–> 3000 mV at 1800 mV normal standby
regulator: VAUX3: 1800 mV normal standby
regulator: VAUX4: 1800 mV normal standby
omap_device: omap_i2c.1: new worst case deactivate latency 0: 30517
omap_i2c omap_i2c.2: bus 2 rev4.0 at 400 kHz
omap_i2c omap_i2c.3: bus 3 rev4.0 at 100 kHz
Advanced Linux Sound Architecture Driver Version 1.0.23.
Switching to clocksource 32k_counter
musb-hdrc: version 6.0, otg (peripheral+host), debug=0
musb-hdrc musb-hdrc.0: dma type: dma-inventra
musb-hdrc musb-hdrc.0: 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
NetWinder Floating Point Emulator V0.97 (double precision)
omap-iommu omap-iommu.0: isp registered
AM37x/DM37x Linux PSP version 04.02.00.07 (OMAP3BEAGLE)
ashmem: initialized
VFS: Disk quotas dquot_6.5.2
Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
JFFS2 version 2.2. (NAND) (SUMMARY) © 2001-2006 Red Hat, Inc.
msgmni has been set to 479
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
omap_uart.0: ttyO0 at MMIO 0x4806a000 (irq = 72) is a OMAP UART0
omap_uart.1: ttyO1 at MMIO 0x4806c000 (irq = 73) is a OMAP UART1
omap_uart.2: ttyO2 at MMIO 0x49020000 (irq = 74) is a OMAP UART2
console [ttyO2] enabled
omap_uart.3: ttyO3 at MMIO 0x49042000 (irq = 80) is a OMAP UART3
brd: module loaded
loop: module loaded
mtdoops: mtd device (mtddev=name/number) must be supplied
omap2-nand driver initializing
No NAND device found.
No NAND device found.
OneNAND driver initializing
usbcore: registered new interface driver asix
usbcore: registered new interface driver cdc_ether
usbcore: registered new interface driver smsc95xx
usbcore: registered new interface driver net1080
usbcore: registered new interface driver cdc_subset
usbcore: registered new interface driver zaurus
ehci_hcd: USB 2.0 ‘Enhanced’ Host Controller (EHCI) Driver
ehci-omap.0 supply hsusb0 not found, using dummy regulator
ehci-omap.0 supply hsusb1 not found, using dummy regulator
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
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.37-g06ebbba ehci_hcd
usb usb1: SerialNumber: ehci-omap.0
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: c053ff2c
android_bind
android_usb gadget: android_usb ready
musb-hdrc musb-hdrc.0: MUSB HDRC host driver
musb-hdrc musb-hdrc.0: 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.37-g06ebbba musb-hcd
usb usb2: SerialNumber: musb-hdrc.0
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: twl4030_pwrbutton as /devices/platform/omap/omap_i2c.1/i2c-1/1-0049/twl4030_pwrbutton/input/input1
using rtc device, twl_rtc, for alarms
twl_rtc twl_rtc: rtc core: registered twl_rtc as rtc0
i2c /dev entries driver
Linux media interface: v0.10
Linux video capture interface: v2.00
omap3isp supply VDD_CSIPHY1 not found, using dummy regulator
omap3isp supply VDD_CSIPHY2 not found, using dummy regulator
omap3isp omap3isp: Revision 15.0 found
omap-iommu omap-iommu.0: isp: version 1.1
mt9v113 2-003c: chip id mismatch read 0x0, expecting 0x2280
isp_register_subdev_group: Unable to register subdev mt9v113
omap_device: omap_wdt.-1: new worst case activate latency 0: 30517
OMAP Watchdog Timer Rev 0x31: initial timeout 60 sec
twl4030_wdt twl4030_wdt: Failed to register misc device
twl4030_wdt: probe of twl4030_wdt failed with error -16
device-mapper: uevent: version 1.0.3
device-mapper: ioctl: 4.18.0-ioctl (2010-06-29) initialised: 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’ usbcore: registered new interface driver snd-usb-audio OMAP3 Beagle/Devkit8000 SoC init usb 1-2: new high speed USB device using ehci-omap and address 2 asoc: twl4030-hifi <-> omap-mcbsp-dai.1 mapping ok ALSA device list: #0: omap3beagle oprofile: hardware counters not available oprofile: using timer interrupt. TCP cubic registered Initializing XFRM netlink socket NET: Registered protocol family 17 NET: Registered protocol family 15 Registering the dns_resolver key type VFP support v0.3: implementor 41 architecture 3 part 30 variant c rev 3 ThumbEE CPU extension supported. Power Management for TI OMAP3. smartreflex smartreflex.0: omap_sr_probe: SmartReflex driver initialized smartreflex smartreflex.1: omap_sr_probe: SmartReflex driver initialized SmartReflex Class3 initialized clock: disabling unused clocks to save power platform mpu.0: omap_voltage_scale: Already at the requestedrate 600000000 usb 1-2: New USB device found, idVendor=0424, idProduct=9514 usb 1-2: New USB device strings: Mfr=0, Product=0, SerialNumber=0 hub 1-2:1.0: USB hub found hub 1-2:1.0: 5 ports detected regulator_init_complete: incomplete constraints, leaving VDAC on twl_rtc twl_rtc: setting system clock to 2000-01-01 00:08:43 UTC (946685323) omap_vout omap_vout: Buffer Size = 3686400 omap_vout omap_vout: : registered and initialized video device 15 omap_vout omap_vout: Buffer Size = 3686400 omap_vout omap_vout: : registered and initialized video device 16 Waiting 1sec before mounting root device… mmc0: host does not support reading read-only switch. assuming write-enable. mmc0: new high speed SDHC card at address 1234 mmcblk0: mmc0:1234 SA04G 3.67 GiB mmcblk0: p1 p2 p3 usb 1-2.1: new high speed USB device using ehci-omap and address 3 usb 1-2.1: New USB device found, idVendor=0424, idProduct=ec00 usb 1-2.1: New USB device strings: Mfr=0, Product=0, SerialNumber=0 smsc95xx v1.0.4 smsc95xx 1-2.1:1.0: usb0: register ‘smsc95xx’ at usb-ehci-omap.0-2.1, smsc95xx USB 2.0 Ethernet, b2:8a:f9:ec:54:4a usb 1-2.2: new low speed USB device using ehci-omap and address 4 usb 1-2.2: New USB device found, idVendor=062a, idProduct=0201 usb 1-2.2: New USB device strings: Mfr=0, Product=1, SerialNumber=0 usb 1-2.2: Product: USB-compliant keyboard input: USB-compliant keyboard as /devices/platform/ehci-omap.0/usb1/1-2/1-2.2/1-2.2:1.0/input/input2 generic-usb 0003:062A:0201.0001: input: USB HID v1.10 Keyboard [USB-compliant keyboard] on usb-ehci-omap.0-2.2/input0 input: USB-compliant keyboard as /devices/platform/ehci-omap.0/usb1/1-2/1-2.2/1-2.2:1.1/input/input3 generic-usb 0003:062A:0201.0002: input: USB HID v1.10 Mouse [USB-compliant keyboard] on usb-ehci-omap.0-2.2/input1 usb 1-2.3: new low speed USB device using ehci-omap and address 5 usb 1-2.3: New USB device found, idVendor=046d, idProduct=c404 usb 1-2.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0 usb 1-2.3: Product: Trackball usb 1-2.3: Manufacturer: Logitech input: Logitech Trackball as /devices/platform/ehci-omap.0/usb1/1-2/1-2.3/1-2.3:1.0/input/input4 generic-usb 0003:046D:C404.0003: input: USB HID v1.10 Mouse [Logitech Trackball] on usb-ehci-omap.0-2.3/input0 EXT3-fs: barriers not enabled kjournald starting. Commit interval 5 seconds EXT3-fs (mmcblk0p2): using internal journal EXT3-fs (mmcblk0p2): recovery complete EXT3-fs (mmcblk0p2): mounted filesystem with ordered data mode VFS: Mounted root (ext3 filesystem) on device 179:2. Freeing init memory: 204K init (1): /proc/1/oom_adj is deprecated, please use /proc/1/oom_score_adj instead. init: cannot find ‘/system/etc/install-recovery.sh’, disabling ‘flash_recovery’ enabling adb adb_open # warning: `zygote’ uses 32-bit capabilities (legacy support in use) binder: release 1413:1441 transaction 2775 out, still active binder: release 1413:1442 transaction 2795 out, still active binder: release 1413:1467 transaction 3018 out, still active binder: release 1413:1470 transaction 3033 out, still active binder: 1241:1448 transaction failed 29189, size 28-4 binder: send failed reply for transaction 3018, target dead binder: 1241:1268 transaction failed 29189, size 28-4 binder: send failed reply for transaction 2775, target dead binder: 1241:1443 transaction failed 29189, size 28-4 binder: send failed reply for transaction 2795, target dead binder: 1241:1266 transaction failed 29189, size 8-0 binder: send failed reply for transaction 3033, target dead On 8/18/2011 1:31 AM, Amit Pundir wrote:
It’s an Angstrom image with many thinks already installed. I’ve used to to run some workshops. It is even setup to compile things natively for the DSP via c6run.
–Mark
Amit,
I have unsuccessfully tried several times to use the pre-built XM Rev C GingerBread 2.3.4 image via the mkmmc-android.sh script. The resulting image never generates DVI output but I attached the console / adb output.
Please run logcat from Android console and attach the output.
Regards,
Amit Pundir
I/ActivityThread( 1334): Pub com.android.exchange.provider: com.android.exchange.provider.ExchangeProvider
D/dalvikvm( 1100): GC_CONCURRENT freed 944K, 44% free 4370K/7751K, external 2465K/3665K, paused 3ms+5ms
D/dalvikvm( 1100): GC_EXPLICIT freed 59K, 44% free 4374K/7751K, external 2465K/3665K, paused 77ms
E/ActivityManager( 1100): ANR in com.android.email
E/ActivityManager( 1100): Reason: Broadcast of Intent { act=android.intent.action.BOOT_COMPLETED cmp=com.android.email/.service.EmailBroadcastReceiver }
E/ActivityManager( 1100): Load: 4.77 / 1.58 / 0.56
E/ActivityManager( 1100): CPU usage from 0ms to 5015ms later with 99% awake:
E/ActivityManager( 1100): 6.6% 1100/system_server: 5.4% user + 1.2% kernel / faults: 391 minor
E/ActivityManager( 1100): 1.8% 1001/zygote: 1.4% user + 0.4% kernel / faults: 124 minor
E/ActivityManager( 1100): 1.2% 1391/zygote: 1% user + 0.2% kernel / faults: 2872 minor
E/ActivityManager( 1100): 0.4% 1278/android.process.acore: 0.2% user + 0.2% kernel / faults: 31 minor
E/ActivityManager( 1100): 0.4% 1334/zygote: 0.4% user + 0% kernel / faults: 313 minor 9 major
E/ActivityManager( 1100): 0% 3/ksoftirqd/0: 0% user + 0% kernel
E/ActivityManager( 1100): 0% 1231/com.android.phone: 0% user + 0% kernel / faults: 32 minor
E/ActivityManager( 1100): 0% 1235/com.android.systemui: 0% user + 0% kernel / faults: 1 minor
E/ActivityManager( 1100): +0% 1402/sh: 0% user + 0% kernel
E/ActivityManager( 1100): 100% TOTAL: 9.5% user + 2.1% kernel + 88% iowait
E/ActivityManager( 1100): CPU usage from 4478ms to 4999ms later:
E/ActivityManager( 1100): 1.9% 1100/system_server: 0% user + 1.9% kernel / faults: 3 minor
E/ActivityManager( 1100): 5.7% 1124/ActivityManager: 1.9% user + 3.8% kernel
E/ActivityManager( 1100): 100% TOTAL: 0% user + 3.8% kernel + 96% iowait
I/Process ( 1100): Sending signal. PID: 1334 SIG: 9
I/ActivityManager( 1100): Process com.android.email (pid 1334) has died.
I/ActivityThread( 1391): Pub media: com.android.providers.media.MediaProvider
W/ActivityManager( 1100): Timeout of broadcast BroadcastRecord{407772a8 android.intent.action.BOOT_COMPLETED} - receiver=android.os.BinderProxy@4076ce68, started 10004ms ago
W/ActivityManager( 1100): Receiver during timeout: ResolveInfo{407711e8 com.android.providers.media.MediaScannerReceiver p=0 o=0 m=0x108000}
I/Process ( 1100): Sending signal. PID: 1391 SIG: 3
I/dalvikvm( 1391): threadid=4: reacting to signal 3
I/Process ( 1100): Sending signal. PID: 1100 SIG: 3
I/dalvikvm( 1100): threadid=4: reacting to signal 3
I/dalvikvm( 1100): Wrote stack traces to ‘/data/anr/traces.txt’
I/Process ( 1100): Sending signal. PID: 1231 SIG: 3
I/dalvikvm( 1231): threadid=4: reacting to signal 3
I/dalvikvm( 1231): Wrote stack traces to ‘/data/anr/traces.txt’
I/Process ( 1100): Sending signal. PID: 1235 SIG: 3
I/dalvikvm( 1235): threadid=4: reacting to signal 3
I/dalvikvm( 1235): Wrote stack traces to ‘/data/anr/traces.txt’
D/dalvikvm( 1391): GC_CONCURRENT freed 396K, 51% free 2773K/5639K, external 716K/1038K, paused 3ms+3ms
D/dalvikvm( 1100): GC_EXPLICIT freed 734K, 44% free 4365K/7751K, external 2465K/3665K, paused 54ms
V/MediaProvider( 1391): Attached volume: internal
V/MediaProvider( 1391): /mnt/sdcard volume ID: 188847328
I/Process ( 1100): Sending signal. PID: 1391 SIG: 9
E/ActivityManager( 1100): ANR in android.process.media
E/ActivityManager( 1100): Reason: Broadcast of Intent { act=android.intent.action.BOOT_COMPLETED cmp=com.android.providers.media/.MediaScannerReceiver }
E/ActivityManager( 1100): Load: 4.87 / 1.66 / 0.59
E/ActivityManager( 1100): CPU usage from 4993ms to -1296ms ago:
E/ActivityManager( 1100): 4.2% 1100/system_server: 3.4% user + 0.7% kernel / faults: 220 minor
E/ActivityManager( 1100): 1.7% 1391/zygote: 1.4% user + 0.3% kernel / faults: 1029 minor 3 major
E/ActivityManager( 1100): 0% 4/kworker/0:0: 0% user + 0% kernel
E/ActivityManager( 1100): 0% 56/irq/74-serial i: 0% user + 0% kernel
E/ActivityManager( 1100): 0% 634/mmcqd/0: 0% user + 0% kernel
E/ActivityManager( 1100): 0% 1073/logcat: 0% user + 0% kernel
E/ActivityManager( 1100): 0.1% 1278/android.process.acore: 0% user + 0.1% kernel / faults: 1 minor
E/ActivityManager( 1100): +0% 1404/sh: 0% user + 0% kernel
E/ActivityManager( 1100): 100% TOTAL: 4.4% user + 1.5% kernel + 93% iowait
E/ActivityManager( 1100): CPU usage from 760ms to 1278ms later:
E/ActivityManager( 1100): 3.8% 1391/android.process.media: 3.8% user + 0% kernel / faults: 335 minor
E/ActivityManager( 1100): 3.8% 1391/d.process.media: 1.9% user + 1.9% kernel
E/ActivityManager( 1100): 1.9% 1395/HeapWorker: 1.9% user + 0% kernel
E/ActivityManager( 1100): 1.9% 1399/Compiler: 1.9% user + 0% kernel
E/ActivityManager( 1100): 1.9% 1100/system_server: 1.9% user + 0% kernel
E/ActivityManager( 1100): 1.9% 1124/ActivityManager: 1.9% user + 0% kernel
E/ActivityManager( 1100): 100% TOTAL: 7.6% user + 1.9% kernel + 90% iowait
I/ActivityManager( 1100): Process android.process.media (pid 1391) has died.
I/ActivityManager( 1100): Start proc android.process.media for restart android.process.media: pid=1414 uid=10015 gids={1015, 2001, 3003}
I/ActivityManager( 1100): Start proc com.android.mms for broadcast com.android.mms/.transaction.MmsSystemEventReceiver: pid=1416 uid=10028 gids={3003, 1015}
I/ActivityThread( 1414): Pub media: com.android.providers.media.MediaProvider
V/MediaProvider( 1414): Attached volume: internal
V/MediaProvider( 1414): /mnt/sdcard volume ID: 188847328
V/MediaProvider( 1414): Attached volume: external
I/ActivityThread( 1414): Pub downloads: com.android.providers.downloads.DownloadProvider
I/ActivityThread( 1414): Pub drm: com.android.providers.drm.DrmProvider
I/ActivityThread( 1416): Pub com.android.mms.SuggestionsProvider: com.android.mms.SuggestionsProvider
W/ActivityManager( 1100): Timeout of broadcast BroadcastRecord{407772a8 android.intent.action.BOOT_COMPLETED} - receiver=android.os.BinderProxy@40779580, started 10004ms ago
W/ActivityManager( 1100): Receiver during timeout: ResolveInfo{40771268 com.android.mms.transaction.MmsSystemEventReceiver p=0 o=0 m=0x108000}
I/Process ( 1100): Sending signal. PID: 1416 SIG: 3
I/dalvikvm( 1416): threadid=4: reacting to signal 3
I/dalvikvm( 1416): Wrote stack traces to ‘/data/anr/traces.txt’
I/Process ( 1100): Sending signal. PID: 1100 SIG: 3
I/dalvikvm( 1100): threadid=4: reacting to signal 3
I/dalvikvm( 1100): Wrote stack traces to ‘/data/anr/traces.txt’
I/Process ( 1100): Sending signal. PID: 1231 SIG: 3
I/dalvikvm( 1231): threadid=4: reacting to signal 3
I/dalvikvm( 1231): Wrote stack traces to ‘/data/anr/traces.txt’
I/Process ( 1100): Sending signal. PID: 1235 SIG: 3
I/dalvikvm( 1235): threadid=4: reacting to signal 3
I/dalvikvm( 1235): Wrote stack traces to ‘/data/anr/traces.txt’
D/dalvikvm( 1100): GC_EXPLICIT freed 862K, 46% free 4244K/7751K, external 2465K/3665K, paused 54ms
I/Process ( 1100): Sending signal. PID: 1416 SIG: 9
E/ActivityManager( 1100): ANR in com.android.mms
E/ActivityManager( 1100): Reason: Broadcast of Intent { act=android.intent.action.BOOT_COMPLETED cmp=com.android.mms/.transaction.MmsSystemEventReceiver }
E/ActivityManager( 1100): Load: 4.82 / 1.8 / 0.66
E/ActivityManager( 1100): CPU usage from 12300ms to 0ms ago:
E/ActivityManager( 1100): 0.9% 1100/system_server: 0.7% user + 0.2% kernel / faults: 138 minor
E/ActivityManager( 1100): 0.2% 634/mmcqd/0: 0% user + 0.2% kernel
E/ActivityManager( 1100): 0% 56/irq/74-serial i: 0% user + 0% kernel
E/ActivityManager( 1100): 0% 996/servicemanager: 0% user + 0% kernel
E/ActivityManager( 1100): 0% 1001/zygote: 0% user + 0% kernel / faults: 26 minor
E/ActivityManager( 1100): 0% 1073/logcat: 0% user + 0% kernel
E/ActivityManager( 1100): 0% 1231/com.android.phone: 0% user + 0% kernel / faults: 45 minor
E/ActivityManager( 1100): +0% 1414/android.process.media: 0% user + 0% kernel
E/ActivityManager( 1100): +0% 1416/com.android.mms: 0% user + 0% kernel
E/ActivityManager( 1100): +0% 1449//init: 0% user + 0% kernel
E/ActivityManager( 1100): 99% TOTAL: 2.9% user + 1.9% kernel + 95% iowait
E/ActivityManager( 1100): CPU usage from 204ms to 720ms later:
E/ActivityManager( 1100): 100% TOTAL: 1.9% user + 1.9% kernel + 96% iowait
I/ActivityManager( 1100): Process com.android.mms (pid 1416) has died.
I/ActivityManager( 1100): Start proc com.android.bluetooth for broadcast com.android.bluetooth/.opp.BluetoothOppReceiver: pid=1460 uid=10030 gids={3003, 3002, 3001, 1015}
I/ActivityThread( 1460): Pub com.android.bluetooth.opp: com.android.bluetooth.opp.BluetoothOppProvider
I/ActivityManager( 1100): Start proc com.android.providers.calendar for broadcast com.android.providers.calendar/.CalendarReceiver: pid=1475 uid=10036 gids={3003}
D/dalvikvm( 1100): GREF has increased to 301
I/ActivityThread( 1475): Pub com.android.calendar: com.android.providers.calendar.CalendarProvider2
I/ActivityManager( 1100): Start proc com.android.protips for broadcast com.android.protips/.ProtipWidget: pid=1490 uid=10016 gids={}
D/Calendar( 1475): missed alarms found: 0
D/dalvikvm( 1238): GC_EXPLICIT freed 107K, 47% free 3022K/5639K, external 2097K/2501K, paused 34ms
I/ActivityManager( 1100): Start proc com.android.music for broadcast com.android.music/.MediaAppWidgetProvider: pid=1501 uid=10020 gids={3003, 1015}
I/ActivityManager( 1100): Start proc com.android.quicksearchbox for broadcast com.android.quicksearchbox/.SearchWidgetProvider: pid=1509 uid=10021 gids={3003}
I/ActivityThread( 1509): Pub com.android.quicksearchbox.google: com.android.quicksearchbox.google.GoogleSuggestionProvider
I/ActivityThread( 1509): Pub com.android.quicksearchbox.shortcuts: com.android.quicksearchbox.ShortcutsProvider
I/ActivityManager( 1100): Start proc com.cooliris.media for broadcast com.cooliris.media/com.cooliris.cache.BootReceiver: pid=1518 uid=10033 gids={1015, 3003}
D/MediaScannerService( 1414): start scanning volume external
I/ActivityThread( 1518): Pub com.cooliris.picasa.contentprovider: com.cooliris.picasa.PicasaContentProvider
D/dalvikvm( 1518): GC_CONCURRENT freed 609K, 53% free 2797K/5831K, external 716K/1038K, paused 3ms+3ms
W/ActivityManager( 1100): Timeout of broadcast BroadcastRecord{407f1e18 android.intent.action.MEDIA_MOUNTED} - receiver=android.os.BinderProxy@4079d7f0, started 10001ms ago
W/ActivityManager( 1100): Receiver during timeout: ResolveInfo{407f1d48 com.cooliris.cache.BootReceiver p=0 o=0 m=0x208000}
W/ActivityManager( 1100): finishReceiver called but no pending broadcasts
I/Process ( 1100): Sending signal. PID: 1518 SIG: 3
I/dalvikvm( 1518): threadid=4: reacting to signal 3
I/dalvikvm( 1518): Wrote stack traces to ‘/data/anr/traces.txt’
I/Process ( 1100): Sending signal. PID: 1100 SIG: 3
I/dalvikvm( 1100): threadid=4: reacting to signal 3
I/Process ( 1100): Sending signal. PID: 1231 SIG: 3
I/dalvikvm( 1231): threadid=4: reacting to signal 3
I/Process ( 1100): Sending signal. PID: 1235 SIG: 3
I/dalvikvm( 1235): threadid=4: reacting to signal 3
D/dalvikvm( 1100): GC_CONCURRENT freed 965K, 45% free 4284K/7751K, external 2465K/3665K, paused 4ms+15ms
W/ProcessStats( 1100): Skipping unknown process pid 1538
W/ProcessStats( 1100): Skipping unknown process pid 1546
D/dalvikvm( 1100): GC_EXPLICIT freed 55K, 45% free 4290K/7751K, external 2465K/3665K, paused 51ms
E/ActivityManager( 1100): ANR in com.cooliris.media
E/ActivityManager( 1100): Reason: Broadcast of Intent { act=android.intent.action.MEDIA_MOUNTED dat= cmp=com.cooliris.media/com.cooliris.cache.BootReceiver (has extras) } E/ActivityManager( 1100): Load: 5.03 / 2.05 / 0.76 E/ActivityManager( 1100): CPU usage from 4889ms to -3741ms ago: E/ActivityManager( 1100): 4.1% 1100/system_server: 3.1% user + 1% kernel / faults: 292 minor E/ActivityManager( 1100): 0.2% 1518/com.cooliris.media: 0.2% user + 0% kernel / faults: 29 minor E/ActivityManager( 1100): 0.1% 56/irq/74-serial i: 0% user + 0.1% kernel E/ActivityManager( 1100): 0% 660/kjournald: 0% user + 0% kernel E/ActivityManager( 1100): 0.1% 1231/com.android.phone: 0.1% user + 0% kernel / faults: 4 minor E/ActivityManager( 1100): +0% 1547/sh: 0% user + 0% kernel E/ActivityManager( 1100): +0% 1553/sleep: 0% user + 0% kernel E/ActivityManager( 1100): 100% TOTAL: 3.4% user + 2.3% kernel + 94% iowait E/ActivityManager( 1100): CPU usage from 3204ms to 3724ms later with 99% awake: E/ActivityManager( 1100): 1.2% 660/kjournald: 0% user + 1.2% kernel E/ActivityManager( 1100): 1.9% 1100/system_server: 0% user + 1.9% kernel / faults: 1 minor E/ActivityManager( 1100): 1.9% 1124/ActivityManager: 1.9% user + 0% kernel E/ActivityManager( 1100): 100% TOTAL: 1.8% user + 3.7% kernel + 94% iowait I/Process ( 1100): Sending signal. PID: 1518 SIG: 9 I/ActivityManager( 1100): Process com.cooliris.media (pid 1518) has died. I/dalvikvm( 1100): Wrote stack traces to ‘/data/anr/traces.txt’ I/dalvikvm( 1231): Wrote stack traces to ‘/data/anr/traces.txt’ I/dalvikvm( 1235): Wrote stack traces to ‘/data/anr/traces.txt’ D/dalvikvm( 1414): GC_CONCURRENT freed 521K, 52% free 2823K/5831K, external 716K/1038K, paused 3ms+3ms # On 8/18/2011 10:52 AM, Amit Pundir wrote:
Extracting the files from Ubuntu apparently made a difference. Previously I extracted them in Windows and changed to Ubuntu to run the script mkmmc-android.sh .
Thanks to all for your assistance. Now to get the Ethernet going…
I spoke too soon. The Gingerbread 2.3.4 pre-built image now does not display video on my XM Rev C. Is there a way to determine if the display controller output has a problem during the boot sequence?