C64X DSPLIB

Hello Everyone,

I am using the C6416 DSK. I am performing an FFT using TI's C64plus DSP
LIB.

I tried out fft_example.pjt. I made no changes to the code.

But when I run the code on CCS V3.3 ( TMS320C64X Device Cycle Accurate
SImulator ), the compilation is fine but when I load the .out file I get the
following error message

*" Data verification failed at address 0x10800000
PleaSE VERIFY target memory and map

file load failed because of data verification error* "

How can this be dealt with ?

How do you run the C6416DSK with CCS V3.3 ?? This is because the DSK runs
on CCS V3.1 ( V3.1 is shipped along with the DSK ) but when I load the
DSK6416 target on CCS V3.3 it doesnt run. Is it a disadvantage to use CCS
V3.1 ??

Thanks,

Regards,
--
Varun Start a New Thread

Please verify your linker.cmd file, the simulator is basically saying that it is unable to load to the address 0x10800000. Please check the device memory map.

Regards
JS

________________________________
From: c... [mailto:c...] On Behalf Of varoonian .
Sent: Monday, June 21, 2010 2:31 PM
To: c...
Subject: [c6x] C64X DSPLIB

Hello Everyone,

I am using the C6416 DSK. I am performing an FFT using TI's C64plus DSP LIB.

I tried out fft_example.pjt. I made no changes to the code.

But when I run the code on CCS V3.3 ( TMS320C64X Device Cycle Accurate SImulator ), the compilation is fine but when I load the .out file I get the following error message

" Data verification failed at address 0x10800000
PleaSE VERIFY target memory and map

file load failed because of data verification error "

How can this be dealt with ?

How do you run the C6416DSK with CCS V3.3 ?? This is because the DSK runs on CCS V3.1 ( V3.1 is shipped along with the DSK ) but when I load the DSK6416 target on CCS V3.3 it doesnt run. Is it a disadvantage to use CCS V3.1 ??

Thanks,

Regards,
--
Varun

_____________________________________ Start a New Thread

Hello Sir,

It worked. Thanks for the quick reply. I did change the linker command file
to C6416.cmd ( that was previously present in the TI example folder ). May I
know why the original linker command file given in fft_example project
didn't work ?

I have one more question. Does TI have updated target files so that the
C6416 DSK be used with CCS V3.3 ? or is CCS V3.1 good enough ?

Can you recommend any documents (other than EMIF Data sheet) to program the
EMIF in CCS. Even some examples code would be of great help. I am
interfacing the EMIF to Virtex-5 FPGA.

Thanks,

Regards,

Varun Subramanian

On Mon, Jun 21, 2010 at 12:45 PM, Sankaran, Jagadeesh wrote:

> Please verify your linker.cmd file, the simulator is basically saying
> that it is unable to load to the address 0x10800000. Please check the device
> memory map.
>
> Regards
>
> JS
> ------------------------------
>
> *From:* c... [mailto:c...] *On Behalf Of *varoonian
> .
> *Sent:* Monday, June 21, 2010 2:31 PM
> *To:* c...
> *Subject:* [c6x] C64X DSPLIB
>
> Hello Everyone,
>
> I am using the C6416 DSK. I am performing an FFT using TI's C64plus DSP
> LIB.
>
> I tried out fft_example.pjt. I made no changes to the code.
>
> But when I run the code on CCS V3.3 ( TMS320C64X Device Cycle Accurate
> SImulator ), the compilation is fine but when I load the .out file I get the
> following error message
>
> *" Data verification failed at address 0x10800000
> PleaSE VERIFY target memory and map
>
> file load failed because of data verification error* "
>
> How can this be dealt with ?
>
> How do you run the C6416DSK with CCS V3.3 ?? This is because the DSK runs
> on CCS V3.1 ( V3.1 is shipped along with the DSK ) but when I load the
> DSK6416 target on CCS V3.3 it doesnt run. Is it a disadvantage to use CCS
> V3.1 ??
>
> Thanks,
>
> Regards,
> --
> Varun
>

--
Varun

_____________________________________ Start a New Thread

varoonian,

I see a couple of possibilites regarding your problem.

First, has the appropriate .dll file (the drivers) been installed in the 3.3
version. If not, then the wrong object code will be produced.

In a similar area, the 'setup' of CCS 3.3 includes a selection of the target
hardware.
Have you performed the setup and selected the TMS320c6416?
(installing the proper drivers, available from TI (or spectrum digital) will
make the proper DSP selection available.)

Does your .prj file contain the proper DSP selection?

Does your .cmd file properly allocate the various memory segments to match the
c6416 DSP?

The CCS 3.1 was probably setup by the supplier for the correct DSP.
You need to setup the CCS 3.3 for your specific DSP.

R. Williams

---------- Original Message -----------
From: "varoonian ."
To: c...
Sent: Mon, 21 Jun 2010 12:31:15 -0700
Subject: [c6x] C64X DSPLIB

> Hello Everyone,
>
> I am using the C6416 DSK. I am performing an FFT using TI's C64plus DSP
> LIB.
>
> I tried out fft_example.pjt. I made no changes to the code.
>
> But when I run the code on CCS V3.3 ( TMS320C64X Device Cycle Accurate
> SImulator ), the compilation is fine but when I load the .out file I
> get the following error message
>
> *" Data verification failed at address 0x10800000
> PleaSE VERIFY target memory and map
>
> file load failed because of data verification error* "
>
> How can this be dealt with ?
>
> How do you run the C6416DSK with CCS V3.3 ?? This is because the DSK
> runs on CCS V3.1 ( V3.1 is shipped along with the DSK ) but when I
> load the DSK6416 target on CCS V3.3 it doesnt run. Is it a
> disadvantage to use CCS V3.1 ??
>
> Thanks,
>
> Regards,
>
> --
> Varun
------- End of Original Message -------

_____________________________________ Start a New Thread

Hello Varun,


You may be getting messed up due to the number of c6000 'sub-architectures'.

1. "I am using the C6416 DSK. I am performing an FFT using TI's C64plus
DSPLIB"
The c6416 is a c64xx [sometimes called c64 or c64x] architecture. The
c64plus DSPLIB is designed for c64+ architectures and I am surmising that it
was trying to build to a c64+ memory map. Jagadeesh can probably verify if
it is intended to be used with c64xx devices.

2. I believe that if you install the DSK sw after you install CCS 3.3 it can
work. I did that some time ago and do not remember if it was a simple
reinstall or if I have to create some configuration files manually.

my apologies for 'top posting',
mikedunn
On Mon, Jun 21, 2010 at 4:06 PM, Richard Williams wrote:

> varoonian,
>
> I see a couple of possibilites regarding your problem.
>
> First, has the appropriate .dll file (the drivers) been installed in the
> 3.3
> version. If not, then the wrong object code will be produced.
>
> In a similar area, the 'setup' of CCS 3.3 includes a selection of the
> target
> hardware.
> Have you performed the setup and selected the TMS320c6416?
> (installing the proper drivers, available from TI (or spectrum digital)
> will
> make the proper DSP selection available.)
>
> Does your .prj file contain the proper DSP selection?
>
> Does your .cmd file properly allocate the various memory segments to match
> the
> c6416 DSP?
>
> The CCS 3.1 was probably setup by the supplier for the correct DSP.
> You need to setup the CCS 3.3 for your specific DSP.
>
> R. Williams
> ---------- Original Message -----------
> From: "varoonian ." >
> To: c...
> Sent: Mon, 21 Jun 2010 12:31:15 -0700
> Subject: [c6x] C64X DSPLIB
>
> > Hello Everyone,
> >
> > I am using the C6416 DSK. I am performing an FFT using TI's C64plus DSP
> > LIB.
> >
> > I tried out fft_example.pjt. I made no changes to the code.
> >
> > But when I run the code on CCS V3.3 ( TMS320C64X Device Cycle Accurate
> > SImulator ), the compilation is fine but when I load the .out file I
> > get the following error message
> >
> > *" Data verification failed at address 0x10800000
> > PleaSE VERIFY target memory and map
> >
> > file load failed because of data verification error* "
> >
> > How can this be dealt with ?
> >
> > How do you run the C6416DSK with CCS V3.3 ?? This is because the DSK
> > runs on CCS V3.1 ( V3.1 is shipped along with the DSK ) but when I
> > load the DSK6416 target on CCS V3.3 it doesnt run. Is it a
> > disadvantage to use CCS V3.1 ??
> >
> > Thanks,
> >
> > Regards,
> >
> > --
> > Varun
> ------- End of Original Message -------
>
>
>

--
www.dsprelated.com/blogs-1/nf/Mike_Dunn.php Start a New Thread

varoonian,

My replies are interspersed and prefixed with

R. Williams

---------- Original Message -----------
From: "varoonian ."
To: Richard Williams
Cc: c...
Sent: Tue, 22 Jun 2010 16:36:59 -0700
Subject: Re: [c6x] C64X DSPLIB

> Dear Mr.WIlliams,
>
> First of all, thanks for the reply.
>
> I just removed CCS 3.1 and re installed CCS V3.3 Platinum and then installed
> the target files for the DSK 6416. I tried to import the target file DSK6416
> ( of type cc_setup Document ) from the "Setup CCS".

did you run the 'setup' application and select your specific
emulator/target board?
With out 'setup' being run and the correct selection made, CCS 3.3 will use the
default values.
The default values are probably not what you want.

>
> Connection Type: *SDDSKUSB Emulator.*
>
> CCS V3.3 starts and then displays , " Error initializing Emulator I/O
> Port : 540". When I ran the diagnostic utility the test PASSED. Does
> this mean I have to change the port address ?

Are you connecting to the target via a USP port?
The CCS 3.1, that I have, uses a parallel port.
Are you connecting to your target via a USP or via a parallel port?
Everything has to match for successful communication with your target, including
the target has to be powered ON.
The 'setup' application should be a clickable ICON on your desktop, placed there
when you installed the CCS 3.3 software.
If your connection to the target is via a USB port, then it maybe that the
emulator is plugged into a different USB port from what the original 'setup'
specified.
>
> How do I check that the .cmd files allocates memory that matches the
> C6416 ?
First, you need to know the architecture of the T.I. DSP that your target
(DSP 6316) is using. This information can be found in several places, for
instance the system architecture documentation.
Second, you need to know what you are looking at when you examine the contents
of the .cmd file for your project.

The 'memory' entries in the .cmd file, describe:
--'origin' address and 'length' in addresses and (page 0 or page 1)
for each memory area in the DSP address map.
(page 0 and page 1 are the differentiation between executable code and data.)

The memory description (as noted above) tells the linker what areas of the
address map contain memory.

The 'sections' entries in the .cmd file, describe:
--which of the above 'memory' sections is to receive each 'section' of the .out
file information.
the .out file sections are things like:
.data
.text
.stack
.....(there are several other standard sections and you can create your own
using the source code) I.E. In 'C' using the pragma(s) DataSection and
CodeSection
The .cmd file can do a lot of other things. All the .cmd file features are
described (somewhere) in the help files (you did install the help files?)
There are some .cmd files in the /examples sub directory of the CCS 3.3
installation.
There are some .cmd files available on-line at TI.com
Most likely, any .cmd file that you acquire for your target DSP will still need
some small changes for your specific project.

If you are using a CCS 3.3 generated .cmd file and it does not match the memory
map of the DSP you are using, then the CCS is not setup for the correct DSP.

The .cmd file from the compile/link using CCS 3.1 *may* work under CCS 3.3.

Hope this helps.

R. Williams

>
> Regards,
>
> Varun
>
> On Mon, Jun 21, 2010 at 2:06 PM, Richard Williams
wrote:
>
> > varoonian,
> >
> > I see a couple of possibilites regarding your problem.
> >
> > First, has the appropriate .dll file (the drivers) been installed in the
> > 3.3
> > version. If not, then the wrong object code will be produced.
> >
> > In a similar area, the 'setup' of CCS 3.3 includes a selection of the
> > target
> > hardware.
> > Have you performed the setup and selected the TMS320c6416?
> > (installing the proper drivers, available from TI (or spectrum digital)
> > will
> > make the proper DSP selection available.)
> >
> > Does your .prj file contain the proper DSP selection?
> >
> > Does your .cmd file properly allocate the various memory segments to match
> > the
> > c6416 DSP?
> >
> > The CCS 3.1 was probably setup by the supplier for the correct DSP.
> > You need to setup the CCS 3.3 for your specific DSP.
> >
> > R. Williams
> >
> >
> >
> >
> > ---------- Original Message -----------
> > From: "varoonian ."
> > To: c...
> > Sent: Mon, 21 Jun 2010 12:31:15 -0700
> > Subject: [c6x] C64X DSPLIB
> >
> > > Hello Everyone,
> > >
> > > I am using the C6416 DSK. I am performing an FFT using TI's C64plus DSP
> > > LIB.
> > >
> > > I tried out fft_example.pjt. I made no changes to the code.
> > >
> > > But when I run the code on CCS V3.3 ( TMS320C64X Device Cycle Accurate
> > > SImulator ), the compilation is fine but when I load the .out file I
> > > get the following error message
> > >
> > > *" Data verification failed at address 0x10800000
> > > PleaSE VERIFY target memory and map
> > >
> > > file load failed because of data verification error* "
> > >
> > > How can this be dealt with ?
> > >
> > > How do you run the C6416DSK with CCS V3.3 ?? This is because the DSK
> > > runs on CCS V3.1 ( V3.1 is shipped along with the DSK ) but when I
> > > load the DSK6416 target on CCS V3.3 it doesnt run. Is it a
> > > disadvantage to use CCS V3.1 ??
> > >
> > > Thanks,
> > >
> > > Regards,
> > >
> > > --
> > > Varun
> > ------- End of Original Message -------
> >
> > --
> Varun
------- End of Original Message -------

_____________________________________ Start a New Thread

Dear Mr.WIlliams,

First of all, thanks for the reply.

I just removed CCS 3.1 and re installed CCS V3.3 Platinum and then installed
the target files for the DSK 6416. I tried to import the target file DSK6416
( of type cc_setup Document ) from the "Setup CCS".

Connection Type: *SDDSKUSB Emulator.*

CCS V3.3 starts and then displays , " Error initializing Emulator I/O Port :
540". When I ran the diagnostic utility the test PASSED. Does this mean I
have to change the port address ?

How do I check that the .cmd files allocates memory that matches the C6416 ?

Regards,

Varun

On Mon, Jun 21, 2010 at 2:06 PM, Richard Williams wrote:

> varoonian,
>
> I see a couple of possibilites regarding your problem.
>
> First, has the appropriate .dll file (the drivers) been installed in the
> 3.3
> version. If not, then the wrong object code will be produced.
>
> In a similar area, the 'setup' of CCS 3.3 includes a selection of the
> target
> hardware.
> Have you performed the setup and selected the TMS320c6416?
> (installing the proper drivers, available from TI (or spectrum digital)
> will
> make the proper DSP selection available.)
>
> Does your .prj file contain the proper DSP selection?
>
> Does your .cmd file properly allocate the various memory segments to match
> the
> c6416 DSP?
>
> The CCS 3.1 was probably setup by the supplier for the correct DSP.
> You need to setup the CCS 3.3 for your specific DSP.
>
> R. Williams
> ---------- Original Message -----------
> From: "varoonian ."
> To: c...
> Sent: Mon, 21 Jun 2010 12:31:15 -0700
> Subject: [c6x] C64X DSPLIB
>
> > Hello Everyone,
> >
> > I am using the C6416 DSK. I am performing an FFT using TI's C64plus DSP
> > LIB.
> >
> > I tried out fft_example.pjt. I made no changes to the code.
> >
> > But when I run the code on CCS V3.3 ( TMS320C64X Device Cycle Accurate
> > SImulator ), the compilation is fine but when I load the .out file I
> > get the following error message
> >
> > *" Data verification failed at address 0x10800000
> > PleaSE VERIFY target memory and map
> >
> > file load failed because of data verification error* "
> >
> > How can this be dealt with ?
> >
> > How do you run the C6416DSK with CCS V3.3 ?? This is because the DSK
> > runs on CCS V3.1 ( V3.1 is shipped along with the DSK ) but when I
> > load the DSK6416 target on CCS V3.3 it doesnt run. Is it a
> > disadvantage to use CCS V3.1 ??
> >
> > Thanks,
> >
> > Regards,
> >
> > --
> > Varun
> ------- End of Original Message -------
--
Varun Start a New Thread

Hello Mr.Dunn,

Thank you for replying.

In CCS V3.1 with the DSK as target ,when I chose "Rebuild All" for
dsplib64lus.pjt, I got an error saying "ERROR: cannot run cmp6x - file
could not be found".

The same project when I rebuilt it on CCS V3.3 on the C64X simulator it
compiled.Regarding loading DSK 6416 target in CCS V3.3 the error was that it
couldn't initialize the USB port.

Thanks,

Regards,

Varun

On Mon, Jun 21, 2010 at 2:45 PM, Michael Dunn wrote:

> Hello Varun,
>
>
> You may be getting messed up due to the number of c6000
> 'sub-architectures'.
>
> 1. "I am using the C6416 DSK. I am performing an FFT using TI's C64plus
> DSPLIB"
> The c6416 is a c64xx [sometimes called c64 or c64x] architecture. The
> c64plus DSPLIB is designed for c64+ architectures and I am surmising that it
> was trying to build to a c64+ memory map. Jagadeesh can probably verify if
> it is intended to be used with c64xx devices.
>
> 2. I believe that if you install the DSK sw after you install CCS 3.3 it
> can work. I did that some time ago and do not remember if it was a simple
> reinstall or if I have to create some configuration files manually.
>
> my apologies for 'top posting',
> mikedunn
> On Mon, Jun 21, 2010 at 4:06 PM, Richard Williams wrote:
>
>> varoonian,
>>
>> I see a couple of possibilites regarding your problem.
>>
>> First, has the appropriate .dll file (the drivers) been installed in the
>> 3.3
>> version. If not, then the wrong object code will be produced.
>>
>> In a similar area, the 'setup' of CCS 3.3 includes a selection of the
>> target
>> hardware.
>> Have you performed the setup and selected the TMS320c6416?
>> (installing the proper drivers, available from TI (or spectrum digital)
>> will
>> make the proper DSP selection available.)
>>
>> Does your .prj file contain the proper DSP selection?
>>
>> Does your .cmd file properly allocate the various memory segments to match
>> the
>> c6416 DSP?
>>
>> The CCS 3.1 was probably setup by the supplier for the correct DSP.
>> You need to setup the CCS 3.3 for your specific DSP.
>>
>> R. Williams
>> ---------- Original Message -----------
>> From: "varoonian ." >
>> To: c...
>> Sent: Mon, 21 Jun 2010 12:31:15 -0700
>> Subject: [c6x] C64X DSPLIB
>>
>> > Hello Everyone,
>> >
>> > I am using the C6416 DSK. I am performing an FFT using TI's C64plus DSP
>> > LIB.
>> >
>> > I tried out fft_example.pjt. I made no changes to the code.
>> >
>> > But when I run the code on CCS V3.3 ( TMS320C64X Device Cycle Accurate
>> > SImulator ), the compilation is fine but when I load the .out file I
>> > get the following error message
>> >
>> > *" Data verification failed at address 0x10800000
>> > PleaSE VERIFY target memory and map
>> >
>> > file load failed because of data verification error* "
>> >
>> > How can this be dealt with ?
>> >
>> > How do you run the C6416DSK with CCS V3.3 ?? This is because the DSK
>> > runs on CCS V3.1 ( V3.1 is shipped along with the DSK ) but when I
>> > load the DSK6416 target on CCS V3.3 it doesnt run. Is it a
>> > disadvantage to use CCS V3.1 ??
>> >
>> > Thanks,
>> >
>> > Regards,
>> >
>> > --
>> > Varun
>> ------- End of Original Message -------
>>
>>
>> --
> www.dsprelated.com/blogs-1/nf/Mike_Dunn.php
>

--
Varun Start a New Thread

Dear Mr.WIlliams,

My replies are prefixed with .

did you run the 'setup' application and select your specific
emulator/target board?
With out 'setup' being run and the correct selection made, CCS 3.3 will use
the
default values.
The default values are probably not what you want.

*<**V> : First I installed CCS V3.3 , then the DSK target files in
C:\CCStudioV3.3.*
*Then I clicked on Setup Code Composer Studio icon on the desktop and
imported the target file "dsk6416" from the import folder and also included
the "Diagnostics Utility". But all the target files in the import folder are
of type CC5x./4x (.ccs) including the dsk6416 target file. Does this play a
role in this ?*

Are you connecting to the target via a USP port?
The CCS 3.1, that I have, uses a parallel port.
Are you connecting to your target via a USP or via a parallel port?
Everything has to match for successful communication with your target,
including
the target has to be powered ON.
The 'setup' application should be a clickable ICON on your desktop, placed
there
when you installed the CCS 3.3 software.
If your connection to the target is via a USB port, then it maybe that the
emulator is plugged into a different USB port from what the original 'setup'
specified.

* Yes I am using the USB port to connect the DSK6416 to the PC. So as I
said when I imported the DSK6416 and ran it, I got the same error ( " Error
initializing Emulator I/O Port : 540").*
*
*
*Regarding the .cmd file I'll get back to you once I finish reading more
about it.*
*
*
*Thanks once again. Your comments were very helpful.*
*
*
*Regards,*
*
*
*Varun* Start a New Thread

Varoonian,

a quick search of the E2E forum yielded some discussion about not being able to
initialize the USB port and indicated the problem is the msp430.dll file version
being used.

You might want to search TI.com for the appropriate version of the file for your
configuration.

I also came across this:
"I had a similar problem when coneccting to TMS320C6457 .. the problem was
resolved by changing the subpath properties Port number ( in the Target
configuration file .ccxml) from 0x10 to 0x11. May be you will have to do
something similar."

You might also want to read this:

R. Williams
---------- Original Message -----------
From: "varoonian ."
To: Richard Williams
Cc: c...
Sent: Wed, 23 Jun 2010 13:07:08 -0700
Subject: Re: [c6x] C64X DSPLIB

> Dear Mr.WIlliams,
>
> My replies are prefixed with .
>
> did you run the 'setup' application and select your specific
> emulator/target board?
> With out 'setup' being run and the correct selection made, CCS 3.3
> will use the default values. The default values are probably not what
> you want.
>
> *<**V> : First I installed CCS V3.3 , then the DSK target files in
> C:\CCStudioV3.3.*
> *Then I clicked on Setup Code Composer Studio icon on the desktop and
> imported the target file "dsk6416" from the import folder and also included
> the "Diagnostics Utility". But all the target files in the import
> folder are of type CC5x./4x (.ccs) including the dsk6416 target file.
> Does this play a role in this ?*
>
> Are you connecting to the target via a USP port?
> The CCS 3.1, that I have, uses a parallel port.
> Are you connecting to your target via a USP or via a parallel port?
> Everything has to match for successful communication with your target,
> including
> the target has to be powered ON.
> The 'setup' application should be a clickable ICON on your desktop, placed
> there
> when you installed the CCS 3.3 software.
> If your connection to the target is via a USB port, then it maybe that
> the emulator is plugged into a different USB port from what the
> original 'setup' specified.
>
> * Yes I am using the USB port to connect the DSK6416 to the PC. So
> as I said when I imported the DSK6416 and ran it, I got the same error
> ( " Error initializing Emulator I/O Port : 540").* * * *Regarding the
> .cmd file I'll get back to you once I finish reading more about it.* *
> * *Thanks once again. Your comments were very helpful.* * * *Regards,
> * * * *Varun*
------- End of Original Message -------

_____________________________________ Start a New Thread