Other Parts Discussed in Thread: SYSCONFIG, C2000WARE
Tool/software:
Build Error: Exception occurred calling scripting.addModule():
After revisiting my project a few weeks later, having had left it in a good working shape, upon trying to build it with a minor change of a value of the symbolic constant , the #define constant (changing the sampling window of the ADC Driver), I got this error:
Exception occurred calling scripting.addModule().
I undid the change. Same "Exception..." error. Then I used the same project which I had saved in another workspace (as a baseline), without any change. This one built fine. I decided to bring the target file from the other workspace (where it generated build the error) and compile it in the new workspace. For this reason, I had to change the name of the same target file in the new workspace and exclude it from build. It did not work, build error like above. I removed this transferred file from the workspace and included the original file (which was in the project folder but excluded from build, restoring its name and no other change). It generated the same error: Exception occurred calling scripting.addModule(). Basically, the new project structure is the same like before.
I noticed from e2e that a similar problem has been reported even before, but, I do not see that it was addressed at the root cause. It appears that the make utility automation is the culprit as it messes up the Project Dependencies irreversibly. Can somebody explain in detail this and how to avoid this ? Yeah, every once in a while uninstalling/reinstalling the CCS and the SDK works, but, it is still a tedious process and it does not explain this weird and invisible problem.
Thanks a lot,
Erol Nikocevic
