Community: Message List - Symphony Studio Questions

Re: RE: Symphony Studio Questions

support@line6.com — Wed, 27 Apr 2011 04:06:08 GMT

audioartillery wrote:

I suspect if you switch to building outside of Symphony Studio you'll have more control (e.g., a makefile). I haven't found this necessary, I just tweak my debug setting manually. IDE's annoy me anyways so I treat it mainly as a fancy window that runs the compiler for me .

Oh, it's not giving me any trouble, per se, just a minor hassle. I've used Eclipse for a lot of programming in the past, so it's a bit frustrating to see IDE elements I'm accustomed to using present, yet not hooked up to do anything useful. As I mentioned, I was just hoping I was missing something and that somebody else had found an option or tweak that would enable those features, but it looks like I'll just have to live without.

Re: RE: Symphony Studio Questions

support@line6.com — Tue, 26 Apr 2011 04:40:41 GMT

I suspect if you switch to building outside of Symphony Studio you'll have more control (e.g., a makefile). I haven't found this necessary, I just tweak my debug setting manually. IDE's annoy me anyways so I treat it mainly as a fancy window that runs the compiler for me .

Re: RE: Symphony Studio Questions

support@line6.com — Thu, 21 Apr 2011 03:51:31 GMT

Line6Perry wrote:

Sorry for the late reply. The TCDDK product is a really unique one; none of us in Product Support are DSP engineers, so our ability to provide technical/in-depth coding-related answers is very limited.

I checked with some of our internal software team members and the answer they provided me was that this question is really for Freescale since Symphony Studio is their software tool (Symphony Studio isn't a "requirement" to build TCDDK projects); it was provided as a possible dev environment to use for users getting started, but you can use other toolchains of course.

Sorry if this isn't the answer you were hoping for: I'd say check with Freescale Symphony Studio forums for help with the behavior of their compiler and features/behavior with 3rd party plug-ins.

http://forums.freescale.com/t5/Freescale-Product-Forums/ct-p/PRODCOMM

Before asking my question here, I checked on the Freescale forums, and found the same questions (among others) there. Those posts are either ignored, or a Freescale employee points out that they have stopped official support of Symphony Studio. In general, it appears they're moving away from dedicated DSP chips to ARM based chips with SIMD extensions if needed for DSP.

I know it's not your product, so I wasn't expecting an official solution or anything, no worries there. I was just hoping someone who's worked with it here may have had some insight, and it doesn't hurt to ask, right?

Either way, thanks for taking the time to look into it for me.

Re: RE: Symphony Studio Questions

support@line6.com — Tue, 19 Apr 2011 18:30:59 GMT

Sorry for the late reply. The TCDDK product is a really unique one; none of us in Product Support are DSP engineers, so our ability to provide technical/in-depth coding-related answers is very limited.

I checked with some of our internal software team members and the answer they provided me was that this question is really for Freescale since Symphony Studio is their software tool (Symphony Studio isn't a "requirement" to build TCDDK projects); it was provided as a possible dev environment to use for users getting started, but you can use other toolchains of course.

Sorry if this isn't the answer you were hoping for: I'd say check with Freescale Symphony Studio forums for help with the behavior of their compiler and features/behavior with 3rd party plug-ins.

http://forums.freescale.com/t5/Freescale-Product-Forums/ct-p/PRODCOMM

Symphony Studio Questions

support@line6.com — Thu, 14 Apr 2011 02:00:32 GMT

Is anyone aware of a way to detect the active build configuration in Symphony Studio, for use in conditional compilation? Typically this could be done with macros, and the Symphony Studio documentation mentions a ${ConfigName} macro, but I can't seem to access it using assembly. Another typical way of achieving this is with -D defines in the build configuration, but that doesn't seem to work either.

Of course you can create a debug symbol to be used in conditional compiling like this:

DEBUG_LEVEL          equ          1

Without macros to identify the build, the value of separate build and release configurations is reduced a lot.

When building projects, is there any way to get the errors and warnings from the console to show up in the problems tab? Most Eclipse based toolchains support this, and it sure is a handy feature. I can't find any way to enable this with Symphony Studio though.

Lastly, has anyone managed to install any 3rd party plug-ins with Symphony Studio? This is one of the huge benefits of Eclipse, but for some reason the feature appears disabled.

Thanks!