why RTDX support is so limited?

You can find good RTDX documentation at:

http://tiexpressdsp.com/index.php?title=Real_Time_Data_eXchange_%28RTDX%29

http://focus.ti.com/general/docs/techdocsabstract.tsp?abstractName=sprufc7

You can do file Input/Output using code composer studio, but it does not support RTDX. See CCS help and chapter 5.1 of:

I moved your thread to the CCS forum to get into the view of some more CCS specific folks who may be able to comment on RTDX and its future.

Is there any other similar tool for host target communication or is RTDX still the best option even though its not supported?

Could you provide some specifics on what sort of communication you need to handle? From what I recall RTDX was primarily to allow an external application to communicate to a target device through CCS, for example having an excel file or VB program that would read data from the target and display graphs or controls, is this the sort of capability that you are seeking or do you just need to save data off of a target board?

This must have sliped my mind, does CCS 4.x NOT support RTDX at all??????

I am using RTDX for transfering data to and from the DSP during setup and adjustments. Just like the RTDX example used to show...

How do we now transfer files and data to and from the DSP?

Terje

Bernie,

For several years, I've been using RTDX in conjunction with simulation tools such as SystemVue and Mathworks Link to Code Composer Studio (v2.x and v3.x).  It's an ideal development interface because it allows (1) generation of very accurately simulated input signals, (2) interactive debugging within CCS and (3) display of output results using the rich graphing/plotting capabilities of the simulation tools.

I also recently learned that it had been dropped in CCS 4.0.  Why?  Is there an alternative that allows interaction with CCS?

Bob Davenport said:

I also recently learned that it had been dropped in CCS 4.0.  Why?

One of the engineers from the CCS team can probably give a better answer, I was never that involved with RTDX and I hardly used it.

My impression is that RTDX was simply not popular enough to achieve a permanent support status, I knew of relatively few developers who used it and the ones who did tended to have trouble getting started and odd problems once it was going (though working in a apps support role I tend to only see the problems and not the benefits).

Bob Davenport said:

Is there an alternative that allows interaction with CCS?

I don't know of any direct replacement of the entire RTDX functionality, some portions of it can be done in other ways depending on exactly what you want to do. As far as SystemVue and Mathworks Link I could not say, you may want to ask those software vendors if they have any plans to work on a similar mechanism with the contemporary CCS versions.

The fact that we can write DSP code that opens and reads a file on the host's hard drive made it possible to write a simple software that was loaded on the DSP with JTAG that when run reprogrammed the FLASH using exisiting codebase. We could even request the file name from the DSP.

This made the loading of the FLASH for enginerring easy and simple. The tools now does ether not support the Hardware, the POD used or the DSP...

Terje Nilsen said:

The fact that we can write DSP code that opens and reads a file on the host's hard drive made it possible to write a simple software that was loaded on the DSP with JTAG that when run reprogrammed the FLASH using exisiting codebase. We could even request the file name from the DSP.

Terje,

You can still do this using standard file I/O.  For example, go to this wiki page:

http://processors.wiki.ti.com/index.php/SPI_Boot_on_5502_EVM#Writing_the_Image

The program included there runs in CCS 4.x and will program the flash on the 5502 EVM.  It does fread commands from the PC and then writes the flash using the McBSP in SPI mode.

Is that the sort of thing you're talking about?  If so, that doesn't require RTDX and you can definitely do it in CCS 4.x and 5.x.

Brad