Fixing the Morpho Core Exception

After running the MQX batch installation file for MCU10.2 (see MQX Eclipse Working Sets) I had an error dialog when I inspected my debug/run configuration:

“Error loading data producer reader: com.freescale.morpho.core.CWException: The function “getServiceByContractID” returned an error condition (0x80040154)”

Error loading data producer reader

Error loading data producer reader

Additionally the .metadata .log file reported:

!ENTRY 4 120 2012-05-21 20:56:09.760
!MESSAGE The function "getServiceByContractID" returned an error condition  (0x80040154)

I had the same dialog a while back when I was moving around my Eclipse framework installation. At that time, I had found the solution in an email list, but forgotten about it. Until today, when I had that dialog again. So I better post it for everyone :-).

The error happens if .dat files point to wrong file locations to load additional software components. So this could happen if I copy around my Eclipse installation, or if for other reasons the .dat files do not get updated properly.

To solve the problem:

  1. Close Eclipse
  2. Delete the *.dat files in “C:\Freescale\CW MCU v10.2\eclipse\plugins\com.freescale.morpho.core_7.0.0.106089-201110132018\xpcom\bin\components”
  3. Restart Eclipse

Note: the path to “com.freescale.morpho.core_7.0.0.*” depends on the installation path and version of CodeWarrior.

With deleting the *.dat (in my case compreg.dat and xpti.dat) this, the problem goes away.
Another (easier) solution is to run the following batch file inside the CodeWarrior installation:

<installation path>\eclipse\register_xpcom.bat

However, this seems not to solve the case if I move around my layout, but works for me for the MQX installation thing.

Happy Morphing 🙂

6 thoughts on “Fixing the Morpho Core Exception

  1. Pingback: Bit Banging I2C | MCU on Eclipse

    • You are more than welcome. I was running twice into that problem, so I thought it is worthwhile to post the solution. I know that the CodeWarrior team is working on a solution so that fix will not be needed in the future.


  2. Excellent fix, been fighting with this issue then remembered reading about it in this blog. Your blog is very appreciated.


What do you think?

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

This site uses Akismet to reduce spam. Learn how your comment data is processed.