Please note: We are aware of an issue affecting replies on the Arm Community forums, which may not be loading as expected.
We apologize for any inconvenience and appreciate your patience while we investigate and work to resolve the issue.
Thank you for your understanding.
I am using uVision 5.43 with a csolution and associated cproj file from a vendor's example application. I open the solution using the Project Menu. I am able to build/program as normal, but now I want to add files to my project and start developing my own code. When I use Project->Manager, everything except the Pack Installer are grayed out.
Reading the Project Menu doc I linked above, I see a note saying "The project management capabilities are intentionally limited as explained below.". However, the limitations don't include that you can't add new files. I can manually edit the CMSIS project file and then the new file(s) will start showing up.
Strangely, if I don't edit the CMSIS project file, when I build, my new file still gets included.
Is this behavior expected, or a defect?
Initially, µVision only allowed loading of csolution projects for debugging (see Notes at the end of this page: https://developer.arm.com/documentation/101407/0543/User-Interface/Project-Menu-and-Commands?lang=en). In MDK version 5.40, a 'build' functionality (see release notes https://www.keil.com/update/relnotes/MDK540.htm) was added that basically uses the CMSIS Toolbox tools to build the project. This means that other restrictions still apply: