Great question, it reminded me…
The M4 clock settings take over. And there are clock settings that can brick the module, however, we have included a delay of 1.5 seconds before the “main” starts. This delay is located in:
This Delay is added automatically when you build the project in PSoC Creator, and you should remove it in the release version. The delay is put above Clock_Init on purpose!
If there is no delay and you play with different frequencies, and brick the module, there will be no time for your programer to accquire the module, and reprogram it to unbrick it. With the delay, there is 1.5s delay after restart, before it gets bricked, so the programmer can aquire it.
Your project may not have the new “CoreStripper” that automatically adds this functionality. You can download the “new” examples from our github and just replace the CoreStripper.exe in your project, with the new CoreStripper found in the new project on github.
Alternatevly, if you dont want it to create the delay all the time, you can add the delay yourself in the same location, and use the old CoreStripper, although we do not recommend it.
Feel free to mess around with the clocks as long as there is the Delay before Clock_Init