
Running the SnapShot Debugger Chapter 4. Tasks
51 St i m u l i : out s t d l o g i c v e c t o r ( 3 5 downto 0 ) ;
52 R s t n out : out s t d l o g i c ;
53 Arm : out s t d l o g i c
54 ) ;
55 end componen t ;
56
57 component u s e r s l o g i c i s
58 p o r t ( c l k : in s t d l o g i c ;
59 r s t n : in s t d l o g i c ;
60 da ta o ut f r om b loc k : out s t d l o g i c v e c t o r (MNTR WIDTH−1 downto 0 ) ;
61 o p t i o n a l t e s t r s t n i n : i n s t d l o g i c ;
62 o p t i o n a l t e s t a r m i n : in s t d l o g i c ;
63 o p t i o n a l t e s t s t i m u l i i n : in st d l o g i c v e c t o r ( 3 5 downto 0 )
64 ) ;
65 end componen t ;
66 −−NOTE : I t i s not n e c e s sary to con nect the St i m u l i , Arm , and R s t n out to the user l o g i c .
67 −− These s i g n a l s may s a f e l y be l e f t f l o a t i n g , i f t h e use r only wants t o t r a c e e x i s t i n g
68 −− s i g n a l s , and not cause s p e c i f i c b ehav ior through t he debugger .
69
70 −− SIGNAL DECLARATIONS−−
71 s i g n a l u s e r d a t a t o m o n i t o r a n d t r i g g e r : s t d l o g i c v e c t o r (MNTR WIDTH−1 downto 0 ) ;
72 −− t h e se s i g n a l s w i l l be monitored i n SnapShot , with ( 7 1 downto 3 6 ) captured ,
73 −− and ( 3 5 downto 0 ) captu red and s en t to t r i g g e r −de t e c t o r b l o cks as t r i g g e r c h
74 s i g n a l s t i m u l i t o d u t : s t d l o g i c v e c t o r ( 3 5 downto 0 ) ;
75 −− provi des t e s t s t i m u l i t o u s e r l o g i c from SnapShot ; t h i s may s a f e l y be l e f t f l o a t i n g
76 s i g n a l r s t n o u t t o d u t : s t d l o g i c ;
77 −− in d i c a t e s SnapShot i s r e s e t t i n g ; t h i s may s a f e l y be l e f t f l o a t i n g
78 s i g n a l arm to dut : s t d l o g i c ;
79 −− in d i c a t e s SnapShot i s armed ( and has s t a r t e d t e s t i n g p a t t e r n s ) , s t i m u l i i s v a li d ;
80 −− t h i s may s a f e l y be l e f t f l o a t i n g
81
82
83 begin
84 −−MACRO INSTANTIATION−−
85 s n a p s h ot i n s t a n c e : ACX SNAP SHOT
86 ge n e r i c map ( MNTR WIDTH = > MNTR WIDTH ,
87 OUTPUTPIPELINING = > 3 ,
88 DUTNAME = > ” u s e r s l o g i c b l o c k i n s t a n c e ” )
89 p o r t map ( tck => tc k ,
90 t r s t n => t r s t n ,
91 tms => tms ,
92 t d i => td i ,
93 tdo => tdo ,
94 us r c l k => u s r c l k ,
95 Monitor ch = > u s e r d a t a t o mo n i t o r an d t r i g g e r ,
96 t r i g g e r c h = > u s e r d a t a t o m o n i t o r a n d t r i g g e r ( 3 5 downto 0 ) ,
97 St i m u li => s t i m u l i t o d u t ,
98 Rs t n o u t => r s t n o u t t o d u t ,
99 Arm => arm to d ut ) ;
100
101 u s e r s l o g i c b l o c k i n s t a n c e : u s e r s l o g i c
102 p o r t map ( c l k => u s r c l k ,
103 r s t n => u s r r s t n ,
104 d a t a o u t f r o m b l o ck => u s e r d a t a t o m o n i t o r a n d t r i g g e r ,
105 o p t i o n a l t e s t r s t n i n => r s t n o u t t o d u t ,
106 o p t i o n a l t e s t a r m i n => arm to dut ,
107 o p t i o n a l t e s t s t i m u l i i n = > s t i m u l i t o d u t ) ;
108 end arch ;
109 −−END VHDL EXAMPLE−−
Synthesis
After incorporating the SnapShot macro into the design, the user will be able to synthesize the design with
the Synplify-Pro or Precision synthesis tool. After synthesis, the generated netlist can be imported into ACE
to generate the FPGA programming file (bitstream).
Setting Up the Bitporter Pod Connection
The following section describes how to configure the SnapShot Debugger view for communication with
an already-connected Bitporter and an already-programmed Achronix device. For details on physically
connecting the Bitporter pod/cables, please see the Bitporter User Guide (UG004).
In the SnapShot Debugger view, under ”BitPorter Connection” either select Automatically Detect Pod or
Specify Pod Name to choose which already-connected Bitporter pod will be used to communicate with the
already-running design on the Achronix device.
289 http://www.achronix.com UG001 Rev. 5.0 - 5th December 2012
Comentarios a estos manuales