David,
It would be good to understand the issues you are facing better - if
possible, since building with CE 2.0.1 should make life a lot easier
than it seems to have done for you. Sorry you've not had a good
experience so far.
Couple of comments (which you may already know, but thought worth
mentioning) :-
- you should only see the rtdx issue if you have migrated to bios
5.32.01 - If you stick with 5.31.08 you shouldn't see this issue.
Setting the env var as Sam responded should remove the check though if
you need (or want) to use the latest bios version.
- changing the memory map when using CE 2.0.1 shouldn't require any
rebuilding or modifying of dsplink - this can now be specified at
run-time and passed to codec-engine to do this for you when you build
your application.
- there is a new build option in 2.0.1 which tells codec engine based
application to get the configuration of codecs and memory map from the
dsp server. This means you should be able to specify in a single place
in the memory map in the .tcf of the server, then have it inherited by
the application config code. An example usage of this api for an
application config script is shown below.
/*
* ======== Engine Configuration ========
*/
var Engine = xdc.useModule('ti.sdo.ce.Engine');
var demoEngine = Engine.createFromServer(
"myserver",
"./server.x64P",
"mycompany.mygroup.myservers.server"
);
~roger
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On
Behalf Of Ring, Chris
Sent: 14 March 2008 20:00
To: [EMAIL PROTECTED];
[email protected]
Subject: RE: Codec Engine 2.0.1 woes
Please post your server build error.
Chris
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]
> ] On Behalf Of [EMAIL PROTECTED]
> Sent: Friday, March 14, 2008 12:46 PM
> To: [email protected]
> Subject: Codec Engine 2.0.1 woes
>
> Greetings,
>
> I saw some time ago that some people were getting a version
> conflict with
> ti.rtdx package while building the CE 2.0 and Chris Ring said that it
> should be fixed in the patch release 2.0.1...
>
> Well, after jumping through the numerous hoops to change our
> memory map
> from 256M to 128M (which works fine) in dsplink and codec
> engine, building
> the server gives the "incompatible use of package" error.
>
> Since I just want to see if it will build and run at all,
> where the heck do
> I stick that environment setting that makes those errors turn into
> warnings?
>
> Also, any news on CE 2.1?
> I'd really like to use the newest dsplink and bios with our server.
>
> I must rant a little though:
>
> [rant]
>
> TI packages win the award for most obfuscated build systems,
> hands down.
> Also, CE and friends are so finely tuned to use the evmDM6446 in their
> configurations that even though we're running a custom board we had to
> modify all the DM6446-related files/entities to match our
> DM6441 design
> with less memory because of the huge amount of file changes
> that it would
> take to get the build systems to even recognize a custom platform.
>
> I'd rather not spend the day looking for 'ti.platforms.evmDM6446' and
> adding if statement conditionals so the builds don't crap out with
> "unsupported platform"
> Considering the fact that developments are likely to not be
> stuffing evm
> boards inside their products, I'd think that the
> customization would be a
> higher priority rather than make it work on the dvevm.
>
> Please note that these comments do not negate all the work
> that was put
> into making all this work in the first place... as far as the dvevm is
> concerned.
>
> However, they do come from a dev team whose so far faced: audio driver
> lock-up issues, bad to no SD card support, poor osd framebuffer
> performance, and now CE issues... not quite the boost in
> development that
> we'd hoped for. Our bosses are getting tired of listening to our
> explanations of why we're stuck on so and so or things just
> need tweaking
> or it's still a new platform.
>
> [/rant]
>
> -- David
>
> DAVID A. KONDRAD
> Software Design Engineer
> On-Q/Legrand
> www.onqlegrand.com
>
> _______________________________________________
> Davinci-linux-open-source mailing list
> [email protected]
> http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
>
_______________________________________________
Davinci-linux-open-source mailing list
[email protected]
http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
_______________________________________________
Davinci-linux-open-source mailing list
[email protected]
http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
