Hello all:)

I am running a design in edk 6.1 version. and comes up with

" Makefile cannot be saved to run process. Please ensure IPs in MHS
file point to the right MPDs".

 The MHS doesnt contain info about MPDs..

What i have to do on that?

regards

On Oct 17, 4:29 am, xenix <last...@gmail.com> wrote:
> Hello all:)
>
> I am running a design in edk 6.1 version. and comes up with
>
> " Makefile cannot be saved to run process. Please ensure IPs in MHS
> file point to the right MPDs".
>
>  The MHS doesnt contain info about MPDs..
>
> What i have to do on that?
>
> regards

Actually, the MHS has ALL the info on the MPDs :).

Since the MHS file is the single repository for the IP being used to
create the system, each INSTNACE will have a corresponding MPD file.
The MPD file that matches to an INSTANCE is easily decipherable. Let's
take a look at an example:

BEGIN plb_central_dma
 PARAMETER INSTANCE = dma_plb
 PARAMETER HW_VER = 1.00.a
 PARAMETER C_BASEADDR = 0xDC000000
 PARAMETER C_HIGHADDR = 0xDC0000FF
 BUS_INTERFACE MSPLB = plb_1
 PORT IP2INTC_Irpt = dma_int
END

Now for this instance: dma_plb it's being mapped to a plb_central_dma
and that version number is 1.00.a. Therefore there will need to be a
directory:
plb_central_dma_1_00_a in one of the pcore directories (either global,
or project local). The format of that directory is:

\data
\doc
\hdl

In the data directory, there should be plb_central_dma_v2_1_0.mpd
file. (The v2_1_0 may change w/ EDK 6.1 since that's older than any of
the version I've used). The content of that mpd file will start with a
"BEGIN plb_central_dma". There may be #-comments before it, but the
important part is that name. That's how EDK correlates the MPD to the
core. And the version is correlated via pcore directory name.

Does that make sense?

-- Mike

Thanx Mike! :) :)
yes works fine now:)