[Release] TI Android FroYo DevKit V 2.2 for Beagle XM and AM37x/DM3730 EVMs

79 views
Skip to first unread message

Syed Mohammed, Khasim

unread,
Jan 31, 2011, 11:37:29 AM1/31/11
to row...@googlegroups.com, android...@googlegroups.com, beagl...@googlegroups.com
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.

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

Xianghua Xiao

unread,
Jan 31, 2011, 11:02:03 PM1/31/11
to row...@googlegroups.com, beagl...@googlegroups.com, android...@googlegroups.com
I probably am missing something. In the released manifest I saw:
<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

On Mon, Jan 31, 2011 at 1:29 PM, MaNu <manw...@hotmail.com> wrote:
> Hello,
>
> 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>

> --
> 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.
>
>

yaswanth raparti

unread,
Feb 3, 2011, 11:33:32 PM2/3/11
to android-porting
hi syed,
i want to give this a try on my OMAP3530 Board.
But, i have some doubts..
Do i need to build a Different uImage for this?
If yes, what should i configure my uImage for?
which kernel version does it support?


On Jan 31, 9:37 pm, "Syed Mohammed, Khasim " <sm.kha...@gmail.com>
wrote:

Amit Pundir

unread,
Feb 4, 2011, 2:01:41 AM2/4/11
to raparti....@gmail.com, android-porting
On Fri, Feb 4, 2011 at 10:03 AM, yaswanth raparti
<raparti....@gmail.com> wrote:
> hi syed,
> i want to give this a try on my OMAP3530 Board.
> But, i have some doubts..
> Do i need to build a Different uImage for this?
> If yes, what should i configure my uImage for?
> which kernel version does it support?

It is based on 2.6.32 kernel. You will get the complete
package(bootloader, kernel, rootfs etc) in the prebuilt images. If you
are building kernel from sources that came with your board SDK then
use omap3_evm_android_defconfig.

Regards,
Amit Pundir

> --
> unsubscribe: android-porti...@googlegroups.com
> website: http://groups.google.com/group/android-porting
>

Reply all
Reply to author
Forward
0 new messages