OpenCores
URL https://opencores.org/ocsvn/socgen/socgen/trunk

Subversion Repositories socgen

[/] [socgen/] [trunk/] [Projects/] [opencores.org/] [wishbone/] [busDefs/] [abstractors/] [wb_b.2_rtl.xml] - Blame information for rev 135

Details | Compare with Previous | View Log

Line No. Rev Author Line
1 131 jt_eaton
2
30
 
31 135 jt_eaton
32
xmlns:ipxact="http://www.accellera.org/XMLSchema/IPXACT/1685-2014"
33 131 jt_eaton
xmlns:socgen="http://opencores.org"
34
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
35 135 jt_eaton
xsi:schemaLocation="http://www.accellera.org/XMLSchema/IPXACT/1685-2014
36
http://www.accellera.org/XMLSchema/IPXACT/1685-2014/index.xsd">
37 131 jt_eaton
 
38 135 jt_eaton
opencores.org
39
wishbone
40
wb
41
b.2_rtl
42 131 jt_eaton
 
43 135 jt_eaton
44
  
45 131 jt_eaton
 
46 135 jt_eaton
   
47
      clk
48
      The clock input coordinates all activities for the internal logic within the WISHBONE interconnect. All WISHBONE output signals are registered at the rising edge of clk. All WISHBONE input signals are stable before the rising edge of clk.
49
      
50
        
51
          true
52
        
53
        
54
          CLOCK
55
          required
56
          1
57
          out
58
        
59
        
60
          RESET
61
          optional
62
          1
63
          out
64
        
65
        
66
          required
67
          1
68
          in
69
        
70
        
71
          required
72
          1
73
          in
74
        
75
        true
76
      
77
    
78 131 jt_eaton
 
79 135 jt_eaton
    
80
      enable
81
      The enable input determines if a clk cycle should be acted upon or ignored for all operations including reset.
82
      
83
        
84
          CLOCK
85
          illegal
86
        
87
        
88
          ENABLE
89
          required
90
          1
91
          out
92
        
93
        
94
          optional
95
          1
96
          in
97
        
98
        
99
          optional
100
          1
101
          in
102
        
103
      
104
    
105 131 jt_eaton
 
106
 
107 135 jt_eaton
    
108
      rst
109
      The rst input forces the WISHBONE interface to restart. Furthermore, all internal self-starting state machines will be forced into an initial state. This signal only resets the WISHBONE interface. It is not required to reset other parts of an IP core (although it may be used that way).
110
      
111
        
112
          true
113
        
114
        
115
          CLOCK
116
          illegal
117
        
118
        
119
          ENABLE
120
          illegal
121
        
122
        
123
          RESET
124
          required
125
          1
126
          out
127
        
128
        
129
          required
130
          1
131
          in
132
        
133
        
134
          required
135
          1
136
          in
137
        
138
        true
139
      
140
    
141 131 jt_eaton
 
142
 
143
 
144 135 jt_eaton
    
145
      adr
146
      The adr output array is used to pass a binary address. The higher array boundary is specific to the address width of the core, and the lower array boundary is determined by the data port size and granularity. For example the array size on a 32-bit data port with BYTE granularity is adr[n:2]. In some cases (such as FIFO interfaces) the array may not be present on the interface.
147
      
148
        
149
          true
150
        
151
        
152
          CLOCK
153
          illegal
154
        
155
        
156
          ENABLE
157
          illegal
158
        
159
        
160
          RESET
161
          illegal
162
        
163
        
164
          required
165
          out
166
        
167
        
168
          required
169
          in
170
        
171
      
172
    
173 131 jt_eaton
 
174
 
175
 
176 135 jt_eaton
    
177
      cyc
178
      The cycle output when asserted, indicates that a valid bus cycle is in progress. The signal is asserted for the duration of all bus cycles. For example, during a BLOCK transfer cycle there can be multiple data transfers. The signal is asserted during the first data transfer, and remains asserted until the last data transfer. The signal is useful for interfaces with multi-port interfaces (such as dual port memories). In these cases, the  signal requests use of a common bus from an arbiter.
179
      
180
        
181
          true
182
        
183
        
184
          CLOCK
185
          illegal
186
        
187
        
188
          ENABLE
189
          illegal
190
        
191
        
192
          RESET
193
          illegal
194
        
195
        
196
          required
197
          out
198
        
199
        
200
          required
201
          in
202
        
203
      
204
    
205 131 jt_eaton
 
206
 
207
 
208
 
209
 
210 135 jt_eaton
    
211
      wdata
212
      The data output array is used to pass binary data. The array boundaries are determined by the port size, with a maximum port size of 64-bits (e.g. wdata[63:0].Also see the rdata[] and sel[] signal descriptions.
213
      
214
        
215
          CLOCK
216
          illegal
217
        
218
        
219
          ENABLE
220
          illegal
221
        
222
        
223
          RESET
224
          illegal
225
        
226
        
227
          required
228
          out
229
        
230
        
231
          required
232
          in
233
        
234
      
235
    
236 131 jt_eaton
 
237 135 jt_eaton
    
238
      rdata
239
      The data input array is used to pass binary data. The array boundaries are determined by the port size, with a maximum port size of 64-bits (e.g. rdata[63:0]. Also see the wdata[] and sel[] signal descriptions.
240
      
241
        
242
          CLOCK
243
          illegal
244
        
245
        
246
          ENABLE
247
          illegal
248
        
249
        
250
          RESET
251
          illegal
252
        
253
        
254
          required
255
          in
256
        
257
        
258
          required
259
          out
260
        
261
      
262
    
263 131 jt_eaton
 
264
 
265 135 jt_eaton
   
266
      ack
267
      The acknowledge input  when asserted, indicates the normal termination of a bus cycle. Also see the err and rty signal descriptions.
268
      
269
        
270
          CLOCK
271
          illegal
272
        
273
        
274
          ENABLE
275
          illegal
276
        
277
        
278
          RESET
279
          illegal
280
        
281
        
282
          required
283
          in
284
        
285
        
286
          required
287
          out
288
        
289
      
290
    
291 131 jt_eaton
 
292
 
293 135 jt_eaton
   
294
      err
295
      The error input indicates an abnormal cycle termination. The source of the error, and the response generated by the MASTER is defined by the IP core supplier. Also see the ack and rty signal descriptions.
296
      
297
        
298
          CLOCK
299
          illegal
300
        
301
        
302
          ENABLE
303
          illegal
304
        
305
        
306
          RESET
307
          illegal
308
        
309
        
310
          required
311
          in
312
        
313
        
314
          required
315
          out
316
        
317
      
318
    
319 131 jt_eaton
 
320
 
321 135 jt_eaton
   
322
      rty
323
      The retry input indicates that the interface is not ready to accept or send data, and that the cycle should be retried. When and how the cycle is retried is defined by the IP core supplier. Also see the ack and err signal descriptions.
324
      
325
        
326
          CLOCK
327
          illegal
328
        
329
        
330
          ENABLE
331
          illegal
332
        
333
        
334
          RESET
335
          illegal
336
        
337
        
338
          required
339
          in
340
        
341
        
342
          required
343
          out
344
        
345
      
346
    
347 131 jt_eaton
 
348
 
349
 
350
 
351
 
352
 
353 135 jt_eaton
   
354
      sel
355
      The select output array indicates where valid data is expected on the rdata signal array during READ cycles, and where it is placed on the wdata signal array during WRITE cycles. The array boundaries are determined by the granularity of a port. For example, if 8-bit granularity is used on a 64-bit port, then there would be an array of eight select signals with boundaries of sel[7:0]. Each individual select signal correlates to one of eight active bytes on the 64-bit data port. For more information about sel, please refer to the data organization section in Chapter 3 of this specification. Also see the rdata[], wdata[] and stb signal descriptions.
356
      
357
        
358
          CLOCK
359
          illegal
360
        
361
        
362
          ENABLE
363
          illegal
364
        
365
        
366
          RESET
367
          illegal
368
        
369
        
370
          required
371
          out
372
        
373
        
374
          required
375
          in
376
        
377
      
378
    
379 131 jt_eaton
 
380
 
381
 
382
 
383 135 jt_eaton
   
384
      stb
385
      The strobe output indicates a valid data transfer cycle. It is used to qualify various other signals on the interface such as sel[]. The SLAVE asserts either the ack, err  or rty signals in response to every assertion of the stb signal.
386
      
387
        
388
          CLOCK
389
          illegal
390
        
391
        
392
          ENABLE
393
          illegal
394
        
395
        
396
          RESET
397
          illegal
398
        
399
        
400
          required
401
          out
402
        
403
        
404
          required
405
          in
406
        
407
      
408
    
409 131 jt_eaton
 
410
 
411 135 jt_eaton
   
412
      tagn_i
413
      The tag input(s)  are user defined, and are used with either MASTER or SLAVE interfaces. ā€˜Nā€™ in this signal name refers to a tag number because multiple tags may be used (e.g. TAG_I[3]). Tag inputs are used whenever an IP core needs specific information from the interconnection. For example, a MASTER can be designed to monitor the state of a FIFO.
414
      
415
        
416
          CLOCK
417
          illegal
418
        
419
        
420
          ENABLE
421
          illegal
422
        
423
        
424
          RESET
425
          illegal
426
        
427
        
428
          required
429
          in
430
        
431
        
432
          required
433
          out
434
        
435
      
436
    
437 131 jt_eaton
 
438
 
439 135 jt_eaton
   
440
      tagn_o
441
      The tag output(s) are user defined, and are used with either MASTER or SLAVE interfaces. For example, the tag output(s) can be used to indicate the type of data transfer in progress. Furthermore, ā€˜Nā€™ in this signal name refers to a tag number because multiple tags may be used. For example, tagn_o[1] may indicate a valid data transfer cycle, tagn_o[2] may indicate an interrupt acknowledge cycle and so on. The exact meaning of each tag is defined by the IP core provider in the WISHBONE DATASHEET.
442
      
443
        
444
          CLOCK
445
          illegal
446
        
447
        
448
          ENABLE
449
          illegal
450
        
451
        
452
          RESET
453
          illegal
454
        
455
        
456
          required
457
          out
458
        
459
        
460
          required
461
          in
462
        
463
      
464
    
465 131 jt_eaton
 
466
 
467
 
468 135 jt_eaton
    
469
      we
470
      The write enable output indicates whether the current local bus cycle is a READ or WRITE cycle. The signal is negated during READ cycles, and is asserted during WRITE cycles.
471
      
472
        
473
          true
474
        
475
        
476
          CLOCK
477
          illegal
478
        
479
        
480
          ENABLE
481
          illegal
482
        
483
        
484
          RESET
485
          illegal
486
        
487
        
488
          required
489
          out
490
        
491
        
492
          required
493
          in
494
        
495
      
496
    
497 131 jt_eaton
 
498
 
499
 
500
 
501 135 jt_eaton
  
502
503 131 jt_eaton
 
504
 
505
 
506
 
507
 
508
 
509
 
510
 
511
 

powered by: WebSVN 2.1.0

© copyright 1999-2024 OpenCores.org, equivalent to Oliscience, all rights reserved. OpenCores®, registered trademark.