• State Resolved
  • Locked Locked
  • Replies 10 replies
  • Subscribers 82 subscribers
  • Views 2149 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

I can compile due a this error list

guillermo ruiz magaz
Intellectual 470 points
Other Parts Discussed in Thread: TMS320F28335

Hi people, I have a problem when intented to debug a project. I list the content.

Anybody can help me?

 

**** Build of configuration Debug for project Example_2833xAdcSeqModeTest_16 ****

 

C:\Program Files\Texas Instruments\ccsv4\utils\gmake\gmake -k all

'Building target: Example_2833xAdcSeqModeTest.out'

'Invoking: C2000 Linker'

"C:/Program Files/Texas Instruments/ccsv4/tools/compiler/c2000/bin/cl2000" -@ccsLinker.opt -o "Example_2833xAdcSeqModeTest.out"

<Linking>

"C:\Users\ruicano\AppData\Local\Temp\031323", line 27: error: cannot find file

"$"

"C:\Users\ruicano\AppData\Local\Temp\031323", line 27: error: expecting

filename, option, MEMORY, or SECTIONS instead of "("

warning: creating output section ".adc_cal" without a SECTIONS specification

warning: creating output section ".ebss" without a SECTIONS specification

warning: creating output section ".econst" without a SECTIONS specification

warning: creating output section ".reset" without a SECTIONS specification

warning: creating output section "AdcMirrorFile" without a SECTIONS

specification

warning: creating output section "AdcRegsFile" without a SECTIONS

specification

warning: creating output section "CpuTimer0RegsFile" without a SECTIONS

specification

warning: creating output section "CpuTimer1RegsFile" without a SECTIONS

specification

warning: creating output section "CpuTimer2RegsFile" without a SECTIONS

specification

warning: creating output section "CsmPwlFile" without a SECTIONS specification

warning: creating output section "CsmRegsFile" without a SECTIONS

specification

warning: creating output section "DevEmuRegsFile" without a SECTIONS

specification

warning: creating output section "DmaRegsFile" without a SECTIONS

specification

warning: creating output section "ECanaLAMRegsFile" without a SECTIONS

specification

warning: creating output section "ECanaMOTORegsFile" without a SECTIONS

specification

warning: creating output section "ECanaMOTSRegsFile" without a SECTIONS

specification

warning: creating output section "ECanaMboxesFile" without a SECTIONS

specification

warning: creating output section "ECanaRegsFile" without a SECTIONS

specification

warning: creating output section "ECanbLAMRegsFile" without a SECTIONS

specification

warning: creating output section "ECanbMOTORegsFile" without a SECTIONS

specification

warning: creating output section "ECanbMOTSRegsFile" without a SECTIONS

specification

warning: creating output section "ECanbMboxesFile" without a SECTIONS

specification

warning: creating output section "ECanbRegsFile" without a SECTIONS

specification

warning: creating output section "ECap1RegsFile" without a SECTIONS

specification

warning: creating output section "ECap2RegsFile" without a SECTIONS

specification

warning: creating output section "ECap3RegsFile" without a SECTIONS

specification

warning: creating output section "ECap4RegsFile" without a SECTIONS

specification

warning: creating output section "ECap5RegsFile" without a SECTIONS

specification

warning: creating output section "ECap6RegsFile" without a SECTIONS

specification

warning: creating output section "EPwm1RegsFile" without a SECTIONS

specification

warning: creating output section "EPwm2RegsFile" without a SECTIONS

specification

warning: creating output section "EPwm3RegsFile" without a SECTIONS

specification

warning: creating output section "EPwm4RegsFile" without a SECTIONS

specification

warning: creating output section "EPwm5RegsFile" without a SECTIONS

specification

warning: creating output section "EPwm6RegsFile" without a SECTIONS

specification

warning: creating output section "EQep1RegsFile" without a SECTIONS

specification

warning: creating output section "EQep2RegsFile" without a SECTIONS

specification

warning: creating output section "FlashRegsFile" without a SECTIONS

specification

warning: creating output section "GpioCtrlRegsFile" without a SECTIONS

specification

warning: creating output section "GpioDataRegsFile" without a SECTIONS

specification

warning: creating output section "GpioIntRegsFile" without a SECTIONS

specification

warning: creating output section "I2caRegsFile" without a SECTIONS

specification

warning: creating output section "McbspaRegsFile" without a SECTIONS

specification

warning: creating output section "McbspbRegsFile" without a SECTIONS

specification

warning: creating output section "PartIdRegsFile" without a SECTIONS

specification

warning: creating output section "PieCtrlRegsFile" without a SECTIONS

specification

warning: creating output section "PieVectTableFile" without a SECTIONS

specification

warning: creating output section "SciaRegsFile" without a SECTIONS

specification

warning: creating output section "ScibRegsFile" without a SECTIONS

specification

warning: creating output section "ScicRegsFile" without a SECTIONS

specification

warning: creating output section "SpiaRegsFile" without a SECTIONS

specification

warning: creating output section "SysCtrlRegsFile" without a SECTIONS

specification

warning: creating output section "XIntruptRegsFile" without a SECTIONS

specification

warning: creating output section "XintfRegsFile" without a SECTIONS

specification

warning: creating output section "codestart" without a SECTIONS specification

warning: creating output section "ramfuncs" without a SECTIONS specification

warning: entry-point symbol other than "_c_int00" specified: "code_start"

error: errors encountered during linking; "Example_2833xAdcSeqModeTest.out" not

built

 

>> Compilation failure

C:\Program Files\Texas Instruments\ccsv4\utils\gmake\gmake: *** [Example_2833xAdcSeqModeTest.out] Error 1

C:\Program Files\Texas Instruments\ccsv4\utils\gmake\gmake: Target `all' not remade because of errors.

Build complete for project Example_2833xAdcSeqModeTest_16

  • 0
    Expert 2355 points

    Looks like a linker command file error.  The first error will need you to post a copy of that file for debugging.  The warnings on the other hand look like you have not included the peripheral link file (DSP2833x_Headers_NonBIOS.cmd) which is needed to allocate the memory map for the peripherals.

    Tim

  • 0 in reply to Tim King61612
    Intellectual 470 points

    Hi Tim, you said taht is necessary, ...post a copy of that file for debugging.

    Which file? In the Debug folder I have anymore files.

    For the other warnings, I have linked the DSP2833x_Headers_NonBIOS.cmd.

    I attach a project ..._15, that functions properly in my notebook, but no in my computer PC in the laboratory.

    6685.DSP2833x_examples_ccsv4.rar

    My procedure is sometimes, work in my house, compiles the programm and copy in my usb, when arrive to lab. copy and paste in anew folder and make any changes.

    And this project is imposible make this, I am confused.

    I look the .map file, and compare whith othes and is more diferent.

     

     If you can help me.

     

    thanks 4 all

     

    guillermo

  • 0 in reply to guillermo ruiz magaz
    Expert 2355 points

    What you have here is a problem with linked files in your project.  What has happened is that your two command files are not actually part of your project but basically just shortcuts.  This means they are not stored in the project directory but somewhere else on the PC.  What is happening is that you may have changed them on PC #1 but when you copied your project you did not copy the changed files, just the links.  When you got to PC #2 these links linked to files with possibly different configurations.

     

    Here is what I suggest you do:

    On PC #1 (notebook):

    1) In CCS, delete the two command files from your project, however note where they are in your filesystem.

    2) Find the two command files 28335_RAM_lnk.cmd and DSP2833x_Headers_NonBIOS.cmd in your filesystem.  Make a copy of them and paste them in your project directory.

    3) CCS should now add them automatically to your project.  If not, manually add them to your project using Project->Add Files to Project in the menu.

    Now when you copy your project to your lab computer via the usb drive you should have exactly the same code as the other project on the notebook.  Hopefully this will solve the problem.


    Now if you have your original linker errors such as those posted in the original post, please copy the code from 28335_RAM_lnk.cmd into a post and I will see if I can spot where the errors are coming from.

    Thanks,

    Tim


  • 0 in reply to Tim King61612
    Intellectual 470 points

    5047.28335_RAM_lnk.rar

    Hi Tim I make your changes, but don't work propely.

    I look that any files are really links to this files.

    Is posible, make that the entire files in my projects are files and not links? because I believe that, my problem is this.

    thanks for all. 

  • 0 in reply to guillermo ruiz magaz
    Expert 2355 points

    You should remove all linked files and replace them with copies inside your project folder.  This should stop the problem of the project changing between computers.

     

    Tim

  • 0 in reply to Tim King61612
    Intellectual 470 points

    Thanks Tim, I have copied the files in project folder.

    yesterday function OK, but today the message is:

    This project was created for a device-variant that is not currently recognized: TMS320C28XX.TMS320F28335. Please install the device-variant descriptor, or migrate the project to one of the supported device-variants.

    Do you have a suggested reply?

    guillermo

  • 0 in reply to guillermo ruiz magaz
    Intellectual 470 points

    Tim The last problem I believe is a ground association faults.

    I have:

    -Power plant ground

    -Digital ground

    -Analog ground

    -PC ground

    I connect at the first moment the PC and EZDSP, and make a correct compile and target connection.

    conclussion: there are a problem with grounds.

    Thanks for all Tim.

     

    guillermo

  • 0 in reply to guillermo ruiz magaz
    Expert 2355 points
    Unfortunately I do not. Maybe others on this forum or the CCS forum may be able to help you. I suggest since its a new error, make it a new thread as your original error has been solved and has a verified answer. Tim
  • 0 in reply to Tim King61612
    Intellectual 470 points

    Hi Tim I solved the ground and connect EZDSP errors.

    I have put an isolator in the AC power supply  that feed the Boost plant.

     

    thanks.

     

    guillermo

  • 0 in reply to guillermo ruiz magaz
    Intellectual 470 points

    The another compiler error is in the Build  Properties:

    I had put (I don't know because this) the Release in the Build properties, I put the Debug mode and the compiler function Ok.

     

    guillermo