Hi! I have implemented interface for DSK board in MATLAB using which one can carry out data transfers from and to DSK. I have done this using MATLAB API plus MS VC++. Right now I am using my own compiled DLL (with minimum essential operations) to carry out these operations. I am able to bootload and load hex files, run and halt CPU, plus read from and write to memory and data type conversion in 8 bit mode. I am not able to figure out problem with nibble mode. I am able to develop interactive MatLab programs using this interface. I would like to build interface which has complete functionality, leaving out debugging. So can you please mail me DSK3DW? Is it possible to compile source using MSVC++? If anybody is interested in using this interface just mail me! Regards, Ninad Thakoor ----- Original Message ----- From: Keith E. Larson To: sundar_technical ; Sent: Thursday, April 18, 2002 1:41 AM Subject: Re: [c3x] Code Composer / C31 DSK interface Hello Vijay If you could please confirm that this yahoo account can receive three 1.5 Mbyte zips I can send you the new DSK tools that I am working on, which happens to include some Windows debug capability. I have sent this out to several other people and thanks to their help DSK3DW is beginning to look a bit nicer than it did a month ago. And, since I provide the source, a few of them have been bolting their applications directly in. It is not as easy as with a console/dos interface, but once you get the hang of it you can do some pretty interesting things. As for Code Composer, I have been trying to get the Software Development Systems (SDS) people here at TI to cough up the comm link level interface specs for CC, ala the one that Code Explorer (of old) used. They (SDS) is possibly coming around to this, but I would not hold my breath. The original CE interface was cobbled together from the C3x DSK interface I provided the developers at GoDSP before TI bought them. That is when CE got reshaped into Code Composer. The problem is that along the way non JTAG style debugging had been dropped. So for the time being everyone going to CC is stuck with buying into an expensive (and slow) JTAG debug path. This does not mean you cant have CC style features with the C31 DSK, but going down the CC path for the DSK right now is not possible. If you are interested, let me know. I would appreciate whatever feedback you have. Best regards, Keith Larson DSK3DW highlights of DSK3DW --------------------------- Source Tracking --------------- A newer DSK source level tracking has been added as well as COFF source tracking for C. Global and Local Symbol Watch plus Call Stack --------- Global and local symbols are now viewable by special memory window displays which automaticaly track the data type (IE display as fixed or float). Local symbols which are stored on the stack are displayed relative to the current stack pointer (the call frame) and are regressed back to main() so you can *see* what the calling paremeters were further down in the stack. Each frame is also assigned a new color making it easy to see where each function has assigned space on the stack. You can do some interesting things here. For example, you can see and modify variables deeper in the call stack (their symbol names are shown) modifying paramters that have been passed down into functions by pointer. Command and Watch Window ------------------------ Commands such as 'load myapp' and 'reset' are now combined with a smart command interpreter which scans the command line looking for watch and evaluate expressions. If one is found, the expression is re-evaluated. IOW, a seperate watch window is no longer needed. Interactive Graphing -------------------- By assigning some memory locations to graphing, DSK3DW now has the ability to query the application for what type of graph display is needed. The application therefor has the ability to set the graph data type, graph location and graph amplitude. Graphing breakpoints are then used to signal to the debugger when a graphical update is requested (or you can update the graph on all stops). The demo provided to show this feature is FFT_RR5.ASM which is a 1K point Real FFT. The input is simulated but could easily be converted to the ADC to make a full blow spectrum analyzer. Application Control Interface (Equalizer demo) ---------- A special button type is used which combines slider functionality when you click in the buttons sides with dialog functionality when you click in the middle. The Set value and its Min/Max limits are then controlled by labeled locations in memory. All you need to do is create these named locations in the DSK/COFF application and you can control parameters from the debugger while the application is running. The demo provided for this is a stereo 10 band graphic equalizer. Two banks of 10 controls each can be opened in the debugger to control the amplitude of each pass band. This demo also includes a TI patented data compressor that may also be of interest. DSK3DW Strategy --------------- Most of the information panels in a debugger are data dumps of internal memory that are displayed in various formats along with other information like symbols. For example, when a comm/debug kernel is used the registers are kept in memory starting at label _F0. If you display this region of memory with the address field suppressed, symbols and auto type values enabled you get the register display of DSK3D. If on the other hand you enable labels and set the type to disassemble you get the disassembler window. Add to this some other basic controls and file IO and you more or less have a debugger. DSK3WIN ------- This is an application seperate from DSK3DW which is simply a display interface for the Oscilloscope and FFT. It shows how to go the next level and start putting in things like help menues and dialog boxes for AIC control. The graphical display interface is also set up to work more like a piece of lab equipment rather than a degugger window. DSK3DLL.DLL ----------- This DLL contains 80% of the code needed to communicate with the DSK, assemble files, query the symbol tables, analyze math expressions... pretty much anything that could be considered as driver code for the console/dos based tools. OPEN SOURCE ----------- Being that I wrote it, I have control over making this an open source for TI DSP's. You can get in at almost any level here. Even source for the assembler (DSK version) is included. Best regards, Keith Larson ----------------- At 08:43 PM 4/16/02 -0000, you wrote: >Hi, > >I've been using the DOS based DSK tools to run my TMS320C31 board so >far. I need to do the same now with Code Composer, and I downloaded >the 30-day evaluation version from TI's website. > >Could someone tell me how to configure this version of Code Composer >for interfacing with the TMS320C31 DSK board. Specifically, should I >get a device driver from somewhere, or is the evaluation package >already configured to operate with the DSK board. I could only find >C3x and C33 simulator configurations in the CC setup window. > >thanks, >Vijay +-----------+ |Keith Larson | |Member Group Technical Staff | |Texas Instruments Incorporated | | | | 281-274-3288 | | | | www.micro.ti.com/~klarson | |-----------+ | TMS320C3x/C4x/VC33 Applications | | | | TMS320VC33 | | The lowest cost and lowest power 500 uw/mflop | | floating point DSP on the planet! | +-----------+ _____________________________________ Note: If you do a simple "reply" with your email client, only the author of this message will receive your answer. You need to do a "reply all" if you want your answer to be distributed to the entire group. _____________________________________ About this discussion group: To Join: Send an email to To Post: Send an email to To Leave: Send an email to Archives: http://groups.yahoo.com/group/c3x More Groups: http://www.dsprelated.com

Hello Vijay The schemtic can be found in appendix B and a brief description of how the interlock mechanism works is in chapter 4. Figure 4-1 is especialy useful. Still, if all you need is a boot channel, you can simplify even more. Here is one idea. The serial boot loader can be used using a few bit IO lines on the PC (printer port data pins are easy to use) to simulate a serial boot source. If you check the DSK3APPS directory you will find the application 'SERBOOT.CPP'. You will see that it is quite small and simple. The connection is simply a few data pins of the printer port with some isolation resistors to prevent IO driving IO faults. BTW: There is no reason that the serial boot path could not be upgraded into a serial transmit and receive path. And, if the drivers were written for both the send and receive side, you would be able to use all of the DSK tools! The code is on the way directly to your email rather than the Yahoo group. Best regards, Keith hello Keith, Thanks a lot for your feedback, I'll go with Code explorer then. My account is ready to get ~4.5MB, so please go ahead and send me the DSK3DW software, I'll try it out as well. I am assuming that you were responsible for the design of the TMS320C31 DSK board, and I wanted to know whether you have a list of components that I should get if I want to make a simple version of your board for just the DSP chip - PC interface, so that I can download code into the chip and run the debugger using your existing DSK tools. I do not require the rest of the stuff on the DSK board like the Analog interface, I am currently using the DSK board in place of the actual C31 processor for testing out my own motion control board. thanks again, regards, Vijay +-----------+ |Keith Larson | |Member Group Technical Staff | |Texas Instruments Incorporated | | | | 281-274-3288 | | | | www.micro.ti.com/~klarson | |-----------+ | TMS320C3x/C4x/VC33 Applications | | | | TMS320VC33 | | The lowest cost and lowest power 500 uw/mflop | | floating point DSP on the planet! | +-----------+

Hello Vijay, Once I faced the same problem.You SHOULD get the drivers for C31 DSK.If you cant do that then your only option is Code Explorer Debugger from Go-DSP. You can get it from http://briefcase.yahoo.com/husnainalam Best Regards. Husnain.

Hello Vijay If you could please confirm that this yahoo account can receive three 1.5 Mbyte zips I can send you the new DSK tools that I am working on, which happens to include some Windows debug capability. I have sent this out to several other people and thanks to their help DSK3DW is beginning to look a bit nicer than it did a month ago. And, since I provide the source, a few of them have been bolting their applications directly in. It is not as easy as with a console/dos interface, but once you get the hang of it you can do some pretty interesting things. As for Code Composer, I have been trying to get the Software Development Systems (SDS) people here at TI to cough up the comm link level interface specs for CC, ala the one that Code Explorer (of old) used. They (SDS) is possibly coming around to this, but I would not hold my breath. The original CE interface was cobbled together from the C3x DSK interface I provided the developers at GoDSP before TI bought them. That is when CE got reshaped into Code Composer. The problem is that along the way non JTAG style debugging had been dropped. So for the time being everyone going to CC is stuck with buying into an expensive (and slow) JTAG debug path. This does not mean you cant have CC style features with the C31 DSK, but going down the CC path for the DSK right now is not possible. If you are interested, let me know. I would appreciate whatever feedback you have. Best regards, Keith Larson DSK3DW highlights of DSK3DW --------------------------- Source Tracking --------------- A newer DSK source level tracking has been added as well as COFF source tracking for C. Global and Local Symbol Watch plus Call Stack --------- Global and local symbols are now viewable by special memory window displays which automaticaly track the data type (IE display as fixed or float). Local symbols which are stored on the stack are displayed relative to the current stack pointer (the call frame) and are regressed back to main() so you can *see* what the calling paremeters were further down in the stack. Each frame is also assigned a new color making it easy to see where each function has assigned space on the stack. You can do some interesting things here. For example, you can see and modify variables deeper in the call stack (their symbol names are shown) modifying paramters that have been passed down into functions by pointer. Command and Watch Window ------------------------ Commands such as 'load myapp' and 'reset' are now combined with a smart command interpreter which scans the command line looking for watch and evaluate expressions. If one is found, the expression is re-evaluated. IOW, a seperate watch window is no longer needed. Interactive Graphing -------------------- By assigning some memory locations to graphing, DSK3DW now has the ability to query the application for what type of graph display is needed. The application therefor has the ability to set the graph data type, graph location and graph amplitude. Graphing breakpoints are then used to signal to the debugger when a graphical update is requested (or you can update the graph on all stops). The demo provided to show this feature is FFT_RR5.ASM which is a 1K point Real FFT. The input is simulated but could easily be converted to the ADC to make a full blow spectrum analyzer. Application Control Interface (Equalizer demo) ---------- A special button type is used which combines slider functionality when you click in the buttons sides with dialog functionality when you click in the middle. The Set value and its Min/Max limits are then controlled by labeled locations in memory. All you need to do is create these named locations in the DSK/COFF application and you can control parameters from the debugger while the application is running. The demo provided for this is a stereo 10 band graphic equalizer. Two banks of 10 controls each can be opened in the debugger to control the amplitude of each pass band. This demo also includes a TI patented data compressor that may also be of interest. DSK3DW Strategy --------------- Most of the information panels in a debugger are data dumps of internal memory that are displayed in various formats along with other information like symbols. For example, when a comm/debug kernel is used the registers are kept in memory starting at label _F0. If you display this region of memory with the address field suppressed, symbols and auto type values enabled you get the register display of DSK3D. If on the other hand you enable labels and set the type to disassemble you get the disassembler window. Add to this some other basic controls and file IO and you more or less have a debugger. DSK3WIN ------- This is an application seperate from DSK3DW which is simply a display interface for the Oscilloscope and FFT. It shows how to go the next level and start putting in things like help menues and dialog boxes for AIC control. The graphical display interface is also set up to work more like a piece of lab equipment rather than a degugger window. DSK3DLL.DLL ----------- This DLL contains 80% of the code needed to communicate with the DSK, assemble files, query the symbol tables, analyze math expressions... pretty much anything that could be considered as driver code for the console/dos based tools. OPEN SOURCE ----------- Being that I wrote it, I have control over making this an open source for TI DSP's. You can get in at almost any level here. Even source for the assembler (DSK version) is included. Best regards, Keith Larson ----------------- At 08:43 PM 4/16/02 -0000, you wrote: >Hi, > >I've been using the DOS based DSK tools to run my TMS320C31 board so >far. I need to do the same now with Code Composer, and I downloaded >the 30-day evaluation version from TI's website. > >Could someone tell me how to configure this version of Code Composer >for interfacing with the TMS320C31 DSK board. Specifically, should I >get a device driver from somewhere, or is the evaluation package >already configured to operate with the DSK board. I could only find >C3x and C33 simulator configurations in the CC setup window. > >thanks, >Vijay +-----------+ |Keith Larson | |Member Group Technical Staff | |Texas Instruments Incorporated | | | | 281-274-3288 | | | | www.micro.ti.com/~klarson | |-----------+ | TMS320C3x/C4x/VC33 Applications | | | | TMS320VC33 | | The lowest cost and lowest power 500 uw/mflop | | floating point DSP on the planet! | +-----------+