Over a million developers have joined DZone.

Resolving Processor Expert Bogus Errors

· Performance Zone

Discover 50 of the latest mobile performance statistics with the Ultimate Guide to Digital Experience Monitoring, brought to you in partnership with Catchpoint.

Sometimes, especially after making some clock/timing changes in Processor Expert, I have an error showing up in the Processor Expert components:

Processor Expert Components with Errors

Processor Expert Components with Errors

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:

Error about timing?

Error about timing?

In my case here, inspecting the chosen values show that everything is perfectly ok:

Bogus Error in Timing Settings

Bogus Error in Timing Settings

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:

Disabling Component

Disabling Component

And then re-enable it again:

Re-Enabling Component Again

Re-Enabling Component Again

And voilà, the error disappeared:

Error disappeared

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.

Happy Fixing :-)

Is your APM strategy broken? This ebook explores the latest in Gartner research to help you learn how to close the end-user experience gap in APM, brought to you in partnership with Catchpoint.


Published at DZone with permission of Erich Styger, DZone MVB. See the original article here.

Opinions expressed by DZone contributors are their own.

The best of DZone straight to your inbox.

Please provide a valid email address.

Thanks for subscribing!

Awesome! Check your inbox to verify your email so you can start receiving the latest in tech news and resources.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}