Starting digital signal processing with TMS320C6713 DSP Starter Kit

Thanks Randy .

Regards,

Nikola

We (the whole E2E community) appreciate you posting this great information. I wish we had a Like button.

If you are still interested in trying to get CCSv5 to connect to your DSK6713's USB JTAG emulation port, we should probably move this discussion to the Code Composer Forum. But then I would probably lose you because I do not check there very often.

If you have not yet, you will want to look at my favorite Wiki page for emulation setup, GSG:Common target configurations. Search for DSK6713 to see how they say to create a Target Configuration for your board.

I do not have Win7 64-bit, still on XP, but if we advertise it as supporting the DSK6713 on Win7/64, I have faith that it will work.

An alternative to the XDS510-style of emulator is the XDS100-style of emulator. The XDS100's can be found for under $100, and the license for CCSv5 is free when used with an XDS100, just like with the simulator or with an on-board DSK/EVM emulator.

Thanks again for the great post. If you decide to pursue the CCSv5 on WIn7/64 on the Code Composer Forum, please mention it on this thread so I will know.

Regards,
RandyP

Dear Douglas/Randy, 

Many thanks for your extensive feedbacks. I really do appreciate your time and effort. My aim is to develop my own board with Altium designer. However, C6713 can be implemented as a soft core in any of FPGAs supported by Altium. So my general aim is to practice signal processing and develop some basic  data acquisition, signal conditioning circuitry around some sensor and A/D . In near future, I would like to use TI processors in test benches for system identification. I really don't know now what should be best for me. I possess thorough experience in ordinary analog signal processing but I'm completely new in digital signal processing so I need a platform which has got both good support in literature and which is easy to master.

I'm running Oracles Virtual box inside ubuntu, and Windows XP service pack 2 is hosted inside the box. Whether I should follow Randy's advice or yours, depends only on support provided for both processors. For now,  I think that I will choose C6713, as I found many books related to that processor.

If you have any other advice, please let me know.

Best regards,

Nikola

An update:  I finally got my home DSK6713 working properly via its USB JTAG on-board emulation under CCS version 5.2.  I also installed the DSK6713 Board Support Library and C6000 Chip Support Library, and built the missing rts6700.lib using Cygwin.  To build rts6700.lib, find the source archive in the ccsv5\tools\compiler\6000*\lib directory, create an empty directory somewhere to work in, unpack the files from rtssrc.zip into your working directory, and replace the Makefile with this one:

For some reason, part of my previous post got truncated.  I'll try to reconstruct what I said:

Also make an empty subdirectory named "OBJ" in your working directory.  Edit the new Makefile (after renaming it back from Makefile.txt, which name I had to use to get it to upload here) to assign CGT_BIN the correct path.  Note that I reduced the degree of optimization used for sin.c and tanh.c, to work around a compiler bug (reported elsewhere).  Start a Cygwin terminal window in your working directory, and type the command "make library".  Ignore the two warnings about an unused variable "f".  This should produce OBJ\rts6700.lib, which you can move wherever is convenient (I put mine into the CCS "lib" directory).  In a CCS project session, change the Properties:General:Runtime_support_library to the new rts6700.lib using the "Browse..." button.  Good luck!

For some unknown reason, I still had trouble uploading the Makefile.txt.  I'll try once more, but if this doesn't work, feel free to contact me at DAGwyn "at" aol.com and I'll email it to you.  This time I named it "foo.txt".  Of course you need to copy it onto the Makefile from the source archive, or invoke "make -f foo.txt library".

##############################################################################
#
#
# Makefile for C6000 run-time support library version 7.3.5
#
#
##############################################################################

# Hand-edited by D A Gwyn to make just rts6700.lib via Cygwin without using "mklib".

# make -j 8 library
CGT_BIN = /cygdrive/d/ti/ccsv5/tools/compiler/c6000_7.3.5/bin
# SHELL = d:/cygwin/bin/sh.exe
EXTRA_FLAGS =
INC = "."
LIB = rts6700.lib

##############################################################################
#
# You can append options to the standard list by using EXTRA_FLAGS.  This is
# useful for enabling debugging support or activating silicon errata
# workarounds:
#
# gmake LIB=some.lib EXTRA_FLAGS="-g"
#
# You can completely replace the standard list by using STANDARD_FLAGS, but
# this should almost never be necessary.  WARNING: This Makefile will not
# optimize the files if you replace the standard list and your replacement
# options do not include the right optimization flags.
#
# gmake LIB=some.lib STANDARD_FLAGS="-o3 -oe"
#
##############################################################################

# gmake library LIB=rts6700.lib C6700=1 C6000=1 NOT_VENC_ASM=1 sets up the following:

#-----------------------------------------------------------------------------
# Basic definitions
#-----------------------------------------------------------------------------
CC = $(CGT_BIN)/cl6x
AR = $(CGT_BIN)/ar6x
CD = cd
OBJ = OBJ

STANDARD_FLAGS =  -o -oe -k -ps -pdsw225 -q
SPECIAL_FLAGS =  -O1	# workaround for sin.c, tanh.c
UNIVERSAL_FLAGS = -mo --mem_model:data=far --no_visible_enums \
	-c --ti_lib --building_runtime -D_BOOL \
	-mv6700
CPP_FLAGS = -fg --rtti

TARGET_C_SOURCE = \
	autoinit.c \
	boot.c \
	dtos.c \
	gsmfuncs.c \
	gsmvars.c \
	imath40.c \
	imath64.c \
	llshift.c \
	lltoa.c \
	memcpy62.c \
	mpyll.c \
	outprof.c \
	pprof_cio.c \
	pprof_user.c \
	trgmsg.c \
	memset.c \
	copy_zero_init.c \
	copy_decompress_none.c \
	copy_decompress_rle.c \
	copy_decompress_lzss.c \
	imaxabs.c \
	imaxdiv.c \
	strtoimax.c \
	strtoumax.c

DINKUM_MATH_SUBSET_SHARED_WITH_COMPLEX_C_SOURCE = \
	xsin.c \
	xfsin.c \
	xlsin.c \
	xsinh.c \
	xfsinh.c \
	xlsinh.c \
	xcosh.c \
	xfcosh.c \
	xlcosh.c \
	xexp.c \
	xfexp.c \
	xlexp.c \
	xdtest.c \
	xfdtest.c \
	xldtest.c \
	xdscale.c \
	xfdscale.c \
	xldscale.c \
	xdnorm.c \
	xfdnorm.c \
	xldnorm.c \
	xvalues.c \
	xfvalues.c \
	xlvalues.c \
	xferaise.c

C6000_ASM_SOURCE = \
	divi.asm \
	divu.asm \
	memcpy64.asm \
	remi.asm \
	remu.asm \
	strasg.asm

NOT_VENC_ASM_ASM_SOURCE = \
	push.asm \
	call_stub.asm \
	setjmp.asm

ASM_SOURCE = $(C6000_ASM_SOURCE) \
	$(NOT_VENC_ASM_ASM_SOURCE)

GENERIC_EDG_CPP_SOURCE = \
	array_del.cpp \
	array_new.cpp \
	array_nodel.cpp \
	array_nonew.cpp \
	array_pdel.cpp \
	array_pnew.cpp \
	delete.cpp \
	delnothrow.cpp \
	dtor_list.cpp \
	error.cpp \
	guard.cpp \
	memzero.cpp \
	new_.cpp \
	newhandler.cpp \
	newnothrow.cpp \
	placedel.cpp \
	placenew.cpp \
	pure_virt.cpp \
	rtti.cpp \
	set_new.cpp \
	typeinfo_.cpp \
	vars.cpp \
	vec_cctor.cpp \
	vec_newdel.cpp

GENERIC_TI_C_SOURCE = \
	cpy_tbl.c \
	ecvt.c \
	exit.c \
	fcvt.c \
	memory.c \
	_bufread.c \
	_io_perm.c \
	_lock.c \
	_printfi.c \
	_printfi_min.c \
	_printfi_nf.c \
	_scanfi.c \
	_tvaltostr.c \
	abs.c \
	args_main.c \
	asctime.c \
	assert.c \
	atexit.c \
	atof.c \
	atoi.c \
	atol.c \
	atoll.c \
	bsearch.c \
	clearerr.c \
	clock.c \
	ctime_.c \
	ctype.c \
	defs.c \
	difftime.c \
	errno.c \
	fclose.c \
	feof.c \
	ferror.c \
	fflush.c \
	fgetc.c \
	fgetpos.c \
	fgets.c \
	fopen.c \
	fprintf.c \
	fputc.c \
	fputs.c \
	fread.c \
	fscanf.c \
	fseek.c \
	fsetpos.c \
	ftell.c \
	fwrite.c \
	gmtime.c \
	isalnum.c \
	isalpha.c \
	isascii.c \
	iscntrl.c \
	isdigit.c \
	isgraph.c \
	islower.c \
	isprint.c \
	ispunct.c \
	isspace.c \
	isupper.c \
	isxdigit.c \
	localtim.c \
	lowlev.c \
	ltoa.c \
	memccpy.c \
	memchr.c \
	memcmp.c \
	memmov.c \
	mktime.c \
	multibyte.c \
	perror.c \
	printf.c \
	qsort.c \
	rand.c \
	remove.c \
	rewind.c \
	setbuf.c \
	setlocale.c \
	setvbuf.c \
	sinit.c \
	snprintf.c \
	sprintf.c \
	sscanf.c \
	strcat.c \
	strchr.c \
	strcmp.c \
	strcoll.c \
	strcpy.c \
	strcspn.c \
	strerror.c \
	strftime.c \
	strlen.c \
	strncat.c \
	strncmp.c \
	strncpy.c \
	strpbrk.c \
	strrchr.c \
	strspn.c \
	strstr.c \
	strtod.c \
	strtok.c \
	strtol.c \
	strtold.c \
	strtoll.c \
	strtoul.c \
	strtoull.c \
	strxfrm.c \
	time.c \
	tmpfile.c \
	tmpnam.c \
	tmzone.c \
	toascii.c \
	tolower.c \
	toupper.c \
	trgdrv.c \
	ungetc.c \
	vfprintf.c \
	vprintf.c \
	vsnprintf.c \
	vsprintf.c \
	wctype.c

GENERIC_DINKUM_C_SOURCE = \
	signal.c \
	raise.c \
	fwide.c \
	stox.c

GENERIC_DINKUM_CPP_SOURCE = \
	fiopen.cpp \
	iomanip.cpp \
	ios.cpp \
	iostream.cpp \
	limits.cpp \
	locale.cpp \
	locale0.cpp \
	nothrow.cpp \
	raisehan.cpp \
	string.cpp \
	strstrea.cpp \
	throw.cpp \
	wiostrea.cpp \
	wlocale.cpp \
	xfpostox.cpp \
	xlocale.cpp \
	xlocinfo.cpp

CPP_SOURCE = $(GENERIC_EDG_CPP_SOURCE) \
	$(GENERIC_DINKUM_CPP_SOURCE)

GENERIC_DINKUM_CX0_SOURCE = \
	xatexit.cx0

CX0_SOURCE = $(GENERIC_DINKUM_CX0_SOURCE)

GENERIC_DINKUM_CX_SOURCE = \
	wchar.cx

CX_SOURCE = $(GENERIC_DINKUM_CX_SOURCE)

GENERIC_MATH_C_SOURCE = \
	absd.c \
	absf.c \
	acos.c \
	acosf.c \
	acosh.c \
	acoshf.c \
	acot.c \
	acot2.c \
	acot2f.c \
	acotf.c \
	acoth.c \
	acothf.c \
	addd.c \
	addf.c \
	asin.c \
	asinf.c \
	asinh.c \
	asinhf.c \
	atan.c \
	atan2.c \
	atan2f.c \
	atanf.c \
	atanh.c \
	atanhf.c \
	ceil.c \
	ceilf.c \
	cmpd.c \
	cmpf.c \
	cos.c \
	cosf.c \
	cosh.c \
	coshf.c \
	cot.c \
	cotf.c \
	coth.c \
	cothf.c \
	cvtdf.c \
	cvtfd.c \
	div.c \
	divd.c \
	divf.c \
	exp.c \
	exp10.c \
	exp10f.c \
	exp2.c \
	exp2f.c \
	expf.c \
	fabs.c \
	fabsf.c \
	fixdb.c \
	fixdc.c \
	fixdi.c \
	fixdli.c \
	fixdlli.c \
	fixdsi.c \
	fixdu.c \
	fixdul.c \
	fixdull.c \
	fixdus.c \
	fixfb.c \
	fixfc.c \
	fixfi.c \
	fixfli.c \
	fixflli.c \
	fixfsi.c \
	fixfu.c \
	fixful.c \
	fixfull.c \
	fixfus.c \
	floor.c \
	floorf.c \
	fltbd.c \
	fltbf.c \
	fltcd.c \
	fltcf.c \
	fltid.c \
	fltif.c \
	fltlid.c \
	fltlif.c \
	fltllid.c \
	fltllif.c \
	fltsid.c \
	fltsif.c \
	fltud.c \
	fltuf.c \
	fltuld.c \
	fltulf.c \
	fltulld.c \
	fltullf.c \
	fltusd.c \
	fltusf.c \
	fmod.c \
	fmodf.c \
	fpclassify.c \
	fpclassifyf.c \
	frcaddd.c \
	frcaddf.c \
	frcdivd.c \
	frcdivf.c \
	frcmpyd.c \
	frcmpyd_div.c \
	frcmpyf.c \
	frcmpyf_div.c \
	frexp.c \
	frexpf.c \
	isfinite.c \
	isfinitef.c \
	isinf.c \
	isinff.c \
	isnan.c \
	isnanf.c \
	isnormal.c \
	isnormalf.c \
	ldexp.c \
	ldexpf.c \
	ldiv.c \
	lldiv.c \
	log.c \
	log10.c \
	log10f.c \
	log2.c \
	log2f.c \
	logf.c \
	modf.c \
	modff.c \
	modfl.c \
	mpyd.c \
	mpyf.c \
	negd.c \
	negf.c \
	pow.c \
	powf.c \
	powi.c \
	powif.c \
	renormd.c \
	renormf.c \
	round.c \
	roundf.c \
	rsqrt.c \
	rsqrtf.c \
	sinf.c \
	sinh.c \
	sinhf.c \
	sqrt.c \
	sqrtf.c \
	subd.c \
	subf.c \
	tan.c \
	tanf.c \
	tanhf.c \
	trunc.c \
	truncf.c

C_SOURCE = $(TARGET_C_SOURCE) \
	$(DINKUM_MATH_SUBSET_SHARED_WITH_COMPLEX_C_SOURCE) \
	$(GENERIC_TI_C_SOURCE) \
	$(GENERIC_DINKUM_C_SOURCE) \
	$(GENERIC_MATH_C_SOURCE)

SPECIAL_SOURCE = \
	sin.c \
	tanh.c

LINASM_SOURCE = \
	negll.sa

CPP_C_SOURCE =

OBJS:		$(CPP_C_SOURCE) $(CPP_SOURCE) \
		$(LINASM_SOURCE) $(CX_SOURCE) $(C_SOURCE) $(ASM_SOURCE) $(CX0_SOURCE) \
		$(SPECIAL_SOURCE)
	for i in $(SPECIAL_SOURCE); \
	do	$(CC) $$i $(STANDARD_FLAGS) $(EXTRA_FLAGS) $(UNIVERSAL_FLAGS) $(C_FLAGS) \
		$(SPECIAL_FLAGS) -I$(INC) -fr $(OBJ) -fs $(OBJ) -ft $(OBJ); \
	done
	for i in $(CPP_C_SOURCE) $(CPP_SOURCE); \
	do	$(CC) $$i $(STANDARD_FLAGS) $(EXTRA_FLAGS) $(UNIVERSAL_FLAGS) $(CPP_FLAGS) \
		-I$(INC) -fr $(OBJ) -fs $(OBJ) -ft $(OBJ); \
	done
	for i in $(LINASM_SOURCE) $(CX_SOURCE) $(C_SOURCE) $(ASM_SOURCE) $(CX0_SOURCE); \
	do	$(CC) $$i $(STANDARD_FLAGS) $(EXTRA_FLAGS) $(UNIVERSAL_FLAGS) $(C_FLAGS) \
		-I$(INC) -fr $(OBJ) -fs $(OBJ) -ft $(OBJ); \
	done

library:	OBJS
	$(CD) $(OBJ); $(AR) -qa $(LIB) *.obj

info:
	@echo $(UNIVERSAL_FLAGS)
	@echo $(STANDARD_FLAGS)
	@echo $(EXTRA_FLAGS)
	@echo $(C_FLAGS)
	@echo $(CPP_FLAGS)
	@echo
	@echo $(C_OBJS)
	@echo $(CPP_OBJS)

That time it seemed to work.

The other thing I originally said that got truncated was that the CCS maintainers really should include all the RTS libraries with the new version of CCS, like they did in older versions, not just for the latest C6000 models.  Thanks, and sorry for my post getting split up like that.

I should have mentioned that when I got the DSK6713 working via its USB on-board JTAG emulation, it was under CCSv5.2 on native Windows 7 (64-bit), not in a virtual machine.  I forget exactly what the snag was, but if somebody is having the same problem, let me know and I'll try to help.

It's nice to have a signal generator and oscilloscope, but you can get along without them.  CCS has some graphical display features, so if you produce an FFT (for example) in an array on the DSP, you can view it as a graph.  The DSK6713 has an external audio codec chip, accessed via the DSP serial ports (McBSP as I recall), and one of the example applications provided with the board reproduces audio signals (e.g., from an MP3 player, through the DSP app, out to headphones).  You can add your own filtering and simply listen to the effect.  Have fun!

Also, you will be able to download data to the DSP app via the host PC.  It's somewhat slow due to going through the JTAG emulation, but since you can generate data files with software on the PC, you can use that approach instead of a hardware signal source.

Douglas,

please check your e-mail, when you catch enough time please send me the instructions of necessary steps for running under cygwin.

Regards,

Nikola

Douglas, I have been trying to work on DSK6713, using CCSv5.0, I think the last line on this post got truncated and there is nothing to look at "and replace the Makefile with this one:" Can you please reiterate the last line of this post and repost it please.  Greatly appreciated, since I could not find anything related to CCSv5 and DSK6713.  Thank you.

Yes, the post with the Makefile got truncated, but I tried twice more and the second retry seems to have succeeded, with "foo.txt" being the Makefile with a different name to get past the file-posting filter.

I unraveled the Gnu-ish stuff in my copy of the Makefile because I wanted to see exactly what was happening, and I only need to support the C6713 at present.  In the process I patched around the problem compiling sin.c and tanh.c .

I think what TI intended was to start up Cygwin by clicking on "sh.exe" in \ti\ccsv5\utils\cygwin to open a terminal window where you can type Unix-like commands.  Then enter "cd ../../tools/compiler/c6000/lib" then "./mklib.exe --pattern=rts6700.lib", which is supposed to unpack the source archive and run "gmake.exe" (which is in \ti\ccsv5\utils\bin) to build the specified library.  mklib needs to find "unzip.exe" and "gmake.exe" in  your command directory search PATH, and gmake needs "sh.exe".  You can add the necessary directories (.../cygwin and .../bin) to your PATH by "PATH={whatever}:$PATH export PATH".  I'm not sure how you would specify the added paths since Cygwin uses /cygdrive/c instead of C: and they haven't set that up for you.  (For the latest compiler release this is thwarted anyway since the source archive is rtssrc.zip.bz2 not rtssrc.zip.)  I found it easier to use my existing Cygwin environment, which has PATH already set up, and used WinZip to unpack the source archive.

It's probably best if you visit the Cygwin Web site (find it via Google search) for instructions on setting up your own Cygwin environment, which is essentially the same as a standard Unix environment, similar to Linux except oriented more toward the shell command-line interpreter user interface.  (Basically, run their "setup.exe" program, select a download site, and add whatever programs you need to the basic set that they have pre-selected.  You will need gmake and unzip; I don't remember whether they are pre-selected.)  Make sure the directory containing the CCSv5 code generation tools (/ti/ccsv5/tools/compiler/c6000/bin) is in your command directory search PATH.

See also my other recent post about using TI's intended "mklib" library building tool.

Thank you Mr. Douglas Gwyn, I just compiled debugged, connected board to the PC (eclipse) and got everything running.  Now I got to start working with the eclipse for linux.  

Tell us how you worked with DSK6713 under Windows 7 x64, using CCSv5? I'm using Windows 7 x64 and CCSv5.3.

Mihail,

Please try a search of this C67x Single Core DSP Forum for "dsk6713 ccsv5" (no quotes) and look for "threads only". You will find a few threads that have discussed this, and in one of them a star of the forum posted his experiences that led to success, Darrell Thomas. Douglas may have also posted such results, so you may find several helpful threads.

If you have particular questions, you will get the best help by posting a new thread for your specific issues.

Regards,
RandyP

Sir, I have got the same problem, Please mentioned the step ,How can I do it?

And The driver came with this board is only for CCS v3.1 ,How I can get the driver for CCS v5.2?

What kind of problem are you facing right now Biswajit, please explain the platform and the board.

Hi Douglas, I got some problem in connecting the C6713 DSK board to CCSv5 on windows 7. I followed this link to download the c6713DSKDiag.exe, but the emulator connect wasnt successful. it said USB connection failed, and the RD201 LED on the board just keeps flashing. Could you please tell me how did you make it work on yours?

Cheers,

Dennis

I've been successfully using the DSK6713 via CCSv5 on Windows 7 64-bit edition.

After you install CCSv5, for Project/Properties/General/Main/Variant select "DSK6713" and for Project/Properties/General/Main/Connection select "Spectrum Digital DSK-EVM-eZdsp onboard USB Emulator".  Make sure  Project/Properties/General/Main/Advanced settings/Device endianness is set to "little endian" and Project/Properties/General/Main/Advanced settings/Output format is set to "Legacy COFF".  Project/Properties/General/Main/Advanced settings/Runtime support library should be "rts6700.lib" but at one time there was a problem when it attempted to build that library; you can probably work around that by using "rts6200.lib" instead, as a temporary expedient until you manage to build a working "rts6700.lib".

Having properly configured all that, CCSv5 ought to work fine with the DSK6713 JTAG emulation via USB.  The CCSv5 distribution includes all the needed drivers.

The Spectrum Digital CCSv3 software kit includes a Board Support Library and (if I recall correctly) a Chip Support Library that install into folders outside the CCSv5 hierarchy.  I seem to recall that they work okay, but I rolled my own anyway.  You can also find various support libraries (including the CSL, I think) somewhere in the TI Wiki.

Follow this steps; they also work for CCSv5.

http://spinlab.wpi.edu/courses/ece4703_2012/installccsv4.html

Please note that with Windows7 and later, and with CCSv5 and later, we now recommend installing into a folder outside of \Program Files or \Program Files(x86). There are OS issues with Windows7 that have led us to this.

The CCSv5 default folder is probably C:\TI. Personally, I install into a subfolder below that such as C:\TI\CCSv5.3 so I can keep different version available. This may not be of use to you.

Regards,
RandyP

Sorry to resurrect an old thread...

Nikola Radakovic said:

My aim is to develop my own board with Altium designer. However, C6713 can be implemented as a soft core in any of FPGAs supported by Altium.

Nikola,

Can you elaborate on these comments above?  I'm unaware of any effort by TI to release the c6713 has a soft IP that can be implemented inside an FPGA.  Is that what you are saying?  It seemed like your resistance to moving to a newer device like c6748 was tied to that feature.  I was hoping you could elaborate a bit more as I was having trouble finding anything online.

Thanks,
Brad

Dear Brad,

Maybe I was wrong in my conclusion but I think I found out some Altium Library which implements C6713. 

However, I can't remember whether it's C6713/C6748 or some other DSP.  

Please see Libraries of summer version 2009 , http://wiki.altium.com/display/ADOH/Altium+Designer+Summer+09+library+list#AltiumDesignerSummer09librarylist-TexasInstruments

TI Digital Signal Processor 16-Bit.IntLib
TI Digital Signal Processor 32-Bit.IntLib

Best regards,

Nikola

Thanks for the quick reply.  I also see things in there like analog comparators, charge pumps, etc.  My guess would be that these libraries contain things like schematic symbols, footprints, etc. for ICs sold by Texas Instruments (and other vendors).

Yes they do comprise XSpice, footprints for PCB layout and 3D models which can be imported into ANSYS or other FEA tools for thermal and EMC analysis. 

But all in all, it is beyond my knowledge. 

Regards,

Nikola