UPGRADE YOUR BROWSER

We have detected your current browser version is not the latest one. Xilinx.com uses the latest web technologies to bring you the best online experience possible. Please upgrade to a Xilinx.com supported browser:Chrome, Firefox, Internet Explorer 11, Safari. Thank you!

cancel
Showing results for 
Search instead for 
Did you mean: 
Contributor
Contributor
8,648 Views
Registered: ‎11-18-2013

Tri Mode mac chipscope instantiation

Jump to solution

Hi,

I would like to use Virtex-6 Embedded Tri_mode Ethernet Mac Wrapeer version 2.3 IP core. Thare are some extarnal ports in examplke design top entity which are used to configure ethernet interface.

 

Because I dont have any switches on my custom board I would like to use chipscope ICON and VIO to drive inputs and read outputs.

 

The problem is that this core is generated in the command line script implement.sh:

 

#!/bin/sh

# Clean up the results directory
rm -rf results
mkdir -p results

echo 'Synthesizing example design with XST';
xst -ifn xst.scr
cp v6_emac_v2_3_example_design.ngc results/

# Copy the EDIF's generated by Coregen
echo 'Copying files from the netlist directory to the results directory'
cp ../../v6_emac_v2_3.ngc results/

echo 'Copying files from constraints directory to results directory'
cp ../example_design/v6_emac_v2_3_example_design.ucf results/

cd results

echo 'Running ngdbuild'
ngdbuild -uc v6_emac_v2_3_example_design.ucf v6_emac_v2_3_example_design.ngc v6_emac_v2_3_example_design.ngd

echo 'Running map'
map -detail -ol high v6_emac_v2_3_example_design -o mapped.ncd

echo 'Running par'
par -ol high mapped.ncd routed.ncd mapped.pcf

echo 'Running trce'
trce -e 10 routed -o routed mapped.pcf

echo 'Running design through bitgen'
bitgen -w routed routed mapped.pcf

echo 'Running netgen to create gate level VHDL model'
netgen -ofmt vhdl -sim -dir . -pcf mapped.pcf -tm v6_emac_v2_3_example_design -w routed.ncd routed.vhd

What I added to above script( Before ngdbuild command) is this two lines:

ngdbuild -uc chipscope_vio.ucf  chipscope_vio.ngc chipscope_vio.ngd
ngdbuild -uc chipscope_icon.ucf chipscope_icon.ngc chipscope_icon.ngd

 

Chipscope modules are instantiated in v6_emac_v2_3_example_design.vhd file like that:

VIO_0: chipscope_vio
  port map (
    CONTROL => CONTROL,
    ASYNC_IN => ASYNC_IN,
    ASYNC_OUT => ASYNC_OUT);
ICON_0: chipscope_icon
  port map (
    CONTROL0 => CONTROL);

 

During execution of script following warnings are shown:

WARNING:NgdBuild:452 - logical net 'CONTROL<35>' has no driver
WARNING:NgdBuild:452 - logical net 'CONTROL<34>' has no driver
WARNING:NgdBuild:452 - logical net 'CONTROL<33>' has no driver
WARNING:NgdBuild:452 - logical net 'CONTROL<32>' has no driver
WARNING:NgdBuild:452 - logical net 'CONTROL<31>' has no driver
WARNING:NgdBuild:452 - logical net 'CONTROL<30>' has no driver
WARNING:NgdBuild:452 - logical net 'CONTROL<29>' has no driver
WARNING:NgdBuild:452 - logical net 'CONTROL<28>' has no driver
WARNING:NgdBuild:452 - logical net 'CONTROL<27>' has no driver
WARNING:NgdBuild:452 - logical net 'CONTROL<26>' has no driver
WARNING:NgdBuild:452 - logical net 'CONTROL<25>' has no driver
WARNING:NgdBuild:452 - logical net 'CONTROL<24>' has no driver
WARNING:NgdBuild:452 - logical net 'CONTROL<23>' has no driver
WARNING:NgdBuild:452 - logical net 'CONTROL<22>' has no driver
WARNING:NgdBuild:452 - logical net 'CONTROL<21>' has no driver
WARNING:NgdBuild:452 - logical net 'CONTROL<20>' has no driver
WARNING:NgdBuild:452 - logical net 'CONTROL<19>' has no driver
WARNING:NgdBuild:452 - logical net 'CONTROL<18>' has no driver
WARNING:NgdBuild:452 - logical net 'CONTROL<17>' has no driver
WARNING:NgdBuild:452 - logical net 'CONTROL<16>' has no driver
WARNING:NgdBuild:452 - logical net 'CONTROL<15>' has no driver
WARNING:NgdBuild:452 - logical net 'CONTROL<14>' has no driver
WARNING:NgdBuild:452 - logical net 'CONTROL<13>' has no driver
WARNING:NgdBuild:452 - logical net 'CONTROL<12>' has no driver
WARNING:NgdBuild:452 - logical net 'CONTROL<11>' has no driver
WARNING:NgdBuild:452 - logical net 'CONTROL<10>' has no driver
WARNING:NgdBuild:452 - logical net 'CONTROL<9>' has no driver
WARNING:NgdBuild:452 - logical net 'CONTROL<8>' has no driver
WARNING:NgdBuild:452 - logical net 'CONTROL<7>' has no driver
WARNING:NgdBuild:452 - logical net 'CONTROL<6>' has no driver
WARNING:NgdBuild:452 - logical net 'CONTROL<5>' has no driver
WARNING:NgdBuild:452 - logical net 'CONTROL<4>' has no driver
WARNING:NgdBuild:452 - logical net 'CONTROL<2>' has no driver
WARNING:NgdBuild:452 - logical net 'CONTROL<1>' has no driver
WARNING:NgdBuild:452 - logical net 'CONTROL<0>' has no driver

 

WARNING:Par:288 - The signal VIO_0/U0/I_VIO/UPDATE<16> has no load.  PAR will not attempt to route this signal.
WARNING:Par:288 - The signal VIO_0/U0/I_VIO/UPDATE<17> has no load.  PAR will not attempt to route this signal.
WARNING:Par:288 - The signal VIO_0/U0/I_VIO/UPDATE<18> has no load.  PAR will not attempt to route this signal.
WARNING:Par:288 - The signal VIO_0/U0/I_VIO/UPDATE<19> has no load.  PAR will not attempt to route this signal.
WARNING:Par:288 - The signal VIO_0/U0/I_VIO/UPDATE<12> has no load.  PAR will not attempt to route this signal.
WARNING:Par:288 - The signal VIO_0/U0/I_VIO/UPDATE<13> has no load.  PAR will not attempt to route this signal.
WARNING:Par:288 - The signal VIO_0/U0/I_VIO/UPDATE<14> has no load.  PAR will not attempt to route this signal.
WARNING:Par:288 - The signal VIO_0/U0/I_VIO/UPDATE<15> has no load.  PAR will not attempt to route this signal.
WARNING:Par:288 - The signal VIO_0/U0/I_VIO/UPDATE<0> has no load.  PAR will not attempt to route this signal.
WARNING:Par:288 - The signal VIO_0/U0/I_VIO/UPDATE<1> has no load.  PAR will not attempt to route this signal.
WARNING:Par:288 - The signal VIO_0/U0/I_VIO/UPDATE<2> has no load.  PAR will not attempt to route this signal.
WARNING:Par:288 - The signal VIO_0/U0/I_VIO/UPDATE<3> has no load.  PAR will not attempt to route this signal.
WARNING:Par:288 - The signal VIO_0/U0/I_VIO/UPDATE<8> has no load.  PAR will not attempt to route this signal.
WARNING:Par:288 - The signal VIO_0/U0/I_VIO/UPDATE<9> has no load.  PAR will not attempt to route this signal.
WARNING:Par:288 - The signal VIO_0/U0/I_VIO/UPDATE<10> has no load.  PAR will not attempt to route this signal.
WARNING:Par:288 - The signal VIO_0/U0/I_VIO/UPDATE<11> has no load.  PAR will not attempt to route this signal.
WARNING:Par:288 - The signal VIO_0/U0/I_VIO/UPDATE<4> has no load.  PAR will not attempt to route this signal.
WARNING:Par:288 - The signal VIO_0/U0/I_VIO/UPDATE<5> has no load.  PAR will not attempt to route this signal.
WARNING:Par:288 - The signal VIO_0/U0/I_VIO/UPDATE<6> has no load.  PAR will not attempt to route this signal.
WARNING:Par:288 - The signal VIO_0/U0/I_VIO/UPDATE<7> has no load.  PAR will not attempt to route this signal.

 

The script finish work without errors.

The results after downloading bitstream to FPGA is that ChipsScope PRO detetects ICON core with VIO console and properly shows ASYNC_IN signals. But when I tried to drive the ASYNC_OUT its not changing at all. Ive checked it by adding signal to ASYNC_IN(chip_test_out) and ASYNC_OUT(chip_test_in) and connect them:

 

chip_test_out <= chip_test_in; 

 

And toggling  chip_test_in doesnt affect chip_test_out.

 

How to add chipscope cores to project correctly?

 

0 Kudos
1 Solution

Accepted Solutions
Contributor
Contributor
15,842 Views
Registered: ‎11-18-2013

Re: Tri Mode mac chipscope instantiation

Jump to solution

So...

'<=' operator does have a direction

I needed to use:

glbl_rst    <= ASYNC_OUT(0);


instead of:

ASYNC_OUT(0) <=glbl_rst;

 

What a shame!

0 Kudos
1 Reply
Contributor
Contributor
15,843 Views
Registered: ‎11-18-2013

Re: Tri Mode mac chipscope instantiation

Jump to solution

So...

'<=' operator does have a direction

I needed to use:

glbl_rst    <= ASYNC_OUT(0);


instead of:

ASYNC_OUT(0) <=glbl_rst;

 

What a shame!

0 Kudos