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.

user defined functions

hi 

I'm trying to program ezdsp 5505 usb stick

i'm running HTK (Hidden Markov Toolkit) which is a collection of c files. as you can see here, 

 

 undefined                 first referenced

  symbol                       in file     

 ---------                 ----------------

 _AddInXFormDir            ./HVite.obj     

 _AddMMF                   ./HVite.obj     

 _ApplyHMMSetXForm         ./HVite.obj     

 _AttachPreComps           ./HVite.obj   ...

 

 

"AddInXFormDir " "AddMMF" etc. are all function names.

around 100 such errors are generated. all these 100 are user defined functions, defined in various header files which have been included in the include folder.. i dont know why it is still calling it "Undefined symbol". Please help. 

 

  • Is the implementation of these functions in the header files, or in actual C source files or a library.

    The linker is indicating that it can not resolve the label associated with _AddInXFormDir for example, therefore unable to find the implementation.  Simply having it declared in a header file only allows the C Compiler to compile your code with a known prototype of the function.  But you actually need to tell the linker where to find the actual implementation of the function.

    If these functions are implemented in a library, then you need to add the library to the project.  If they are implemented in C source files, then you need to add the appropriate C source files to your project.

  • Thank you very much. that solved the problem. Now the build is complete and when we try to debug it, it shows that the target connection is successfully established. then it gives this statement. "C55xx: Loader: One or more sections of your program falls into a memory region that is not writable. These regions will not actually be written to the target. Check your linker configuration and/or memory map." We are unable to do anything about it. Please help.
  • Sounds like you have a mismatch between your linker command file (see Section 8.6 of SPRU280) used during your build and the debugger memory map.

    Thanks

    ki