AR# 32191

Description

When I use CORE Generator and Synplify in my design, the ChipScope Cores are removed.

What is the problem? How can I work around this?

Solution

The issue in this situation is with the instantiation template generated in the <core_name>.veo. This does not specify the core as a module with the port width, input, output or inout. Synplify will trim out this kind of instantiation. For example:

chipscope_icon_v1_03_a instance_name (

.CONTROL0(CONTROL0)

);

To work around this issue, you can add attributes to the code generated in the <core_name>.veo and a module declaration. For example:

chipscope_icon_v1_03_a instance_name (

.CONTROL0(CONTROL0)

);

module chipscope_vio_v1_02_a (CLK, CONTROL, SYNC_OUT) /* synthesis syn_black_box syn_noprune=1 */;

input CLK;

inout [35 : 0] CONTROL;

output [2 : 0] SYNC_OUT;

endmodule

This issue is resolved in ChipScope Pro 11.2. CORE Generator will add appropriate attributes to the example HDL files.