Tool/software: Code Composer Studio
I don't believe this is a CCS issue, but I have no idea where else to post this.
I have spent a few HOURS trying to (unsuccessfully) get a basic project up and running within CCS. I have managed to get the empty_min project load and linked to the tirtos_builds release project and got the Launchpad LED to flash. Great. So now I want to write to the display, so I open the Display project and copy and paste the relevant source sections surrounding display init, etc. But now I get build errors about not being able to find the Display.h source file. I have attempted editing the source file paths manually, adding references to the "SimpleLink CC13x0 SDK" project and de-referencing the TI-RTOS for CC13XX and CC26XX project, just like the display reference project has. Clean and rebuild and now I get different issues.
From my perspective (new developer perspective), the CC1350 development experience is a frustrating mess. It seems that these example projects lack a unified vision for what a CC1350 project should look like. I have attempted several times to get started with projects using this environment and ultimately just give up and move on to other projects because I can't justify this level of trial-and-error experimentation. Would you please pass this feedback on to the documentation and source code sample teams to ask that they improve the new user experience by ensuring that all of the documentation and source projects reference an authoritative solution set to build from?