This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

RTDX connection to a running DSP

Hello,

I am working with the DSK6713, RTDX 2.11, Code Composer Studio 3.3 and XDS560-PCI JTAG Interface.

I want use HS-RTDX to load many megabytes of data to the VC++ host application on the PC. This works fine with my test application for the DSP and PC. I don't use DSP/BIOS.

Now I want a stand-alone version to boot the dsp from flash memory and connect the RTDX host application later. The dsp application is booting correctly but the RTDX communication with the host don't work.
The host application opens the Code Composer Studio to configure and enable the RTDX channels. The dsp halts after starting CCS. The CCS doesn't reset or restart the DSP, so I have to manually continue running the DSP with the "run" button.

In the RTDX configuration control GUI in CCS I can see that the checkbox "Enable RTDX" is activated from the host but the Hardware Mode is "NONE" and not "RTDX or "HSRTDX". In this situation the host application opens a RTDX channel with an error 0x80004005 (status = rtdx->Open( "ichan", "W" )).
The Hardware Mode switches to activated RTDX-Mode only if I load the dsp application or symbols manually. Then the RTDX comunication works, if I continue running the DSP via CCS again.

 I use the RTDX library "rtdx_noInit.lib" for the C6713 DSP.
This information I found in following RTDX release notes from DSP/BIOS release 5.31.08. An example don't exist.

## RTDX Package 5,3,1 Release Notes
## New versions of the C6000 libraries have been added to address the
## issue of booting from ROM and getting RTDX to work with CCS.  These libraries
## no longer automatically call RTDX_Init() at boot time, otheriwse they are
## identical to standard versions of the libraries.
##
##     rtdx_noInit.lib
##     rtdxhs_noInit.lib
##     rtdxe_noInit.lib
##     rtdxhse_noInit.lib
##     rtdx64xx_noInit.lib
##     rtdx64xxe_noInit.lib
##
## Applications using these libraries now need to call RTDX_Init() once it has
## detected that CCS is connected.  This can be done via any mechanism, but
## one suggested way is to have the application check to see when the RTDX channel
## is enabled and then to call RTDX_Init() before doing any RTDX operations.
## The RTDX channel can be enabled via the RTDX Channel Viewer plugin or the user
## host RTDX application. CCS can be disconnected and reconnected as long as
## RTDX_Quit() is called before CCS is disconnected.  This can be done again by
## checking when the RTDX channel is disabled.
##
## Limitations:
##
## Once Code Composer Studio (CCS) has conected to a running program and RTDX has
## been running, if another disconnect and connect is performed without reloading
## the program, RTDX will not work.

 

** My DSP Application ************************************************

 // Wait for starting Code Composer and opening RTDX input channel
 // from host.
 // If the Hardware Mode is not RTDX, while loop will not leave
 do
 {
    DSK6713_LED_toggle(0);      // indicate program state
    DSK6713_waitusec(300000); // indicate program state

    status = RTDX_isInputEnabled( &ichan );
 }while (  status == 0 );

 DSK6713_LED_off(0);  // indicate program state


 // Call, if using noInit variant of rtdx-Lib
 RTDX_Init();

 // Enable the output channel, "ochan"
 RTDX_enableOutput(&ochan);

    ...write data to PC

*********************************************************************

 

My questions:
1. How can I avoid halting the running dsp while opening CCS?

2. Has anybody experience with RTDX communication to a running dsp?

3. Has anybody experience using the Library rtdx_noInit.lib?

4. The target DSP is the C6424. But the library rtdx64xplushs_noInit.lib is not included in the lib-folder.
   How can I get this lib?

5. Which mechanism switches the Hardware Mode to the RTDX-Mode while loading the dsp application or symbols with CCS?

 

Thanks for answers.