Re: BSP Variables
Oh don't do that.
Start with a fresh project, and enable only what you need.
If you need to experiment with code from BSP or from sample code under MHC-Apps-GenerateAppCode then do in a separate test project, then copy over only what you need.
I've seen that there is some "automatic enabling" by BSP and by the MHC-Apps-GenerateAppCode.
Best to find out what is really happening else it will come back to haunt you.
I use "Beyond Compare" to compare my working project versus experimental projects to see what MHC has done to code and config files, it allows comparing whole project trees (though folders need to be same names if you don't want to step through them). Doing this can be useful (I installed harmony on P: for cleaner backups):
- P:\microchip\harmony\v2_06\apps = Microchip sample projects
- P:\microchip\harmony\v2_06\mine = My own projects
- P:\microchip\harmony\v2_06\mineA (\mineB...) = copies of my own projects, but with other things enabled for experiments, such as BSP or MHC-Apps-Generate... (allows keeping same project names for Beyond Compare)
I recommend setting these as Ready Only in Harmony to prevent mistaken changes during editing:
- _HarmonyReadonly=framework, bsp, third_party, bin(libs)
Notes from a previous post: