• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Subscribers 82 subscribers
  • Views 848 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.

TMS320F28335: DSP2833x_Headers_nonBIOS.cmd is not being built

Neal OHara
Prodigy 100 points

Part Number: TMS320F28335

Hello, I have a project that is using a custom F28335_Link.cmd file, and is using a local copy (but no changes) of the DSP2833x_Headers_nonBIOS.cmd file.

However, my project does not seem to be building the later, despite the folder below being a very explicit part of the include paths

{Project_ROOT}\mcu_device_support\headers\cmd

.temp_build_log.txt

All of the Sections warnings at the end indicate to me the cmd file is not being included correctly, but I do not know why.

I'll attach my build file and my project files in the zip below.

Debug_and_project_files.zip

What is even more confusing for me, is that this project (a new unit testing project) is a very close copy of another unit testing project I have, with the same cmd files, and as far as I can tell, all of the same build and include options. This older ut project builds fine without the sections warnings. 

So I am very confused about why this new ut project is failing to include the DSP2833x_Headers_nonBIOS.cmd file.

Please and thank you for any advice,
Neal

  • 0
    TI__Guru**** 486001 points

    Hello,

    I do not see any reference to "DSP2833x_Headers_nonBIOS.cmd" in the build output. It does not appear that it is part of the project. It is not in the zip that you attached, though I'm sure you intentionally did not provide the source in there.

    Can you show me a screenshot of the project in Project Explorer with the project folders expanded to show the DSP2833x_Headers_nonBIOS.cmd file? Basically I want to see DSP2833x_Headers_nonBIOS.cmd in the Project Explorer.

    Thanks

    ki

  • 0 in reply to Ki
    Prodigy 100 points

    Here's my project setup.

    In the build outputs, all the references to {Project_ROOT}\mcu_device_support\headers\cmd  are the location as shown in the image.

    Thank you for any advice.
    I'm not sure why we would see the cmd file in the built output, I don't see  F28335_Link.cmd  in there either?

    However, I'm confident it is using my custom F28335_Link.cmd file, because the map file matches it. 

  • +1 in reply to Neal OHara
    TI__Guru**** 486001 points

    I see that "mcu_device_support" has some file.folder specific options. What are they?

    Neal OHara said:
    I don't see  F28335_Link.cmd  in there either?

    You can see your full linker options in the "ccsLinker.opt" file in the "Debug (plain output)" subfolder. If you open the file, you will see it referenced twoards the end.

    Thanks

    ki

  • 0 in reply to Ki
    Prodigy 100 points

    Thank you, that folder diff was the issue.
    There was weirdness with when we created the dir and checkout that made CCS think that folder had differences, but it really should not have.
    Doing a refresh on that folder checkout and reloading the cproject file so that folder did not have any local changes fixed my build issue.
    Not sure what CCS thought was different, but it shouldn't have.

    Thanks again for the advice.