^

AR# 34778 12.1 EDK - "ERROR:EDK:1550 - cannot find MPD for the pcore "core_name_v1_01_a" in any of the repositories"

Why am I getting errors about my core's MPD file not being found?

I have a global repository located on a network drive. When I try to connect with XMD, errors similar to the following occur:

"ERROR: EDK:1550 - ...- cannot find MPD for the pcore "core_name_v1_01_a" in any of the repositories.
ERROR: EDK: 1552 - ... - cannot find MPD for the pcore
ERROR: EDK: 2185 - problem reading in the XMP file
ERROR: EDK: 3305 - Conversion to XML failed."

There are a number of issues related to this problem:

1. The search path to the network drive is being passed improperly.

- To work around this issue, put your global repository on a local drive, or run XMD via command line from a DOS or Xbash shell:

xmd -xmp system.xmp -opt etc/<xmd_opt_file>.opt

This problem is fixed in version 12.2.

2. Your design is an EDK system instantiated in an ISE project.

- When an EDK project is instantiated in an ISE project, the Revup Wizard to change your core from an older revision to the highest minor revision does not run. To work around this problem, open your XPS project outside of ISE software and let the Revup Wizard migrate necessary cores.

3. Your design contains an obsoleted version of the core but the Revup Wizard is not selecting a valid newer minor revision of the core in favor of alerting you to a newer major version of the core. The Revup Wizard cannot automatically migrate to a new major version of the core.

- To work around this problem, you will have to hand edit the MHS file, replacing the version number of the problem core with a valid, newer version of the core. A valid newer version of the core is any core version greater than the core's current version, as long as the major version number is the same. For example, the MPMC core has versions mpmc_v5_02_a, mpmc_v5_03_a, mpmc_v5_04_a and mpmc_v6_00_a. Versions mpmc_v5_02_a, mpmc_v5_03_a, mpmc_v5_04_a will be drop in compatible because the major version number, 5, is the same whereas mpmc_v6_00_a is not compatible.

4. Your design contains an obsoleted version of a core that has been completely removed from the provided repository. This recently happened with most of the OPB cores.

- When this happens you will need to make a local copy of the cores from an older version of the EDK tools. You may need to make changes to the MPD files in order for the localization to work. Cores that are encrypted cannot be made local so there is not a forward migration plan. To read more about the MPD format please see the "Platform Specification Format Reference Manual."
AR# 34778
Date Created 03/16/2010
Last Updated 07/13/2010
Status Active
Type
Tools
  • EDK - 11.1
  • EDK - 11.2
  • EDK - 11.3
  • More
  • EDK - 11.4
  • EDK - 11.5
  • EDK - 12.1
  • Less
IP
  • XPS LL TEMAC
Feed Back