eLinux.org - User contributions [en]

BeagleBoard/DSP Clarification

2010-09-08T11:37:57Z

Felipec: Add syslink

[[Category: Linux]]
[[Category: OMAP]]
This article tries to explain all the different Linux DSP systems for OMAP3 chips (e.g. used on [[BeagleBoard]]), how they are similar and different.

== dsp-gateway ==

[http://dspgateway.sourceforge.net/pub/index.php?Page=FAQ DSP Gateway] was developed by Nokia for the Maemo Internet Tablets. It's the first open implementation and currently the more open. The open code consists not only of the Linux kernel side, but also the DSP operating system. Unfortunately the development is essentially halted.

It works on OMAP1 and OMAP2, it's production ready, used on the Nokia N800 and N810, it follows Linux standards and it's close to upstream acceptance. There's code for OMAP3 but it hasn't been thoroughly tested.

It is maintained by Hiroshi DOYU.

There are a few user space applications that use it. Essentially GStreamer Nokia DSP plug-ins and a few others developed by the Maemo community.

However, it's mostly unmaintained.

== dsp-bridge ==

[http://omappedia.org/wiki/DSPBridge_Project tidspbridge] originally developed by TI, after its release in open source it has received many more contributions, primarily from TI and Nokia.

It still doesn't meet Linux standards although there has been a lot of progress. Only the ARM side is available as open source; unlike the dsp-gateway, the DSP side is completely closed.

There has been a lot of work spent into cleaning up the code to live up to linux standards, and currently it's on the staging tree with a strong push to merge it on mainline.

It shares the mailbox code with dsp-gateway, and soon iommu too.

There are more user-space applications using it, including gst-dsp directly, gst-openmax and gst-goo through TI's OpenMAX IL implementation which is also open source. [http://code.entropywave.com/leonora Leonora] is a project implementing the Theora codec on the DSP, and is a good example of non-trivial code running on the DSP and communicating with a process running on the ARM core.

For documentation and project overview, visit: [https://www.omapzoom.org/gf/project/omapbridge/docman/?subdir=3 TI DSP/Bridge project]

== dsp-link ==

A slimmer version of the dsp-bridge, also developed by TI. It supports a wide variety of devices (e.g. DaVinci, OMAP2, OMAP3, and discreet GPP+DSP devices).

The kernel driver doesn't meet the Linux kernel coding conventions. The sources haven't been submitted for review, and it is not currently planned to be merged into upstream kernels.

Some of the key differences with respect to dsp-bridge is the lack of advanced power management features (like DVFS and [http://focus.ti.com/general/docs/wtbu/wtbugencontent.tsp?templateId=6123&navigationId=12032&contentId=4609 SmartReflex]), and lack of dynamic MMU support.

[http://tiexpressdsp.com/index.php/Codec_Engine_Overview Codec Engine] and [http://tiexpressdsp.com/index.php/DMAI DMAI] have been built upon it, and there are GStreamer plug-ins provided by TI to use the algorithms.

Unlike the other implementations, it has strong support from the Angstrom distribution precisely because of wider platform support.

See [http://wiki.davincidsp.com/index.php?title=Category:DSPLink DSPLink articles in Texas Instruments Embedded Processors Wiki], too.

== syslink ==

For OMAP4 a new consolidated bridge is being developed [http://omappedia.org/wiki/Syslink_Project syslink]. It's an evolution of previous IPC mechanisms, reusing elements such as iommu and mailbox, and incorporating ideas such as moving the module loading to user-space from dsp-gateway.

Unlike it's predecessors it's supposed to be upstreamed since the get-go, and in fact some patches are already integrated (in iommu and mailbox).

== Interesting threads ==

* [http://linux.omap.com/pipermail/linux-omap-open-source/2007-May/009850.html bridge vs link]
* [http://marc.info/?l=linux-omap&m=123626584228670&w=2 different power management]

BeagleBoard/DSP Clarification

2010-09-08T11:30:34Z

Felipec: /* dsp-link */ add key differences

[[Category: Linux]]
[[Category: OMAP]]
This article tries to explain all the different Linux DSP systems for OMAP3 chips (e.g. used on [[BeagleBoard]]), how they are similar and different.

== dsp-gateway ==

[http://dspgateway.sourceforge.net/pub/index.php?Page=FAQ DSP Gateway] was developed by Nokia for the Maemo Internet Tablets. It's the first open implementation and currently the more open. The open code consists not only of the Linux kernel side, but also the DSP operating system. Unfortunately the development is essentially halted.

It works on OMAP1 and OMAP2, it's production ready, used on the Nokia N800 and N810, it follows Linux standards and it's close to upstream acceptance. There's code for OMAP3 but it hasn't been thoroughly tested.

It is maintained by Hiroshi DOYU.

There are a few user space applications that use it. Essentially GStreamer Nokia DSP plug-ins and a few others developed by the Maemo community.

However, it's mostly unmaintained.

== dsp-bridge ==

[http://omappedia.org/wiki/DSPBridge_Project tidspbridge] originally developed by TI, after its release in open source it has received many more contributions, primarily from TI and Nokia.

It still doesn't meet Linux standards although there has been a lot of progress. Only the ARM side is available as open source; unlike the dsp-gateway, the DSP side is completely closed.

There has been a lot of work spent into cleaning up the code to live up to linux standards, and currently it's on the staging tree with a strong push to merge it on mainline.

It shares the mailbox code with dsp-gateway, and soon iommu too.

There are more user-space applications using it, including gst-dsp directly, gst-openmax and gst-goo through TI's OpenMAX IL implementation which is also open source. [http://code.entropywave.com/leonora Leonora] is a project implementing the Theora codec on the DSP, and is a good example of non-trivial code running on the DSP and communicating with a process running on the ARM core.

For documentation and project overview, visit: [https://www.omapzoom.org/gf/project/omapbridge/docman/?subdir=3 TI DSP/Bridge project]

== dsp-link ==

A slimmer version of the dsp-bridge, also developed by TI. It supports a wide variety of devices (e.g. DaVinci, OMAP2, OMAP3, and discreet GPP+DSP devices).

The kernel driver doesn't meet the Linux kernel coding conventions. The sources haven't been submitted for review, and it is not currently planned to be merged into upstream kernels.

Some of the key differences with respect to dsp-bridge is the lack of advanced power management features (like DVFS and [http://focus.ti.com/general/docs/wtbu/wtbugencontent.tsp?templateId=6123&navigationId=12032&contentId=4609 SmartReflex]), and lack of dynamic MMU support.

[http://tiexpressdsp.com/index.php/Codec_Engine_Overview Codec Engine] and [http://tiexpressdsp.com/index.php/DMAI DMAI] have been built upon it, and there are GStreamer plug-ins provided by TI to use the algorithms.

Unlike the other implementations, it has strong support from the Angstrom distribution precisely because of wider platform support.

See [http://wiki.davincidsp.com/index.php?title=Category:DSPLink DSPLink articles in Texas Instruments Embedded Processors Wiki], too.

== Interesting threads ==

* [http://linux.omap.com/pipermail/linux-omap-open-source/2007-May/009850.html bridge vs link]
* [http://marc.info/?l=linux-omap&m=123626584228670&w=2 different power management]

BeagleBoard/DSP Clarification

2010-07-21T22:34:22Z

Felipec: No more to reference

[[Category: Linux]]
[[Category: OMAP]]
This article tries to explain all the different Linux DSP systems for OMAP3 chips (e.g. used on [[BeagleBoard]]), how they are similar and different.

== dsp-gateway ==

[http://dspgateway.sourceforge.net/pub/index.php?Page=FAQ DSP Gateway] was developed by Nokia for the Maemo Internet Tablets. It's the first open implementation and currently the more open. The open code consists not only of the Linux kernel side, but also the DSP operating system. Unfortunately the development is essentially halted.

It works on OMAP1 and OMAP2, it's production ready, used on the Nokia N800 and N810, it follows Linux standards and it's close to upstream acceptance. There's code for OMAP3 but it hasn't been thoroughly tested.

It is maintained by Hiroshi DOYU.

There are a few user space applications that use it. Essentially GStreamer Nokia DSP plug-ins and a few others developed by the Maemo community.

However, it's mostly unmaintained.

== dsp-bridge ==

[http://omappedia.org/wiki/DSPBridge_Project tidspbridge] originally developed by TI, after its release in open source it has received many more contributions, primarily from TI and Nokia.

It still doesn't meet Linux standards although there has been a lot of progress. Only the ARM side is available as open source; unlike the dsp-gateway, the DSP side is completely closed.

There has been a lot of work spent into cleaning up the code to live up to linux standards, and currently it's on the staging tree with a strong push to merge it on mainline.

It shares the mailbox code with dsp-gateway, and soon iommu too.

There are more user-space applications using it, including gst-dsp directly, gst-openmax and gst-goo through TI's OpenMAX IL implementation which is also open source. [http://code.entropywave.com/leonora Leonora] is a project implementing the Theora codec on the DSP, and is a good example of non-trivial code running on the DSP and communicating with a process running on the ARM core.

For documentation and project overview, visit: [https://www.omapzoom.org/gf/project/omapbridge/docman/?subdir=3 TI DSP/Bridge project]

== dsp-link ==

A slimmer version of the dsp-bridge, also developed by TI. It supports a wide variety of devices (e.g. DaVinci, OMAP2, OMAP3, and discreet GPP+DSP devices).

The kernel driver doesn't meet the Linux kernel coding conventions. The sources haven't been submitted for review, and it is not currently planned to be merged into upstream kernels.

[http://tiexpressdsp.com/index.php/Codec_Engine_Overview Codec Engine] and [http://tiexpressdsp.com/index.php/DMAI DMAI] have been built upon it, and there are GStreamer plug-ins provided by TI to use the algorithms.

Unlike the other implementations, it has strong support from the Angstrom distribution precisely because of wider platform support.

See [http://wiki.davincidsp.com/index.php?title=Category:DSPLink DSPLink articles in Texas Instruments Embedded Processors Wiki], too.

== Interesting threads ==

* [http://linux.omap.com/pipermail/linux-omap-open-source/2007-May/009850.html bridge vs link]
* [http://marc.info/?l=linux-omap&m=123626584228670&w=2 different power management]

BeagleBoard/DSP Clarification

2010-07-21T22:33:59Z

Felipec: Update mainly for tidspbridge

[[Category: Linux]]
[[Category: OMAP]]
This article tries to explain all the different Linux DSP systems for OMAP3 chips (e.g. used on [[BeagleBoard]]), how they are similar and different.

== dsp-gateway ==

[http://dspgateway.sourceforge.net/pub/index.php?Page=FAQ DSP Gateway] was developed by Nokia for the Maemo Internet Tablets. It's the first open implementation and currently the more open. The open code consists not only of the Linux kernel side, but also the DSP operating system. Unfortunately the development is essentially halted.

It works on OMAP1 and OMAP2, it's production ready, used on the Nokia N800 and N810, it follows Linux standards and it's close to upstream acceptance. There's code for OMAP3 but it hasn't been thoroughly tested.

It is maintained by Hiroshi DOYU.

There are a few user space applications that use it. Essentially GStreamer Nokia DSP plug-ins and a few others developed by the Maemo community.

However, it's mostly unmaintained.

== dsp-bridge ==

[http://omappedia.org/wiki/DSPBridge_Project tidspbridge] originally developed by TI, after its release in open source it has received many more contributions, primarily from TI and Nokia.

It still doesn't meet Linux standards although there has been a lot of progress. Only the ARM side is available as open source; unlike the dsp-gateway, the DSP side is completely closed.

There has been a lot of work spent into cleaning up the code to live up to linux standards, and currently it's on the staging tree with a strong push to merge it on mainline.

It shares the mailbox code with dsp-gateway, and soon iommu too.

There are more user-space applications using it, including gst-dsp directly, gst-openmax and gst-goo through TI's OpenMAX IL implementation which is also open source. [http://code.entropywave.com/leonora Leonora] is a project implementing the Theora codec on the DSP, and is a good example of non-trivial code running on the DSP and communicating with a process running on the ARM core.

For documentation and project overview, visit: [https://www.omapzoom.org/gf/project/omapbridge/docman/?subdir=3 TI DSP/Bridge project]

== dsp-link ==

A slimmer version of the dsp-bridge, also developed by TI. It supports a wide variety of devices (e.g. DaVinci, OMAP2, OMAP3, and discreet GPP+DSP devices).

The kernel driver doesn't meet the Linux kernel coding conventions. The sources haven't been submitted for review, and it is not currently planned to be merged into upstream kernels.

[http://tiexpressdsp.com/index.php/Codec_Engine_Overview Codec Engine] and [http://tiexpressdsp.com/index.php/DMAI DMAI] have been built upon it, and there are GStreamer plug-ins provided by TI to use the algorithms.

Unlike the other implementations, it has strong support from the Angstrom distribution precisely because of wider platform support.

See [http://wiki.davincidsp.com/index.php?title=Category:DSPLink DSPLink articles in Texas Instruments Embedded Processors Wiki], too.

== References ==

<references/>

== Interesting threads ==

* [http://linux.omap.com/pipermail/linux-omap-open-source/2007-May/009850.html bridge vs link]
* [http://marc.info/?l=linux-omap&m=123626584228670&w=2 different power management]

BeagleBoard/DSP Howto

2010-05-02T12:40:43Z

Felipec: /* Kernel driver */ Fix kernel build instructions.

[[Category: Linux]]
[[Category: OMAP]]
This article explains how to use the DSP in [http://focus.ti.com/general/docs/gencontent.tsp?contentId=36915&DCMP=OMAP_Feb27_2008&HQS=Other+PR+omap3503pr OMAP3] at [[BeagleBoard|BeagleBoard]] with TI's deliverables. For DSP tool chain see [[BeagleBoard#C64x.2B_DSP|C64x+ DSP]].

= Setup =

== Kernel driver ==

In order to use the DSP you would need TI's [[BeagleBoard/DSP_Clarification#dsp-bridge|bridgedriver]] module on the kernel. You can use my (Felipec's) branch in github that is based on 2.6.32-rc3 and has DSS2 too.

<code>
git clone git://gitorious.org/~felipec/linux-omap/felipec.git linux-omap
cd linux-omap
git checkout -b felipec v2.6.32-felipec1
make omap3_beagle_defconfig
make
</code>

Then build the '''uImage''' as usual and install the modules on your rootfs:
make INSTALL_MOD_PATH=/media/rootfs modules_install

== TI binaries ==

In order to get the DSP binaries for multimedia processing you need to download TI's OpenMAX IL [https://omapzoom.org/gf/download/frsrelease/111/396/tiopenmax-0.3.tar.gz package]. Once you have extracted the tarball you'll have to run the installer ''TI-OMX-Sample-Firmware-0.3-Linux-x86-Install'' and accept the license agreement.

You would end up with a bunch of binaries in <code>lib/dsp</code>, copy them to your root filesystem at the same location (/lib/dsp).

=== ping test ===

If you want to test the DSP you can try the simple ping test provided in this [https://omapzoom.org/gf/download/frsrelease/132/632/dspbridge_binaries.tar.bz2 package].

Just:
./ping.out

If you get an error like:
DSPNode_Allocate failed: 0x80008008

Then it's possible that the ping DSP socket node is not loaded. If you use 'baseimage.dof' you need to load it dynamically:

./dynreg.out -r pingdyn_3430.dll64P

On the other hand, 'ddspbase_tiomap3430.dof64P' has the node statically included, so there's no need to do that.

= Running =

On the board use this to load the module:

modprobe bridgedriver base_img=/lib/dsp/baseimage.dof

= Developing =

There are two ways to compile your own DSP nodes; the official one which requires XDC tools, and the simplified one (which I prefer).

== Official ==

Download the dsp-bridge examples from the [https://omapzoom.org/gf/download/frsrelease/147/848/dspbridge_LDP_v1.8.tar.gz omapzoom project]. Once you extract the main tarball you'll need to extract the individual tarballs on the same directory, so you have something like:

config.bld
documents
dsp
mpu_api
mpu_driver
product.mak
samplemakefile
samples

=== DSP side ===

You'll need the [https://www-a.ti.com/downloads/sds_support/targetcontent/LinuxDspTools/download.html C6x compiler], extract it in "/opt/dsp/cgt6x-6.0.22". The recommended version is '''v6.0.22'''.

You'll need the "DSP/BIOS" package and "RTSC/XDCtools" in order to compile the dsp-brige examples, you can download them from [https://www-a.ti.com/downloads/sds_support/targetcontent/index.html here]. Here we will assume they are installed in "/opt/dsp".

Edit "product.mak" to match the version of your tools. Then run:
make -f samplemakefile .bridge_samples DD_XDCDIR=/opt/dsp/xdctools_3_10_02 SABIOS_DIR=/opt/dsp/bios_5_33_04/packages DEPOT=/opt/dsp

=== ARM side ===

You'll need to prepare a '''target''' directory:
export target=/tmp/dsp-target
mkdir -p $target/lib

Also, build libbridge and libqos:
cd mpu_api/src
make PREFIX=$target/.. CROSS=arm-linux- install

To build the examples:
cd samples/mpu/src
make PREFIX=$target/.. CROSS=arm-linux- LIBINCLUDES=$target/lib LDPATH=$target/lib install

All you need will be on '/tmp/dsp-target'.

== Simplified ==

In order to develop dynamic dsp nodes you'll need a [https://www-a.ti.com/downloads/sds_support/targetcontent/LinuxDspTools/download.html C6x compiler] (the recommended version is '''v6.1.7''') and doffbuild tools.

=== doffbuild tools ===

The only relevant tool is DLLcreate, which can be found in TI's omapzoom site, on the [http://omapzoom.org/gf/download/frsrelease/108/421/dspbridge_dsp.tar.gz dspbridge_dsp] package.

mkdir -p tmp
tar -xf dspbridge_dsp.tar.gz -C tmp
mv tmp/dsp/bdsptools/packages/ti/dspbridge/dsp/doffbuild /opt/doffbuild
rm -rf tmp

=== Example dsp node ===

Here is an [http://github.com/felipec/dsp-dummy example dsp node] that is simply passing buffers back and forth.

git clone git://github.com/felipec/dsp-dummy.git
make DSP_TOOLS=/opt/dsptools DSP_DOFFBUILD=/opt/doffbuild

As a result you'll have two binaries; '''dummy.dll64P''' for dsp-side, and '''dummy''' for arm-side.

To load the dynamic node:
/dspbridge/dynreg.out -r /lib/dsp/dummy.dll64P

Now you can run the '''dummy''' test application.

= More information =

* [[BeagleBoard/gst-openmax]]

User:Felipec

2010-01-30T21:19:00Z

Felipec: Dummy edit

Felipe Contreras.

Talk:BeagleBoard/DSP Clarification

2009-06-01T09:50:49Z

Felipec: /* tidspbridge stability */ add my signature

== Oldest implementation ==

dsp-gateway is not the oldest implementation, just the first one to be open source.--[[User:Jkridner|Jkridner]] 21:45, 6 May 2009 (UTC)

:Right, I meant the oldest open source implementation, feel free to re-word. -- [[User:Felipec|Felipec]] 00:05, 8 May 2009 (UTC)

:: I changed it to "It's the first open implementation and currently the more open" -- [[User:Felipec|Felipec]] 23:14, 14 May 2009 (UTC)

== tidspbridge stability ==

In my experience the DSP bridge is far from stable. I see multiple crashes and hangs, and I can even reboot the device by following a sequence of commands. Also proof of the instability is the multiple critical fixes that are being sent to linux-omap mailing list all the time. -- [[User:Felipec|Felipec]] 10:16, 9 May 2009 (UTC)

Wikipedia and personal opinion "A stable version is one that has been through enough real-world testing to reasonably assume there are no showstopper problems, or at least that any problems are known and documented." but that does not mean that it won't benefit from any bug fix or enhancements. A fork from the stable version will be the code cleanup and redesign that is planned which might uncover some corner cases in bridge and open source modules as well. Again, any bug report is welcomed. -[[User:Omar_rmz|Omar_rmz]] 17:20, 9 May 2009 (UTC)

: Exactly, there are showstopper problems therefore it's not stable. A bug is simply 'unexpected behavior' and there many kinds, some of the worst are; crashes and deadlocks, but the bridgedriver goes to an even worst level; it reboots the device. You can say it's a "corner-case" because you have seen it very rarely in your occasional testing, but when a device goes into production there would be thousands, perhaps millions of people, using it constantly with a much wider variety of clips. A corner-case that reboots the device is absolutely showstopper. -- [[User:Felipec|Felipec]] 22:10, 9 May 2009 (UTC)

:: Please let me know when you report this as a formal bug or provide at least steps to reproduce. - [[User:Omar_rmz|Omar_rmz]] 00:35, 14 May 2009 (UTC)

: I removed the comments regarding stability for now, both on dspbridge and mailbox/iommu. I have not seen TI saying that iommu/mailbox are not stable, please provide a reference. As for the dspbridge stability, if you don't continue the discussion here I'll add the comment again saying that it's unstable. -- [[User:Felipec|Felipec]] 23:19, 14 May 2009 (UTC)

:: Again my personal opinion doesn't reflect a company, or are you speaking on behalf of Nokia? Look at my original comment "There are plans to share the mailbox and iommu that the dsp-gateway uses, whenever they are stable and have the full set of features supported by tidspbridge custom implementations, as well as to move parts of it to user-space." Do not rephrase and ask for references of things that you wrote. - [[User:Omar_rmz|Omar_rmz]] 00:35, 14 May 2009 (UTC)

::: I'm speaking as a member of the community. You said 'whenever they are stable' which means they are not stable yet, if TI considers them stable then there's no point in saying 'whenever they are stable'.

:::: ??? - I'll try to explain, 'whenever they are stable' means I tested them and there are failures and features missing, I'm preparing some patches on those... BTW I don't know if TI considers them to be stable or not. - [[User:Omar_rmz|Omar_rmz]] 6:53, 15 May 2009 (UTC)

::::: I've never seen any comments from anyone regarding the stability of mailbox/iommu. On wiki pages it doesn't really make sense to write things out of personal experience, there needs to be a reference. -- [[User:Felipec|Felipec]] 22:25, 15 May 2009 (UTC)

:::::: Just hilarious... read your first post on this discussion: "In my experience the DSP bridge is far from stable."; this is not leading any way, I'm fine if you think the driver is unstable, I'll try to keep working on it and your patches are welcomed to improve the code quality. [[User:Omar_rmz|Omar_rmz]] 23:53, 19 May 2009 (UTC)

::::::: First of all, there's a difference between personal experience that is not shared with anybody else, and personal experience that is shared and confirmed (other members of my team can attest to dsp-bridge's unstability). Also, the fact that someone somewhere hasn't found a critical bug doesn't mean there are no critical bug, so the personal experience of someone who finds the dsp-bridge stable doesn't say much, the "personal" experience of someone who has found a bug *does* say a lot. It could be for example that you are being way too complacent with the dsp-bridge, while other people are stress-testing it. -- [[User:Felipec|Felipec]] 09:50, 1 June 2009 (UTC)

== tidspbridge and pm ==

Omar: you added this "but now, after a lot of progress in pm branch, bridgedriver must be aligned with linux-omap-pm" there reference points to a master branch where there is no bridge driver, what is that supposed to prove? There are other branches in omapzoom that have the bridgedriver, I guess using a different pm than linux-omap. I'll remove that comment for now. Please provide a valid reference. -- [[User:Felipec|Felipec]] 23:30, 14 May 2009 (UTC)

: Agree on that, don't have a solid reference it was a personal opinion - [[User:Omar_rmz|Omar_rmz]] 00:47, 14 May 2009 (UTC)

Talk:BeagleBoard/DSP Clarification

2009-06-01T09:50:30Z

Felipec: /* tidspbridge stability */

== Oldest implementation ==

dsp-gateway is not the oldest implementation, just the first one to be open source.--[[User:Jkridner|Jkridner]] 21:45, 6 May 2009 (UTC)

:Right, I meant the oldest open source implementation, feel free to re-word. -- [[User:Felipec|Felipec]] 00:05, 8 May 2009 (UTC)

:: I changed it to "It's the first open implementation and currently the more open" -- [[User:Felipec|Felipec]] 23:14, 14 May 2009 (UTC)

== tidspbridge stability ==

In my experience the DSP bridge is far from stable. I see multiple crashes and hangs, and I can even reboot the device by following a sequence of commands. Also proof of the instability is the multiple critical fixes that are being sent to linux-omap mailing list all the time. -- [[User:Felipec|Felipec]] 10:16, 9 May 2009 (UTC)

Wikipedia and personal opinion "A stable version is one that has been through enough real-world testing to reasonably assume there are no showstopper problems, or at least that any problems are known and documented." but that does not mean that it won't benefit from any bug fix or enhancements. A fork from the stable version will be the code cleanup and redesign that is planned which might uncover some corner cases in bridge and open source modules as well. Again, any bug report is welcomed. -[[User:Omar_rmz|Omar_rmz]] 17:20, 9 May 2009 (UTC)

: Exactly, there are showstopper problems therefore it's not stable. A bug is simply 'unexpected behavior' and there many kinds, some of the worst are; crashes and deadlocks, but the bridgedriver goes to an even worst level; it reboots the device. You can say it's a "corner-case" because you have seen it very rarely in your occasional testing, but when a device goes into production there would be thousands, perhaps millions of people, using it constantly with a much wider variety of clips. A corner-case that reboots the device is absolutely showstopper. -- [[User:Felipec|Felipec]] 22:10, 9 May 2009 (UTC)

:: Please let me know when you report this as a formal bug or provide at least steps to reproduce. - [[User:Omar_rmz|Omar_rmz]] 00:35, 14 May 2009 (UTC)

: I removed the comments regarding stability for now, both on dspbridge and mailbox/iommu. I have not seen TI saying that iommu/mailbox are not stable, please provide a reference. As for the dspbridge stability, if you don't continue the discussion here I'll add the comment again saying that it's unstable. -- [[User:Felipec|Felipec]] 23:19, 14 May 2009 (UTC)

:: Again my personal opinion doesn't reflect a company, or are you speaking on behalf of Nokia? Look at my original comment "There are plans to share the mailbox and iommu that the dsp-gateway uses, whenever they are stable and have the full set of features supported by tidspbridge custom implementations, as well as to move parts of it to user-space." Do not rephrase and ask for references of things that you wrote. - [[User:Omar_rmz|Omar_rmz]] 00:35, 14 May 2009 (UTC)

::: I'm speaking as a member of the community. You said 'whenever they are stable' which means they are not stable yet, if TI considers them stable then there's no point in saying 'whenever they are stable'.

:::: ??? - I'll try to explain, 'whenever they are stable' means I tested them and there are failures and features missing, I'm preparing some patches on those... BTW I don't know if TI considers them to be stable or not. - [[User:Omar_rmz|Omar_rmz]] 6:53, 15 May 2009 (UTC)

::::: I've never seen any comments from anyone regarding the stability of mailbox/iommu. On wiki pages it doesn't really make sense to write things out of personal experience, there needs to be a reference. -- [[User:Felipec|Felipec]] 22:25, 15 May 2009 (UTC)

:::::: Just hilarious... read your first post on this discussion: "In my experience the DSP bridge is far from stable."; this is not leading any way, I'm fine if you think the driver is unstable, I'll try to keep working on it and your patches are welcomed to improve the code quality. [[User:Omar_rmz|Omar_rmz]] 23:53, 19 May 2009 (UTC)

::::::: First of all, there's a difference between personal experience that is not shared with anybody else, and personal experience that is shared and confirmed (other members of my team can attest to dsp-bridge's unstability). Also, the fact that someone somewhere hasn't found a critical bug doesn't mean there are no critical bug, so the personal experience of someone who finds the dsp-bridge stable doesn't say much, the "personal" experience of someone who has found a bug *does* say a lot. It could be for example that you are being way too complacent with the dsp-bridge, while other people are stress-testing it.

== tidspbridge and pm ==

Omar: you added this "but now, after a lot of progress in pm branch, bridgedriver must be aligned with linux-omap-pm" there reference points to a master branch where there is no bridge driver, what is that supposed to prove? There are other branches in omapzoom that have the bridgedriver, I guess using a different pm than linux-omap. I'll remove that comment for now. Please provide a valid reference. -- [[User:Felipec|Felipec]] 23:30, 14 May 2009 (UTC)

: Agree on that, don't have a solid reference it was a personal opinion - [[User:Omar_rmz|Omar_rmz]] 00:47, 14 May 2009 (UTC)

Talk:BeagleBoard/DSP Clarification

2009-05-15T22:25:56Z

Felipec: /* tidspbridge stability */

== Oldest implementation ==

dsp-gateway is not the oldest implementation, just the first one to be open source.--[[User:Jkridner|Jkridner]] 21:45, 6 May 2009 (UTC)

:Right, I meant the oldest open source implementation, feel free to re-word. -- [[User:Felipec|Felipec]] 00:05, 8 May 2009 (UTC)

:: I changed it to "It's the first open implementation and currently the more open" -- [[User:Felipec|Felipec]] 23:14, 14 May 2009 (UTC)

== tidspbridge stability ==

In my experience the DSP bridge is far from stable. I see multiple crashes and hangs, and I can even reboot the device by following a sequence of commands. Also proof of the instability is the multiple critical fixes that are being sent to linux-omap mailing list all the time. -- [[User:Felipec|Felipec]] 10:16, 9 May 2009 (UTC)

Wikipedia and personal opinion "A stable version is one that has been through enough real-world testing to reasonably assume there are no showstopper problems, or at least that any problems are known and documented." but that does not mean that it won't benefit from any bug fix or enhancements. A fork from the stable version will be the code cleanup and redesign that is planned which might uncover some corner cases in bridge and open source modules as well. Again, any bug report is welcomed. -[[User:Omar_rmz|Omar_rmz]] 17:20, 9 May 2009 (UTC)

: Exactly, there are showstopper problems therefore it's not stable. A bug is simply 'unexpected behavior' and there many kinds, some of the worst are; crashes and deadlocks, but the bridgedriver goes to an even worst level; it reboots the device. You can say it's a "corner-case" because you have seen it very rarely in your occasional testing, but when a device goes into production there would be thousands, perhaps millions of people, using it constantly with a much wider variety of clips. A corner-case that reboots the device is absolutely showstopper. -- [[User:Felipec|Felipec]] 22:10, 9 May 2009 (UTC)

:: Please let me know when you report this as a formal bug or provide at least steps to reproduce. - [[User:Omar_rmz|Omar_rmz]] 00:35, 14 May 2009 (UTC)

: I removed the comments regarding stability for now, both on dspbridge and mailbox/iommu. I have not seen TI saying that iommu/mailbox are not stable, please provide a reference. As for the dspbridge stability, if you don't continue the discussion here I'll add the comment again saying that it's unstable. -- [[User:Felipec|Felipec]] 23:19, 14 May 2009 (UTC)

:: Again my personal opinion doesn't reflect a company, or are you speaking on behalf of Nokia? Look at my original comment "There are plans to share the mailbox and iommu that the dsp-gateway uses, whenever they are stable and have the full set of features supported by tidspbridge custom implementations, as well as to move parts of it to user-space." Do not rephrase and ask for references of things that you wrote. - [[User:Omar_rmz|Omar_rmz]] 00:35, 14 May 2009 (UTC)

::: I'm speaking as a member of the community. You said 'whenever they are stable' which means they are not stable yet, if TI considers them stable then there's no point in saying 'whenever they are stable'.

:::: ??? - I'll try to explain, 'whenever they are stable' means I tested them and there are failures and features missing, I'm preparing some patches on those... BTW I don't know if TI considers them to be stable or not. - [[User:Omar_rmz|Omar_rmz]] 6:53, 15 May 2009 (UTC)

::::: I've never seen any comments from anyone regarding the stability of mailbox/iommu. On wiki pages it doesn't really make sense to write things out of personal experience, there needs to be a reference. -- [[User:Felipec|Felipec]] 22:25, 15 May 2009 (UTC)

== tidspbridge and pm ==

Omar: you added this "but now, after a lot of progress in pm branch, bridgedriver must be aligned with linux-omap-pm" there reference points to a master branch where there is no bridge driver, what is that supposed to prove? There are other branches in omapzoom that have the bridgedriver, I guess using a different pm than linux-omap. I'll remove that comment for now. Please provide a valid reference. -- [[User:Felipec|Felipec]] 23:30, 14 May 2009 (UTC)

: Agree on that, don't have a solid reference it was a personal opinion - [[User:Omar_rmz|Omar_rmz]] 00:47, 14 May 2009 (UTC)

Talk:BeagleBoard/DSP Clarification

2009-05-15T09:30:42Z

Felipec: /* tidspbridge stability */

== Oldest implementation ==

dsp-gateway is not the oldest implementation, just the first one to be open source.--[[User:Jkridner|Jkridner]] 21:45, 6 May 2009 (UTC)

:Right, I meant the oldest open source implementation, feel free to re-word. -- [[User:Felipec|Felipec]] 00:05, 8 May 2009 (UTC)

:: I changed it to "It's the first open implementation and currently the more open" -- [[User:Felipec|Felipec]] 23:14, 14 May 2009 (UTC)

== tidspbridge stability ==

In my experience the DSP bridge is far from stable. I see multiple crashes and hangs, and I can even reboot the device by following a sequence of commands. Also proof of the instability is the multiple critical fixes that are being sent to linux-omap mailing list all the time. -- [[User:Felipec|Felipec]] 10:16, 9 May 2009 (UTC)

Wikipedia and personal opinion "A stable version is one that has been through enough real-world testing to reasonably assume there are no showstopper problems, or at least that any problems are known and documented." but that does not mean that it won't benefit from any bug fix or enhancements. A fork from the stable version will be the code cleanup and redesign that is planned which might uncover some corner cases in bridge and open source modules as well. Again, any bug report is welcomed. -[[User:Omar_rmz|Omar_rmz]] 17:20, 9 May 2009 (UTC)

: Exactly, there are showstopper problems therefore it's not stable. A bug is simply 'unexpected behavior' and there many kinds, some of the worst are; crashes and deadlocks, but the bridgedriver goes to an even worst level; it reboots the device. You can say it's a "corner-case" because you have seen it very rarely in your occasional testing, but when a device goes into production there would be thousands, perhaps millions of people, using it constantly with a much wider variety of clips. A corner-case that reboots the device is absolutely showstopper. -- [[User:Felipec|Felipec]] 22:10, 9 May 2009 (UTC)

:: Please let me know when you report this as a formal bug or provide at least steps to reproduce. - [[User:Omar_rmz|Omar_rmz]] 00:35, 14 May 2009 (UTC)

: I removed the comments regarding stability for now, both on dspbridge and mailbox/iommu. I have not seen TI saying that iommu/mailbox are not stable, please provide a reference. As for the dspbridge stability, if you don't continue the discussion here I'll add the comment again saying that it's unstable. -- [[User:Felipec|Felipec]] 23:19, 14 May 2009 (UTC)

:: Again my personal opinion doesn't reflect a company, or are you speaking on behalf of Nokia? Look at my original comment "There are plans to share the mailbox and iommu that the dsp-gateway uses, whenever they are stable and have the full set of features supported by tidspbridge custom implementations, as well as to move parts of it to user-space." Do not rephrase and ask for references of things that you wrote. - [[User:Omar_rmz|Omar_rmz]] 00:35, 14 May 2009 (UTC)

::: I'm speaking as a member of the community. You said 'whenever they are stable' which means they are not stable yet, if TI considers them stable then there's no point in saying 'whenever they are stable'.

== tidspbridge and pm ==

Omar: you added this "but now, after a lot of progress in pm branch, bridgedriver must be aligned with linux-omap-pm" there reference points to a master branch where there is no bridge driver, what is that supposed to prove? There are other branches in omapzoom that have the bridgedriver, I guess using a different pm than linux-omap. I'll remove that comment for now. Please provide a valid reference. -- [[User:Felipec|Felipec]] 23:30, 14 May 2009 (UTC)

: Agree on that, don't have a solid reference it was a personal opinion - [[User:Omar_rmz|Omar_rmz]] 00:47, 14 May 2009 (UTC)

BeagleBoard/DSP Clarification

2009-05-14T23:30:45Z

Felipec: /* dsp-bridge */ no valid reference for TI willing to use linux-omap pm

[[Category: Linux]]
[[Category: OMAP]]
This article tries to explain all the different Linux DSP systems for OMAP chips (e.g. used on [[BeagleBoard]]), how they are similar and different.

== dsp-gateway ==

[http://dspgateway.sourceforge.net/pub/index.php?Page=FAQ DSP Gateway] was developed by Nokia for the Maemo Internet Tablets. It's the first open implementation and currently the more open. The open code consists not only of the Linux kernel side, but also the DSP operating system. Unfortunately the development is essentially halted.

It works on OMAP1 and OMAP2, it's production ready, used on the Nokia N800 and N810, it follows Linux standards and it's close to upstream acceptance. There's code for OMAP3 but it hasn't been thoroughly tested.

It is maintained by Hiroshi DOYU.

There are a few user space applications that use it. Essentially GStreamer Nokia DSP plug-ins and a few others developed by the Maemo community.

== dsp-bridge ==

[https://www.omapzoom.org/gf/project/omapbridge/wiki/? tidspbridge] originally developed by TI, after its release in open source it has received many more contributions, primarily from TI and Nokia.

It still doesn't meet Linux standards although there has been a lot of progress. Only the ARM side is available as open source; unlike the dsp-gateway, the DSP side is completely closed.

There is a disagreement<ref>[http://marc.info/?l=linux-omap&m=120820462123556&w=2 Omapzoom predecessor: "new development happens where there are gaps"]</ref> between TI and the community as how power management must be handled, which created two forks: linux-omap, and omapzoom. However, TI is also working with the community on the linux-omap-pm branch maintained by Kevin Hillman.

It's under heavy code cleanup<ref>[http://marc.info/?l=linux-omap&m=124148814309478&w=2 Dspbridge: Staging TODO List]</ref>; the first dspbridge appearance was in form of tarballs <ref>[http://marc.info/?l=linux-omap&m=120761100810527&w=2 Dspbridge: First appearance]</ref>, some time later it was merged into TI's omapzoom tree<ref>[http://marc.info/?l=linux-omap&m=121340174005072&w=2 Dspbridge: First set of patches]</ref>. Then, Hiroshi DOYU split the driver into a logical set of patches<ref>[http://marc.info/?l=linux-omap&m=121878286205991&w=2 Port TI DSP BRIDGE for a new dedicated branch in linux-omap]</ref> but its inclusion into linux-omap was rejected and it was maintained in www.muru.com<ref>[http://marc.info/?l=linux-omap&m=121879938429430&w=2 muru.com tidspbridge/]</ref> (Tony Lindgren's personal site), from there it jumped into Hiroshi's personal web space <ref>[http://marc.info/?l=linux-omap&m=122188661716962&w=2 Latest dspbridge rebased on l-o and sync'ed with o-z]</ref> and it finally ended in gitorious <ref>[http://marc.info/?l=linux-omap&m=122692901013682&w=2 Dspbridge gitorious repository]</ref>, now Ameya Palande took over.

There are plans to share the mailbox and iommu that the dsp-gateway uses (which are part of the omap platform) as well as to move parts of it to user-space. However, TI argues the platform code is missing features from tidspbridge.

There are slightly more user-space applications using it, including gst-openmax and gst-goo through TI's OpenMAX IL implementation which is also open source.

For documentation and project overview, visit: [https://www.omapzoom.org/gf/project/omapbridge/docman/?subdir=3 TI DSP/Bridge project]

== dsp-link ==

A slimmer version of the dsp-bridge targeted for the DaVinci platform also developed by TI. It supports a wider variety of chips, not only OMAP.

It is the one farther from meeting Linux standards. The code hasn't even been submitted for reviewing nor is planned to to be merged at any time.

It's tightly tied to CodecEngine and DMAI, and there are GStreamer plug-ins provided by TI to use the algorithms.

Unlike the other implementations, it has strong support from the Angstrom distribution precisely because of wider platform support.

See [http://wiki.davincidsp.com/index.php?title=Category:DSPLink DSPLink articles in Texas Instruments Embedded Processors Wiki], too.

== References ==
<references/>

== Interesting threads ==

* [http://linux.omap.com/pipermail/linux-omap-open-source/2007-May/009850.html bridge vs link]
* [http://marc.info/?l=linux-omap&m=123626584228670&w=2 different power management]

Talk:BeagleBoard/DSP Clarification

2009-05-14T23:30:21Z

Felipec: tidspbridge and pm

Talk:BeagleBoard/DSP Clarification

2009-05-14T23:19:01Z

Felipec: /* tidspbridge stability */

BeagleBoard/DSP Clarification

2009-05-14T23:16:54Z

Felipec: /* dsp-bridge */ Remove comments about stability.

[[Category: Linux]]
[[Category: OMAP]]
This article tries to explain all the different Linux DSP systems for OMAP chips (e.g. used on [[BeagleBoard]]), how they are similar and different.

== dsp-gateway ==

[http://dspgateway.sourceforge.net/pub/index.php?Page=FAQ DSP Gateway] was developed by Nokia for the Maemo Internet Tablets. It's the first open implementation and currently the more open. The open code consists not only of the Linux kernel side, but also the DSP operating system. Unfortunately the development is essentially halted.

It works on OMAP1 and OMAP2, it's production ready, used on the Nokia N800 and N810, it follows Linux standards and it's close to upstream acceptance. There's code for OMAP3 but it hasn't been thoroughly tested.

It is maintained by Hiroshi DOYU.

There are a few user space applications that use it. Essentially GStreamer Nokia DSP plug-ins and a few others developed by the Maemo community.

== dsp-bridge ==

[https://www.omapzoom.org/gf/project/omapbridge/wiki/? tidspbridge] originally developed by TI, after its release in open source it has received many more contributions, primarily from TI and Nokia.

It still doesn't meet Linux standards although there has been a lot of progress. Only the ARM side is available as open source; unlike the dsp-gateway, the DSP side is completely closed.

There was a disagreement<ref>[http://marc.info/?l=linux-omap&m=120820462123556&w=2 Omapzoom predecessor: "new development happens where there are gaps"]</ref> between TI and the community as how power management must be handled, which created two forks: linux-omap, and omapzoom; but now, after a lot of progress in pm branch, bridgedriver must be aligned with linux-omap-pm<ref>[http://git.omapzoom.org/?p=repo/omapkernel.git;a=shortlog;h=refs/heads/master No dspbridge patches in omapzoom]</ref>. TI is also working with the community on the linux-omap-pm branch maintained by Kevin Hillman.

It's under heavy code cleanup<ref>[http://marc.info/?l=linux-omap&m=124148814309478&w=2 Dspbridge: Staging TODO List]</ref>; the first dspbridge appearance was in form of tarballs <ref>[http://marc.info/?l=linux-omap&m=120761100810527&w=2 Dspbridge: First appearance]</ref>, some time later it was merged into TI's omapzoom tree<ref>[http://marc.info/?l=linux-omap&m=121340174005072&w=2 Dspbridge: First set of patches]</ref>. Then, Hiroshi DOYU split the driver into a logical set of patches<ref>[http://marc.info/?l=linux-omap&m=121878286205991&w=2 Port TI DSP BRIDGE for a new dedicated branch in linux-omap]</ref> but its inclusion into linux-omap was rejected and it was maintained in www.muru.com<ref>[http://marc.info/?l=linux-omap&m=121879938429430&w=2 muru.com tidspbridge/]</ref> (Tony Lindgren's personal site), from there it jumped into Hiroshi's personal web space <ref>[http://marc.info/?l=linux-omap&m=122188661716962&w=2 Latest dspbridge rebased on l-o and sync'ed with o-z]</ref> and it finally ended in gitorious <ref>[http://marc.info/?l=linux-omap&m=122692901013682&w=2 Dspbridge gitorious repository]</ref>, now Ameya Palande took over.

There are plans to share the mailbox and iommu that the dsp-gateway uses (which are part of the omap platform) as well as to move parts of it to user-space. However, TI argues the platform code is missing features from tidspbridge.

There are slightly more user-space applications using it, including gst-openmax and gst-goo through TI's OpenMAX IL implementation which is also open source.

For documentation and project overview, visit: [https://www.omapzoom.org/gf/project/omapbridge/docman/?subdir=3 TI DSP/Bridge project]

== dsp-link ==

A slimmer version of the dsp-bridge targeted for the DaVinci platform also developed by TI. It supports a wider variety of chips, not only OMAP.

It is the one farther from meeting Linux standards. The code hasn't even been submitted for reviewing nor is planned to to be merged at any time.

It's tightly tied to CodecEngine and DMAI, and there are GStreamer plug-ins provided by TI to use the algorithms.

Unlike the other implementations, it has strong support from the Angstrom distribution precisely because of wider platform support.

See [http://wiki.davincidsp.com/index.php?title=Category:DSPLink DSPLink articles in Texas Instruments Embedded Processors Wiki], too.

== References ==
<references/>

== Interesting threads ==

* [http://linux.omap.com/pipermail/linux-omap-open-source/2007-May/009850.html bridge vs link]
* [http://marc.info/?l=linux-omap&m=123626584228670&w=2 different power management]

Talk:BeagleBoard/DSP Clarification

2009-05-14T23:14:02Z

Felipec: /* Oldest implementation */

BeagleBoard/DSP Clarification

2009-05-14T23:13:29Z

Felipec: /* dsp-gateway */ reword

[[Category: Linux]]
[[Category: OMAP]]
This article tries to explain all the different Linux DSP systems for OMAP chips (e.g. used on [[BeagleBoard]]), how they are similar and different.

== dsp-gateway ==

[http://dspgateway.sourceforge.net/pub/index.php?Page=FAQ DSP Gateway] was developed by Nokia for the Maemo Internet Tablets. It's the first open implementation and currently the more open. The open code consists not only of the Linux kernel side, but also the DSP operating system. Unfortunately the development is essentially halted.

It works on OMAP1 and OMAP2, it's production ready, used on the Nokia N800 and N810, it follows Linux standards and it's close to upstream acceptance. There's code for OMAP3 but it hasn't been thoroughly tested.

It is maintained by Hiroshi DOYU.

There are a few user space applications that use it. Essentially GStreamer Nokia DSP plug-ins and a few others developed by the Maemo community.

== dsp-bridge ==

[https://www.omapzoom.org/gf/project/omapbridge/wiki/? tidspbridge] originally developed by TI, after its release in open source it has received many more contributions, primarily from TI and Nokia.

It is stable, but it still doesn't meet Linux standards although there has been a lot of progress. Only the ARM side is available as open source; unlike the dsp-gateway, the DSP side is completely closed.

There was a disagreement<ref>[http://marc.info/?l=linux-omap&m=120820462123556&w=2 Omapzoom predecessor: "new development happens where there are gaps"]</ref> between TI and the community as how power management must be handled, which created two forks: linux-omap, and omapzoom; but now, after a lot of progress in pm branch, bridgedriver must be aligned with linux-omap-pm<ref>[http://git.omapzoom.org/?p=repo/omapkernel.git;a=shortlog;h=refs/heads/master No dspbridge patches in omapzoom]</ref>. TI is also working with the community on the linux-omap-pm branch maintained by Kevin Hillman.

It's under heavy code cleanup<ref>[http://marc.info/?l=linux-omap&m=124148814309478&w=2 Dspbridge: Staging TODO List]</ref>; the first dspbridge appearance was in form of tarballs <ref>[http://marc.info/?l=linux-omap&m=120761100810527&w=2 Dspbridge: First appearance]</ref>, some time later it was merged into TI's omapzoom tree<ref>[http://marc.info/?l=linux-omap&m=121340174005072&w=2 Dspbridge: First set of patches]</ref>. Then, Hiroshi DOYU split the driver into a logical set of patches<ref>[http://marc.info/?l=linux-omap&m=121878286205991&w=2 Port TI DSP BRIDGE for a new dedicated branch in linux-omap]</ref> but its inclusion into linux-omap was rejected and it was maintained in www.muru.com<ref>[http://marc.info/?l=linux-omap&m=121879938429430&w=2 muru.com tidspbridge/]</ref> (Tony Lindgren's personal site), from there it jumped into Hiroshi's personal web space <ref>[http://marc.info/?l=linux-omap&m=122188661716962&w=2 Latest dspbridge rebased on l-o and sync'ed with o-z]</ref> and it finally ended in gitorious <ref>[http://marc.info/?l=linux-omap&m=122692901013682&w=2 Dspbridge gitorious repository]</ref>, now Ameya Palande took over.

There are plans to share the mailbox and iommu that the dsp-gateway uses (which are part of the omap platform) as well as to move parts of it to user-space. However, TI argues the platform code is missing features from tidspbridge and it is unstable.

There are slightly more user-space applications using it, including gst-openmax and gst-goo through TI's OpenMAX IL implementation which is also open source.

For documentation and project overview, visit: [https://www.omapzoom.org/gf/project/omapbridge/docman/?subdir=3 TI DSP/Bridge project]

== dsp-link ==

A slimmer version of the dsp-bridge targeted for the DaVinci platform also developed by TI. It supports a wider variety of chips, not only OMAP.

It is the one farther from meeting Linux standards. The code hasn't even been submitted for reviewing nor is planned to to be merged at any time.

It's tightly tied to CodecEngine and DMAI, and there are GStreamer plug-ins provided by TI to use the algorithms.

Unlike the other implementations, it has strong support from the Angstrom distribution precisely because of wider platform support.

See [http://wiki.davincidsp.com/index.php?title=Category:DSPLink DSPLink articles in Texas Instruments Embedded Processors Wiki], too.

== References ==
<references/>

== Interesting threads ==

* [http://linux.omap.com/pipermail/linux-omap-open-source/2007-May/009850.html bridge vs link]
* [http://marc.info/?l=linux-omap&m=123626584228670&w=2 different power management]

Talk:BeagleBoard/DSP Clarification

2009-05-09T22:10:31Z

Felipec: /* tidspbridge stability */

Talk:BeagleBoard/DSP Clarification

2009-05-09T22:10:20Z

Felipec: /* tidspbridge stability */

Talk:BeagleBoard/DSP Clarification

2009-05-09T10:16:00Z

Felipec: tidspbridge stability

BeagleBoard/DSP Clarification

2009-05-08T00:22:43Z

Felipec: /* dsp-link */ add Angstrom note

[[Category: Linux]]
[[Category: OMAP]]
This article tries to explain all the different Linux DSP systems for OMAP chips (e.g. used on [[BeagleBoard]]), how they are similar and different.

== dsp-gateway ==

[http://dspgateway.sourceforge.net/pub/index.php?Page=FAQ DSP Gateway] was developed by Nokia for the Maemo Internet Tablets. It's the oldest and more open of the implementations. The open code consists not only of the Linux kernel side, but also the DSP operating system. Unfortunately the development is essentially halted.

It works on OMAP1 and OMAP2, it's production ready, used on the Nokia N800 and N810, it follows Linux standards and it's close to upstream acceptance. There's code for OMAP3 but it hasn't been thoroughly tested.

It is maintained by Hiroshi DOYU.

There are a few user space applications that use it. Essentially GStreamer Nokia DSP plug-ins and a few others developed by the Maemo community.

== dsp-bridge ==

[https://www.omapzoom.org/gf/project/omapbridge/wiki/? tidspbridge] originally developed by TI, after its release in open source it has received many more contributions, primarily from TI and Nokia.

It is probably not production ready, and it still doesn't meet Linux standards although there has been a lot of progress. Only the ARM side is available as open source; unlike the dsp-gateway, the DSP side is completely closed.

Unfortunately there's a disagreement<ref>[http://marc.info/?l=linux-omap&m=123626584228670&w=2 Different power management thread]</ref> between TI and the community as how power management must be handled, so there are two forks: linux-omap, and omapzoom. TI is also working with the community on the linux-omap-pm branch maintained by Kevin Hillman.

It's under heavy development, the linux-omap tree was originally maintained by Hiroshi DOYU, but now Ameya Palande took over.

There are plans to share the mailbox and iommu that the dsp-gateway uses (which are part of the omap platform) as well as to move parts of it to user-space. However, TI argues the platform code is missing features from tidspbridge.

There are slightly more user-space applications using it, including gst-openmax and gst-goo through TI's OpenMAX IL implementation which is also open source.

For documentation and project overview, visit: [https://www.omapzoom.org/gf/project/omapbridge/docman/?subdir=3 TI DSP/Bridge project]

== dsp-link ==

A slimmer version of the dsp-bridge targeted for the DaVinci platform also developed by TI. It supports a wider variety of chips, not only OMAP.

It is the one farther from meeting Linux standards. The code hasn't even been submitted for reviewing nor is planned to to be merged at any time.

It's tightly tied to CodecEngine and DMAI, and there are GStreamer plug-ins provided by TI to use the algorithms.

Unlike the other implementations, it has strong support from the Angstrom distribution precisely because of wider platform support.

See [http://wiki.davincidsp.com/index.php?title=Category:DSPLink DSPLink articles in Texas Instruments Embedded Processors Wiki], too.

== References ==
<references/>

== Interesting threads ==

* [http://linux.omap.com/pipermail/linux-omap-open-source/2007-May/009850.html bridge vs link]
* [http://marc.info/?l=linux-omap&m=123626584228670&w=2 different power management]

BeagleBoard/DSP Clarification

2009-05-08T00:16:40Z

Felipec: copy-paste != good

BeagleBoard/DSP Clarification

2009-05-08T00:10:44Z

Felipec: Improve references

Talk:BeagleBoard/DSP Clarification

2009-05-08T00:05:28Z

Felipec:

Talk:BeagleBoard/DSP Clarification

2009-05-08T00:03:13Z

Felipec: Oldest implementation

dsp-gateway is not the oldest implementation, just the first one to be open source.--[[User:Jkridner|Jkridner]] 21:45, 6 May 2009 (UTC)

== Oldest implementation ==

Right I meant the oldest open source implementation.

BeagleBoard/DSP Clarification

2009-05-08T00:00:18Z

Felipec: /* dsp-bridge */ Some reverts and more explanations

BeagleBoard/DSP Clarification

2009-05-07T23:44:00Z

Felipec: /* dsp-bridge */ primiarily implies there are other contributors

BeagleBoard/DSP Clarification

2009-05-07T23:42:35Z

Felipec: Interesting threads

BeagleBoard/DSP Clarification

2009-05-06T21:44:43Z

Felipec: /* dsp-gateway */ fix

This article tries to explain all the different Linux DSP systems for OMAP chips, how they are similar and different.

== dsp-gateway ==

DSP Gateway was developed by Nokia for the Maemo Internet Tablets. It's the oldest and more open of the implementations. The open code consists not only of the linux kernel side, but also the DSP operating system. Unfortunately the development is essentially halted.

[http://dspgateway.sourceforge.net/pub/index.php?Page=FAQ Link].

It works on OMAP1 and OMAP2, it's production ready, used on the Nokia N800 and N810, it follows linux standards and it's close to upstream acceptance. There's code for OMAP3 but it hasn't been thoroughly tested.

It is maintained by Hiroshi DOYU.

There are a few user-space applications that use it. Essentially GStreamer Nokia DSP plugins and a few others developed by the Maemo community.

== dsp-bridge ==

tidspbridge originally developed by TI, but after being released as open source it has received many contributions, predominantly by Nokia.

It's probably not production ready (at least I don't know of any released product using it), and it still doesn't meet linux standards although there has been a lot of progress. Only the ARM side is available as open source, unlike the dsp-bridge, the DSP side is completely closed.

Unfortunately there's a disagreement between TI and the community as how power management must be handled, so there are two forks: linux-omap, and omapzoom.

It's under heavy development, originally maintained by Hiroshi DOYU, but now Ameya Palande took over.

There is plans to share the mailbox and iommu that the dsp-gateway uses, but it's independent from it, as well as to move parts of it to user-space.

There are slightly more user-space applications using it, including gst-openmax through TI's OpenMAX IL implementation which is also open source. and gst-goo.

== dsp-link ==

A slimmer version of the dsp-bridge targeted for the DaVinci platform also developed by TI. It supports a wider variety of chips, not only OMAP.

It is the one farther from meeting linux standards, the code hasn't even been submitted for reviewing nor is planned to to be merged at any time.

It's tightly tied to codecengine and dmai and there are GStreamer plug-ins provided by TI to use the algorithms.

BeagleBoard/DSP Clarification

2009-05-06T21:42:45Z

Felipec: Initial version

This article tries to explain all the different Linux DSP systems for OMAP chips, how they are similar and different.

== dsp-gateway ==

DSP Gateway was developed by Nokia for the Maemo Internet Tablets. It's the oldest and more open of the implementations. The open code consists not only of the linux kernel side, but also the DSP operating system. Unfortunately the development is essentially halted.

[http://dspgateway.sourceforge.net/pub/index.php?Page=FAQ Link].

It works on OMAP1 and OMAP2, it's production ready, used on the Nokia N800 and N810, it follows linux standards and it's close to upstream acceptance. There's code for OMAP3 but it has been thoroughly tested.

It is maintained by Hiroshi DOYU.

There are a few user-space applications that use it. Essentially GStreamer Nokia DSP plugins and a few others developed by the Maemo community.

== dsp-bridge ==

tidspbridge originally developed by TI, but after being released as open source it has received many contributions, predominantly by Nokia.

It's probably not production ready (at least I don't know of any released product using it), and it still doesn't meet linux standards although there has been a lot of progress. Only the ARM side is available as open source, unlike the dsp-bridge, the DSP side is completely closed.

Unfortunately there's a disagreement between TI and the community as how power management must be handled, so there are two forks: linux-omap, and omapzoom.

It's under heavy development, originally maintained by Hiroshi DOYU, but now Ameya Palande took over.

There is plans to share the mailbox and iommu that the dsp-gateway uses, but it's independent from it, as well as to move parts of it to user-space.

There are slightly more user-space applications using it, including gst-openmax through TI's OpenMAX IL implementation which is also open source. and gst-goo.

== dsp-link ==

A slimmer version of the dsp-bridge targeted for the DaVinci platform also developed by TI. It supports a wider variety of chips, not only OMAP.

It is the one farther from meeting linux standards, the code hasn't even been submitted for reviewing nor is planned to to be merged at any time.

It's tightly tied to codecengine and dmai and there are GStreamer plug-ins provided by TI to use the algorithms.

BeagleBoard/gst-openmax

2009-05-06T19:44:00Z

Felipec: /* gst-openmax */ Remove stuff that's not needed any more

[[Category: Linux]]
[[Category: OMAP]]
This article explains how to use TI's DSP with GStreamer (e.g. on [[BeagleBoard|BeagleBoard]]). You need to have the DSP properly set up following [[BeagleBoard/DSP_Howto]].

= Setup =

== OpenMAX IL ==

The easiest way to use the DSP capabilities is through the [http://www.khronos.org/openmax/ OpenMAX IL] API, but in order to compile TI's implementation a special DSP library is required.

=== libdspbridge ===

git clone git://github.com/felipec/libdspbridge.git
cd libdspbridge
make DESTDIR='''rootfs''' install

=== libomxil-ti ===

git clone git://github.com/felipec/libomxil-ti.git
cd libomxil-ti
make BRIDGE_CFLAGS=-I../'''libdspbridge'''/inc BRIDGE_LIBS=-L../'''libdspbridge'''/lib DESTDIR='''rootfs''' install

== gst-openmax ==

You would need to compile gst-openmax inside scratchbox:

git clone git://github.com/felipec/gst-openmax.git
cd gst-openmax
git checkout -b omap origin/omap
./autogen.sh --noconfigure
./configure --prefix=/usr
make DESTDIR='''rootfs''' install

= Related stuff =

In order to get the omapfb usable for video playback you need this kernel argument:
video=omapfb:vram:2M,vram:4M

And the GStreamer element:
git clone git://github.com/felipec/gst-omapfb.git
cd gst-omapfb
make DESTDIR='''rootfs''' install

= Running =

You should be able to use the gst-openmax elements now:

gst-launch-0.10 filesrc location="foobar.avi" ! avidemux ! omx_mpeg4dec ! omapfbsink

BeagleBoard/gst-openmax

2009-05-06T19:43:02Z

Felipec: /* gst-openmax */ Use omap branch!

[[Category: Linux]]
[[Category: OMAP]]
This article explains how to use TI's DSP with GStreamer (e.g. on [[BeagleBoard|BeagleBoard]]). You need to have the DSP properly set up following [[BeagleBoard/DSP_Howto]].

= Setup =

== OpenMAX IL ==

The easiest way to use the DSP capabilities is through the [http://www.khronos.org/openmax/ OpenMAX IL] API, but in order to compile TI's implementation a special DSP library is required.

=== libdspbridge ===

git clone git://github.com/felipec/libdspbridge.git
cd libdspbridge
make DESTDIR='''rootfs''' install

=== libomxil-ti ===

git clone git://github.com/felipec/libomxil-ti.git
cd libomxil-ti
make BRIDGE_CFLAGS=-I../'''libdspbridge'''/inc BRIDGE_LIBS=-L../'''libdspbridge'''/lib DESTDIR='''rootfs''' install

== gst-openmax ==

You would need to compile gst-openmax inside scratchbox:

git clone git://github.com/felipec/gst-openmax.git
cd gst-openmax
git checkout -b omap origin/omap
./autogen.sh --noconfigure
./configure --prefix=/usr
make DESTDIR='''rootfs''' install

PS: according to this thread http://groups.google.com/group/beagleboard/browse_thread/thread/335c2f6cb7b2adc5?pli=1, you will need to fetch the common directory from http://cgit.freedesktop.org/~bilboed/common/ for the autogen.sh script to work

= Related stuff =

In order to get the omapfb usable for video playback you need this kernel argument:
video=omapfb:vram:2M,vram:4M

And the GStreamer element:
git clone git://github.com/felipec/gst-omapfb.git
cd gst-omapfb
make DESTDIR='''rootfs''' install

= Running =

You should be able to use the gst-openmax elements now:

gst-launch-0.10 filesrc location="foobar.avi" ! avidemux ! omx_mpeg4dec ! omapfbsink

BeagleBoard/DSP Howto

2009-04-10T22:29:37Z

Felipec: /* Simplified */

[[Category: Linux]]
[[Category: OMAP]]
This article explains how to use the DSP in [http://focus.ti.com/general/docs/gencontent.tsp?contentId=36915&DCMP=OMAP_Feb27_2008&HQS=Other+PR+omap3503pr OMAP3] at [[BeagleBoard|BeagleBoard]] with TI's deliverables. For DSP tool chain see [[BeagleBoard#C64x.2B_DSP|C64x+ DSP]].

= Setup =

== Kernel driver ==

In order to use the DSP you would need TI's bridgedriver module on the kernel. You can use my branch in github that is based on 2.6.28-omap1 and has DSS2 too.

<code>
git clone git://github.com/felipec/linux-omap.git
git checkout -b felipec v2.6.28-felipec1
cd linux-omap
make omap3_beagle_defconfig
make
</code>

Then build the '''uImage''' as usual and install the modules on your rootfs:
make INSTALL_MOD_PATH=/media/rootfs modules_install

== TI binaries ==

In order to get the DSP binaries for multimedia processing you need to download TI's OpenMAX IL [https://omapzoom.org/gf/download/frsrelease/111/396/tiopenmax-0.3.tar.gz package]. Once you have extracted the tarball you'll have to run the installer ''TI-OMX-Sample-Firmware-0.3-Linux-x86-Install'' and accept the license agreement.

You would end up with a bunch of binaries in <code>lib/dsp</code>, copy them to your root filesystem at the same location (/lib/dsp).

=== ping test ===

If you want to test the DSP you can try the simple ping test provided in this [https://omapzoom.org/gf/download/frsrelease/132/632/dspbridge_binaries.tar.bz2 package].

Just:
./ping.out

If you get an error like:
DSPNode_Allocate failed: 0x80008008

Then it's possible that the ping DSP socket node is not loaded. If you use 'baseimage.dof' you need to load it dynamically:

./dynreg.out -r pingdyn_3430.dll64P

On the other hand, 'ddspbase_tiomap3430.dof64P' has the node statically included, so there's no need to do that.

= Running =

On the board use this to load the module:

modprobe bridgedriver base_img=/lib/dsp/baseimage.dof

= Developing =

There are two ways to compile your own DSP nodes; the official one which requires XDC tools, and the simplified one (which I prefer).

== Official ==

Download the dsp-bridge examples from the [https://omapzoom.org/gf/download/frsrelease/147/848/dspbridge_LDP_v1.8.tar.gz omapzoom project]. Once you extract the main tarball you'll need to extract the individual tarballs on the same directory, so you have something like:

config.bld
documents
dsp
mpu_api
mpu_driver
product.mak
samplemakefile
samples

=== DSP side ===

You'll need the [https://www-a.ti.com/downloads/sds_support/targetcontent/LinuxDspTools/download.html C6x compiler], extract it in "/opt/dsp/cgt6x-6.0.22". The recommended version is '''v6.0.22'''.

You'll need the "DSP/BIOS" package and "RTSC/XDCtools" in order to compile the dsp-brige examples, you can download them from [https://www-a.ti.com/downloads/sds_support/targetcontent/index.html here]. Here we will assume they are installed in "/opt/dsp".

Edit "product.mak" to match the version of your tools. Then run:
make -f samplemakefile .bridge_samples DD_XDCDIR=/opt/dsp/xdctools_3_10_02 SABIOS_DIR=/opt/dsp/bios_5_33_04/packages DEPOT=/opt/dsp

=== ARM side ===

You'll need to prepare a '''target''' directory:
export target=/tmp/dsp-target
mkdir -p $target/lib

Also, build libbridge and libqos:
cd mpu_api/src
make PREFIX=$target/.. CROSS=arm-linux- install

To build the examples:
cd samples/mpu/src
make PREFIX=$target/.. CROSS=arm-linux- LIBINCLUDES=$target/lib LDPATH=$target/lib install

All you need will be on '/tmp/dsp-target'.

== Simplified ==

In order to develop dynamic dsp nodes you'll need a [https://www-a.ti.com/downloads/sds_support/targetcontent/LinuxDspTools/download.html C6x compiler] (the recommended version is '''v6.1.7''') and doffbuild tools.

=== doffbuild tools ===

The only relevant tool is DLLcreate, which can be found in TI's omapzoom site, on the [http://omapzoom.org/gf/download/frsrelease/108/421/dspbridge_dsp.tar.gz dspbridge_dsp] package.

mkdir -p tmp
tar -xf dspbridge_dsp.tar.gz -C tmp
mv tmp/dsp/bdsptools/packages/ti/dspbridge/dsp/doffbuild /opt/doffbuild
rm -rf tmp

=== libdspbridge ===

This library is used by the user-space applications.

git clone git://github.com/felipec/libdspbridge.git
cd libdspbridge
make DESTDIR='''$rootfs''' install

=== Example dsp node ===

Here is an [http://github.com/felipec/dsp-dummy example dsp node] that is simply passing buffers back and forth.

git clone git://github.com/felipec/dsp-dummy.git
make DSP_TOOLS=/opt/dsptools DSP_DOFFBUILD=/opt/doffbuild BRIDGE_DIR=../libdspbridge

As a result you'll have two binaries; '''dummy.dll64P''' for dsp-side, and '''dummy''' for arm-side.

To load the dynamic node:
/dspbridge/dynreg.out -r /lib/dsp/dummy.dll64P

Now you can run the '''dummy''' test application.

= More information =

* [[BeagleBoard/gst-openmax]]

BeagleBoard/DSP Howto

2009-04-10T22:28:13Z

Felipec: /* Kernel driver */

[[Category: Linux]]
[[Category: OMAP]]
This article explains how to use the DSP in [http://focus.ti.com/general/docs/gencontent.tsp?contentId=36915&DCMP=OMAP_Feb27_2008&HQS=Other+PR+omap3503pr OMAP3] at [[BeagleBoard|BeagleBoard]] with TI's deliverables. For DSP tool chain see [[BeagleBoard#C64x.2B_DSP|C64x+ DSP]].

= Setup =

== Kernel driver ==

In order to use the DSP you would need TI's bridgedriver module on the kernel. You can use my branch in github that is based on 2.6.28-omap1 and has DSS2 too.

<code>
git clone git://github.com/felipec/linux-omap.git
git checkout -b felipec v2.6.28-felipec1
cd linux-omap
make omap3_beagle_defconfig
make
</code>

Then build the '''uImage''' as usual and install the modules on your rootfs:
make INSTALL_MOD_PATH=/media/rootfs modules_install

== TI binaries ==

In order to get the DSP binaries for multimedia processing you need to download TI's OpenMAX IL [https://omapzoom.org/gf/download/frsrelease/111/396/tiopenmax-0.3.tar.gz package]. Once you have extracted the tarball you'll have to run the installer ''TI-OMX-Sample-Firmware-0.3-Linux-x86-Install'' and accept the license agreement.

You would end up with a bunch of binaries in <code>lib/dsp</code>, copy them to your root filesystem at the same location (/lib/dsp).

=== ping test ===

If you want to test the DSP you can try the simple ping test provided in this [https://omapzoom.org/gf/download/frsrelease/132/632/dspbridge_binaries.tar.bz2 package].

Just:
./ping.out

If you get an error like:
DSPNode_Allocate failed: 0x80008008

Then it's possible that the ping DSP socket node is not loaded. If you use 'baseimage.dof' you need to load it dynamically:

./dynreg.out -r pingdyn_3430.dll64P

On the other hand, 'ddspbase_tiomap3430.dof64P' has the node statically included, so there's no need to do that.

= Running =

On the board use this to load the module:

modprobe bridgedriver base_img=/lib/dsp/baseimage.dof

= Developing =

There are two ways to compile your own DSP nodes; the official one which requires XDC tools, and the simplified one (which I prefer).

== Official ==

Download the dsp-bridge examples from the [https://omapzoom.org/gf/download/frsrelease/147/848/dspbridge_LDP_v1.8.tar.gz omapzoom project]. Once you extract the main tarball you'll need to extract the individual tarballs on the same directory, so you have something like:

config.bld
documents
dsp
mpu_api
mpu_driver
product.mak
samplemakefile
samples

=== DSP side ===

You'll need the [https://www-a.ti.com/downloads/sds_support/targetcontent/LinuxDspTools/download.html C6x compiler], extract it in "/opt/dsp/cgt6x-6.0.22". The recommended version is '''v6.0.22'''.

You'll need the "DSP/BIOS" package and "RTSC/XDCtools" in order to compile the dsp-brige examples, you can download them from [https://www-a.ti.com/downloads/sds_support/targetcontent/index.html here]. Here we will assume they are installed in "/opt/dsp".

Edit "product.mak" to match the version of your tools. Then run:
make -f samplemakefile .bridge_samples DD_XDCDIR=/opt/dsp/xdctools_3_10_02 SABIOS_DIR=/opt/dsp/bios_5_33_04/packages DEPOT=/opt/dsp

=== ARM side ===

You'll need to prepare a '''target''' directory:
export target=/tmp/dsp-target
mkdir -p $target/lib

Also, build libbridge and libqos:
cd mpu_api/src
make PREFIX=$target/.. CROSS=arm-linux- install

To build the examples:
cd samples/mpu/src
make PREFIX=$target/.. CROSS=arm-linux- LIBINCLUDES=$target/lib LDPATH=$target/lib install

All you need will be on '/tmp/dsp-target'.

== Simplified ==

In order to develop dynamic dsp nodes you'll need a [https://www-a.ti.com/downloads/sds_support/targetcontent/LinuxDspTools/download.html C6x compiler] (only 6.0.x seem to work) and doffbuild tools. The recommended version is '''v6.0.22'''.

=== doffbuild tools ===

The only relevant tool is DLLcreate, which can be found in TI's omapzoom site, on the [http://omapzoom.org/gf/download/frsrelease/108/421/dspbridge_dsp.tar.gz dspbridge_dsp] package.

mkdir -p tmp
tar -xf dspbridge_dsp.tar.gz -C tmp
mv tmp/dsp/bdsptools/packages/ti/dspbridge/dsp/doffbuild /opt/doffbuild
rm -rf tmp

=== libdspbridge ===

This library is used by the user-space applications.

git clone git://github.com/felipec/libdspbridge.git
cd libdspbridge
make DESTDIR='''$rootfs''' install

=== Example dsp node ===

Here is an [http://github.com/felipec/dsp-dummy example dsp node] that is simply passing buffers back and forth.

git clone git://github.com/felipec/dsp-dummy.git
make DSP_TOOLS=/opt/dsptools DSP_DOFFBUILD=/opt/doffbuild BRIDGE_DIR=../libdspbridge

As a result you'll have two binaries; '''dummy.dll64P''' for dsp-side, and '''dummy''' for arm-side.

To load the dynamic node:
/dspbridge/dynreg.out -r /lib/dsp/dummy.dll64P

Now you can run the '''dummy''' test application.

= More information =

* [[BeagleBoard/gst-openmax]]

BeagleBoard/DSP Howto

2009-04-10T22:25:34Z

Felipec: /* Kernel driver */ update

[[Category: Linux]]
[[Category: OMAP]]
This article explains how to use the DSP in [http://focus.ti.com/general/docs/gencontent.tsp?contentId=36915&DCMP=OMAP_Feb27_2008&HQS=Other+PR+omap3503pr OMAP3] at [[BeagleBoard|BeagleBoard]] with TI's deliverables. For DSP tool chain see [[BeagleBoard#C64x.2B_DSP|C64x+ DSP]].

= Setup =

== Kernel driver ==

In order to use the DSP you would need TI's bridgedriver module on the kernel. You can use my branch in github that is based on 2.6.28-omap1 and has DSS2 too.

<code>
git clone git://github.com/felipec/linux-omap.git
git checkout -b felipec v2.6.28-felipec1
cd linux-omap
make omap3_beagle_defconfig
make
</code>

== TI binaries ==

In order to get the DSP binaries for multimedia processing you need to download TI's OpenMAX IL [https://omapzoom.org/gf/download/frsrelease/111/396/tiopenmax-0.3.tar.gz package]. Once you have extracted the tarball you'll have to run the installer ''TI-OMX-Sample-Firmware-0.3-Linux-x86-Install'' and accept the license agreement.

You would end up with a bunch of binaries in <code>lib/dsp</code>, copy them to your root filesystem at the same location (/lib/dsp).

=== ping test ===

If you want to test the DSP you can try the simple ping test provided in this [https://omapzoom.org/gf/download/frsrelease/132/632/dspbridge_binaries.tar.bz2 package].

Just:
./ping.out

If you get an error like:
DSPNode_Allocate failed: 0x80008008

Then it's possible that the ping DSP socket node is not loaded. If you use 'baseimage.dof' you need to load it dynamically:

./dynreg.out -r pingdyn_3430.dll64P

On the other hand, 'ddspbase_tiomap3430.dof64P' has the node statically included, so there's no need to do that.

= Running =

On the board use this to load the module:

modprobe bridgedriver base_img=/lib/dsp/baseimage.dof

= Developing =

There are two ways to compile your own DSP nodes; the official one which requires XDC tools, and the simplified one (which I prefer).

== Official ==

Download the dsp-bridge examples from the [https://omapzoom.org/gf/download/frsrelease/147/848/dspbridge_LDP_v1.8.tar.gz omapzoom project]. Once you extract the main tarball you'll need to extract the individual tarballs on the same directory, so you have something like:

config.bld
documents
dsp
mpu_api
mpu_driver
product.mak
samplemakefile
samples

=== DSP side ===

You'll need the [https://www-a.ti.com/downloads/sds_support/targetcontent/LinuxDspTools/download.html C6x compiler], extract it in "/opt/dsp/cgt6x-6.0.22". The recommended version is '''v6.0.22'''.

You'll need the "DSP/BIOS" package and "RTSC/XDCtools" in order to compile the dsp-brige examples, you can download them from [https://www-a.ti.com/downloads/sds_support/targetcontent/index.html here]. Here we will assume they are installed in "/opt/dsp".

Edit "product.mak" to match the version of your tools. Then run:
make -f samplemakefile .bridge_samples DD_XDCDIR=/opt/dsp/xdctools_3_10_02 SABIOS_DIR=/opt/dsp/bios_5_33_04/packages DEPOT=/opt/dsp

=== ARM side ===

You'll need to prepare a '''target''' directory:
export target=/tmp/dsp-target
mkdir -p $target/lib

Also, build libbridge and libqos:
cd mpu_api/src
make PREFIX=$target/.. CROSS=arm-linux- install

To build the examples:
cd samples/mpu/src
make PREFIX=$target/.. CROSS=arm-linux- LIBINCLUDES=$target/lib LDPATH=$target/lib install

All you need will be on '/tmp/dsp-target'.

== Simplified ==

In order to develop dynamic dsp nodes you'll need a [https://www-a.ti.com/downloads/sds_support/targetcontent/LinuxDspTools/download.html C6x compiler] (only 6.0.x seem to work) and doffbuild tools. The recommended version is '''v6.0.22'''.

=== doffbuild tools ===

The only relevant tool is DLLcreate, which can be found in TI's omapzoom site, on the [http://omapzoom.org/gf/download/frsrelease/108/421/dspbridge_dsp.tar.gz dspbridge_dsp] package.

mkdir -p tmp
tar -xf dspbridge_dsp.tar.gz -C tmp
mv tmp/dsp/bdsptools/packages/ti/dspbridge/dsp/doffbuild /opt/doffbuild
rm -rf tmp

=== libdspbridge ===

This library is used by the user-space applications.

git clone git://github.com/felipec/libdspbridge.git
cd libdspbridge
make DESTDIR='''$rootfs''' install

=== Example dsp node ===

Here is an [http://github.com/felipec/dsp-dummy example dsp node] that is simply passing buffers back and forth.

git clone git://github.com/felipec/dsp-dummy.git
make DSP_TOOLS=/opt/dsptools DSP_DOFFBUILD=/opt/doffbuild BRIDGE_DIR=../libdspbridge

As a result you'll have two binaries; '''dummy.dll64P''' for dsp-side, and '''dummy''' for arm-side.

To load the dynamic node:
/dspbridge/dynreg.out -r /lib/dsp/dummy.dll64P

Now you can run the '''dummy''' test application.

= More information =

* [[BeagleBoard/gst-openmax]]

BeagleBoard/DSP Howto

2009-04-10T14:07:03Z

Felipec: /* Simplified */

[[Category: Linux]]
[[Category: OMAP]]
This article explains how to use the DSP in [http://focus.ti.com/general/docs/gencontent.tsp?contentId=36915&DCMP=OMAP_Feb27_2008&HQS=Other+PR+omap3503pr OMAP3] at [[BeagleBoard|BeagleBoard]] with TI's deliverables. For DSP tool chain see [[BeagleBoard#C64x.2B_DSP|C64x+ DSP]].

= Setup =

== Kernel driver ==

In order to use the DSP you would need TI's bridgedriver module on the kernel. For that you would need Hiroshi's [http://4869037.web.fc2.com/tidspbridge-20080922.tgz patches] on top of linux-omap:

<code>
git clone http://www.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap-2.6.git
cd linux-omap-2.6
wget http://4869037.web.fc2.com/tidspbridge-20081021.tgz
tar xvzf tidspbridge-20081021.tgz
git am *.patch
make omap3_beagle_defconfig
</code>

Then <code>make menuconfig</code> and add the following options in the menuconfig:
<pre>
CONFIG_FB_OMAP_CONSISTENT_DMA_SIZE=14 #in Device Drivers->Graphics support->Support for frame buffer devices->Consistent DMA memory size
CONFIG_MPU_BRIDGE=m #in Device Drivers->DSP Bridge driver
</pre>

== TI binaries ==

In order to get the DSP binaries for multimedia processing you need to download TI's OpenMAX IL [https://omapzoom.org/gf/download/frsrelease/111/396/tiopenmax-0.3.tar.gz package]. Once you have extracted the tarball you'll have to run the installer ''TI-OMX-Sample-Firmware-0.3-Linux-x86-Install'' and accept the license agreement.

You would end up with a bunch of binaries in <code>lib/dsp</code>, copy them to your root filesystem at the same location (/lib/dsp).

=== ping test ===

If you want to test the DSP you can try the simple ping test provided in this [https://omapzoom.org/gf/download/frsrelease/132/632/dspbridge_binaries.tar.bz2 package].

Just:
./ping.out

If you get an error like:
DSPNode_Allocate failed: 0x80008008

Then it's possible that the ping DSP socket node is not loaded. If you use 'baseimage.dof' you need to load it dynamically:

./dynreg.out -r pingdyn_3430.dll64P

On the other hand, 'ddspbase_tiomap3430.dof64P' has the node statically included, so there's no need to do that.

= Running =

On the board use this to load the module:

modprobe bridgedriver base_img=/lib/dsp/baseimage.dof

= Developing =

There are two ways to compile your own DSP nodes; the official one which requires XDC tools, and the simplified one (which I prefer).

== Official ==

Download the dsp-bridge examples from the [https://omapzoom.org/gf/download/frsrelease/147/848/dspbridge_LDP_v1.8.tar.gz omapzoom project]. Once you extract the main tarball you'll need to extract the individual tarballs on the same directory, so you have something like:

config.bld
documents
dsp
mpu_api
mpu_driver
product.mak
samplemakefile
samples

=== DSP side ===

You'll need the [https://www-a.ti.com/downloads/sds_support/targetcontent/LinuxDspTools/download.html C6x compiler], extract it in "/opt/dsp/cgt6x-6.0.22". The recommended version is '''v6.0.22'''.

You'll need the "DSP/BIOS" package and "RTSC/XDCtools" in order to compile the dsp-brige examples, you can download them from [https://www-a.ti.com/downloads/sds_support/targetcontent/index.html here]. Here we will assume they are installed in "/opt/dsp".

Edit "product.mak" to match the version of your tools. Then run:
make -f samplemakefile .bridge_samples DD_XDCDIR=/opt/dsp/xdctools_3_10_02 SABIOS_DIR=/opt/dsp/bios_5_33_04/packages DEPOT=/opt/dsp

=== ARM side ===

You'll need to prepare a '''target''' directory:
export target=/tmp/dsp-target
mkdir -p $target/lib

Also, build libbridge and libqos:
cd mpu_api/src
make PREFIX=$target/.. CROSS=arm-linux- install

To build the examples:
cd samples/mpu/src
make PREFIX=$target/.. CROSS=arm-linux- LIBINCLUDES=$target/lib LDPATH=$target/lib install

All you need will be on '/tmp/dsp-target'.

== Simplified ==

In order to develop dynamic dsp nodes you'll need a [https://www-a.ti.com/downloads/sds_support/targetcontent/LinuxDspTools/download.html C6x compiler] (only 6.0.x seem to work) and doffbuild tools. The recommended version is '''v6.0.22'''.

=== doffbuild tools ===

The only relevant tool is DLLcreate, which can be found in TI's omapzoom site, on the [http://omapzoom.org/gf/download/frsrelease/108/421/dspbridge_dsp.tar.gz dspbridge_dsp] package.

mkdir -p tmp
tar -xf dspbridge_dsp.tar.gz -C tmp
mv tmp/dsp/bdsptools/packages/ti/dspbridge/dsp/doffbuild /opt/doffbuild
rm -rf tmp

=== libdspbridge ===

This library is used by the user-space applications.

git clone git://github.com/felipec/libdspbridge.git
cd libdspbridge
make DESTDIR='''$rootfs''' install

=== Example dsp node ===

Here is an [http://github.com/felipec/dsp-dummy example dsp node] that is simply passing buffers back and forth.

git clone git://github.com/felipec/dsp-dummy.git
make DSP_TOOLS=/opt/dsptools DSP_DOFFBUILD=/opt/doffbuild BRIDGE_DIR=../libdspbridge

As a result you'll have two binaries; '''dummy.dll64P''' for dsp-side, and '''dummy''' for arm-side.

To load the dynamic node:
/dspbridge/dynreg.out -r /lib/dsp/dummy.dll64P

Now you can run the '''dummy''' test application.

= More information =

* [[BeagleBoard/gst-openmax]]

BeagleBoard/DSP Howto

2009-04-10T14:05:29Z

Felipec: /* DSP side */

[[Category: Linux]]
[[Category: OMAP]]
This article explains how to use the DSP in [http://focus.ti.com/general/docs/gencontent.tsp?contentId=36915&DCMP=OMAP_Feb27_2008&HQS=Other+PR+omap3503pr OMAP3] at [[BeagleBoard|BeagleBoard]] with TI's deliverables. For DSP tool chain see [[BeagleBoard#C64x.2B_DSP|C64x+ DSP]].

= Setup =

== Kernel driver ==

In order to use the DSP you would need TI's bridgedriver module on the kernel. For that you would need Hiroshi's [http://4869037.web.fc2.com/tidspbridge-20080922.tgz patches] on top of linux-omap:

<code>
git clone http://www.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap-2.6.git
cd linux-omap-2.6
wget http://4869037.web.fc2.com/tidspbridge-20081021.tgz
tar xvzf tidspbridge-20081021.tgz
git am *.patch
make omap3_beagle_defconfig
</code>

Then <code>make menuconfig</code> and add the following options in the menuconfig:
<pre>
CONFIG_FB_OMAP_CONSISTENT_DMA_SIZE=14 #in Device Drivers->Graphics support->Support for frame buffer devices->Consistent DMA memory size
CONFIG_MPU_BRIDGE=m #in Device Drivers->DSP Bridge driver
</pre>

== TI binaries ==

In order to get the DSP binaries for multimedia processing you need to download TI's OpenMAX IL [https://omapzoom.org/gf/download/frsrelease/111/396/tiopenmax-0.3.tar.gz package]. Once you have extracted the tarball you'll have to run the installer ''TI-OMX-Sample-Firmware-0.3-Linux-x86-Install'' and accept the license agreement.

You would end up with a bunch of binaries in <code>lib/dsp</code>, copy them to your root filesystem at the same location (/lib/dsp).

=== ping test ===

If you want to test the DSP you can try the simple ping test provided in this [https://omapzoom.org/gf/download/frsrelease/132/632/dspbridge_binaries.tar.bz2 package].

Just:
./ping.out

If you get an error like:
DSPNode_Allocate failed: 0x80008008

Then it's possible that the ping DSP socket node is not loaded. If you use 'baseimage.dof' you need to load it dynamically:

./dynreg.out -r pingdyn_3430.dll64P

On the other hand, 'ddspbase_tiomap3430.dof64P' has the node statically included, so there's no need to do that.

= Running =

On the board use this to load the module:

modprobe bridgedriver base_img=/lib/dsp/baseimage.dof

= Developing =

There are two ways to compile your own DSP nodes; the official one which requires XDC tools, and the simplified one (which I prefer).

== Official ==

Download the dsp-bridge examples from the [https://omapzoom.org/gf/download/frsrelease/147/848/dspbridge_LDP_v1.8.tar.gz omapzoom project]. Once you extract the main tarball you'll need to extract the individual tarballs on the same directory, so you have something like:

config.bld
documents
dsp
mpu_api
mpu_driver
product.mak
samplemakefile
samples

=== DSP side ===

You'll need the [https://www-a.ti.com/downloads/sds_support/targetcontent/LinuxDspTools/download.html C6x compiler], extract it in "/opt/dsp/cgt6x-6.0.22". The recommended version is '''v6.0.22'''.

You'll need the "DSP/BIOS" package and "RTSC/XDCtools" in order to compile the dsp-brige examples, you can download them from [https://www-a.ti.com/downloads/sds_support/targetcontent/index.html here]. Here we will assume they are installed in "/opt/dsp".

Edit "product.mak" to match the version of your tools. Then run:
make -f samplemakefile .bridge_samples DD_XDCDIR=/opt/dsp/xdctools_3_10_02 SABIOS_DIR=/opt/dsp/bios_5_33_04/packages DEPOT=/opt/dsp

=== ARM side ===

You'll need to prepare a '''target''' directory:
export target=/tmp/dsp-target
mkdir -p $target/lib

Also, build libbridge and libqos:
cd mpu_api/src
make PREFIX=$target/.. CROSS=arm-linux- install

To build the examples:
cd samples/mpu/src
make PREFIX=$target/.. CROSS=arm-linux- LIBINCLUDES=$target/lib LDPATH=$target/lib install

All you need will be on '/tmp/dsp-target'.

== Simplified ==

In order to develop dynamic dsp nodes you'll need a [https://www-a.ti.com/downloads/sds_support/targetcontent/LinuxDspTools/download.html C6x compiler] and doffbuild tools.

Apparently the only version that works is v6.0.16.

=== doffbuild tools ===

The only relevant tool is DLLcreate, which can be found in TI's omapzoom site, on the [http://omapzoom.org/gf/download/frsrelease/108/421/dspbridge_dsp.tar.gz dspbridge_dsp] package.

mkdir -p tmp
tar -xf dspbridge_dsp.tar.gz -C tmp
mv tmp/dsp/bdsptools/packages/ti/dspbridge/dsp/doffbuild /opt/doffbuild
rm -rf tmp

=== libdspbridge ===

This library is used by the user-space applications.

git clone git://github.com/felipec/libdspbridge.git
cd libdspbridge
make DESTDIR='''$rootfs''' install

=== Example dsp node ===

Here is an [http://github.com/felipec/dsp-dummy example dsp node] that is simply passing buffers back and forth.

git clone git://github.com/felipec/dsp-dummy.git
make DSP_TOOLS=/opt/dsptools DSP_DOFFBUILD=/opt/doffbuild BRIDGE_DIR=../libdspbridge

As a result you'll have two binaries; '''dummy.dll64P''' for dsp-side, and '''dummy''' for arm-side.

To load the dynamic node:
/dspbridge/dynreg.out -r /lib/dsp/dummy.dll64P

Now you can run the '''dummy''' test application.

= More information =

* [[BeagleBoard/gst-openmax]]

BeagleBoard/DSP Howto

2009-04-10T14:05:08Z

Felipec: /* DSP side */

[[Category: Linux]]
[[Category: OMAP]]
This article explains how to use the DSP in [http://focus.ti.com/general/docs/gencontent.tsp?contentId=36915&DCMP=OMAP_Feb27_2008&HQS=Other+PR+omap3503pr OMAP3] at [[BeagleBoard|BeagleBoard]] with TI's deliverables. For DSP tool chain see [[BeagleBoard#C64x.2B_DSP|C64x+ DSP]].

= Setup =

== Kernel driver ==

In order to use the DSP you would need TI's bridgedriver module on the kernel. For that you would need Hiroshi's [http://4869037.web.fc2.com/tidspbridge-20080922.tgz patches] on top of linux-omap:

<code>
git clone http://www.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap-2.6.git
cd linux-omap-2.6
wget http://4869037.web.fc2.com/tidspbridge-20081021.tgz
tar xvzf tidspbridge-20081021.tgz
git am *.patch
make omap3_beagle_defconfig
</code>

Then <code>make menuconfig</code> and add the following options in the menuconfig:
<pre>
CONFIG_FB_OMAP_CONSISTENT_DMA_SIZE=14 #in Device Drivers->Graphics support->Support for frame buffer devices->Consistent DMA memory size
CONFIG_MPU_BRIDGE=m #in Device Drivers->DSP Bridge driver
</pre>

== TI binaries ==

In order to get the DSP binaries for multimedia processing you need to download TI's OpenMAX IL [https://omapzoom.org/gf/download/frsrelease/111/396/tiopenmax-0.3.tar.gz package]. Once you have extracted the tarball you'll have to run the installer ''TI-OMX-Sample-Firmware-0.3-Linux-x86-Install'' and accept the license agreement.

You would end up with a bunch of binaries in <code>lib/dsp</code>, copy them to your root filesystem at the same location (/lib/dsp).

=== ping test ===

If you want to test the DSP you can try the simple ping test provided in this [https://omapzoom.org/gf/download/frsrelease/132/632/dspbridge_binaries.tar.bz2 package].

Just:
./ping.out

If you get an error like:
DSPNode_Allocate failed: 0x80008008

Then it's possible that the ping DSP socket node is not loaded. If you use 'baseimage.dof' you need to load it dynamically:

./dynreg.out -r pingdyn_3430.dll64P

On the other hand, 'ddspbase_tiomap3430.dof64P' has the node statically included, so there's no need to do that.

= Running =

On the board use this to load the module:

modprobe bridgedriver base_img=/lib/dsp/baseimage.dof

= Developing =

There are two ways to compile your own DSP nodes; the official one which requires XDC tools, and the simplified one (which I prefer).

== Official ==

Download the dsp-bridge examples from the [https://omapzoom.org/gf/download/frsrelease/147/848/dspbridge_LDP_v1.8.tar.gz omapzoom project]. Once you extract the main tarball you'll need to extract the individual tarballs on the same directory, so you have something like:

config.bld
documents
dsp
mpu_api
mpu_driver
product.mak
samplemakefile
samples

=== DSP side ===

You'll need the [https://www-a.ti.com/downloads/sds_support/targetcontent/LinuxDspTools/download.html C6x compiler], extract it in "/opt/dsp/cgt6x-6.0.22". The recommended version is ''v6.0.22''.

You'll need the "DSP/BIOS" package and "RTSC/XDCtools" in order to compile the dsp-brige examples, you can download them from [https://www-a.ti.com/downloads/sds_support/targetcontent/index.html here]. Here we will assume they are installed in "/opt/dsp".

Edit "product.mak" to match the version of your tools. Then run:
make -f samplemakefile .bridge_samples DD_XDCDIR=/opt/dsp/xdctools_3_10_02 SABIOS_DIR=/opt/dsp/bios_5_33_04/packages DEPOT=/opt/dsp

=== ARM side ===

You'll need to prepare a '''target''' directory:
export target=/tmp/dsp-target
mkdir -p $target/lib

Also, build libbridge and libqos:
cd mpu_api/src
make PREFIX=$target/.. CROSS=arm-linux- install

To build the examples:
cd samples/mpu/src
make PREFIX=$target/.. CROSS=arm-linux- LIBINCLUDES=$target/lib LDPATH=$target/lib install

All you need will be on '/tmp/dsp-target'.

== Simplified ==

In order to develop dynamic dsp nodes you'll need a [https://www-a.ti.com/downloads/sds_support/targetcontent/LinuxDspTools/download.html C6x compiler] and doffbuild tools.

Apparently the only version that works is v6.0.16.

=== doffbuild tools ===

The only relevant tool is DLLcreate, which can be found in TI's omapzoom site, on the [http://omapzoom.org/gf/download/frsrelease/108/421/dspbridge_dsp.tar.gz dspbridge_dsp] package.

mkdir -p tmp
tar -xf dspbridge_dsp.tar.gz -C tmp
mv tmp/dsp/bdsptools/packages/ti/dspbridge/dsp/doffbuild /opt/doffbuild
rm -rf tmp

=== libdspbridge ===

This library is used by the user-space applications.

git clone git://github.com/felipec/libdspbridge.git
cd libdspbridge
make DESTDIR='''$rootfs''' install

=== Example dsp node ===

Here is an [http://github.com/felipec/dsp-dummy example dsp node] that is simply passing buffers back and forth.

git clone git://github.com/felipec/dsp-dummy.git
make DSP_TOOLS=/opt/dsptools DSP_DOFFBUILD=/opt/doffbuild BRIDGE_DIR=../libdspbridge

As a result you'll have two binaries; '''dummy.dll64P''' for dsp-side, and '''dummy''' for arm-side.

To load the dynamic node:
/dspbridge/dynreg.out -r /lib/dsp/dummy.dll64P

Now you can run the '''dummy''' test application.

= More information =

* [[BeagleBoard/gst-openmax]]

BeagleBoard/DSP Howto

2009-04-10T13:33:36Z

Felipec: /* ARM side */

[[Category: Linux]]
[[Category: OMAP]]
This article explains how to use the DSP in [http://focus.ti.com/general/docs/gencontent.tsp?contentId=36915&DCMP=OMAP_Feb27_2008&HQS=Other+PR+omap3503pr OMAP3] at [[BeagleBoard|BeagleBoard]] with TI's deliverables. For DSP tool chain see [[BeagleBoard#C64x.2B_DSP|C64x+ DSP]].

= Setup =

== Kernel driver ==

In order to use the DSP you would need TI's bridgedriver module on the kernel. For that you would need Hiroshi's [http://4869037.web.fc2.com/tidspbridge-20080922.tgz patches] on top of linux-omap:

<code>
git clone http://www.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap-2.6.git
cd linux-omap-2.6
wget http://4869037.web.fc2.com/tidspbridge-20081021.tgz
tar xvzf tidspbridge-20081021.tgz
git am *.patch
make omap3_beagle_defconfig
</code>

Then <code>make menuconfig</code> and add the following options in the menuconfig:
<pre>
CONFIG_FB_OMAP_CONSISTENT_DMA_SIZE=14 #in Device Drivers->Graphics support->Support for frame buffer devices->Consistent DMA memory size
CONFIG_MPU_BRIDGE=m #in Device Drivers->DSP Bridge driver
</pre>

== TI binaries ==

In order to get the DSP binaries for multimedia processing you need to download TI's OpenMAX IL [https://omapzoom.org/gf/download/frsrelease/111/396/tiopenmax-0.3.tar.gz package]. Once you have extracted the tarball you'll have to run the installer ''TI-OMX-Sample-Firmware-0.3-Linux-x86-Install'' and accept the license agreement.

You would end up with a bunch of binaries in <code>lib/dsp</code>, copy them to your root filesystem at the same location (/lib/dsp).

=== ping test ===

If you want to test the DSP you can try the simple ping test provided in this [https://omapzoom.org/gf/download/frsrelease/132/632/dspbridge_binaries.tar.bz2 package].

Just:
./ping.out

If you get an error like:
DSPNode_Allocate failed: 0x80008008

Then it's possible that the ping DSP socket node is not loaded. If you use 'baseimage.dof' you need to load it dynamically:

./dynreg.out -r pingdyn_3430.dll64P

On the other hand, 'ddspbase_tiomap3430.dof64P' has the node statically included, so there's no need to do that.

= Running =

On the board use this to load the module:

modprobe bridgedriver base_img=/lib/dsp/baseimage.dof

= Developing =

There are two ways to compile your own DSP nodes; the official one which requires XDC tools, and the simplified one (which I prefer).

== Official ==

Download the dsp-bridge examples from the [https://omapzoom.org/gf/download/frsrelease/147/848/dspbridge_LDP_v1.8.tar.gz omapzoom project]. Once you extract the main tarball you'll need to extract the individual tarballs on the same directory, so you have something like:

config.bld
documents
dsp
mpu_api
mpu_driver
product.mak
samplemakefile
samples

=== DSP side ===

You'll need the [https://www-a.ti.com/downloads/sds_support/targetcontent/LinuxDspTools/download.html C6x compiler], extract it in "/opt/dsp/cgt6x-6.0.16". The only version tested is 6.0.16.

You'll need the "DSP/BIOS" package and "RTSC/XDCtools" in order to compile the dsp-brige examples, you can download them from [https://www-a.ti.com/downloads/sds_support/targetcontent/index.html here]. Here we will assume they are installed in "/opt/dsp".

Edit "product.mak" to match the version of your tools. Then run:
make -f samplemakefile .bridge_samples DD_XDCDIR=/opt/dsp/xdctools_3_10_02 SABIOS_DIR=/opt/dsp/bios_5_33_04/packages DEPOT=/opt/dsp

=== ARM side ===

You'll need to prepare a '''target''' directory:
export target=/tmp/dsp-target
mkdir -p $target/lib

Also, build libbridge and libqos:
cd mpu_api/src
make PREFIX=$target/.. CROSS=arm-linux- install

To build the examples:
cd samples/mpu/src
make PREFIX=$target/.. CROSS=arm-linux- LIBINCLUDES=$target/lib LDPATH=$target/lib install

All you need will be on '/tmp/dsp-target'.

== Simplified ==

In order to develop dynamic dsp nodes you'll need a [https://www-a.ti.com/downloads/sds_support/targetcontent/LinuxDspTools/download.html C6x compiler] and doffbuild tools.

Apparently the only version that works is v6.0.16.

=== doffbuild tools ===

The only relevant tool is DLLcreate, which can be found in TI's omapzoom site, on the [http://omapzoom.org/gf/download/frsrelease/108/421/dspbridge_dsp.tar.gz dspbridge_dsp] package.

mkdir -p tmp
tar -xf dspbridge_dsp.tar.gz -C tmp
mv tmp/dsp/bdsptools/packages/ti/dspbridge/dsp/doffbuild /opt/doffbuild
rm -rf tmp

=== libdspbridge ===

This library is used by the user-space applications.

git clone git://github.com/felipec/libdspbridge.git
cd libdspbridge
make DESTDIR='''$rootfs''' install

=== Example dsp node ===

Here is an [http://github.com/felipec/dsp-dummy example dsp node] that is simply passing buffers back and forth.

git clone git://github.com/felipec/dsp-dummy.git
make DSP_TOOLS=/opt/dsptools DSP_DOFFBUILD=/opt/doffbuild BRIDGE_DIR=../libdspbridge

As a result you'll have two binaries; '''dummy.dll64P''' for dsp-side, and '''dummy''' for arm-side.

To load the dynamic node:
/dspbridge/dynreg.out -r /lib/dsp/dummy.dll64P

Now you can run the '''dummy''' test application.

= More information =

* [[BeagleBoard/gst-openmax]]

BeagleBoard/DSP Howto

2009-04-10T13:25:07Z

Felipec: /* Official */ Update ARM side instructions

[[Category: Linux]]
[[Category: OMAP]]
This article explains how to use the DSP in [http://focus.ti.com/general/docs/gencontent.tsp?contentId=36915&DCMP=OMAP_Feb27_2008&HQS=Other+PR+omap3503pr OMAP3] at [[BeagleBoard|BeagleBoard]] with TI's deliverables. For DSP tool chain see [[BeagleBoard#C64x.2B_DSP|C64x+ DSP]].

= Setup =

== Kernel driver ==

In order to use the DSP you would need TI's bridgedriver module on the kernel. For that you would need Hiroshi's [http://4869037.web.fc2.com/tidspbridge-20080922.tgz patches] on top of linux-omap:

<code>
git clone http://www.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap-2.6.git
cd linux-omap-2.6
wget http://4869037.web.fc2.com/tidspbridge-20081021.tgz
tar xvzf tidspbridge-20081021.tgz
git am *.patch
make omap3_beagle_defconfig
</code>

Then <code>make menuconfig</code> and add the following options in the menuconfig:
<pre>
CONFIG_FB_OMAP_CONSISTENT_DMA_SIZE=14 #in Device Drivers->Graphics support->Support for frame buffer devices->Consistent DMA memory size
CONFIG_MPU_BRIDGE=m #in Device Drivers->DSP Bridge driver
</pre>

== TI binaries ==

In order to get the DSP binaries for multimedia processing you need to download TI's OpenMAX IL [https://omapzoom.org/gf/download/frsrelease/111/396/tiopenmax-0.3.tar.gz package]. Once you have extracted the tarball you'll have to run the installer ''TI-OMX-Sample-Firmware-0.3-Linux-x86-Install'' and accept the license agreement.

You would end up with a bunch of binaries in <code>lib/dsp</code>, copy them to your root filesystem at the same location (/lib/dsp).

=== ping test ===

If you want to test the DSP you can try the simple ping test provided in this [https://omapzoom.org/gf/download/frsrelease/132/632/dspbridge_binaries.tar.bz2 package].

Just:
./ping.out

If you get an error like:
DSPNode_Allocate failed: 0x80008008

Then it's possible that the ping DSP socket node is not loaded. If you use 'baseimage.dof' you need to load it dynamically:

./dynreg.out -r pingdyn_3430.dll64P

On the other hand, 'ddspbase_tiomap3430.dof64P' has the node statically included, so there's no need to do that.

= Running =

On the board use this to load the module:

modprobe bridgedriver base_img=/lib/dsp/baseimage.dof

= Developing =

There are two ways to compile your own DSP nodes; the official one which requires XDC tools, and the simplified one (which I prefer).

== Official ==

Download the dsp-bridge examples from the [https://omapzoom.org/gf/download/frsrelease/147/848/dspbridge_LDP_v1.8.tar.gz omapzoom project]. Once you extract the main tarball you'll need to extract the individual tarballs on the same directory, so you have something like:

config.bld
documents
dsp
mpu_api
mpu_driver
product.mak
samplemakefile
samples

=== DSP side ===

You'll need the [https://www-a.ti.com/downloads/sds_support/targetcontent/LinuxDspTools/download.html C6x compiler], extract it in "/opt/dsp/cgt6x-6.0.16". The only version tested is 6.0.16.

You'll need the "DSP/BIOS" package and "RTSC/XDCtools" in order to compile the dsp-brige examples, you can download them from [https://www-a.ti.com/downloads/sds_support/targetcontent/index.html here]. Here we will assume they are installed in "/opt/dsp".

Edit "product.mak" to match the version of your tools. Then run:
make -f samplemakefile .bridge_samples DD_XDCDIR=/opt/dsp/xdctools_3_10_02 SABIOS_DIR=/opt/dsp/bios_5_33_04/packages DEPOT=/opt/dsp

=== ARM side ===

You'll need to prepare a '*target*' directory:
export target=/tmp/dsp-target
mkdir -p $target/lib

Also, build libbridge and libqos:
cd mpu_api/src
make PREFIX=$target/.. CROSS=arm-linux- install

To build the examples:
cd samples/mpu/src
make PREFIX=$target/.. CROSS=arm-linux- LIBINCLUDES=$target/lib LDPATH=$target/lib install

All you need will be on '/tmp/dsp-target'.

== Simplified ==

In order to develop dynamic dsp nodes you'll need a [https://www-a.ti.com/downloads/sds_support/targetcontent/LinuxDspTools/download.html C6x compiler] and doffbuild tools.

Apparently the only version that works is v6.0.16.

=== doffbuild tools ===

The only relevant tool is DLLcreate, which can be found in TI's omapzoom site, on the [http://omapzoom.org/gf/download/frsrelease/108/421/dspbridge_dsp.tar.gz dspbridge_dsp] package.

mkdir -p tmp
tar -xf dspbridge_dsp.tar.gz -C tmp
mv tmp/dsp/bdsptools/packages/ti/dspbridge/dsp/doffbuild /opt/doffbuild
rm -rf tmp

=== libdspbridge ===

This library is used by the user-space applications.

git clone git://github.com/felipec/libdspbridge.git
cd libdspbridge
make DESTDIR='''$rootfs''' install

=== Example dsp node ===

Here is an [http://github.com/felipec/dsp-dummy example dsp node] that is simply passing buffers back and forth.

git clone git://github.com/felipec/dsp-dummy.git
make DSP_TOOLS=/opt/dsptools DSP_DOFFBUILD=/opt/doffbuild BRIDGE_DIR=../libdspbridge

As a result you'll have two binaries; '''dummy.dll64P''' for dsp-side, and '''dummy''' for arm-side.

To load the dynamic node:
/dspbridge/dynreg.out -r /lib/dsp/dummy.dll64P

Now you can run the '''dummy''' test application.

= More information =

* [[BeagleBoard/gst-openmax]]

BeagleBoard/DSP Howto

2009-04-10T12:33:52Z

Felipec: /* Developing */ Add XDC info.

[[Category: Linux]]
[[Category: OMAP]]
This article explains how to use the DSP in [http://focus.ti.com/general/docs/gencontent.tsp?contentId=36915&DCMP=OMAP_Feb27_2008&HQS=Other+PR+omap3503pr OMAP3] at [[BeagleBoard|BeagleBoard]] with TI's deliverables. For DSP tool chain see [[BeagleBoard#C64x.2B_DSP|C64x+ DSP]].

= Setup =

== Kernel driver ==

In order to use the DSP you would need TI's bridgedriver module on the kernel. For that you would need Hiroshi's [http://4869037.web.fc2.com/tidspbridge-20080922.tgz patches] on top of linux-omap:

<code>
git clone http://www.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap-2.6.git
cd linux-omap-2.6
wget http://4869037.web.fc2.com/tidspbridge-20081021.tgz
tar xvzf tidspbridge-20081021.tgz
git am *.patch
make omap3_beagle_defconfig
</code>

Then <code>make menuconfig</code> and add the following options in the menuconfig:
<pre>
CONFIG_FB_OMAP_CONSISTENT_DMA_SIZE=14 #in Device Drivers->Graphics support->Support for frame buffer devices->Consistent DMA memory size
CONFIG_MPU_BRIDGE=m #in Device Drivers->DSP Bridge driver
</pre>

== TI binaries ==

In order to get the DSP binaries for multimedia processing you need to download TI's OpenMAX IL [https://omapzoom.org/gf/download/frsrelease/111/396/tiopenmax-0.3.tar.gz package]. Once you have extracted the tarball you'll have to run the installer ''TI-OMX-Sample-Firmware-0.3-Linux-x86-Install'' and accept the license agreement.

You would end up with a bunch of binaries in <code>lib/dsp</code>, copy them to your root filesystem at the same location (/lib/dsp).

=== ping test ===

If you want to test the DSP you can try the simple ping test provided in this [https://omapzoom.org/gf/download/frsrelease/132/632/dspbridge_binaries.tar.bz2 package].

Just:
./ping.out

If you get an error like:
DSPNode_Allocate failed: 0x80008008

Then it's possible that the ping DSP socket node is not loaded. If you use 'baseimage.dof' you need to load it dynamically:

./dynreg.out -r pingdyn_3430.dll64P

On the other hand, 'ddspbase_tiomap3430.dof64P' has the node statically included, so there's no need to do that.

= Running =

On the board use this to load the module:

modprobe bridgedriver base_img=/lib/dsp/baseimage.dof

= Developing =

There are two ways to compile your own DSP nodes; the official one which requires XDC tools, and the simplified one (which I prefer).

== Official ==

You'll need the [https://www-a.ti.com/downloads/sds_support/targetcontent/LinuxDspTools/download.html C6x compiler], extract it in "/opt/dsp/cgt6x-6.0.16". The only version tested is 6.0.16.

You'll need the "DSP/BIOS" package and "RTSC/XDCtools" in order to compile the dsp-brige examples, you can download them from [https://www-a.ti.com/downloads/sds_support/targetcontent/index.html here]. Here we will assume they are installed in "/opt/dsp".

Download the dsp-bridge examples from the [https://omapzoom.org/gf/download/frsrelease/147/848/dspbridge_LDP_v1.8.tar.gz omapzoom project]. Once you extract the main tarball you'll need to extract both 'dspbridge_dsp.tar.gz' and 'dspbridge_samples.tar.gz' on the same directory so you have something like:

config.bld
documents
dsp
product.mak
samplemakefile
samples

Edit "product.mak" to match the version of your tools. Then run:
make -f samplemakefile .bridge_samples DD_XDCDIR=/opt/dsp/xdctools_3_10_02 SABIOS_DIR=/opt/dsp/bios_5_33_04/packages DEPOT=/opt/dsp

== Simplified ==

In order to develop dynamic dsp nodes you'll need a [https://www-a.ti.com/downloads/sds_support/targetcontent/LinuxDspTools/download.html C6x compiler] and doffbuild tools.

Apparently the only version that works is v6.0.16.

=== doffbuild tools ===

The only relevant tool is DLLcreate, which can be found in TI's omapzoom site, on the [http://omapzoom.org/gf/download/frsrelease/108/421/dspbridge_dsp.tar.gz dspbridge_dsp] package.

mkdir -p tmp
tar -xf dspbridge_dsp.tar.gz -C tmp
mv tmp/dsp/bdsptools/packages/ti/dspbridge/dsp/doffbuild /opt/doffbuild
rm -rf tmp

=== libdspbridge ===

This library is used by the user-space applications.

git clone git://github.com/felipec/libdspbridge.git
cd libdspbridge
make DESTDIR='''$rootfs''' install

=== Example dsp node ===

Here is an [http://github.com/felipec/dsp-dummy example dsp node] that is simply passing buffers back and forth.

git clone git://github.com/felipec/dsp-dummy.git
make DSP_TOOLS=/opt/dsptools DSP_DOFFBUILD=/opt/doffbuild BRIDGE_DIR=../libdspbridge

As a result you'll have two binaries; '''dummy.dll64P''' for dsp-side, and '''dummy''' for arm-side.

To load the dynamic node:
/dspbridge/dynreg.out -r /lib/dsp/dummy.dll64P

Now you can run the '''dummy''' test application.

= More information =

* [[BeagleBoard/gst-openmax]]

BeagleBoard/DSP Howto

2009-01-13T15:23:33Z

Felipec: /* Developing */

BeagleBoard/DSP Howto

2008-12-08T14:37:28Z

Felipec: /* ping test */

BeagleBoard/video

2008-11-04T21:46:53Z

Felipec: Initial version.

This article describes information regarding video output on the beagleboard.

== omapfb ==

The current framebuffer diver has a generic interface (/dev/fb) but also a specific OMAP (2 and 3) interface for YUV overlays (/dev/fb1).

In order to use the YUV overlays (/dev/fb1) you need to specify some kernel parameters:

video=omapfb:vram:2M,vram:4M

For this particular case you'll need a corresponding consistent DMA size configuration:

CONFIG_FB_OMAP_CONSISTENT_DMA_SIZE=6

In order for the display controller to work you'll need a patch from Mans Rullgard which can be found [http://people.freedesktop.org/~felipec/beagle/0001-OMAP-Enable-overlay-optimisation.patch here]. (At least at the time of this writing it's still needed 2.6.27-omap1)

For examples of how to use the custom omapfb see:

* [http://github.com/felipec/gst-omapfb gst-omapfb]
* [http://git.mansr.com/?p=omapfbplay omapfbplay]

BeagleBoard/DSP Howto

2008-10-22T14:48:07Z

Felipec: /* Kernel driver */ Update Hiroshi's patches.

BeagleBoard/DSP Howto

2008-10-20T18:06:07Z

Felipec: /* More information */ Fix link.

BeagleBoard/DSP Howto

2008-10-20T18:05:17Z

Felipec: /* libdspbridge */ Up one level.

BeagleBoard/DSP Howto

2008-10-20T18:01:54Z

Felipec: /* Developing */ Add example dsp-node

BeagleBoard/DSP Howto

2008-10-20T17:36:34Z

Felipec: /* doffbuild tools */ Add intructions.

BeagleBoard/DSP Howto

2008-10-20T17:31:39Z

Felipec: Add developing information.

BeagleBoard/DSP Howto

2008-10-20T17:11:57Z

Felipec: Move gst-openmax information.

BeagleBoard/gst-openmax

2008-10-20T17:11:00Z

Felipec: Initial gst-openmax page.

[[Category: Linux]]
[[Category: OMAP]]

This article explains how to use TI's DSP with GStreamer. You need to have the DSP properly set up following [[BeagleBoard/DSP_Howto]].

= Setup =

== OpenMAX IL ==

The easiest way to use the DSP capabilities is through the [http://www.khronos.org/openmax/ OpenMAX IL] API, but in order to compile TI's implementation a special DSP library is required.

=== libdspbridge ===

git clone git://github.com/felipec/libdspbridge.git
cd libdspbridge
make DESTDIR='''rootfs''' install

=== libomxil-ti ===

git clone git://github.com/felipec/libomxil-ti.git
cd libomxil-ti
make BRIDGE_CFLAGS=-I../'''libdspbridge'''/inc BRIDGE_LIBS=-L../'''libdspbridge'''/lib DESTDIR='''rootfs''' install

== gst-openmax ==

You would need to compile gst-openmax inside scratchbox:

git clone git://github.com/felipec/gst-openmax.git
cd gst-openmax
./autogen.sh --noconfigure
./configure --prefix=/usr
make DESTDIR='''rootfs''' install

= Related stuff =

In order to get the omapfb usable for video playback you need this kernel argument:
video=omapfb:vram:2M,vram:4M

And the GStreamer element:
git clone git://github.com/felipec/gst-omapfb.git
cd gst-omapfb
make DESTDIR='''rootfs''' install

= Running =

You should be able to use the gst-openmax elements now:

gst-launch-0.10 filesrc location="foobar.avi" ! avidemux ! omx_mpeg4dec ! omapfbsink