[Announcement] New DSP Firmware Available
Goluguri, Jayabharath
Dear All,
I would like to announce the availability of new DSP firmware binaries to the community.
We are releasing the following codec binaries:
· MPEG4 Video Dec
· H263 Video Dec
· JPEG Dec
· JPEG Enc
· AAC Dec
DSP Firmware v1.0 for Android:
· This is the first firmware release to the community for Android
· OpenMax components are already available on public GIT tree’s
· Support for Zoom2 platform
TI OpenMAX & DSP Firmware v0.4.1 for Angstrom/Gstreamer:
· Previous firmware 0.3.5 has watermarked codecs AAC/MPEG4
· New firmware v0.4.1 removes the watermarks and adds support for more codecs.
You can download them at : https://gforge.ti.com/gf/project/openmax/frs/?action=index
Also, you can use & edit the wikipages at : http://omappedia.org/wiki/OpenMAX_Project
Regards,
-Jayabharath
Checkout the new : http://omapzoom.org
Goluguri, Jayabharath
Dear All,
I would like to inform you of the availability of the Graphics SDK for Zoom2 that can be used with a Linux environment (e.g., Angstrom on Zoom2).
For download and access to SDK : http://focus.ti.com/general/docs/wtbu/wtbugencontent.tsp?templateId=6123&navigationId=12719&contentId=27458
More information: http://omappedia.org/wiki/Graphics_SDK
Regards,
-Jayabharath
Mike Turquette
Jayabharath<jayab...@ti.com> wrote:
> Dear All,
>
>
>
> I would like to inform you of the availability of the Graphics SDK for Zoom2
> that can be used with a Linux environment (e.g., Angstrom on Zoom2).
That is great Jay! What kernel versions are these SDK's compatible
with? Do they still enforce version check with specific releases (ie,
works with 2.6.29 but not 2.6.30)?
Mike
Goluguri, Jayabharath
I believe, this SDK should work with the 2.6.27 kernel available from public git tree.
Also, this SDK should have GPL'ed kernel driver sources included i.e., this will enable you/community to move the driver to different kernel incase you are using say 2.6.29+
Regards,
--Jay
Goluguri, Jayabharath
Nipuna who is on the omapzoom list can give more details on the what specific environments the binaries are test with and address your questions below.
--Jay
-----Original Message-----
From: G2 [mailto:greg...@gentil.com]
Sent: Thursday, September 03, 2009 2:47 AM
To: Beagle Board
Cc: felipe.c...@gmail.com; "jayabhar..."@ti.com; jkri...@beagleboard.org; Goluguri, Jayabharath
Subject: Re: Fwd: [Announcement] New DSP Firmware Available
I tried on the Touch Book (similar to Beagleboard) and it's not
working for me: both the ping.out test as well as gstreamer are
failing with the LCML ERROR: DSP 8000800a. For reference, I have a
working 3.x DSP bridge + gstreamer on the same card. And I have just
overwritten the DSP binaries.
I guess that we need some recompilations/patches of libomxil-ti and
the ping.out example. I think that Felipe is the mastermind/expert to
quickly debug this.
Also, it would be interesting if one of the TI guys who posted those
binaries can explain if they have successfully tested on Angstrom.
Very last, here are the lists of the various folders:
./dsp-3.x
./dsp-3.x/baseimage.dof
./dsp-3.x/dctn_dyn.dll64P
./dsp-3.x/mp4vdec_sn.dll64P
./dsp-3.x/mpeg4aacdec_sn.dll64P
./dsp-3.x/postprocessor.dll64P
./dsp-3.x/ringio.dll64P
./dsp-3.x/usn.dll64P
./dsp-3.x/vpp_sn.dll64P
./dsp-4.x-android
./dsp-4.x-android/baseimage.dof
./dsp-4.x-android/conversions.dll64P
./dsp-4.x-android/dctn_dyn.dll64P
./dsp-4.x-android/h264vdec_sn.dll64P
./dsp-4.x-android/jpegdec_sn.dll64P
./dsp-4.x-android/jpegenc_sn.dll64P
./dsp-4.x-android/m4venc_sn.dll64P
./dsp-4.x-android/mp4vdec_sn.dll64P
./dsp-4.x-android/mpeg4aacdec_sn.dll64P
./dsp-4.x-android/postprocessor.dll64P
./dsp-4.x-android/postprocessor_dualout.dll64P
./dsp-4.x-android/ringio.dll64P
./dsp-4.x-android/usn.dll64P
./dsp-4.x-android/vpp_sn.dll64P
./dsp-4.x/baseimage.dof
./dsp-4.x/dctn_dyn.dll64P
./dsp-4.x/h264vdec_sn.dll64P
./dsp-4.x/jpegdec_sn.dll64P
./dsp-4.x/jpegenc_sn.dll64P
./dsp-4.x/m4venc_sn.dll64P
./dsp-4.x/mp4vdec_sn.dll64P
./dsp-4.x/mpeg4aacdec_sn.dll64P
./dsp-4.x/mpeg4aacenc_sn.dll64P
./dsp-4.x/ringio.dll64P
./dsp-4.x/usn.dll64P
./dsp-4.x/vpp_sn.dll64P
Why postprocessor.dll64P has disappeared in 4.x while it's still there
for the Android distro? What are postprocessor_dualout.dll64P and
conversions.dll64P? Why those two binaries are only in Android? Why
the binaries of 4.x differs from the ones of Android?
I hope that somebody with the knowledge can step in,
Grégoire
On Sep 1, 5:19 am, Jason Kridner <jkrid...@beagleboard.org> wrote:
> Have any Beagle Board fans tried these binaries out?
>
> ---------- Forwarded message ----------
> From: Goluguri, Jayabharath <jayabhar...@ti.com>
> Date: Mon, Aug 31, 2009 at 5:31 PM
> Subject: [Announcement] New DSP Firmware Available
> To: "omapandroid-discuss...@gforge.ti.com"
>
> <omapandroid-discuss...@gforge.ti.com>, "omap...@googlegroups.com"
> <omap...@googlegroups.com>
>
> Dear All,
>
> I would like to announce the availability of new DSP firmware binaries
> to the community.
>
> We are releasing the following codec binaries:
>
> · MPEG4 Video Dec
>
> · H263 Video Dec
>
> · JPEG Dec
>
> · JPEG Enc
>
> · AAC Dec
>
> DSP Firmware v1.0 for Android:
>
> · This is the first firmware release to the community for Android
>
> · OpenMax components are already available on public GIT tree's
>
> · Support for Zoom2 platform
>
> TI OpenMAX& DSP Firmware v0.4.1 for Angstrom/Gstreamer:
Gunasekera, Nipuna
These DSP binaries and OMX components were taken from a TI internal release that was tested using 2.6.24 kernel + bridge on a TI 3430 SDP. I'm in the process of testing the same with Angstrom on Zoom2 with newer kernel/bridge combinations. Please note that only the mentioned use-cases in the wiki are supported (even though some extra socket nodes were included in the package). Any feedback on your testing on HW such as beagle is appreciated.
Can you please tell me which kernel you were using etc?
Regarding the Android package, we have some additional use cases supported such as JPEG encoder and these have been verified on OMAP Zoom2, thus conversions.dll64p and postprocessor_dualout.dll64p were needed for RGB to YUV conversions.
Best Regards -Nipuna
Gunasekera, Nipuna
First the OMX components will have to be compiled using the given make files in order to be used with their corresponding DSP binaries. We also have to find the correct kernel/bridge combinations for your specific devices.
"tiopenmax-0.4.1" package does not support encoding currently. So if you extract the package you will not see "jpeg_enc" OMX components in "tiopenmax-0.4.1\image\src\openmax_il" for example. (only jpeg dec was provided). We however, released the binaries because we plan to support it in the future.
"Android_DSP_Binaries_1.0" package does support "jpeg_enc" and hence the additional socket nodes (conversions.dll64P and postprocessor_dualout.dll64P) are released for color conversions etc.
I believe we're no longer using postprocessor.dll64P in our newer gstreamer based internal releases. Copying Luis also to confirm.
Best Regards -Nipuna
-----Original Message-----
From: Gregoire Gentil [mailto:gregoir...@gmail.com] On Behalf Of Gregoire Gentil
Sent: Thursday, September 03, 2009 12:37 PM
To: Gunasekera, Nipuna
Cc: omap...@googlegroups.com; felipe.c...@gmail.com; jkri...@beagleboard.org; Diaz, Daniel
Subject: RE: : [Announcement] New DSP Firmware Available
Hello,
Thanks for your email and your answers.
Testing case here is Touch Book (similar to Beagleboard for this kind of
stuff) + a derivative of Angstrom including kernel 2.6.29 plus
git://github.com/felipec/libomxil-ti.git;protocol=git version
18b2794567728f3dfa6ec93f7e3b9a74f3549390 plus gst-openmax_0.10.0.5.
The first and key question is what needs to be rebuilt and updated to
integrate those 4.x DSP binaries.
Also, I'm not sure that you didn't answer precisely my questions below.
I reformulate:
- why postprocessor.dll64P has disappeared between 3.x and 4.x? It's not
needed any more. Even when encoding?
- why *.dll64P differs between 4.x and 4.x-Android?
- why conversions.dll64P and postprocessor_dualout.dll64P are in
4.x-Android while not in 4.x though jpeg encoder is in 4.x and you may
need RGB to YUV?
Many thanks in advance for your answers so that we can debug this
situation,
Grégoire