|
Message
From: Kevin Somervill<k.m.somervill@l...>
Date: Fri Jan 20 17:51:59 CET 2006
Subject: [oc] problem with opb2wb core
Hello,
| I have downloaded the OPB2WB file and unziped it in
| ../EDK/HW/C:\EDK\hw\XilinxProcessorIPLib\pcores directory.
| Then I included the opb2wb peripheral in my micoblaze
| project, and set it correctly (I think !!!!) I also tryed to
| create the netlist but it was an missmatch error between the
| mpd file and the .v file : one time the rst signal is
| named "rst" and in the other "opb_rst". Why??? It is realy
| an error?????
Yes.
| I look in the netlist file and the name is "rst".
If the EDK is complaining about the signal, then you installed the core
correctly. What you are seeing is a bug that I found in '04? You can go
through and make the name the same in all places and it will work fine. I
sent a fix to Rudolf but apparently he never checked it in. Oh well.
| if I change in the mpd file "opb_rst" to "rst" the netlist
| succed and is created.
|
| Then when I integrate my micoblaze project in my Xilinx VHDL
| project and I do a synthesis it will work but when I wanted
| to translate it I have an error:
|
| ERROR:NgdBuild:604 - logical block
| 'Inst_micro_blaze/opb2wb_rs422/opb2wb_rs422'
| with type 'opb2wb' could not be resolved. A pin name
| misspelling can cause
| this, a missing edif or ngc file, or the misspelling of a
| type name. Symbol
| 'opb2wb' is not supported in target 'spartan3'.
Does the MPD contain a line like
OPTION ARCH_SUPPORT =
spartan2:spartan2e:spartan3:virtex:virtex2:virtex2p:virtexe
I believe I had to add this as well.
./ks
|
 |
Browse
