DM642 EVM examples

Hi everyone,
I have a very basic question. I have a DM642 EVM, XD510 USB & CCS
3.3 setup. Why does the examples given do not work?

First, upon trying to open the project, there is warning about older
CDB configuration file, which must be converted to TCF. Not sure
whether this is relevant or not though.

Then, when I tried to rebuild the project, I've got an error saying
that no chip is defined. After I correct that using -dCHIP_DM642,
I've got this error:
undefined first referenced
symbol in file
--------- ----------------
_I2C_outOfReset
C:/CCStudio_v3.3/boards/evmdm642/lib/evmdm642bsl.lib
.. etc ..
>> error: symbol referencing errors - './Debug/led.out' not built
>> Compilation failure
Build Complete,
2 Errors, 0 Warnings, 0 Remarks.

Can anyone help? Thanks.
Hanief

Check Out Industry's First Single-Chip, Multi-Format, Real-Time HD Video Transcoding Solution for Commercial & Consumer End Equipment: www.ti.com/dm6467 Start a New Thread

Hanief,

On Tue, Mar 4, 2008 at 11:32 PM, H wrote:

> Hi everyone,
> I have a very basic question. I have a DM642 EVM, XD510 USB & CCS
> 3.3 setup. Why does the examples given do not work?
>
> First, upon trying to open the project, there is warning about older
> CDB configuration file, which must be converted to TCF. Not sure
> whether this is relevant or not though.

This means that the project was developed on a previous version of CCS
[TI should have converted it to the current version]. Once the
conversion to tcf is completed, the project *should* work as it did
originally.
>
> Then, when I tried to rebuild the project, I've got an error saying
> that no chip is defined. After I correct that using -dCHIP_DM642,
> I've got this error:
> undefined first referenced
> symbol in file
> --------- ----------------
> _I2C_outOfReset
> C:/CCStudio_v3.3/boards/evmdm642/lib/evmdm642bsl.lib
> .. etc ..
> >> error: symbol referencing errors - './Debug/led.out' not built
> >> Compilation failure
> Build Complete,
> 2 Errors, 0 Warnings, 0 Remarks.

I am not specifically familiar with this project and the 'etc' part is
tough to decipher. One issue could be that the original project was
designed to be built with CSL and it was omitted [or relocated] from
the current version of CCS. You might try selecting the
'CCStudio_v3.3' directory under Windows Explorer and searching for all
*.c and *.h files that contain 'I2C_outOfReset'. If you locate the
function, you can add it to your project.

mikedunn
>
> Can anyone help? Thanks.
> Hanief
>
>

--
www.dsprelated.com/blogs-1/nf/Mike_Dunn.php
Check Out Industry's First Single-Chip, Multi-Format, Real-Time HD Video Transcoding Solution for Commercial & Consumer End Equipment: www.ti.com/dm6467 Start a New Thread

--- In c..., "Michael Dunn" wrote:
>
> Hanief,
>
> On Tue, Mar 4, 2008 at 11:32 PM, H wrote:
> > Then, when I tried to rebuild the project, I've got an error
> > saying that no chip is defined. After I correct that using -
> > dCHIP_DM642, I've got this error:
> > undefined first referenced
> > symbol in file
> > --------- ----------------
> > _I2C_outOfReset
> > C:/CCStudio_v3.3/boards/evmdm642/lib/evmdm642bsl.lib
> > .. etc ..
> > >> error: symbol referencing errors - './Debug/led.out' not
built
> > >> Compilation failure
> > Build Complete,
> > 2 Errors, 0 Warnings, 0 Remarks.
>
> I am not specifically familiar with this project and the 'etc'
part is
> tough to decipher. One issue could be that the original project was
> designed to be built with CSL and it was omitted [or relocated]
from
> the current version of CCS. You might try selecting the
> 'CCStudio_v3.3' directory under Windows Explorer and searching for
all
> *.c and *.h files that contain 'I2C_outOfReset'. If you locate the
> function, you can add it to your project.
>
> mikedunn
> >
> > Can anyone help? Thanks.
> > Hanief
> >

Hi again,
Well, I didn't copy the rest of the errors, hence the 'etc' bit. In
any case, here they are:
_I2C_outOfReset
_I2C_getConfig
_I2C_start
_GPIO_open
_I2C_open
_CSLDM642_LIB_
_CACHE_enableCaching
_I2C_xrdy
_I2C_bb
_I2C_sendStop
_EMIFA_config
__CSL_init
_I2C_writeByte
_I2C_config
_GPIO_pinRead
_GPIO_pinEnable
_GPIO_pinDirection
_GPIO_pinWrite
All 18 are called in
C:/CCStudio_v3.3/boards/evmdm642/lib/evmdm642bsl.lib
The thing is, all the above symbols are defined in various header
files that are already included with the project. I2C_outOfReset for
example, is defined with
IDECL void I2C_outOfReset(I2C_Handle hI2c);
in "csl_i2c.h" which is included in the project by default. I'm not
too sure what IDECL is though.
Thanks.
Hanief

Check Out Industry's First Single-Chip, Multi-Format, Real-Time HD Video Transcoding Solution for Commercial & Consumer End Equipment: www.ti.com/dm6467 Start a New Thread

Hanief,

On Thu, Mar 6, 2008 at 3:24 AM, H wrote:

> --- In c..., "Michael Dunn" wrote:
> >
> > Hanief,
> > > On Tue, Mar 4, 2008 at 11:32 PM, H wrote:
> >
> >
> > > Then, when I tried to rebuild the project, I've got an error
> > > saying that no chip is defined. After I correct that using -
> > > dCHIP_DM642, I've got this error:
> > > undefined first referenced
> > > symbol in file
> > > --------- ----------------
> > > _I2C_outOfReset
> > > C:/CCStudio_v3.3/boards/evmdm642/lib/evmdm642bsl.lib
> > > .. etc ..
> > > >> error: symbol referencing errors - './Debug/led.out' not
> built
> > > >> Compilation failure
> > > Build Complete,
> > > 2 Errors, 0 Warnings, 0 Remarks.
> >
> > I am not specifically familiar with this project and the 'etc'
> part is
> > tough to decipher. One issue could be that the original project was
> > designed to be built with CSL and it was omitted [or relocated]
> from
> > the current version of CCS. You might try selecting the
> > 'CCStudio_v3.3' directory under Windows Explorer and searching for
> all
> > *.c and *.h files that contain 'I2C_outOfReset'. If you locate the
> > function, you can add it to your project.
> >
> > mikedunn
> > >
> > > Can anyone help? Thanks.
> > > Hanief
> > > Hi again,
> Well, I didn't copy the rest of the errors, hence the 'etc' bit. In
> any case, here they are:
> _I2C_outOfReset
> _I2C_getConfig
> _I2C_start
> _GPIO_open
> _I2C_open
> _CSLDM642_LIB_
> _CACHE_enableCaching
> _I2C_xrdy
> _I2C_bb
> _I2C_sendStop
> _EMIFA_config
> __CSL_init
> _I2C_writeByte
> _I2C_config
> _GPIO_pinRead
> _GPIO_pinEnable
> _GPIO_pinDirection
> _GPIO_pinWrite

These look like CSL files.

> All 18 are called in
> C:/CCStudio_v3.3/boards/evmdm642/lib/evmdm642bsl.lib
> The thing is, all the above symbols are defined in various header
> files that are already included with the project. I2C_outOfReset for
> example, is defined with
> IDECL void I2C_outOfReset(I2C_Handle hI2c);
> in "csl_i2c.h" which is included in the project by default. I'm not
> too sure what IDECL is though.

IDECL should be defined somewhere in a header file.

The functions are declared in header files, but do the actual functions exist??

The nature of your error message [symbol referencing errors] would
lead me to believe that your project cannot locate the functions.

mikedunn
> Thanks.
> Hanief
>
>

--
www.dsprelated.com/blogs-1/nf/Mike_Dunn.php
Check Out Industry's First Single-Chip, Multi-Format, Real-Time HD Video Transcoding Solution for Commercial & Consumer End Equipment: www.ti.com/dm6467 Start a New Thread

--- In c..., "Michael Dunn" wrote:
>
> Hanief,
>
> On Thu, Mar 6, 2008 at 3:24 AM, H wrote:
>
> > --- In c..., "Michael Dunn"
wrote:
> > >
> > > Hanief,
> > >
> > > On Tue, Mar 4, 2008 at 11:32 PM, H wrote:
> > >
> > > > Then, when I tried to rebuild the project, I've got an error
> > > > saying that no chip is defined. After I correct that using -
> > > > dCHIP_DM642, I've got this error:
> > > > undefined first referenced
> > > > symbol in file
> > > > --------- ----------------
> > > > _I2C_outOfReset
> > > > C:/CCStudio_v3.3/boards/evmdm642/lib/evmdm642bsl.lib
> > > > .. etc ..
> > > > >> error: symbol referencing errors - './Debug/led.out' not
> > built
> > > > >> Compilation failure
> > > > Build Complete,
> > > > 2 Errors, 0 Warnings, 0 Remarks.
> > >
> > > I am not specifically familiar with this project and the 'etc'
> > part is
> > > tough to decipher. One issue could be that the original
project was
> > > designed to be built with CSL and it was omitted [or
relocated]
> > from
> > > the current version of CCS. You might try selecting the
> > > 'CCStudio_v3.3' directory under Windows Explorer and
searching for
> > all
> > > *.c and *.h files that contain 'I2C_outOfReset'. If you
locate the
> > > function, you can add it to your project.
> > >
> > > mikedunn
> > > >
> > > > Can anyone help? Thanks.
> > > > Hanief
> > > >
> >
> > Hi again,
> > Well, I didn't copy the rest of the errors, hence the 'etc'
bit. In
> > any case, here they are:
> > _I2C_outOfReset
> > _I2C_getConfig
> > _I2C_start
> > _GPIO_open
> > _I2C_open
> > _CSLDM642_LIB_
> > _CACHE_enableCaching
> > _I2C_xrdy
> > _I2C_bb
> > _I2C_sendStop
> > _EMIFA_config
> > __CSL_init
> > _I2C_writeByte
> > _I2C_config
> > _GPIO_pinRead
> > _GPIO_pinEnable
> > _GPIO_pinDirection
> > _GPIO_pinWrite
>
> These look like CSL files.
>
> > All 18 are called in
> > C:/CCStudio_v3.3/boards/evmdm642/lib/evmdm642bsl.lib
> > The thing is, all the above symbols are defined in various
header
> > files that are already included with the project.
I2C_outOfReset for
> > example, is defined with
> > IDECL void I2C_outOfReset(I2C_Handle hI2c);
> > in "csl_i2c.h" which is included in the project by default. I'm
not
> > too sure what IDECL is though.
>
> IDECL should be defined somewhere in a header file.
>
> The functions are declared in header files, but do the actual
functions exist??
>
> The nature of your error message [symbol referencing errors] would
> lead me to believe that your project cannot locate the functions.
>
> mikedunn

Hi Mikedunn & everyone,
You're right, IDECL is defined somewhere above in "csl_i2c.h".

The functions are not called in the source file. The only
place 'I2C_outOfReset' is called is in the file it's declared:
IDEF void I2C_outOfReset(I2C_Handle hI2c){
I2C_FSETSH(hI2c,I2CMDR,IRS,NRST);

Btw, I just noticed that "evmdm642bsl.lib", the library file that's
causing all this problems, is not included in the project. Huh?

Thanks.
Hanief

Check Out Industry's First Single-Chip, Multi-Format, Real-Time HD Video Transcoding Solution for Commercial & Consumer End Equipment: www.ti.com/dm6467 Start a New Thread

--- In c..., "Michael Dunn" wrote:
>
> Hanief,
>
> On Tue, Mar 4, 2008 at 11:32 PM, H wrote:
>
> > Hi everyone,
> > I have a very basic question. I have a DM642 EVM, XD510 USB &
> > CCS 3.3 setup. Why does the examples given do not work?
> >
> > First, upon trying to open the project, there is warning about
> > older CDB configuration file, which must be converted to TCF.
> > Not sure whether this is relevant or not though.
>
> This means that the project was developed on a previous version of
> CCS [TI should have converted it to the current version]. Once the
> conversion to tcf is completed, the project *should* work as it did
> originally.
> >
> > Then, when I tried to rebuild the project, I've got an error
> > saying that no chip is defined. After I correct that using -
> > dCHIP_DM642, I've got this error:
> > undefined first referenced
> > symbol in file
> > --------- ----------------
> > _I2C_outOfReset
> > C:/CCStudio_v3.3/boards/evmdm642/lib/evmdm642bsl.lib
> > .. etc ..
> > >> error: symbol referencing errors - './Debug/led.out' not
built
> > >> Compilation failure
> > Build Complete,
> > 2 Errors, 0 Warnings, 0 Remarks.
>
> I am not specifically familiar with this project and the 'etc'
> part is tough to decipher. One issue could be that the original
> project was designed to be built with CSL and it was omitted [or
> relocated] from the current version of CCS. You might try
> selecting the 'CCStudio_v3.3' directory under Windows Explorer and
> searching for all *.c and *.h files that contain 'I2C_outOfReset'.
> If you locate the function, you can add it to your project.
>
> mikedunn
> >
> > Can anyone help? Thanks.
> > Hanief

Hi everyone,
Just to say that I've solved this problem, quite a stupid mistake
really. It was as Mike suggested, related to CSL. I only added -
l"[User_Install_Dir]\lib" (the directory) in the linker options
instead of -l"[User_Install_Dir]\lib|cslDM642.lib" (the file).
Cheers,
Hanief
p/s: can enyone enlighten me of the difference between #include
and #include "abc.h"? Start a New Thread

Hanief,

On 3/28/08, H wrote:
>
> --- In c... , "Michael Dunn" <
> mike.dunn.001@...> wrote:
> >
> > Hanief,
> >
> > On Tue, Mar 4, 2008 at 11:32 PM, H wrote:
> >
> > > Hi everyone,
> > > I have a very basic question. I have a DM642 EVM, XD510 USB &
> > > CCS 3.3 setup. Why does the examples given do not work?
> > >
> > > First, upon trying to open the project, there is warning about
> > > older CDB configuration file, which must be converted to TCF.
> > > Not sure whether this is relevant or not though.
> >
> > This means that the project was developed on a previous version of
> > CCS [TI should have converted it to the current version]. Once the
> > conversion to tcf is completed, the project *should* work as it did
> > originally.
> > >
> > > Then, when I tried to rebuild the project, I've got an error
> > > saying that no chip is defined. After I correct that using -
> > > dCHIP_DM642, I've got this error:
> > > undefined first referenced
> > > symbol in file
> > > --------- ----------------
> > > _I2C_outOfReset
> > > C:/CCStudio_v3.3/boards/evmdm642/lib/evmdm642bsl.lib
> > > .. etc ..
> > > >> error: symbol referencing errors - './Debug/led.out' not
> built
> > > >> Compilation failure
> > > Build Complete,
> > > 2 Errors, 0 Warnings, 0 Remarks.
> >
> > I am not specifically familiar with this project and the 'etc'
> > part is tough to decipher. One issue could be that the original
> > project was designed to be built with CSL and it was omitted [or
> > relocated] from the current version of CCS. You might try
> > selecting the 'CCStudio_v3.3' directory under Windows Explorer and
> > searching for all *.c and *.h files that contain 'I2C_outOfReset'.
> > If you locate the function, you can add it to your project.
> >
> > mikedunn
> > >
> > > Can anyone help? Thanks.
> > > Hanief
>
> Hi everyone,
> Just to say that I've solved this problem, quite a stupid mistake
> really. It was as Mike suggested, related to CSL. I only added -
> l"[User_Install_Dir]\lib" (the directory) in the linker options
> instead of -l"[User_Install_Dir]\lib|cslDM642.lib" (the file).
> Cheers,
> Hanief
> p/s: can enyone enlighten me of the difference between #include
> and #include "abc.h"?
>

Both forms of '#include' work the same way - they replace the line with the
contents of the referenced file for the purpose of compilation. The only
difference is the paths that are searched to locate the file. The simple
short answer is that you use ' <> ' to include files that are distributed
with the compiler and ' "" ' to include files that are part of your project.

mikedunn

>

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