1/1 
|
opb2wb
by osquillar on Dec 17, 2008 |
osquillar
Posts: 4 Joined: Jul 14, 2008 Last seen: Jan 12, 2009 |
||
|
Hello all, I've unziped the opb_wb.tar file into the pcores folder in the
Xilinx EDK and I've been able to generate the netlist using XPS. I've tried to implement the desing into ISE but the following error appears. ERROR: NgdBuild:604 - logical block 'Inst_cpu_micro_blaze/opb2wb_0/opb2wb_0' 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 'spartan3e'. As I've added the line OPTION ARCH_SUPPORT = spartan3e to the mpd file but same result. The RTL schematic is correct and the opb2wb wrapper is connected to the OPB bus signals correctly. Any idea about this issue?. Kindest Regards Oscar |
|||
|
opb2wb
by phs on Dec 19, 2008 |
phs
Posts: 1 Joined: Nov 6, 2011 Last seen: Dec 16, 2011 |
||
|
is your PAO file correct?
You have to list all entities there.
----- Original Message -----
From: osquillar at terra.esosquillar at t...>
To:
Date: Wed Dec 17 14:38:31 CET 2008
Subject: [oc] opb2wb
Hello all, I've unziped the opb_wb.tar file into the pcores folder
in the Xilinx EDK and I've been able to generate the netlist using XPS. I've tried to implement the desing into ISE but the following error appears. ERROR: NgdBuild:604 - logical block 'Inst_cpu_micro_blaze/opb2wb_0/opb2wb_0' 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 'spartan3e'. As I've added the line OPTION ARCH_SUPPORT = spartan3e to the mpd file but same result. The RTL schematic is correct and the opb2wb wrapper is connected to the OPB bus signals correctly. Any idea about this issue?. Kindest Regards Oscar |
|||
|
opb2wb
by osquillar on Dec 21, 2008 |
osquillar
Posts: 4 Joined: Jul 14, 2008 Last seen: Jan 12, 2009 |
||
|
Hello,
My PAO file looks like this
lib opb2wb_v1_00_a opb2wb
----- Original Message -----
From: phs at gmx.netphs at g...>
To:
Date: Fri Dec 19 21:34:29 CET 2008
Subject: [oc] opb2wb
is your PAO file correct?
You have to list all entities there.
----- Original Message -----
From: osquillar at terra.es
To:
Date: Wed Dec 17 14:38:31 CET 2008
Subject: [oc] opb2wb
> Hello all, I've unziped the opb_wb.tar file into the pcores
folder
> in the
> Xilinx EDK and I've been able to generate the netlist using XPS.
> I've
> tried to implement the desing into ISE but the following error > appears. > ERROR: NgdBuild:604 - logical > block 'Inst_cpu_micro_blaze/opb2wb_0/opb2wb_0' 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 'spartan3e'. > As I've added the line OPTION ARCH_SUPPORT = spartan3e > to the mpd file but same result. > The RTL schematic is correct and the opb2wb wrapper is connected to
> the OPB bus signals correctly.
> Any idea about this issue?. > Kindest Regards > Oscar > > |
|||
|
opb2wb
by osquillar on Jan 12, 2009 |
osquillar
Posts: 4 Joined: Jul 14, 2008 Last seen: Jan 12, 2009 |
||
|
Hello psh, the pao file was right, at the end I could insert the opb2wb
controller in my system but renaming the opb2wb_shell.v file to
opb2wb.v. After that change, there Xilinx EDK create the periperhal
without any problem
----- Original Message -----
From: phs at gmx.netphs at g...>
To:
Date: Fri Dec 19 21:34:29 CET 2008
Subject: [oc] opb2wb
is your PAO file correct?
You have to list all entities there.
----- Original Message -----
From: osquillar at terra.es
To:
Date: Wed Dec 17 14:38:31 CET 2008
Subject: [oc] opb2wb
> Hello all, I've unziped the opb_wb.tar file into the pcores
folder
> in the
> Xilinx EDK and I've been able to generate the netlist using XPS.
> I've
> tried to implement the desing into ISE but the following error > appears. > ERROR: NgdBuild:604 - logical > block 'Inst_cpu_micro_blaze/opb2wb_0/opb2wb_0' 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 'spartan3e'. > As I've added the line OPTION ARCH_SUPPORT = spartan3e > to the mpd file but same result. > The RTL schematic is correct and the opb2wb wrapper is connected to
> the OPB bus signals correctly.
> Any idea about this issue?. > Kindest Regards > Oscar > > |
|||
1/1