Link DSPBIOS 6 Project with DSPLINK

Samuel,

DSPLink has not been verified with DSP/BIOS 6 API's. DSPLink has only been verified with the compatibility layer for DSP/BIOS 5 in DSP/BIOS 6.

Moving DSPLink to DSP/BIOS 6 is not limited to build update but will involve change in code as well. There is no plan to do this in any future DSPLink release.

Can you explain you app scenario to me? I want to understand if just using the compatibility layer will be sufficient for you.

Deepali

Deepali,

the project I'm working on is a radio base station. The DSP and an FPGA do the signal processing work, the ARM controls operation and provides interfaces to the user and the network. On the DSP there will be a framework running with a complex threading model and an event-based inter-object, inter-process and inter-processor communication scheme that's running on top of DSP/BIOS. We're still in the first quarter of the project, and maybe 5% of the DSP code has been written. TI suggests in SPRAAS7B (Migrating a DSP/BIOS 5 Application to DSP/BIOS 6), section 4.1, last sentence: "While most legacy modules are supported, we recommend that you use the new DSP/BIOS 6 modules if you are writing new code". So I decided it's better to change the existing code to be DSP/BIOS 6 native.

My experience has shown that it is quite cumbersome to mix the configuration for DSP/BIOS 6 modules with configuration for DSP/BIOS 5 modules. Version 6 is a completely different kernel, and I don't see the point in using it if you suggest to stick with the legacy layer. In that case, I'd rather go for version 5 (It's like having the CGT7 available but not being able to use it's new features (EABI) because of the lack of library support, but that's a different story).

Let me put your statement regarding DSPLink in other words:

• The difference between kernel versions 5 and 6 is bigger than the legacy layer implies
• The absence of a plan to provide a DSP/BIOS 6 native DSPLink version implies that the DSPLink product is maintained but not advanced. So should we build our own DSPLink replacement to be ready for what the future holds and to have the full flexibility to adopt whatever features we want?

Cheers,

Sam

Sam,

To answer one part of your question:

The absence of a plan to provide a DSP/BIOS 6 native DSPLink version implies that the DSPLink product is maintained but not advanced. So should we build our own DSPLink replacement to be ready for what the future holds and to have the full flexibility to adopt whatever features we want?

The next generation of DSPLink coming out at the end of this year supports 'true' BIOS 6. So I would suggest to wait for it to release. Which platform are you on?

Deepali

Deepali,

do you have more information about the next generation DSPLink? What's the release plan, will the full release be available at the end of the year and alpha/beta versions earlier this year? or are you speaking of a beta release at the end of this year?

The platform i'm working of is TMS320DM6443

Sam

Deepali,

Thanks for the info. We're currently switching back to BIOS5. We might or might not give BIOS6 a second try when the new DSPLink release is available, depending on how much  headroom is left in our project.

Sam

Hello Deepali,

Is the early release available yet? I am working with an OMAP3530.

Thank you in advance.

Rasha,

The early release is not available yet. Can you give further details on which company this project is for?

Deepali