[Release] TI Android FroYo DevKit V 2.2 for Beagle XM and AM37x/DM3730 EVMs
Syed Mohammed, Khasim
As a follow up to our TI Android FroYo DevKit V 2.0 release in Oct
2010, we hereby announce the availability of TI Android FroYo DevKit V
2.2 for AM35x, AM37x, OMAP35x, DM3730 devices. The release has been
validated on AM35x/DM3730/AM37x EVMs and Beagleboard rev C4/XM.
Thanks a lot for your help and support during review, bug fixes and
enhancements.
Thanks to Mentor Graphics team for helping us integrating DSP
(hardware) accelerated CODECs.
What's new in this release?
DSP (hardware) accelerated multimedia CODECs (720P MPEG4 ASP and H.264
MP/HP) for DM3730, Power Management, WLAN (WL1271) on AM37x EVM,
Bluetooth connectivity for OPP, A2DP profiles on AM37x EVM, Camera
Image capture on Beagle XM, Fastboot utility for firmware upgrade,
NAND UBI File System based booting, UI and video on S-video, hardware
accelerated dynamic rotation for Video pipeline, etc.
The features from previous release like USB Mass Storage, Audio
record/playback, Keypad, Touchscreen, etc are still retained.
DevKit release V2.2 can be downloaded from:
Sitara page :
http://focus.ti.com/docs/toolsw/folders/print/androidsdk-sitara.html
Davinci page :
http://focus.ti.com/docs/toolsw/folders/print/androidsdk-dm37x.html
Explore latest exciting features with TI Android DevKit V2.2
See Beagle XM analyzing and printing live BarCodes and QR Codes
through Camera module, Go wireless with WLAN and Bluetooth support on
AM37x EVM, Enjoy 720p DSP (hardware) accelerated multimedia, Upgrade
Firmware dynamically by flashing on board NAND with Fastboot, Improved
power management, leverage RowboPERF app for performance measurement &
benchmarking, and lot more... (see flash video)
Please give us your feedback on improvements.
Regards,
Khasim
Maxim Podbereznyy
--
You received this message because you are subscribed to the Google Groups "Beagle Board" group.
To post to this group, send email to beagl...@googlegroups.com.
To unsubscribe from this group, send email to beagleboard...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/beagleboard?hl=en.
MaNu
Release notes and user guide of V2.0 don't mention touchscreen. In
fact: my usb touchscreen doesn't work. Does new version include this
peripheral?: Docs are still not mentioning anything...
Thank you very much.
On 31 ene, 17:37, "Syed Mohammed, Khasim " <sm.kha...@gmail.com>
wrote:
Xianghua Xiao
<project name="packages-apps-gallery3D" path="packages/apps/Gallery3D"
revision="c8396cca79725b2e7366f125264f691e9ddbbc9a"/>
but on rowboat's website it is "packages-apps-gallery3d", I had to
change 3D to 3d to checkout, anyone else has seen the same thing?
Xianghua
Gyorgy Szekely
I just installed the Beagle image on a rev C3 board, it's pretty cool. With some tweaking of the kernel command line, I got it working in 1280x1024 native display resolution. Only thing I miss is the DSP support, so:
- is it possible to build a rowboat image with DSP support for the OMAP3530?
- is such a (pre-built) image available somewhere or do you plan to release?
Regards,
Gyorgy
Hello all,
As a follow up to our TI Android FroYo DevKit V 2.0 release in Oct
2010, we hereby announce the availability of TI Android FroYo DevKit V
2.2 for AM35x, AM37x, OMAP35x, DM3730 devices. The release has been
validated on AM35x/DM3730/AM37x EVMs and Beagleboard rev C4/XM.
...
Xianghua Xiao
displayed for 30 minutes, still nothing more. I noticed IOWAIT is 99%
most of the time, I start a reboot by typing in 'reboot', then Android
fully came up but with a few errors:
"EXT3-fs error (device mmcblk0p2): ext3_add_entry: bad entry in
directory #64397: inode
..."
some apps can not run after Android is up, and IOWAIT stays high(99%)
all the time.
will try a different MicroSD card, I understand the first boot time is
long, but how long is normal?
Xianghua
On Mon, Jan 31, 2011 at 10:43 PM, dell ny <ny7...@gmail.com> wrote:
> Hi Khasim,
>
> Android DevKit V2.2 seems can't work on my BeagleBoard xM,
> here is the step and log:
>
> 1, download the beagleboard-xm.tar.gz
> 2, tar -xzvf beagleboard-xm.tar.gz
> 3, cd beagleboard-xm
> 4, sudo ./mkmmc-android /dev/sdb
>
> wait to complete.
>
> Insert the uSD card to BB-xM and power up.
> Wait for long time, but nothing display on screen (DVI port).
> The Angstrom can display something on screen,
> So the hardware is OK.
>
> below is the log:
>
> ---------------------------------------------------------------------------------
> Texas Instruments X-Loader 1.47 (Jan 14 2011 - 15:43:37)
> Unsupported Chip!
> Beagle xM Rev A
> Starting X-loader on MMC
> Reading boot sector
> 208660 Bytes Read from MMC
> Starting OS Bootloader from MMC...
> Starting OS Bootloader...
> U-Boot 2010.06 (Jan 14 2011 - 15:46:27)
> OMAP34xx/35xx-GP ES2.0, CPU-OPP2 L3-165MHz
> OMAP3 Beagle board + LPDDR/NAND
> I2C: ready
> DRAM: 384 MiB
> NAND: 0 MiB
> *** Warning - bad CRC or NAND, using default environment
> In: serial
> Out: serial
> Err: serial
> Beagle xM Rev A
> Die ID #55de00011ff00000015739eb0802d00f
> Hit any key to stop autoboot: 10 9 8 7 6 5 4 3 2 1 0
> mmc1 is available
> reading boot.scr
> 415 bytes read
> Running bootscript from mmc ...
> ## Executing script at 82000000
> reading uImage
> 2618432 bytes read
> ***** Kernel: /dev/mmcblk0p1/uImage *****
> ***** RootFS: /dev/mmcblk0p2 *****
> ## Booting kernel from Legacy Image at 80200000 ...
> Image Name: Linux-2.6.32
> Image Type: ARM Linux Kernel Image (uncompressed)
> Data Size: 2618368 Bytes = 2.5 MiB
> 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 (a0393957@swubn01) (gcc version 4.4.0 (GCC) ) #4 Wed
> Jan 19 15:12:38 IST 2011
> CPU: ARMv7 Processor [413fc082] revision 2 (ARMv7), cr=10c53c7f
> CPU: VIPT nonaliasing data cache, VIPT nonaliasing instruction cache
> Machine: OMAP3 Beagle Board
> Memory policy: ECC disabled, Data cache writeback
> OMAP3630/DM3730 ES1.0 (l2cache iva sgx neon isp 192mhz_clk )
> 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: console=ttyS2,115200n8 androidboot.console=ttyS2
> mem=256M root=/dev/mmcblk0p2 rw rootfstype=ext3 rootdelay=1 init=/init
> ip=off mpurate=800 omap_vout.vid1_static_vrfb_alloc=y
> 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: 249856KB available (4532K code, 825K data, 172K init, 0K highmem)
> Hierarchical RCU implementation.
> NR_IRQS:402
> Clocking rate (Crystal/Core/MPU): 26.0/664/600 MHz
> Reprogramming SDRC clock to 664000000 Hz
> dpll3_m2_clk rate change failed: -22
> 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: GPTIMER12 at 32768 Hz
> Console: colour dummy device 80x30
> Calibrating delay loop... 513.62 BogoMIPS (lpj=2007040)
> 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
> Target VDD1 OPP = 3, VDD2 OPP = 2
> OMAP DMA hardware revision 5.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 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 normal standby
> regulator: VDAC: 1800 mV normal standby
> regulator: VPLL2: 1800 mV normal standby
> regulator: VSIM: 1800 <--> 3000 mV normal standby
> regulator: VAUX3: 1800 mV normal standby
> regulator: VAUX4: 1800 mV normal standby
> i2c_omap i2c_omap.2: bus 2 rev4.0 at 400 kHz
> i2c_omap i2c_omap.3: bus 3 rev4.0 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
> 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: 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.
> yaffs Jan 19 2011 15:03:57 Installing.
> 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
> Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
> serial8250.0: ttyS0 at MMIO 0x4806a000 (irq = 72) is a ST16654
> serial8250.1: ttyS1 at MMIO 0x4806c000 (irq = 73) is a ST16654
> serial8250.2: 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 cdc_eem
> usbcore: registered new interface driver dm9601
> usbcore: registered new interface driver smsc95xx
> usbcore: registered new interface driver gl620a
> usbcore: registered new interface driver net1080
> usbcore: registered new interface driver plusb
> usbcore: registered new interface driver rndis_host
> usbcore: registered new interface driver cdc_subset
> usbcore: registered new interface driver zaurus
> usbcore: registered new interface driver MOSCHIP usb-ethernet driver
> 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 1
> ehci-omap ehci-omap.0: irq 77, io mem 0x48064800
> ehci-omap ehci-omap.0: USB 2.0 started, EHCI 1.00
> 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: c04d153c
> android_bind
> android_usb gadget: android_usb ready
> musb_hdrc musb_hdrc: MUSB HDRC host driver
> musb_hdrc musb_hdrc: new USB bus registered, assigned bus number 2
> 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
> i2c /dev entries driver
> Linux video capture interface: v2.00
> mt9v113 2-003c: Registered to v4l2 master omap34xxcam!!
> omap-iommu omap-iommu.0: isp: version 1.1
> OMAP Watchdog Timer Rev 0x31: initial timeout 60 sec
> mmci-omap-hs mmci-omap-hs.1: err -16 configuring card detect
> 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'
> Advanced Linux Sound Architecture Driver Version 1.0.21.
> usbcore: registered new interface driver snd-usb-audio
> 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
> usb 1-2: new high speed USB device using ehci-omap and address 2
> 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
> Power Management for TI OMAP3.
> Unable to set L3 frequency (400000000)
> Switched to new clocking rate (Crystal/Core/MPU): 26.0/664/800 MHz
> IVA2 clocking rate: 660 MHz
> SmartReflex driver initialized
> omap3beaglelmb: Driver registration complete
> VFP support v0.3: implementor 41 architecture 3 part 30 variant c rev 3
> omapdss DPI: Could not find exact pixel clock. Requested 23500 kHz, got
> 24000 kHz
> regulator_init_complete: incomplete constraints, leaving VAUX4 on
> regulator_init_complete: incomplete constraints, leaving VAUX3 on
> regulator_init_complete: incomplete constraints, leaving VDVI on
> regulator_init_complete: incomplete constraints, leaving VDAC on
> drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
> mt9v113 2-003c: chip id mismatch read 0x0, expecting 0x2280
> mt9v113 2-003c: Unable to detect decoder
> mt9v113 2-003c: chip id mismatch read 0x0, expecting 0x2280
> mt9v113 2-003c: Unable to detect decoder
> mt9v113 2-003c: chip id mismatch read 0x0, expecting 0x2280
> mt9v113 2-003c: Unable to detect decoder
> mt9v113 2-003c: chip id mismatch read 0x0, expecting 0x2280
> mt9v113 2-003c: Unable to detect decoder
> omapdss DPI error: display already enabled
> omap_vout omap_vout: 'dvi' Display already enabled
> omapdss DPI error: display already enabled
> omap_vout omap_vout: 'dvi' Display already enabled
> omap_vout omap_vout: Buffer Size = 3686400
> omap_vout omap_vout: : registered and initialized video device 0
> omap_vout omap_vout: Buffer Size = 3686400
> omap_vout omap_vout: : registered and initialized video device 1
> hub 1-2:1.0: USB hub found
> Waiting 1sec before mounting root device...
> hub 1-2:1.0: 5 ports detected
> 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
> smsc95xx v1.0.4
> usb0: register 'smsc95xx' at usb-ehci-omap.0-2.1, smsc95xx USB 2.0 Ethernet,
> 3e:91:a6:e4:de:f2
> kjournald starting. Commit interval 5 seconds
> EXT3-fs (mmcblk0p2): using internal journal
> EXT3-fs (mmcblk0p2): recovery complete
> EXT3-fs (mmcblk0p2): mounted filesystem with writeback data mode
> VFS: Mounted root (ext3 filesystem) on device 179:2.
> Freeing init memory: 172K
> Warning: unable to open an initial console.
> init: cannot open '/initlogo.rle'
> init: cannot find '/system/etc/install-recovery.sh', disabling
> 'flash_recovery'
> #
> #enabling adb
> adb_open
> ls
> config
> etc
> init
> mnt
> initlogo.rle.bak
> cache
> d
> sdcard
> dev
> sbin
> init.rc
> init.goldfish.rc
> system
> acct
> lost+found
> default.prop
> data
> proc
> sys
> # # ls /pr oc
> pvr
> asound
> binder
> mtd
> sysrq-trigger
> partitions
> diskstats
> crypto
> yaffs
> kpageflags
> kpagecount
> kmsg
> softirqs
> version
> uptime
> stat
> meminfo
> loadavg
> interrupts
> devices
> cpuinfo
> cmdline
> locks
> filesystems
> slabinfo
> swaps
> vmallocinfo
> zoneinfo
> vmstat
> pagetypeinfo
> buddyinfo
> config.gz
> kallsyms
> modules
> timer_list
> iomem
> ioports
> execdomains
> cpu
> scsi
> misc
> fb
> wakelocks
> irq
> sys
> bus
> tty
> driver
> fs
> sysvipc
> net
> mounts
> self
> 1
> 2
> 3
> 4
> 5
> 6
> 10
> 13
> 189
> 191
> 193
> 206
> 210
> 213
> 221
> 222
> 251
> 266
> 268
> 277
> 278
> 280
> 281
> 282
> 432
> 498
> 499
> 505
> 540
> 549
> 550
> 804
> 806
> 807
> 808
> 809
> 810
> 811
> 812
> 813
> 814
> 815
> 816
> 874
> 876
> 877
> # ls /dev
> pvrsrvkm
> cpuctl
> video2
> video1
> omap-resizer
> omap-previewer
> usbmon0
> vcsa1
> vcs1
> vcsa
> vcs
> ptmx
> tty63
> tty62
> tty61
> tty60
> tty59
> tty58
> tty57
> tty56
> tty55
> tty54
> tty53
> tty52
> tty51
> tty50
> tty49
> tty48
> tty47
> tty46
> tty45
> tty44
> tty43
> tty42
> tty41
> tty40
> tty39
> tty38
> tty37
> tty36
> tty35
> tty34
> tty33
> tty32
> tty31
> tty30
> tty29
> tty28
> tty27
> tty26
> tty25
> tty24
> tty23
> tty22
> tty21
> tty20
> tty19
> tty18
> tty17
> tty16
> tty15
> tty14
> tty13
> tty12
> tty11
> tty10
> tty9
> tty8
> tty7
> tty6
> tty5
> tty4
> tty3
> tty2
> tty1
> tty0
> console
> tty
> network_throughput
> network_latency
> cpu_dma_latency
> log
> binder
> alarm
> uinput
> psaux
> android_adb_enable
> android_adb
> ubi_ctrl
> ashmem
> kmsg
> urandom
> random
> full
> zero
> null
> kmem
> mem
> snd
> ttyS3
> block
> graphics
> watchdog
> 1-2.1
> 1-2
> usb1
> usbmon1
> usb2
> usbmon2
> ttyS2
> ttyS1
> ttyS0
> input
> i2c-3
> i2c-2
> i2c-1
> socket
> pts
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Beagle Board" group.
>> To post to this group, send email to beagl...@googlegroups.com.
>> To unsubscribe from this group, send email to
>> beagleboard...@googlegroups.com.
>> For more options, visit this group at
>> http://groups.google.com/group/beagleboard?hl=en.
>>
>
> --
> You received this message because you are subscribed to the Google Groups
> "rowboat" group.
> To post to this group, send email to row...@googlegroups.com.
> To unsubscribe from this group, send email to
> rowboat+u...@googlegroups.com.
> For more options, visit this group at
Xianghua Xiao
one warning/error message on serial port:
"
binder: release 1063:1063 transaction 1340 out, still active
binder: 912:1028 transaction failed 29189, size 4-0
binder: send failed reply for transaction 1340, target dead
"
the card makes a big difference.
Xianghua
dell ny
Joseph, Arun
Can you please provide the logcat result as well?
It seems process Zygote is not starting up in your case .
Regards,
Arun
--
You received this message because you are subscribed to the Google Groups
"rowboat" group.
To post to this group, send email to row...@googlegroups.com.
To unsubscribe from this group, send email to
rowboat+u...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/rowboat?hl=en.
Syed Mohammed, Khasim
The rootfs in DM3730 folder can boot directly on Beagle rev C4, this
has DSP CODECs, we have tried this on XM only, give a try.
Regards,
Khasim