• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 52 subscribers
  • Views 1463 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

CCS v5.4.0.00091 / Windows 7 - 64 (F28069) Linker Command File Entry Vanishes!

Mark Walsh1
Prodigy 180 points
Other Parts Discussed in Thread: CONTROLSUITE

When I first got started over a month ago (note that I was a heavy user of CC and then CCS from 2001 to 2005), I was experiencing differences in behavior between the sample projects, and my own project with the sample projects' code pasted into them, so I imported a sample project, pasted in my code, and told CCS to rename the project.  The first problem came when I ran out of memory, and editing the .cmd file had no effect.  I soon discovered that in the importing of the project, CCS had copied a .cmd file to my local directory, but was still using the old one.  That was easy to fix; I simply went to Project Properties, pointed to the new file, and moved forward.

Unfortunately, the sample code (e.g. Example_2806xCpuTimer would not function from within my project, and I finally got to the point where something had to be done about it.  I put breakpoints in the ISRs, but the DSP would never get there.  Going back to the original sample project, the DSP would get there.  I read hundreds of forum entries until I found a recent one in which somebody was experiencing similar strange behavior, and it was suggested that he run the "Check for Updates" function.  I did so myself, and received the following error messages:

Some sites could not be found. See the error log for more detail.
No repository found at file:/C:/Users/km6xu/AppData/Local/Temp/ijtmp_6B5DB922-B91C-45C9-8E61-8B6181ECDD0D/dvtRepo.
No repository found at file:/C:/Users/km6xu/AppData/Local/Temp/ijtmp_6B5DB922-B91C-45C9-8E61-8B6181ECDD0D/gmfRepo.

What does that mean?  It should be noted that when I first installed CCS, I selected all of the defaults, and received some cryptic warning messages about XDAIS (which I definitely don't need), but looking in the forums brought no clarity (other than the suggestion to try checking for updates).  Anyway, after this update, I tried to build my code again, and received many linker errors.  Looking through the linker output, I found that it was using a different linker command file (F2806x_Headers_nonBIOS.cmd) rather than one that I had specified.  I went to the project properties, and found that the selection for my linker command file was gone!  I selected my own file, had the same build results, went back to Project Properties, saw that my own entry had again been deleted, changed it back to my own file, and repeated the above several times, but without luck.  Rebooting the PC didn't change anything, and I can no longer build my project!

Looking through the forums, I saw that somebody had a somewhat similar problem, and he was told to use the "add files" function to get his own linker command file into his project, and hopefully the newer file would take precedence over the old one.  Sure enough, buried in my project was a linker command file with the old name.  When I tried to do as suggested for the other person, I received the following error:

Could not link:
28069_RAM_lnk_new.cmd

I wasn't trying to link, I was just trying to add my linker command file to the project!  I have had a number of hurdles, but this one is the worst so far as I cannot figure out a workaround.  Any ideas (besides spending an entire day reinstalling everything)?

And I don't know if it is relevant, but I should add another data point.  In addition to my own hardware, I have a TI eval board (Docking-stn USB-EMU [R3]) with a TI F28069 controlCARD Release 1.1.  When I run the sample PWM code, there is no PWM activity on either of the boards, even though the code looks correct.  Is this a problem with CCSv5, both boards, or is the sample code defective?  And could this be related to the headache above?  I haven't bothered to port the sample project's code into my code because it seems like if it doesn't work as it should, it isn't likely to work when integrated with my code.  What to do?

Also, if this is not the appropriate place to ask such questions, please flame away.  I know that things have changed since 2005, and I just need to get some results.

Thanks -- Mark

  • 0
    TI__Guru**** 173310 points

    Mark,

    I'm sorry to hear you've been having so many troubles getting your project going with CCSv5.4. Let us take a step back and I'll try to help you get past your linker command file issues and build errors.

    I think we will set aside the "Check for updates" errors for now, as I don't think the issue you were experiencing running your code would've been related to updates.

    So for your current situation, please provide the following information:

    1) What is your exact version of CCS and compiler tools being used for the build? You can check the compiler version from Project Properties->General.

    2) What are the linker errors you see? Please copy and paste the full output in the CCS build console to a text file and attach it here.

    The ControlSuite example projects typically have 2 linker command file - F2806x_Headers_nonBIOS.cmd and 28069_RAM_lnk.cmd. I suspect you want to replace 28069_RAM_lnk.cmd with your own, is that right? If so, you should be able to simply exclude the 28069_RAM_lnk.cmd from the build, and then copy or link to your custom linker command file. The F2806x_Headers_nonBIOS.cmd is also typically necessary to allocate sections specific to peripheral registers. If you have already tried this, please detail the steps you took and any problems/errors along the way. In any case looking at the build output should give some additional clues as well.

    Mark Walsh1 said:
     In addition to my own hardware, I have a TI eval board (Docking-stn USB-EMU [R3]) with a TI F28069 controlCARD Release 1.1.  When I run the sample PWM code, there is no PWM activity on either of the boards, even though the code looks correct.  Is this a problem with CCSv5, both boards, or is the sample code defective?

    The Controlsuite examples are well tested and should work out of the box. If they are not, I would suggest posting this specific question to the C2000 device forum as it is that team that creates/releases these examples.

  • 0 in reply to AartiG
    Prodigy 180 points

    AartiG, I really appreciate your quick response!  We have CCS version 5.4.0.00091, and the compiler version is TI v6.1.0 (effective compiler version TI v6.1.4).

    The linker errors made it pretty obvious that a linker command file was not being found.

    Thanks for pointing out that in addition to specifying a linker command file under Project, Properties (where I was experiencing the buggy behavior), your suggestion made me realize that one can also specify it by right-clicking on the project (in the Project Explorer window), and selecting "Add Files..."  At first, I was experiencing some buggy behavior there as well.  I could add my command file, but it would appear in the list with a 'slash' through its icon, and simply renaming the file and trying again did not help.  What *did* work was moving all of the .cmd files out of my project directory, then moving in just the one that I wanted, and then using the "Add Files" function.  Simply *looking* at it with Project, Properties shows that it has been accepted as the linker command file.

    The bottom line is that the project now compiles and *links!*

    I'll document my experience with the sample PWM code, and then go to the C2000 device forum as you have suggested.

    Thanks -- Mark

  • 0 in reply to Mark Walsh1
    TI__Guru**** 173310 points

    Mark, glad to hear you are now able to compile and link and get past your previous errors.

    Mark Walsh1 said:
     I could add my command file, but it would appear in the list with a 'slash' through its icon, and simply renaming the file and trying again did not help.

    A file with a slash through it (also grayed out) means that the file is "excluded" from build. I'm not really sure why that happened in your case, but this and some other concepts concerning CCS Projects and build system are explained in this wiki article, which could be a helpful resource as you go through your development: http://processors.wiki.ti.com/index.php/Projects_and_Build_Handbook_for_CCS