Sign in

username:

password:



Not a member?

Search Comp.Arch.FPGA



Search tips

fpga by Keywords

Altera | ASIC | CPLD | Cyclone | DCM | DDR | DSP | Ethernet | ISE | JTAG | Linux | LVDS | Microblaze | ML310 | Modelsim | NIOS | OPB | PCI | Quartus | RocketIO | SDRAM | Spartan | Spartan3 | SRAM | Stratix | Verilog | VHDL | Virtex | Virtex-4 | Virtex-II | Xilinx | XST

Ads

See Also

DSPEmbedded SystemsElectronics

Comp.Arch.FPGA | chipscope on opb bus

There are 2 messages in this thread.

You are currently looking at messages 0 to 2.

chipscope on opb bus - 2005-07-26 10:39:00

Hello, i'm using XPS to build a system based on a
Microblaze cpu, and i
would like to add a Chipscope OPB IBA to analyse OPB . I connect it
through my mb_opb but i've got this error

NgdBuild:455 - logical net 'ilmb_LMB_BE<0>' has multiple driver(s):
pin G on block XST_GND with type GND,
pin O on block
chipscope_opb_iba_0/chipscope_opb_iba_0/i_chipscope_opb_iba_0/chipscope_opb_i
ba_0/i_no_d/u_ila/u_dout with type LUT3

does anyone know why my chipscope is driving a LMB net although i just
want to connect it to OPB bus

thanks in advance
cedric.

______________________________
Join the blogging team on FPGARelated.com and earn rewards! Details Here.



Re: chipscope on opb bus - Antti Lukats - 2005-07-26 10:49:00

<b...@hotmail.com> schrieb im
Newsbeitrag
news:1...@g43g2000cwa.googlegroups.com...
> Hello, i'm using XPS to build a system based on a Microblaze cpu, and i
> would like to add a Chipscope OPB IBA to analyse OPB . I connect it
> through my mb_opb but i've got this error
>
> NgdBuild:455 - logical net 'ilmb_LMB_BE<0>' has multiple driver(s):
> pin G on block XST_GND with type GND,
> pin O on block
>
chipscope_opb_iba_0/chipscope_opb_iba_0/i_chipscope_opb_iba_0/chipscope_opb_
i
> ba_0/i_no_d/u_ila/u_dout with type LUT3
>
> does anyone know why my chipscope is driving a LMB net although i just
> want to connect it to OPB bus
>
> thanks in advance
> cedric.
>

its not driving LMB bus actually - there is mockup with the chipscope cores,
so 2 signals from unrelated modules that both are logic ground are seen as
being connected together and that makes the tools think there is multiply
driver conflict.

this problem happens sometimes. im not sure how to avoid this.

Antti