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.

error: symbol referencing errors - './Debug/transmitter.out not built

Other Parts Discussed in Thread: CCSTUDIO

I'm having trouble building a project included in Chassaing's book. This project implements a BPSK modulator on the DSK, but when loading the program to the DSK

I have found there is no output, so I have tried to modifiy the code to include these lines:

#define DSK6713_AIC23_INPUT_MIC 0x0015

#define DSK6713_AIC23_INPUT_LINE 0x0011

Uint16 inputsource=DSK6713_AIC23_INPUT_MIC

but when debugging there are several problems, because the library search paths have to be modified using building options. So far I haven't been able to debug the modified code because even after including the search path it keeps showing this:

>> warning: Detected a near (.bss section relative) data reference to the symbol
_DSK6713_AIC23_codecdatahandle defined in section .far. The
reference occurs in
C:\CCStudio_v3.1\MyProjects\PSK\transmitter\Debug\c6713dskinit.obj,
section .text, SPC offset 00000074. Either make the symbol near
data by placing it in the .bss section, or make the references to
the symbol far. For C/C++ code use 'far' or 'near' modifiers on
the type definition of the symbol or compile with the
--mem_model:data switch.

I would like some help, because even after having changed the compiler option  Memory Models: Far(--mem_model:data=far) It still won't work.

  • Carlos,

    You should concentrate first on getting the proven project to work exactly as it is from the book. Since this has been used by many people and published, and since you are using the same hardware, you should be able to duplicate those results.

    It is very difficult to move from something that is known to be failing and then try to debug modifications from there that are now failing in new ways.

    The warning says that the reference is coming from an object file. Do you build that object file from source or is it a pre-built object or library file? The problem is likely in your linker command file, but all of this consideration is equally likely to be taking you down a path to another failing project.

    Regards,
    RandyP

  • Well, the fact is that if I choose to take Chassaing's project as it comes in the CD and open it and then loading it to the DSK and running it,

    the osciloscope shows nothing at the output. I started doing modifications after having tried several times to get the original project to work.

    If I take this project and make no changes, but select Debug, it shows a first error, because it can't find dsk6713.h and other files. That's why I added the search paths in

    the first place. So far I have been able to get the BPSK output, but I had to suppress a part of the code in which the signal from the microphone was first passed through

     a low pass filter. I did that because even after a succesful debug, when trying to load the program and error appeared saying that there was a memory map problem at

    address 0x90000000. Now I can run it, but I still have to try the demodulator.

  • Carlos,

    Since I do not have any Chassaing books, I do not know what you get in one of the projects from it. Most well-documented projects have all the files, including the .pjt project file, so that you can build it successfully. Is that not the case here?

    Which revision of the book, and which book, are you referencing? I would assume it is the 2008 revision.

    Which project is it?

    You should also have the DSK libraries and example files. Can you get one of those to work that will read from one of the analog inputs and write to one of the analog outputs? This is to verify that your board works.

    But I am confused now about what is running and what is not. From your comments above, it sounds like you do get output from the project but not the way you want to.

    Have you been through the online training material for the C6713? Go to the Wiki and do a search for "c6713 training" (no quotes). You will find a link to an archived training class that includes a student guide and example labs that you can run. The student guide walks you through how to create and build a project, how to work with the memory map and the memory components of the DSK.

    You should have been able to avoid this training when you started from a well-documented working example. But since you are making modifications, the training will be needed so you can understand how to make things fit in the available memory and how the various parts of a CCS project are created.

    May I ask why you have chosen this project and this DSK for your work? We do have newer and faster boards, such as for the C6748. Just curious.

    Regards,
    RandyP

  • Hi, well the book is the 2008 revised edition, authors are Rulph Chassaing and Donald Reay. It comes with a CD, containing all of the example codes in the book, as projects to implement in the DSK. I'm currently working with one of the projects in the chapter DSP applications and Student Projects. I have already tested most of the projects in  chapter 2: Input and Output with the DSK, one of them explains how to use the DSP to acquire a signal from a microphone and then sending it to the output. This morning I tested that program to make sure my DSK works properly.

    Now to answer your question about what is working: the project transmitter located in the folder PSK in the CD didn't work for me at first. It had all the necessary files to be implemented in the board, especially the .out file, but the oscilloscope showed nothing. Then I tried to debug it and It didn't work because of the search paths. So I modified the search paths in the compiler and linker tabs in Build options, but I kept getting an error related to memory. I fixed that by eliminating a code line that reads:

    yn= fircircfunc(sample_data,h,N)

    this was supposed to implement a lowpass filter using a file called lpf1500.cof, which contains coefficients for a lowpass filter with cutoff frequency of 3 kHz.

    So after this modification was made I tested the program using an oscilloscope and I see a sine wave modulated  using BPSK (I can see the phase changes every now and then). This morning I tested the receiver connecting two DSK's, but unfortunately It didn't work, and I'm still working on that.

    Thanks for the information about training material, I'll check it out. It's been two months since I started my thesis and I have worked with Chassaing's book and another book called "Communication System Design Using DSP Algorithms with laboratory experiments for the TMS320C6713" written by Steven A. Tretter

    The reason why I  use the  C6713 is that it is  the only DSP starter kit available at my University (Universidad de Antioquia, Colombia), and my undergraduate thesis consists in developing a series of laboratory projects to show Electronic Engineering Undergraduates such as myself how to implement DSP algorithms, because so far the Digital Signal Processing subject has been taught using matlab (simulations) and the teacher in charge  of the course wants to change that. I must also develop a pitch estimator all by myself (no examples found so far) and a VOCODER.

  • Carlos,

    If you can, please point the course instructor to a recent Blog on the E2E Forum by our University Program manager, Cathy Wicks, at http://e2e.ti.com/blogs_/b/designproject/archive/2012/06/03/now-is-a-great-time-to-update-your-dsp-lab-or-start-a-new-one.aspx . She discusses plans to help with things just like what the course teacher wants to do, update the course to include hardware and especially the latest hardware from the C6748 device. It is a superset of the C6713, but of course there are some differences between the DSK boards that we build now compared to the DSK6713.

    It is very good to hear that you have several of the projects working and you are able to get input and output on the DSK.

    If your project is not building exactly the way it does in the CD, then you must be using a different version of the Code Generation Tools or different build options. The Build Options are specified in the .pjt file, so that should not be the problem. But does the book say whether you must build with Release to get it to fit, or does it imply that a Debug build should work?

    Your post above sounds more positive, like you are making some good progress in spite of my lack of answers for you. Please keep us posted on your progress. And please be patient with us, since it is difficult to give a good answer to how to fix something that has changed. We want to read of your success as much as you do.

    Regards,
    RandyP