Many times Processor Expert is right. But not always: It is possible that Processor Expert is stuck on the error, and there seems no way out. But there is a trick to resolve it….
Typically the problem happens to me after changing the internal clock timings of the microcontroller. Then this has an impact on other components in the project:
In my case here, inspecting the chosen values show that everything is perfectly ok:
It does not happen always, but enough, and if it happens, it gets painful. Students in my class typically report me these kind of problems with ‘it went away when I restarted Eclipse’. There is a simpler workaround.
The trick is that Processor Expert can be forced to redo the setting verification. This happens when I
- open the project (this happens a well with opening a workspace (thus restarting Eclipse))
- enable the component in the project
So if I believe it is one of these bogus errors, I simple select the component and disable it with the context menu:
And then re-enable it again:
And voilà, the error disappeared:
If that does not help, then there is probably an error across multiple components. Then the easiest way is to close the project (menu Project > Close Project) and then re-open it again with the menu Project > Open Project.
While it is not good that Processor Expert seems to be stuck on a false/bogus error, at least closing and re-opening the component or project is an easy workaround (once I know about it). Without that, it would be necessary to switch the workspace or even restart Eclipse (which I avoid as takes some more time).
That particular problem has been reported. Until it gets fixed, the above workaround should do it.