Xilinx Trademarks and Copyright Information
Xilinx is disclosing this user guide, manual, release note, and/or specification (the “Documentation”) to yousolely for use in the development of designs to operate with Xilinx hardware devices. You may not reproduce,distribute, republish, download, display, post, or transmit the Documentation in any form or by any meansincluding, but not limited to, electronic, mechanical, photocopying, recording, or otherwise, without the priorwritten consent of Xilinx. Xilinx expressly disclaims any liability arising out of your use of the Documentation.Xilinx reserves the right, at its sole discretion, to change the Documentation without notice at any time. Xilinxassumes no obligation to correct any errors contained in the Documentation, or to advise you of any correctionsor updates. Xilinx expressly disclaims any liability in connection with technical support or assistance that may beprovided to you in connection with the Information.
THE DOCUMENTATION IS DISCLOSED TO YOU “AS-IS” WITH NOWARRANTY OF ANY KIND. XILINXMAKES NO OTHER WARRANTIES, WHETHER EXPRESS, IMPLIED, OR STATUTORY, REGARDINGTHE DOCUMENTATION, INCLUDING ANY WARRANTIES OF MERCHANTABILITY, FITNESS FOR APARTICULAR PURPOSE, OR NONINFRINGEMENT OF THIRD-PARTY RIGHTS. IN NO EVENT WILLXILINX BE LIABLE FOR ANY CONSEQUENTIAL, INDIRECT, EXEMPLARY, SPECIAL, OR INCIDENTALDAMAGES, INCLUDING ANY LOSS OF DATA OR LOST PROFITS, ARISING FROM YOUR USE OF THEDOCUMENTATION.
© Copyright 2002-2009 Xilinx Inc. All Rights Reserved. XILINX, the Xilinx logo, the Brand Window and otherdesignated brands included herein are trademarks of Xilinx, Inc. All other trademarks are the property oftheir respective owners.
CPLD Libraries Guide2 www.xilinx.com UG606 (v 11.3) September 16, 2009
Table of ContentsXilinx Trademarks and Copyright Information......................................................................................... 2
Chapter 1 About this Guide......................................................................................................................... 45About Design Elements ........................................................................................................................ 45
Chapter 2 Functional Categories .................................................................................................................. 47Chapter 3 About Design Elements ............................................................................................................... 63
ACC1.................................................................................................................................................. 64Supported Architectures................................................................................................................ 64Introduction.................................................................................................................................. 64Design Entry Method .................................................................................................................... 64For More Information .................................................................................................................... 65
ACC16 ................................................................................................................................................ 66Supported Architectures................................................................................................................ 66Introduction.................................................................................................................................. 66Logic Table ................................................................................................................................... 67Design Entry Method .................................................................................................................... 67For More Information .................................................................................................................... 67
ACC4.................................................................................................................................................. 68Supported Architectures................................................................................................................ 68Introduction.................................................................................................................................. 68Logic Table ................................................................................................................................... 69Design Entry Method .................................................................................................................... 69For More Information .................................................................................................................... 69
ACC8.................................................................................................................................................. 70Supported Architectures................................................................................................................ 70Introduction.................................................................................................................................. 70Logic Table ................................................................................................................................... 71Design Entry Method .................................................................................................................... 71For More Information .................................................................................................................... 71
ADD1 ................................................................................................................................................. 72Supported Architectures................................................................................................................ 72Introduction.................................................................................................................................. 72Logic Table ................................................................................................................................... 72Design Entry Method .................................................................................................................... 72For More Information .................................................................................................................... 72
ADD16................................................................................................................................................ 73Supported Architectures................................................................................................................ 73Introduction.................................................................................................................................. 73Logic Table ................................................................................................................................... 73Design Entry Method .................................................................................................................... 74For More Information .................................................................................................................... 74
ADD4 ................................................................................................................................................. 75Supported Architectures................................................................................................................ 75Introduction.................................................................................................................................. 75Logic Table ................................................................................................................................... 75Design Entry Method .................................................................................................................... 76For More Information .................................................................................................................... 76
ADD8 ................................................................................................................................................. 77Supported Architectures................................................................................................................ 77Introduction.................................................................................................................................. 77Logic Table ................................................................................................................................... 77Design Entry Method .................................................................................................................... 77For More Information .................................................................................................................... 78
ADSU1................................................................................................................................................ 79Supported Architectures................................................................................................................ 79Introduction.................................................................................................................................. 79
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 3
Design Entry Method .................................................................................................................... 80For More Information .................................................................................................................... 80
ADSU16 .............................................................................................................................................. 81Supported Architectures................................................................................................................ 81Introduction.................................................................................................................................. 81Logic Table ................................................................................................................................... 81Design Entry Method .................................................................................................................... 82For More Information .................................................................................................................... 82
ADSU4................................................................................................................................................ 83Supported Architectures................................................................................................................ 83Introduction.................................................................................................................................. 83Logic Table ................................................................................................................................... 83Design Entry Method .................................................................................................................... 84For More Information .................................................................................................................... 84
ADSU8................................................................................................................................................ 85Supported Architectures................................................................................................................ 85Introduction.................................................................................................................................. 85Logic Table ................................................................................................................................... 85Design Entry Method .................................................................................................................... 86For More Information .................................................................................................................... 86
AND2 ................................................................................................................................................. 87Supported Architectures................................................................................................................ 87Introduction.................................................................................................................................. 87Design Entry Method .................................................................................................................... 87For More Information .................................................................................................................... 87
AND2B1.............................................................................................................................................. 88Supported Architectures................................................................................................................ 88Introduction.................................................................................................................................. 88Design Entry Method .................................................................................................................... 88For More Information .................................................................................................................... 88
AND2B2.............................................................................................................................................. 89Supported Architectures................................................................................................................ 89Introduction.................................................................................................................................. 89Design Entry Method .................................................................................................................... 89For More Information .................................................................................................................... 89
AND3 ................................................................................................................................................. 90Supported Architectures................................................................................................................ 90Introduction.................................................................................................................................. 90Design Entry Method .................................................................................................................... 90For More Information .................................................................................................................... 90
AND3B1.............................................................................................................................................. 91Supported Architectures................................................................................................................ 91Introduction.................................................................................................................................. 91Design Entry Method .................................................................................................................... 91For More Information .................................................................................................................... 91
AND3B2.............................................................................................................................................. 92Supported Architectures................................................................................................................ 92Introduction.................................................................................................................................. 92Design Entry Method .................................................................................................................... 92For More Information .................................................................................................................... 92
AND3B3.............................................................................................................................................. 93Supported Architectures................................................................................................................ 93Introduction.................................................................................................................................. 93Design Entry Method .................................................................................................................... 93For More Information .................................................................................................................... 93
AND4 ................................................................................................................................................. 94Supported Architectures................................................................................................................ 94Introduction.................................................................................................................................. 94Design Entry Method .................................................................................................................... 94
CPLD Libraries Guide4 www.xilinx.com UG606 (v 11.3) September 16, 2009
For More Information .................................................................................................................... 94AND4B1.............................................................................................................................................. 95
Supported Architectures................................................................................................................ 95Introduction.................................................................................................................................. 95Design Entry Method .................................................................................................................... 95For More Information .................................................................................................................... 95
AND4B2.............................................................................................................................................. 96Supported Architectures................................................................................................................ 96Introduction.................................................................................................................................. 96Design Entry Method .................................................................................................................... 96For More Information .................................................................................................................... 96
AND4B3.............................................................................................................................................. 97Supported Architectures................................................................................................................ 97Introduction.................................................................................................................................. 97Design Entry Method .................................................................................................................... 97For More Information .................................................................................................................... 97
AND4B4.............................................................................................................................................. 98Supported Architectures................................................................................................................ 98Introduction.................................................................................................................................. 98Design Entry Method .................................................................................................................... 98For More Information .................................................................................................................... 98
AND5 ................................................................................................................................................. 99Supported Architectures................................................................................................................ 99Introduction.................................................................................................................................. 99Design Entry Method .................................................................................................................... 99For More Information .................................................................................................................... 99
AND5B1............................................................................................................................................. 100Supported Architectures............................................................................................................... 100Introduction................................................................................................................................. 100Design Entry Method ................................................................................................................... 100For More Information ................................................................................................................... 100
AND5B2............................................................................................................................................. 101Supported Architectures............................................................................................................... 101Introduction................................................................................................................................. 101Design Entry Method ................................................................................................................... 101For More Information ................................................................................................................... 101
AND5B3............................................................................................................................................. 102Supported Architectures............................................................................................................... 102Introduction................................................................................................................................. 102Design Entry Method ................................................................................................................... 102For More Information ................................................................................................................... 102
AND5B4............................................................................................................................................. 103Supported Architectures............................................................................................................... 103Introduction................................................................................................................................. 103Design Entry Method ................................................................................................................... 103For More Information ................................................................................................................... 103
AND5B5............................................................................................................................................. 104Supported Architectures............................................................................................................... 104Introduction................................................................................................................................. 104Design Entry Method ................................................................................................................... 104For More Information ................................................................................................................... 104
AND6 ................................................................................................................................................ 105Supported Architectures............................................................................................................... 105Introduction................................................................................................................................. 105Design Entry Method ................................................................................................................... 105For More Information ................................................................................................................... 105
AND7 ................................................................................................................................................ 106Supported Architectures............................................................................................................... 106Introduction................................................................................................................................. 106
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 5
Design Entry Method ................................................................................................................... 106For More Information ................................................................................................................... 106
AND8 ................................................................................................................................................ 107Supported Architectures............................................................................................................... 107Introduction................................................................................................................................. 107Design Entry Method ................................................................................................................... 107For More Information ................................................................................................................... 107
AND9 ................................................................................................................................................ 108Supported Architectures............................................................................................................... 108Introduction................................................................................................................................. 108Design Entry Method ................................................................................................................... 108For More Information ................................................................................................................... 108
BRLSHFT4 ......................................................................................................................................... 109Supported Architectures............................................................................................................... 109Introduction................................................................................................................................. 109Logic Table .................................................................................................................................. 109Design Entry Method ................................................................................................................... 109For More Information ................................................................................................................... 109
BRLSHFT8 ......................................................................................................................................... 110Supported Architectures............................................................................................................... 110Introduction................................................................................................................................. 110Logic Table .................................................................................................................................. 110Design Entry Method ................................................................................................................... 110For More Information ................................................................................................................... 111
BUF ................................................................................................................................................... 112Supported Architectures............................................................................................................... 112Introduction................................................................................................................................. 112Design Entry Method ................................................................................................................... 112For More Information ................................................................................................................... 112
BUF16 ................................................................................................................................................ 113Supported Architectures............................................................................................................... 113Introduction................................................................................................................................. 113Design Entry Method ................................................................................................................... 113For More Information ................................................................................................................... 113
BUF4.................................................................................................................................................. 114Supported Architectures............................................................................................................... 114Introduction................................................................................................................................. 114Design Entry Method ................................................................................................................... 114For More Information ................................................................................................................... 114
BUF8.................................................................................................................................................. 115Supported Architectures............................................................................................................... 115Introduction................................................................................................................................. 115Design Entry Method ................................................................................................................... 115For More Information ................................................................................................................... 115
BUFE ................................................................................................................................................. 116Supported Architectures............................................................................................................... 116Introduction................................................................................................................................. 116Logic Table .................................................................................................................................. 116Design Entry Method ................................................................................................................... 116For More Information ................................................................................................................... 116
BUFE16 .............................................................................................................................................. 117Supported Architectures............................................................................................................... 117Introduction................................................................................................................................. 117Logic Table .................................................................................................................................. 117Design Entry Method ................................................................................................................... 117For More Information ................................................................................................................... 117
BUFE4................................................................................................................................................ 118Supported Architectures............................................................................................................... 118Introduction................................................................................................................................. 118
CPLD Libraries Guide6 www.xilinx.com UG606 (v 11.3) September 16, 2009
Logic Table .................................................................................................................................. 118Design Entry Method ................................................................................................................... 118For More Information ................................................................................................................... 118
BUFE8................................................................................................................................................ 119Supported Architectures............................................................................................................... 119Introduction................................................................................................................................. 119Logic Table .................................................................................................................................. 119Design Entry Method ................................................................................................................... 119For More Information ................................................................................................................... 119
BUFG................................................................................................................................................. 120Supported Architectures............................................................................................................... 120Introduction................................................................................................................................. 120Port Descriptions.......................................................................................................................... 120Design Entry Method ................................................................................................................... 120For More Information ................................................................................................................... 121
BUFGSR............................................................................................................................................. 122Supported Architectures............................................................................................................... 122Introduction................................................................................................................................. 122Design Entry Method ................................................................................................................... 122For More Information ................................................................................................................... 122
BUFGTS ............................................................................................................................................. 123Supported Architectures............................................................................................................... 123Introduction................................................................................................................................. 123Design Entry Method ................................................................................................................... 123For More Information ................................................................................................................... 123
BUFT ................................................................................................................................................. 124Supported Architectures............................................................................................................... 124Introduction................................................................................................................................. 124Logic Table .................................................................................................................................. 124Design Entry Method ................................................................................................................... 124For More Information ................................................................................................................... 124
BUFT16 .............................................................................................................................................. 125Supported Architectures............................................................................................................... 125Introduction................................................................................................................................. 125Logic Table .................................................................................................................................. 125Design Entry Method ................................................................................................................... 125For More Information ................................................................................................................... 125
BUFT4................................................................................................................................................ 126Supported Architectures............................................................................................................... 126Introduction................................................................................................................................. 126Logic Table .................................................................................................................................. 126Design Entry Method ................................................................................................................... 126For More Information ................................................................................................................... 126
BUFT8................................................................................................................................................ 127Supported Architectures............................................................................................................... 127Introduction................................................................................................................................. 127Logic Table .................................................................................................................................. 127Design Entry Method ................................................................................................................... 127For More Information ................................................................................................................... 127
CB16CE.............................................................................................................................................. 128Supported Architectures............................................................................................................... 128Introduction................................................................................................................................. 128Logic Table .................................................................................................................................. 128Design Entry Method ................................................................................................................... 128For More Information ................................................................................................................... 129
CB16CLE............................................................................................................................................ 130Supported Architectures............................................................................................................... 130Introduction................................................................................................................................. 130Logic Table .................................................................................................................................. 131
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 7
Design Entry Method ................................................................................................................... 131For More Information ................................................................................................................... 131
CB16CLED ......................................................................................................................................... 132Supported Architectures............................................................................................................... 132Introduction................................................................................................................................. 132Logic Table .................................................................................................................................. 133Design Entry Method ................................................................................................................... 133For More Information ................................................................................................................... 133
CB16RE.............................................................................................................................................. 134Supported Architectures............................................................................................................... 134Introduction................................................................................................................................. 134Logic Table .................................................................................................................................. 134Design Entry Method ................................................................................................................... 134For More Information ................................................................................................................... 135
CB16RLE............................................................................................................................................ 136Supported Architectures............................................................................................................... 136Introduction................................................................................................................................. 136Logic Table .................................................................................................................................. 137Design Entry Method ................................................................................................................... 137For More Information ................................................................................................................... 137
CB16X1 .............................................................................................................................................. 138Supported Architectures............................................................................................................... 138Introduction................................................................................................................................. 138Logic Table .................................................................................................................................. 139Design Entry Method ................................................................................................................... 139For More Information ................................................................................................................... 139
CB16X2 .............................................................................................................................................. 140Supported Architectures............................................................................................................... 140Introduction................................................................................................................................. 140Logic Table .................................................................................................................................. 141Design Entry Method ................................................................................................................... 141For More Information ................................................................................................................... 141
CB2CE ............................................................................................................................................... 142Supported Architectures............................................................................................................... 142Introduction................................................................................................................................. 142Logic Table .................................................................................................................................. 142Design Entry Method ................................................................................................................... 142For More Information ................................................................................................................... 143
CB2CLE ............................................................................................................................................. 144Supported Architectures............................................................................................................... 144Introduction................................................................................................................................. 144Logic Table .................................................................................................................................. 144Design Entry Method ................................................................................................................... 145For More Information ................................................................................................................... 145
CB2CLED........................................................................................................................................... 146Supported Architectures............................................................................................................... 146Introduction................................................................................................................................. 146Logic Table .................................................................................................................................. 147Design Entry Method ................................................................................................................... 147For More Information ................................................................................................................... 147
CB2RE................................................................................................................................................ 148Supported Architectures............................................................................................................... 148Introduction................................................................................................................................. 148Logic Table .................................................................................................................................. 148Design Entry Method ................................................................................................................... 148For More Information ................................................................................................................... 149
CB2RLE ............................................................................................................................................. 150Supported Architectures............................................................................................................... 150Introduction................................................................................................................................. 150
CPLD Libraries Guide8 www.xilinx.com UG606 (v 11.3) September 16, 2009
Logic Table .................................................................................................................................. 151Design Entry Method ................................................................................................................... 151For More Information ................................................................................................................... 151
CB2X1................................................................................................................................................ 152Supported Architectures............................................................................................................... 152Introduction................................................................................................................................. 152Logic Table .................................................................................................................................. 153Design Entry Method ................................................................................................................... 153For More Information ................................................................................................................... 153
CB4CE ............................................................................................................................................... 154Supported Architectures............................................................................................................... 154Introduction................................................................................................................................. 154Logic Table .................................................................................................................................. 154Design Entry Method ................................................................................................................... 155For More Information ................................................................................................................... 155
CB4CLE ............................................................................................................................................. 156Supported Architectures............................................................................................................... 156Introduction................................................................................................................................. 156Logic Table .................................................................................................................................. 157Design Entry Method ................................................................................................................... 157For More Information ................................................................................................................... 157
CB4CLED........................................................................................................................................... 158Supported Architectures............................................................................................................... 158Introduction................................................................................................................................. 158Logic Table .................................................................................................................................. 159Design Entry Method ................................................................................................................... 159For More Information ................................................................................................................... 159
CB4RE................................................................................................................................................ 160Supported Architectures............................................................................................................... 160Introduction................................................................................................................................. 160Logic Table .................................................................................................................................. 160Design Entry Method ................................................................................................................... 161For More Information ................................................................................................................... 161
CB4RLE ............................................................................................................................................. 162Supported Architectures............................................................................................................... 162Introduction................................................................................................................................. 162Logic Table .................................................................................................................................. 163Design Entry Method ................................................................................................................... 163For More Information ................................................................................................................... 163
CB4X1................................................................................................................................................ 164Supported Architectures............................................................................................................... 164Introduction................................................................................................................................. 164Logic Table .................................................................................................................................. 165Design Entry Method ................................................................................................................... 165For More Information ................................................................................................................... 165
CB4X2................................................................................................................................................ 166Supported Architectures............................................................................................................... 166Introduction................................................................................................................................. 166Logic Table .................................................................................................................................. 167Design Entry Method ................................................................................................................... 167For More Information ................................................................................................................... 167
CB8CE ............................................................................................................................................... 168Supported Architectures............................................................................................................... 168Introduction................................................................................................................................. 168Logic Table .................................................................................................................................. 168Design Entry Method ................................................................................................................... 168For More Information ................................................................................................................... 169
CB8CLE ............................................................................................................................................. 170Supported Architectures............................................................................................................... 170
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 9
Introduction................................................................................................................................. 170Logic Table .................................................................................................................................. 171Design Entry Method ................................................................................................................... 171For More Information ................................................................................................................... 171
CB8CLED........................................................................................................................................... 172Supported Architectures............................................................................................................... 172Introduction................................................................................................................................. 172Logic Table .................................................................................................................................. 173Design Entry Method ................................................................................................................... 173For More Information ................................................................................................................... 173
CB8RE................................................................................................................................................ 174Supported Architectures............................................................................................................... 174Introduction................................................................................................................................. 174Logic Table .................................................................................................................................. 174Design Entry Method ................................................................................................................... 174For More Information ................................................................................................................... 175
CB8RLE ............................................................................................................................................. 176Supported Architectures............................................................................................................... 176Introduction................................................................................................................................. 176Logic Table .................................................................................................................................. 177Design Entry Method ................................................................................................................... 177For More Information ................................................................................................................... 177
CB8X1................................................................................................................................................ 178Supported Architectures............................................................................................................... 178Introduction................................................................................................................................. 178Logic Table .................................................................................................................................. 179Design Entry Method ................................................................................................................... 179For More Information ................................................................................................................... 179
CB8X2................................................................................................................................................ 180Supported Architectures............................................................................................................... 180Introduction................................................................................................................................. 180Logic Table .................................................................................................................................. 181Design Entry Method ................................................................................................................... 181For More Information ................................................................................................................... 181
CBD16CE ........................................................................................................................................... 182Supported Architectures............................................................................................................... 182Introduction................................................................................................................................. 182Logic Table .................................................................................................................................. 182Design Entry Method ................................................................................................................... 182For More Information ................................................................................................................... 183
CBD16CLE ......................................................................................................................................... 184Supported Architectures............................................................................................................... 184Introduction................................................................................................................................. 184Logic Table .................................................................................................................................. 184Design Entry Method ................................................................................................................... 185For More Information ................................................................................................................... 185
CBD16CLED....................................................................................................................................... 186Supported Architectures............................................................................................................... 186Introduction................................................................................................................................. 186Logic Table .................................................................................................................................. 187Design Entry Method ................................................................................................................... 187For More Information ................................................................................................................... 187
CBD16RE ........................................................................................................................................... 188Supported Architectures............................................................................................................... 188Introduction................................................................................................................................. 188Logic Table .................................................................................................................................. 188Design Entry Method ................................................................................................................... 188For More Information ................................................................................................................... 189
CBD16RLE ......................................................................................................................................... 190
CPLD Libraries Guide10 www.xilinx.com UG606 (v 11.3) September 16, 2009
Supported Architectures............................................................................................................... 190Introduction................................................................................................................................. 190Logic Table .................................................................................................................................. 190Design Entry Method ................................................................................................................... 191For More Information ................................................................................................................... 191
CBD16X1............................................................................................................................................ 192Supported Architectures............................................................................................................... 192Introduction................................................................................................................................. 192Logic Table .................................................................................................................................. 193Design Entry Method ................................................................................................................... 193For More Information ................................................................................................................... 193
CBD16X2............................................................................................................................................ 194Supported Architectures............................................................................................................... 194Introduction................................................................................................................................. 194Logic Table .................................................................................................................................. 195Design Entry Method ................................................................................................................... 195For More Information ................................................................................................................... 195
CBD2CE............................................................................................................................................. 196Supported Architectures............................................................................................................... 196Introduction................................................................................................................................. 196Logic Table .................................................................................................................................. 196Design Entry Method ................................................................................................................... 196For More Information ................................................................................................................... 197
CBD2CLE........................................................................................................................................... 198Supported Architectures............................................................................................................... 198Introduction................................................................................................................................. 198Logic Table .................................................................................................................................. 199Design Entry Method ................................................................................................................... 199For More Information ................................................................................................................... 199
CBD2CLED ........................................................................................................................................ 200Supported Architectures............................................................................................................... 200Introduction................................................................................................................................. 200Logic Table .................................................................................................................................. 201Design Entry Method ................................................................................................................... 201For More Information ................................................................................................................... 201
CBD2RE............................................................................................................................................. 202Supported Architectures............................................................................................................... 202Introduction................................................................................................................................. 202Logic Table .................................................................................................................................. 202Design Entry Method ................................................................................................................... 203For More Information ................................................................................................................... 203
CBD2RLE........................................................................................................................................... 204Supported Architectures............................................................................................................... 204Introduction................................................................................................................................. 204Logic Table .................................................................................................................................. 205Design Entry Method ................................................................................................................... 205For More Information ................................................................................................................... 205
CBD2X1 ............................................................................................................................................. 206Supported Architectures............................................................................................................... 206Introduction................................................................................................................................. 206Logic Table .................................................................................................................................. 207Design Entry Method ................................................................................................................... 207For More Information ................................................................................................................... 207
CBD2X2 ............................................................................................................................................. 208Supported Architectures............................................................................................................... 208Introduction................................................................................................................................. 208Logic Table .................................................................................................................................. 209Design Entry Method ................................................................................................................... 209For More Information ................................................................................................................... 209
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 11
CBD4CE............................................................................................................................................. 210Supported Architectures............................................................................................................... 210Introduction................................................................................................................................. 210Logic Table .................................................................................................................................. 210Design Entry Method ................................................................................................................... 211For More Information ................................................................................................................... 211
CBD4CLE........................................................................................................................................... 212Supported Architectures............................................................................................................... 212Introduction................................................................................................................................. 212Logic Table .................................................................................................................................. 212Design Entry Method ................................................................................................................... 213For More Information ................................................................................................................... 213
CBD4CLED ........................................................................................................................................ 214Supported Architectures............................................................................................................... 214Introduction................................................................................................................................. 214Logic Table .................................................................................................................................. 215Design Entry Method ................................................................................................................... 215For More Information ................................................................................................................... 215
CBD4RE............................................................................................................................................. 216Supported Architectures............................................................................................................... 216Introduction................................................................................................................................. 216Logic Table .................................................................................................................................. 216Design Entry Method ................................................................................................................... 217For More Information ................................................................................................................... 217
CBD4RLE........................................................................................................................................... 218Supported Architectures............................................................................................................... 218Introduction................................................................................................................................. 218Logic Table .................................................................................................................................. 219Design Entry Method ................................................................................................................... 219For More Information ................................................................................................................... 219
CBD4X1 ............................................................................................................................................. 220Supported Architectures............................................................................................................... 220Introduction................................................................................................................................. 220Logic Table .................................................................................................................................. 221Design Entry Method ................................................................................................................... 221For More Information ................................................................................................................... 221
CBD4X2 ............................................................................................................................................. 222Supported Architectures............................................................................................................... 222Introduction................................................................................................................................. 222Logic Table .................................................................................................................................. 223Design Entry Method ................................................................................................................... 223For More Information ................................................................................................................... 223
CBD8CE............................................................................................................................................. 224Supported Architectures............................................................................................................... 224Introduction................................................................................................................................. 224Logic Table .................................................................................................................................. 224Design Entry Method ................................................................................................................... 224For More Information ................................................................................................................... 225
CBD8CLE........................................................................................................................................... 226Supported Architectures............................................................................................................... 226Introduction................................................................................................................................. 226Logic Table .................................................................................................................................. 227Design Entry Method ................................................................................................................... 227For More Information ................................................................................................................... 227
CBD8CLED ........................................................................................................................................ 228Supported Architectures............................................................................................................... 228Introduction................................................................................................................................. 228Logic Table .................................................................................................................................. 229Design Entry Method ................................................................................................................... 229
CPLD Libraries Guide12 www.xilinx.com UG606 (v 11.3) September 16, 2009
For More Information ................................................................................................................... 229CBD8RE............................................................................................................................................. 230
Supported Architectures............................................................................................................... 230Introduction................................................................................................................................. 230Logic Table .................................................................................................................................. 230Design Entry Method ................................................................................................................... 230For More Information ................................................................................................................... 231
CBD8X1 ............................................................................................................................................. 232Supported Architectures............................................................................................................... 232Introduction................................................................................................................................. 232Logic Table .................................................................................................................................. 233Design Entry Method ................................................................................................................... 233For More Information ................................................................................................................... 233
CBD8X2 ............................................................................................................................................. 234Supported Architectures............................................................................................................... 234Introduction................................................................................................................................. 234Logic Table .................................................................................................................................. 235Design Entry Method ................................................................................................................... 235For More Information ................................................................................................................... 235
CD4CE............................................................................................................................................... 236Supported Architectures............................................................................................................... 236Introduction................................................................................................................................. 236Logic Table .................................................................................................................................. 237Design Entry Method ................................................................................................................... 237For More Information ................................................................................................................... 237
CD4CLE............................................................................................................................................. 238Supported Architectures............................................................................................................... 238Introduction................................................................................................................................. 238Logic Table .................................................................................................................................. 239Design Entry Method ................................................................................................................... 239For More Information ................................................................................................................... 239
CD4RE ............................................................................................................................................... 240Supported Architectures............................................................................................................... 240Introduction................................................................................................................................. 240Logic Table .................................................................................................................................. 241Design Entry Method ................................................................................................................... 241For More Information ................................................................................................................... 241
CD4RLE............................................................................................................................................. 242Supported Architectures............................................................................................................... 242Introduction................................................................................................................................. 242Logic Table .................................................................................................................................. 243Design Entry Method ................................................................................................................... 243For More Information ................................................................................................................... 243
CDD4CE ............................................................................................................................................ 244Supported Architectures............................................................................................................... 244Introduction................................................................................................................................. 244Logic Table .................................................................................................................................. 245Design Entry Method ................................................................................................................... 245For More Information ................................................................................................................... 245
CDD4CLE .......................................................................................................................................... 246Supported Architectures............................................................................................................... 246Introduction................................................................................................................................. 246Logic Table .................................................................................................................................. 247Design Entry Method ................................................................................................................... 247For More Information ................................................................................................................... 247
CDD4RE ............................................................................................................................................ 248Supported Architectures............................................................................................................... 248Introduction................................................................................................................................. 248Logic Table .................................................................................................................................. 249
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 13
Design Entry Method ................................................................................................................... 249For More Information ................................................................................................................... 249
CDD4RLE .......................................................................................................................................... 250Supported Architectures............................................................................................................... 250Introduction................................................................................................................................. 250Design Entry Method ................................................................................................................... 250For More Information ................................................................................................................... 250
CJ4CE ................................................................................................................................................ 251Supported Architectures............................................................................................................... 251Introduction................................................................................................................................. 251Logic Table .................................................................................................................................. 251Design Entry Method ................................................................................................................... 251For More Information ................................................................................................................... 251
CJ4RE ................................................................................................................................................ 252Supported Architectures............................................................................................................... 252Introduction................................................................................................................................. 252Logic Table .................................................................................................................................. 252Design Entry Method ................................................................................................................... 252For More Information ................................................................................................................... 252
CJ5CE ................................................................................................................................................ 253Supported Architectures............................................................................................................... 253Introduction................................................................................................................................. 253Logic Table .................................................................................................................................. 253Design Entry Method ................................................................................................................... 253For More Information ................................................................................................................... 253
CJ5RE ................................................................................................................................................ 254Supported Architectures............................................................................................................... 254Introduction................................................................................................................................. 254Logic Table .................................................................................................................................. 254Design Entry Method ................................................................................................................... 254For More Information ................................................................................................................... 254
CJ8CE ................................................................................................................................................ 255Supported Architectures............................................................................................................... 255Introduction................................................................................................................................. 255Logic Table .................................................................................................................................. 255Design Entry Method ................................................................................................................... 255For More Information ................................................................................................................... 255
CJ8RE ................................................................................................................................................ 256Supported Architectures............................................................................................................... 256Introduction................................................................................................................................. 256Logic Table .................................................................................................................................. 256Design Entry Method ................................................................................................................... 256For More Information ................................................................................................................... 256
CJD4CE.............................................................................................................................................. 257Supported Architectures............................................................................................................... 257Introduction................................................................................................................................. 257Logic Table .................................................................................................................................. 257Design Entry Method ................................................................................................................... 257For More Information ................................................................................................................... 257
CJD4RE.............................................................................................................................................. 258Supported Architectures............................................................................................................... 258Introduction................................................................................................................................. 258Logic Table .................................................................................................................................. 258Design Entry Method ................................................................................................................... 258For More Information ................................................................................................................... 258
CJD5CE.............................................................................................................................................. 259Supported Architectures............................................................................................................... 259Introduction................................................................................................................................. 259Logic Table .................................................................................................................................. 259
CPLD Libraries Guide14 www.xilinx.com UG606 (v 11.3) September 16, 2009
Design Entry Method ................................................................................................................... 259For More Information ................................................................................................................... 259
CJD5RE.............................................................................................................................................. 260Supported Architectures............................................................................................................... 260Introduction................................................................................................................................. 260Logic Table .................................................................................................................................. 260Design Entry Method ................................................................................................................... 260For More Information ................................................................................................................... 260
CJD8CE.............................................................................................................................................. 261Supported Architectures............................................................................................................... 261Introduction................................................................................................................................. 261Logic Table .................................................................................................................................. 261Design Entry Method ................................................................................................................... 261For More Information ................................................................................................................... 261
CJD8RE.............................................................................................................................................. 262Supported Architectures............................................................................................................... 262Introduction................................................................................................................................. 262Logic Table .................................................................................................................................. 262Design Entry Method ................................................................................................................... 262For More Information ................................................................................................................... 262
CLK_DIV10 ........................................................................................................................................ 263Supported Architectures............................................................................................................... 263Introduction................................................................................................................................. 263Design Entry Method ................................................................................................................... 263For More Information ................................................................................................................... 264
CLK_DIV10R...................................................................................................................................... 265Supported Architectures............................................................................................................... 265Introduction................................................................................................................................. 265Design Entry Method ................................................................................................................... 265For More Information ................................................................................................................... 266
CLK_DIV10RSD ................................................................................................................................. 267Supported Architectures............................................................................................................... 267Introduction................................................................................................................................. 267Design Entry Method ................................................................................................................... 267For More Information ................................................................................................................... 268
CLK_DIV10SD.................................................................................................................................... 269Supported Architectures............................................................................................................... 269Introduction................................................................................................................................. 269Design Entry Method ................................................................................................................... 269For More Information ................................................................................................................... 270
CLK_DIV12 ........................................................................................................................................ 271Supported Architectures............................................................................................................... 271Introduction................................................................................................................................. 271Design Entry Method ................................................................................................................... 271For More Information ................................................................................................................... 272
CLK_DIV12R...................................................................................................................................... 273Supported Architectures............................................................................................................... 273Introduction................................................................................................................................. 273Design Entry Method ................................................................................................................... 273For More Information ................................................................................................................... 274
CLK_DIV12RSD ................................................................................................................................. 275Supported Architectures............................................................................................................... 275Introduction................................................................................................................................. 275Design Entry Method ................................................................................................................... 275For More Information ................................................................................................................... 276
CLK_DIV12SD.................................................................................................................................... 277Supported Architectures............................................................................................................... 277Introduction................................................................................................................................. 277Design Entry Method ................................................................................................................... 277
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 15
For More Information ................................................................................................................... 278CLK_DIV14R...................................................................................................................................... 279
Supported Architectures............................................................................................................... 279Introduction................................................................................................................................. 279Design Entry Method ................................................................................................................... 279For More Information ................................................................................................................... 280
CLK_DIV14RSD ................................................................................................................................. 281Supported Architectures............................................................................................................... 281Introduction................................................................................................................................. 281Design Entry Method ................................................................................................................... 281For More Information ................................................................................................................... 282
CLK_DIV14SD.................................................................................................................................... 283Supported Architectures............................................................................................................... 283Introduction................................................................................................................................. 283Design Entry Method ................................................................................................................... 283For More Information ................................................................................................................... 284
CLK_DIV16 ........................................................................................................................................ 285Supported Architectures............................................................................................................... 285Introduction................................................................................................................................. 285Design Entry Method ................................................................................................................... 285For More Information ................................................................................................................... 286
CLK_DIV16R...................................................................................................................................... 287Supported Architectures............................................................................................................... 287Introduction................................................................................................................................. 287Design Entry Method ................................................................................................................... 287For More Information ................................................................................................................... 288
CLK_DIV16RSD ................................................................................................................................. 289Supported Architectures............................................................................................................... 289Introduction................................................................................................................................. 289Design Entry Method ................................................................................................................... 289For More Information ................................................................................................................... 290
CLK_DIV16SD.................................................................................................................................... 291Supported Architectures............................................................................................................... 291Introduction................................................................................................................................. 291Design Entry Method ................................................................................................................... 291For More Information ................................................................................................................... 292
CLK_DIV2.......................................................................................................................................... 293Supported Architectures............................................................................................................... 293Introduction................................................................................................................................. 293Design Entry Method ................................................................................................................... 293For More Information ................................................................................................................... 294
CLK_DIV2R ....................................................................................................................................... 295Supported Architectures............................................................................................................... 295Introduction................................................................................................................................. 295Design Entry Method ................................................................................................................... 295For More Information ................................................................................................................... 296
CLK_DIV2RSD ................................................................................................................................... 297Supported Architectures............................................................................................................... 297Introduction................................................................................................................................. 297Design Entry Method ................................................................................................................... 297For More Information ................................................................................................................... 298
CLK_DIV2SD ..................................................................................................................................... 299Supported Architectures............................................................................................................... 299Introduction................................................................................................................................. 299Design Entry Method ................................................................................................................... 299For More Information ................................................................................................................... 300
CLK_DIV4.......................................................................................................................................... 301Supported Architectures............................................................................................................... 301Introduction................................................................................................................................. 301
CPLD Libraries Guide16 www.xilinx.com UG606 (v 11.3) September 16, 2009
Design Entry Method ................................................................................................................... 301For More Information ................................................................................................................... 302
CLK_DIV4R ....................................................................................................................................... 303Supported Architectures............................................................................................................... 303Introduction................................................................................................................................. 303Design Entry Method ................................................................................................................... 303For More Information ................................................................................................................... 304
CLK_DIV4RSD ................................................................................................................................... 305Supported Architectures............................................................................................................... 305Introduction................................................................................................................................. 305Design Entry Method ................................................................................................................... 305For More Information ................................................................................................................... 306
CLK_DIV4SD ..................................................................................................................................... 307Supported Architectures............................................................................................................... 307Introduction................................................................................................................................. 307Design Entry Method ................................................................................................................... 307For More Information ................................................................................................................... 308
CLK_DIV6.......................................................................................................................................... 309Supported Architectures............................................................................................................... 309Introduction................................................................................................................................. 309Design Entry Method ................................................................................................................... 309For More Information ................................................................................................................... 310
CLK_DIV6R ....................................................................................................................................... 311Supported Architectures............................................................................................................... 311Introduction................................................................................................................................. 311Design Entry Method ................................................................................................................... 311For More Information ................................................................................................................... 312
CLK_DIV6RSD ................................................................................................................................... 313Supported Architectures............................................................................................................... 313Introduction................................................................................................................................. 313Design Entry Method ................................................................................................................... 313For More Information ................................................................................................................... 314
CLK_DIV6SD ..................................................................................................................................... 315Supported Architectures............................................................................................................... 315Introduction................................................................................................................................. 315Design Entry Method ................................................................................................................... 315For More Information ................................................................................................................... 316
CLK_DIV8.......................................................................................................................................... 317Supported Architectures............................................................................................................... 317Introduction................................................................................................................................. 317Design Entry Method ................................................................................................................... 317For More Information ................................................................................................................... 318
CLK_DIV8R ....................................................................................................................................... 319Supported Architectures............................................................................................................... 319Introduction................................................................................................................................. 319Design Entry Method ................................................................................................................... 319For More Information ................................................................................................................... 320
CLK_DIV8RSD ................................................................................................................................... 321Supported Architectures............................................................................................................... 321Introduction................................................................................................................................. 321Design Entry Method ................................................................................................................... 321For More Information ................................................................................................................... 322
CLK_DIV8SD ..................................................................................................................................... 323Supported Architectures............................................................................................................... 323Introduction................................................................................................................................. 323Design Entry Method ................................................................................................................... 323For More Information ................................................................................................................... 324
COMP16 ............................................................................................................................................ 325Supported Architectures............................................................................................................... 325
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 17
Introduction................................................................................................................................. 325Design Entry Method ................................................................................................................... 325For More Information ................................................................................................................... 325
COMP2 .............................................................................................................................................. 326Supported Architectures............................................................................................................... 326Introduction................................................................................................................................. 326Design Entry Method ................................................................................................................... 326For More Information ................................................................................................................... 326
COMP4 .............................................................................................................................................. 327Supported Architectures............................................................................................................... 327Introduction................................................................................................................................. 327Design Entry Method ................................................................................................................... 327For More Information ................................................................................................................... 327
COMP8 .............................................................................................................................................. 328Supported Architectures............................................................................................................... 328Introduction................................................................................................................................. 328Design Entry Method ................................................................................................................... 328For More Information ................................................................................................................... 328
COMPM16 ......................................................................................................................................... 329Supported Architectures............................................................................................................... 329Introduction................................................................................................................................. 329Logic Table .................................................................................................................................. 329Design Entry Method ................................................................................................................... 330For More Information ................................................................................................................... 330
COMPM2........................................................................................................................................... 331Supported Architectures............................................................................................................... 331Introduction................................................................................................................................. 331Logic Table .................................................................................................................................. 331Design Entry Method ................................................................................................................... 331For More Information ................................................................................................................... 331
COMPM4........................................................................................................................................... 332Supported Architectures............................................................................................................... 332Introduction................................................................................................................................. 332Logic Table .................................................................................................................................. 332Design Entry Method ................................................................................................................... 332For More Information ................................................................................................................... 332
COMPM8........................................................................................................................................... 333Supported Architectures............................................................................................................... 333Introduction................................................................................................................................. 333Logic Table .................................................................................................................................. 333Design Entry Method ................................................................................................................... 334For More Information ................................................................................................................... 334
CR16CE.............................................................................................................................................. 335Supported Architectures............................................................................................................... 335Introduction................................................................................................................................. 335Logic Table .................................................................................................................................. 335Design Entry Method ................................................................................................................... 335For More Information ................................................................................................................... 335
CR8CE ............................................................................................................................................... 336Supported Architectures............................................................................................................... 336Introduction................................................................................................................................. 336Logic Table .................................................................................................................................. 336Design Entry Method ................................................................................................................... 336For More Information ................................................................................................................... 336
CRD16CE........................................................................................................................................... 337Supported Architectures............................................................................................................... 337Introduction................................................................................................................................. 337Logic Table .................................................................................................................................. 337Design Entry Method ................................................................................................................... 337
CPLD Libraries Guide18 www.xilinx.com UG606 (v 11.3) September 16, 2009
For More Information ................................................................................................................... 337CRD8CE............................................................................................................................................. 338
Supported Architectures............................................................................................................... 338Introduction................................................................................................................................. 338Logic Table .................................................................................................................................. 338Design Entry Method ................................................................................................................... 338For More Information ................................................................................................................... 338
D2_4E ................................................................................................................................................ 339Supported Architectures............................................................................................................... 339Introduction................................................................................................................................. 339Logic Table .................................................................................................................................. 339Design Entry Method ................................................................................................................... 339For More Information ................................................................................................................... 339
D3_8E ................................................................................................................................................ 340Supported Architectures............................................................................................................... 340Introduction................................................................................................................................. 340Logic Table .................................................................................................................................. 340Design Entry Method ................................................................................................................... 340For More Information ................................................................................................................... 340
D4_16E............................................................................................................................................... 341Supported Architectures............................................................................................................... 341Introduction................................................................................................................................. 341Design Entry Method ................................................................................................................... 341For More Information ................................................................................................................... 341
FD ..................................................................................................................................................... 342Supported Architectures............................................................................................................... 342Introduction................................................................................................................................. 342Logic Table .................................................................................................................................. 342Design Entry Method ................................................................................................................... 342Available Attributes ..................................................................................................................... 342For More Information ................................................................................................................... 342
FD16 .................................................................................................................................................. 343Supported Architectures............................................................................................................... 343Introduction................................................................................................................................. 343Logic Table .................................................................................................................................. 343Design Entry Method ................................................................................................................... 343For More Information ................................................................................................................... 343
FD16CE.............................................................................................................................................. 344Supported Architectures............................................................................................................... 344Introduction................................................................................................................................. 344Logic Table .................................................................................................................................. 344Design Entry Method ................................................................................................................... 344Available Attributes ..................................................................................................................... 344For More Information ................................................................................................................... 344
FD16RE.............................................................................................................................................. 345Supported Architectures............................................................................................................... 345Introduction................................................................................................................................. 345Logic Table .................................................................................................................................. 345Design Entry Method ................................................................................................................... 345Available Attributes ..................................................................................................................... 345For More Information ................................................................................................................... 345
FD4.................................................................................................................................................... 346Supported Architectures............................................................................................................... 346Introduction................................................................................................................................. 346Logic Table .................................................................................................................................. 346Design Entry Method ................................................................................................................... 346For More Information ................................................................................................................... 346
FD4CE ............................................................................................................................................... 347Supported Architectures............................................................................................................... 347
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 19
Introduction................................................................................................................................. 347Logic Table .................................................................................................................................. 347Design Entry Method ................................................................................................................... 347Available Attributes ..................................................................................................................... 347For More Information ................................................................................................................... 347
FD8.................................................................................................................................................... 348Supported Architectures............................................................................................................... 348Introduction................................................................................................................................. 348Logic Table .................................................................................................................................. 348Design Entry Method ................................................................................................................... 348For More Information ................................................................................................................... 348
FD8CE ............................................................................................................................................... 349Supported Architectures............................................................................................................... 349Introduction................................................................................................................................. 349Logic Table .................................................................................................................................. 349Design Entry Method ................................................................................................................... 349Available Attributes ..................................................................................................................... 349For More Information ................................................................................................................... 349
FD8RE ............................................................................................................................................... 350Supported Architectures............................................................................................................... 350Introduction................................................................................................................................. 350Logic Table .................................................................................................................................. 350Design Entry Method ................................................................................................................... 350Available Attributes ..................................................................................................................... 350For More Information ................................................................................................................... 350
FDC ................................................................................................................................................... 351Supported Architectures............................................................................................................... 351Introduction................................................................................................................................. 351Logic Table .................................................................................................................................. 351Design Entry Method ................................................................................................................... 351Available Attributes ..................................................................................................................... 351For More Information ................................................................................................................... 351
FDCE ................................................................................................................................................. 352Supported Architectures............................................................................................................... 352Introduction................................................................................................................................. 352Logic Table .................................................................................................................................. 352Design Entry Method ................................................................................................................... 352Available Attributes ..................................................................................................................... 352For More Information ................................................................................................................... 353
FDCP ................................................................................................................................................. 354Supported Architectures............................................................................................................... 354Introduction................................................................................................................................. 354Logic Table .................................................................................................................................. 354Design Entry Method ................................................................................................................... 354Available Attributes ..................................................................................................................... 354For More Information ................................................................................................................... 355
FDCPE ............................................................................................................................................... 356Supported Architectures............................................................................................................... 356Introduction................................................................................................................................. 356Logic Table .................................................................................................................................. 356Port Descriptions.......................................................................................................................... 357Design Entry Method ................................................................................................................... 357Available Attributes ..................................................................................................................... 357For More Information ................................................................................................................... 358
FDD................................................................................................................................................... 359Supported Architectures............................................................................................................... 359Introduction................................................................................................................................. 359Logic Table .................................................................................................................................. 359Design Entry Method ................................................................................................................... 359
CPLD Libraries Guide20 www.xilinx.com UG606 (v 11.3) September 16, 2009
Available Attributes ..................................................................................................................... 359For More Information ................................................................................................................... 359
FDD16 ............................................................................................................................................... 360Supported Architectures............................................................................................................... 360Introduction................................................................................................................................. 360Logic Table .................................................................................................................................. 360Design Entry Method ................................................................................................................... 360For More Information ................................................................................................................... 360
FDD16CE ........................................................................................................................................... 361Supported Architectures............................................................................................................... 361Introduction................................................................................................................................. 361Logic Table .................................................................................................................................. 361Design Entry Method ................................................................................................................... 361For More Information ................................................................................................................... 361
FDD16RE ........................................................................................................................................... 362Supported Architectures............................................................................................................... 362Introduction................................................................................................................................. 362Logic Table .................................................................................................................................. 362Design Entry Method ................................................................................................................... 362For More Information ................................................................................................................... 362
FDD4 ................................................................................................................................................. 363Supported Architectures............................................................................................................... 363Introduction................................................................................................................................. 363Logic Table .................................................................................................................................. 363Design Entry Method ................................................................................................................... 363For More Information ................................................................................................................... 363
FDD4CE............................................................................................................................................. 364Supported Architectures............................................................................................................... 364Introduction................................................................................................................................. 364Logic Table .................................................................................................................................. 364Design Entry Method ................................................................................................................... 364For More Information ................................................................................................................... 364
FDD4RE............................................................................................................................................. 365Supported Architectures............................................................................................................... 365Introduction................................................................................................................................. 365Logic Table .................................................................................................................................. 365Design Entry Method ................................................................................................................... 365For More Information ................................................................................................................... 365
FDD8 ................................................................................................................................................. 366Supported Architectures............................................................................................................... 366Introduction................................................................................................................................. 366Logic Table .................................................................................................................................. 366Design Entry Method ................................................................................................................... 366For More Information ................................................................................................................... 366
FDD8CE............................................................................................................................................. 367Supported Architectures............................................................................................................... 367Introduction................................................................................................................................. 367Logic Table .................................................................................................................................. 367Design Entry Method ................................................................................................................... 367For More Information ................................................................................................................... 367
FDD8RE............................................................................................................................................. 368Supported Architectures............................................................................................................... 368Introduction................................................................................................................................. 368Logic Table .................................................................................................................................. 368Design Entry Method ................................................................................................................... 368For More Information ................................................................................................................... 368
FDDC ................................................................................................................................................ 369Supported Architectures............................................................................................................... 369Introduction................................................................................................................................. 369
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 21
Logic Table .................................................................................................................................. 369Design Entry Method ................................................................................................................... 369Available Attributes ..................................................................................................................... 369For More Information ................................................................................................................... 369
FDDCE .............................................................................................................................................. 370Supported Architectures............................................................................................................... 370Introduction................................................................................................................................. 370Logic Table .................................................................................................................................. 370Design Entry Method ................................................................................................................... 370Available Attributes ..................................................................................................................... 371For More Information ................................................................................................................... 371
FDDCP .............................................................................................................................................. 372Supported Architectures............................................................................................................... 372Introduction................................................................................................................................. 372Logic Table .................................................................................................................................. 372Design Entry Method ................................................................................................................... 372Available Attributes ..................................................................................................................... 372For More Information ................................................................................................................... 373
FDDCPE ............................................................................................................................................ 374Supported Architectures............................................................................................................... 374Introduction................................................................................................................................. 374Logic Table .................................................................................................................................. 374Design Entry Method ................................................................................................................... 374Available Attributes ..................................................................................................................... 374For More Information ................................................................................................................... 375
FDDP................................................................................................................................................. 376Supported Architectures............................................................................................................... 376Introduction................................................................................................................................. 376Logic Table .................................................................................................................................. 376Design Entry Method ................................................................................................................... 376Available Attributes ..................................................................................................................... 376For More Information ................................................................................................................... 376
FDDPE............................................................................................................................................... 377Supported Architectures............................................................................................................... 377Introduction................................................................................................................................. 377Logic Table .................................................................................................................................. 377Design Entry Method ................................................................................................................... 377Available Attributes ..................................................................................................................... 378For More Information ................................................................................................................... 378
FDDR................................................................................................................................................. 379Supported Architectures............................................................................................................... 379Introduction................................................................................................................................. 379Logic Table .................................................................................................................................. 379Design Entry Method ................................................................................................................... 379Available Attributes ..................................................................................................................... 379For More Information ................................................................................................................... 379
FDDRE............................................................................................................................................... 380Supported Architectures............................................................................................................... 380Introduction................................................................................................................................. 380Logic Table .................................................................................................................................. 380Design Entry Method ................................................................................................................... 380Available Attributes ..................................................................................................................... 380For More Information ................................................................................................................... 381
FDDRS............................................................................................................................................... 382Supported Architectures............................................................................................................... 382Introduction................................................................................................................................. 382Logic Table .................................................................................................................................. 382Design Entry Method ................................................................................................................... 382Available Attributes ..................................................................................................................... 383
CPLD Libraries Guide22 www.xilinx.com UG606 (v 11.3) September 16, 2009
For More Information ................................................................................................................... 383FDDRSE............................................................................................................................................. 384
Supported Architectures............................................................................................................... 384Introduction................................................................................................................................. 384Logic Table .................................................................................................................................. 384Design Entry Method ................................................................................................................... 384Available Attributes ..................................................................................................................... 385For More Information ................................................................................................................... 385
FDDS ................................................................................................................................................. 386Supported Architectures............................................................................................................... 386Introduction................................................................................................................................. 386Logic Table .................................................................................................................................. 386Design Entry Method ................................................................................................................... 386Available Attributes ..................................................................................................................... 386For More Information ................................................................................................................... 387
FDDSE ............................................................................................................................................... 388Supported Architectures............................................................................................................... 388Introduction................................................................................................................................. 388Logic Table .................................................................................................................................. 388Design Entry Method ................................................................................................................... 388Available Attributes ..................................................................................................................... 388For More Information ................................................................................................................... 389
FDDSR............................................................................................................................................... 390Supported Architectures............................................................................................................... 390Introduction................................................................................................................................. 390Logic Table .................................................................................................................................. 390Design Entry Method ................................................................................................................... 390Available Attributes ..................................................................................................................... 391For More Information ................................................................................................................... 391
FDDSRE............................................................................................................................................. 392Supported Architectures............................................................................................................... 392Introduction................................................................................................................................. 392Logic Table .................................................................................................................................. 392Design Entry Method ................................................................................................................... 392Available Attributes ..................................................................................................................... 393For More Information ................................................................................................................... 393
FDP ................................................................................................................................................... 394Supported Architectures............................................................................................................... 394Introduction................................................................................................................................. 394Logic Table .................................................................................................................................. 394Design Entry Method ................................................................................................................... 394Available Attributes ..................................................................................................................... 394For More Information ................................................................................................................... 394
FDPE ................................................................................................................................................. 395Supported Architectures............................................................................................................... 395Introduction................................................................................................................................. 395Logic Table .................................................................................................................................. 395Design Entry Method ................................................................................................................... 395Available Attributes ..................................................................................................................... 395For More Information ................................................................................................................... 396
FDR ................................................................................................................................................... 397Supported Architectures............................................................................................................... 397Introduction................................................................................................................................. 397Logic Table .................................................................................................................................. 397Design Entry Method ................................................................................................................... 397Available Attributes ..................................................................................................................... 397For More Information ................................................................................................................... 397
FDRE ................................................................................................................................................. 398Supported Architectures............................................................................................................... 398
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 23
Introduction................................................................................................................................. 398Logic Table .................................................................................................................................. 398Design Entry Method ................................................................................................................... 398Available Attributes ..................................................................................................................... 398For More Information ................................................................................................................... 399
FDRS ................................................................................................................................................. 400Supported Architectures............................................................................................................... 400Introduction................................................................................................................................. 400Logic Table .................................................................................................................................. 400Design Entry Method ................................................................................................................... 400Available Attributes ..................................................................................................................... 400For More Information ................................................................................................................... 401
FDRSE ............................................................................................................................................... 402Supported Architectures............................................................................................................... 402Introduction................................................................................................................................. 402Logic Table .................................................................................................................................. 402Design Entry Method ................................................................................................................... 402Available Attributes ..................................................................................................................... 402For More Information ................................................................................................................... 403
FDS.................................................................................................................................................... 404Supported Architectures............................................................................................................... 404Introduction................................................................................................................................. 404Logic Table .................................................................................................................................. 404Design Entry Method ................................................................................................................... 404Available Attributes ..................................................................................................................... 404For More Information ................................................................................................................... 404
FDSE.................................................................................................................................................. 405Supported Architectures............................................................................................................... 405Introduction................................................................................................................................. 405Logic Table .................................................................................................................................. 405Design Entry Method ................................................................................................................... 405Available Attributes ..................................................................................................................... 405For More Information ................................................................................................................... 406
FDSR ................................................................................................................................................. 407Supported Architectures............................................................................................................... 407Introduction................................................................................................................................. 407Logic Table .................................................................................................................................. 407Design Entry Method ................................................................................................................... 407Available Attributes ..................................................................................................................... 407For More Information ................................................................................................................... 408
FDSRE ............................................................................................................................................... 409Supported Architectures............................................................................................................... 409Introduction................................................................................................................................. 409Logic Table .................................................................................................................................. 409Design Entry Method ................................................................................................................... 409Available Attributes ..................................................................................................................... 409For More Information ................................................................................................................... 410
FJKC .................................................................................................................................................. 411Supported Architectures............................................................................................................... 411Introduction................................................................................................................................. 411Logic Table .................................................................................................................................. 411Design Entry Method ................................................................................................................... 411Available Attributes ..................................................................................................................... 411For More Information ................................................................................................................... 412
FJKCE ................................................................................................................................................ 413Supported Architectures............................................................................................................... 413Introduction................................................................................................................................. 413Logic Table .................................................................................................................................. 413Design Entry Method ................................................................................................................... 413
CPLD Libraries Guide24 www.xilinx.com UG606 (v 11.3) September 16, 2009
Available Attributes ..................................................................................................................... 413For More Information ................................................................................................................... 414
FJKCP ................................................................................................................................................ 415Supported Architectures............................................................................................................... 415Introduction................................................................................................................................. 415Logic Table .................................................................................................................................. 415Design Entry Method ................................................................................................................... 415Available Attributes ..................................................................................................................... 416For More Information ................................................................................................................... 416
FJKCPE .............................................................................................................................................. 417Supported Architectures............................................................................................................... 417Introduction................................................................................................................................. 417Logic Table .................................................................................................................................. 417Design Entry Method ................................................................................................................... 417Available Attributes ..................................................................................................................... 418For More Information ................................................................................................................... 418
FJKP .................................................................................................................................................. 419Supported Architectures............................................................................................................... 419Introduction................................................................................................................................. 419Logic Table .................................................................................................................................. 419Design Entry Method ................................................................................................................... 419Available Attributes ..................................................................................................................... 419For More Information ................................................................................................................... 420
FJKPE ................................................................................................................................................ 421Supported Architectures............................................................................................................... 421Introduction................................................................................................................................. 421Logic Table .................................................................................................................................. 421Design Entry Method ................................................................................................................... 421Available Attributes ..................................................................................................................... 422For More Information ................................................................................................................... 422
FJKRSE .............................................................................................................................................. 423Supported Architectures............................................................................................................... 423Introduction................................................................................................................................. 423Logic Table .................................................................................................................................. 423Design Entry Method ................................................................................................................... 423Available Attributes ..................................................................................................................... 424For More Information ................................................................................................................... 424
FJKSRE .............................................................................................................................................. 425Supported Architectures............................................................................................................... 425Introduction................................................................................................................................. 425Logic Table .................................................................................................................................. 425Design Entry Method ................................................................................................................... 425Available Attributes ..................................................................................................................... 426For More Information ................................................................................................................... 426
FTC.................................................................................................................................................... 427Supported Architectures............................................................................................................... 427Introduction................................................................................................................................. 427Logic Table .................................................................................................................................. 427Design Entry Method ................................................................................................................... 427Available Attributes ..................................................................................................................... 427For More Information ................................................................................................................... 427
FTCE.................................................................................................................................................. 428Supported Architectures............................................................................................................... 428Introduction................................................................................................................................. 428Logic Table .................................................................................................................................. 428Design Entry Method ................................................................................................................... 428Available Attributes ..................................................................................................................... 428For More Information ................................................................................................................... 428
FTCLE ............................................................................................................................................... 429
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 25
Supported Architectures............................................................................................................... 429Introduction................................................................................................................................. 429Logic Table .................................................................................................................................. 429Design Entry Method ................................................................................................................... 429Available Attributes ..................................................................................................................... 429For More Information ................................................................................................................... 430
FTCLEX ............................................................................................................................................. 431Supported Architectures............................................................................................................... 431Introduction................................................................................................................................. 431Logic Table .................................................................................................................................. 431Design Entry Method ................................................................................................................... 431Available Attributes ..................................................................................................................... 431For More Information ................................................................................................................... 432
FTCP.................................................................................................................................................. 433Supported Architectures............................................................................................................... 433Introduction................................................................................................................................. 433Logic Table .................................................................................................................................. 433Design Entry Method ................................................................................................................... 433Available Attributes ..................................................................................................................... 433For More Information ................................................................................................................... 434
FTCPE................................................................................................................................................ 435Supported Architectures............................................................................................................... 435Introduction................................................................................................................................. 435Logic Table .................................................................................................................................. 435Design Entry Method ................................................................................................................... 435Available Attributes ..................................................................................................................... 435For More Information ................................................................................................................... 436
FTCPLE ............................................................................................................................................. 437Supported Architectures............................................................................................................... 437Introduction................................................................................................................................. 437Logic Table .................................................................................................................................. 437Design Entry Method ................................................................................................................... 438Available Attributes ..................................................................................................................... 438For More Information ................................................................................................................... 438
FTDCE ............................................................................................................................................... 439Supported Architectures............................................................................................................... 439Introduction................................................................................................................................. 439Logic Table .................................................................................................................................. 439Design Entry Method ................................................................................................................... 439Available Attributes ..................................................................................................................... 439For More Information ................................................................................................................... 439
FTDCLE............................................................................................................................................. 440Supported Architectures............................................................................................................... 440Introduction................................................................................................................................. 440Logic Table .................................................................................................................................. 440Design Entry Method ................................................................................................................... 440Available Attributes ..................................................................................................................... 441For More Information ................................................................................................................... 441
FTDCLEX........................................................................................................................................... 442Supported Architectures............................................................................................................... 442Introduction................................................................................................................................. 442Logic Table .................................................................................................................................. 442Design Entry Method ................................................................................................................... 442Available Attributes ..................................................................................................................... 443For More Information ................................................................................................................... 443
FTDCP ............................................................................................................................................... 444Supported Architectures............................................................................................................... 444Introduction................................................................................................................................. 444Logic Table .................................................................................................................................. 444
CPLD Libraries Guide26 www.xilinx.com UG606 (v 11.3) September 16, 2009
Design Entry Method ................................................................................................................... 444Available Attributes ..................................................................................................................... 444For More Information ................................................................................................................... 445
FTDRSE ............................................................................................................................................. 446Supported Architectures............................................................................................................... 446Introduction................................................................................................................................. 446Logic Table .................................................................................................................................. 446Design Entry Method ................................................................................................................... 446Available Attributes ..................................................................................................................... 447For More Information ................................................................................................................... 447
FTDRSLE ........................................................................................................................................... 448Supported Architectures............................................................................................................... 448Introduction................................................................................................................................. 448Logic Table .................................................................................................................................. 449Design Entry Method ................................................................................................................... 449Available Attributes ..................................................................................................................... 449For More Information ................................................................................................................... 449
FTP .................................................................................................................................................... 450Supported Architectures............................................................................................................... 450Introduction................................................................................................................................. 450Logic Table .................................................................................................................................. 450Design Entry Method ................................................................................................................... 450Available Attributes ..................................................................................................................... 450For More Information ................................................................................................................... 450
FTPE.................................................................................................................................................. 451Supported Architectures............................................................................................................... 451Introduction................................................................................................................................. 451Logic Table .................................................................................................................................. 451Design Entry Method ................................................................................................................... 451Available Attributes ..................................................................................................................... 451For More Information ................................................................................................................... 452
FTPLE................................................................................................................................................ 453Supported Architectures............................................................................................................... 453Introduction................................................................................................................................. 453Logic Table .................................................................................................................................. 453Design Entry Method ................................................................................................................... 453Available Attributes ..................................................................................................................... 454For More Information ................................................................................................................... 454
FTRSE ................................................................................................................................................ 455Supported Architectures............................................................................................................... 455Introduction................................................................................................................................. 455Logic Table .................................................................................................................................. 455Design Entry Method ................................................................................................................... 455Available Attributes ..................................................................................................................... 455For More Information ................................................................................................................... 456
FTRSLE.............................................................................................................................................. 457Supported Architectures............................................................................................................... 457Introduction................................................................................................................................. 457Logic Table .................................................................................................................................. 457Design Entry Method ................................................................................................................... 458Available Attributes ..................................................................................................................... 458For More Information ................................................................................................................... 458
FTSRE................................................................................................................................................ 459Supported Architectures............................................................................................................... 459Introduction................................................................................................................................. 459Logic Table .................................................................................................................................. 459Design Entry Method ................................................................................................................... 459Available Attributes ..................................................................................................................... 459For More Information ................................................................................................................... 460
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 27
FTSRLE.............................................................................................................................................. 461Supported Architectures............................................................................................................... 461Introduction................................................................................................................................. 461Logic Table .................................................................................................................................. 461Design Entry Method ................................................................................................................... 461Available Attributes ..................................................................................................................... 462For More Information ................................................................................................................... 462
GND.................................................................................................................................................. 463Supported Architectures............................................................................................................... 463Introduction................................................................................................................................. 463Design Entry Method ................................................................................................................... 463For More Information ................................................................................................................... 463
IBUF .................................................................................................................................................. 464Supported Architectures............................................................................................................... 464Introduction................................................................................................................................. 464Port Descriptions.......................................................................................................................... 464Design Entry Method ................................................................................................................... 464Available Attributes ..................................................................................................................... 464For More Information ................................................................................................................... 465
IBUF16 ............................................................................................................................................... 466Supported Architectures............................................................................................................... 466Introduction................................................................................................................................. 466Design Entry Method ................................................................................................................... 466Available Attributes ..................................................................................................................... 466For More Information ................................................................................................................... 466
IBUF4................................................................................................................................................. 467Supported Architectures............................................................................................................... 467Introduction................................................................................................................................. 467Design Entry Method ................................................................................................................... 467Available Attributes ..................................................................................................................... 467For More Information ................................................................................................................... 467
IBUF8................................................................................................................................................. 468Supported Architectures............................................................................................................... 468Introduction................................................................................................................................. 468Design Entry Method ................................................................................................................... 468Available Attributes ..................................................................................................................... 468For More Information ................................................................................................................... 468
INV.................................................................................................................................................... 469Supported Architectures............................................................................................................... 469Introduction................................................................................................................................. 469Design Entry Method ................................................................................................................... 469For More Information ................................................................................................................... 469
INV16 ................................................................................................................................................ 470Supported Architectures............................................................................................................... 470Introduction................................................................................................................................. 470Design Entry Method ................................................................................................................... 470For More Information ................................................................................................................... 470
INV4.................................................................................................................................................. 471Supported Architectures............................................................................................................... 471Introduction................................................................................................................................. 471Design Entry Method ................................................................................................................... 471For More Information ................................................................................................................... 471
INV8.................................................................................................................................................. 472Supported Architectures............................................................................................................... 472Introduction................................................................................................................................. 472Design Entry Method ................................................................................................................... 472For More Information ................................................................................................................... 472
IOBUFE.............................................................................................................................................. 473Supported Architectures............................................................................................................... 473
CPLD Libraries Guide28 www.xilinx.com UG606 (v 11.3) September 16, 2009
Introduction................................................................................................................................. 473Logic Table .................................................................................................................................. 473Design Entry Method ................................................................................................................... 473For More Information ................................................................................................................... 474
KEEPER ............................................................................................................................................. 475Supported Architectures............................................................................................................... 475Introduction................................................................................................................................. 475Port Descriptions.......................................................................................................................... 475Design Entry Method ................................................................................................................... 475For More Information ................................................................................................................... 476
LD ..................................................................................................................................................... 477Supported Architectures............................................................................................................... 477Introduction................................................................................................................................. 477Logic Table .................................................................................................................................. 477Design Entry Method ................................................................................................................... 477Available Attributes ..................................................................................................................... 477For More Information ................................................................................................................... 477
LD16.................................................................................................................................................. 478Supported Architectures............................................................................................................... 478Introduction................................................................................................................................. 478Logic Table .................................................................................................................................. 478Design Entry Method ................................................................................................................... 478Available Attributes ..................................................................................................................... 478For More Information ................................................................................................................... 478
LD4.................................................................................................................................................... 479Supported Architectures............................................................................................................... 479Introduction................................................................................................................................. 479Logic Table .................................................................................................................................. 479Design Entry Method ................................................................................................................... 479Available Attributes ..................................................................................................................... 479For More Information ................................................................................................................... 480
LD8.................................................................................................................................................... 481Supported Architectures............................................................................................................... 481Introduction................................................................................................................................. 481Logic Table .................................................................................................................................. 481Design Entry Method ................................................................................................................... 481Available Attributes ..................................................................................................................... 481For More Information ................................................................................................................... 481
LDC................................................................................................................................................... 482Supported Architectures............................................................................................................... 482Introduction................................................................................................................................. 482Logic Table .................................................................................................................................. 482Design Entry Method ................................................................................................................... 482Available Attributes ..................................................................................................................... 482For More Information ................................................................................................................... 482
LDCP................................................................................................................................................. 483Supported Architectures............................................................................................................... 483Introduction................................................................................................................................. 483Logic Table .................................................................................................................................. 483Design Entry Method ................................................................................................................... 483Available Attributes ..................................................................................................................... 483For More Information ................................................................................................................... 484
LDG................................................................................................................................................... 485Supported Architectures............................................................................................................... 485Introduction................................................................................................................................. 485Logic Table .................................................................................................................................. 485Design Entry Method ................................................................................................................... 485Available Attributes ..................................................................................................................... 485For More Information ................................................................................................................... 486
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 29
LDG16 ............................................................................................................................................... 487Supported Architectures............................................................................................................... 487Introduction................................................................................................................................. 487Logic Table .................................................................................................................................. 487Design Entry Method ................................................................................................................... 487For More Information ................................................................................................................... 487
LDG4 ................................................................................................................................................. 488Supported Architectures............................................................................................................... 488Introduction................................................................................................................................. 488Logic Table .................................................................................................................................. 488Design Entry Method ................................................................................................................... 488For More Information ................................................................................................................... 488
LDG8 ................................................................................................................................................. 489Supported Architectures............................................................................................................... 489Introduction................................................................................................................................. 489Logic Table .................................................................................................................................. 489Design Entry Method ................................................................................................................... 489For More Information ................................................................................................................... 489
LDP ................................................................................................................................................... 490Supported Architectures............................................................................................................... 490Introduction................................................................................................................................. 490Logic Table .................................................................................................................................. 490Design Entry Method ................................................................................................................... 490Available Attributes ..................................................................................................................... 490For More Information ................................................................................................................... 491
M16_1E .............................................................................................................................................. 492Supported Architectures............................................................................................................... 492Introduction................................................................................................................................. 492Logic Table .................................................................................................................................. 493Design Entry Method ................................................................................................................... 493For More Information ................................................................................................................... 493
M2_1.................................................................................................................................................. 494Supported Architectures............................................................................................................... 494Introduction................................................................................................................................. 494Logic Table .................................................................................................................................. 494Design Entry Method ................................................................................................................... 494For More Information ................................................................................................................... 494
M2_1B1 .............................................................................................................................................. 495Supported Architectures............................................................................................................... 495Introduction................................................................................................................................. 495Logic Table .................................................................................................................................. 495Design Entry Method ................................................................................................................... 495For More Information ................................................................................................................... 495
M2_1B2 .............................................................................................................................................. 496Supported Architectures............................................................................................................... 496Introduction................................................................................................................................. 496Logic Table .................................................................................................................................. 496Design Entry Method ................................................................................................................... 496For More Information ................................................................................................................... 496
M2_1E................................................................................................................................................ 497Supported Architectures............................................................................................................... 497Introduction................................................................................................................................. 497Logic Table .................................................................................................................................. 497Design Entry Method ................................................................................................................... 497For More Information ................................................................................................................... 497
M4_1E................................................................................................................................................ 498Supported Architectures............................................................................................................... 498Introduction................................................................................................................................. 498Logic Table .................................................................................................................................. 498
CPLD Libraries Guide30 www.xilinx.com UG606 (v 11.3) September 16, 2009
Design Entry Method ................................................................................................................... 498For More Information ................................................................................................................... 498
M8_1E................................................................................................................................................ 499Supported Architectures............................................................................................................... 499Introduction................................................................................................................................. 499Logic Table .................................................................................................................................. 499Design Entry Method ................................................................................................................... 499For More Information ................................................................................................................... 500
NAND2 ............................................................................................................................................. 501Supported Architectures............................................................................................................... 501Introduction................................................................................................................................. 501Design Entry Method ................................................................................................................... 501For More Information ................................................................................................................... 501
NAND2B1.......................................................................................................................................... 502Supported Architectures............................................................................................................... 502Introduction................................................................................................................................. 502Design Entry Method ................................................................................................................... 502For More Information ................................................................................................................... 502
NAND2B2.......................................................................................................................................... 503Supported Architectures............................................................................................................... 503Introduction................................................................................................................................. 503Design Entry Method ................................................................................................................... 503For More Information ................................................................................................................... 503
NAND3 ............................................................................................................................................. 504Supported Architectures............................................................................................................... 504Introduction................................................................................................................................. 504Design Entry Method ................................................................................................................... 504For More Information ................................................................................................................... 504
NAND3B1.......................................................................................................................................... 505Supported Architectures............................................................................................................... 505Introduction................................................................................................................................. 505Design Entry Method ................................................................................................................... 505For More Information ................................................................................................................... 505
NAND3B2.......................................................................................................................................... 506Supported Architectures............................................................................................................... 506Introduction................................................................................................................................. 506Design Entry Method ................................................................................................................... 506For More Information ................................................................................................................... 506
NAND3B3.......................................................................................................................................... 507Supported Architectures............................................................................................................... 507Introduction................................................................................................................................. 507Design Entry Method ................................................................................................................... 507For More Information ................................................................................................................... 507
NAND4 ............................................................................................................................................. 508Supported Architectures............................................................................................................... 508Introduction................................................................................................................................. 508Design Entry Method ................................................................................................................... 508For More Information ................................................................................................................... 508
NAND4B1.......................................................................................................................................... 509Supported Architectures............................................................................................................... 509Introduction................................................................................................................................. 509Design Entry Method ................................................................................................................... 509For More Information ................................................................................................................... 509
NAND4B2.......................................................................................................................................... 510Supported Architectures............................................................................................................... 510Introduction................................................................................................................................. 510Design Entry Method ................................................................................................................... 510For More Information ................................................................................................................... 510
NAND4B3.......................................................................................................................................... 511
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 31
Supported Architectures............................................................................................................... 511Introduction................................................................................................................................. 511Design Entry Method ................................................................................................................... 511For More Information ................................................................................................................... 511
NAND4B4.......................................................................................................................................... 512Supported Architectures............................................................................................................... 512Introduction................................................................................................................................. 512Design Entry Method ................................................................................................................... 512For More Information ................................................................................................................... 512
NAND5 ............................................................................................................................................. 513Supported Architectures............................................................................................................... 513Introduction................................................................................................................................. 513Design Entry Method ................................................................................................................... 513For More Information ................................................................................................................... 513
NAND5B1.......................................................................................................................................... 514Supported Architectures............................................................................................................... 514Introduction................................................................................................................................. 514Design Entry Method ................................................................................................................... 514For More Information ................................................................................................................... 514
NAND5B2.......................................................................................................................................... 515Supported Architectures............................................................................................................... 515Introduction................................................................................................................................. 515Design Entry Method ................................................................................................................... 515For More Information ................................................................................................................... 515
NAND5B3.......................................................................................................................................... 516Supported Architectures............................................................................................................... 516Introduction................................................................................................................................. 516Design Entry Method ................................................................................................................... 516For More Information ................................................................................................................... 516
NAND5B4.......................................................................................................................................... 517Supported Architectures............................................................................................................... 517Introduction................................................................................................................................. 517Design Entry Method ................................................................................................................... 517For More Information ................................................................................................................... 517
NAND5B5.......................................................................................................................................... 518Supported Architectures............................................................................................................... 518Introduction................................................................................................................................. 518Design Entry Method ................................................................................................................... 518For More Information ................................................................................................................... 518
NAND6 ............................................................................................................................................. 519Supported Architectures............................................................................................................... 519Introduction................................................................................................................................. 519Design Entry Method ................................................................................................................... 519For More Information ................................................................................................................... 519
NAND7 ............................................................................................................................................. 520Supported Architectures............................................................................................................... 520Introduction................................................................................................................................. 520Design Entry Method ................................................................................................................... 520For More Information ................................................................................................................... 520
NAND8 ............................................................................................................................................. 521Supported Architectures............................................................................................................... 521Introduction................................................................................................................................. 521Design Entry Method ................................................................................................................... 521For More Information ................................................................................................................... 521
NAND9 ............................................................................................................................................. 522Supported Architectures............................................................................................................... 522Introduction................................................................................................................................. 522Design Entry Method ................................................................................................................... 522For More Information ................................................................................................................... 522
CPLD Libraries Guide32 www.xilinx.com UG606 (v 11.3) September 16, 2009
NOR2................................................................................................................................................. 523Supported Architectures............................................................................................................... 523Introduction................................................................................................................................. 523Design Entry Method ................................................................................................................... 523For More Information ................................................................................................................... 523
NOR2B1............................................................................................................................................. 524Supported Architectures............................................................................................................... 524Introduction................................................................................................................................. 524Design Entry Method ................................................................................................................... 524For More Information ................................................................................................................... 524
NOR2B2............................................................................................................................................. 525Supported Architectures............................................................................................................... 525Introduction................................................................................................................................. 525Design Entry Method ................................................................................................................... 525For More Information ................................................................................................................... 525
NOR3................................................................................................................................................. 526Supported Architectures............................................................................................................... 526Introduction................................................................................................................................. 526Design Entry Method ................................................................................................................... 526For More Information ................................................................................................................... 526
NOR3B1............................................................................................................................................. 527Supported Architectures............................................................................................................... 527Introduction................................................................................................................................. 527Design Entry Method ................................................................................................................... 527For More Information ................................................................................................................... 527
NOR3B2............................................................................................................................................. 528Supported Architectures............................................................................................................... 528Introduction................................................................................................................................. 528Design Entry Method ................................................................................................................... 528For More Information ................................................................................................................... 528
NOR3B3............................................................................................................................................. 529Supported Architectures............................................................................................................... 529Introduction................................................................................................................................. 529Design Entry Method ................................................................................................................... 529For More Information ................................................................................................................... 529
NOR4................................................................................................................................................. 530Supported Architectures............................................................................................................... 530Introduction................................................................................................................................. 530Design Entry Method ................................................................................................................... 530For More Information ................................................................................................................... 530
NOR4B1............................................................................................................................................. 531Supported Architectures............................................................................................................... 531Introduction................................................................................................................................. 531Design Entry Method ................................................................................................................... 531For More Information ................................................................................................................... 531
NOR4B2............................................................................................................................................. 532Supported Architectures............................................................................................................... 532Introduction................................................................................................................................. 532Design Entry Method ................................................................................................................... 532For More Information ................................................................................................................... 532
NOR4B3............................................................................................................................................. 533Supported Architectures............................................................................................................... 533Introduction................................................................................................................................. 533Design Entry Method ................................................................................................................... 533For More Information ................................................................................................................... 533
NOR4B4............................................................................................................................................. 534Supported Architectures............................................................................................................... 534Introduction................................................................................................................................. 534Design Entry Method ................................................................................................................... 534
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 33
For More Information ................................................................................................................... 534NOR5................................................................................................................................................. 535
Supported Architectures............................................................................................................... 535Introduction................................................................................................................................. 535Design Entry Method ................................................................................................................... 535For More Information ................................................................................................................... 535
NOR5B1............................................................................................................................................. 536Supported Architectures............................................................................................................... 536Introduction................................................................................................................................. 536Design Entry Method ................................................................................................................... 536For More Information ................................................................................................................... 536
NOR5B2............................................................................................................................................. 537Supported Architectures............................................................................................................... 537Introduction................................................................................................................................. 537Design Entry Method ................................................................................................................... 537For More Information ................................................................................................................... 537
NOR5B3............................................................................................................................................. 538Supported Architectures............................................................................................................... 538Introduction................................................................................................................................. 538Design Entry Method ................................................................................................................... 538For More Information ................................................................................................................... 538
NOR5B4............................................................................................................................................. 539Supported Architectures............................................................................................................... 539Introduction................................................................................................................................. 539Design Entry Method ................................................................................................................... 539For More Information ................................................................................................................... 539
NOR5B5............................................................................................................................................. 540Supported Architectures............................................................................................................... 540Introduction................................................................................................................................. 540Design Entry Method ................................................................................................................... 540For More Information ................................................................................................................... 540
NOR6................................................................................................................................................. 541Supported Architectures............................................................................................................... 541Introduction................................................................................................................................. 541Design Entry Method ................................................................................................................... 541For More Information ................................................................................................................... 541
NOR7................................................................................................................................................. 542Supported Architectures............................................................................................................... 542Introduction................................................................................................................................. 542Design Entry Method ................................................................................................................... 542For More Information ................................................................................................................... 542
NOR8................................................................................................................................................. 543Supported Architectures............................................................................................................... 543Introduction................................................................................................................................. 543Design Entry Method ................................................................................................................... 543For More Information ................................................................................................................... 543
NOR9................................................................................................................................................. 544Supported Architectures............................................................................................................... 544Introduction................................................................................................................................. 544Design Entry Method ................................................................................................................... 544For More Information ................................................................................................................... 544
OBUF................................................................................................................................................. 545Supported Architectures............................................................................................................... 545Introduction................................................................................................................................. 545Port Descriptions.......................................................................................................................... 545Design Entry Method ................................................................................................................... 545Available Attributes ..................................................................................................................... 545For More Information ................................................................................................................... 546
OBUF16 ............................................................................................................................................. 547
CPLD Libraries Guide34 www.xilinx.com UG606 (v 11.3) September 16, 2009
Supported Architectures............................................................................................................... 547Introduction................................................................................................................................. 547Design Entry Method ................................................................................................................... 547Available Attributes ..................................................................................................................... 547For More Information ................................................................................................................... 547
OBUF4 ............................................................................................................................................... 548Supported Architectures............................................................................................................... 548Introduction................................................................................................................................. 548Design Entry Method ................................................................................................................... 548Available Attributes ..................................................................................................................... 548For More Information ................................................................................................................... 548
OBUF8 ............................................................................................................................................... 549Supported Architectures............................................................................................................... 549Introduction................................................................................................................................. 549Design Entry Method ................................................................................................................... 549Available Attributes ..................................................................................................................... 549For More Information ................................................................................................................... 549
OBUFE............................................................................................................................................... 550Supported Architectures............................................................................................................... 550Introduction................................................................................................................................. 550Logic Table .................................................................................................................................. 550Design Entry Method ................................................................................................................... 550For More Information ................................................................................................................... 550
OBUFE16 ........................................................................................................................................... 551Supported Architectures............................................................................................................... 551Introduction................................................................................................................................. 551Logic Table .................................................................................................................................. 551Design Entry Method ................................................................................................................... 551For More Information ................................................................................................................... 551
OBUFE4 ............................................................................................................................................. 552Supported Architectures............................................................................................................... 552Introduction................................................................................................................................. 552Logic Table .................................................................................................................................. 552Design Entry Method ................................................................................................................... 552For More Information ................................................................................................................... 552
OBUFE8 ............................................................................................................................................. 553Supported Architectures............................................................................................................... 553Introduction................................................................................................................................. 553Logic Table .................................................................................................................................. 553Design Entry Method ................................................................................................................... 553For More Information ................................................................................................................... 553
OBUFT............................................................................................................................................... 554Supported Architectures............................................................................................................... 554Introduction................................................................................................................................. 554Logic Table .................................................................................................................................. 554Port Descriptions.......................................................................................................................... 554Design Entry Method ................................................................................................................... 554Available Attributes ..................................................................................................................... 554For More Information ................................................................................................................... 555
OBUFT16 ........................................................................................................................................... 556Supported Architectures............................................................................................................... 556Introduction................................................................................................................................. 556Logic Table .................................................................................................................................. 556Design Entry Method ................................................................................................................... 556Available Attributes ..................................................................................................................... 556For More Information ................................................................................................................... 556
OBUFT4 ............................................................................................................................................. 557Supported Architectures............................................................................................................... 557Introduction................................................................................................................................. 557
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 35
Logic Table .................................................................................................................................. 557Design Entry Method ................................................................................................................... 557Available Attributes ..................................................................................................................... 557For More Information ................................................................................................................... 557
OBUFT8 ............................................................................................................................................. 558Supported Architectures............................................................................................................... 558Introduction................................................................................................................................. 558Logic Table .................................................................................................................................. 558Design Entry Method ................................................................................................................... 558Available Attributes ..................................................................................................................... 558For More Information ................................................................................................................... 558
OR2 ................................................................................................................................................... 559Supported Architectures............................................................................................................... 559Introduction................................................................................................................................. 559Design Entry Method ................................................................................................................... 559For More Information ................................................................................................................... 559
OR2B1................................................................................................................................................ 560Supported Architectures............................................................................................................... 560Introduction................................................................................................................................. 560Design Entry Method ................................................................................................................... 560For More Information ................................................................................................................... 560
OR2B2................................................................................................................................................ 561Supported Architectures............................................................................................................... 561Introduction................................................................................................................................. 561Design Entry Method ................................................................................................................... 561For More Information ................................................................................................................... 561
OR3 ................................................................................................................................................... 562Supported Architectures............................................................................................................... 562Introduction................................................................................................................................. 562Design Entry Method ................................................................................................................... 562For More Information ................................................................................................................... 562
OR3B1................................................................................................................................................ 563Supported Architectures............................................................................................................... 563Introduction................................................................................................................................. 563Design Entry Method ................................................................................................................... 563For More Information ................................................................................................................... 563
OR3B2................................................................................................................................................ 564Supported Architectures............................................................................................................... 564Introduction................................................................................................................................. 564Design Entry Method ................................................................................................................... 564For More Information ................................................................................................................... 564
OR3B3................................................................................................................................................ 565Supported Architectures............................................................................................................... 565Introduction................................................................................................................................. 565Design Entry Method ................................................................................................................... 565For More Information ................................................................................................................... 565
OR4 ................................................................................................................................................... 566Supported Architectures............................................................................................................... 566Introduction................................................................................................................................. 566Design Entry Method ................................................................................................................... 566For More Information ................................................................................................................... 566
OR4B1................................................................................................................................................ 567Supported Architectures............................................................................................................... 567Introduction................................................................................................................................. 567Design Entry Method ................................................................................................................... 567For More Information ................................................................................................................... 567
OR4B2................................................................................................................................................ 568Supported Architectures............................................................................................................... 568Introduction................................................................................................................................. 568
CPLD Libraries Guide36 www.xilinx.com UG606 (v 11.3) September 16, 2009
Design Entry Method ................................................................................................................... 568For More Information ................................................................................................................... 568
OR4B3................................................................................................................................................ 569Supported Architectures............................................................................................................... 569Introduction................................................................................................................................. 569Design Entry Method ................................................................................................................... 569For More Information ................................................................................................................... 569
OR4B4................................................................................................................................................ 570Supported Architectures............................................................................................................... 570Introduction................................................................................................................................. 570Design Entry Method ................................................................................................................... 570For More Information ................................................................................................................... 570
OR5 ................................................................................................................................................... 571Supported Architectures............................................................................................................... 571Introduction................................................................................................................................. 571Design Entry Method ................................................................................................................... 571For More Information ................................................................................................................... 571
OR5B1................................................................................................................................................ 572Supported Architectures............................................................................................................... 572Introduction................................................................................................................................. 572Design Entry Method ................................................................................................................... 572For More Information ................................................................................................................... 572
OR5B2................................................................................................................................................ 573Supported Architectures............................................................................................................... 573Introduction................................................................................................................................. 573Design Entry Method ................................................................................................................... 573For More Information ................................................................................................................... 573
OR5B3................................................................................................................................................ 574Supported Architectures............................................................................................................... 574Introduction................................................................................................................................. 574Design Entry Method ................................................................................................................... 574For More Information ................................................................................................................... 574
OR5B4................................................................................................................................................ 575Supported Architectures............................................................................................................... 575Introduction................................................................................................................................. 575Design Entry Method ................................................................................................................... 575For More Information ................................................................................................................... 575
OR5B5................................................................................................................................................ 576Supported Architectures............................................................................................................... 576Introduction................................................................................................................................. 576Design Entry Method ................................................................................................................... 576For More Information ................................................................................................................... 576
OR6 ................................................................................................................................................... 577Supported Architectures............................................................................................................... 577Introduction................................................................................................................................. 577Design Entry Method ................................................................................................................... 577For More Information ................................................................................................................... 577
OR7 ................................................................................................................................................... 578Supported Architectures............................................................................................................... 578Introduction................................................................................................................................. 578Design Entry Method ................................................................................................................... 578For More Information ................................................................................................................... 578
OR8 ................................................................................................................................................... 579Supported Architectures............................................................................................................... 579Introduction................................................................................................................................. 579Design Entry Method ................................................................................................................... 579For More Information ................................................................................................................... 579
OR9 ................................................................................................................................................... 580Supported Architectures............................................................................................................... 580
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 37
Introduction................................................................................................................................. 580Design Entry Method ................................................................................................................... 580For More Information ................................................................................................................... 580
PULLDOWN...................................................................................................................................... 581Supported Architectures............................................................................................................... 581Introduction................................................................................................................................. 581Port Descriptions.......................................................................................................................... 581Design Entry Method ................................................................................................................... 581For More Information ................................................................................................................... 582
PULLUP............................................................................................................................................. 583Supported Architectures............................................................................................................... 583Introduction................................................................................................................................. 583Port Descriptions.......................................................................................................................... 583Design Entry Method ................................................................................................................... 583For More Information ................................................................................................................... 584
SR16CE .............................................................................................................................................. 585Supported Architectures............................................................................................................... 585Introduction................................................................................................................................. 585Logic Table .................................................................................................................................. 585Design Entry Method ................................................................................................................... 585For More Information ................................................................................................................... 586
SR16CLE ............................................................................................................................................ 587Supported Architectures............................................................................................................... 587Introduction................................................................................................................................. 587Logic Table .................................................................................................................................. 587Design Entry Method ................................................................................................................... 588For More Information ................................................................................................................... 588
SR16CLED.......................................................................................................................................... 589Supported Architectures............................................................................................................... 589Introduction................................................................................................................................. 589Logic Table .................................................................................................................................. 589Design Entry Method ................................................................................................................... 590For More Information ................................................................................................................... 590
SR16RE .............................................................................................................................................. 591Supported Architectures............................................................................................................... 591Introduction................................................................................................................................. 591Logic Table .................................................................................................................................. 591Design Entry Method ................................................................................................................... 591For More Information ................................................................................................................... 592
SR16RLE ............................................................................................................................................ 593Supported Architectures............................................................................................................... 593Introduction................................................................................................................................. 593Logic Table .................................................................................................................................. 594Design Entry Method ................................................................................................................... 594For More Information ................................................................................................................... 594
SR16RLED.......................................................................................................................................... 595Supported Architectures............................................................................................................... 595Introduction................................................................................................................................. 595Logic Table .................................................................................................................................. 596Design Entry Method ................................................................................................................... 596For More Information ................................................................................................................... 596
SR4CE................................................................................................................................................ 597Supported Architectures............................................................................................................... 597Introduction................................................................................................................................. 597Logic Table .................................................................................................................................. 597Design Entry Method ................................................................................................................... 597For More Information ................................................................................................................... 598
SR4CLE.............................................................................................................................................. 599Supported Architectures............................................................................................................... 599
CPLD Libraries Guide38 www.xilinx.com UG606 (v 11.3) September 16, 2009
Introduction................................................................................................................................. 599Logic Table .................................................................................................................................. 600Design Entry Method ................................................................................................................... 600For More Information ................................................................................................................... 600
SR4CLED ........................................................................................................................................... 601Supported Architectures............................................................................................................... 601Introduction................................................................................................................................. 601Logic Table .................................................................................................................................. 602Design Entry Method ................................................................................................................... 602For More Information ................................................................................................................... 602
SR4RE................................................................................................................................................ 603Supported Architectures............................................................................................................... 603Introduction................................................................................................................................. 603Logic Table .................................................................................................................................. 603Design Entry Method ................................................................................................................... 603For More Information ................................................................................................................... 604
SR4RLE.............................................................................................................................................. 605Supported Architectures............................................................................................................... 605Introduction................................................................................................................................. 605Logic Table .................................................................................................................................. 606Design Entry Method ................................................................................................................... 606For More Information ................................................................................................................... 606
SR4RLED ........................................................................................................................................... 607Supported Architectures............................................................................................................... 607Introduction................................................................................................................................. 607Logic Table .................................................................................................................................. 608Design Entry Method ................................................................................................................... 608For More Information ................................................................................................................... 608
SR8CE................................................................................................................................................ 609Supported Architectures............................................................................................................... 609Introduction................................................................................................................................. 609Logic Table .................................................................................................................................. 609Design Entry Method ................................................................................................................... 609For More Information ................................................................................................................... 610
SR8CLE.............................................................................................................................................. 611Supported Architectures............................................................................................................... 611Introduction................................................................................................................................. 611Logic Table .................................................................................................................................. 611Design Entry Method ................................................................................................................... 612For More Information ................................................................................................................... 612
SR8CLED ........................................................................................................................................... 613Supported Architectures............................................................................................................... 613Introduction................................................................................................................................. 613Logic Table .................................................................................................................................. 613Design Entry Method ................................................................................................................... 614For More Information ................................................................................................................... 614
SR8RE................................................................................................................................................ 615Supported Architectures............................................................................................................... 615Introduction................................................................................................................................. 615Logic Table .................................................................................................................................. 615Design Entry Method ................................................................................................................... 615For More Information ................................................................................................................... 616
SR8RLE.............................................................................................................................................. 617Supported Architectures............................................................................................................... 617Introduction................................................................................................................................. 617Logic Table .................................................................................................................................. 618Design Entry Method ................................................................................................................... 618For More Information ................................................................................................................... 618
SR8RLED ........................................................................................................................................... 619
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 39
Supported Architectures............................................................................................................... 619Introduction................................................................................................................................. 619Logic Table .................................................................................................................................. 620Design Entry Method ................................................................................................................... 620For More Information ................................................................................................................... 620
SRD16CE............................................................................................................................................ 621Supported Architectures............................................................................................................... 621Introduction................................................................................................................................. 621Logic Table .................................................................................................................................. 621Design Entry Method ................................................................................................................... 621For More Information ................................................................................................................... 622
SRD16CLE.......................................................................................................................................... 623Supported Architectures............................................................................................................... 623Introduction................................................................................................................................. 623Logic Table .................................................................................................................................. 624Design Entry Method ................................................................................................................... 624For More Information ................................................................................................................... 624
SRD16CLED....................................................................................................................................... 625Supported Architectures............................................................................................................... 625Introduction................................................................................................................................. 625Logic Table .................................................................................................................................. 626Design Entry Method ................................................................................................................... 626For More Information ................................................................................................................... 626
SRD16RE............................................................................................................................................ 627Supported Architectures............................................................................................................... 627Introduction................................................................................................................................. 627Logic Table .................................................................................................................................. 627Design Entry Method ................................................................................................................... 628For More Information ................................................................................................................... 628
SRD16RLE.......................................................................................................................................... 629Supported Architectures............................................................................................................... 629Introduction................................................................................................................................. 629Logic Table .................................................................................................................................. 630Design Entry Method ................................................................................................................... 630For More Information ................................................................................................................... 630
SRD16RLED ....................................................................................................................................... 631Supported Architectures............................................................................................................... 631Introduction................................................................................................................................. 631Logic Table .................................................................................................................................. 632Design Entry Method ................................................................................................................... 632For More Information ................................................................................................................... 632
SRD4CE ............................................................................................................................................. 633Supported Architectures............................................................................................................... 633Introduction................................................................................................................................. 633Logic Table .................................................................................................................................. 633Design Entry Method ................................................................................................................... 633For More Information ................................................................................................................... 634
SRD4CLE ........................................................................................................................................... 635Supported Architectures............................................................................................................... 635Introduction................................................................................................................................. 635Logic Table .................................................................................................................................. 636Design Entry Method ................................................................................................................... 636For More Information ................................................................................................................... 636
SRD4CLED......................................................................................................................................... 637Supported Architectures............................................................................................................... 637Introduction................................................................................................................................. 637Logic Table .................................................................................................................................. 638Design Entry Method ................................................................................................................... 638For More Information ................................................................................................................... 638
CPLD Libraries Guide40 www.xilinx.com UG606 (v 11.3) September 16, 2009
SRD4RE ............................................................................................................................................. 639Supported Architectures............................................................................................................... 639Introduction................................................................................................................................. 639Logic Table .................................................................................................................................. 639Design Entry Method ................................................................................................................... 640For More Information ................................................................................................................... 640
SRD4RLE ........................................................................................................................................... 641Supported Architectures............................................................................................................... 641Introduction................................................................................................................................. 641Logic Table .................................................................................................................................. 642Design Entry Method ................................................................................................................... 642For More Information ................................................................................................................... 642
SRD4RLED......................................................................................................................................... 643Supported Architectures............................................................................................................... 643Introduction................................................................................................................................. 643Logic Table .................................................................................................................................. 644Design Entry Method ................................................................................................................... 644For More Information ................................................................................................................... 644
SRD8CE ............................................................................................................................................. 645Supported Architectures............................................................................................................... 645Introduction................................................................................................................................. 645Logic Table .................................................................................................................................. 645Design Entry Method ................................................................................................................... 645For More Information ................................................................................................................... 646
SRD8CLE ........................................................................................................................................... 647Supported Architectures............................................................................................................... 647Introduction................................................................................................................................. 647Logic Table .................................................................................................................................. 648Design Entry Method ................................................................................................................... 648For More Information ................................................................................................................... 648
SRD8CLED......................................................................................................................................... 649Supported Architectures............................................................................................................... 649Introduction................................................................................................................................. 649Logic Table .................................................................................................................................. 650Design Entry Method ................................................................................................................... 650For More Information ................................................................................................................... 650
SRD8RE ............................................................................................................................................. 651Supported Architectures............................................................................................................... 651Introduction................................................................................................................................. 651Logic Table .................................................................................................................................. 651Design Entry Method ................................................................................................................... 652For More Information ................................................................................................................... 652
SRD8RLE ........................................................................................................................................... 653Supported Architectures............................................................................................................... 653Introduction................................................................................................................................. 653Logic Table .................................................................................................................................. 654Design Entry Method ................................................................................................................... 654For More Information ................................................................................................................... 654
SRD8RLED......................................................................................................................................... 655Supported Architectures............................................................................................................... 655Introduction................................................................................................................................. 655Logic Table .................................................................................................................................. 656Design Entry Method ................................................................................................................... 656For More Information ................................................................................................................... 656
VCC................................................................................................................................................... 657Supported Architectures............................................................................................................... 657Introduction................................................................................................................................. 657Design Entry Method ................................................................................................................... 657For More Information ................................................................................................................... 657
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 41
XNOR2 .............................................................................................................................................. 658Supported Architectures............................................................................................................... 658Introduction................................................................................................................................. 658Logic Table .................................................................................................................................. 658Design Entry Method ................................................................................................................... 658For More Information ................................................................................................................... 658
XNOR3 .............................................................................................................................................. 659Supported Architectures............................................................................................................... 659Introduction................................................................................................................................. 659Logic Table .................................................................................................................................. 659Design Entry Method ................................................................................................................... 659For More Information ................................................................................................................... 659
XNOR4 .............................................................................................................................................. 660Supported Architectures............................................................................................................... 660Introduction................................................................................................................................. 660Logic Table .................................................................................................................................. 660Design Entry Method ................................................................................................................... 660For More Information ................................................................................................................... 660
XNOR5 .............................................................................................................................................. 661Supported Architectures............................................................................................................... 661Introduction................................................................................................................................. 661Logic Table .................................................................................................................................. 661Design Entry Method ................................................................................................................... 661For More Information ................................................................................................................... 661
XNOR6 .............................................................................................................................................. 662Supported Architectures............................................................................................................... 662Introduction................................................................................................................................. 662Logic Table .................................................................................................................................. 662Design Entry Method ................................................................................................................... 662For More Information ................................................................................................................... 662
XNOR7 .............................................................................................................................................. 663Supported Architectures............................................................................................................... 663Introduction................................................................................................................................. 663Logic Table .................................................................................................................................. 663Design Entry Method ................................................................................................................... 663For More Information ................................................................................................................... 663
XNOR8 .............................................................................................................................................. 664Supported Architectures............................................................................................................... 664Introduction................................................................................................................................. 664Logic Table .................................................................................................................................. 664Design Entry Method ................................................................................................................... 664For More Information ................................................................................................................... 664
XNOR9 .............................................................................................................................................. 665Supported Architectures............................................................................................................... 665Introduction................................................................................................................................. 665Logic Table .................................................................................................................................. 665Design Entry Method ................................................................................................................... 665For More Information ................................................................................................................... 665
XOR2 ................................................................................................................................................. 666Supported Architectures............................................................................................................... 666Introduction................................................................................................................................. 666Design Entry Method ................................................................................................................... 666For More Information ................................................................................................................... 666
XOR3 ................................................................................................................................................. 667Supported Architectures............................................................................................................... 667Introduction................................................................................................................................. 667Design Entry Method ................................................................................................................... 667For More Information ................................................................................................................... 667
XOR4 ................................................................................................................................................. 668
CPLD Libraries Guide42 www.xilinx.com UG606 (v 11.3) September 16, 2009
Supported Architectures............................................................................................................... 668Introduction................................................................................................................................. 668Design Entry Method ................................................................................................................... 668For More Information ................................................................................................................... 668
XOR5 ................................................................................................................................................. 669Supported Architectures............................................................................................................... 669Introduction................................................................................................................................. 669Design Entry Method ................................................................................................................... 669For More Information ................................................................................................................... 669
XOR6 ................................................................................................................................................. 670Supported Architectures............................................................................................................... 670Introduction................................................................................................................................. 670Design Entry Method ................................................................................................................... 670For More Information ................................................................................................................... 670
XOR7 ................................................................................................................................................. 671Supported Architectures............................................................................................................... 671Introduction................................................................................................................................. 671Design Entry Method ................................................................................................................... 671For More Information ................................................................................................................... 671
XOR8 ................................................................................................................................................. 672Supported Architectures............................................................................................................... 672Introduction................................................................................................................................. 672Design Entry Method ................................................................................................................... 672For More Information ................................................................................................................... 672
XOR9 ................................................................................................................................................. 673Supported Architectures............................................................................................................... 673Introduction................................................................................................................................. 673Design Entry Method ................................................................................................................... 673For More Information ................................................................................................................... 673
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 43
Chapter 1
About this GuideThis schematic guide is part of the ISE documentation collection. A separate version of this guide is available ifyou prefer to work with HDL.
This guide contains the following:
• Introduction.
• A list of design elements supported in this architecture, organized by functional categories.
• Individual descriptions of each available primitive.
About Design ElementsThis version of the Libraries Guide describes design elements available for this architecture. There are severalcategories of design elements:
• Primitives - The simplest design elements in the Xilinx libraries. Primitives are the design element "atoms."Examples of Xilinx primitives are the simple buffer, BUF, and the D flip-flop with clock enable and clear,FDCE.
• Macros - The design element "molecules" of the Xilinx libraries. Macros can be created from the designelement primitives or macros. For example, the FD4CE flip-flop macro is a composite of 4 FDCE primitives.
Xilinx maintains software libraries with hundreds of functional design elements (macros and primitives) fordifferent device architectures. New functional elements are assembled with each release of development systemsoftware. This guide is one in a series of architecture-specific libraries.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 45
Chapter 2
Functional CategoriesThis section categorizes, by function, the circuit design elements described in detail later in this guide. Theelements ( primitives and macros) are listed in alphanumeric order under each functional category.
Arithmetic Flip Flop Shift Register
Buffer General Shifter
Clock Divider IO
Comparator Latch
Counter Logic
Decoder Mux
ArithmeticDesign Element Description
ACC1 Macro: 1-Bit Loadable Cascadable Accumulator with Carry-In, Carry-Out, andSynchronous Reset
ACC16 Macro: 16-Bit Loadable Cascadable Accumulator with Carry-In, Carry-Out, andSynchronous Reset
ACC4 Macro: 4-Bit Loadable Cascadable Accumulator with Carry-In, Carry-Out, andSynchronous Reset
ACC8 Macro: 8-Bit Loadable Cascadable Accumulator with Carry-In, Carry-Out, andSynchronous Reset
ADD1 Macro: 1-Bit Full Adder with Carry-In and Carry-Out
ADD16 Macro: 16-Bit Cascadable Full Adder with Carry-In, Carry-Out, and Overflow
ADD4 Macro: 4-Bit Cascadable Full Adder with Carry-In, Carry-Out, and Overflow
ADD8 Macro: 8-Bit Cascadable Full Adder with Carry-In, Carry-Out, and Overflow
ADSU1 Macro: 1-Bit Cascadable Adder/Subtracter with Carry-In, Carry-Out
ADSU16 Macro: 16-Bit Cascadable Adder/Subtracter with Carry-In, Carry-Out, and Overflow
ADSU4 Macro: 4-Bit Cascadable Adder/Subtracter with Carry-In, Carry-Out, and Overflow
ADSU8 Macro: 8-Bit Cascadable Adder/Subtracter with Carry-In, Carry-Out, and Overflow
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 47
Chapter 2: Functional Categories
BufferDesign Element Description
BUF Primitive: General Purpose Buffer
BUF16 Macro: 16-Bit General Purpose Buffer
BUF4 Macro: 4-Bit General Purpose Buffer
BUF8 Macro: 8-Bit General Purpose Buffer
BUFE Primitive: Internal 3-State Buffer with Active High Enable
BUFE16 Macro: 16-Bit Internal 3-State Buffer with Active High Enable
BUFE4 Macro: 4-BitInternal 3-State Buffer with Active High Enable
BUFE8 Macro: 8-Bit Internal 3-State Buffer with Active High Enable
BUFG Primitive: Global Clock Buffer
BUFGSR Primitive: Global Set/Reset Input Buffer
BUFGTS Primitive: Global 3-State Input Buffer
BUFT Primitive: Internal 3-State Buffer with Active Low Enable
BUFT16 Macro: 16-Bit Internal 3-State Buffers with Active Low Enable
BUFT4 Macro: 4-Bit Internal 3-State Buffers with Active Low Enable
BUFT8 Macro: 8-Bit Internal 3-State Buffers with Active Low Enable
CPLD Libraries Guide48 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 2: Functional Categories
Clock DividerDesign Element Description
CLK_DIV10 Primitive: Simple Global Clock Divide by 10
CLK_DIV10R Primitive: Global Clock Divide by 10 with Synchronous Reset
CLK_DIV10RSD Primitive: Global Clock Divide by 10 with Synchronous Reset and Start Delay
CLK_DIV10SD Primitive: Global Clock Divide by 10 with Start Delay
CLK_DIV12 Primitive: Simple Global Clock Divide by 12
CLK_DIV12R Primitive: Global Clock Divide by 12 with Synchronous Reset
CLK_DIV12RSD Primitive: Global Clock Divide by 12 with Synchronous Reset and Start Delay
CLK_DIV12SD Primitive: Global Clock Divide by 12 with Start Delay
CLK_DIV14R Primitive: Global Clock Divide by 14 with Synchronous Reset
CLK_DIV14RSD Primitive: Global Clock Divide by 14 with Synchronous Reset and Start Delay
CLK_DIV14SD Primitive: Global Clock Divide by 14 with Start Delay
CLK_DIV16 Primitive: Simple Global Clock Divide by 16
CLK_DIV16R Primitive: Global Clock Divide by 16 with Synchronous Reset
CLK_DIV16RSD Primitive: Global Clock Divide by 16 with Synchronous Reset and Start Delay
CLK_DIV16SD Primitive: Global Clock Divide by 16 with Start Delay
CLK_DIV2 Primitive: Simple Global Clock Divide by 2
CLK_DIV2R Primitive: Global Clock Divide by 2 with Synchronous Reset
CLK_DIV2RSD Primitive: Global Clock Divide by 2 with Synchronous Reset and Start Delay
CLK_DIV2SD Primitive: Global Clock Divide by 2 with Start Delay
CLK_DIV4 Primitive: Simple Global Clock Divide by 4
CLK_DIV4R Primitive: Global Clock Divide by 4 with Synchronous Reset
CLK_DIV4RSD Primitive: Global Clock Divide by 4 with Synchronous Reset and Start Delay
CLK_DIV4SD Primitive: Global Clock Divide by 4 with Start Delay
CLK_DIV6 Primitive: Simple Global Clock Divide by 6
CLK_DIV6R Primitive: Global Clock Divide by 6 with Synchronous Reset
CLK_DIV6RSD Primitive: Global Clock Divide by 6 with Synchronous Reset and Start Delay
CLK_DIV6SD Primitive: Global Clock Divide by 6 with Start Delay
CLK_DIV8 Primitive: Simple Global Clock Divide by 8
CLK_DIV8R Primitive: Global Clock Divide by 8 with Synchronous Reset
CLK_DIV8RSD Primitive: Global Clock Divide by 8 with Synchronous Reset and Start Delay
CLK_DIV8SD Primitive: Global Clock Divide by 8 with Start Delay
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 49
Chapter 2: Functional Categories
ComparatorDesign Element Description
COMP16 Macro: 16-Bit Identity Comparator
COMP2 Macro: 2-Bit Identity Comparator
COMP4 Macro: 4-Bit Identity Comparator
COMP8 Macro: 8-Bit Identity Comparator
COMPM16 Macro: 16-Bit Magnitude Comparator
COMPM2 Macro: 2-Bit Magnitude Comparator
COMPM4 Macro: 4-Bit Magnitude Comparator
COMPM8 Macro: 8-Bit Magnitude Comparator
CounterDesign Element Description
CB16CE Macro: 16-Bit Cascadable Binary Counter with Clock Enable and Asynchronous Clear
CB16CLE Macro: 16-Bit Loadable Cascadable Binary Counters with Clock Enable andAsynchronous Clear
CB16CLED Macro: 16-Bit Loadable Cascadable Bidirectional Binary Counters with Clock Enableand Asynchronous Clear
CB16RE Macro: 16-Bit Cascadable Binary Counter with Clock Enable and Synchronous Reset
CB16RLE Macro: 16-Bit Loadable Cascadable Binary Counter with Clock Enable andSynchronous Reset
CB16X1 Macro: 16-Bit Loadable Cascadable Bidirectional Binary Counter with Clock Enableand Asynchronous Clear
CB16X2 Macro: 16-Bit Loadable Cascadable Bidirectional Binary Counter with Clock Enableand Synchro-nous Reset
CB2CE Macro: 2-Bit Cascadable Binary Counter with Clock Enable and Asynchronous Clear
CB2CLE Macro: 2-Bit Loadable Cascadable Binary Counters with Clock Enable andAsynchronous Clear
CB2CLED Macro: 2-Bit Loadable Cascadable Bidirectional Binary Counters with Clock Enableand Asynchronous Clear
CB2RE Macro: 2-Bit Cascadable Binary Counter with Clock Enable and Synchronous Reset
CB2RLE Macro: 2-Bit Loadable Cascadable Binary Counter with Clock Enable and SynchronousReset
CB2X1 Macro: 2-Bit Loadable Cascadable Bidirectional Binary Counter with Clock Enableand Asynchronous Clear
CB4CE Macro: 4-Bit Cascadable Binary Counter with Clock Enable and Asynchronous Clear
CB4CLE Macro: 4-Bit Loadable Cascadable Binary Counters with Clock Enable andAsynchronous Clear
CB4CLED Macro: 4-Bit Loadable Cascadable Bidirectional Binary Counters with Clock Enableand Asynchronous Clear
CB4RE Macro: 4-Bit Cascadable Binary Counter with Clock Enable and Synchronous Reset
CB4RLE Macro: 4-Bit Loadable Cascadable Binary Counter with Clock Enable and SynchronousReset
CPLD Libraries Guide50 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 2: Functional Categories
Design Element Description
CB4X1 Macro: 4-Bit Loadable Cascadable Bidirectional Binary Counter with Clock Enableand Asynchronous Clear
CB4X2 Macro: 4-Bit Loadable Cascadable Bidirectional Binary Counter with Clock Enableand Synchronous Reset
CB8CE Macro: 8-Bit Cascadable Binary Counter with Clock Enable and Asynchronous Clear
CB8CLE Macro: 8-Bit Loadable Cascadable Binary Counters with Clock Enable andAsynchronous Clear
CB8CLED Macro: 8-Bit Loadable Cascadable Bidirectional Binary Counters with Clock Enableand Asynchronous Clear
CB8RE Macro: 8-Bit Cascadable Binary Counter with Clock Enable and Synchronous Reset
CB8RLE Macro: 8-Bit Loadable Cascadable Binary Counter with Clock Enable and SynchronousReset
CB8X1 Macro: 8-Bit Loadable Cascadable Bidirectional Binary Counter with Clock Enableand Asynchronous Clear
CB8X2 Macro: 8-Bit Loadable Cascadable Bidirectional Binary Counter with Clock Enableand Synchronous Reset
CBD16CE Macro: 16-Bit Cascadable Dual Edge Triggered Binary Counter with Clock Enableand Asynchronous Clear
CBD16CLE Macro: 16-Bit Loadable Cascadable Dual Edge Triggered Binary Counter with ClockEnable and Asynchronous Clear
CBD16CLED Macro: 16-Bit Loadable Cascadable Bidirectional Dual Edge Triggered Binary Counterwith Clock Enable and Asynchronous Clear
CBD16RE Macro: 16-Bit Cascadable Dual Edge Triggered Binary Counter with Clock Enableand Synchronous Reset
CBD16RLE Macro: 16-Bit Loadable Cascadable Dual Edge Triggered Binary Counter with ClockEnable and Synchronous Reset
CBD16X1 Macro: 16-Bit Loadable Cascadable Bidirectional Dual Edge Triggered Binary Counterwith Clock Enable and Asynchronous Clear
CBD16X2 Macro: 16-Bit Loadable Cascadable Bidirectional Dual Edge Triggered Binary Counterwith Clock Enable and Synchronous Reset
CBD2CE Macro: 2-Bit Cascadable Dual Edge Triggered Binary Counter with Clock Enableand Asynchronous Clear
CBD2CLE Macro: 2-Bit Loadable Cascadable Dual Edge Triggered Binary Counter with ClockEnable and Asynchronous Clear
CBD2CLED Macro: 2-Bit Loadable Cascadable Bidirectional Dual Edge Triggered Binary Counterwith Clock Enable and Asynchronous Clear
CBD2RE Macro: 2-Bit Cascadable Dual Edge Triggered Binary Counter with Clock Enableand Synchronous Reset
CBD2RLE Macro: 2-Bit Loadable Cascadable Dual Edge Triggered Binary Counter with ClockEnable and Synchronous Reset
CBD2X1 Macro: 2-Bit Loadable Cascadable Bidirectional Dual Edge Triggered Binary Counterwith Clock Enable and Asynchronous Clear
CBD2X2 Macro: 2-Bit Loadable Cascadable Bidirectional Dual Edge Triggered Binary Counterwith Clock Enable and Synchronous Reset
CBD4CE Macro: 4-Bit Cascadable Dual Edge Triggered Binary Counter with Clock Enableand Asynchronous Clear
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 51
Chapter 2: Functional Categories
Design Element Description
CBD4CLE Macro: 4-Bit Loadable Cascadable Dual Edge Triggered Binary Counter with ClockEnable and Asynchronous Clear
CBD4CLED Macro: 4-Bit Loadable Cascadable Bidirectional Dual Edge Triggered Binary Counterwith Clock Enable and Asynchronous Clear
CBD4RE Macro: 4-Bit Cascadable Dual Edge Triggered Binary Counter with Clock Enableand Synchronous Reset
CBD4RLE Macro: 4-Bit Loadable Cascadable Dual Edge Triggered Binary Counter with ClockEnable and Synchronous Reset
CBD4X1 Macro: 4-Bit Loadable Cascadable Bidirectional Dual Edge Triggered Binary Counterwith Clock Enable and Asynchronous Clear
CBD4X2 Macro: 4-Bit Loadable Cascadable Bidirectional Dual Edge Triggered Binary Counterwith Clock Enable and Synchronous Reset
CBD8CE Macro: 8-Bit Cascadable Dual Edge Triggered Binary Counter with Clock Enableand Asynchronous Clear
CBD8CLE Macro: 8-Bit Loadable Cascadable Dual Edge Triggered Binary Counter with ClockEnable and Asynchronous Clear
CBD8CLED Macro: 8-Bit Loadable Cascadable Bidirectional Dual Edge Triggered Binary Counterwith Clock Enable and Asynchronous Clear
CBD8RE Macro: 8-Bit Cascadable Dual Edge Triggered Binary Counter with Clock Enableand Synchronous Reset
CBD8X1 Macro: 8-Bit Loadable Cascadable Bidirectional Dual Edge Triggered Binary Counterwith Clock Enable and Asynchronous Clear
CBD8X2 Macro: 8-Bit Loadable Cascadable Bidirectional Dual Edge Triggered Binary Counterwith Clock Enable and Synchronous Reset
CD4CE Macro: 4-Bit Cascadable BCD Counter with Clock Enable and Asynchronous Clear
CD4CLE Macro: 4-Bit Loadable Cascadable BCD Counter with Clock Enable and AsynchronousClear
CD4RE Macro: 4-Bit Cascadable BCD Counter with Clock Enable and Synchronous Reset
CD4RLE Macro: 4-Bit Loadable Cascadable BCD Counter with Clock Enable and SynchronousReset
CDD4CE Macro: 4-Bit Cascadable Dual Edge Triggered BCD Counter with Clock Enable andAsynchronous Clear
CDD4CLE Macro: 4-Bit Loadable Cascadable Dual Edge Triggered BCD Counter with ClockEnable and Asynchronous Clear
CDD4RE Macro: 4-Bit Cascadable Dual Edge Triggered BCD Counter with Clock Enable andSynchronous Reset
CDD4RLE Macro: 4-Bit Loadable Cascadable Dual Edge Triggered BCD Counter with ClockEnable and Synchronous Reset
CJ4CE 4-Bit Johnson Counter with Clock Enable and Asynchronous Clear
CJ4RE Macro: 4-Bit Johnson Counter with Clock Enable and Synchronous Reset
CJ5CE Macro: 5-Bit Johnson Counter with Clock Enable and Asynchronous Clear
CJ5RE Macro: 5-Bit Johnson Counter with Clock Enable and Synchronous Reset
CJ8CE Macro: 8-Bit Johnson Counter with Clock Enable and Asynchronous Clear
CJ8RE Macro: 8-Bit Johnson Counter with Clock Enable and Synchronous Reset
CJD4CE Macro: 4-Bit Dual Edge Triggered Johnson Counter with Clock Enable andAsynchronous Clear
CPLD Libraries Guide52 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 2: Functional Categories
Design Element Description
CJD4RE Macro: 4-Bit Dual Edge Triggered Johnson Counter with Clock Enable andSynchronous Reset
CJD5CE Macro: 5-Bit Dual Edge Triggered Johnson Counter with Clock Enable andAsynchronous Clear
CJD5RE Macro: 5-Bit Dual Edge Triggered Johnson Counter with Clock Enable andSynchronous Reset
CJD8CE Macro: 8-Bit Dual Edge Triggered Johnson Counter with Clock Enable andAsynchronous Clear
CJD8RE Macro: 8-Bit Dual Edge Triggered Johnson Counter with Clock Enable andSynchronous Reset
CR16CE Macro: 16-Bit Negative-Edge Binary Ripple Counter with Clock Enable andAsynchronous Clear
CR8CE Macro: 8-Bit Negative-Edge Binary Ripple Counter with Clock Enable andAsynchronous Clear
CRD16CE Macro: 16-Bit Dual-Edge Triggered Binary Ripple Counter with Clock Enable andAsynchronous Clear
CRD8CE Macro: 8-Bit Dual-Edge Triggered Binary Ripple Counter with Clock Enable andAsynchronous Clear
DecoderDesign Element Description
D2_4E Macro: 2- to 4-Line Decoder/Demultiplexer with Enable
D3_8E Macro: 3- to 8-Line Decoder/Demultiplexer with Enable
D4_16E Macro: 4- to 16-Line Decoder/Demultiplexer with Enable
Flip FlopDesign Element Description
FD Unknown type: D Flip-Flop
FD16 Macro: Multiple D Flip-Flop
FD16CE Macro: 16-Bit Data Register with Clock Enable and Asynchronous Clear
FD16RE Macro: 16-Bit Data Register with Clock Enable and Synchronous Reset
FD4 Macro: Multiple D Flip-Flop
FD4CE Macro: 4-Bit Data Register with Clock Enable and Asynchronous Clear
FD8 Macro: Multiple D Flip-Flop
FD8CE Macro: 8-Bit Data Register with Clock Enable and Asynchronous Clear
FD8RE Macro: 8-Bit Data Register with Clock Enable and Synchronous Reset
FDC Unknown type: D Flip-Flop with Asynchronous Clear
FDCE Primitive: D Flip-Flop with Clock Enable and Asynchronous Clear
FDCP Primitive: D Flip-Flop with Asynchronous Preset and Clear
FDCPE Primitive: D Flip-Flop with Clock Enable and Asynchronous Preset and Clear
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 53
Chapter 2: Functional Categories
Design Element Description
FDD Macro: Dual Edge Triggered D Flip-Flop
FDD16 Macro: Multiple Dual Edge Triggered D Flip-Flop
FDD16CE Macro: 16-Bit Dual Edge Triggered Data Register with Clock Enable and AsynchronousClear
FDD16RE Macro: 16-Bit Dual Edge Triggered Data Register with Clock Enable and SynchronousReset
FDD4 Multiple Dual Edge Triggered D Flip-Flop
FDD4CE Macro: 4-Bit Dual Edge Triggered Data Register with Clock Enable and AsynchronousClear
FDD4RE Macro: 4-Bit Dual Edge Triggered Data Register with Clock Enable and SynchronousReset
FDD8 Macro: Multiple Dual Edge Triggered D Flip-Flop
FDD8CE Macro: 8-Bit Dual Edge Triggered Data Register with Clock Enable and AsynchronousClear
FDD8RE Macro: 8-Bit Dual Edge Triggered Data Register with Clock Enable and SynchronousReset
FDDC Macro: D Dual Edge Triggered Flip-Flop with Asynchronous Clear
FDDCE Primitive: Dual Edge Triggered D Flip-Flop with Clock Enable and AsynchronousClear
FDDCP Primitive: Dual Edge Triggered D Flip-Flop Asynchronous Preset and Clear
FDDCPE Macro: Dual Edge Triggered D Flip-Flop with Clock Enable and Asynchronous Presetand Clear
FDDP Macro: Dual Edge Triggered D Flip-Flop with Asynchronous Preset
FDDPE Primitive: Dual Edge Triggered D Flip-Flop with Clock Enable and AsynchronousPreset
FDDR Macro: Dual Edge Triggered D Flip-Flop with Synchronous Reset
FDDRE Macro: Dual Edge Triggered D Flip-Flop with Clock Enable and Synchronous Reset
FDDRS Macro: Dual Edge Triggered D Flip-Flop with Synchronous Reset and Set
FDDRSE Macro: Dual Edge Triggered D Flip-Flop with Synchronous Reset and Set and ClockEnable
FDDS Macro: Dual Edge Triggered D Flip-Flop with Synchronous Set
FDDSE Macro: D Flip-Flop with Clock Enable and Synchronous Set
FDDSR Macro: Dual Edge Triggered D Flip-Flop with Synchronous Set and Reset
FDDSRE Macro: Dual Edge Triggered D Flip-Flop with Synchronous Set and Reset and ClockEnable
FDP Unknown type: D Flip-Flop with Asynchronous Preset
FDPE Primitive: D Flip-Flop with Clock Enable and Asynchronous Preset
FDR Unknown type: D Flip-Flop with Synchronous Reset
FDRE Unknown type: D Flip-Flop with Clock Enable and Synchronous Reset
FDRS Unknown type: Macro: D Flip-Flop with Synchronous Reset and Set
FDRSE Unknown type: D Flip-Flop with Synchronous Reset and Set and Clock Enable
FDS Unknown type: D Flip-Flop with Synchronous Set
CPLD Libraries Guide54 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 2: Functional Categories
Design Element Description
FDSE Unknown type: D Flip-Flop with Clock Enable and Synchronous Set
FDSR D Flip-Flop with Synchronous Set and Reset
FDSRE Macro: D Flip-Flop with Synchronous Set and Reset and Clock Enable
FJKC Macro: J-K Flip-Flop with Asynchronous Clear
FJKCE Macro: J-K Flip-Flop with Clock Enable and Asynchronous Clear
FJKCP Macro: J-K Flip-Flop with Asynchronous Clear and Preset
FJKCPE Macro: J-K Flip-Flop with Asynchronous Clear and Preset and Clock Enable
FJKP Macro: J-K Flip-Flop with Asynchronous Preset
FJKPE Macro: J-K Flip-Flop with Clock Enable and Asynchronous Preset
FJKRSE Macro: J-K Flip-Flop with Clock Enable and Synchronous Reset and Set
FJKSRE Macro: J-K Flip-Flop with Clock Enable and Synchronous Set and Reset
FTC Macro: Toggle Flip-Flop with Asynchronous Clear
FTCE Macro: Toggle Flip-Flop with Clock Enable and Asynchronous Clear
FTCLE Macro: Toggle/Loadable Flip-Flop with Clock Enable and Asynchronous Clear
FTCLEX Macro: Toggle/Loadable Flip-Flop with Clock Enable and Asynchronous Clear
FTCP Primitive: Toggle Flip-Flop with Asynchronous Clear and Preset
FTCPE Macro: Toggle Flip-Flop with Clock Enable and Asynchronous Clear and Preset
FTCPLE Macro: Loadable Toggle Flip-Flop with Clock Enable and Asynchronous Clear andPreset
FTDCE Macro: Dual-Edge Triggered Toggle Flip-Flop with Clock Enable and AsynchronousClear
FTDCLE Macro: Dual-Edge Triggered Toggle/Loadable Flip-Flop with Clock Enable andAsynchronous Clear
FTDCLEX Macro: Dual-Edge Triggered Toggle/Loadable Flip-Flop with Clock Enable andAsynchronous Clear
FTDCP Primitive: Dual-Edge Triggered Toggle Flip-Flop with Asynchronous Clear and Preset
FTDRSE Macro: Dual-Edge Triggered Toggle Flip-Flop with Synchronous Reset, Set, andClock Enable
FTDRSLE Macro: Dual-Edge Triggered Toggle Flip-Flop with Clock Enable and SynchronousReset and Set
FTP Macro: Toggle Flip-Flop with Asynchronous Preset
FTPE Macro: Toggle Flip-Flop with Clock Enable and Asynchronous Preset
FTPLE Macro: Toggle/Loadable Flip-Flop with Clock Enable and Asynchronous Preset
FTRSE Macro: Toggle Flip-Flop with Clock Enable and Synchronous Reset and Set
FTRSLE Macro: Toggle/Loadable Flip-Flop with Clock Enable and Synchronous Reset and Set
FTSRE Macro: Toggle Flip-Flop with Clock Enable and Synchronous Set and Reset
FTSRLE Macro: Toggle/Loadable Flip-Flop with Clock Enable and Synchronous Set and Reset
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 55
Chapter 2: Functional Categories
GeneralDesign Element Description
GND Primitive: Ground-Connection Signal Tag
KEEPER Primitive: KEEPER Symbol
PULLDOWN Primitive: Resistor to GND for Input Pads, Open-Drain, and 3-State Outputs
PULLUP Primitive: Resistor to VCC for Input PADs, Open-Drain, and 3-State Outputs
VCC Primitive: VCC-Connection Signal Tag
IODesign Element Description
IBUF Primitive: Input Buffer
IBUF16 Macro: 16-Bit Input Buffer
IBUF4 Macro: 4-Bit Input Buffer
IBUF8 Macro: 8-Bit Input Buffer
IOBUFE Primitive: Bi-Directional Buffer
OBUF Primitive: Output Buffer
OBUF16 Macro: 16-Bit Output Buffer
OBUF4 Macro: 4-Bit Output Buffer
OBUF8 Macro: 8-Bit Output Buffer
OBUFE Macro: 3-State Output Buffer with Active-High Output Enable
OBUFE16 Macro: 16-Bit 3-State Output Buffer with Active-High Output Enable
OBUFE4 Macro: 4-Bit 3-State Output Buffer with Active-High Output Enable
OBUFE8 Macro: 8-Bit 3-State Output Buffer with Active-High Output Enable
OBUFT Primitive: 3-State Output Buffer with Active Low Output Enable
OBUFT16 Macro: 16-Bit 3-State Output Buffer with Active Low Output Enable
OBUFT4 Macro: 4-Bit 3-State Output Buffers with Active-Low Output Enable
OBUFT8 Macro: 8-Bit 3-State Output Buffers with Active-Low Output Enable
CPLD Libraries Guide56 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 2: Functional Categories
LatchDesign Element Description
LD Primitive: Transparent Data Latch
LD16 Macro: Multiple Transparent Data Latch
LD4 Macro: Multiple Transparent Data Latch
LD8 Macro: Multiple Transparent Data Latch
LDC Primitive: Macro: Transparent Data Latch with Asynchronous Clear
LDCP Primitive: Transparent Data Latch with Asynchronous Clear and Preset
LDG Primitive: Transparent Datagate Latch
LDG16 Macro: 16-bit Transparent Datagate Latch
LDG4 Macro: 4-Bit Transparent Datagate Latch
LDG8 Macro: 8-Bit Transparent Datagate Latch
LDP Primitive: Macro: Transparent Data Latch with Asynchronous Preset
LogicDesign Element Description
AND2 Primitive: 2-Input AND Gate with Non-Inverted Inputs
AND2B1 Primitive: 2-Input AND Gate with 1 Inverted and 1 Non-Inverted Inputs
AND2B2 Primitive: 2-Input AND Gate with Inverted Inputs
AND3 Primitive: 3-Input AND Gate with Non-Inverted Inputs
AND3B1 Primitive: 3-Input AND Gate with 1 Inverted and 2 Non-Inverted Inputs
AND3B2 Primitive: 3-Input AND Gate with 2 Inverted and 1 Non-Inverted Inputs
AND3B3 Primitive: 3-Input AND Gate with Inverted Inputs
AND4 Primitive: 4-Input AND Gate with Non-Inverted Inputs
AND4B1 Primitive: 4-Input AND Gate with 1 Inverted and 3 Non-Inverted Inputs
AND4B2 Primitive: 4-Input AND Gate with 2 Inverted and 2 Non-Inverted Inputs
AND4B3 Primitive: 4-Input AND Gate with 3 Inverted and 1 Non-Inverted Inputs
AND4B4 Primitive: 4-Input AND Gate with Inverted Inputs
AND5 Primitive: 5-Input AND Gate with Non-Inverted Inputs
AND5B1 Primitive: 5-Input AND Gate with 1 Inverted and 4 Non-Inverted Inputs
AND5B2 Primitive: 5-Input AND Gate with 2 Inverted and 3 Non-Inverted Inputs
AND5B3 Primitive: 5-Input AND Gate with 3 Inverted and 2 Non-Inverted Inputs
AND5B4 Primitive: 5-Input AND Gate with 4 Inverted and 1 Non-Inverted Inputs
AND5B5 Primitive: 5-Input AND Gate with Inverted Inputs
AND6 Macro: 6-Input AND Gate with Non-Inverted Inputs
AND7 Macro: 7-Input AND Gate with Non-Inverted Inputs
AND8 Macro: 8-Input AND Gate with Non-Inverted Inputs
AND9 Macro: 9-Input AND Gate with Non-Inverted Inputs
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 57
Chapter 2: Functional Categories
Design Element Description
INV Primitive: Inverter
INV16 Macro: 16 Inverters
INV4 Macro: Four Inverters
INV8 Macro: Eight Inverters
NAND2 Primitive: 2-Input NAND Gate with Non-Inverted Inputs
NAND2B1 Primitive: 2-Input NAND Gate with 1 Inverted and 1 Non-Inverted Inputs
NAND2B2 Primitive: 2-Input NAND Gate with Inverted Inputs
NAND3 Primitive: 3-Input NAND Gate with Non-Inverted Inputs
NAND3B1 Primitive: 3-Input NAND Gate with 1 Inverted and 2 Non-Inverted Inputs
NAND3B2 Primitive: 3-Input NAND Gate with 2 Inverted and 1 Non-Inverted Inputs
NAND3B3 Primitive: 3-Input NAND Gate with Inverted Inputs
NAND4 Primitive: 4-Input NAND Gate with Non-Inverted Inputs
NAND4B1 Primitive: 4-Input NAND Gate with 1 Inverted and 3 Non-Inverted Inputs
NAND4B2 Primitive: 4-Input NAND Gate with 2 Inverted and 2 Non-Inverted Inputs
NAND4B3 Primitive: 4-Input NAND Gate with 3 Inverted and 1 Non-Inverted Inputs
NAND4B4 Primitive: 4-Input NAND Gate with Inverted Inputs
NAND5 Primitive: 5-Input NAND Gate with Non-Inverted Inputs
NAND5B1 Primitive: 5-Input NAND Gate with 1 Inverted and 4 Non-Inverted Inputs
NAND5B2 Primitive: 5-Input NAND Gate with 2 Inverted and 3 Non-Inverted Inputs
NAND5B3 Primitive: 5-Input NAND Gate with 3 Inverted and 2 Non-Inverted Inputs
NAND5B4 Primitive: 5-Input NAND Gate with 4 Inverted and 1 Non-Inverted Inputs
NAND5B5 Primitive: 5-Input NAND Gate with Inverted Inputs
NAND6 Macro: 6-Input NAND Gate with Non-Inverted Inputs
NAND7 Macro: 7-Input NAND Gate with Non-Inverted Inputs
NAND8 Macro: 8-Input NAND Gate with Non-Inverted Inputs
NAND9 Macro: 9-Input NAND Gate with Non-Inverted Inputs
NOR2 Primitive: 2-Input NOR Gate with Non-Inverted Inputs
NOR2B1 Primitive: 2-Input NOR Gate with 1 Inverted and 1 Non-Inverted Inputs
NOR2B2 Primitive: 2-Input NOR Gate with Inverted Inputs
NOR3 Primitive: 3-Input NOR Gate with Non-Inverted Inputs
NOR3B1 Primitive: 3-Input NOR Gate with 1 Inverted and 2 Non-Inverted Inputs
NOR3B2 Primitive: 3-Input NOR Gate with 2 Inverted and 1 Non-Inverted Inputs
NOR3B3 Primitive: 3-Input NOR Gate with Inverted Inputs
NOR4 Primitive: 4-Input NOR Gate with Non-Inverted Inputs
NOR4B1 Primitive: 4-Input NOR Gate with 1 Inverted and 3 Non-Inverted Inputs
NOR4B2 Primitive: 4-Input NOR Gate with 2 Inverted and 2 Non-Inverted Inputs
NOR4B3 Primitive: 4-Input NOR Gate with 3 Inverted and 1 Non-Inverted Inputs
NOR4B4 Primitive: 4-Input NOR Gate with Inverted Inputs
CPLD Libraries Guide58 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 2: Functional Categories
Design Element Description
NOR5 Primitive: 5-Input NOR Gate with Non-Inverted Inputs
NOR5B1 Primitive: 5-Input NOR Gate with 1 Inverted and 4 Non-Inverted Inputs
NOR5B2 Primitive: 5-Input NOR Gate with 2 Inverted and 3 Non-Inverted Inputs
NOR5B3 Primitive: 5-Input NOR Gate with 3 Inverted and 2 Non-Inverted Inputs
NOR5B4 Primitive: 5-Input NOR Gate with 4 Inverted and 1 Non-Inverted Inputs
NOR5B5 Primitive: 5-Input NOR Gate with Inverted Inputs
NOR6 Macro: 6-Input NOR Gate with Non-Inverted Inputs
NOR7 Macro: 7-Input NOR Gate with Non-Inverted Inputs
NOR8 Macro: 8-Input NOR Gate with Non-Inverted Inputs
NOR9 Macro: 9-Input NOR Gate with Non-Inverted Inputs
OR2 Primitive: 2-Input OR Gate with Non-Inverted Inputs
OR2B1 Primitive: 2-Input OR Gate with 1 Inverted and 1 Non-Inverted Inputs
OR2B2 Primitive: 2-Input OR Gate with Inverted Inputs
OR3 Primitive: 3-Input OR Gate with Non-Inverted Inputs
OR3B1 Primitive: 3-Input OR Gate with 1 Inverted and 2 Non-Inverted Inputs
OR3B2 Primitive: 3-Input OR Gate with 2 Inverted and 1 Non-Inverted Inputs
OR3B3 Primitive: 3-Input OR Gate with Inverted Inputs
OR4 Primitive: 4-Input OR Gate with Non-Inverted Inputs
OR4B1 Primitive: 4-Input OR Gate with 1 Inverted and 3 Non-Inverted Inputs
OR4B2 Primitive: 4-Input OR Gate with 2 Inverted and 2 Non-Inverted Inputs
OR4B3 Primitive: 4-Input OR Gate with 3 Inverted and 1 Non-Inverted Inputs
OR4B4 Primitive: 4-Input OR Gate with Inverted Inputs
OR5 Primitive: 5-Input OR Gate with Non-Inverted Inputs
OR5B1 Primitive: 5-Input OR Gate with 1 Inverted and 4 Non-Inverted Inputs
OR5B2 Primitive: 5-Input OR Gate with 2 Inverted and 3 Non-Inverted Inputs
OR5B3 Primitive: 5-Input OR Gate with 3 Inverted and 2 Non-Inverted Inputs
OR5B4 Primitive: 5-Input OR Gate with 4 Inverted and 1 Non-Inverted Inputs
OR5B5 Primitive: 5-Input OR Gate with Inverted Inputs
OR6 Macro: 6-Input OR Gate with Non-Inverted Inputs
OR7 Macro: 7-Input OR Gate with Non-Inverted Inputs
OR8 Macro: 8-Input OR Gate with Non-Inverted Inputs
OR9 Macro: 9-Input OR Gate with Non-Inverted Inputs
XNOR2 Primitive: 2-Input XNOR Gate with Non-Inverted Inputs
XNOR3 Primitive: 3-Input XNOR Gate with Non-Inverted Inputs
XNOR4 Primitive: 4-Input XNOR Gate with Non-Inverted Inputs
XNOR5 Primitive: 5-Input XNOR Gate with Non-Inverted Inputs
XNOR6 Macro: 6-Input XNOR Gate with Non-Inverted Inputs
XNOR7 Macro: 7-Input XNOR Gate with Non-Inverted Inputs
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 59
Chapter 2: Functional Categories
Design Element Description
XNOR8 Macro: 8-Input XNOR Gate with Non-Inverted Inputs
XNOR9 Macro: 9-Input XNOR Gate with Non-Inverted Inputs
XOR2 Primitive: 2-Input XOR Gate with Non-Inverted Inputs
XOR3 Primitive: 3-Input XOR Gate with Non-Inverted Inputs
XOR4 Primitive: 4-Input XOR Gate with Non-Inverted Inputs
XOR5 Primitive: 5-Input XOR Gate with Non-Inverted Inputs
XOR6 Macro: 6-Input XOR Gate with Non-Inverted Inputs
XOR7 Macro: 7-Input XOR Gate with Non-Inverted Inputs
XOR8 Macro: 8-Input XOR Gate with Non-Inverted Inputs
XOR9 Macro: 9-Input XOR Gate with Non-Inverted Inputs
MuxDesign Element Description
M16_1E Macro: 16-to-1 Multiplexer with Enable
M2_1 Macro: 2-to-1 Multiplexer
M2_1B1 Macro: 2-to-1 Multiplexer with D0 Inverted
M2_1B2 Macro: 2-to-1 Multiplexer with D0 and D1 Inverted
M2_1E Macro: 2-to-1 Multiplexer with Enable
M4_1E Macro: 4-to-1 Multiplexer with Enable
M8_1E Macro: 8-to-1 Multiplexer with Enable
Shift RegisterDesign Element Description
SR16CE Macro: 16-Bit Serial-In Parallel-Out Shift Register with Clock Enable andAsynchronous Clear
SR16CLE Macro: 16-Bit Loadable Serial/Parallel-In Parallel-Out Shift Register with Clock Enableand Asynchronous Clear
SR16CLED Macro: 16-Bit Shift Register with Clock Enable and Asynchronous Clear
SR16RE Macro: 16-Bit Serial-In Parallel-Out Shift Register with Clock Enable and SynchronousReset
SR16RLE Macro: 16-Bit Loadable Serial/Parallel-In Parallel-Out Shift Register with Clock Enableand Synchronous Reset
SR16RLED Macro: 16-Bit Shift Register with Clock Enable and Synchronous Reset
SR4CE Macro: 4-Bit Serial-In Parallel-Out Shift Register with Clock Enable and AsynchronousClear
SR4CLE Macro: 4-Bit Loadable Serial/Parallel-In Parallel-Out Shift Register with Clock Enableand Asynchronous Clear
SR4CLED Macro: 4-Bit Shift Register with Clock Enable and Asynchronous Clear
CPLD Libraries Guide60 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 2: Functional Categories
Design Element Description
SR4RE Macro: 4-Bit Serial-In Parallel-Out Shift Register with Clock Enable and SynchronousReset
SR4RLE Macro: 4-Bit Loadable Serial/Parallel-In Parallel-Out Shift Register with Clock Enableand Synchronous Reset
SR4RLED Macro: 4-Bit Shift Register with Clock Enable and Synchronous Reset
SR8CE Macro: 8-Bit Serial-In Parallel-Out Shift Register with Clock Enable and AsynchronousClear
SR8CLE Macro: 8-Bit Loadable Serial/Parallel-In Parallel-Out Shift Register with Clock Enableand Asynchronous Clear
SR8CLED Macro: 8-Bit Shift Register with Clock Enable and Asynchronous Clear
SR8RE Macro: 8-Bit Serial-In Parallel-Out Shift Register with Clock Enable and SynchronousReset
SR8RLE Macro: 8-Bit Loadable Serial/Parallel-In Parallel-Out Shift Register with Clock Enableand Synchronous Reset
SR8RLED Macro: 8-Bit Shift Register with Clock Enable and Synchronous Reset
SRD16CE Macro: 16-Bit Serial-In Parallel-Out Dual Edge Triggered Shift Register with ClockEnable and Asynchronous Clear
SRD16CLE Macro: 16-Bit Loadable Serial/Parallel-In Parallel-Out Dual Edge Triggered ShiftRegister with Clock Enable and Asynchronous Clear
SRD16CLED Macro: 16-Bit Dual Edge Triggered Shift Register with Clock Enable and AsynchronousClear
SRD16RE Macro: 16-Bit Serial-In Parallel-Out Dual Edge Triggered Shift Register with ClockEnable and Synchronous Reset
SRD16RLE Macro: 16-Bit Loadable Serial/Parallel-In Parallel-Out Dual Edge Triggered ShiftRegister with Clock Enable and Synchronous Reset
SRD16RLED Macro: 16-Bit Dual Edge Triggered Shift Register with Clock Enable and SynchronousReset
SRD4CE Macro: 4-Bit Serial-In Parallel-Out Dual Edge Triggered Shift Register with ClockEnable and Asynchronous Clear
SRD4CLE Macro: 4-Bit Loadable Serial/Parallel-In Parallel-Out Dual Edge Triggered ShiftRegister with Clock Enable and Asynchronous Clear
SRD4CLED Macro: 4-Bit Dual Edge Triggered Shift Register with Clock Enable and AsynchronousClear
SRD4RE Macro: 4-Bit Serial-In Parallel-Out Dual Edge Triggered Shift Register with ClockEnable and Synchronous Reset
SRD4RLE Macro: 4-Bit Loadable Serial/Parallel-In Parallel-Out Dual Edge Triggered ShiftRegister with Clock Enable and Synchronous Reset
SRD4RLED Macro: 4-Bit Dual Edge Triggered Shift Register with Clock Enable and SynchronousReset
SRD8CE Macro: 8-Bit Serial-In Parallel-Out Dual Edge Triggered Shift Register with ClockEnable and Asynchronous Clear
SRD8CLE Macro: 8-Bit Loadable Serial/Parallel-In Parallel-Out Dual Edge Triggered ShiftRegister with Clock Enable and Asynchronous Clear
SRD8CLED Macro: 8-Bit Dual Edge Triggered Shift Register with Clock Enable and AsynchronousClear
SRD8RE Macro: 8-Bit Serial-In Parallel-Out Dual Edge Triggered Shift Register with ClockEnable and Synchronous Reset
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 61
Chapter 2: Functional Categories
Design Element Description
SRD8RLE Macro: 8-Bit Loadable Serial/Parallel-In Parallel-Out Dual Edge Triggered ShiftRegister with Clock Enable and Synchronous Reset
SRD8RLED Macro: 8-Bit Dual Edge Triggered Shift Register with Clock Enable and SynchronousReset
ShifterDesign Element Description
BRLSHFT4 Macro: 4-Bit Barrel Shifter
BRLSHFT8 Macro: 8-Bit Barrel Shifter
CPLD Libraries Guide62 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3
About Design ElementsThis section describes the design elements that can be used with this architecture. The design elements areorganized alphabetically.
The following information is provided for each design element, where applicable:
• Name of element
• Brief description
• Schematic symbol (if any)
• Logic Table (if any)
• Port Descriptions (if any)
• Design Entry Method
• Available Attributes (if any)
• For more information
You can find examples of VHDL and Verilog instantiation code in the ISE software (in the main menu, select Edit> Language Templates or in the Libraries Guide for HDL Designs for this architecture.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 63
Chapter 3: About Design Elements
ACC1Macro: 1-Bit Loadable Cascadable Accumulator with Carry-In, Carry-Out, and Synchronous Reset
Supported ArchitecturesThis design element is supported in the following architectures only:• XC9500• CoolRunner™ XPLA3• CoolRunner-II
IntroductionThis design element can add or subtract a 1-bit unsigned-binary word to or from the contents of a 1-bit dataregister and store the results in the register. The register can be loaded with a 1-bit word. The synchronous reset(R) has priority over all other inputs and, when High, causes the output to go to logic level zero during theLow-to-High clock (C) transition. Clock (C) transitions are ignored when clock enable (CE) is Low.
Load
When the load input (L) is High, CE is ignored and the data on the input D0 is loaded into the 1-bit registerduring the Low-to-High clock (C) transition.
Add
When control inputs ADD and CE are both High, the accumulator adds a 1-bit word (B0) and carry-in (CI) to thecontents of the 1-bit register. The result is stored in the register and appears on output Q0 during the Low-to-Highclock transition. The carry-out (CO) is not registered synchronously with the data output. CO always reflects theaccumulation of input B0 and the contents of the register, which allows cascading of ACC1s by connecting CO ofone stage to CI of the next stage. In add mode, CO acts as a carry-out, and CO and CI are active-High.
Subtract
When ADD is Low and CE is High, the 1-bit word B0 and CI are subtracted from the contents of the register. Theresult is stored in the register and appears on output Q0 during the Low-to-High clock transition. The carry-out(CO) is not registered synchronously with the data output. CO always reflects the accumulation of input B0 andthe contents of the register, which allows cascading of ACC1s by connecting CO of one stage to CI of the nextstage. In subtract mode, CO acts as a borrow, and CO and CI are active-Low.
This design element is asynchronously cleared, outputs Low, when power is applied. For CPLD devices, you cansimulate power-on by applying a High-level pulse on the PRLD global net.
Design Entry MethodThis design element is only for use in schematics.
CPLD Libraries Guide64 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 65
Chapter 3: About Design Elements
ACC16Macro: 16-Bit Loadable Cascadable Accumulator with Carry-In, Carry-Out, and Synchronous Reset
Supported ArchitecturesThis design element is supported in the following architectures only:• XC9500• CoolRunner™ XPLA3• CoolRunner-II
IntroductionThis design element can add or subtract a 16-bit unsigned-binary, respectively or two’s-complement word toor from the contents of a 16-bit data register and store the results in the register. The register can be loadedwith the 16-bit word.
When the load input (L) is High, CE is ignored and the data on the D inputs is loaded into the register during theLow-to-High clock (C) transition. ACC16 loads the data on inputs D15 : D0 into the 16-bit register.
This design element operates on either 16-bit unsigned binary numbers or 16-bit two’s-complement numbers. Ifthe inputs are interpreted as unsigned binary, the result can be interpreted as unsigned binary. If the inputsare interpreted as two’s complement, the output can be interpreted as two’s complement. The only functionaldifference between an unsigned binary operation and a two’s-complement operation is how they determinewhen “overflow” occurs. Unsigned binary uses carry-out (CO), while two’s complement uses OFL to determinewhen “overflow” occurs.• For unsigned binary operation, ACC16 can represent numbers between 0 and 15, inclusive. In add mode,
CO is active (High) when the sum exceeds the bounds of the adder/subtracter. In subtract mode, CO is anactive-Low borrow-out and goes Low when the difference exceeds the bounds. The carry-out (CO) isnot registered synchronously with the data outputs. CO always reflects the accumulation of the B inputs(B15 : B0 for ACC16). This allows the cascading of ACC16s by connecting CO of one stage to CI of thenext stage. An unsigned binary “overflow” that is always active-High can be generated by gating theADD signal and CO as follows:unsigned overflow = CO XOR ADD
Ignore OFL in unsigned binary operation.• For two’s-complement operation, ACC16 represents numbers between -8 and +7, inclusive. If an addition
or subtraction operation result exceeds this range, the OFL output goes High. The overflow (OFL) is notregistered synchronously with the data outputs. OFL always reflects the accumulation of the B inputs (B15 :B0 for ACC16) and the contents of the register, which allows cascading of ACC4s by connecting OFL of onestage to CI of the next stage.
CPLD Libraries Guide66 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
Ignore CO in two’s-complement operation.
The synchronous reset (R) has priority over all other inputs, and when set to High, causes all outputs to go tologic level zero during the Low-to-High clock (C) transition. Clock (C) transitions are ignored when clockenable (CE) is Low.
This design element is asynchronously cleared, outputs Low, when power is applied. For CPLD devices, you cansimulate power-on by applying a High-level pulse on the PRLD global net.
Logic TableInput Output
R L CE ADD D C Q
1 x x x x ↑ 0
0 1 x x Dn ↑ Dn
0 0 1 1 x ↑ Q0+Bn+CI
0 0 1 0 x ↑ Q0-Bn-CI
0 0 0 x x ↑ No Change
Q0: Previous value of Q
Bn: Value of Data input B
CI: Value of input CI
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 67
Chapter 3: About Design Elements
ACC4Macro: 4-Bit Loadable Cascadable Accumulator with Carry-In, Carry-Out, and Synchronous Reset
Supported ArchitecturesThis design element is supported in the following architectures only:• XC9500• CoolRunner™ XPLA3• CoolRunner-II
IntroductionThis design element can add or subtract a 4-bit unsigned-binary, respectively or two’s-complement word to orfrom the contents of a 4-bit data register and store the results in the register. The register can be loaded with the4-bit word.
When the load input (L) is High, CE is ignored and the data on the D inputs is loaded into the register during theLow-to-High clock (C) transition. ACC4 loads the data on inputs D3 : D0 into the 4-bit register.
This design element operates on either 4-bit unsigned binary numbers or 4-bit two’s-complement numbers. Ifthe inputs are interpreted as unsigned binary, the result can be interpreted as unsigned binary. If the inputsare interpreted as two’s complement, the output can be interpreted as two’s complement. The only functionaldifference between an unsigned binary operation and a two’s-complement operation is how they determinewhen “overflow” occurs. Unsigned binary uses carry-out (CO), while two’s complement uses OFL to determinewhen “overflow” occurs.• For unsigned binary operation, ACC4 can represent numbers between 0 and 15, inclusive. In add mode,
CO is active (High) when the sum exceeds the bounds of the adder/subtracter. In subtract mode, CO is anactive-Low borrow-out and goes Low when the difference exceeds the bounds. The carry-out (CO) isnot registered synchronously with the data outputs. CO always reflects the accumulation of the B inputs(B3 : B0 for ACC4). This allows the cascading of ACC4s by connecting CO of one stage to CI of the nextstage. An unsigned binary “overflow” that is always active-High can be generated by gating the ADDsignal and CO as follows:unsigned overflow = CO XOR ADD
Ignore OFL in unsigned binary operation.
CPLD Libraries Guide68 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
• For two’s-complement operation, ACC4 represents numbers between -8 and +7, inclusive. If an additionor subtraction operation result exceeds this range, the OFL output goes High. The overflow (OFL) is notregistered synchronously with the data outputs. OFL always reflects the accumulation of the B inputs (B3 :B0 for ACC4) and the contents of the register, which allows cascading of ACC4s by connecting OFL of onestage to CI of the next stage.
Ignore CO in two’s-complement operation.
The synchronous reset (R) has priority over all other inputs, and when set to High, causes all outputs to go tologic level zero during the Low-to-High clock (C) transition. Clock (C) transitions are ignored when clockenable (CE) is Low.
This design element is asynchronously cleared, outputs Low, when power is applied. For CPLD devices, you cansimulate power-on by applying a High-level pulse on the PRLD global net.
Logic TableInput Output
R L CE ADD D C Q
1 x x x x ↑ 0
0 1 x x Dn ↑ Dn
0 0 1 1 x ↑ Q0+Bn+CI
0 0 1 0 x ↑ Q0-Bn-CI
0 0 0 x x ↑ No Change
Q0: Previous value of Q
Bn: Value of Data input B
CI: Value of input CI
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 69
Chapter 3: About Design Elements
ACC8Macro: 8-Bit Loadable Cascadable Accumulator with Carry-In, Carry-Out, and Synchronous Reset
Supported ArchitecturesThis design element is supported in the following architectures only:• XC9500• CoolRunner™ XPLA3• CoolRunner-II
IntroductionThis design element can add or subtract a 8-bit unsigned-binary, respectively or two’s-complement word to orfrom the contents of a 8-bit data register and store the results in the register. The register can be loaded with the8-bit word.
When the load input (L) is High, CE is ignored and the data on the D inputs is loaded into the register during theLow-to-High clock (C) transition. ACC8 loads the data on inputs D7 : D0 into the 8-bit register.
This design element operates on either 8-bit unsigned binary numbers or 8-bit two’s-complement numbers. Ifthe inputs are interpreted as unsigned binary, the result can be interpreted as unsigned binary. If the inputsare interpreted as two’s complement, the output can be interpreted as two’s complement. The only functionaldifference between an unsigned binary operation and a two’s-complement operation is how they determinewhen “overflow” occurs. Unsigned binary uses carry-out (CO), while two’s complement uses OFL to determinewhen “overflow” occurs.• For unsigned binary operation, ACC8 can represent numbers between 0 and 255, inclusive. In add mode,
CO is active (High) when the sum exceeds the bounds of the adder/subtracter. In subtract mode, CO is anactive-Low borrow-out and goes Low when the difference exceeds the bounds. The carry-out (CO) isnot registered synchronously with the data outputs. CO always reflects the accumulation of the B inputs(B3 : B0 for ACC4). This allows the cascading of ACC8s by connecting CO of one stage to CI of the nextstage. An unsigned binary “overflow” that is always active-High can be generated by gating the ADDsignal and CO as follows:unsigned overflow = CO XOR ADD
Ignore OFL in unsigned binary operation.• For two’s-complement operation, ACC8 represents numbers between -128 and +127, inclusive. If an addition
or subtraction operation result exceeds this range, the OFL output goes High. The overflow (OFL) is notregistered synchronously with the data outputs. OFL always reflects the accumulation of the B inputs (B3 :B0 for ACC8) and the contents of the register, which allows cascading of ACC8s by connecting OFL of onestage to CI of the next stage.
CPLD Libraries Guide70 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
Ignore CO in two’s-complement operation.
The synchronous reset (R) has priority over all other inputs, and when set to High, causes all outputs to go tologic level zero during the Low-to-High clock (C) transition. Clock (C) transitions are ignored when clockenable (CE) is Low.
This design element is asynchronously cleared, outputs Low, when power is applied. For CPLD devices, you cansimulate power-on by applying a High-level pulse on the PRLD global net.
Logic TableInput Output
R L CE ADD D C Q
1 x x x x ↑ 0
0 1 x x Dn ↑ Dn
0 0 1 1 x ↑ Q0+Bn+CI
0 0 1 0 x ↑ Q0-Bn-CI
0 0 0 x x ↑ No Change
Q0: Previous value of Q
Bn: Value of Data input B
CI: Value of input CI
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 71
Chapter 3: About Design Elements
ADD1Macro: 1-Bit Full Adder with Carry-In and Carry-Out
Supported ArchitecturesThis design element is supported in the following architectures only:
• XC9500
• CoolRunner™ XPLA3
• CoolRunner-II
IntroductionThis design element is a cascadable 1-bit full adder with carry-in and carry-out. It adds two 1-bit words (A andB) and a carry-in (CI), producing a binary sum (S0) output and a carry-out (CO).
Logic TableInputs Outputs
A0 B0 CI S0 CO
0 0 0 0 0
1 0 0 1 0
0 1 0 1 0
1 1 0 0 1
0 0 1 1 0
1 0 1 0 1
0 1 1 0 1
1 1 1 1 1
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries Guide72 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
ADD16Macro: 16-Bit Cascadable Full Adder with Carry-In, Carry-Out, and Overflow
Supported ArchitecturesThis design element is supported in the following architectures only:
• XC9500
• CoolRunner™ XPLA3
• CoolRunner-II
IntroductionThis design element adds two words and a carry-in (CI), producing a sum output and carry-out (CO) or overflow(OFL). The factors added are A15:A0, B15:B0 and CI, producing the sum output S15:S0 and CO (or OFL).
Logic TableInput Output
A B S
An Bn An+Bn+CI
CI: Value of input CI.
Unsigned Binary Versus Two’s Complement
This design element can operate on either 16-bit unsigned binary numbers or 16-bit two’s-complement numbers,respectively. If the inputs are interpreted as unsigned binary, the result can be interpreted as unsigned binary. Ifthe inputs are interpreted as two’s complement, the output can be interpreted as two’s complement. The onlyfunctional difference between an unsigned binary operation and a two’s-complement operation is the way theydetermine when “overflow” occurs. Unsigned binary uses CO, while two’s-complement uses OFL to determinewhen “overflow” occurs. To interpret the inputs as unsigned binary, follow the CO output. To interpret theinputs as two’s complement, follow the OFL output.
Unsigned Binary Operation
For unsigned binary operation, this element represents numbers between 0 and 65535, inclusive. OFL is ignoredin unsigned binary operation.
Two’s-Complement Operation
For two’s-complement operation, this element can represent numbers between -32768 and +32767, inclusive. OFLis active (High) when the sum exceeds the bounds of the adder. CO is ignored in two’s-complement operation.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 73
Chapter 3: About Design Elements
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries Guide74 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
ADD4Macro: 4-Bit Cascadable Full Adder with Carry-In, Carry-Out, and Overflow
Supported ArchitecturesThis design element is supported in the following architectures only:• XC9500• CoolRunner™ XPLA3• CoolRunner-II
IntroductionThis design element adds two words and a carry-in (CI), producing a sum output and carry-out (CO) or overflow(OFL). The factors added are A3:A0, B3:B0, and CI producing the sum output S3:S0 and CO (or OFL).
Logic TableInput Output
A B S
An Bn An+Bn+CI
CI: Value of input CI.
Unsigned Binary Versus Two’s Complement
This design element can operate on either 4-bit unsigned binary numbers or 4-bit two’s-complement numbers,respectively. If the inputs are interpreted as unsigned binary, the result can be interpreted as unsigned binary. Ifthe inputs are interpreted as two’s complement, the output can be interpreted as two’s complement. The onlyfunctional difference between an unsigned binary operation and a two’s-complement operation is the way theydetermine when “overflow” occurs. Unsigned binary uses CO, while two’s-complement uses OFL to determinewhen “overflow” occurs. To interpret the inputs as unsigned binary, follow the CO output. To interpret theinputs as two’s complement, follow the OFL output.
Unsigned Binary Operation
For unsigned binary operation, this element represents numbers from 0 to 15, inclusive. OFL is ignoredin unsigned binary operation.
Two’s-Complement Operation
For two’s-complement operation, this element can represent numbers between -8 and +7, inclusive. OFL is active(High) when the sum exceeds the bounds of the adder. CO is ignored in two’s-complement operation.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 75
Chapter 3: About Design Elements
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries Guide76 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
ADD8Macro: 8-Bit Cascadable Full Adder with Carry-In, Carry-Out, and Overflow
Supported ArchitecturesThis design element is supported in the following architectures only:• XC9500• CoolRunner™ XPLA3• CoolRunner-II
IntroductionThis design element adds two words and a carry-in (CI), producing a sum output and carry-out (CO) or overflow(OFL). The factors added are A7:A0, B7:B0, and CI, producing the sum output S7:S0 and CO (or OFL).
Logic TableInput Output
A B S
An Bn An+Bn+CI
CI: Value of input CI.
Unsigned Binary Versus Two’s Complement
This design element can operate on either 8-bit unsigned binary numbers or 8-bit two’s-complement numbers,respectively. If the inputs are interpreted as unsigned binary, the result can be interpreted as unsigned binary. Ifthe inputs are interpreted as two’s complement, the output can be interpreted as two’s complement. The onlyfunctional difference between an unsigned binary operation and a two’s-complement operation is the way theydetermine when “overflow” occurs. Unsigned binary uses CO, while two’s-complement uses OFL to determinewhen “overflow” occurs. To interpret the inputs as unsigned binary, follow the CO output. To interpret theinputs as two’s complement, follow the OFL output.
Unsigned Binary Operation
For unsigned binary operation, this element represents numbers between 0 and 255, inclusive. OFL is ignoredin unsigned binary operation.
Two’s-Complement Operation
For two’s-complement operation, this element can represent numbers between -128 and +127, inclusive. OFL isactive (High) when the sum exceeds the bounds of the adder. CO is ignored in two’s-complement operation.
Design Entry MethodThis design element is only for use in schematics.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 77
Chapter 3: About Design Elements
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries Guide78 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
ADSU1Macro: 1-Bit Cascadable Adder/Subtracter with Carry-In, Carry-Out
Supported ArchitecturesThis design element is supported in the following architectures only:
• XC9500
• CoolRunner™ XPLA3
• CoolRunner-II
IntroductionWhen the ADD input is High, this element adds two 1-bit words (A0 and B0) with a carry-in (CI), producing a1-bit output (S0) and a carry-out (CO). When the ADD input is Low, B0 is subtracted from A0, producinga result (S0) and borrow (CO).
In add mode, CO represents a carry-out, and CO and CI are active-High. In subtract mode, CO represents aborrow, and CO and CI are active-Low.
Add Function, ADD=1
Inputs Outputs
A0 B0 CI S0 CO
0 0 0 0 0
0 1 0 1 0
1 0 0 1 0
1 1 0 0 1
0 0 1 1 0
0 1 1 0 1
1 0 1 0 1
1 1 1 1 1
Subtract Function, ADD=0
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 79
Chapter 3: About Design Elements
Inputs Outputs
A0 B0 CI S0 CO
0 0 0 1 0
0 1 0 0 0
1 0 0 0 1
1 1 0 1 0
0 0 1 0 1
0 1 1 1 0
1 0 1 1 1
1 1 1 0 1
1 0 1 1 1
1 1 1 0 1
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries Guide80 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
ADSU16Macro: 16-Bit Cascadable Adder/Subtracter with Carry-In, Carry-Out, and Overflow
Supported ArchitecturesThis design element is supported in the following architectures only:• XC9500• CoolRunner™ XPLA3• CoolRunner-II
IntroductionWhen the ADD input is High, this element adds two 16-bit words (A15:A0 and B15:B0) and a carry-in (CI),producing a 16-bit sum output (S15:S0) and carry-out (CO) or overflow (OFL).
When the ADD input is Low, this element subtracts B15:B0 from A15:A0, producing a difference output anda carry-out (CO) or an overflow (OFL).
In add mode, CO and CI are active-High. In subtract mode, CO and CI are active-Low. OFL is active-High inadd and subtract modes.
Logic TableInput Output
ADD A B S
1 An Bn An+Bn+CI*
0 An Bn An-Bn-CI*
CI*: ADD = 0, CI, CO active LOW
CI*: ADD = 1, CI, CO active HIGH
Unsigned Binary Versus Two’s Complement
This design element can operate on either 16-bit unsigned binary numbers or 16-bit two’s-complement numbers.If the inputs are interpreted as unsigned binary, the result can be interpreted as unsigned binary. If the inputsare interpreted as two’s complement, the output can be interpreted as two’s complement. The only functionaldifference between an unsigned binary operation and a two’s-complement operation is the way they determinewhen “overflow” occurs. Unsigned binary uses CO, while two’s complement uses OFL to determine when“overflow” occurs.
With adder/subtracters, either unsigned binary or two’s-complement operations cause an overflow. If theresult crosses the overflow boundary, an overflow is generated. Similarly, when the result crosses the carry-outboundary, a carry-out is generated.
Unsigned Binary Operation
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 81
Chapter 3: About Design Elements
For unsigned binary operation, this element can represent numbers between 0 and 65535, inclusive. In addmode, CO is active (High) when the sum exceeds the bounds of the adder/subtracter. In subtract mode, CO is anactive-Low borrow-out and goes Low when the difference exceeds the bounds.
An unsigned binary “overflow” that is always active-High can be generated by gating the ADD signal and COas follows:
unsigned overflow = CO XOR ADD
OFL is ignored in unsigned binary operation.
Two’s-Complement Operation
For two’s-complement operation, this element can represent numbers between -32768 and +32767, inclusive.
If an addition or subtraction operation result exceeds this range, the OFL output goes High. CO is ignored intwo’s-complement operation.
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries Guide82 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
ADSU4Macro: 4-Bit Cascadable Adder/Subtracter with Carry-In, Carry-Out, and Overflow
Supported ArchitecturesThis design element is supported in the following architectures only:• XC9500• CoolRunner™ XPLA3• CoolRunner-II
IntroductionWhen the ADD input is High, this element adds two 4-bit words (A3:A0 and B3:B0) and a carry-in (CI),producing a 4-bit sum output (S3:S0) and a carry-out (CO) or an overflow (OFL).
When the ADD input is Low, this element subtracts B3:B0 from A3:A0, producing a 4-bit difference output(S3:S0) and a carry-out (CO) or an overflow (OFL).
In add mode, CO and CI are active-High. In subtract mode, CO and CI are active-Low. OFL is active-High inadd and subtract modes.
Logic TableInput Output
ADD A B S
1 An Bn An+Bn+CI*
0 An Bn An-Bn-CI*
CI*: ADD = 0, CI, CO active LOW
CI*: ADD = 1, CI, CO active HIGH
Unsigned Binary Versus Two’s Complement
This design element can operate on either 4-bit unsigned binary numbers or 4-bit two’s-complement numbers. Ifthe inputs are interpreted as unsigned binary, the result can be interpreted as unsigned binary. If the inputsare interpreted as two’s complement, the output can be interpreted as two’s complement. The only functionaldifference between an unsigned binary operation and a two’s-complement operation is the way they determinewhen “overflow” occurs. Unsigned binary uses CO, while two’s complement uses OFL to determine when“overflow” occurs.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 83
Chapter 3: About Design Elements
With adder/subtracters, either unsigned binary or two’s-complement operations cause an overflow. If theresult crosses the overflow boundary, an overflow is generated. Similarly, when the result crosses the carry-outboundary, a carry-out is generated.
Unsigned Binary Operation
For unsigned binary operation, ADSU4 can represent numbers between 0 and 15, inclusive. In add mode, CO isactive (High) when the sum exceeds the bounds of the adder/subtracter. In subtract mode, CO is an active-Lowborrow-out and goes Low when the difference exceeds the bounds.
An unsigned binary “overflow” that is always active-High can be generated by gating the ADD signal and COas follows:
unsigned overflow = CO XOR ADD
OFL is ignored in unsigned binary operation.
Two’s-Complement Operation
For two’s-complement operation, this element can represent numbers between -8 and +7, inclusive.
If an addition or subtraction operation result exceeds this range, the OFL output goes High. CO is ignored intwo’s-complement operation.
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries Guide84 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
ADSU8Macro: 8-Bit Cascadable Adder/Subtracter with Carry-In, Carry-Out, and Overflow
Supported ArchitecturesThis design element is supported in the following architectures only:• XC9500• CoolRunner™ XPLA3• CoolRunner-II
IntroductionWhen the ADD input is High, this element adds two 8-bit words (A7:A0 and B7:B0) and a carry-in (CI),producing, an 8-bit sum output (S7:S0) and carry-out (CO) or an overflow (OFL).
When the ADD input is Low, this element subtracts B7:B0 from A7:A0, producing an 8-bit difference output(S7:S0) and a carry-out (CO) or an overflow (OFL).
In add mode, CO and CI are active-High. In subtract mode, CO and CI are active-Low. OFL is active-High inadd and subtract modes.
Logic TableInput Output
ADD A B S
1 An Bn An+Bn+CI*
0 An Bn An-Bn-CI*
CI*: ADD = 0, CI, CO active LOW
CI*: ADD = 1, CI, CO active HIGH
Unsigned Binary Versus Two’s Complement
This design element can operate on either 8-bit unsigned binary numbers or 8-bit two’s-complement numbers. Ifthe inputs are interpreted as unsigned binary, the result can be interpreted as unsigned binary. If the inputsare interpreted as two’s complement, the output can be interpreted as two’s complement. The only functionaldifference between an unsigned binary operation and a two’s-complement operation is the way they determinewhen “overflow” occurs. Unsigned binary uses CO, while two’s complement uses OFL to determine when“overflow” occurs.
With adder/subtracters, either unsigned binary or two’s-complement operations cause an overflow. If theresult crosses the overflow boundary, an overflow is generated. Similarly, when the result crosses the carry-outboundary, a carry-out is generated.
Unsigned Binary Operation
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 85
Chapter 3: About Design Elements
For unsigned binary operation, this element can represent numbers between 0 and 255, inclusive. In add mode,CO is active (High) when the sum exceeds the bounds of the adder/subtracter. In subtract mode, CO is anactive-Low borrow-out and goes Low when the difference exceeds the bounds.
An unsigned binary “overflow” that is always active-High can be generated by gating the ADD signal and COas follows:unsigned overflow = CO XOR ADD
OFL is ignored in unsigned binary operation.
Two’s-Complement Operation
For two’s-complement operation, this element can represent numbers between -128 and +127, inclusive.
If an addition or subtraction operation result exceeds this range, the OFL output goes High. CO is ignored intwo’s-complement operation.
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries Guide86 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
AND2Primitive: 2-Input AND Gate with Non-Inverted Inputs
Supported ArchitecturesThis design element is supported in the following architectures only:
• XC9500
• CoolRunner™ XPLA3
• CoolRunner-II
IntroductionAND functions of up to five inputs are available in any combination of inverting and non-inverting inputs. ANDfunctions of six to nine inputs, 12 inputs, and 16 inputs are available with noninverting inputs. To make someor all inputs inverting, use external inverters. Because each input uses a CLB resource, replace functions withunused inputs with functions having the appropriate number of inputs.
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 87
Chapter 3: About Design Elements
AND2B1Primitive: 2-Input AND Gate with 1 Inverted and 1 Non-Inverted Inputs
Supported ArchitecturesThis design element is supported in the following architectures only:
• XC9500
• CoolRunner™ XPLA3
• CoolRunner-II
IntroductionAND functions of up to five inputs are available in any combination of inverting and non-inverting inputs. ANDfunctions of six to nine inputs, 12 inputs, and 16 inputs are available with noninverting inputs. To make someor all inputs inverting, use external inverters. Because each input uses a CLB resource, replace functions withunused inputs with functions having the appropriate number of inputs.
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries Guide88 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
AND2B2Primitive: 2-Input AND Gate with Inverted Inputs
Supported ArchitecturesThis design element is supported in the following architectures only:
• XC9500
• CoolRunner™ XPLA3
• CoolRunner-II
IntroductionAND functions of up to five inputs are available in any combination of inverting and non-inverting inputs. ANDfunctions of six to nine inputs, 12 inputs, and 16 inputs are available with noninverting inputs. To make someor all inputs inverting, use external inverters. Because each input uses a CLB resource, replace functions withunused inputs with functions having the appropriate number of inputs.
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 89
Chapter 3: About Design Elements
AND3Primitive: 3-Input AND Gate with Non-Inverted Inputs
Supported ArchitecturesThis design element is supported in the following architectures only:
• XC9500
• CoolRunner™ XPLA3
• CoolRunner-II
IntroductionAND functions of up to five inputs are available in any combination of inverting and non-inverting inputs. ANDfunctions of six to nine inputs, 12 inputs, and 16 inputs are available with noninverting inputs. To make someor all inputs inverting, use external inverters. Because each input uses a CLB resource, replace functions withunused inputs with functions having the appropriate number of inputs.
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries Guide90 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
AND3B1Primitive: 3-Input AND Gate with 1 Inverted and 2 Non-Inverted Inputs
Supported ArchitecturesThis design element is supported in the following architectures only:
• XC9500
• CoolRunner™ XPLA3
• CoolRunner-II
IntroductionAND functions of up to five inputs are available in any combination of inverting and non-inverting inputs. ANDfunctions of six to nine inputs, 12 inputs, and 16 inputs are available with noninverting inputs. To make someor all inputs inverting, use external inverters. Because each input uses a CLB resource, replace functions withunused inputs with functions having the appropriate number of inputs.
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 91
Chapter 3: About Design Elements
AND3B2Primitive: 3-Input AND Gate with 2 Inverted and 1 Non-Inverted Inputs
Supported ArchitecturesThis design element is supported in the following architectures only:
• XC9500
• CoolRunner™ XPLA3
• CoolRunner-II
IntroductionAND functions of up to five inputs are available in any combination of inverting and non-inverting inputs. ANDfunctions of six to nine inputs, 12 inputs, and 16 inputs are available with noninverting inputs. To make someor all inputs inverting, use external inverters. Because each input uses a CLB resource, replace functions withunused inputs with functions having the appropriate number of inputs.
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries Guide92 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
AND3B3Primitive: 3-Input AND Gate with Inverted Inputs
Supported ArchitecturesThis design element is supported in the following architectures only:
• XC9500
• CoolRunner™ XPLA3
• CoolRunner-II
IntroductionAND functions of up to five inputs are available in any combination of inverting and non-inverting inputs. ANDfunctions of six to nine inputs, 12 inputs, and 16 inputs are available with noninverting inputs. To make someor all inputs inverting, use external inverters. Because each input uses a CLB resource, replace functions withunused inputs with functions having the appropriate number of inputs.
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 93
Chapter 3: About Design Elements
AND4Primitive: 4-Input AND Gate with Non-Inverted Inputs
Supported ArchitecturesThis design element is supported in the following architectures only:
• XC9500
• CoolRunner™ XPLA3
• CoolRunner-II
IntroductionAND functions of up to five inputs are available in any combination of inverting and non-inverting inputs. ANDfunctions of six to nine inputs, 12 inputs, and 16 inputs are available with noninverting inputs. To make someor all inputs inverting, use external inverters. Because each input uses a CLB resource, replace functions withunused inputs with functions having the appropriate number of inputs.
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries Guide94 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
AND4B1Primitive: 4-Input AND Gate with 1 Inverted and 3 Non-Inverted Inputs
Supported ArchitecturesThis design element is supported in the following architectures only:
• XC9500
• CoolRunner™ XPLA3
• CoolRunner-II
IntroductionAND functions of up to five inputs are available in any combination of inverting and non-inverting inputs. ANDfunctions of six to nine inputs, 12 inputs, and 16 inputs are available with noninverting inputs. To make someor all inputs inverting, use external inverters. Because each input uses a CLB resource, replace functions withunused inputs with functions having the appropriate number of inputs.
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 95
Chapter 3: About Design Elements
AND4B2Primitive: 4-Input AND Gate with 2 Inverted and 2 Non-Inverted Inputs
Supported ArchitecturesThis design element is supported in the following architectures only:
• XC9500
• CoolRunner™ XPLA3
• CoolRunner-II
IntroductionAND functions of up to five inputs are available in any combination of inverting and non-inverting inputs. ANDfunctions of six to nine inputs, 12 inputs, and 16 inputs are available with noninverting inputs. To make someor all inputs inverting, use external inverters. Because each input uses a CLB resource, replace functions withunused inputs with functions having the appropriate number of inputs.
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries Guide96 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
AND4B3Primitive: 4-Input AND Gate with 3 Inverted and 1 Non-Inverted Inputs
Supported ArchitecturesThis design element is supported in the following architectures only:
• XC9500
• CoolRunner™ XPLA3
• CoolRunner-II
IntroductionAND functions of up to five inputs are available in any combination of inverting and non-inverting inputs. ANDfunctions of six to nine inputs, 12 inputs, and 16 inputs are available with noninverting inputs. To make someor all inputs inverting, use external inverters. Because each input uses a CLB resource, replace functions withunused inputs with functions having the appropriate number of inputs.
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 97
Chapter 3: About Design Elements
AND4B4Primitive: 4-Input AND Gate with Inverted Inputs
Supported ArchitecturesThis design element is supported in the following architectures only:
• XC9500
• CoolRunner™ XPLA3
• CoolRunner-II
IntroductionAND functions of up to five inputs are available in any combination of inverting and non-inverting inputs. ANDfunctions of six to nine inputs, 12 inputs, and 16 inputs are available with noninverting inputs. To make someor all inputs inverting, use external inverters. Because each input uses a CLB resource, replace functions withunused inputs with functions having the appropriate number of inputs.
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries Guide98 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
AND5Primitive: 5-Input AND Gate with Non-Inverted Inputs
Supported ArchitecturesThis design element is supported in the following architectures only:
• XC9500
• CoolRunner™ XPLA3
• CoolRunner-II
IntroductionAND functions of up to five inputs are available in any combination of inverting and non-inverting inputs. ANDfunctions of six to nine inputs, 12 inputs, and 16 inputs are available with noninverting inputs. To make someor all inputs inverting, use external inverters. Because each input uses a CLB resource, replace functions withunused inputs with functions having the appropriate number of inputs.
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 99
Chapter 3: About Design Elements
AND5B1Primitive: 5-Input AND Gate with 1 Inverted and 4 Non-Inverted Inputs
Supported ArchitecturesThis design element is supported in the following architectures only:
• XC9500
• CoolRunner™ XPLA3
• CoolRunner-II
IntroductionAND functions of up to five inputs are available in any combination of inverting and non-inverting inputs. ANDfunctions of six to nine inputs, 12 inputs, and 16 inputs are available with noninverting inputs. To make someor all inputs inverting, use external inverters. Because each input uses a CLB resource, replace functions withunused inputs with functions having the appropriate number of inputs.
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries Guide100 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
AND5B2Primitive: 5-Input AND Gate with 2 Inverted and 3 Non-Inverted Inputs
Supported ArchitecturesThis design element is supported in the following architectures only:
• XC9500
• CoolRunner™ XPLA3
• CoolRunner-II
IntroductionAND functions of up to five inputs are available in any combination of inverting and non-inverting inputs. ANDfunctions of six to nine inputs, 12 inputs, and 16 inputs are available with noninverting inputs. To make someor all inputs inverting, use external inverters. Because each input uses a CLB resource, replace functions withunused inputs with functions having the appropriate number of inputs.
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 101
Chapter 3: About Design Elements
AND5B3Primitive: 5-Input AND Gate with 3 Inverted and 2 Non-Inverted Inputs
Supported ArchitecturesThis design element is supported in the following architectures only:
• XC9500
• CoolRunner™ XPLA3
• CoolRunner-II
IntroductionAND functions of up to five inputs are available in any combination of inverting and non-inverting inputs. ANDfunctions of six to nine inputs, 12 inputs, and 16 inputs are available with noninverting inputs. To make someor all inputs inverting, use external inverters. Because each input uses a CLB resource, replace functions withunused inputs with functions having the appropriate number of inputs.
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries Guide102 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
AND5B4Primitive: 5-Input AND Gate with 4 Inverted and 1 Non-Inverted Inputs
Supported ArchitecturesThis design element is supported in the following architectures only:
• XC9500
• CoolRunner™ XPLA3
• CoolRunner-II
IntroductionAND functions of up to five inputs are available in any combination of inverting and non-inverting inputs. ANDfunctions of six to nine inputs, 12 inputs, and 16 inputs are available with noninverting inputs. To make someor all inputs inverting, use external inverters. Because each input uses a CLB resource, replace functions withunused inputs with functions having the appropriate number of inputs.
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 103
Chapter 3: About Design Elements
AND5B5Primitive: 5-Input AND Gate with Inverted Inputs
Supported ArchitecturesThis design element is supported in the following architectures only:
• XC9500
• CoolRunner™ XPLA3
• CoolRunner-II
IntroductionAND functions of up to five inputs are available in any combination of inverting and non-inverting inputs. ANDfunctions of six to nine inputs, 12 inputs, and 16 inputs are available with noninverting inputs. To make someor all inputs inverting, use external inverters. Because each input uses a CLB resource, replace functions withunused inputs with functions having the appropriate number of inputs.
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries Guide104 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
AND6Macro: 6-Input AND Gate with Non-Inverted Inputs
Supported ArchitecturesThis design element is supported in the following architectures only:
• XC9500
• CoolRunner™ XPLA3
• CoolRunner-II
IntroductionAND functions of up to five inputs are available in any combination of inverting and non-inverting inputs. ANDfunctions of six to nine inputs, 12 inputs, and 16 inputs are available with noninverting inputs. To make someor all inputs inverting, use external inverters. Because each input uses a CLB resource, replace functions withunused inputs with functions having the appropriate number of inputs.
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 105
Chapter 3: About Design Elements
AND7Macro: 7-Input AND Gate with Non-Inverted Inputs
Supported ArchitecturesThis design element is supported in the following architectures only:
• XC9500
• CoolRunner™ XPLA3
• CoolRunner-II
IntroductionAND functions of up to five inputs are available in any combination of inverting and non-inverting inputs. ANDfunctions of six to nine inputs, 12 inputs, and 16 inputs are available with noninverting inputs. To make someor all inputs inverting, use external inverters. Because each input uses a CLB resource, replace functions withunused inputs with functions having the appropriate number of inputs.
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries Guide106 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
AND8Macro: 8-Input AND Gate with Non-Inverted Inputs
Supported ArchitecturesThis design element is supported in the following architectures only:
• XC9500
• CoolRunner™ XPLA3
• CoolRunner-II
IntroductionAND functions of up to five inputs are available in any combination of inverting and non-inverting inputs. ANDfunctions of six to nine inputs, 12 inputs, and 16 inputs are available with noninverting inputs. To make someor all inputs inverting, use external inverters. Because each input uses a CLB resource, replace functions withunused inputs with functions having the appropriate number of inputs.
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 107
Chapter 3: About Design Elements
AND9Macro: 9-Input AND Gate with Non-Inverted Inputs
Supported ArchitecturesThis design element is supported in the following architectures only:
• XC9500
• CoolRunner™ XPLA3
• CoolRunner-II
IntroductionAND functions of up to five inputs are available in any combination of inverting and non-inverting inputs. ANDfunctions of six to nine inputs, 12 inputs, and 16 inputs are available with noninverting inputs. To make someor all inputs inverting, use external inverters. Because each input uses a CLB resource, replace functions withunused inputs with functions having the appropriate number of inputs.
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries Guide108 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
BRLSHFT4Macro: 4-Bit Barrel Shifter
Supported ArchitecturesThis design element is supported in the following architectures only:
• XC9500
• CoolRunner™ XPLA3
• CoolRunner-II
IntroductionThis design element is a 4-bit barrel shifter that can rotate four inputs (I3 : I0) up to four places. The controlinputs (S1 and S0) determine the number of positions, from one to four, that the data is rotated. The four outputs(O3 : O0) reflect the shifted data inputs.
Logic TableInputs Outputs
S1 S0 I0 I1 I2 I3 O0 O1 O2 O3
0 0 a b c d a b c d
0 1 a b c d b c d a
1 0 a b c d c d a b
1 1 a b c d d a b c
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 109
Chapter 3: About Design Elements
BRLSHFT8Macro: 8-Bit Barrel Shifter
Supported ArchitecturesThis design element is supported in the following architectures only:• XC9500• CoolRunner™ XPLA3• CoolRunner-II
IntroductionThis design element is an 8-bit barrel shifter, can rotate the eight inputs (I7 : I0) up to eight places. The controlinputs (S2 : S0) determine the number of positions, from one to eight, that the data is rotated. The eight outputs(O7 : O0) reflect the shifted data inputs.
Logic TableInputs Outputs
S2 S1 S0 I0 I1 I2 I3 I4 I5 I6 I7 O0 O1 O2 O3 O4 O5 O6 O7
0 0 0 a b c d e f g h a b c d e f g h
0 0 1 a b c d e f g h b c d e f g h a
0 1 0 a b c d e f g h c d e f g h a b
0 1 1 a b c d e f g h d e f g h a b c
1 0 0 a b c d e f g h e f g h a b c d
1 0 1 a b c d e f g h f g h a b c d e
1 1 0 a b c d e f g h g h a b c d e f
1 1 1 a b c d e f g h h a b c d e f g
Design Entry MethodThis design element is only for use in schematics.
CPLD Libraries Guide110 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 111
Chapter 3: About Design Elements
BUFPrimitive: General Purpose Buffer
Supported ArchitecturesThis design element is supported in the following architectures only:
• XC9500
• CoolRunner™ XPLA3
• CoolRunner-II
IntroductionThis is a general-purpose, non-inverting buffer.
This element is not necessary and is removed by the partitioning software (MAP).
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries Guide112 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
BUF16Macro: 16-Bit General Purpose Buffer
Supported ArchitecturesThis design element is supported in the following architectures only:
• XC9500
• CoolRunner™ XPLA3
• CoolRunner-II
IntroductionThis is a 16-bit, general purpose, non-inverting buffer. In working with CPLDs, this element is usuallyremoved, unless you inhibit optimization by applying the OPT=OFF attribute to the symbol, or by using theLOGIC_OPT=OFF global attribute.
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 113
Chapter 3: About Design Elements
BUF4Macro: 4-Bit General Purpose Buffer
Supported ArchitecturesThis design element is supported in the following architectures only:
• XC9500
• CoolRunner™ XPLA3
• CoolRunner-II
IntroductionThis is a 4-bit, general purpose, non-inverting buffer. In working with CPLDs, this element is usuallyremoved, unless you inhibit optimization by applying the OPT=OFF attribute to the symbol, or by using theLOGIC_OPT=OFF global attribute.
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries Guide114 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
BUF8Macro: 8-Bit General Purpose Buffer
Supported ArchitecturesThis design element is supported in the following architectures only:
• XC9500
• CoolRunner™ XPLA3
• CoolRunner-II
IntroductionThis is a 8-bit, general purpose, non-inverting buffer. In working with CPLDs, this element is usuallyremoved, unless you inhibit optimization by applying the OPT=OFF attribute to the symbol, or by using theLOGIC_OPT=OFF global attribute.
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 115
Chapter 3: About Design Elements
BUFEPrimitive: Internal 3-State Buffer with Active High Enable
Supported ArchitecturesThis design element is supported in the following architectures only:
• XC9500
• CoolRunner™ XPLA3
IntroductionThis design element is a single, 3-state buffer with input I and output O, and an active-High output enable (E).When E is High, data on the input of the buffer is transferred to the corresponding output. When E is Low, theoutput is high impedance (Z state or Off). The outputs of the buffers are connected to horizontal longlinesin FPGA architectures.
The outputs of separate symbols for this entity can be tied together to form a bus or a multiplexer. Make surethat only one E is High at any one time. If none of the E inputs is active-High, a “weak-keeper” circuit keepsthe output bus from floating but does not guarantee that the bus remains at the last value driven onto it. Forcertain CPLD devices, output from nets assume the High logic level when all connected BUFE/BUFT buffersare disabled. For FPGA devices, elements need a PULLUP element connected to their output. NGDBuildinserts a PULLUP element if one is not connected.
Logic TableInputs Outputs
E I O
0 X Z
1 1 1
1 0 0
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries Guide116 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
BUFE16Macro: 16-Bit Internal 3-State Buffer with Active High Enable
Supported ArchitecturesThis design element is supported in the following architectures only:
• XC9500
• CoolRunner™ XPLA3
IntroductionThis design element is a multiple 3-state buffer with inputs of I15 : I0 and outputs of O15 : O0 and an active-Highoutput enable (E). When E is High, data on the inputs of the buffers is transferred to the corresponding outputs.
When E is Low, the output is high impedance (Z state or Off). The outputs of the buffers are connected tohorizontal longlines in FPGA architectures. The outputs of separate BUFE elements can be tied together toform a bus or a multiplexer. Make sure that only one E is High at any one time. If none of the E inputs isactive-High, a “weak-keeper” circuit keeps the output bus from floating but does not guarantee that the busremains at the last value driven onto it.
Logic TableInputs Outputs
E I O
0 X Z
1 1 1
1 0 0
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 117
Chapter 3: About Design Elements
BUFE4Macro: 4-BitInternal 3-State Buffer with Active High Enable
Supported ArchitecturesThis design element is supported in the following architectures only:• XC9500• CoolRunner™ XPLA3
IntroductionThis design element is a multiple 3-state buffer with inputs of I3 : I0 and outputs of O3 : O0 and an active-Highoutput enable (E). When E is High, data on the inputs of the buffers is transferred to the corresponding outputs.
When E is Low, the output is high impedance (Z state or Off). The outputs of the buffers are connected tohorizontal longlines in FPGA architectures. The outputs of separate BUFE elements can be tied together toform a bus or a multiplexer. Make sure that only one E is High at any one time. If none of the E inputs isactive-High, a “weak-keeper” circuit keeps the output bus from floating but does not guarantee that the busremains at the last value driven onto it.
Logic TableInputs Outputs
E I O
0 X Z
1 1 1
1 0 0
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.• See the appropriate CPLD Data Sheets.
CPLD Libraries Guide118 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
BUFE8Macro: 8-Bit Internal 3-State Buffer with Active High Enable
Supported ArchitecturesThis design element is supported in the following architectures only:
• XC9500
• CoolRunner™ XPLA3
IntroductionThis design element is a multiple 3-state buffer with inputs of I7 : I0 and outputs of O7 : O0 and an active-Highoutput enable (E). When E is High, data on the inputs of the buffers is transferred to the corresponding outputs.
When E is Low, the output is high impedance (Z state or Off). The outputs of the buffers are connected tohorizontal longlines in FPGA architectures. The outputs of separate BUFE elements can be tied together toform a bus or a multiplexer. Make sure that only one E is High at any one time. If none of the E inputs isactive-High, a “weak-keeper” circuit keeps the output bus from floating but does not guarantee that the busremains at the last value driven onto it.
Logic TableInputs Outputs
E I O
0 X Z
1 1 1
1 0 0
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 119
Chapter 3: About Design Elements
BUFGPrimitive: Global Clock Buffer
Supported ArchitecturesThis design element is supported in the following architectures only:
• XC9500
• CoolRunner™ XPLA3
• CoolRunner-II
IntroductionThis design element is a high-fanout buffer that connects signals to the global routing resources for low skewdistribution of the signal. BUFGs are typically used on clock nets.
Port DescriptionsPort Type Width Function
I Input 1 Clock buffer output
O Output 1 Clock buffer input
Design Entry MethodThis design element can be used in schematics.
VHDL Instantiation TemplateUnless they already exist, copy the following two statements and paste them before the entity declaration.
Library UNISIM;use UNISIM.vcomponents.all;
-- BUFG: Global Clock Buffer-- Virtex-6-- Xilinx HDL Libraries Guide, version 11.2
BUFG_inst : BUFGgeneric map ()port map (
O => O, -- 1-bit Clock buffer outputI => I -- 1-bit Clock buffer input
);
-- End of BUFG_inst instantiation
CPLD Libraries Guide120 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
Verilog Instantiation Template// BUFG: Global Clock Buffer (source by an internal signal)// All FPGAs// Xilinx HDL Libraries Guide, version 11.2
BUFG BUFG_inst (.O(O), // Clock buffer output.I(I) // Clock buffer input
);
// End of BUFG_inst instantiation
For More Information• See the appropriate CPLD User Guide.
• See the appropriate EDK documentation.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 121
Chapter 3: About Design Elements
BUFGSRPrimitive: Global Set/Reset Input Buffer
Supported ArchitecturesThis design element is supported in the following architectures only:
• XC9500
• CoolRunner™ XPLA3
• CoolRunner-II
IntroductionThis design element distributes Global Set/Reset (GSR) signals throughout selected flip-flops of anXC9500/XV/XL, CoolRunner™ XPLA3, or CoolRunner™-II device. Global Set/Reset (GSR) control pins areavailable on these CPLD devices. Consult device data sheets for availability.
This design element always acts as an input buffer. To use it in a schematic, connect the input of the designelement symbol to an IPAD or an IOPAD representing the GSR signal source. GSR signals generated on-chipmust be passed through an OBUF-type buffer before they are connected to the design element.
For Global Set/Reset (GSR) control, the output of the design element normally connects to the CLR or PREinput of a flip-flop symbol, like FDCP, or any registered symbol with asynchronous clear or preset. The GlobalSet/Reset (GSR) control signal may pass through an inverter to perform an active-low set/reset. The output of thedesign element may also be used as an ordinary input signal to other logic elsewhere in the design. This designelement can control any number of flip-flops in a design.
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries Guide122 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
BUFGTSPrimitive: Global 3-State Input Buffer
Supported ArchitecturesThis design element is supported in the following architectures only:
• XC9500
• CoolRunner™ XPLA3
• CoolRunner-II
IntroductionThis design element distributes global output-enable signals throughout the output pad drivers of CPLD devices.Global Three-State (GTS) control pins are available on these CPLD devices. Consult device data sheets foravailability.
This element always acts as an input buffer. To use it in a schematic, connect the input of the BUFGTS symbolto an IPAD or an IOPAD representing the GTS signal source. GTS signals generated on-chip must be passedthrough an OBUF-type buffer before they are connected to this element.
For global 3-state control, the output of this element normally connects to the E input of a 3-state output buffersymbol, OBUFE. The global 3-state control signal may pass through an inverter or control an OBUFT symbolto perform an active-low output-enable. The same 3-state control signal may even be used both inverted andnon-inverted to enable alternate groups of device outputs. The output of BUFGTS may also be used as anordinary input signal to other logic elsewhere in the design. Each BUFGTS can control any number of outputbuffers in a design.
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 123
Chapter 3: About Design Elements
BUFTPrimitive: Internal 3-State Buffer with Active Low Enable
Supported ArchitecturesThis design element is supported in the following architectures only:
• XC9500
• CoolRunner™ XPLA3
IntroductionThis design element is a single 3-state buffer with input I and an output of O and active-Low output enable (T).When T is Low, data on the input of the buffer is transferred to the corresponding output. When T is High,the output is high impedance (Z state or off). The output of the buffer is connected to a horizontal longlinein FPGA architectures.
The output of separate BUFT symbols can be tied together to form a bus or a multiplexer. Make sure that onlyone T is Low at one time. For CPLD devices, BUFT output nets assume the High logic level when all connectedBUFE/BUFT buffers are disabled. For FPGAs, when all BUFTs on a net are disabled, the net is High. For correctsimulation of this effect, a PULLUP element must be connected to the net. NGDBuild inserts a PULLUP elementif one is not connected so that back-annotation simulation reflects the true state of the device.
Logic TableInputs Outputs
T I O
1 X Z
0 1 1
0 0 0
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries Guide124 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
BUFT16Macro: 16-Bit Internal 3-State Buffers with Active Low Enable
Supported ArchitecturesThis design element is supported in the following architectures only:
• XC9500
• CoolRunner™ XPLA3
IntroductionThis design element is a multiple 3-state buffer with inputs I15:10 and outputs O15:O0 and active-Low outputenable (T). When T is Low, data on the inputs of the buffers is transferred to the corresponding outputs. When Tis High, the output is high impedance (Z state or off). The outputs of the buffers are connected to horizontallonglines in FPGA architectures.
The output of separate BUFT symbols can be tied together to form a bus or a multiplexer. Make sure that onlyone T is Low at one time. For CPLD devices, BUFT output nets assume the High logic level when all connectedBUFE/BUFT buffers are disabled. For FPGAs, when all BUFTs on a net are disabled, the net is High. For correctsimulation of this effect, a PULLUP element must be connected to the net. NGDBuild inserts a PULLUP elementif one is not connected so that back-annotation simulation reflects the true state of the device.
Logic TableInputs Outputs
T I O
1 X Z
0 1 1
0 0 0
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 125
Chapter 3: About Design Elements
BUFT4Macro: 4-Bit Internal 3-State Buffers with Active Low Enable
Supported ArchitecturesThis design element is supported in the following architectures only:• XC9500• CoolRunner™ XPLA3
IntroductionThis design element is a multiple 3-state buffer with inputs I3:I0 and outputs O3:O0 and active-Low outputenable (T). When T is Low, data on the inputs of the buffers is transferred to the corresponding outputs. When Tis High, the output is high impedance (Z state or off). The outputs of the buffers are connected to horizontallonglines in FPGA architectures.
The output of separate BUFT symbols can be tied together to form a bus or a multiplexer. Make sure that onlyone T is Low at one time. For CPLD devices, BUFT output nets assume the High logic level when all connectedBUFE/BUFT buffers are disabled. For FPGAs, when all BUFTs on a net are disabled, the net is High. For correctsimulation of this effect, a PULLUP element must be connected to the net. NGDBuild inserts a PULLUP elementif one is not connected so that back-annotation simulation reflects the true state of the device.
Logic TableInputs Outputs
T I O
1 X Z
0 1 1
0 0 0
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.• See the appropriate CPLD Data Sheets.
CPLD Libraries Guide126 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
BUFT8Macro: 8-Bit Internal 3-State Buffers with Active Low Enable
Supported ArchitecturesThis design element is supported in the following architectures only:
• XC9500
• CoolRunner™ XPLA3
IntroductionThis design element is a multiple 3-state buffer with inputs I7:I0 and outputs O7:O0 and active-Low outputenable (T). When T is Low, data on the inputs of the buffers is transferred to the corresponding outputs. When Tis High, the output is high impedance (Z state or off). The outputs of the buffers are connected to horizontallonglines in FPGA architectures.
The output of separate BUFT symbols can be tied together to form a bus or a multiplexer. Make sure that onlyone T is Low at one time. For CPLD devices, BUFT output nets assume the High logic level when all connectedBUFE/BUFT buffers are disabled. For FPGAs, when all BUFTs on a net are disabled, the net is High. For correctsimulation of this effect, a PULLUP element must be connected to the net. NGDBuild inserts a PULLUP elementif one is not connected so that back-annotation simulation reflects the true state of the device.
Logic TableInputs Outputs
T I O
1 X Z
0 1 1
0 0 0
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 127
Chapter 3: About Design Elements
CB16CEMacro: 16-Bit Cascadable Binary Counter with Clock Enable and Asynchronous Clear
Supported ArchitecturesThis design element is supported in the following architectures only:• XC9500• CoolRunner™ XPLA3• CoolRunner-II
IntroductionThis design element is an asynchronously clearable, cascadable binary counter. The asynchronous clear (CLR)input, when High, overrides all other inputs and forces the Q outputs, terminal count (TC), and clock enable out(CEO) to logic level zero, independent of clock transitions. The Q outputs increment when the clock enable input(CE) is High during the Low-to-High clock (C) transition. The counter ignores clock transitions when CE is Low.The TC output is High when all Q outputs are High.
Create larger counters by connecting the CEO output of each stage to the CE input of the next stage andconnecting the C and CLR inputs in parallel. CEO is active (High) when TC and CE are High. The maximumlength of the counter is determined by the accumulated CE-to-TC propagation delays versus the clock period.The clock period must be greater than n (tCE-TC), where n is the number of stages and the time tCE-TC is theCE-to-TC propagation delay of each stage. When cascading counters, use the CEO output if the counter uses theCE input or use the TC output if it does not.
This counter is asynchronously cleared, outputs Low, when power is applied. For CPLD devices, you cansimulate power-on by applying a High-level pulse on the PRLD global net.
Logic TableInputs Outputs
CLR CE C Qz-Q0 TC CEO
1 X X 0 0 0
0 0 X No change No change 0
0 1 ↑ Inc TC CEO
z = bit width - 1
TC = Qz•Q(z-1)•Q(z-2)•...•Q0
CEO = TC•CE
Design Entry MethodThis design element is only for use in schematics.
CPLD Libraries Guide128 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 129
Chapter 3: About Design Elements
CB16CLEMacro: 16-Bit Loadable Cascadable Binary Counters with Clock Enable and Asynchronous Clear
Supported ArchitecturesThis design element is supported in the following architectures only:
• XC9500
• CoolRunner™ XPLA3
• CoolRunner-II
IntroductionThis element is a synchronously loadable, asynchronously clearable, cascadable binary counter. Theasynchronous clear (CLR) input, when High, overrides all other inputs and forces the Q outputs, terminalcount (TC), and clock enable out (CEO) to logic level zero, independent of clock transitions. The data on theD inputs is loaded into the counter when the load enable input (L) is High during the Low-to-High clocktransition, independent of the state of clock enable (CE). The Q outputs increment when CE is High during theLow-to-High clock transition. The counter ignores clock transitions when CE is Low. The TC output is Highwhen all Q outputs are High.
Create larger counters by connecting the CEO output of each stage to the CE input of the next stage andconnecting the C, L, and CLR inputs in parallel. CEO is active (High) when TC and CE are High. The maximumlength of the counter is determined by the accumulated CE-to-TC propagation delays versus the clock period.The clock period must be greater than n (tCE-TC), where n is the number of stages and the time tCE-TC is theCE-to-TC propagation delay of each stage. When cascading counters, use the CEO output if the counter uses theCE input or use the TC output if it does not.
This counter is asynchronously cleared, outputs Low, when power is applied. For CPLD devices, you cansimulate power-on by applying a High-level pulse on the PRLD global net.
CPLD Libraries Guide130 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
Logic TableInputs Outputs
CLR L CE C Dz-D0 Qz-Q0 TC CEO
1 X X X X 0 0 0
0 1 X ↑ Dn Dn TC CEO
0 0 0 X X No change No change 0
0 0 1 ↑ X Inc TC CEO
z = bit width - 1
TC = Qz•Q(z-1)•Q(z-2)•...•Q0
CEO = TC•CE
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 131
Chapter 3: About Design Elements
CB16CLEDMacro: 16-Bit Loadable Cascadable Bidirectional Binary Counters with Clock Enable andAsynchronous Clear
Supported ArchitecturesThis design element is supported in the following architectures only:
• XC9500
• CoolRunner™ XPLA3
• CoolRunner-II
IntroductionThis design element is a synchronously loadable, asynchronously clearable, cascadable, bidirectional binarycounter. The asynchronous clear (CLR) input, when High, overrides all other inputs and forces the Q outputs,terminal count (TC), and clock enable out (CEO) to logic level zero, independent of clock transitions. The data onthe D inputs is loaded into the counter when the load enable input (L) is High during the Low-to-High clock(C) transition, independent of the state of clock enable (CE). The Q outputs decrement when CE is High andUP is Low during the Low-to- High clock transition. The Q outputs increment when CE and UP are High. Thecounter ignores clock transitions when CE is Low.
For counting up, the TC output is High when all Q outputs and UP are High. For counting down, the TCoutput is High when all Q outputs and UP are Low.
Create larger counters by connecting the CEO output of each stage to the CE input of the next stage andconnecting the C, UP, L, and CLR inputs in parallel. CEO is active (High) when TC and CE are High. Themaximum length of the counter is determined by the accumulated CE-to-TC propagation delays versus the clockperiod. The clock period must be greater than n (tCE-TC), where n is the number of stages and the time tCE-TC isthe CE-to-TC propagation delay of each stage. When cascading counters, use the CEO output if the counteruses the CE input or use the TC output if it does not.
For CPLD parts, see “CB2X1”, “CB4X1”, “CB8X1”, “CB16X1” for high-performance cascadable, bidirectionalcounters.
This counter is asynchronously cleared, outputs Low, when power is applied. For CPLD devices, you cansimulate power-on by applying a High-level pulse on the PRLD global net.
CPLD Libraries Guide132 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
Logic TableInputs Outputs
CLR L CE C UP Dz-D0 Qz-Q0 TC CEO
1 X X X X X 0 0 0
0 1 X ↑ X Dn Dn TC CEO
0 0 0 X X X No change No change 0
0 0 1 ↑ 1 X Inc TC CEO
0 0 1 ↑ 0 X Dec TC CEO
z = bit width - 1
TC = (Qz•Q(z-1)•Q(z-2)•...•Q0•UP) + (Qz•Q(z-1)•Q(z-2)•...•Q0•UP)
CEO = TC•CE
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 133
Chapter 3: About Design Elements
CB16REMacro: 16-Bit Cascadable Binary Counter with Clock Enable and Synchronous Reset
Supported ArchitecturesThis design element is supported in the following architectures only:• XC9500• CoolRunner™ XPLA3• CoolRunner-II
IntroductionThis design element is a synchronous, resettable, cascadable binary counter. The synchronous reset (R), whenHigh, overrides all other inputs and forces the Q outputs, terminal count (TC), and clock enable out (CEO) tozero on the Low-to-High clock transition. The Q outputs increment when the clock enable input (CE) is Highduring the Low-to-High clock (C) transition. The counter ignores clock transitions when CE is Low. The TCoutput is High when both Q outputs are High.
Create larger counters by connecting the CEO output of each stage to the CE input of the next stage andconnecting the C and R inputs in parallel. CEO is active (High) when TC and CE are High. The maximum lengthof the counter is determined by the accumulated CE-to-TC propagation delays versus the clock period. Theclock period must be greater than n (tCE-TC), where n is the number of stages and the time tCE-TC is the CE-to-TCpropagation delay of each stage. When cascading counters, use the CEO output if the counter uses the CEinput or use the TC output if it does not.
This counter is asynchronously cleared, outputs Low, when power is applied. For CPLD devices, you cansimulate power-on by applying a High-level pulse on the PRLD global net.
Logic TableInputs Outputs
R CE C Qz-Q0 TC CEO
1 X ↑ 0 0 0
0 0 X No change No change 0
0 1 ↑ Inc TC CEO
z = bit width - 1
TC = Qz•Q(z-1)•Q(z-2)•...•Q0)
CEO = TC•CE
Design Entry MethodThis design element is only for use in schematics.
CPLD Libraries Guide134 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 135
Chapter 3: About Design Elements
CB16RLEMacro: 16-Bit Loadable Cascadable Binary Counter with Clock Enable and Synchronous Reset
Supported ArchitecturesThis design element is supported in the following architectures only:
• XC9500
• CoolRunner™ XPLA3
• CoolRunner-II
IntroductionThis design element is a synchronous, loadable, resettable, cascadable binary counter. The synchronous reset(R), when High, overrides all other inputs and forces the Q outputs, terminal count (TC), and clock enable out(CEO) to zero on the Low-to-High clock (C) transition.
The data on the D inputs is loaded into the counter when the load enable input (L) is High during theLow-to-High clock (C) transition, independent of the state of CE. The Q outputs increment when CE is Highduring the Low-to-High clock transition. The counter ignores clock transitions when CE is Low. The TC outputis High when all Q outputs are High. The CEO output is High when all Q outputs and CE are High to allowdirect cascading of counters.
Create larger counters by connecting the CEO output of each stage to the CE input of the next stage andconnecting the C, L, and R inputs in parallel. CEO is active (High) when TC and CE are High. The maximumlength of the counter is determined by the accumulated CE-to-TC propagation delays versus the clock period.The clock period must be greater than n (tCE-TC), where n is the number of stages and the time tCE-TC is theCE-to-TC propagation delay of each stage. When cascading counters, use the CEO output if the counter uses theCE input or use the TC output if it does not.
This counter is asynchronously cleared, outputs Low, when power is applied. For CPLD devices, you cansimulate power-on by applying a High-level pulse on the PRLD global net.
CPLD Libraries Guide136 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
Logic TableInputs Outputs
R L CE C Dz-D0 Qz-Q0 TC CEO
1 X X ↑ X 0 0 0
0 1 X ↑ Dn Dn TC CEO
0 0 0 X X No change No change 0
0 0 1 ↑ X Inc TC CEO
z = bit width - 1
TC = Qz•Q(z-1)•Q(z-2)•...•Q0
CEO = TC•CE
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 137
Chapter 3: About Design Elements
CB16X1Macro: 16-Bit Loadable Cascadable Bidirectional Binary Counter with Clock Enable andAsynchronous Clear
Supported ArchitecturesThis design element is supported in the following architectures only:• XC9500• CoolRunner™ XPLA3• CoolRunner-II
IntroductionThis design element is a synchronously loadable, asynchronously clearable, bidirectional binary counter. It hasseparate count-enable inputs and synchronous terminal-count outputs for up and down directions to supporthigh-speed cascading.
The asynchronous clear (CLR) is the highest priority input. When CLR is High, all other inputs are ignored; dataoutputs (Q) go to logic level zero, terminal count outputs TCU and TCD go to zero and one, respectively, clockenable outputs CEOU and CEOD go to Low and High, respectively, independent of clock transitions. The dataon the D inputs loads into the counter on the Low-to-High clock (C) transition when the load enable input (L)is High, independent of the CE inputs.
The Q outputs increment when CEU is High, provided CLR and L are Low, during the Low-to-High clocktransition. The Q outputs decrement when CED is High, provided CLR and L are Low. The counter ignoresclock transitions when CEU and CED are Low. Both CEU and CED should not be High during the same clocktransition; the CEOU and CEOD outputs might not function properly for cascading when CEU and CED areboth High.
For counting up, the CEOU output is High when all Q outputs and CEU are High. For counting down, theCEOD output is High when all Q outputs are Low and CED is High. To cascade counters, connect the CEOU andCEOD outputs of each counter directly to the CEU and CED inputs, respectively, of the next stage. Connectthe clock, L, and CLR inputs in parallel.
The maximum clocking frequency of these counter components is unaffected by the number of cascaded stagesfor all counting and loading functions. The TCU terminal count output is High when all Q outputs are High,regardless of CEU. The TCD output is High when all Q outputs are Low, regardless of CED.
When cascading counters, the final terminal count signals can be produced by AND wiring all the TCU outputs(for the up direction) and all the TCD outputs (for the down direction). The TCU, CEOU, and CEOD outputs areproduced by optimizable AND gates within the component. This results in zero propagation from the CEUand CED inputs and from the Q outputs, provided all connections from each such output remain on-chip.Otherwise, a macrocell buffer delay is introduced.
The counter is initialized to zero (TCU Low and TCD High) when power is applied. You can simulate power-onby applying a High-level pulse on the PRLD global net.
CPLD Libraries Guide138 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
Logic TableInputs Outputs
CLR L CEU CED C Dz-D0 Qz-Q0 TCU TCD CEOU CEOD
1 X X X X X 0 0 1 0 CEOD
0 1 X X ↑ Dn Dn TCU TCD CEOU CEOD
0 0 0 0 X X NoChange
NoChange
NoChange
0 0
0 0 1 0 ↑ X Inc TCU TCD CEOU 0
0 0 0 1 ↑ X Dec TCU TCD 0 CEOD
0 0 1 1 ↑ X Inc TCU TCD Invalid Invalid
z = bit width - 1
TCU = Qz•Q(z-1)•Q(z-2)•...•Q0
TCD = Qz•Q(z-1)•Q(z-2)•...•Q0
CEOU = TCU•CEU
CEOD = TCD•CED
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 139
Chapter 3: About Design Elements
CB16X2Macro: 16-Bit Loadable Cascadable Bidirectional Binary Counter with Clock Enable andSynchro-nous Reset
Supported ArchitecturesThis design element is supported in the following architectures only:
• XC9500
• CoolRunner™ XPLA3
• CoolRunner-II
IntroductionThis design element is a synchronous, loadable, resettable, bidirectional binary counter. It has separatecount-enable inputs and synchronous terminal-count outputs for up and down directions to support high-speedcascading in CPLD architectures.
The synchronous reset (R) is the highest priority input. When R is High, all other inputs are ignored; the dataoutputs (Q) go to logic level zero, terminal count outputs TCU and TCD go to zero and one, respectively,and clock enable outputs CEOU and CEOD go to Low and High, respectively, on the Low-to-High clock (C)transition. The data on the D inputs loads into the counter on the Low-to-High clock (C) transition when the loadenable input (L) is High, independent of the CE inputs.
All Q outputs increment when CEU is High, provided R and L are Low during the Low-to-High clock transition.All Q outputs decrement when CED is High, provided R and L are Low. The counter ignores clock transitionswhen CEU and CED are Low. Both CEU and CED should not be High during the same clock transition; theCEOU and CEOD outputs might not function properly for cascading when CEU and CED are both High.
For counting up, the CEOU output is High when all Q outputs and CEU are High. For counting down, theCEOD output is High when all Q outputs are Low and CED is High. To cascade counters, the CEOU and CEODoutputs of each counter are, respectively, connected directly to the CEU and CED inputs of the next stage. The C,L, and R inputs are connected in parallel.
The maximum clocking frequency of these counter components is unaffected by the number of cascaded stagesfor all counting and loading functions. The TCU terminal count output is High when all Q outputs are High,regardless of CEU. The TCD output is High when all Q outputs are Low, regardless of CED.
When cascading counters, the final terminal count signals can be produced by AND wiring all the TCU outputs(for the up direction) and all the TCD outputs (for the down direction). The TCU, CEOU, and CEOD outputs areproduced by optimizable AND gates within the component. This results in zero propagation from the CEUand CED inputs and from the Q outputs, provided all connections from each such output remain on-chip.Otherwise, a macrocell buffer delay is introduced.
The counter is initialized to zero (TCU Low and TCD High) when power is applied. You can simulate power-onby applying a High-level pulse on the PRLD global net.
CPLD Libraries Guide140 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
Logic TableInputs Outputs
R L CEU CED C Dz-D0 Qz-Q0 TCU TCD CEOU CEOD
1 X X X ↑ X 0 0 1 0 CEOD
0 1 X X ↑ Dn Dn TCU TCD CEOU CEOD
0 0 0 0 X X No Chg No Chg No Chg 0 0
0 0 1 0 ↑ X Inc TCU TCD CEOU 0
0 0 0 1 ↑ X Dec TCU TCD 0 CEOD
0 0 1 1 ↑ X Inc TCU TCD Invalid Invalid
z = bit width - 1
TCU = Qz•Q(z-1)•Q(z-2)•...•Q0
TCD = Qz•Q(z-1)•Q(z-2)•...•Q0
CEOU = TCU•CEU
CEOD = TCD•CED
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 141
Chapter 3: About Design Elements
CB2CEMacro: 2-Bit Cascadable Binary Counter with Clock Enable and Asynchronous Clear
Supported ArchitecturesThis design element is supported in the following architectures only:• XC9500• CoolRunner™ XPLA3• CoolRunner-II
IntroductionThis design element is an asynchronously clearable, cascadable binary counter. The asynchronous clear (CLR)input, when High, overrides all other inputs and forces the Q outputs, terminal count (TC), and clock enable out(CEO) to logic level zero, independent of clock transitions. The Q outputs increment when the clock enable input(CE) is High during the Low-to-High clock (C) transition. The counter ignores clock transitions when CE is Low.The TC output is High when all Q outputs are High.
Create larger counters by connecting the CEO output of each stage to the CE input of the next stage andconnecting the C and CLR inputs in parallel. CEO is active (High) when TC and CE are High. The maximumlength of the counter is determined by the accumulated CE-to-TC propagation delays versus the clock period.The clock period must be greater than n (tCE-TC), where n is the number of stages and the time tCE-TC is theCE-to-TC propagation delay of each stage. When cascading counters, use the CEO output if the counter uses theCE input or use the TC output if it does not.
This counter is asynchronously cleared, outputs Low, when power is applied. For CPLD devices, you cansimulate power-on by applying a High-level pulse on the PRLD global net.
Logic TableInputs Outputs
CLR CE C Qz-Q0 TC CEO
1 X X 0 0 0
0 0 X No change No change 0
0 1 ↑ Inc TC CEO
z = bit width - 1
TC = Qz•Q(z-1)•Q(z-2)•...•Q0
CEO = TC•CE
Design Entry MethodThis design element is only for use in schematics.
CPLD Libraries Guide142 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 143
Chapter 3: About Design Elements
CB2CLEMacro: 2-Bit Loadable Cascadable Binary Counters with Clock Enable and Asynchronous Clear
Supported ArchitecturesThis design element is supported in the following architectures only:• XC9500• CoolRunner™ XPLA3• CoolRunner-II
IntroductionThis element is a synchronously loadable, asynchronously clearable, cascadable binary counter. Theasynchronous clear (CLR) input, when High, overrides all other inputs and forces the Q outputs, terminalcount (TC), and clock enable out (CEO) to logic level zero, independent of clock transitions. The data on theD inputs is loaded into the counter when the load enable input (L) is High during the Low-to-High clocktransition, independent of the state of clock enable (CE). The Q outputs increment when CE is High during theLow-to-High clock transition. The counter ignores clock transitions when CE is Low. The TC output is Highwhen all Q outputs are High.
Create larger counters by connecting the CEO output of each stage to the CE input of the next stage andconnecting the C, L, and CLR inputs in parallel. CEO is active (High) when TC and CE are High. The maximumlength of the counter is determined by the accumulated CE-to-TC propagation delays versus the clock period.The clock period must be greater than n (tCE-TC), where n is the number of stages and the time tCE-TC is theCE-to-TC propagation delay of each stage. When cascading counters, use the CEO output if the counter uses theCE input or use the TC output if it does not.
This counter is asynchronously cleared, outputs Low, when power is applied. For CPLD devices, you cansimulate power-on by applying a High-level pulse on the PRLD global net.
Logic TableInputs Outputs
CLR L CE C Dz-D0 Qz-Q0 TC CEO
1 X X X X 0 0 0
0 1 X ↑ Dn Dn TC CEO
0 0 0 X X No change No change 0
0 0 1 ↑ X Inc TC CEO
z = bit width - 1
TC = Qz•Q(z-1)•Q(z-2)•...•Q0
CPLD Libraries Guide144 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
Inputs Outputs
CLR L CE C Dz-D0 Qz-Q0 TC CEO
CEO = TC•CE
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 145
Chapter 3: About Design Elements
CB2CLEDMacro: 2-Bit Loadable Cascadable Bidirectional Binary Counters with Clock Enable andAsynchronous Clear
Supported ArchitecturesThis design element is supported in the following architectures only:
• XC9500
• CoolRunner™ XPLA3
• CoolRunner-II
IntroductionThis design element is a synchronously loadable, asynchronously clearable, cascadable, bidirectional binarycounter. The asynchronous clear (CLR) input, when High, overrides all other inputs and forces the Q outputs,terminal count (TC), and clock enable out (CEO) to logic level zero, independent of clock transitions. The data onthe D inputs is loaded into the counter when the load enable input (L) is High during the Low-to-High clock(C) transition, independent of the state of clock enable (CE). The Q outputs decrement when CE is High andUP is Low during the Low-to- High clock transition. The Q outputs increment when CE and UP are High. Thecounter ignores clock transitions when CE is Low.
For counting up, the TC output is High when all Q outputs and UP are High. For counting down, the TCoutput is High when all Q outputs and UP are Low.
Create larger counters by connecting the CEO output of each stage to the CE input of the next stage andconnecting the C, UP, L, and CLR inputs in parallel. CEO is active (High) when TC and CE are High. Themaximum length of the counter is determined by the accumulated CE-to-TC propagation delays versus the clockperiod. The clock period must be greater than n (tCE-TC), where n is the number of stages and the time tCE-TC isthe CE-to-TC propagation delay of each stage. When cascading counters, use the CEO output if the counteruses the CE input or use the TC output if it does not.
For CPLD parts, see “CB2X1”, “CB4X1”, “CB8X1”, “CB16X1” for high-performance cascadable, bidirectionalcounters.
This counter is asynchronously cleared, outputs Low, when power is applied. For CPLD devices, you cansimulate power-on by applying a High-level pulse on the PRLD global net.
CPLD Libraries Guide146 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
Logic TableInputs Outputs
CLR L CE C UP Dz-D0 Qz-Q0 TC CEO
1 X X X X X 0 0 0
0 1 X ↑ X Dn Dn TC CEO
0 0 0 X X X No change No change 0
0 0 1 ↑ 1 X Inc TC CEO
0 0 1 ↑ 0 X Dec TC CEO
z = bit width - 1
TC = (Qz•Q(z-1)•Q(z-2)•...•Q0•UP) + (Qz•Q(z-1)•Q(z-2)•...•Q0•UP)
CEO = TC•CE
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 147
Chapter 3: About Design Elements
CB2REMacro: 2-Bit Cascadable Binary Counter with Clock Enable and Synchronous Reset
Supported ArchitecturesThis design element is supported in the following architectures only:• XC9500• CoolRunner™ XPLA3• CoolRunner-II
IntroductionThis design element is a synchronous, resettable, cascadable binary counter. The synchronous reset (R), whenHigh, overrides all other inputs and forces the Q outputs, terminal count (TC), and clock enable out (CEO) tozero on the Low-to-High clock transition. The Q outputs increment when the clock enable input (CE) is Highduring the Low-to-High clock (C) transition. The counter ignores clock transitions when CE is Low. The TCoutput is High when both Q outputs are High.
Create larger counters by connecting the CEO output of each stage to the CE input of the next stage andconnecting the C and R inputs in parallel. CEO is active (High) when TC and CE are High. The maximum lengthof the counter is determined by the accumulated CE-to-TC propagation delays versus the clock period. Theclock period must be greater than n (tCE-TC), where n is the number of stages and the time tCE-TC is the CE-to-TCpropagation delay of each stage. When cascading counters, use the CEO output if the counter uses the CEinput or use the TC output if it does not.
This counter is asynchronously cleared, outputs Low, when power is applied. For CPLD devices, you cansimulate power-on by applying a High-level pulse on the PRLD global net.
Logic TableInputs Outputs
R CE C Qz-Q0 TC CEO
1 X ↑ 0 0 0
0 0 X No change No change 0
0 1 ↑ Inc TC CEO
z = bit width - 1
TC = Qz•Q(z-1)•Q(z-2)•...•Q0)
CEO = TC•CE
Design Entry MethodThis design element is only for use in schematics.
CPLD Libraries Guide148 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 149
Chapter 3: About Design Elements
CB2RLEMacro: 2-Bit Loadable Cascadable Binary Counter with Clock Enable and Synchronous Reset
Supported ArchitecturesThis design element is supported in the following architectures only:
• XC9500
• CoolRunner™ XPLA3
• CoolRunner-II
IntroductionThis design element is a synchronous, loadable, resettable, cascadable binary counter. The synchronous reset(R), when High, overrides all other inputs and forces the Q outputs, terminal count (TC), and clock enable out(CEO) to zero on the Low-to-High clock (C) transition.
The data on the D inputs is loaded into the counter when the load enable input (L) is High during theLow-to-High clock (C) transition, independent of the state of CE. The Q outputs increment when CE is Highduring the Low-to-High clock transition. The counter ignores clock transitions when CE is Low. The TC outputis High when all Q outputs are High. The CEO output is High when all Q outputs and CE are High to allowdirect cascading of counters.
Create larger counters by connecting the CEO output of each stage to the CE input of the next stage andconnecting the C, L, and R inputs in parallel. CEO is active (High) when TC and CE are High. The maximumlength of the counter is determined by the accumulated CE-to-TC propagation delays versus the clock period.The clock period must be greater than n (tCE-TC), where n is the number of stages and the time tCE-TC is theCE-to-TC propagation delay of each stage. When cascading counters, use the CEO output if the counter uses theCE input or use the TC output if it does not.
This counter is asynchronously cleared, outputs Low, when power is applied. For CPLD devices, you cansimulate power-on by applying a High-level pulse on the PRLD global net.
CPLD Libraries Guide150 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
Logic TableInputs Outputs
R L CE C Dz-D0 Qz-Q0 TC CEO
1 X X ↑ X 0 0 0
0 1 X ↑ Dn Dn TC CEO
0 0 0 X X No change No change 0
0 0 1 ↑ X Inc TC CEO
z = bit width - 1
TC = Qz•Q(z-1)•Q(z-2)•...•Q0
CEO = TC•CE
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 151
Chapter 3: About Design Elements
CB2X1Macro: 2-Bit Loadable Cascadable Bidirectional Binary Counter with Clock Enable andAsynchronous Clear
Supported ArchitecturesThis design element is supported in the following architectures only:• XC9500• CoolRunner™ XPLA3• CoolRunner-II
IntroductionThis design element is a synchronously loadable, asynchronously clearable, bidirectional binary counter. It hasseparate count-enable inputs and synchronous terminal-count outputs for up and down directions to supporthigh-speed cascading.
The asynchronous clear (CLR) is the highest priority input. When CLR is High, all other inputs are ignored; dataoutputs (Q) go to logic level zero, terminal count outputs TCU and TCD go to zero and one, respectively, clockenable outputs CEOU and CEOD go to Low and High, respectively, independent of clock transitions. The dataon the D inputs loads into the counter on the Low-to-High clock (C) transition when the load enable input (L)is High, independent of the CE inputs.
The Q outputs increment when CEU is High, provided CLR and L are Low, during the Low-to-High clocktransition. The Q outputs decrement when CED is High, provided CLR and L are Low. The counter ignoresclock transitions when CEU and CED are Low. Both CEU and CED should not be High during the same clocktransition; the CEOU and CEOD outputs might not function properly for cascading when CEU and CED areboth High.
For counting up, the CEOU output is High when all Q outputs and CEU are High. For counting down, theCEOD output is High when all Q outputs are Low and CED is High. To cascade counters, connect the CEOU andCEOD outputs of each counter directly to the CEU and CED inputs, respectively, of the next stage. Connectthe clock, L, and CLR inputs in parallel.
The maximum clocking frequency of these counter components is unaffected by the number of cascaded stagesfor all counting and loading functions. The TCU terminal count output is High when all Q outputs are High,regardless of CEU. The TCD output is High when all Q outputs are Low, regardless of CED.
When cascading counters, the final terminal count signals can be produced by AND wiring all the TCU outputs(for the up direction) and all the TCD outputs (for the down direction). The TCU, CEOU, and CEOD outputs areproduced by optimizable AND gates within the component. This results in zero propagation from the CEUand CED inputs and from the Q outputs, provided all connections from each such output remain on-chip.Otherwise, a macrocell buffer delay is introduced.
CPLD Libraries Guide152 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
The counter is initialized to zero (TCU Low and TCD High) when power is applied. You can simulate power-onby applying a High-level pulse on the PRLD global net.
Logic TableInputs Outputs
CLR L CEU CED C Dz-D0 Qz-Q0 TCU TCD CEOU CEOD
1 X X X X X 0 0 1 0 CEOD
0 1 X X ↑ Dn Dn TCU TCD CEOU CEOD
0 0 0 0 X X NoChange
NoChange
NoChange
0 0
0 0 1 0 ↑ X Inc TCU TCD CEOU 0
0 0 0 1 ↑ X Dec TCU TCD 0 CEOD
0 0 1 1 ↑ X Inc TCU TCD Invalid Invalid
z = bit width - 1
TCU = Qz•Q(z-1)•Q(z-2)•...•Q0
TCD = Qz•Q(z-1)•Q(z-2)•...•Q0
CEOU = TCU•CEU
CEOD = TCD•CED
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 153
Chapter 3: About Design Elements
CB4CEMacro: 4-Bit Cascadable Binary Counter with Clock Enable and Asynchronous Clear
Supported ArchitecturesThis design element is supported in the following architectures only:• XC9500• CoolRunner™ XPLA3• CoolRunner-II
IntroductionThis design element is an asynchronously clearable, cascadable binary counter. The asynchronous clear (CLR)input, when High, overrides all other inputs and forces the Q outputs, terminal count (TC), and clock enable out(CEO) to logic level zero, independent of clock transitions. The Q outputs increment when the clock enable input(CE) is High during the Low-to-High clock (C) transition. The counter ignores clock transitions when CE is Low.The TC output is High when all Q outputs are High.
Create larger counters by connecting the CEO output of each stage to the CE input of the next stage andconnecting the C and CLR inputs in parallel. CEO is active (High) when TC and CE are High. The maximumlength of the counter is determined by the accumulated CE-to-TC propagation delays versus the clock period.The clock period must be greater than n (tCE-TC), where n is the number of stages and the time tCE-TC is theCE-to-TC propagation delay of each stage. When cascading counters, use the CEO output if the counter uses theCE input or use the TC output if it does not.
This counter is asynchronously cleared, outputs Low, when power is applied. For CPLD devices, you cansimulate power-on by applying a High-level pulse on the PRLD global net.
Logic TableInputs Outputs
CLR CE C Qz-Q0 TC CEO
1 X X 0 0 0
0 0 X No change No change 0
0 1 ↑ Inc TC CEO
z = bit width - 1
TC = Qz•Q(z-1)•Q(z-2)•...•Q0
CEO = TC•CE
CPLD Libraries Guide154 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 155
Chapter 3: About Design Elements
CB4CLEMacro: 4-Bit Loadable Cascadable Binary Counters with Clock Enable and Asynchronous Clear
Supported ArchitecturesThis design element is supported in the following architectures only:
• XC9500
• CoolRunner™ XPLA3
• CoolRunner-II
IntroductionThis element is a synchronously loadable, asynchronously clearable, cascadable binary counter. Theasynchronous clear (CLR) input, when High, overrides all other inputs and forces the Q outputs, terminalcount (TC), and clock enable out (CEO) to logic level zero, independent of clock transitions. The data on theD inputs is loaded into the counter when the load enable input (L) is High during the Low-to-High clocktransition, independent of the state of clock enable (CE). The Q outputs increment when CE is High during theLow-to-High clock transition. The counter ignores clock transitions when CE is Low. The TC output is Highwhen all Q outputs are High.
Create larger counters by connecting the CEO output of each stage to the CE input of the next stage andconnecting the C, L, and CLR inputs in parallel. CEO is active (High) when TC and CE are High. The maximumlength of the counter is determined by the accumulated CE-to-TC propagation delays versus the clock period.The clock period must be greater than n (tCE-TC), where n is the number of stages and the time tCE-TC is theCE-to-TC propagation delay of each stage. When cascading counters, use the CEO output if the counter uses theCE input or use the TC output if it does not.
This counter is asynchronously cleared, outputs Low, when power is applied. For CPLD devices, you cansimulate power-on by applying a High-level pulse on the PRLD global net.
CPLD Libraries Guide156 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
Logic TableInputs Outputs
CLR L CE C Dz-D0 Qz-Q0 TC CEO
1 X X X X 0 0 0
0 1 X ↑ Dn Dn TC CEO
0 0 0 X X No change No change 0
0 0 1 ↑ X Inc TC CEO
z = bit width - 1
TC = Qz•Q(z-1)•Q(z-2)•...•Q0
CEO = TC•CE
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 157
Chapter 3: About Design Elements
CB4CLEDMacro: 4-Bit Loadable Cascadable Bidirectional Binary Counters with Clock Enable andAsynchronous Clear
Supported ArchitecturesThis design element is supported in the following architectures only:
• XC9500
• CoolRunner™ XPLA3
• CoolRunner-II
IntroductionThis design element is a synchronously loadable, asynchronously clearable, cascadable, bidirectional binarycounter. The asynchronous clear (CLR) input, when High, overrides all other inputs and forces the Q outputs,terminal count (TC), and clock enable out (CEO) to logic level zero, independent of clock transitions. The data onthe D inputs is loaded into the counter when the load enable input (L) is High during the Low-to-High clock(C) transition, independent of the state of clock enable (CE). The Q outputs decrement when CE is High andUP is Low during the Low-to- High clock transition. The Q outputs increment when CE and UP are High. Thecounter ignores clock transitions when CE is Low.
For counting up, the TC output is High when all Q outputs and UP are High. For counting down, the TCoutput is High when all Q outputs and UP are Low.
Create larger counters by connecting the CEO output of each stage to the CE input of the next stage andconnecting the C, UP, L, and CLR inputs in parallel. CEO is active (High) when TC and CE are High. Themaximum length of the counter is determined by the accumulated CE-to-TC propagation delays versus the clockperiod. The clock period must be greater than n (tCE-TC), where n is the number of stages and the time tCE-TC isthe CE-to-TC propagation delay of each stage. When cascading counters, use the CEO output if the counteruses the CE input or use the TC output if it does not.
For CPLD parts, see “CB2X1”, “CB4X1”, “CB8X1”, “CB16X1” for high-performance cascadable, bidirectionalcounters.
This counter is asynchronously cleared, outputs Low, when power is applied. For CPLD devices, you cansimulate power-on by applying a High-level pulse on the PRLD global net.
CPLD Libraries Guide158 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
Logic TableInputs Outputs
CLR L CE C UP Dz-D0 Qz-Q0 TC CEO
1 X X X X X 0 0 0
0 1 X ↑ X Dn Dn TC CEO
0 0 0 X X X No change No change 0
0 0 1 ↑ 1 X Inc TC CEO
0 0 1 ↑ 0 X Dec TC CEO
z = bit width - 1
TC = (Qz•Q(z-1)•Q(z-2)•...•Q0•UP) + (Qz•Q(z-1)•Q(z-2)•...•Q0•UP)
CEO = TC•CE
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 159
Chapter 3: About Design Elements
CB4REMacro: 4-Bit Cascadable Binary Counter with Clock Enable and Synchronous Reset
Supported ArchitecturesThis design element is supported in the following architectures only:• XC9500• CoolRunner™ XPLA3• CoolRunner-II
IntroductionThis design element is a synchronous, resettable, cascadable binary counter. The synchronous reset (R), whenHigh, overrides all other inputs and forces the Q outputs, terminal count (TC), and clock enable out (CEO) tozero on the Low-to-High clock transition. The Q outputs increment when the clock enable input (CE) is Highduring the Low-to-High clock (C) transition. The counter ignores clock transitions when CE is Low. The TCoutput is High when both Q outputs are High.
Create larger counters by connecting the CEO output of each stage to the CE input of the next stage andconnecting the C and R inputs in parallel. CEO is active (High) when TC and CE are High. The maximum lengthof the counter is determined by the accumulated CE-to-TC propagation delays versus the clock period. Theclock period must be greater than n (tCE-TC), where n is the number of stages and the time tCE-TC is the CE-to-TCpropagation delay of each stage. When cascading counters, use the CEO output if the counter uses the CEinput or use the TC output if it does not.
This counter is asynchronously cleared, outputs Low, when power is applied. For CPLD devices, you cansimulate power-on by applying a High-level pulse on the PRLD global net.
Logic TableInputs Outputs
R CE C Qz-Q0 TC CEO
1 X ↑ 0 0 0
0 0 X No change No change 0
0 1 ↑ Inc TC CEO
z = bit width - 1
TC = Qz•Q(z-1)•Q(z-2)•...•Q0)
CEO = TC•CE
CPLD Libraries Guide160 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 161
Chapter 3: About Design Elements
CB4RLEMacro: 4-Bit Loadable Cascadable Binary Counter with Clock Enable and Synchronous Reset
Supported ArchitecturesThis design element is supported in the following architectures only:
• XC9500
• CoolRunner™ XPLA3
• CoolRunner-II
IntroductionThis design element is a synchronous, loadable, resettable, cascadable binary counter. The synchronous reset(R), when High, overrides all other inputs and forces the Q outputs, terminal count (TC), and clock enable out(CEO) to zero on the Low-to-High clock (C) transition.
The data on the D inputs is loaded into the counter when the load enable input (L) is High during theLow-to-High clock (C) transition, independent of the state of CE. The Q outputs increment when CE is Highduring the Low-to-High clock transition. The counter ignores clock transitions when CE is Low. The TC outputis High when all Q outputs are High. The CEO output is High when all Q outputs and CE are High to allowdirect cascading of counters.
Create larger counters by connecting the CEO output of each stage to the CE input of the next stage andconnecting the C, L, and R inputs in parallel. CEO is active (High) when TC and CE are High. The maximumlength of the counter is determined by the accumulated CE-to-TC propagation delays versus the clock period.The clock period must be greater than n (tCE-TC), where n is the number of stages and the time tCE-TC is theCE-to-TC propagation delay of each stage. When cascading counters, use the CEO output if the counter uses theCE input or use the TC output if it does not.
This counter is asynchronously cleared, outputs Low, when power is applied. For CPLD devices, you cansimulate power-on by applying a High-level pulse on the PRLD global net.
CPLD Libraries Guide162 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
Logic TableInputs Outputs
R L CE C Dz-D0 Qz-Q0 TC CEO
1 X X ↑ X 0 0 0
0 1 X ↑ Dn Dn TC CEO
0 0 0 X X No change No change 0
0 0 1 ↑ X Inc TC CEO
z = bit width - 1
TC = Qz•Q(z-1)•Q(z-2)•...•Q0
CEO = TC•CE
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 163
Chapter 3: About Design Elements
CB4X1Macro: 4-Bit Loadable Cascadable Bidirectional Binary Counter with Clock Enable andAsynchronous Clear
Supported ArchitecturesThis design element is supported in the following architectures only:• XC9500• CoolRunner™ XPLA3• CoolRunner-II
IntroductionThis design element is a synchronously loadable, asynchronously clearable, bidirectional binary counter. It hasseparate count-enable inputs and synchronous terminal-count outputs for up and down directions to supporthigh-speed cascading.
The asynchronous clear (CLR) is the highest priority input. When CLR is High, all other inputs are ignored; dataoutputs (Q) go to logic level zero, terminal count outputs TCU and TCD go to zero and one, respectively, clockenable outputs CEOU and CEOD go to Low and High, respectively, independent of clock transitions. The dataon the D inputs loads into the counter on the Low-to-High clock (C) transition when the load enable input (L)is High, independent of the CE inputs.
The Q outputs increment when CEU is High, provided CLR and L are Low, during the Low-to-High clocktransition. The Q outputs decrement when CED is High, provided CLR and L are Low. The counter ignoresclock transitions when CEU and CED are Low. Both CEU and CED should not be High during the same clocktransition; the CEOU and CEOD outputs might not function properly for cascading when CEU and CED areboth High.
For counting up, the CEOU output is High when all Q outputs and CEU are High. For counting down, theCEOD output is High when all Q outputs are Low and CED is High. To cascade counters, connect the CEOU andCEOD outputs of each counter directly to the CEU and CED inputs, respectively, of the next stage. Connectthe clock, L, and CLR inputs in parallel.
The maximum clocking frequency of these counter components is unaffected by the number of cascaded stagesfor all counting and loading functions. The TCU terminal count output is High when all Q outputs are High,regardless of CEU. The TCD output is High when all Q outputs are Low, regardless of CED.
When cascading counters, the final terminal count signals can be produced by AND wiring all the TCU outputs(for the up direction) and all the TCD outputs (for the down direction). The TCU, CEOU, and CEOD outputs areproduced by optimizable AND gates within the component. This results in zero propagation from the CEUand CED inputs and from the Q outputs, provided all connections from each such output remain on-chip.Otherwise, a macrocell buffer delay is introduced.
CPLD Libraries Guide164 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
The counter is initialized to zero (TCU Low and TCD High) when power is applied. You can simulate power-onby applying a High-level pulse on the PRLD global net.
Logic TableInputs Outputs
CLR L CEU CED C Dz-D0 Qz-Q0 TCU TCD CEOU CEOD
1 X X X X X 0 0 1 0 CEOD
0 1 X X ↑ Dn Dn TCU TCD CEOU CEOD
0 0 0 0 X X NoChange
NoChange
NoChange
0 0
0 0 1 0 ↑ X Inc TCU TCD CEOU 0
0 0 0 1 ↑ X Dec TCU TCD 0 CEOD
0 0 1 1 ↑ X Inc TCU TCD Invalid Invalid
z = bit width - 1
TCU = Qz•Q(z-1)•Q(z-2)•...•Q0
TCD = Qz•Q(z-1)•Q(z-2)•...•Q0
CEOU = TCU•CEU
CEOD = TCD•CED
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 165
Chapter 3: About Design Elements
CB4X2Macro: 4-Bit Loadable Cascadable Bidirectional Binary Counter with Clock Enable and SynchronousReset
Supported ArchitecturesThis design element is supported in the following architectures only:• XC9500• CoolRunner™ XPLA3• CoolRunner-II
IntroductionThis design element is a synchronous, loadable, resettable, bidirectional binary counter. It has separatecount-enable inputs and synchronous terminal-count outputs for up and down directions to support high-speedcascading in CPLD architectures.
The synchronous reset (R) is the highest priority input. When R is High, all other inputs are ignored; the dataoutputs (Q) go to logic level zero, terminal count outputs TCU and TCD go to zero and one, respectively,and clock enable outputs CEOU and CEOD go to Low and High, respectively, on the Low-to-High clock (C)transition. The data on the D inputs loads into the counter on the Low-to-High clock (C) transition when the loadenable input (L) is High, independent of the CE inputs.
All Q outputs increment when CEU is High, provided R and L are Low during the Low-to-High clock transition.All Q outputs decrement when CED is High, provided R and L are Low. The counter ignores clock transitionswhen CEU and CED are Low. Both CEU and CED should not be High during the same clock transition; theCEOU and CEOD outputs might not function properly for cascading when CEU and CED are both High.
For counting up, the CEOU output is High when all Q outputs and CEU are High. For counting down, theCEOD output is High when all Q outputs are Low and CED is High. To cascade counters, the CEOU and CEODoutputs of each counter are, respectively, connected directly to the CEU and CED inputs of the next stage. The C,L, and R inputs are connected in parallel.
The maximum clocking frequency of these counter components is unaffected by the number of cascaded stagesfor all counting and loading functions. The TCU terminal count output is High when all Q outputs are High,regardless of CEU. The TCD output is High when all Q outputs are Low, regardless of CED.
When cascading counters, the final terminal count signals can be produced by AND wiring all the TCU outputs(for the up direction) and all the TCD outputs (for the down direction). The TCU, CEOU, and CEOD outputs areproduced by optimizable AND gates within the component. This results in zero propagation from the CEUand CED inputs and from the Q outputs, provided all connections from each such output remain on-chip.Otherwise, a macrocell buffer delay is introduced.
CPLD Libraries Guide166 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
The counter is initialized to zero (TCU Low and TCD High) when power is applied. You can simulate power-onby applying a High-level pulse on the PRLD global net.
Logic TableInputs Outputs
R L CEU CED C Dz-D0 Qz-Q0 TCU TCD CEOU CEOD
1 X X X ↑ X 0 0 1 0 CEOD
0 1 X X ↑ Dn Dn TCU TCD CEOU CEOD
0 0 0 0 X X No Chg No Chg No Chg 0 0
0 0 1 0 ↑ X Inc TCU TCD CEOU 0
0 0 0 1 ↑ X Dec TCU TCD 0 CEOD
0 0 1 1 ↑ X Inc TCU TCD Invalid Invalid
z = bit width - 1
TCU = Qz•Q(z-1)•Q(z-2)•...•Q0
TCD = Qz•Q(z-1)•Q(z-2)•...•Q0
CEOU = TCU•CEU
CEOD = TCD•CED
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 167
Chapter 3: About Design Elements
CB8CEMacro: 8-Bit Cascadable Binary Counter with Clock Enable and Asynchronous Clear
Supported ArchitecturesThis design element is supported in the following architectures only:• XC9500• CoolRunner™ XPLA3• CoolRunner-II
IntroductionThis design element is an asynchronously clearable, cascadable binary counter. The asynchronous clear (CLR)input, when High, overrides all other inputs and forces the Q outputs, terminal count (TC), and clock enable out(CEO) to logic level zero, independent of clock transitions. The Q outputs increment when the clock enable input(CE) is High during the Low-to-High clock (C) transition. The counter ignores clock transitions when CE is Low.The TC output is High when all Q outputs are High.
Create larger counters by connecting the CEO output of each stage to the CE input of the next stage andconnecting the C and CLR inputs in parallel. CEO is active (High) when TC and CE are High. The maximumlength of the counter is determined by the accumulated CE-to-TC propagation delays versus the clock period.The clock period must be greater than n (tCE-TC), where n is the number of stages and the time tCE-TC is theCE-to-TC propagation delay of each stage. When cascading counters, use the CEO output if the counter uses theCE input or use the TC output if it does not.
This counter is asynchronously cleared, outputs Low, when power is applied. For CPLD devices, you cansimulate power-on by applying a High-level pulse on the PRLD global net.
Logic TableInputs Outputs
CLR CE C Qz-Q0 TC CEO
1 X X 0 0 0
0 0 X No change No change 0
0 1 ↑ Inc TC CEO
z = bit width - 1
TC = Qz•Q(z-1)•Q(z-2)•...•Q0
CEO = TC•CE
Design Entry MethodThis design element is only for use in schematics.
CPLD Libraries Guide168 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 169
Chapter 3: About Design Elements
CB8CLEMacro: 8-Bit Loadable Cascadable Binary Counters with Clock Enable and Asynchronous Clear
Supported ArchitecturesThis design element is supported in the following architectures only:
• XC9500
• CoolRunner™ XPLA3
• CoolRunner-II
IntroductionThis element is a synchronously loadable, asynchronously clearable, cascadable binary counter. Theasynchronous clear (CLR) input, when High, overrides all other inputs and forces the Q outputs, terminalcount (TC), and clock enable out (CEO) to logic level zero, independent of clock transitions. The data on theD inputs is loaded into the counter when the load enable input (L) is High during the Low-to-High clocktransition, independent of the state of clock enable (CE). The Q outputs increment when CE is High during theLow-to-High clock transition. The counter ignores clock transitions when CE is Low. The TC output is Highwhen all Q outputs are High.
Create larger counters by connecting the CEO output of each stage to the CE input of the next stage andconnecting the C, L, and CLR inputs in parallel. CEO is active (High) when TC and CE are High. The maximumlength of the counter is determined by the accumulated CE-to-TC propagation delays versus the clock period.The clock period must be greater than n (tCE-TC), where n is the number of stages and the time tCE-TC is theCE-to-TC propagation delay of each stage. When cascading counters, use the CEO output if the counter uses theCE input or use the TC output if it does not.
This counter is asynchronously cleared, outputs Low, when power is applied. For CPLD devices, you cansimulate power-on by applying a High-level pulse on the PRLD global net.
CPLD Libraries Guide170 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
Logic TableInputs Outputs
CLR L CE C Dz-D0 Qz-Q0 TC CEO
1 X X X X 0 0 0
0 1 X ↑ Dn Dn TC CEO
0 0 0 X X No change No change 0
0 0 1 ↑ X Inc TC CEO
z = bit width - 1
TC = Qz•Q(z-1)•Q(z-2)•...•Q0
CEO = TC•CE
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 171
Chapter 3: About Design Elements
CB8CLEDMacro: 8-Bit Loadable Cascadable Bidirectional Binary Counters with Clock Enable andAsynchronous Clear
Supported ArchitecturesThis design element is supported in the following architectures only:
• XC9500
• CoolRunner™ XPLA3
• CoolRunner-II
IntroductionThis design element is a synchronously loadable, asynchronously clearable, cascadable, bidirectional binarycounter. The asynchronous clear (CLR) input, when High, overrides all other inputs and forces the Q outputs,terminal count (TC), and clock enable out (CEO) to logic level zero, independent of clock transitions. The data onthe D inputs is loaded into the counter when the load enable input (L) is High during the Low-to-High clock(C) transition, independent of the state of clock enable (CE). The Q outputs decrement when CE is High andUP is Low during the Low-to- High clock transition. The Q outputs increment when CE and UP are High. Thecounter ignores clock transitions when CE is Low.
For counting up, the TC output is High when all Q outputs and UP are High. For counting down, the TCoutput is High when all Q outputs and UP are Low.
Create larger counters by connecting the CEO output of each stage to the CE input of the next stage andconnecting the C, UP, L, and CLR inputs in parallel. CEO is active (High) when TC and CE are High. Themaximum length of the counter is determined by the accumulated CE-to-TC propagation delays versus the clockperiod. The clock period must be greater than n (tCE-TC), where n is the number of stages and the time tCE-TC isthe CE-to-TC propagation delay of each stage. When cascading counters, use the CEO output if the counteruses the CE input or use the TC output if it does not.
For CPLD parts, see “CB2X1”, “CB4X1”, “CB8X1”, “CB16X1” for high-performance cascadable, bidirectionalcounters.
This counter is asynchronously cleared, outputs Low, when power is applied. For CPLD devices, you cansimulate power-on by applying a High-level pulse on the PRLD global net.
CPLD Libraries Guide172 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
Logic TableInputs Outputs
CLR L CE C UP Dz-D0 Qz-Q0 TC CEO
1 X X X X X 0 0 0
0 1 X ↑ X Dn Dn TC CEO
0 0 0 X X X No change No change 0
0 0 1 ↑ 1 X Inc TC CEO
0 0 1 ↑ 0 X Dec TC CEO
z = bit width - 1
TC = (Qz•Q(z-1)•Q(z-2)•...•Q0•UP) + (Qz•Q(z-1)•Q(z-2)•...•Q0•UP)
CEO = TC•CE
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 173
Chapter 3: About Design Elements
CB8REMacro: 8-Bit Cascadable Binary Counter with Clock Enable and Synchronous Reset
Supported ArchitecturesThis design element is supported in the following architectures only:• XC9500• CoolRunner™ XPLA3• CoolRunner-II
IntroductionThis design element is a synchronous, resettable, cascadable binary counter. The synchronous reset (R), whenHigh, overrides all other inputs and forces the Q outputs, terminal count (TC), and clock enable out (CEO) tozero on the Low-to-High clock transition. The Q outputs increment when the clock enable input (CE) is Highduring the Low-to-High clock (C) transition. The counter ignores clock transitions when CE is Low. The TCoutput is High when both Q outputs are High.
Create larger counters by connecting the CEO output of each stage to the CE input of the next stage andconnecting the C and R inputs in parallel. CEO is active (High) when TC and CE are High. The maximum lengthof the counter is determined by the accumulated CE-to-TC propagation delays versus the clock period. Theclock period must be greater than n (tCE-TC), where n is the number of stages and the time tCE-TC is the CE-to-TCpropagation delay of each stage. When cascading counters, use the CEO output if the counter uses the CEinput or use the TC output if it does not.
This counter is asynchronously cleared, outputs Low, when power is applied. For CPLD devices, you cansimulate power-on by applying a High-level pulse on the PRLD global net.
Logic TableInputs Outputs
R CE C Qz-Q0 TC CEO
1 X ↑ 0 0 0
0 0 X No change No change 0
0 1 ↑ Inc TC CEO
z = bit width - 1
TC = Qz•Q(z-1)•Q(z-2)•...•Q0)
CEO = TC•CE
Design Entry MethodThis design element is only for use in schematics.
CPLD Libraries Guide174 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 175
Chapter 3: About Design Elements
CB8RLEMacro: 8-Bit Loadable Cascadable Binary Counter with Clock Enable and Synchronous Reset
Supported ArchitecturesThis design element is supported in the following architectures only:
• XC9500
• CoolRunner™ XPLA3
• CoolRunner-II
IntroductionThis design element is a synchronous, loadable, resettable, cascadable binary counter. The synchronous reset(R), when High, overrides all other inputs and forces the Q outputs, terminal count (TC), and clock enable out(CEO) to zero on the Low-to-High clock (C) transition.
The data on the D inputs is loaded into the counter when the load enable input (L) is High during theLow-to-High clock (C) transition, independent of the state of CE. The Q outputs increment when CE is Highduring the Low-to-High clock transition. The counter ignores clock transitions when CE is Low. The TC outputis High when all Q outputs are High. The CEO output is High when all Q outputs and CE are High to allowdirect cascading of counters.
Create larger counters by connecting the CEO output of each stage to the CE input of the next stage andconnecting the C, L, and R inputs in parallel. CEO is active (High) when TC and CE are High. The maximumlength of the counter is determined by the accumulated CE-to-TC propagation delays versus the clock period.The clock period must be greater than n (tCE-TC), where n is the number of stages and the time tCE-TC is theCE-to-TC propagation delay of each stage. When cascading counters, use the CEO output if the counter uses theCE input or use the TC output if it does not.
This counter is asynchronously cleared, outputs Low, when power is applied. For CPLD devices, you cansimulate power-on by applying a High-level pulse on the PRLD global net.
CPLD Libraries Guide176 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
Logic TableInputs Outputs
R L CE C Dz-D0 Qz-Q0 TC CEO
1 X X ↑ X 0 0 0
0 1 X ↑ Dn Dn TC CEO
0 0 0 X X No change No change 0
0 0 1 ↑ X Inc TC CEO
z = bit width - 1
TC = Qz•Q(z-1)•Q(z-2)•...•Q0
CEO = TC•CE
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 177
Chapter 3: About Design Elements
CB8X1Macro: 8-Bit Loadable Cascadable Bidirectional Binary Counter with Clock Enable andAsynchronous Clear
Supported ArchitecturesThis design element is supported in the following architectures only:• XC9500• CoolRunner™ XPLA3• CoolRunner-II
IntroductionThis design element is a synchronously loadable, asynchronously clearable, bidirectional binary counter. It hasseparate count-enable inputs and synchronous terminal-count outputs for up and down directions to supporthigh-speed cascading.
The asynchronous clear (CLR) is the highest priority input. When CLR is High, all other inputs are ignored; dataoutputs (Q) go to logic level zero, terminal count outputs TCU and TCD go to zero and one, respectively, clockenable outputs CEOU and CEOD go to Low and High, respectively, independent of clock transitions. The dataon the D inputs loads into the counter on the Low-to-High clock (C) transition when the load enable input (L)is High, independent of the CE inputs.
The Q outputs increment when CEU is High, provided CLR and L are Low, during the Low-to-High clocktransition. The Q outputs decrement when CED is High, provided CLR and L are Low. The counter ignoresclock transitions when CEU and CED are Low. Both CEU and CED should not be High during the same clocktransition; the CEOU and CEOD outputs might not function properly for cascading when CEU and CED areboth High.
For counting up, the CEOU output is High when all Q outputs and CEU are High. For counting down, theCEOD output is High when all Q outputs are Low and CED is High. To cascade counters, connect the CEOU andCEOD outputs of each counter directly to the CEU and CED inputs, respectively, of the next stage. Connectthe clock, L, and CLR inputs in parallel.
The maximum clocking frequency of these counter components is unaffected by the number of cascaded stagesfor all counting and loading functions. The TCU terminal count output is High when all Q outputs are High,regardless of CEU. The TCD output is High when all Q outputs are Low, regardless of CED.
When cascading counters, the final terminal count signals can be produced by AND wiring all the TCU outputs(for the up direction) and all the TCD outputs (for the down direction). The TCU, CEOU, and CEOD outputs areproduced by optimizable AND gates within the component. This results in zero propagation from the CEUand CED inputs and from the Q outputs, provided all connections from each such output remain on-chip.Otherwise, a macrocell buffer delay is introduced.
The counter is initialized to zero (TCU Low and TCD High) when power is applied. You can simulate power-onby applying a High-level pulse on the PRLD global net.
CPLD Libraries Guide178 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
Logic TableInputs Outputs
CLR L CEU CED C Dz-D0 Qz-Q0 TCU TCD CEOU CEOD
1 X X X X X 0 0 1 0 CEOD
0 1 X X ↑ Dn Dn TCU TCD CEOU CEOD
0 0 0 0 X X NoChange
NoChange
NoChange
0 0
0 0 1 0 ↑ X Inc TCU TCD CEOU 0
0 0 0 1 ↑ X Dec TCU TCD 0 CEOD
0 0 1 1 ↑ X Inc TCU TCD Invalid Invalid
z = bit width - 1
TCU = Qz•Q(z-1)•Q(z-2)•...•Q0
TCD = Qz•Q(z-1)•Q(z-2)•...•Q0
CEOU = TCU•CEU
CEOD = TCD•CED
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 179
Chapter 3: About Design Elements
CB8X2Macro: 8-Bit Loadable Cascadable Bidirectional Binary Counter with Clock Enable and SynchronousReset
Supported ArchitecturesThis design element is supported in the following architectures only:• XC9500• CoolRunner™ XPLA3• CoolRunner-II
IntroductionThis design element is a synchronous, loadable, resettable, bidirectional binary counter. It has separatecount-enable inputs and synchronous terminal-count outputs for up and down directions to support high-speedcascading in CPLD architectures.
The synchronous reset (R) is the highest priority input. When R is High, all other inputs are ignored; the dataoutputs (Q) go to logic level zero, terminal count outputs TCU and TCD go to zero and one, respectively,and clock enable outputs CEOU and CEOD go to Low and High, respectively, on the Low-to-High clock (C)transition. The data on the D inputs loads into the counter on the Low-to-High clock (C) transition when the loadenable input (L) is High, independent of the CE inputs.
All Q outputs increment when CEU is High, provided R and L are Low during the Low-to-High clock transition.All Q outputs decrement when CED is High, provided R and L are Low. The counter ignores clock transitionswhen CEU and CED are Low. Both CEU and CED should not be High during the same clock transition; theCEOU and CEOD outputs might not function properly for cascading when CEU and CED are both High.
For counting up, the CEOU output is High when all Q outputs and CEU are High. For counting down, theCEOD output is High when all Q outputs are Low and CED is High. To cascade counters, the CEOU and CEODoutputs of each counter are, respectively, connected directly to the CEU and CED inputs of the next stage. The C,L, and R inputs are connected in parallel.
The maximum clocking frequency of these counter components is unaffected by the number of cascaded stagesfor all counting and loading functions. The TCU terminal count output is High when all Q outputs are High,regardless of CEU. The TCD output is High when all Q outputs are Low, regardless of CED.
When cascading counters, the final terminal count signals can be produced by AND wiring all the TCU outputs(for the up direction) and all the TCD outputs (for the down direction). The TCU, CEOU, and CEOD outputs areproduced by optimizable AND gates within the component. This results in zero propagation from the CEUand CED inputs and from the Q outputs, provided all connections from each such output remain on-chip.Otherwise, a macrocell buffer delay is introduced.
The counter is initialized to zero (TCU Low and TCD High) when power is applied. You can simulate power-onby applying a High-level pulse on the PRLD global net.
CPLD Libraries Guide180 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
Logic TableInputs Outputs
R L CEU CED C Dz-D0 Qz-Q0 TCU TCD CEOU CEOD
1 X X X ↑ X 0 0 1 0 CEOD
0 1 X X ↑ Dn Dn TCU TCD CEOU CEOD
0 0 0 0 X X No Chg No Chg No Chg 0 0
0 0 1 0 ↑ X Inc TCU TCD CEOU 0
0 0 0 1 ↑ X Dec TCU TCD 0 CEOD
0 0 1 1 ↑ X Inc TCU TCD Invalid Invalid
z = bit width - 1
TCU = Qz•Q(z-1)•Q(z-2)•...•Q0
TCD = Qz•Q(z-1)•Q(z-2)•...•Q0
CEOU = TCU•CEU
CEOD = TCD•CED
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 181
Chapter 3: About Design Elements
CBD16CEMacro: 16-Bit Cascadable Dual Edge Triggered Binary Counter with Clock Enable and AsynchronousClear
Supported ArchitecturesThis design element is supported in the following architectures only:CoolRunner™-II
IntroductionThis element is an asynchronously clearable, cascadable dual edge triggered binary counter. The asynchronousclear (CLR) input, when High, overrides all other inputs and forces the Q outputs, terminal count (TC), and clockenable out (CEO) to logic level zero, independent of clock transitions. The Q outputs increment when the clockenable input (CE) is High during the Low-to-High and High-to-Low clock (C) transition. The counter ignoresclock transitions when CE is Low. The TC output is High when all Q outputs are High.
Create larger counters by connecting the CEO output of each stage to the CE input of the next stage andconnecting the C and CLR inputs in parallel. CEO is active (High) when TC and CE are High. The maximumlength of the counter is determined by the accumulated CE-to-TC propagation delays versus the clock period.The clock period must be greater than n (tCE-TC), where n is the number of stages and the time tCE-TC is theCE-to-TC propagation delay of each stage. When cascading counters, use the CEO output if the counter uses theCE input or use the TC output if it does not.
This counter is asynchronously cleared, outputs Low, when power is applied. For CPLD devices, you cansimulate power-on by applying a High-level pulse on the PRLD global net.
Logic TableInputs Outputs
CLR CE C Qz : Q0 TC CEO
1 X X 0 0 0
0 0 X No change No change 0
0 1 ↑ Inc TC CEO
0 1 ↓ Inc TC CEO
z = bit width - 1
TC = Qz•Q(z-1)•Q(z-2)•...•Q0
CEO = TC•CE
Design Entry MethodThis design element is only for use in schematics.
CPLD Libraries Guide182 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 183
Chapter 3: About Design Elements
CBD16CLEMacro: 16-Bit Loadable Cascadable Dual Edge Triggered Binary Counter with Clock Enable andAsynchronous Clear
Supported ArchitecturesThis design element is supported in the following architectures only:
CoolRunner™-II
IntroductionThis is a synchronously loadable, asynchronously clearable, cascadable dual edge triggered binary counters.The asynchronous clear (CLR) input, when High, overrides all other inputs and forces the Q outputs, terminalcount (TC), and clock enable out (CEO) to logic level zero, independent of clock transitions. The data on theD inputs is loaded into the counter when the load enable input (L) is High during the Low-to-High clocktransition, independent of the state of clock enable (CE). The Q outputs increment when CE is High during theLow-to-High and High-to-Low clock transition. The counter ignores clock transitions when CE is Low. The TCoutput is High when all Q outputs are High.
Create larger counters by connecting the CEO output of each stage to the CE input of the next stage andconnecting the C, L, and CLR inputs in parallel. CEO is active (High) when TC and CE are High. The maximumlength of the counter is determined by the accumulated CE-to-TC propagation delays versus the clock period.The clock period must be greater than n (tCE-TC), where n is the number of stages and the time tCE-TC is theCE-to-TC propagation delay of each stage. When cascading counters, use the CEO output if the counter uses theCE input or use the TC output if it does not.
This counter is asynchronously cleared, outputs Low, when power is applied. For CPLD devices, you cansimulate power-on by applying a High-level pulse on the PRLD global net.
Logic TableInputs Outputs
CLR L CE C Dz : D0 Qz : Q0 TC CEO
1 X X X X 0 0 0
0 1 X ↑ Dn Dn TC CEO
0 1 X ↓ Dn Dn TC CEO
0 0 0 X X No change No change 0
0 0 1 ↑ X Inc TC CEO
0 0 1 ↓ X Inc TC CEO
CPLD Libraries Guide184 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
Inputs Outputs
CLR L CE C Dz : D0 Qz : Q0 TC CEO
z = bit width - 1
TC = Qz•Q(z-1)•Q(z-2)•...•Q0
CEO = TC•CE
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 185
Chapter 3: About Design Elements
CBD16CLEDMacro: 16-Bit Loadable Cascadable Bidirectional Dual Edge Triggered Binary Counter with ClockEnable and Asynchronous Clear
Supported ArchitecturesThis design element is supported in the following architectures only:
CoolRunner™-II
IntroductionThis design element is a synchronously loadable, asynchronously clearable, cascadable, bidirectional dual edgetriggered binary counter. The asynchronous clear (CLR) input, when High, overrides all other inputs andforces the Q outputs, terminal count (TC), and clock enable out (CEO) to logic level zero, independent of clocktransitions. The data on the D inputs is loaded into the counter when the load enable input (L) is High during theLow-to-High clock (C) transition, independent of the state of clock enable (CE). The Q outputs decrement whenCE is High and UP is Low during the Low-to-High and High-to-Low clock transition. The Q outputs incrementwhen CE and UP are High. The counter ignores clock transitions when CE is Low.
For counting up, the TC output is High when all Q outputs and UP are High. For counting down, the TCoutput is High when all Q outputs and UP are Low.
Create larger counters by connecting the CEO output of each stage to the CE input of the next stage andconnecting the C, UP, L, and CLR inputs in parallel. CEO is active (High) when TC and CE are High. Themaximum length of the counter is determined by the accumulated CE-to-TC propagation delays versus the clockperiod. The clock period must be greater than n (tCE-TC), where n is the number of stages and the time tCE-TC isthe CE-to-TC propagation delay of each stage. When cascading counters, use the CEO output if the counteruses the CE input or use the TC output if it does not.
See “CB2X1,” “CB4X1,” “CB8X1,” “CB16X1” for high-performance cascadable, bidirectional counters.
This counter is asynchronously cleared, outputs Low, when power is applied. For CPLD devices, you cansimulate power-on by applying a High-level pulse on the PRLD global net.
CPLD Libraries Guide186 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
Logic TableInputs Outputs
CLR L CE C UP Dz : D0 Qz : Q0 TC CEO
1 X X X X X 0 0 0
0 1 X ↑ X Dn Dn TC CEO
0 1 X ↓ X Dn Dn TC CEO
0 0 0 X X X No change No change 0
0 0 1 ↑ 1 X Inc TC CEO
0 0 1 ↓ 1 X Inc TC CEO
0 0 1 ↑ 0 X Dec TC CEO
0 0 1 ↓ 0 X Dec TC CEO
z = bit width - 1
TC = (Qz•Q(z-1)•Q(z-2)•...•Q0•UP) + (Qz•Q(z-1)•Q(z-2)•...•Q0•UP)
CEO = TC•CE
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 187
Chapter 3: About Design Elements
CBD16REMacro: 16-Bit Cascadable Dual Edge Triggered Binary Counter with Clock Enable and SynchronousReset
Supported ArchitecturesThis design element is supported in the following architectures only:CoolRunner™-II
IntroductionThis design element is a synchronous, resettable, cascadable dual edge triggered binary counter. The synchronousreset (R), when High, overrides all other inputs and forces the Q outputs, terminal count (TC), and clock enableout (CEO) to logic level zero during the Low-to-High or High-to-Low clock transition. The Q outputs incrementwhen the clock enable input (CE) is High during the Low-to-High and High-to-Low clock (C) transition. Thecounter ignores clock transitions when CE is Low. The TC output is High when both Q outputs are High.
Create larger counters by connecting the CEO output of each stage to the CE input of the next stage andconnecting the C and R inputs in parallel. CEO is active (High) when TC and CE are High. The maximum lengthof the counter is determined by the accumulated CE-to-TC propagation delays versus the clock period. Theclock period must be greater than n (tCE-TC), where n is the number of stages and the time tCE-TC is the CE-to-TCpropagation delay of each stage. When cascading counters, use the CEO output if the counter uses the CEinput or use the TC output if it does not.
This counter is asynchronously cleared, outputs Low, when power is applied. For CPLD devices, you cansimulate power-on by applying a High-level pulse on the PRLD global net.
Logic TableInputs Outputs
R CE C Qz-Q0 TC CEO
1 X ↑ 0 0 0
1 X ↓ 0 0 0
0 0 X No change No change 0
0 1 ↑ Inc TC CEO
0 1 ↓ Inc TC CEO
z = bit width - 1
TC = Qz•Q(z-1)•Q(z-2)•...•Q0)
CEO = TC•CE
Design Entry MethodThis design element is only for use in schematics.
CPLD Libraries Guide188 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 189
Chapter 3: About Design Elements
CBD16RLEMacro: 16-Bit Loadable Cascadable Dual Edge Triggered Binary Counter with Clock Enable andSynchronous Reset
Supported ArchitecturesThis design element is supported in the following architectures only:
CoolRunner™-II
IntroductionThis design element is a synchronous, loadable, resettable, cascadable dual edge triggered binary counter. Thesynchronous reset (R), when High, overrides all other inputs and forces the Q outputs, terminal count (TC), andclock enable out (CEO) outputs to Low on the Low-to-High or High-to-Low clock (C) transition.
The data on the D inputs is loaded into the counter when the load enable input (L) is High during theLow-to-High and High-to-Low clock (C) transition, independent of the state of CE. The Q outputs incrementwhen CE is High during the Low-to-High and High-to-Low clock transition. The counter ignores clocktransitions when CE is Low. The TC output is High when all Q outputs are High. The CEO output is High whenall Q outputs and CE are High to allow direct cascading of counters.
Create larger counters by connecting the CEO output of each stage to the CE input of the next stage andconnecting the C, L, and R inputs in parallel. CEO is active (High) when TC and CE are High. The maximumlength of the counter is determined by the accumulated CE-to-TC propagation delays versus the clock period.The clock period must be greater than n (tCE-TC), where n is the number of stages and the time tCE-TC is theCE-to-TC propagation delay of each stage. When cascading counters, use the CEO output if the counter uses theCE input or use the TC output if it does not.
This counter is asynchronously cleared, outputs Low, when power is applied. For CPLD devices, you cansimulate power-on by applying a High-level pulse on the PRLD global net.
Logic TableInputs Outputs
R L CE C Dz : D0 Qz : Q0 TC CEO
1 X X ↑ X 0 0 0
1 X X ↓ X 0 0 0
0 1 X ↑ Dn Dn TC CEO
0 1 X ↓ Dn Dn TC CEO
0 0 0 X X No change No change 0
CPLD Libraries Guide190 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
Inputs Outputs
R L CE C Dz : D0 Qz : Q0 TC CEO
0 0 1 ↑ X Inc TC CEO
0 0 1 ↓ X Inc TC CEO
z = bit width - 1
TC = Qz•Q(z-1)•Q(z-2)•...•Q0
CEO = TC•CE
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 191
Chapter 3: About Design Elements
CBD16X1Macro: 16-Bit Loadable Cascadable Bidirectional Dual Edge Triggered Binary Counter with ClockEnable and Asynchronous Clear
Supported ArchitecturesThis design element is supported in the following architectures only:
CoolRunner™-II
IntroductionThis design element is a synchronously loadable, asynchronously clearable, bidirectional dual edge triggeredbinary counters. It has separate count-enable inputs and synchronous terminal-count outputs for up and downdirections to support high speed cascading.
The asynchronous clear (CLR) is the highest priority input. When CLR is High, all other inputs are ignored; dataoutputs (Q) go to logic level zero, terminal count outputs TCU and TCD go to zero and one, respectively, clockenable outputs CEOU and CEOD go to Low and High, respectively, independent of clock transitions. The dataon the D inputs loads into the counter on the Low-to-High and High-to-Low clock (C) transition when the loadenable input (L) is High, independent of the CE inputs.
The Q outputs increment when CEU is High, provided CLR and L are Low, during the Low-to-High andHigh-to-Low clock transition. The Q outputs decrement when CED is High, provided CLR and L are Low.The counter ignores clock transitions when CEU and CED are Low. Both CEU and CED should not be Highduring the same clock transition; the CEOU and CEOD outputs might not function properly for cascading whenCEU and CED are both High.
For counting up, the CEOU output is High when all Q outputs and CEU are High. For counting down, theCEOD output is High when all Q outputs are Low and CED is High. To cascade counters, the CEOU and CEODoutputs of each counter are connected directly to the CEU and CED inputs, respectively, of the next stage. Theclock, L, and CLR inputs are connected in parallel.
The maximum clocking frequency of these counters is unaffected by the number of cascaded stages for allcounting and loading functions. The TCU terminal count output is High when all Q outputs are High, regardlessof CEU. The TCD output is High when all Q outputs are Low, regardless of CED.
When cascading counters, the final terminal count signals can be produced by AND wiring all the TCU outputs(for the up direction) and all the TCD outputs (for the down direction). The TCU, CEOU, and CEOD outputs areproduced by optimizable AND gates within the component. This results in zero propagation from the CEUand CED inputs and from the Q outputs, provided all connections from each such output remain on-chip.Otherwise, a macrocell buffer delay is introduced.
This counter is asynchronously cleared, outputs Low, when power is applied. For CPLD devices, you cansimulate power-on by applying a High-level pulse on the PRLD global net.
CPLD Libraries Guide192 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
Logic TableInputs Outputs
CLR L CEU CED C Dz–D0 Qz–Q0 TCU TCD CEOU CEOD
1 X X X X X 0 0 1 0 CEOD
0 1 X X ↑ Dn Dn TCU TCD CEOU CEOD
0 1 X X ↓ Dn Dn TCU TCD CEOU CEOD
0 0 0 0 X X NoChange
NoChange
NoChange
0 0
0 0 1 0 ↑ X Inc TCU TCD CEOU 0
0 0 1 0 ↓ X Inc TCU TCD CEOU 0
0 0 0 1 ↑ X Dec TCU TCD 0 CEOD
0 0 0 1 ↓ X Dec TCU TCD 0 CEOD
0 0 1 1 ↑ X Inc TCU TCD Invalid Invalid
0 0 1 1 ↓ X Inc TCU TCD Invalid Invalid
z = bit width - 1
TCU = Qz•Q(z-1)•Q(z-2)•...•Q0
TCD = Qz•Q(z-1)•Q(z-2)•...•Q0
CEOU = TCU•CEU
CEOD = TCD•CED
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 193
Chapter 3: About Design Elements
CBD16X2Macro: 16-Bit Loadable Cascadable Bidirectional Dual Edge Triggered Binary Counter with ClockEnable and Synchronous Reset
Supported ArchitecturesThis design element is supported in the following architectures only:
CoolRunner™-II
IntroductionThis design element is a synchronous, loadable, resettable, bidirectional dual edge triggered binary counter. Ithas separate count-enable inputs and synchronous terminal-count outputs for up and down directions tosupport high-speed cascading.
The synchronous reset (R) is the highest priority input. When R is High, all other inputs are ignored; the dataoutputs (Q) go to logic level zero, terminal count outputs TCU and TCD go to zero and one, respectively, andclock enable outputs CEOU and CEOD go to Low and High, respectively, on the Low-to-High and High-to-Lowclock (C) transition. The data on the D inputs loads into the counter on the Low-to-High and High-to-Low clock(C) transition when the load enable input (L) is High, independent of the CE inputs.
All Q outputs increment when CEU is High, provided R and L are Low during the Low-to-High andHigh-to-Low clock transition. All Q outputs decrement when CED is High, provided R and L are Low. Thecounter ignores clock transitions when CEU and CED are Low. Both CEU and CED should not be High duringthe same clock transition; the CEOU and CEOD outputs might not function properly for cascading when CEUand CED are both High.
For counting up, the CEOU output is High when all Q outputs and CEU are High. For counting down, theCEOD output is High when all Q outputs are Low and CED is High. To cascade counters, the CEOU and CEODoutputs of each counter are, respectively, connected directly to the CEU and CED inputs of the next stage. The C,L, and R inputs are connected in parallel.
The maximum clocking frequency of these counter components is unaffected by the number of cascaded stagesfor all counting and loading functions. The TCU terminal count output is High when all Q outputs are High,regardless of CEU. The TCD output is High when all Q outputs are Low, regardless of CED.
When cascading counters, the final terminal count signals can be produced by AND wiring all the TCU outputs(for the up direction) and all the TCD outputs (for the down direction). The TCU, CEOU, and CEOD outputs areproduced by optimizable AND gates within the component. This results in zero propagation from the CEUand CED inputs and from the Q outputs, provided all connections from each such output remain on-chip.Otherwise, a macrocell buffer delay is introduced.
This counter is asynchronously cleared, outputs Low, when power is applied. For CPLD devices, you cansimulate power-on by applying a High-level pulse on the PRLD global net.
CPLD Libraries Guide194 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
Logic TableInputs Outputs
R L CEU CED C Dz : D0 Qz : Q0 TCU TCD CEOU CEOD
1 X X X ↑ X 0 0 1 0 CEOD
1 X X X ↓ X 0 0 1 0 CEOD
0 1 X X ↑ Dn Dn TCU TCD CEOU CEOD
0 1 X X ↓ Dn Dn TCU TCD CEOU CEOD
0 0 0 0 X X NoChange NoChange
NoChange
0 0
0 0 1 0 ↑ X Inc TCU TCD CEOU 0
0 0 1 0 ↓ X Inc TCU TCD CEOU 0
0 0 0 1 ↑ X Dec TCU TCD 0 CEOD
0 0 0 1 ↓ X Dec TCU TCD 0 CEOD
0 0 1 1 ↑ X Inc TCU TCD Invalid Invalid
0 0 1 1 ↓ X Inc TCU TCD Invalid Invalid
z = bit width - 1
TCU = Qz•Q(z-1)•Q(z-2)•...•Q0
TCD = Qz•Q(z-1)•Q(z-2)•...•Q0
CEOU = TCU•CEU
CEOD = TCD•CED
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 195
Chapter 3: About Design Elements
CBD2CEMacro: 2-Bit Cascadable Dual Edge Triggered Binary Counter with Clock Enable and AsynchronousClear
Supported ArchitecturesThis design element is supported in the following architectures only:CoolRunner™-II
IntroductionThis element is an asynchronously clearable, cascadable dual edge triggered binary counter. The asynchronousclear (CLR) input, when High, overrides all other inputs and forces the Q outputs, terminal count (TC), and clockenable out (CEO) to logic level zero, independent of clock transitions. The Q outputs increment when the clockenable input (CE) is High during the Low-to-High and High-to-Low clock (C) transition. The counter ignoresclock transitions when CE is Low. The TC output is High when all Q outputs are High.
Create larger counters by connecting the CEO output of each stage to the CE input of the next stage andconnecting the C and CLR inputs in parallel. CEO is active (High) when TC and CE are High. The maximumlength of the counter is determined by the accumulated CE-to-TC propagation delays versus the clock period.The clock period must be greater than n (tCE-TC), where n is the number of stages and the time tCE-TC is theCE-to-TC propagation delay of each stage. When cascading counters, use the CEO output if the counter uses theCE input or use the TC output if it does not.
This counter is asynchronously cleared, outputs Low, when power is applied. For CPLD devices, you cansimulate power-on by applying a High-level pulse on the PRLD global net.
Logic TableInputs Outputs
CLR CE C Qz : Q0 TC CEO
1 X X 0 0 0
0 0 X No change No change 0
0 1 ↑ Inc TC CEO
0 1 ↓ Inc TC CEO
z = bit width - 1
TC = Qz•Q(z-1)•Q(z-2)•...•Q0
CEO = TC•CE
Design Entry MethodThis design element is only for use in schematics.
CPLD Libraries Guide196 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 197
Chapter 3: About Design Elements
CBD2CLEMacro: 2-Bit Loadable Cascadable Dual Edge Triggered Binary Counter with Clock Enable andAsynchronous Clear
Supported ArchitecturesThis design element is supported in the following architectures only:
CoolRunner™-II
IntroductionThis is a synchronously loadable, asynchronously clearable, cascadable dual edge triggered binary counters.The asynchronous clear (CLR) input, when High, overrides all other inputs and forces the Q outputs, terminalcount (TC), and clock enable out (CEO) to logic level zero, independent of clock transitions. The data on theD inputs is loaded into the counter when the load enable input (L) is High during the Low-to-High clocktransition, independent of the state of clock enable (CE). The Q outputs increment when CE is High during theLow-to-High and High-to-Low clock transition. The counter ignores clock transitions when CE is Low. The TCoutput is High when all Q outputs are High.
Create larger counters by connecting the CEO output of each stage to the CE input of the next stage andconnecting the C, L, and CLR inputs in parallel. CEO is active (High) when TC and CE are High. The maximumlength of the counter is determined by the accumulated CE-to-TC propagation delays versus the clock period.The clock period must be greater than n (tCE-TC), where n is the number of stages and the time tCE-TC is theCE-to-TC propagation delay of each stage. When cascading counters, use the CEO output if the counter uses theCE input or use the TC output if it does not.
This counter is asynchronously cleared, outputs Low, when power is applied. For CPLD devices, you cansimulate power-on by applying a High-level pulse on the PRLD global net.
CPLD Libraries Guide198 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
Logic TableInputs Outputs
CLR L CE C Dz : D0 Qz : Q0 TC CEO
1 X X X X 0 0 0
0 1 X ↑ Dn Dn TC CEO
0 1 X ↓ Dn Dn TC CEO
0 0 0 X X No change No change 0
0 0 1 ↑ X Inc TC CEO
0 0 1 ↓ X Inc TC CEO
z = bit width - 1
TC = Qz•Q(z-1)•Q(z-2)•...•Q0
CEO = TC•CE
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 199
Chapter 3: About Design Elements
CBD2CLEDMacro: 2-Bit Loadable Cascadable Bidirectional Dual Edge Triggered Binary Counter with ClockEnable and Asynchronous Clear
Supported ArchitecturesThis design element is supported in the following architectures only:
CoolRunner™-II
IntroductionThis design element is a synchronously loadable, asynchronously clearable, cascadable, bidirectional dual edgetriggered binary counter. The asynchronous clear (CLR) input, when High, overrides all other inputs andforces the Q outputs, terminal count (TC), and clock enable out (CEO) to logic level zero, independent of clocktransitions. The data on the D inputs is loaded into the counter when the load enable input (L) is High during theLow-to-High clock (C) transition, independent of the state of clock enable (CE). The Q outputs decrement whenCE is High and UP is Low during the Low-to-High and High-to-Low clock transition. The Q outputs incrementwhen CE and UP are High. The counter ignores clock transitions when CE is Low.
For counting up, the TC output is High when all Q outputs and UP are High. For counting down, the TCoutput is High when all Q outputs and UP are Low.
Create larger counters by connecting the CEO output of each stage to the CE input of the next stage andconnecting the C, UP, L, and CLR inputs in parallel. CEO is active (High) when TC and CE are High. Themaximum length of the counter is determined by the accumulated CE-to-TC propagation delays versus the clockperiod. The clock period must be greater than n (tCE-TC), where n is the number of stages and the time tCE-TC isthe CE-to-TC propagation delay of each stage. When cascading counters, use the CEO output if the counteruses the CE input or use the TC output if it does not.
See “CB2X1,” “CB4X1,” “CB8X1,” “CB16X1” for high-performance cascadable, bidirectional counters.
This counter is asynchronously cleared, outputs Low, when power is applied. For CPLD devices, you cansimulate power-on by applying a High-level pulse on the PRLD global net.
CPLD Libraries Guide200 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
Logic TableInputs Outputs
CLR L CE C UP Dz : D0 Qz : Q0 TC CEO
1 X X X X X 0 0 0
0 1 X ↑ X Dn Dn TC CEO
0 1 X ↓ X Dn Dn TC CEO
0 0 0 X X X No change No change 0
0 0 1 ↑ 1 X Inc TC CEO
0 0 1 ↓ 1 X Inc TC CEO
0 0 1 ↑ 0 X Dec TC CEO
0 0 1 ↓ 0 X Dec TC CEO
z = bit width - 1
TC = (Qz•Q(z-1)•Q(z-2)•...•Q0•UP) + (Qz•Q(z-1)•Q(z-2)•...•Q0•UP)
CEO = TC•CE
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 201
Chapter 3: About Design Elements
CBD2REMacro: 2-Bit Cascadable Dual Edge Triggered Binary Counter with Clock Enable and SynchronousReset
Supported ArchitecturesThis design element is supported in the following architectures only:
CoolRunner™-II
IntroductionThis design element is a synchronous, resettable, cascadable dual edge triggered binary counter. The synchronousreset (R), when High, overrides all other inputs and forces the Q outputs, terminal count (TC), and clock enableout (CEO) to logic level zero during the Low-to-High or High-to-Low clock transition. The Q outputs incrementwhen the clock enable input (CE) is High during the Low-to-High and High-to-Low clock (C) transition. Thecounter ignores clock transitions when CE is Low. The TC output is High when both Q outputs are High.
Create larger counters by connecting the CEO output of each stage to the CE input of the next stage andconnecting the C and R inputs in parallel. CEO is active (High) when TC and CE are High. The maximum lengthof the counter is determined by the accumulated CE-to-TC propagation delays versus the clock period. Theclock period must be greater than n (tCE-TC), where n is the number of stages and the time tCE-TC is the CE-to-TCpropagation delay of each stage. When cascading counters, use the CEO output if the counter uses the CEinput or use the TC output if it does not.
This counter is asynchronously cleared, outputs Low, when power is applied. For CPLD devices, you cansimulate power-on by applying a High-level pulse on the PRLD global net.
Logic TableInputs Outputs
R CE C Qz-Q0 TC CEO
1 X ↑ 0 0 0
1 X ↓ 0 0 0
0 0 X No change No change 0
0 1 ↑ Inc TC CEO
0 1 ↓ Inc TC CEO
z = bit width - 1
TC = Qz•Q(z-1)•Q(z-2)•...•Q0)
CEO = TC•CE
CPLD Libraries Guide202 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 203
Chapter 3: About Design Elements
CBD2RLEMacro: 2-Bit Loadable Cascadable Dual Edge Triggered Binary Counter with Clock Enable andSynchronous Reset
Supported ArchitecturesThis design element is supported in the following architectures only:
CoolRunner™-II
IntroductionThis design element is a synchronous, loadable, resettable, cascadable dual edge triggered binary counter. Thesynchronous reset (R), when High, overrides all other inputs and forces the Q outputs, terminal count (TC), andclock enable out (CEO) outputs to Low on the Low-to-High or High-to-Low clock (C) transition.
The data on the D inputs is loaded into the counter when the load enable input (L) is High during theLow-to-High and High-to-Low clock (C) transition, independent of the state of CE. The Q outputs incrementwhen CE is High during the Low-to-High and High-to-Low clock transition. The counter ignores clocktransitions when CE is Low. The TC output is High when all Q outputs are High. The CEO output is High whenall Q outputs and CE are High to allow direct cascading of counters.
Create larger counters by connecting the CEO output of each stage to the CE input of the next stage andconnecting the C, L, and R inputs in parallel. CEO is active (High) when TC and CE are High. The maximumlength of the counter is determined by the accumulated CE-to-TC propagation delays versus the clock period.The clock period must be greater than n (tCE-TC), where n is the number of stages and the time tCE-TC is theCE-to-TC propagation delay of each stage. When cascading counters, use the CEO output if the counter uses theCE input or use the TC output if it does not.
This counter is asynchronously cleared, outputs Low, when power is applied. For CPLD devices, you cansimulate power-on by applying a High-level pulse on the PRLD global net.
CPLD Libraries Guide204 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
Logic TableInputs Outputs
R L CE C Dz : D0 Qz : Q0 TC CEO
1 X X ↑ X 0 0 0
1 X X ↓ X 0 0 0
0 1 X ↑ Dn Dn TC CEO
0 1 X ↓ Dn Dn TC CEO
0 0 0 X X No change No change 0
0 0 1 ↑ X Inc TC CEO
0 0 1 ↓ X Inc TC CEO
z = bit width - 1
TC = Qz•Q(z-1)•Q(z-2)•...•Q0
CEO = TC•CE
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 205
Chapter 3: About Design Elements
CBD2X1Macro: 2-Bit Loadable Cascadable Bidirectional Dual Edge Triggered Binary Counter with ClockEnable and Asynchronous Clear
Supported ArchitecturesThis design element is supported in the following architectures only:CoolRunner™-II
IntroductionThis design element is a synchronously loadable, asynchronously clearable, bidirectional dual edge triggeredbinary counters. It has separate count-enable inputs and synchronous terminal-count outputs for up and downdirections to support high speed cascading.
The asynchronous clear (CLR) is the highest priority input. When CLR is High, all other inputs are ignored; dataoutputs (Q) go to logic level zero, terminal count outputs TCU and TCD go to zero and one, respectively, clockenable outputs CEOU and CEOD go to Low and High, respectively, independent of clock transitions. The dataon the D inputs loads into the counter on the Low-to-High and High-to-Low clock (C) transition when the loadenable input (L) is High, independent of the CE inputs.
The Q outputs increment when CEU is High, provided CLR and L are Low, during the Low-to-High andHigh-to-Low clock transition. The Q outputs decrement when CED is High, provided CLR and L are Low.The counter ignores clock transitions when CEU and CED are Low. Both CEU and CED should not be Highduring the same clock transition; the CEOU and CEOD outputs might not function properly for cascading whenCEU and CED are both High.
For counting up, the CEOU output is High when all Q outputs and CEU are High. For counting down, theCEOD output is High when all Q outputs are Low and CED is High. To cascade counters, the CEOU and CEODoutputs of each counter are connected directly to the CEU and CED inputs, respectively, of the next stage. Theclock, L, and CLR inputs are connected in parallel.
The maximum clocking frequency of these counters is unaffected by the number of cascaded stages for allcounting and loading functions. The TCU terminal count output is High when all Q outputs are High, regardlessof CEU. The TCD output is High when all Q outputs are Low, regardless of CED.
When cascading counters, the final terminal count signals can be produced by AND wiring all the TCU outputs(for the up direction) and all the TCD outputs (for the down direction). The TCU, CEOU, and CEOD outputs areproduced by optimizable AND gates within the component. This results in zero propagation from the CEUand CED inputs and from the Q outputs, provided all connections from each such output remain on-chip.Otherwise, a macrocell buffer delay is introduced.
This counter is asynchronously cleared, outputs Low, when power is applied. For CPLD devices, you cansimulate power-on by applying a High-level pulse on the PRLD global net.
CPLD Libraries Guide206 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
Logic TableInputs Outputs
CLR L CEU CED C Dz–D0 Qz–Q0 TCU TCD CEOU CEOD
1 X X X X X 0 0 1 0 CEOD
0 1 X X ↑ Dn Dn TCU TCD CEOU CEOD
0 1 X X ↓ Dn Dn TCU TCD CEOU CEOD
0 0 0 0 X X NoChange
NoChange
NoChange
0 0
0 0 1 0 ↑ X Inc TCU TCD CEOU 0
0 0 1 0 ↓ X Inc TCU TCD CEOU 0
0 0 0 1 ↑ X Dec TCU TCD 0 CEOD
0 0 0 1 ↓ X Dec TCU TCD 0 CEOD
0 0 1 1 ↑ X Inc TCU TCD Invalid Invalid
0 0 1 1 ↓ X Inc TCU TCD Invalid Invalid
z = bit width - 1
TCU = Qz•Q(z-1)•Q(z-2)•...•Q0
TCD = Qz•Q(z-1)•Q(z-2)•...•Q0
CEOU = TCU•CEU
CEOD = TCD•CED
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 207
Chapter 3: About Design Elements
CBD2X2Macro: 2-Bit Loadable Cascadable Bidirectional Dual Edge Triggered Binary Counter with ClockEnable and Synchronous Reset
Supported ArchitecturesThis design element is supported in the following architectures only:CoolRunner™-II
IntroductionThis design element is a synchronous, loadable, resettable, bidirectional dual edge triggered binary counter. Ithas separate count-enable inputs and synchronous terminal-count outputs for up and down directions tosupport high-speed cascading.
The synchronous reset (R) is the highest priority input. When R is High, all other inputs are ignored; the dataoutputs (Q) go to logic level zero, terminal count outputs TCU and TCD go to zero and one, respectively, andclock enable outputs CEOU and CEOD go to Low and High, respectively, on the Low-to-High and High-to-Lowclock (C) transition. The data on the D inputs loads into the counter on the Low-to-High and High-to-Low clock(C) transition when the load enable input (L) is High, independent of the CE inputs.
All Q outputs increment when CEU is High, provided R and L are Low during the Low-to-High andHigh-to-Low clock transition. All Q outputs decrement when CED is High, provided R and L are Low. Thecounter ignores clock transitions when CEU and CED are Low. Both CEU and CED should not be High duringthe same clock transition; the CEOU and CEOD outputs might not function properly for cascading when CEUand CED are both High.
For counting up, the CEOU output is High when all Q outputs and CEU are High. For counting down, theCEOD output is High when all Q outputs are Low and CED is High. To cascade counters, the CEOU and CEODoutputs of each counter are, respectively, connected directly to the CEU and CED inputs of the next stage. The C,L, and R inputs are connected in parallel.
The maximum clocking frequency of these counter components is unaffected by the number of cascaded stagesfor all counting and loading functions. The TCU terminal count output is High when all Q outputs are High,regardless of CEU. The TCD output is High when all Q outputs are Low, regardless of CED.
When cascading counters, the final terminal count signals can be produced by AND wiring all the TCU outputs(for the up direction) and all the TCD outputs (for the down direction). The TCU, CEOU, and CEOD outputs areproduced by optimizable AND gates within the component. This results in zero propagation from the CEUand CED inputs and from the Q outputs, provided all connections from each such output remain on-chip.Otherwise, a macrocell buffer delay is introduced.
This counter is asynchronously cleared, outputs Low, when power is applied. For CPLD devices, you cansimulate power-on by applying a High-level pulse on the PRLD global net.
CPLD Libraries Guide208 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
Logic TableInputs Outputs
R L CEU CED C Dz : D0 Qz : Q0 TCU TCD CEOU CEOD
1 X X X ↑ X 0 0 1 0 CEOD
1 X X X ↓ X 0 0 1 0 CEOD
0 1 X X ↑ Dn Dn TCU TCD CEOU CEOD
0 1 X X ↓ Dn Dn TCU TCD CEOU CEOD
0 0 0 0 X X NoChange NoChange
NoChange
0 0
0 0 1 0 ↑ X Inc TCU TCD CEOU 0
0 0 1 0 ↓ X Inc TCU TCD CEOU 0
0 0 0 1 ↑ X Dec TCU TCD 0 CEOD
0 0 0 1 ↓ X Dec TCU TCD 0 CEOD
0 0 1 1 ↑ X Inc TCU TCD Invalid Invalid
0 0 1 1 ↓ X Inc TCU TCD Invalid Invalid
z = bit width - 1
TCU = Qz•Q(z-1)•Q(z-2)•...•Q0
TCD = Qz•Q(z-1)•Q(z-2)•...•Q0
CEOU = TCU•CEU
CEOD = TCD•CED
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 209
Chapter 3: About Design Elements
CBD4CEMacro: 4-Bit Cascadable Dual Edge Triggered Binary Counter with Clock Enable and AsynchronousClear
Supported ArchitecturesThis design element is supported in the following architectures only:
CoolRunner™-II
IntroductionThis element is an asynchronously clearable, cascadable dual edge triggered binary counter. The asynchronousclear (CLR) input, when High, overrides all other inputs and forces the Q outputs, terminal count (TC), and clockenable out (CEO) to logic level zero, independent of clock transitions. The Q outputs increment when the clockenable input (CE) is High during the Low-to-High and High-to-Low clock (C) transition. The counter ignoresclock transitions when CE is Low. The TC output is High when all Q outputs are High.
Create larger counters by connecting the CEO output of each stage to the CE input of the next stage andconnecting the C and CLR inputs in parallel. CEO is active (High) when TC and CE are High. The maximumlength of the counter is determined by the accumulated CE-to-TC propagation delays versus the clock period.The clock period must be greater than n (tCE-TC), where n is the number of stages and the time tCE-TC is theCE-to-TC propagation delay of each stage. When cascading counters, use the CEO output if the counter uses theCE input or use the TC output if it does not.
This counter is asynchronously cleared, outputs Low, when power is applied. For CPLD devices, you cansimulate power-on by applying a High-level pulse on the PRLD global net.
Logic TableInputs Outputs
CLR CE C Qz : Q0 TC CEO
1 X X 0 0 0
0 0 X No change No change 0
0 1 ↑ Inc TC CEO
0 1 ↓ Inc TC CEO
z = bit width - 1
TC = Qz•Q(z-1)•Q(z-2)•...•Q0
CEO = TC•CE
CPLD Libraries Guide210 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 211
Chapter 3: About Design Elements
CBD4CLEMacro: 4-Bit Loadable Cascadable Dual Edge Triggered Binary Counter with Clock Enable andAsynchronous Clear
Supported ArchitecturesThis design element is supported in the following architectures only:
CoolRunner™-II
IntroductionThis is a synchronously loadable, asynchronously clearable, cascadable dual edge triggered binary counters.The asynchronous clear (CLR) input, when High, overrides all other inputs and forces the Q outputs, terminalcount (TC), and clock enable out (CEO) to logic level zero, independent of clock transitions. The data on theD inputs is loaded into the counter when the load enable input (L) is High during the Low-to-High clocktransition, independent of the state of clock enable (CE). The Q outputs increment when CE is High during theLow-to-High and High-to-Low clock transition. The counter ignores clock transitions when CE is Low. The TCoutput is High when all Q outputs are High.
Create larger counters by connecting the CEO output of each stage to the CE input of the next stage andconnecting the C, L, and CLR inputs in parallel. CEO is active (High) when TC and CE are High. The maximumlength of the counter is determined by the accumulated CE-to-TC propagation delays versus the clock period.The clock period must be greater than n (tCE-TC), where n is the number of stages and the time tCE-TC is theCE-to-TC propagation delay of each stage. When cascading counters, use the CEO output if the counter uses theCE input or use the TC output if it does not.
This counter is asynchronously cleared, outputs Low, when power is applied. For CPLD devices, you cansimulate power-on by applying a High-level pulse on the PRLD global net.
Logic TableInputs Outputs
CLR L CE C Dz : D0 Qz : Q0 TC CEO
1 X X X X 0 0 0
0 1 X ↑ Dn Dn TC CEO
0 1 X ↓ Dn Dn TC CEO
0 0 0 X X No change No change 0
CPLD Libraries Guide212 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
Inputs Outputs
CLR L CE C Dz : D0 Qz : Q0 TC CEO
0 0 1 ↑ X Inc TC CEO
0 0 1 ↓ X Inc TC CEO
z = bit width - 1
TC = Qz•Q(z-1)•Q(z-2)•...•Q0
CEO = TC•CE
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 213
Chapter 3: About Design Elements
CBD4CLEDMacro: 4-Bit Loadable Cascadable Bidirectional Dual Edge Triggered Binary Counter with ClockEnable and Asynchronous Clear
Supported ArchitecturesThis design element is supported in the following architectures only:
CoolRunner™-II
IntroductionThis design element is a synchronously loadable, asynchronously clearable, cascadable, bidirectional dual edgetriggered binary counter. The asynchronous clear (CLR) input, when High, overrides all other inputs andforces the Q outputs, terminal count (TC), and clock enable out (CEO) to logic level zero, independent of clocktransitions. The data on the D inputs is loaded into the counter when the load enable input (L) is High during theLow-to-High clock (C) transition, independent of the state of clock enable (CE). The Q outputs decrement whenCE is High and UP is Low during the Low-to-High and High-to-Low clock transition. The Q outputs incrementwhen CE and UP are High. The counter ignores clock transitions when CE is Low.
For counting up, the TC output is High when all Q outputs and UP are High. For counting down, the TCoutput is High when all Q outputs and UP are Low.
Create larger counters by connecting the CEO output of each stage to the CE input of the next stage andconnecting the C, UP, L, and CLR inputs in parallel. CEO is active (High) when TC and CE are High. Themaximum length of the counter is determined by the accumulated CE-to-TC propagation delays versus the clockperiod. The clock period must be greater than n (tCE-TC), where n is the number of stages and the time tCE-TC isthe CE-to-TC propagation delay of each stage. When cascading counters, use the CEO output if the counteruses the CE input or use the TC output if it does not.
See “CB2X1,” “CB4X1,” “CB8X1,” “CB16X1” for high-performance cascadable, bidirectional counters.
This counter is asynchronously cleared, outputs Low, when power is applied. For CPLD devices, you cansimulate power-on by applying a High-level pulse on the PRLD global net.
CPLD Libraries Guide214 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
Logic TableInputs Outputs
CLR L CE C UP Dz : D0 Qz : Q0 TC CEO
1 X X X X X 0 0 0
0 1 X ↑ X Dn Dn TC CEO
0 1 X ↓ X Dn Dn TC CEO
0 0 0 X X X No change No change 0
0 0 1 ↑ 1 X Inc TC CEO
0 0 1 ↓ 1 X Inc TC CEO
0 0 1 ↑ 0 X Dec TC CEO
0 0 1 ↓ 0 X Dec TC CEO
z = bit width - 1
TC = (Qz•Q(z-1)•Q(z-2)•...•Q0•UP) + (Qz•Q(z-1)•Q(z-2)•...•Q0•UP)
CEO = TC•CE
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 215
Chapter 3: About Design Elements
CBD4REMacro: 4-Bit Cascadable Dual Edge Triggered Binary Counter with Clock Enable and SynchronousReset
Supported ArchitecturesThis design element is supported in the following architectures only:CoolRunner™-II
IntroductionThis design element is a synchronous, resettable, cascadable dual edge triggered binary counter. The synchronousreset (R), when High, overrides all other inputs and forces the Q outputs, terminal count (TC), and clock enableout (CEO) to logic level zero during the Low-to-High or High-to-Low clock transition. The Q outputs incrementwhen the clock enable input (CE) is High during the Low-to-High and High-to-Low clock (C) transition. Thecounter ignores clock transitions when CE is Low. The TC output is High when both Q outputs are High.
Create larger counters by connecting the CEO output of each stage to the CE input of the next stage andconnecting the C and R inputs in parallel. CEO is active (High) when TC and CE are High. The maximum lengthof the counter is determined by the accumulated CE-to-TC propagation delays versus the clock period. Theclock period must be greater than n (tCE-TC), where n is the number of stages and the time tCE-TC is the CE-to-TCpropagation delay of each stage. When cascading counters, use the CEO output if the counter uses the CEinput or use the TC output if it does not.
This counter is asynchronously cleared, outputs Low, when power is applied. For CPLD devices, you cansimulate power-on by applying a High-level pulse on the PRLD global net.
Logic TableInputs Outputs
R CE C Qz-Q0 TC CEO
1 X ↑ 0 0 0
1 X ↓ 0 0 0
0 0 X No change No change 0
0 1 ↑ Inc TC CEO
0 1 ↓ Inc TC CEO
z = bit width - 1
TC = Qz•Q(z-1)•Q(z-2)•...•Q0)
CEO = TC•CE
CPLD Libraries Guide216 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 217
Chapter 3: About Design Elements
CBD4RLEMacro: 4-Bit Loadable Cascadable Dual Edge Triggered Binary Counter with Clock Enable andSynchronous Reset
Supported ArchitecturesThis design element is supported in the following architectures only:
CoolRunner™-II
IntroductionThis design element is a synchronous, loadable, resettable, cascadable dual edge triggered binary counter. Thesynchronous reset (R), when High, overrides all other inputs and forces the Q outputs, terminal count (TC), andclock enable out (CEO) outputs to Low on the Low-to-High or High-to-Low clock (C) transition.
The data on the D inputs is loaded into the counter when the load enable input (L) is High during theLow-to-High and High-to-Low clock (C) transition, independent of the state of CE. The Q outputs incrementwhen CE is High during the Low-to-High and High-to-Low clock transition. The counter ignores clocktransitions when CE is Low. The TC output is High when all Q outputs are High. The CEO output is High whenall Q outputs and CE are High to allow direct cascading of counters.
Create larger counters by connecting the CEO output of each stage to the CE input of the next stage andconnecting the C, L, and R inputs in parallel. CEO is active (High) when TC and CE are High. The maximumlength of the counter is determined by the accumulated CE-to-TC propagation delays versus the clock period.The clock period must be greater than n (tCE-TC), where n is the number of stages and the time tCE-TC is theCE-to-TC propagation delay of each stage. When cascading counters, use the CEO output if the counter uses theCE input or use the TC output if it does not.
This counter is asynchronously cleared, outputs Low, when power is applied. For CPLD devices, you cansimulate power-on by applying a High-level pulse on the PRLD global net.
CPLD Libraries Guide218 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
Logic TableInputs Outputs
R L CE C Dz : D0 Qz : Q0 TC CEO
1 X X ↑ X 0 0 0
1 X X ↓ X 0 0 0
0 1 X ↑ Dn Dn TC CEO
0 1 X ↓ Dn Dn TC CEO
0 0 0 X X No change No change 0
0 0 1 ↑ X Inc TC CEO
0 0 1 ↓ X Inc TC CEO
z = bit width - 1
TC = Qz•Q(z-1)•Q(z-2)•...•Q0
CEO = TC•CE
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 219
Chapter 3: About Design Elements
CBD4X1Macro: 4-Bit Loadable Cascadable Bidirectional Dual Edge Triggered Binary Counter with ClockEnable and Asynchronous Clear
Supported ArchitecturesThis design element is supported in the following architectures only:
CoolRunner™-II
IntroductionThis design element is a synchronously loadable, asynchronously clearable, bidirectional dual edge triggeredbinary counters. It has separate count-enable inputs and synchronous terminal-count outputs for up and downdirections to support high speed cascading.
The asynchronous clear (CLR) is the highest priority input. When CLR is High, all other inputs are ignored; dataoutputs (Q) go to logic level zero, terminal count outputs TCU and TCD go to zero and one, respectively, clockenable outputs CEOU and CEOD go to Low and High, respectively, independent of clock transitions. The dataon the D inputs loads into the counter on the Low-to-High and High-to-Low clock (C) transition when the loadenable input (L) is High, independent of the CE inputs.
The Q outputs increment when CEU is High, provided CLR and L are Low, during the Low-to-High andHigh-to-Low clock transition. The Q outputs decrement when CED is High, provided CLR and L are Low.The counter ignores clock transitions when CEU and CED are Low. Both CEU and CED should not be Highduring the same clock transition; the CEOU and CEOD outputs might not function properly for cascading whenCEU and CED are both High.
For counting up, the CEOU output is High when all Q outputs and CEU are High. For counting down, theCEOD output is High when all Q outputs are Low and CED is High. To cascade counters, the CEOU and CEODoutputs of each counter are connected directly to the CEU and CED inputs, respectively, of the next stage. Theclock, L, and CLR inputs are connected in parallel.
The maximum clocking frequency of these counters is unaffected by the number of cascaded stages for allcounting and loading functions. The TCU terminal count output is High when all Q outputs are High, regardlessof CEU. The TCD output is High when all Q outputs are Low, regardless of CED.
When cascading counters, the final terminal count signals can be produced by AND wiring all the TCU outputs(for the up direction) and all the TCD outputs (for the down direction). The TCU, CEOU, and CEOD outputs areproduced by optimizable AND gates within the component. This results in zero propagation from the CEUand CED inputs and from the Q outputs, provided all connections from each such output remain on-chip.Otherwise, a macrocell buffer delay is introduced.
CPLD Libraries Guide220 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
This counter is asynchronously cleared, outputs Low, when power is applied. For CPLD devices, you cansimulate power-on by applying a High-level pulse on the PRLD global net.
Logic TableInputs Outputs
CLR L CEU CED C Dz–D0 Qz–Q0 TCU TCD CEOU CEOD
1 X X X X X 0 0 1 0 CEOD
0 1 X X ↑ Dn Dn TCU TCD CEOU CEOD
0 1 X X ↓ Dn Dn TCU TCD CEOU CEOD
0 0 0 0 X X NoChange
NoChange
NoChange
0 0
0 0 1 0 ↑ X Inc TCU TCD CEOU 0
0 0 1 0 ↓ X Inc TCU TCD CEOU 0
0 0 0 1 ↑ X Dec TCU TCD 0 CEOD
0 0 0 1 ↓ X Dec TCU TCD 0 CEOD
0 0 1 1 ↑ X Inc TCU TCD Invalid Invalid
0 0 1 1 ↓ X Inc TCU TCD Invalid Invalid
z = bit width - 1
TCU = Qz•Q(z-1)•Q(z-2)•...•Q0
TCD = Qz•Q(z-1)•Q(z-2)•...•Q0
CEOU = TCU•CEU
CEOD = TCD•CED
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 221
Chapter 3: About Design Elements
CBD4X2Macro: 4-Bit Loadable Cascadable Bidirectional Dual Edge Triggered Binary Counter with ClockEnable and Synchronous Reset
Supported ArchitecturesThis design element is supported in the following architectures only:CoolRunner™-II
IntroductionThis design element is a synchronous, loadable, resettable, bidirectional dual edge triggered binary counter. Ithas separate count-enable inputs and synchronous terminal-count outputs for up and down directions tosupport high-speed cascading.
The synchronous reset (R) is the highest priority input. When R is High, all other inputs are ignored; the dataoutputs (Q) go to logic level zero, terminal count outputs TCU and TCD go to zero and one, respectively, andclock enable outputs CEOU and CEOD go to Low and High, respectively, on the Low-to-High and High-to-Lowclock (C) transition. The data on the D inputs loads into the counter on the Low-to-High and High-to-Low clock(C) transition when the load enable input (L) is High, independent of the CE inputs.
All Q outputs increment when CEU is High, provided R and L are Low during the Low-to-High andHigh-to-Low clock transition. All Q outputs decrement when CED is High, provided R and L are Low. Thecounter ignores clock transitions when CEU and CED are Low. Both CEU and CED should not be High duringthe same clock transition; the CEOU and CEOD outputs might not function properly for cascading when CEUand CED are both High.
For counting up, the CEOU output is High when all Q outputs and CEU are High. For counting down, theCEOD output is High when all Q outputs are Low and CED is High. To cascade counters, the CEOU and CEODoutputs of each counter are, respectively, connected directly to the CEU and CED inputs of the next stage. The C,L, and R inputs are connected in parallel.
The maximum clocking frequency of these counter components is unaffected by the number of cascaded stagesfor all counting and loading functions. The TCU terminal count output is High when all Q outputs are High,regardless of CEU. The TCD output is High when all Q outputs are Low, regardless of CED.
When cascading counters, the final terminal count signals can be produced by AND wiring all the TCU outputs(for the up direction) and all the TCD outputs (for the down direction). The TCU, CEOU, and CEOD outputs areproduced by optimizable AND gates within the component. This results in zero propagation from the CEUand CED inputs and from the Q outputs, provided all connections from each such output remain on-chip.Otherwise, a macrocell buffer delay is introduced.
This counter is asynchronously cleared, outputs Low, when power is applied. For CPLD devices, you cansimulate power-on by applying a High-level pulse on the PRLD global net.
CPLD Libraries Guide222 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
Logic TableInputs Outputs
R L CEU CED C Dz : D0 Qz : Q0 TCU TCD CEOU CEOD
1 X X X ↑ X 0 0 1 0 CEOD
1 X X X ↓ X 0 0 1 0 CEOD
0 1 X X ↑ Dn Dn TCU TCD CEOU CEOD
0 1 X X ↓ Dn Dn TCU TCD CEOU CEOD
0 0 0 0 X X NoChange NoChange
NoChange
0 0
0 0 1 0 ↑ X Inc TCU TCD CEOU 0
0 0 1 0 ↓ X Inc TCU TCD CEOU 0
0 0 0 1 ↑ X Dec TCU TCD 0 CEOD
0 0 0 1 ↓ X Dec TCU TCD 0 CEOD
0 0 1 1 ↑ X Inc TCU TCD Invalid Invalid
0 0 1 1 ↓ X Inc TCU TCD Invalid Invalid
z = bit width - 1
TCU = Qz•Q(z-1)•Q(z-2)•...•Q0
TCD = Qz•Q(z-1)•Q(z-2)•...•Q0
CEOU = TCU•CEU
CEOD = TCD•CED
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 223
Chapter 3: About Design Elements
CBD8CEMacro: 8-Bit Cascadable Dual Edge Triggered Binary Counter with Clock Enable and AsynchronousClear
Supported ArchitecturesThis design element is supported in the following architectures only:CoolRunner™-II
IntroductionThis element is an asynchronously clearable, cascadable dual edge triggered binary counter. The asynchronousclear (CLR) input, when High, overrides all other inputs and forces the Q outputs, terminal count (TC), and clockenable out (CEO) to logic level zero, independent of clock transitions. The Q outputs increment when the clockenable input (CE) is High during the Low-to-High and High-to-Low clock (C) transition. The counter ignoresclock transitions when CE is Low. The TC output is High when all Q outputs are High.
Create larger counters by connecting the CEO output of each stage to the CE input of the next stage andconnecting the C and CLR inputs in parallel. CEO is active (High) when TC and CE are High. The maximumlength of the counter is determined by the accumulated CE-to-TC propagation delays versus the clock period.The clock period must be greater than n (tCE-TC), where n is the number of stages and the time tCE-TC is theCE-to-TC propagation delay of each stage. When cascading counters, use the CEO output if the counter uses theCE input or use the TC output if it does not.
This counter is asynchronously cleared, outputs Low, when power is applied. For CPLD devices, you cansimulate power-on by applying a High-level pulse on the PRLD global net.
Logic TableInputs Outputs
CLR CE C Qz : Q0 TC CEO
1 X X 0 0 0
0 0 X No change No change 0
0 1 ↑ Inc TC CEO
0 1 ↓ Inc TC CEO
z = bit width - 1
TC = Qz•Q(z-1)•Q(z-2)•...•Q0
CEO = TC•CE
Design Entry MethodThis design element is only for use in schematics.
CPLD Libraries Guide224 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 225
Chapter 3: About Design Elements
CBD8CLEMacro: 8-Bit Loadable Cascadable Dual Edge Triggered Binary Counter with Clock Enable andAsynchronous Clear
Supported ArchitecturesThis design element is supported in the following architectures only:
CoolRunner™-II
IntroductionThis is a synchronously loadable, asynchronously clearable, cascadable dual edge triggered binary counters.The asynchronous clear (CLR) input, when High, overrides all other inputs and forces the Q outputs, terminalcount (TC), and clock enable out (CEO) to logic level zero, independent of clock transitions. The data on theD inputs is loaded into the counter when the load enable input (L) is High during the Low-to-High clocktransition, independent of the state of clock enable (CE). The Q outputs increment when CE is High during theLow-to-High and High-to-Low clock transition. The counter ignores clock transitions when CE is Low. The TCoutput is High when all Q outputs are High.
Create larger counters by connecting the CEO output of each stage to the CE input of the next stage andconnecting the C, L, and CLR inputs in parallel. CEO is active (High) when TC and CE are High. The maximumlength of the counter is determined by the accumulated CE-to-TC propagation delays versus the clock period.The clock period must be greater than n (tCE-TC), where n is the number of stages and the time tCE-TC is theCE-to-TC propagation delay of each stage. When cascading counters, use the CEO output if the counter uses theCE input or use the TC output if it does not.
This counter is asynchronously cleared, outputs Low, when power is applied. For CPLD devices, you cansimulate power-on by applying a High-level pulse on the PRLD global net.
CPLD Libraries Guide226 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
Logic TableInputs Outputs
CLR L CE C Dz : D0 Qz : Q0 TC CEO
1 X X X X 0 0 0
0 1 X ↑ Dn Dn TC CEO
0 1 X ↓ Dn Dn TC CEO
0 0 0 X X No change No change 0
0 0 1 ↑ X Inc TC CEO
0 0 1 ↓ X Inc TC CEO
z = bit width - 1
TC = Qz•Q(z-1)•Q(z-2)•...•Q0
CEO = TC•CE
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 227
Chapter 3: About Design Elements
CBD8CLEDMacro: 8-Bit Loadable Cascadable Bidirectional Dual Edge Triggered Binary Counter with ClockEnable and Asynchronous Clear
Supported ArchitecturesThis design element is supported in the following architectures only:
CoolRunner™-II
IntroductionThis design element is a synchronously loadable, asynchronously clearable, cascadable, bidirectional dual edgetriggered binary counter. The asynchronous clear (CLR) input, when High, overrides all other inputs andforces the Q outputs, terminal count (TC), and clock enable out (CEO) to logic level zero, independent of clocktransitions. The data on the D inputs is loaded into the counter when the load enable input (L) is High during theLow-to-High clock (C) transition, independent of the state of clock enable (CE). The Q outputs decrement whenCE is High and UP is Low during the Low-to-High and High-to-Low clock transition. The Q outputs incrementwhen CE and UP are High. The counter ignores clock transitions when CE is Low.
For counting up, the TC output is High when all Q outputs and UP are High. For counting down, the TCoutput is High when all Q outputs and UP are Low.
Create larger counters by connecting the CEO output of each stage to the CE input of the next stage andconnecting the C, UP, L, and CLR inputs in parallel. CEO is active (High) when TC and CE are High. Themaximum length of the counter is determined by the accumulated CE-to-TC propagation delays versus the clockperiod. The clock period must be greater than n (tCE-TC), where n is the number of stages and the time tCE-TC isthe CE-to-TC propagation delay of each stage. When cascading counters, use the CEO output if the counteruses the CE input or use the TC output if it does not.
See “CB2X1,” “CB4X1,” “CB8X1,” “CB16X1” for high-performance cascadable, bidirectional counters.
This counter is asynchronously cleared, outputs Low, when power is applied. For CPLD devices, you cansimulate power-on by applying a High-level pulse on the PRLD global net.
CPLD Libraries Guide228 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
Logic TableInputs Outputs
CLR L CE C UP Dz : D0 Qz : Q0 TC CEO
1 X X X X X 0 0 0
0 1 X ↑ X Dn Dn TC CEO
0 1 X ↓ X Dn Dn TC CEO
0 0 0 X X X No change No change 0
0 0 1 ↑ 1 X Inc TC CEO
0 0 1 ↓ 1 X Inc TC CEO
0 0 1 ↑ 0 X Dec TC CEO
0 0 1 ↓ 0 X Dec TC CEO
z = bit width - 1
TC = (Qz•Q(z-1)•Q(z-2)•...•Q0•UP) + (Qz•Q(z-1)•Q(z-2)•...•Q0•UP)
CEO = TC•CE
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 229
Chapter 3: About Design Elements
CBD8REMacro: 8-Bit Cascadable Dual Edge Triggered Binary Counter with Clock Enable and SynchronousReset
Supported ArchitecturesThis design element is supported in the following architectures only:CoolRunner™-II
IntroductionThis design element is a synchronous, resettable, cascadable dual edge triggered binary counter. The synchronousreset (R), when High, overrides all other inputs and forces the Q outputs, terminal count (TC), and clock enableout (CEO) to logic level zero during the Low-to-High or High-to-Low clock transition. The Q outputs incrementwhen the clock enable input (CE) is High during the Low-to-High and High-to-Low clock (C) transition. Thecounter ignores clock transitions when CE is Low. The TC output is High when both Q outputs are High.
Create larger counters by connecting the CEO output of each stage to the CE input of the next stage andconnecting the C and R inputs in parallel. CEO is active (High) when TC and CE are High. The maximum lengthof the counter is determined by the accumulated CE-to-TC propagation delays versus the clock period. Theclock period must be greater than n (tCE-TC), where n is the number of stages and the time tCE-TC is the CE-to-TCpropagation delay of each stage. When cascading counters, use the CEO output if the counter uses the CEinput or use the TC output if it does not.
This counter is asynchronously cleared, outputs Low, when power is applied. For CPLD devices, you cansimulate power-on by applying a High-level pulse on the PRLD global net.
Logic TableInputs Outputs
R CE C Qz-Q0 TC CEO
1 X ↑ 0 0 0
1 X ↓ 0 0 0
0 0 X No change No change 0
0 1 ↑ Inc TC CEO
0 1 ↓ Inc TC CEO
z = bit width - 1
TC = Qz•Q(z-1)•Q(z-2)•...•Q0)
CEO = TC•CE
Design Entry MethodThis design element is only for use in schematics.
CPLD Libraries Guide230 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 231
Chapter 3: About Design Elements
CBD8X1Macro: 8-Bit Loadable Cascadable Bidirectional Dual Edge Triggered Binary Counter with ClockEnable and Asynchronous Clear
Supported ArchitecturesThis design element is supported in the following architectures only:
CoolRunner™-II
IntroductionThis design element is a synchronously loadable, asynchronously clearable, bidirectional dual edge triggeredbinary counters. It has separate count-enable inputs and synchronous terminal-count outputs for up and downdirections to support high speed cascading.
The asynchronous clear (CLR) is the highest priority input. When CLR is High, all other inputs are ignored; dataoutputs (Q) go to logic level zero, terminal count outputs TCU and TCD go to zero and one, respectively, clockenable outputs CEOU and CEOD go to Low and High, respectively, independent of clock transitions. The dataon the D inputs loads into the counter on the Low-to-High and High-to-Low clock (C) transition when the loadenable input (L) is High, independent of the CE inputs.
The Q outputs increment when CEU is High, provided CLR and L are Low, during the Low-to-High andHigh-to-Low clock transition. The Q outputs decrement when CED is High, provided CLR and L are Low.The counter ignores clock transitions when CEU and CED are Low. Both CEU and CED should not be Highduring the same clock transition; the CEOU and CEOD outputs might not function properly for cascading whenCEU and CED are both High.
For counting up, the CEOU output is High when all Q outputs and CEU are High. For counting down, theCEOD output is High when all Q outputs are Low and CED is High. To cascade counters, the CEOU and CEODoutputs of each counter are connected directly to the CEU and CED inputs, respectively, of the next stage. Theclock, L, and CLR inputs are connected in parallel.
The maximum clocking frequency of these counters is unaffected by the number of cascaded stages for allcounting and loading functions. The TCU terminal count output is High when all Q outputs are High, regardlessof CEU. The TCD output is High when all Q outputs are Low, regardless of CED.
When cascading counters, the final terminal count signals can be produced by AND wiring all the TCU outputs(for the up direction) and all the TCD outputs (for the down direction). The TCU, CEOU, and CEOD outputs areproduced by optimizable AND gates within the component. This results in zero propagation from the CEUand CED inputs and from the Q outputs, provided all connections from each such output remain on-chip.Otherwise, a macrocell buffer delay is introduced.
This counter is asynchronously cleared, outputs Low, when power is applied. For CPLD devices, you cansimulate power-on by applying a High-level pulse on the PRLD global net.
CPLD Libraries Guide232 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
Logic TableInputs Outputs
CLR L CEU CED C Dz–D0 Qz–Q0 TCU TCD CEOU CEOD
1 X X X X X 0 0 1 0 CEOD
0 1 X X ↑ Dn Dn TCU TCD CEOU CEOD
0 1 X X ↓ Dn Dn TCU TCD CEOU CEOD
0 0 0 0 X X NoChange
NoChange
NoChange
0 0
0 0 1 0 ↑ X Inc TCU TCD CEOU 0
0 0 1 0 ↓ X Inc TCU TCD CEOU 0
0 0 0 1 ↑ X Dec TCU TCD 0 CEOD
0 0 0 1 ↓ X Dec TCU TCD 0 CEOD
0 0 1 1 ↑ X Inc TCU TCD Invalid Invalid
0 0 1 1 ↓ X Inc TCU TCD Invalid Invalid
z = bit width - 1
TCU = Qz•Q(z-1)•Q(z-2)•...•Q0
TCD = Qz•Q(z-1)•Q(z-2)•...•Q0
CEOU = TCU•CEU
CEOD = TCD•CED
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 233
Chapter 3: About Design Elements
CBD8X2Macro: 8-Bit Loadable Cascadable Bidirectional Dual Edge Triggered Binary Counter with ClockEnable and Synchronous Reset
Supported ArchitecturesThis design element is supported in the following architectures only:
CoolRunner™-II
IntroductionThis design element is a synchronous, loadable, resettable, bidirectional dual edge triggered binary counter. Ithas separate count-enable inputs and synchronous terminal-count outputs for up and down directions tosupport high-speed cascading.
The synchronous reset (R) is the highest priority input. When R is High, all other inputs are ignored; the dataoutputs (Q) go to logic level zero, terminal count outputs TCU and TCD go to zero and one, respectively, andclock enable outputs CEOU and CEOD go to Low and High, respectively, on the Low-to-High and High-to-Lowclock (C) transition. The data on the D inputs loads into the counter on the Low-to-High and High-to-Low clock(C) transition when the load enable input (L) is High, independent of the CE inputs.
All Q outputs increment when CEU is High, provided R and L are Low during the Low-to-High andHigh-to-Low clock transition. All Q outputs decrement when CED is High, provided R and L are Low. Thecounter ignores clock transitions when CEU and CED are Low. Both CEU and CED should not be High duringthe same clock transition; the CEOU and CEOD outputs might not function properly for cascading when CEUand CED are both High.
For counting up, the CEOU output is High when all Q outputs and CEU are High. For counting down, theCEOD output is High when all Q outputs are Low and CED is High. To cascade counters, the CEOU and CEODoutputs of each counter are, respectively, connected directly to the CEU and CED inputs of the next stage. The C,L, and R inputs are connected in parallel.
The maximum clocking frequency of these counter components is unaffected by the number of cascaded stagesfor all counting and loading functions. The TCU terminal count output is High when all Q outputs are High,regardless of CEU. The TCD output is High when all Q outputs are Low, regardless of CED.
When cascading counters, the final terminal count signals can be produced by AND wiring all the TCU outputs(for the up direction) and all the TCD outputs (for the down direction). The TCU, CEOU, and CEOD outputs areproduced by optimizable AND gates within the component. This results in zero propagation from the CEUand CED inputs and from the Q outputs, provided all connections from each such output remain on-chip.Otherwise, a macrocell buffer delay is introduced.
This counter is asynchronously cleared, outputs Low, when power is applied. For CPLD devices, you cansimulate power-on by applying a High-level pulse on the PRLD global net.
CPLD Libraries Guide234 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
Logic TableInputs Outputs
R L CEU CED C Dz : D0 Qz : Q0 TCU TCD CEOU CEOD
1 X X X ↑ X 0 0 1 0 CEOD
1 X X X ↓ X 0 0 1 0 CEOD
0 1 X X ↑ Dn Dn TCU TCD CEOU CEOD
0 1 X X ↓ Dn Dn TCU TCD CEOU CEOD
0 0 0 0 X X NoChange NoChange
NoChange
0 0
0 0 1 0 ↑ X Inc TCU TCD CEOU 0
0 0 1 0 ↓ X Inc TCU TCD CEOU 0
0 0 0 1 ↑ X Dec TCU TCD 0 CEOD
0 0 0 1 ↓ X Dec TCU TCD 0 CEOD
0 0 1 1 ↑ X Inc TCU TCD Invalid Invalid
0 0 1 1 ↓ X Inc TCU TCD Invalid Invalid
z = bit width - 1
TCU = Qz•Q(z-1)•Q(z-2)•...•Q0
TCD = Qz•Q(z-1)•Q(z-2)•...•Q0
CEOU = TCU•CEU
CEOD = TCD•CED
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 235
Chapter 3: About Design Elements
CD4CEMacro: 4-Bit Cascadable BCD Counter with Clock Enable and Asynchronous Clear
Supported ArchitecturesThis design element is supported in the following architectures only:
• XC9500
• CoolRunner™ XPLA3
• CoolRunner-II
IntroductionCD4CE is a 4-bit (stage), asynchronous clearable, cascadable binary-coded-decimal (BCD) counter. Theasynchronous clear input (CLR) is the highest priority input. When CLR is High, all other inputs are ignored;the Q outputs, terminal count (TC), and clock enable out (CEO) go to logic level zero, independent of clocktransitions. The Q outputs increment when clock enable (CE) is High during the Low-to-High clock (C)transition. The counter ignores clock transitions when CE is Low. The TC output is High when Q3 and Q0 areHigh and Q2 and Q1 are Low.
The counter recovers from any of six possible illegal states and returns to a normal count sequence within twoclock cycles for Xilinx® devices, as shown in the following state diagram:
Create larger counters by connecting the CEO output of each stage to the CE input of the next stage andconnecting the C and CLR inputs in parallel. CEO is active (High) when TC and CE are High. The maximumlength of the counter is determined by the accumulated CE-to-TC propagation delays versus the clock period.The clock period must be greater than n (tCE-TC), where n is the number of stages and the time tCE-TC is theCE-to-TC propagation delay of each stage. When cascading counters, use the CEO output if the counter uses theCE input or use the TC output if it does not.
This counter is asynchronously cleared, outputs Low, when power is applied. For CPLD devices, you cansimulate power-on by applying a High-level pulse on the PRLD global net.
CPLD Libraries Guide236 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
Logic TableInputs Outputs
CLR CE C Q3 Q2 Q1 Q0 TC CEO
1 X X 0 0 0 0 0 0
0 1 ↑ Inc Inc Inc Inc TC CEO
0 0 X No Change No Change No Change No Change TC 0
0 1 X 1 0 0 1 1 1
TC = Q3•!Q2•!Q1•Q0
CEO = TC•CE
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 237
Chapter 3: About Design Elements
CD4CLEMacro: 4-Bit Loadable Cascadable BCD Counter with Clock Enable and Asynchronous Clear
Supported ArchitecturesThis design element is supported in the following architectures only:• XC9500• CoolRunner™ XPLA3• CoolRunner-II
IntroductionCD4CLE is a 4-bit (stage), synchronously loadable, asynchronously clearable, binarycoded- decimal (BCD)counter. The asynchronous clear input (CLR) is the highest priority input. When (CLR) is High, all other inputsare ignored; the (Q) outputs, terminal count (TC), and clock enable out (CEO) go to logic level zero, independentof clock transitions. The data on the (D) inputs is loaded into the counter when the load enable input (L) is Highduring the Low-to-High clock (C) transition. The (Q) outputs increment when clock enable input (CE) is Highduring the Low- to-High clock transition. The counter ignores clock transitions when (CE) is Low. The (TC)output is High when Q3 and Q0 are High and Q2 and Q1 are Low.
The counter recovers from any of six possible illegal states and returns to a normal count sequence within twoclock cycles for Xilinx® devices, as shown in the following state diagram:
Create larger counters by connecting the CEO output of each stage to the CE input of the next stage andconnecting the C, L, and CLR inputs in parallel. CEO is active (High) when TC and CE are High. The maximumlength of the counter is determined by the accumulated CE-to-TC propagation delays versus the clock period.The clock period must be greater than n (tCE-TC), where n is the number of stages and the time tCE-TC is theCE-to-TC propagation delay of each stage. When cascading counters, use the CEO output if the counter uses theCE input or use the TC output if it does not.
This counter is asynchronously cleared, outputs Low, when power is applied. For CPLD devices, you cansimulate power-on by applying a High-level pulse on the PRLD global net.
CPLD Libraries Guide238 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
Logic TableInputs Outputs
CLR L CE D3 : D0 C Q3 Q2 Q1 Q0 TC CEO
1 X X X X 0 0 0 0 0 0
0 1 X D3 : D0 ↑ D3 D2 D1 D0 TC CEO
0 0 1 X ↑ Inc Inc Inc Inc TC CEO
0 0 0 X X NoChange
NoChange
NoChange
NoChange
TC 0
0 0 1 X X 1 0 0 1 1 1
TC = Q3•!Q2•!Q1•Q0
CEO = TC•CE
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 239
Chapter 3: About Design Elements
CD4REMacro: 4-Bit Cascadable BCD Counter with Clock Enable and Synchronous Reset
Supported ArchitecturesThis design element is supported in the following architectures only:
• XC9500
• CoolRunner™ XPLA3
• CoolRunner-II
IntroductionCD4RE is a 4-bit (stage), synchronous resettable, cascadable binary-coded-decimal (BCD) counter. Thesynchronous reset input (R) is the highest priority input. When (R) is High, all other inputs are ignored; the(Q) outputs, terminal count (TC), and clock enable out (CEO) go to logic level zero on the Low-to-High clock(C) transition. The (Q) outputs increment when the clock enable input (CE) is High during the Low-to- Highclock transition. The counter ignores clock transitions when (CE) is Low. The (TC) output is High when Q3and Q0 are High and Q2 and Q1 are Low.
The counter recovers from any of six possible illegal states and returns to a normal count sequence within twoclock cycles for Xilinx® devices, as shown in the following state diagram:
Create larger counters by connecting the CEO output of each stage to the CE input of the next stage andconnecting the C and R inputs in parallel. CEO is active (High) when TC and CE are High. The maximum lengthof the counter is determined by the accumulated CE-to-TC propagation delays versus the clock period. Theclock period must be greater than n (tCE-TC), where n is the number of stages and the time tCE-TC is the CE-to-TCpropagation delay of each stage. When cascading counters, use the CEO output if the counter uses the CEinput or use the TC output if it does not.
This counter is asynchronously cleared, outputs Low, when power is applied. For CPLD devices, you cansimulate power-on by applying a High-level pulse on the PRLD global net.
CPLD Libraries Guide240 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
Logic TableInputs Outputs
R CE C Q3 Q2 Q1 Q0 TC CEO
1 X ↑ 0 0 0 0 0 0
0 1 ↑ Inc Inc Inc Inc TC CEO
0 0 X No Change No Change No Change No Change TC 0
0 1 X 1 0 0 1 1 1
TC = Q3•!Q2•!Q1•Q0
CEO = TC•CE
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 241
Chapter 3: About Design Elements
CD4RLEMacro: 4-Bit Loadable Cascadable BCD Counter with Clock Enable and Synchronous Reset
Supported ArchitecturesThis design element is supported in the following architectures only:• XC9500• CoolRunner™ XPLA3• CoolRunner-II
IntroductionCD4RLE is a 4-bit (stage), synchronous loadable, resettable, binary-coded-decimal (BCD) counter. Thesynchronous reset input (R) is the highest priority input. When R is High, all other inputs are ignored; theQ outputs, terminal count (TC), and clock enable out (CEO) go to logic level zero on the Low-to-High clocktransitions. The data on the D inputs is loaded into the counter when the load enable input (L) is High during theLow-to-High clock (C) transition. The Q outputs increment when the clock enable input (CE) is High during theLow-to-High clock transition. The counter ignores clock transitions when CE is Low. The TC output is Highwhen Q3 and Q0 are High and Q2 and Q1 are Low.
The counter recovers from any of six possible illegal states and returns to a normal count sequence within twoclock cycles for Xilinx® devices, as shown in the following state diagram:
Create larger counters by connecting the CEO output of each stage to the CE input of the next stage andconnecting the C, L, and R inputs in parallel. CEO is active (High) when TC and CE are High. The maximumlength of the counter is determined by the accumulated CE-to-TC propagation delays versus the clock period.The clock period must be greater than n (tCE-TC), where n is the number of stages and the time tCE-TC is theCE-to-TC propagation delay of each stage. When cascading counters, use the CEO output if the counter uses theCE input or use the TC output if it does not.
CPLD Libraries Guide242 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
This counter is asynchronously cleared, outputs Low, when power is applied. For CPLD devices, you cansimulate power-on by applying a High-level pulse on the PRLD global net.
Logic TableInputs Outputs
R L CE D3 : D0 C Q3 Q2 Q1 Q0 TC CEO
1 X X X ↑ 0 0 0 0 0 0
0 1 X D3 : D0 ↑ D3 D D D0 TC CEO
0 0 1 X ↑ Inc Inc Inc Inc TC CEO
0 0 0 X X No Change NoChange
NoChange
NoChange
TC 0
0 0 1 X X 1 0 0 1 1 1
TC = Q3•!Q2•!Q1•Q0
CEO = TC•CE
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 243
Chapter 3: About Design Elements
CDD4CEMacro: 4-Bit Cascadable Dual Edge Triggered BCD Counter with Clock Enable and AsynchronousClear
Supported ArchitecturesThis design element is supported in the following architectures only:
CoolRunner™-II
IntroductionCDD4CE is a 4-bit (stage), asynchronous clearable, cascadable dual edge triggered Binary-coded-decimal (BCD)counter. The asynchronous clear input (CLR) is the highest priority input. When CLR is High, all other inputsare ignored; the Q outputs, terminal count (TC), and clock enable out (CEO) go to logic level zero, independentof clock transitions. The Q outputs increment when clock enable (CE) is High during the Low-to-High andHigh-to-Low clock (C) transition. The counter ignores clock transitions when CE is Low. The TC output isHigh when Q3 and Q0 are High and Q2 and Q1 are Low. The counter recovers to zero from any illegal statewithin the first clock cycle.
The counter recovers from any of six possible illegal states and returns to a normal count sequence within twoclock cycles for Xilinx® devices, as shown in the following state diagram:
Create larger counters by connecting the CEO output of each stage to the CE input of the next stage andconnecting the C and CLR inputs in parallel. CEO is active (High) when TC and CE are High. The maximumlength of the counter is determined by the accumulated CE-to-TC propagation delays versus the clock period.The clock period must be greater than n (tCE-TC), where n is the number of stages and the time tCE-TC is theCE-to-TC propagation delay of each stage. When cascading counters, use the CEO output if the counter uses theCE input or use the TC output if it does not.
This counter is asynchronously cleared, outputs Low, when power is applied. For CPLD devices, you cansimulate power-on by applying a High-level pulse on the PRLD global net.
CPLD Libraries Guide244 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
Logic TableInputs Outputs
CLR CE C Q3 Q2 Q1 Q0 TC CEO
1 X X 0 0 0 0 0 0
0 1 ↑ Inc Inc Inc Inc TC CEO
0 1 ↓ Inc Inc Inc Inc TC CEO
0 0 X No Change No Change No Change No Change TC 0
0 1 X 1 0 0 1 1 1
TC = Q3•!Q2•!Q1•Q0
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 245
Chapter 3: About Design Elements
CDD4CLEMacro: 4-Bit Loadable Cascadable Dual Edge Triggered BCD Counter with Clock Enable andAsynchronous Clear
Supported ArchitecturesThis design element is supported in the following architectures only:CoolRunner™-II
IntroductionCDD4CLE is a 4-bit (stage), synchronously loadable, asynchronously clearable, dual edge triggeredBinary-coded-decimal (BCD) counter. The asynchronous clear input (CLR) is the highest priority input. WhenCLR is High, all other inputs are ignored; the Q outputs, terminal count (TC), and clock enable out (CEO) go tologic level zero, independent of clock transitions. The data on the D inputs is loaded into the counter when theload enable input (L) is High during the Low-to-High and High-to-Low clock (C) transitions. The Q outputsincrement when clock enable input (CE) is High during the Low- to-High clock transition. The counter ignoresclock transitions when CE is Low. The TC output is High when Q3 and Q0 are High and Q2 and Q1 are Low. Thecounter recovers to zero from any illegal state within the first clock cycle.
The counter recovers from any of six possible illegal states and returns to a normal count sequence within twoclock cycles for Xilinx® devices, as shown in the following state diagram:
Create larger counters by connecting the CEO output of each stage to the CE input of the next stage andconnecting the C, L, and CLR inputs in parallel. CEO is active (High) when TC and CE are High. The maximumlength of the counter is determined by the accumulated CE-to-TC propagation delays versus the clock period.The clock period must be greater than n (tCE-TC), where n is the number of stages and the time tCE-TC is theCE-to-TC propagation delay of each stage. When cascading counters, use the CEO output if the counter uses theCE input or use the TC output if it does not.
This counter is asynchronously cleared, outputs Low, when power is applied. For CPLD devices, you cansimulate power-on by applying a High-level pulse on the PRLD global net.
CPLD Libraries Guide246 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
Logic TableInputs Outputs
CLR L CE D3 : D0 C Q3 Q2 Q1 Q0 TC CEO
1 X X X X 0 0 0 0 0 0
0 1 X D3 : D0 ↑ D3 D2 D1 D0 TC CEO
0 1 X D3 : D0 ↓ D3 D2 D1 D0 TC CEO
0 0 1 X ↑ Inc Inc Inc Inc TC CEO
0 0 1 X ↓ Inc Inc Inc Inc TC CEO
0 0 0 X X NoChange
NoChange
NoChange
NoChange
TC 0
0 0 1 X X 1 0 0 1 1 1
TC = Q3•!Q2•!Q1•Q0
CEO = TC•CE
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 247
Chapter 3: About Design Elements
CDD4REMacro: 4-Bit Cascadable Dual Edge Triggered BCD Counter with Clock Enable and SynchronousReset
Supported ArchitecturesThis design element is supported in the following architectures only:
CoolRunner™-II
IntroductionCDD4RE is a 4-bit (stage), synchronous resettable, cascadable dual edge triggered binary-coded-decimal(BCD) counter. The synchronous reset input (R) is the highest priority input. When R is High, all other inputsare ignored; the Q outputs, terminal count (TC), and clock enable out (CEO) go to logic level zero on theLow-to-High or High-to-Low clock (C) transition. The Q outputs increment when the clock enable input (CE) isHigh during the Low-to-High and High-to-Low clock transition. The counter ignores clock transitions whenCE is Low. The TC output is High when Q3 and Q0 are High and Q2 and Q1 are Low. The counter recovers tozero from any illegal state within the first clock cycle.
The counter recovers from any of six possible illegal states and returns to a normal count sequence within twoclock cycles for Xilinx® devices, as shown in the following state diagram:
Create larger counters by connecting the CEO output of each stage to the CE input of the next stage andconnecting the C and R inputs in parallel. CEO is active (High) when TC and CE are High. The maximum lengthof the counter is determined by the accumulated CE-to-TC propagation delays versus the clock period. Theclock period must be greater than n (tCE-TC), where n is the number of stages and the time tCE-TC is the CE-to-TCpropagation delay of each stage. When cascading counters, use the CEO output if the counter uses the CEinput or use the TC output if it does not.
This counter is asynchronously cleared, outputs Low, when power is applied. For CPLD devices, you cansimulate power-on by applying a High-level pulse on the PRLD global net.
CPLD Libraries Guide248 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
Logic TableInputs Outputs
R CE C Q3 Q2 Q1 Q0 TC CEO
1 X ↑ 0 0 0 0 0 0
1 X ↓ 0 0 0 0 0 0
0 1 ↑ Inc Inc Inc Inc TC CEO
0 1 ↓ Inc Inc Inc Inc TC CEO
0 0 X No Change No Change No Change No Change TC 0
0 1 X 1 0 0 1 1 1
TC = Q3•!Q2•!Q1•Q0
CEO = TC•CE
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 249
Chapter 3: About Design Elements
CDD4RLEMacro: 4-Bit Loadable Cascadable Dual Edge Triggered BCD Counter with Clock Enable andSynchronous Reset
Supported ArchitecturesThis design element is supported in the following architectures only:
CoolRunner™-II
IntroductionThis is a 4-bit (stage), synchronous loadable, resettable, dual edge triggered binary-coded-decimal (BCD) counter.The synchronous reset input (R) is the highest priority input. When R is High, all other inputs are ignored;the Q outputs, terminal count (TC), and clock enable out (CEO) go to logic level zero on the Low-to-High orHigh-to-Low clock transitions. The data on the D inputs is loaded into the counter when the load enable input(L) is High during the Low-to-High and High-to-Low clock (C) transition. The Q outputs increment when theclock enable input (CE) is High during the Low-to-High and High-to-Low clock transition. The counter ignoresclock transitions when CE is Low. The TC output is High when Q3 and Q0 are High and Q2 and Q1 are Low. Thecounter recovers to zero from any illegal state within the first clock cycle.
Larger counters are created by connecting the count enable out (CEO) output of the first stage to the CE input ofthe next stage and connecting the R, L, and C inputs in parallel. CEO is active (High) when TC and CE are High.The maximum length of the counter is determined by the accumulated CE-to-TC propagation delays versus theclock period. The clock period must be greater than n(tCE-TC), where n is the number of stages and the timetCE-TC is the CE-to-TC propagation delay of each stage. When cascading counters, use the CEO output if thecounter uses the CE input; use the TC output if it does not.
This counter is asynchronously cleared, outputs Low, when power is applied. For CPLD devices, you cansimulate power-on by applying a High-level pulse on the PRLD global net.
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries Guide250 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
CJ4CE4-Bit Johnson Counter with Clock Enable and Asynchronous Clear
Supported ArchitecturesThis design element is supported in the following architectures only:
• XC9500
• CoolRunner™ XPLA3
• CoolRunner-II
IntroductionThis design element is a clearable Johnson/shift counter. The asynchronous clear (CLR) input, when High,overrides all other inputs and forces the data (Q) outputs to logic level zero, independent of clock (C) transitions.The counter increments (shifts Q0 to Q1, Q1 to Q2,and so forth) when the clock enable input (CE) is High duringthe Low-to-High clock transition. Clock transitions are ignored when (CE) is Low.
The Q3 output is inverted and fed back to input Q0 to provide continuous counting operation.
This counter is asynchronously cleared, outputs Low, when power is applied.
Logic TableInputs Outputs
CLR CE C Q0 Q1 through Q3
1 X X 0 0
0 0 X No change No change
0 1 ↑ !q3 q0 through q2
q = state of referenced output one setup time prior to active clock transition
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 251
Chapter 3: About Design Elements
CJ4REMacro: 4-Bit Johnson Counter with Clock Enable and Synchronous Reset
Supported ArchitecturesThis design element is supported in the following architectures only:
• XC9500
• CoolRunner™ XPLA3
• CoolRunner-II
IntroductionThis design element is a resettable Johnson/shift counter. The synchronous reset (R) input, when High, overridesall other inputs and forces the data (Q) outputs to logic level zero during the Low-to-High clock (C) transition.The counter increments (shifts Q0 to Q1, Q1 to Q2, and so forth) when the clock enable input (CE) is High duringthe Low-to-High clock transition. Clock transitions are ignored when CE is Low.
The Q3 output is inverted and fed back to input Q0 to provide continuous counting operation.
This counter is asynchronously cleared, outputs Low, when power is applied.
Logic TableInputs Outputs
R CE C Q0 Q1 through Q3
1 X ↑ 0 0
0 0 X No change No change
0 1 ↑ !q3 q0 through q2
q = state of referenced output one setup time prior to active clock transition
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries Guide252 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
CJ5CEMacro: 5-Bit Johnson Counter with Clock Enable and Asynchronous Clear
Supported ArchitecturesThis design element is supported in the following architectures only:• XC9500• CoolRunner™ XPLA3• CoolRunner-II
IntroductionThis design element is a clearable Johnson/shift counter. The asynchronous clear (CLR) input, when High,overrides all other inputs and forces the data (Q) outputs to logic level zero, independent of clock (C) transitions.The counter increments (shifts Q0 to Q1, Q1 to Q2,and so forth) when the clock enable input (CE) is High duringthe Low-to-High clock transition. Clock transitions are ignored when (CE) is Low.
The Q4 output is inverted and fed back to input Q0 to provide continuous counting operation.
This counter is asynchronously cleared, outputs Low, when power is applied.
Logic TableInputs Outputs
CLR CE C Q0 Q1 through Q4
1 X X 0 0
0 0 X No change No change
0 1 ↑ !q4 q0 through q3
q = state of referenced output one setup time prior to active clock transition
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.• See the appropriate CPLD Data Sheets.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 253
Chapter 3: About Design Elements
CJ5REMacro: 5-Bit Johnson Counter with Clock Enable and Synchronous Reset
Supported ArchitecturesThis design element is supported in the following architectures only:• XC9500• CoolRunner™ XPLA3• CoolRunner-II
IntroductionThis design element is a resettable Johnson/shift counter. The synchronous reset (R) input, when High, overridesall other inputs and forces the data (Q) outputs to logic level zero during the Low-to-High clock (C) transition.The counter increments (shifts Q0 to Q1, Q1 to Q2, and so forth) when the clock enable input (CE) is High duringthe Low-to-High clock transition. Clock transitions are ignored when CE is Low.
The Q4 output is inverted and fed back to input Q0 to provide continuous counting operation.
This counter is asynchronously cleared, outputs Low, when power is applied.
Logic TableInputs Outputs
R CE C Q0 Q1 through Q4
1 X ↑ 0 0
0 0 X No change No change
0 1 ↑ !q4 q0 through q3
q = state of referenced output one setup time prior to active clock transition
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.• See the appropriate CPLD Data Sheets.
CPLD Libraries Guide254 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
CJ8CEMacro: 8-Bit Johnson Counter with Clock Enable and Asynchronous Clear
Supported ArchitecturesThis design element is supported in the following architectures only:
• XC9500
• CoolRunner™ XPLA3
• CoolRunner-II
IntroductionThis design element is a clearable Johnson/shift counter. The asynchronous clear (CLR) input, when High,overrides all other inputs and forces the data (Q) outputs to logic level zero, independent of clock (C) transitions.The counter increments (shifts Q0 to Q1, Q1 to Q2,and so forth) when the clock enable input (CE) is High duringthe Low-to-High clock transition. Clock transitions are ignored when (CE) is Low.
The Q7 output is inverted and fed back to input Q0 to provide continuous counting operation.
This counter is asynchronously cleared, outputs Low, when power is applied.
Logic TableInputs Outputs
CLR CE C Q0 Q1 through Q8
1 X X 0 0
0 0 X No change No change
0 1 ↑ !q7 q0 through q7
q = state of referenced output one setup time prior to active clock transition
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 255
Chapter 3: About Design Elements
CJ8REMacro: 8-Bit Johnson Counter with Clock Enable and Synchronous Reset
Supported ArchitecturesThis design element is supported in the following architectures only:
• XC9500
• CoolRunner™ XPLA3
• CoolRunner-II
IntroductionThis design element is a resettable Johnson/shift counter. The synchronous reset (R) input, when High, overridesall other inputs and forces the data (Q) outputs to logic level zero during the Low-to-High clock (C) transition.The counter increments (shifts Q0 to Q1, Q1 to Q2, and so forth) when the clock enable input (CE) is High duringthe Low-to-High clock transition. Clock transitions are ignored when CE is Low.
The Q7 output is inverted and fed back to input Q0 to provide continuous counting operation.
This counter is asynchronously cleared, outputs Low, when power is applied.
Logic TableInputs Outputs
R CE C Q0 Q1 through Q7
1 X ↑ 0 0
0 0 X No change No change
0 1 ↑ !q7 q0 through q6
q = state of referenced output one setup time prior to active clock transition
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries Guide256 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
CJD4CEMacro: 4-Bit Dual Edge Triggered Johnson Counter with Clock Enable and Asynchronous Clear
Supported ArchitecturesThis design element is supported in the following architectures only:
CoolRunner™-II
IntroductionThis element is a dual edge triggered clearable Johnson/shift counter. The asynchronous clear (CLR) input, whenHigh, overrides all other inputs and causes the data (Q) outputs to go to logic level zero independent of clock (C)transitions. The counter increments (shifts Q0 to Q1, Q1 to Q2,etc.) when the clock enable input (CE) is Highduring the Low-to-High and High-to-Low clock transition. Clock transitions are ignored when CE is Low.
The Q3 output is inverted and fed back to input Q0 to provide continuous counting operation.
This counter is asynchronously cleared, outputs Low, when power is applied. For CPLD devices, you cansimulate power-on by applying a High-level pulse on the PRLD global net.
Logic TableInputs Outputs
CLR CE C Q0 Q1 through Q3
1 X X 0 0
0 0 X No Change No Change
0 1 ↑ !q3 q0 through q2
0 1 ↓ !q3 q0 through q2
q = state of referenced output one setup time prior to active clock transition
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 257
Chapter 3: About Design Elements
CJD4REMacro: 4-Bit Dual Edge Triggered Johnson Counter with Clock Enable and Synchronous Reset
Supported ArchitecturesThis design element is supported in the following architectures only:CoolRunner™-II
IntroductionThis design element is a resettable dual edge triggered Johnson/shift counter. The synchronous reset (R) input,when High, overrides all other inputs and causes the data (Q) outputs to go to logic level zero during theLow-to-High and High-to-Low clock (C) transitions. The counter increments (shifts Q0 to Q1, Q1 to Q2, etc.)when the clock enable input (CE) is High during the Low-to-High and High-to-Low clock transition. Clocktransitions are ignored when CE is Low.
The Q3 output is inverted and fed back to input Q0 to provide continuous counting operation.
This counter is asynchronously cleared, outputs Low, when power is applied. For CPLD devices, you cansimulate power-on by applying a High-level pulse on the PRLD global net.
Logic TableInputs Outputs
R CE C Q0 Q1 : Q3
1 X ↑ 0 0
1 X ↓ 0 0
0 0 X No Change No Change
0 1 ↑ !q3 q0 : q2
0 1 ↓ !q3 q0 : q2
q = state of referenced output one setup time prior to active clock transition
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.• See the appropriate CPLD Data Sheets.
CPLD Libraries Guide258 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
CJD5CEMacro: 5-Bit Dual Edge Triggered Johnson Counter with Clock Enable and Asynchronous Clear
Supported ArchitecturesThis design element is supported in the following architectures only:CoolRunner™-II
IntroductionThis element is a dual edge triggered clearable Johnson/shift counter. The asynchronous clear (CLR) input, whenHigh, overrides all other inputs and causes the data (Q) outputs to go to logic level zero independent of clock (C)transitions. The counter increments (shifts Q0 to Q1, Q1 to Q2,etc.) when the clock enable input (CE) is Highduring the Low-to-High and High-to-Low clock transition. Clock transitions are ignored when CE is Low.
The Q4 output is inverted and fed back to input Q0 to provide continuous counting operation.
This counter is asynchronously cleared, outputs Low, when power is applied. For CPLD devices, you cansimulate power-on by applying a High-level pulse on the PRLD global net.
Logic TableInputs Outputs
CLR CE C Q0 Q1 through Q4
1 X X 0 0
0 0 X No Change No Change
0 1 ↑ !q4 q0 through q3
0 1 ↓ !q4 q0 through q3
q = state of referenced output one setup time prior to active clock transition
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.• See the appropriate CPLD Data Sheets.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 259
Chapter 3: About Design Elements
CJD5REMacro: 5-Bit Dual Edge Triggered Johnson Counter with Clock Enable and Synchronous Reset
Supported ArchitecturesThis design element is supported in the following architectures only:CoolRunner™-II
IntroductionThis design element is a resettable dual edge triggered Johnson/shift counter. The synchronous reset (R) input,when High, overrides all other inputs and causes the data (Q) outputs to go to logic level zero during theLow-to-High and High-to-Low clock (C) transitions. The counter increments (shifts Q0 to Q1, Q1 to Q2, etc.)when the clock enable input (CE) is High during the Low-to-High and High-to-Low clock transition. Clocktransitions are ignored when CE is Low.
The Q4 output is inverted and fed back to input Q0 to provide continuous counting operation.
This counter is asynchronously cleared, outputs Low, when power is applied. For CPLD devices, you cansimulate power-on by applying a High-level pulse on the PRLD global net.
Logic TableInputs Outputs
R CE C Q0 Q1 : Q4
1 X ↑ 0 0
1 X ↓ 0 0
0 0 X No Change No Change
0 1 ↑ !q4 q0 : q3
0 1 ↓ !q4 q0 : q3
q = state of referenced output one setup time prior to active clock transition
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.• See the appropriate CPLD Data Sheets.
CPLD Libraries Guide260 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
CJD8CEMacro: 8-Bit Dual Edge Triggered Johnson Counter with Clock Enable and Asynchronous Clear
Supported ArchitecturesThis design element is supported in the following architectures only:
CoolRunner™-II
IntroductionThis element is a dual edge triggered clearable Johnson/shift counter. The asynchronous clear (CLR) input, whenHigh, overrides all other inputs and causes the data (Q) outputs to go to logic level zero independent of clock (C)transitions. The counter increments (shifts Q0 to Q1, Q1 to Q2,etc.) when the clock enable input (CE) is Highduring the Low-to-High and High-to-Low clock transition. Clock transitions are ignored when CE is Low.
The Q7 output is inverted and fed back to input Q0 to provide continuous counting operation.
This counter is asynchronously cleared, outputs Low, when power is applied. For CPLD devices, you cansimulate power-on by applying a High-level pulse on the PRLD global net.
Logic TableInputs Outputs
CLR CE C Q0 Q1 through Q7
1 X X 0 0
0 0 X No Change No Change
0 1 ↑ !q7 q0 through q6
0 1 ↓ !q7 q0 through q6
q = state of referenced output one setup time prior to active clock transition
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 261
Chapter 3: About Design Elements
CJD8REMacro: 8-Bit Dual Edge Triggered Johnson Counter with Clock Enable and Synchronous Reset
Supported ArchitecturesThis design element is supported in the following architectures only:CoolRunner™-II
IntroductionThis design element is a resettable dual edge triggered Johnson/shift counter. The synchronous reset (R) input,when High, overrides all other inputs and causes the data (Q) outputs to go to logic level zero during theLow-to-High and High-to-Low clock (C) transitions. The counter increments (shifts Q0 to Q1, Q1 to Q2, etc.)when the clock enable input (CE) is High during the Low-to-High and High-to-Low clock transition. Clocktransitions are ignored when CE is Low.
The Q7 output is inverted and fed back to input Q0 to provide continuous counting operation.
This counter is asynchronously cleared, outputs Low, when power is applied. For CPLD devices, you cansimulate power-on by applying a High-level pulse on the PRLD global net.
Logic TableInputs Outputs
R CE C Q0 Q1 : Q7
1 X ↑ 0 0
1 X ↓ 0 0
0 0 X No Change No Change
0 1 ↑ !q7 q0 : q6
0 1 ↓ !q7 q0 : q6
q = state of referenced output one setup time prior to active clock transition
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.• See the appropriate CPLD Data Sheets.
CPLD Libraries Guide262 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
CLK_DIV10Primitive: Simple Global Clock Divide by 10
Supported ArchitecturesThis design element is supported in the following architectures only:CoolRunner™-II
IntroductionThis design element divides a user-provided external clock signal gclk<2> by 10.
Only one clock divider may be used per design. The global clock divider is available on the XC2C128, XC2C256,XC2C384, and XC2C512 CoolRunner-II devices, but not the XC2C32 or XC2C64. The CLKIN input can onlybe connected to the device gclk<2> pin. The duty cycle of the CLKDV output is 50-50. The CLKDV output canonly connect to clock inputs of synchronous elements. It cannot be used as combinatorial logic, and shouldnot be routed directly to an output pin.
The CLKDV output is reset low by power-on reset circuitry.
Design Entry MethodThis design element can be used in schematics.
VHDL Instantiation TemplateUnless they already exist, copy the following two statements and paste them before the entity declaration.
Library UNISIM;use UNISIM.vcomponents.all;
-- CLK_DIV10: Simple Clock Divide by 10-- CoolRunner-II-- Xilinx HDL Language Template, version 10.1
CLK_DIV10_inst : CLK_DIV10port map (
CLKDV => CLKDV, -- Divided clock outputCLKIN => CLKIN -- Clock input
);
-- End of CLK_DIV10_inst instantiation
Verilog Instantiation Template// CLK_DIV10: Simple Clock Divide by 10// CoolRunner-II// Xilinx HDL Language Template, version 10.1
CLK_DIV10 CLK_DIV10_inst (.CLKDV(CLKDV), // Divided clock output.CLKIN(CLKIN) // Clock input
);
// End of CLK_DIV10_inst instantiation
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 263
Chapter 3: About Design Elements
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries Guide264 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
CLK_DIV10RPrimitive: Global Clock Divide by 10 with Synchronous Reset
Supported ArchitecturesThis design element is supported in the following architectures only:
CoolRunner™-II
IntroductionThis design element divides a user-provided external clock signal gclk<2> by 10.
Only one clock divider may be used per design. The global clock divider is available on the XC2C128, XC2C256,XC2C384, and XC2C512 CoolRunner™-II devices, but not the XC2C32 or XC2C64. The CLKIN and CDRSTinputs can only be connected to the device gclk<2> and CDRST pins. The duty cycle of the CLKDV output is50-50. The CLKDV output can only connect to clock inputs of synchronous elements. It cannot be used ascombinatorial logic, and should not be routed directly to an output pin.
The CDRST input is an active High synchronous reset. If CDRST is input High when the CLKDV output is High,the CLKDV output remains High to complete the last clock pulse, and then goes Low.
The CLKDV output is reset low by power-on reset circuitry.
Design Entry MethodThis design element can be used in schematics.
VHDL Instantiation TemplateUnless they already exist, copy the following two statements and paste them before the entity declaration.
Library UNISIM;use UNISIM.vcomponents.all;
-- CLK_DIV10R: Clock Divide by 10 with Synchronous Reset-- CoolRunner-II-- Xilinx HDL Language Template, version 10.1
CLK_DIV10R_inst : CLK_DIV10Rport map (
CLKDV => CLKDV, -- Divided clock outputCDRST => CDRST, -- Synchronous reset inputCLKIN => CLKIN -- Clock input
);
-- End of CLK_DIV10R_inst instantiation
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 265
Chapter 3: About Design Elements
Verilog Instantiation Template// CLK_DIV10R: Clock Divide by 10 with Synchronous Reset// CoolRunner-II// Xilinx HDL Language Template, version 10.1
CLK_DIV10R CLK_DIV10R_inst (.CLKDV(CLKDV), // Divided clock output.CDRST(CDRST), // Synchronous reset input.CLKIN(CLKIN) // Clock input
);
// End of CLK_DIV10R_inst instantiation
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries Guide266 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
CLK_DIV10RSDPrimitive: Global Clock Divide by 10 with Synchronous Reset and Start Delay
Supported ArchitecturesThis design element is supported in the following architectures only:CoolRunner™-II
IntroductionThis design element divides a user-provided external clock signal gclk<2> by 10.
Only one clock divider may be used per design. The global clock divider is available on the XC2C128, XC2C256,XC2C384, and XC2C512 CoolRunner™-II devices, but not the XC2C32 or XC2C64. The CLKIN and CDRSTinputs can only be connected to the device gclk<2> and CDRST pins. The duty cycle of the CLKDV output is50-50. The CLKDV output can only connect to clock inputs of synchronous elements. It cannot be used ascombinatorial logic, and should not be routed directly to an output pin.
The CDRST input is an active High synchronous reset. If CDRST is input High when the CLKDV output is High,the CLKDV output remains High to complete the last clock pulse, and then goes Low.
The start delay function delays the start of the CLKDV output by (n + 1) clocks, where n is the divisor forthe clock divider.
The CLKDV output is reset low by power-on reset circuitry.
Design Entry MethodThis design element can be used in schematics.
VHDL Instantiation TemplateUnless they already exist, copy the following two statements and paste them before the entity declaration.
Library UNISIM;use UNISIM.vcomponents.all;
-- CLK_DIV10RSD: Clock Divide by 10 with Synchronous Reset and Start-- Delay-- CoolRunner-II-- Xilinx HDL Language Template, version 10.1
CLK_DIV10RSD_inst : CLK_DIV10RSD-- Edit the following generic to specify the number of clock cycles-- to delay before starting.generic map (
DIVIDER_DELAY => 1)port map (
CLKDV => CLKDV, -- Divided clock outputCDRST => CDRST, -- Synchronous reset inputCLKIN => CLKIN -- Clock input
);
-- End of CLK_DIV10RSD_inst instantiation
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 267
Chapter 3: About Design Elements
Verilog Instantiation Template// CLK_DIV12RSD: Clock Divide by 12 with Synchronous Reset and Start// Delay// CoolRunner-II// Xilinx HDL Language Template, version 10.1
CLK_DIV12RSD CLK_DIV12RSD_inst (.CLKDV(CLKDV), // Divided clock output.CDRST(CDRST), // Synchronous reset input.CLKIN(CLKIN) // Clock input
);
// Edit the following defparam to specify the number of clock// cycles to delay before starting. If the instance name to// the clock divider is changed, that change needs to be// reflected in the defparam statements.
defparam CLK_DIV12RSD_inst.DIVIDER_DELAY = 1;
// End of CLK_DIV12RSD_inst instantiation
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries Guide268 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
CLK_DIV10SDPrimitive: Global Clock Divide by 10 with Start Delay
Supported ArchitecturesThis design element is supported in the following architectures only:
CoolRunner™-II
IntroductionThis design element divides a user-provided external clock signal gclk<2> by 10.
Only one clock divider may be used per design. The global clock divider is available on the XC2C128, XC2C256,XC2C384, and XC2C512 CoolRunner-II devices, but not the XC2C32 or XC2C64. The CLKIN input can onlybe connected to the device gclk<2> pin. The duty cycle of the CLKDV output is 50-50. The CLKDV output canonly connect to clock inputs of synchronous elements. It cannot be used as combinatorial logic, and shouldnot be routed directly to an output pin.
The start delay function delays the start of the CLKDV output by (n + 1) clocks, where n is the divisor forthe clock divider.
The CLKDV output is reset low by power-on reset circuitry.
Design Entry MethodThis design element can be used in schematics.
VHDL Instantiation TemplateUnless they already exist, copy the following two statements and paste them before the entity declaration.
Library UNISIM;use UNISIM.vcomponents.all;
-- CLK_DIV10SD: Clock Divide by 10 with Start Delay-- CoolRunner-II-- Xilinx HDL Language Template, version 10.1
CLK_DIV10SD_inst : CLK_DIV10SD-- Edit the following generic to specify the number of clock cycles-- to delay before starting.generic map (
DIVIDER_DELAY => 1)port map (
CLKDV => CLKDV, -- Divided clock outputCLKIN => CLKIN -- Clock input
);
-- End of CLK_DIV10SD_inst instantiation
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 269
Chapter 3: About Design Elements
Verilog Instantiation Template// CLK_DIV10SD: Clock Divide by 10 with Start Delay// CoolRunner-II// Xilinx HDL Language Template, version 10.1
CLK_DIV10SD CLK_DIV10SD_inst (.CLKDV(CLKDV), // Divided clock output.CDRST(CDRST), // Synchronous reset input.CLKIN(CLKIN) // Clock input
);
// Edit the following defparam to specify the number of clock// cycles to delay before starting. If the instance name to// the clock divider is changed, that change needs to be// reflected in the defparam statements.
defparam CLK_DIV10SD_inst.DIVIDER_DELAY = 1;
// End of CLK_DIV10SD_inst instantiation
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries Guide270 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
CLK_DIV12Primitive: Simple Global Clock Divide by 12
Supported ArchitecturesThis design element is supported in the following architectures only:CoolRunner™-II
IntroductionThis design element divides a user-provided external clock signal gclk<2> by 12.
Only one clock divider may be used per design. The global clock divider is available on the XC2C128, XC2C256,XC2C384, and XC2C512 CoolRunner-II devices, but not the XC2C32 or XC2C64. The CLKIN input can onlybe connected to the device gclk<2> pin. The duty cycle of the CLKDV output is 50-50. The CLKDV output canonly connect to clock inputs of synchronous elements. It cannot be used as combinatorial logic, and shouldnot be routed directly to an output pin.
The CLKDV output is reset low by power-on reset circuitry.
Design Entry MethodThis design element can be used in schematics.
VHDL Instantiation TemplateUnless they already exist, copy the following two statements and paste them before the entity declaration.
Library UNISIM;use UNISIM.vcomponents.all;
-- CLK_DIV12: Simple Clock Divide by 12-- CoolRunner-II-- Xilinx HDL Language Template, version 10.1
CLK_DIV12_inst : CLK_DIV12port map (
CLKDV => CLKDV, -- Divided clock outputCLKIN => CLKIN -- Clock input
);
-- End of CLK_DIV12_inst instantiation
Verilog Instantiation Template// CLK_DIV12: Simple Clock Divide by 12// CoolRunner-II// Xilinx HDL Language Template, version 10.1
CLK_DIV12 CLK_DIV12_inst (.CLKDV(CLKDV), // Divided clock output.CLKIN(CLKIN) // Clock input
);
// End of CLK_DIV12_inst instantiation
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 271
Chapter 3: About Design Elements
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries Guide272 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
CLK_DIV12RPrimitive: Global Clock Divide by 12 with Synchronous Reset
Supported ArchitecturesThis design element is supported in the following architectures only:
CoolRunner™-II
IntroductionThis design element divides a user-provided external clock signal gclk<2> by 12.
Only one clock divider may be used per design. The global clock divider is available on the XC2C128, XC2C256,XC2C384, and XC2C512 CoolRunner™-II devices, but not the XC2C32 or XC2C64. The CLKIN and CDRSTinputs can only be connected to the device gclk<2> and CDRST pins. The duty cycle of the CLKDV output is50-50. The CLKDV output can only connect to clock inputs of synchronous elements. It cannot be used ascombinatorial logic, and should not be routed directly to an output pin.
The CDRST input is an active High synchronous reset. If CDRST is input High when the CLKDV output is High,the CLKDV output remains High to complete the last clock pulse, and then goes Low.
The CLKDV output is reset low by power-on reset circuitry.
Design Entry MethodThis design element can be used in schematics.
VHDL Instantiation TemplateUnless they already exist, copy the following two statements and paste them before the entity declaration.
Library UNISIM;use UNISIM.vcomponents.all;
-- CLK_DIV12R: Clock Divide by 12 with Synchronous Reset-- CoolRunner-II-- Xilinx HDL Language Template, version 10.1
CLK_DIV12R_inst : CLK_DIV12Rport map (
CLKDV => CLKDV, -- Divided clock outputCDRST => CDRST, -- Synchronous reset inputCLKIN => CLKIN -- Clock input
);
-- End of CLK_DIV12R_inst instantiation
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 273
Chapter 3: About Design Elements
Verilog Instantiation Template// CLK_DIV12R: Clock Divide by 12 with Synchronous Reset// CoolRunner-II// Xilinx HDL Language Template, version 10.1
CLK_DIV12R CLK_DIV12R_inst (.CLKDV(CLKDV), // Divided clock output.CDRST(CDRST), // Synchronous reset input.CLKIN(CLKIN) // Clock input
);
// End of CLK_DIV12R_inst instantiation
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries Guide274 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
CLK_DIV12RSDPrimitive: Global Clock Divide by 12 with Synchronous Reset and Start Delay
Supported ArchitecturesThis design element is supported in the following architectures only:CoolRunner™-II
IntroductionThis design element divides a user-provided external clock signal gclk<2> by 12.
Only one clock divider may be used per design. The global clock divider is available on the XC2C128, XC2C256,XC2C384, and XC2C512 CoolRunner™-II devices, but not the XC2C32 or XC2C64. The CLKIN and CDRSTinputs can only be connected to the device gclk<2> and CDRST pins. The duty cycle of the CLKDV output is50-50. The CLKDV output can only connect to clock inputs of synchronous elements. It cannot be used ascombinatorial logic, and should not be routed directly to an output pin.
The CDRST input is an active High synchronous reset. If CDRST is input High when the CLKDV output is High,the CLKDV output remains High to complete the last clock pulse, and then goes Low.
The start delay function delays the start of the CLKDV output by (n + 1) clocks, where n is the divisor forthe clock divider.
The CLKDV output is reset low by power-on reset circuitry.
Design Entry MethodThis design element can be used in schematics.
VHDL Instantiation TemplateUnless they already exist, copy the following two statements and paste them before the entity declaration.
Library UNISIM;use UNISIM.vcomponents.all;
-- CLK_DIV12RSD: Clock Divide by 12 with Synchronous Reset and Start-- Delay-- CoolRunner-II-- Xilinx HDL Language Template, version 10.1
CLK_DIV12RSD_inst : CLK_DIV12RSD-- Edit the following generic to specify the number of clock cycles-- to delay before starting.generic map (
DIVIDER_DELAY => 1)port map (
CLKDV => CLKDV, -- Divided clock outputCDRST => CDRST, -- Synchronous reset inputCLKIN => CLKIN -- Clock input
);
-- End of CLK_DIV12RSD_inst instantiation
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 275
Chapter 3: About Design Elements
Verilog Instantiation Template// CLK_DIV12RSD: Clock Divide by 12 with Synchronous Reset and Start// Delay// CoolRunner-II// Xilinx HDL Language Template, version 10.1
CLK_DIV12RSD CLK_DIV12RSD_inst (.CLKDV(CLKDV), // Divided clock output.CDRST(CDRST), // Synchronous reset input.CLKIN(CLKIN) // Clock input
);
// Edit the following defparam to specify the number of clock// cycles to delay before starting. If the instance name to// the clock divider is changed, that change needs to be// reflected in the defparam statements.
defparam CLK_DIV12RSD_inst.DIVIDER_DELAY = 1;
// End of CLK_DIV12RSD_inst instantiation
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries Guide276 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
CLK_DIV12SDPrimitive: Global Clock Divide by 12 with Start Delay
Supported ArchitecturesThis design element is supported in the following architectures only:
CoolRunner™-II
IntroductionThis design element divides a user-provided external clock signal gclk<2> by 12.
Only one clock divider may be used per design. The global clock divider is available on the XC2C128, XC2C256,XC2C384, and XC2C512 CoolRunner-II devices, but not the XC2C32 or XC2C64. The CLKIN input can onlybe connected to the device gclk<2> pin. The duty cycle of the CLKDV output is 50-50. The CLKDV output canonly connect to clock inputs of synchronous elements. It cannot be used as combinatorial logic, and shouldnot be routed directly to an output pin.
The start delay function delays the start of the CLKDV output by (n + 1) clocks, where n is the divisor forthe clock divider.
The CLKDV output is reset low by power-on reset circuitry.
Design Entry MethodThis design element can be used in schematics.
VHDL Instantiation TemplateUnless they already exist, copy the following two statements and paste them before the entity declaration.
Library UNISIM;use UNISIM.vcomponents.all;
-- CLK_DIV12SD: Clock Divide by 12 with Start Delay-- CoolRunner-II-- Xilinx HDL Language Template, version 10.1
CLK_DIV12SD_inst : CLK_DIV12SD-- Edit the following generic to specify the number of clock cycles-- to delay before starting.generic map (
DIVIDER_DELAY => 1)port map (
CLKDV => CLKDV, -- Divided clock outputCLKIN => CLKIN -- Clock input
);
-- End of CLK_DIV12SD_inst instantiation
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 277
Chapter 3: About Design Elements
Verilog Instantiation Template// CLK_DIV12SD: Clock Divide by 12 with Start Delay// CoolRunner-II// Xilinx HDL Language Template, version 10.1
CLK_DIV12SD CLK_DIV12SD_inst (.CLKDV(CLKDV), // Divided clock output.CDRST(CDRST), // Synchronous reset input.CLKIN(CLKIN) // Clock input
);
// Edit the following defparam to specify the number of clock// cycles to delay before starting. If the instance name to// the clock divider is changed, that change needs to be// reflected in the defparam statements.
defparam CLK_DIV12SD_inst.DIVIDER_DELAY = 1;
// End of CLK_DIV12SD_inst instantiation
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries Guide278 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
CLK_DIV14RPrimitive: Global Clock Divide by 14 with Synchronous Reset
Supported ArchitecturesThis design element is supported in the following architectures only:
CoolRunner™-II
IntroductionThis design element divides a user-provided external clock signal gclk<2> by 14.
Only one clock divider may be used per design. The global clock divider is available on the XC2C128, XC2C256,XC2C384, and XC2C512 CoolRunner™-II devices, but not the XC2C32 or XC2C64. The CLKIN and CDRSTinputs can only be connected to the device gclk<2> and CDRST pins. The duty cycle of the CLKDV output is50-50. The CLKDV output can only connect to clock inputs of synchronous elements. It cannot be used ascombinatorial logic, and should not be routed directly to an output pin.
The CDRST input is an active High synchronous reset. If CDRST is input High when the CLKDV output is High,the CLKDV output remains High to complete the last clock pulse, and then goes Low.
The CLKDV output is reset low by power-on reset circuitry.
Design Entry MethodThis design element can be used in schematics.
VHDL Instantiation TemplateUnless they already exist, copy the following two statements and paste them before the entity declaration.
Library UNISIM;use UNISIM.vcomponents.all;
-- CLK_DIV14R: Clock Divide by 14 with Synchronous Reset-- CoolRunner-II-- Xilinx HDL Language Template, version 10.1
CLK_DIV14R_inst : CLK_DIV14Rport map (
CLKDV => CLKDV, -- Divided clock outputCDRST => CDRST, -- Synchronous reset inputCLKIN => CLKIN -- Clock input
);
-- End of CLK_DIV14R_inst instantiation
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 279
Chapter 3: About Design Elements
Verilog Instantiation Template// CLK_DIV14R: Clock Divide by 14 with Synchronous Reset// CoolRunner-II// Xilinx HDL Language Template, version 10.1
CLK_DIV14R CLK_DIV14R_inst (.CLKDV(CLKDV), // Divided clock output.CDRST(CDRST), // Synchronous reset input.CLKIN(CLKIN) // Clock input
);
// End of CLK_DIV14R_inst instantiation
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries Guide280 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
CLK_DIV14RSDPrimitive: Global Clock Divide by 14 with Synchronous Reset and Start Delay
Supported ArchitecturesThis design element is supported in the following architectures only:CoolRunner™-II
IntroductionThis design element divides a user-provided external clock signal gclk<2> by 14.
Only one clock divider may be used per design. The global clock divider is available on the XC2C128, XC2C256,XC2C384, and XC2C512 CoolRunner™-II devices, but not the XC2C32 or XC2C64. The CLKIN and CDRSTinputs can only be connected to the device gclk<2> and CDRST pins. The duty cycle of the CLKDV output is50-50. The CLKDV output can only connect to clock inputs of synchronous elements. It cannot be used ascombinatorial logic, and should not be routed directly to an output pin.
The CDRST input is an active High synchronous reset. If CDRST is input High when the CLKDV output is High,the CLKDV output remains High to complete the last clock pulse, and then goes Low.
The start delay function delays the start of the CLKDV output by (n + 1) clocks, where n is the divisor forthe clock divider.
The CLKDV output is reset low by power-on reset circuitry.
Design Entry MethodThis design element can be used in schematics.
VHDL Instantiation TemplateUnless they already exist, copy the following two statements and paste them before the entity declaration.
Library UNISIM;use UNISIM.vcomponents.all;
-- CLK_DIV14RSD: Clock Divide by 14 with Synchronous Reset and Start-- Delay-- CoolRunner-II-- Xilinx HDL Language Template, version 10.1
CLK_DIV14RSD_inst : CLK_DIV14RSD-- Edit the following generic to specify the number of clock cycles-- to delay before starting.generic map (
DIVIDER_DELAY => 1)port map (
CLKDV => CLKDV, -- Divided clock outputCDRST => CDRST, -- Synchronous reset inputCLKIN => CLKIN -- Clock input
);
-- End of CLK_DIV14RSD_inst instantiation
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 281
Chapter 3: About Design Elements
Verilog Instantiation Template// CLK_DIV14RSD: Clock Divide by 14 with Synchronous Reset and Start// Delay// CoolRunner-II// Xilinx HDL Language Template, version 10.1
CLK_DIV14RSD CLK_DIV14RSD_inst (.CLKDV(CLKDV), // Divided clock output.CDRST(CDRST), // Synchronous reset input.CLKIN(CLKIN) // Clock input
);
// Edit the following defparam to specify the number of clock// cycles to delay before starting. If the instance name to// the clock divider is changed, that change needs to be// reflected in the defparam statements.
defparam CLK_DIV14RSD_inst.DIVIDER_DELAY = 1;
// End of CLK_DIV14RSD_inst instantiation
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries Guide282 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
CLK_DIV14SDPrimitive: Global Clock Divide by 14 with Start Delay
Supported ArchitecturesThis design element is supported in the following architectures only:
CoolRunner™-II
IntroductionThis design element divides a user-provided external clock signal gclk<2> by 14.
Only one clock divider may be used per design. The global clock divider is available on the XC2C128, XC2C256,XC2C384, and XC2C512 CoolRunner-II devices, but not the XC2C32 or XC2C64. The CLKIN input can onlybe connected to the device gclk<2> pin. The duty cycle of the CLKDV output is 50-50. The CLKDV output canonly connect to clock inputs of synchronous elements. It cannot be used as combinatorial logic, and shouldnot be routed directly to an output pin.
The start delay function delays the start of the CLKDV output by (n + 1) clocks, where n is the divisor forthe clock divider.
The CLKDV output is reset low by power-on reset circuitry.
Design Entry MethodThis design element can be used in schematics.
VHDL Instantiation TemplateUnless they already exist, copy the following two statements and paste them before the entity declaration.
Library UNISIM;use UNISIM.vcomponents.all;
-- CLK_DIV14SD: Clock Divide by 14 with Start Delay-- CoolRunner-II-- Xilinx HDL Language Template, version 10.1
CLK_DIV14SD_inst : CLK_DIV14SD-- Edit the following generic to specify the number of clock cycles-- to delay before starting.generic map (
DIVIDER_DELAY => 1)port map (
CLKDV => CLKDV, -- Divided clock outputCLKIN => CLKIN -- Clock input
);
-- End of CLK_DIV14SD_inst instantiation
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 283
Chapter 3: About Design Elements
Verilog Instantiation Template// CLK_DIV14SD: Clock Divide by 14 with Start Delay// CoolRunner-II// Xilinx HDL Language Template, version 10.1
CLK_DIV14SD CLK_DIV14SD_inst (.CLKDV(CLKDV), // Divided clock output.CDRST(CDRST), // Synchronous reset input.CLKIN(CLKIN) // Clock input
);
// Edit the following defparam to specify the number of clock// cycles to delay before starting. If the instance name to// the clock divider is changed, that change needs to be// reflected in the defparam statements.
defparam CLK_DIV14SD_inst.DIVIDER_DELAY = 1;
// End of CLK_DIV14SD_inst instantiation
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries Guide284 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
CLK_DIV16Primitive: Simple Global Clock Divide by 16
Supported ArchitecturesThis design element is supported in the following architectures only:
CoolRunner™-II
IntroductionThis design element divides a user-provided external clock signal gclk<2> by 16.
Only one clock divider may be used per design. The global clock divider is available on the XC2C128, XC2C256,XC2C384, and XC2C512 CoolRunner-II devices, but not the XC2C32 or XC2C64. The CLKIN input can onlybe connected to the device gclk<2> pin. The duty cycle of the CLKDV output is 50-50. The CLKDV output canonly connect to clock inputs of synchronous elements. It cannot be used as combinatorial logic, and shouldnot be routed directly to an output pin.
When using this component, the dedicated clock divider reset pin on the device is reserved and may not beused by user logic.
The CLKDV output is reset low by power-on reset circuitry.
Design Entry MethodThis design element can be used in schematics.
VHDL Instantiation TemplateUnless they already exist, copy the following two statements and paste them before the entity declaration.
Library UNISIM;use UNISIM.vcomponents.all;
-- CLK_DIV16: Simple Clock Divide by 16-- CoolRunner-II-- Xilinx HDL Language Template, version 10.1
CLK_DIV16_inst : CLK_DIV16port map (
CLKDV => CLKDV, -- Divided clock outputCLKIN => CLKIN -- Clock input
);
-- End of CLK_DIV16_inst instantiation
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 285
Chapter 3: About Design Elements
Verilog Instantiation Template// CLK_DIV16: Simple Clock Divide by 16// CoolRunner-II// Xilinx HDL Language Template, version 10.1
CLK_DIV16 CLK_DIV16_inst (.CLKDV(CLKDV), // Divided clock output.CLKIN(CLKIN) // Clock input
);
// End of CLK_DIV16_inst instantiation
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries Guide286 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
CLK_DIV16RPrimitive: Global Clock Divide by 16 with Synchronous Reset
Supported ArchitecturesThis design element is supported in the following architectures only:
CoolRunner™-II
IntroductionThis design element divides a user-provided external clock signal gclk<2> by 16.
Only one clock divider may be used per design. The global clock divider is available on the XC2C128, XC2C256,XC2C384, and XC2C512 CoolRunner™-II devices, but not the XC2C32 or XC2C64. The CLKIN and CDRSTinputs can only be connected to the device gclk<2> and CDRST pins. The duty cycle of the CLKDV output is50-50. The CLKDV output can only connect to clock inputs of synchronous elements. It cannot be used ascombinatorial logic, and should not be routed directly to an output pin.
The CDRST input is an active High synchronous reset. If CDRST is input High when the CLKDV output is High,the CLKDV output remains High to complete the last clock pulse, and then goes Low.
The CLKDV output is reset low by power-on reset circuitry.
Design Entry MethodThis design element can be used in schematics.
VHDL Instantiation TemplateUnless they already exist, copy the following two statements and paste them before the entity declaration.
Library UNISIM;use UNISIM.vcomponents.all;
-- CLK_DIV16R: Clock Divide by 16 with Synchronous Reset-- CoolRunner-II-- Xilinx HDL Language Template, version 10.1
CLK_DIV16R_inst : CLK_DIV16Rport map (
CLKDV => CLKDV, -- Divided clock outputCDRST => CDRST, -- Synchronous reset inputCLKIN => CLKIN -- Clock input
);
-- End of CLK_DIV16R_inst instantiation
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 287
Chapter 3: About Design Elements
Verilog Instantiation Template// CLK_DIV16R: Clock Divide by 16 with Synchronous Reset// CoolRunner-II// Xilinx HDL Language Template, version 10.1
CLK_DIV16R CLK_DIV16R_inst (.CLKDV(CLKDV), // Divided clock output.CDRST(CDRST), // Synchronous reset input.CLKIN(CLKIN) // Clock input
);
// End of CLK_DIV16_inst instantiation
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries Guide288 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
CLK_DIV16RSDPrimitive: Global Clock Divide by 16 with Synchronous Reset and Start Delay
Supported ArchitecturesThis design element is supported in the following architectures only:CoolRunner™-II
IntroductionThis design element divides a user-provided external clock signal gclk<2> by 16.
Only one clock divider may be used per design. The global clock divider is available on the XC2C128, XC2C256,XC2C384, and XC2C512 CoolRunner™-II devices, but not the XC2C32 or XC2C64. The CLKIN and CDRSTinputs can only be connected to the device gclk<2> and CDRST pins. The duty cycle of the CLKDV output is50-50. The CLKDV output can only connect to clock inputs of synchronous elements. It cannot be used ascombinatorial logic, and should not be routed directly to an output pin.
The CDRST input is an active High synchronous reset. If CDRST is input High when the CLKDV output is High,the CLKDV output remains High to complete the last clock pulse, and then goes Low.
The start delay function delays the start of the CLKDV output by (n + 1) clocks, where n is the divisor forthe clock divider.
The CLKDV output is reset low by power-on reset circuitry.
Design Entry MethodThis design element can be used in schematics.
VHDL Instantiation TemplateUnless they already exist, copy the following two statements and paste them before the entity declaration.
Library UNISIM;use UNISIM.vcomponents.all;
-- CLK_DIV16RSD: Clock Divide by 16 with Synchronous Reset and Start-- Delay-- CoolRunner-II-- Xilinx HDL Language Template, version 10.1
CLK_DIV16RSD_inst : CLK_DIV16RSD-- Edit the following generic to specify the number of clock cycles-- to delay before starting.generic map (
DIVIDER_DELAY => 1)port map (
CLKDV => CLKDV, -- Divided clock outputCDRST => CDRST, -- Synchronous reset inputCLKIN => CLKIN -- Clock input
);
-- End of CLK_DIV16RSD_inst instantiation
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 289
Chapter 3: About Design Elements
Verilog Instantiation Template// CLK_DIV16RSD: Clock Divide by 16 with Synchronous Reset and Start// Delay// CoolRunner-II// Xilinx HDL Language Template, version 10.1
CLK_DIV16RSD CLK_DIV16RSD_inst (.CLKDV(CLKDV), // Divided clock output.CDRST(CDRST), // Synchronous reset input.CLKIN(CLKIN) // Clock input
);
// Edit the following defparam to specify the number of clock// cycles to delay before starting. If the instance name to// the clock divider is changed, that change needs to be// reflected in the defparam statements.
defparam CLK_DIV16RSD_inst.DIVIDER_DELAY = 1;
// End of CLK_DIV16RSD_inst instantiation
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries Guide290 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
CLK_DIV16SDPrimitive: Global Clock Divide by 16 with Start Delay
Supported ArchitecturesThis design element is supported in the following architectures only:
CoolRunner™-II
IntroductionThis design element divides a user-provided external clock signal gclk<2> by 16.
Only one clock divider may be used per design. The global clock divider is available on the XC2C128, XC2C256,XC2C384, and XC2C512 CoolRunner-II devices, but not the XC2C32 or XC2C64. The CLKIN input can onlybe connected to the device gclk<2> pin. The duty cycle of the CLKDV output is 50-50. The CLKDV output canonly connect to clock inputs of synchronous elements. It cannot be used as combinatorial logic, and shouldnot be routed directly to an output pin.
The start delay function delays the start of the CLKDV output by (n + 1) clocks, where n is the divisor forthe clock divider.
The CLKDV output is reset low by power-on reset circuitry.
Design Entry MethodThis design element can be used in schematics.
VHDL Instantiation TemplateUnless they already exist, copy the following two statements and paste them before the entity declaration.
Library UNISIM;use UNISIM.vcomponents.all;
-- CLK_DIV16SD: Clock Divide by 16 with Start Delay-- CoolRunner-II-- Xilinx HDL Language Template, version 10.1
CLK_DIV16SD_inst : CLK_DIV16SD-- Edit the following generic to specify the number of clock cycles-- to delay before starting.generic map (
DIVIDER_DELAY => 1)port map (
CLKDV => CLKDV, -- Divided clock outputCLKIN => CLKIN -- Clock input
);
-- End of CLK_DIV16SD_inst instantiation
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 291
Chapter 3: About Design Elements
Verilog Instantiation Template// CLK_DIV16SD: Clock Divide by 16 with Start Delay// CoolRunner-II// Xilinx HDL Language Template, version 10.1
CLK_DIV16SD CLK_DIV16SD_inst (.CLKDV(CLKDV), // Divided clock output.CDRST(CDRST), // Synchronous reset input.CLKIN(CLKIN) // Clock input
);
// Edit the following defparam to specify the number of clock// cycles to delay before starting. If the instance name to// the clock divider is changed, that change needs to be// reflected in the defparam statements.
defparam CLK_DIV16SD_inst.DIVIDER_DELAY = 1;
// End of CLK_DIV16SD_inst instantiation
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries Guide292 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
CLK_DIV2Primitive: Simple Global Clock Divide by 2
Supported ArchitecturesThis design element is supported in the following architectures only:CoolRunner™-II
IntroductionThis design element divides a user-provided external clock signal gclk<2> by 2.
Only one clock divider may be used per design. The global clock divider is available on the XC2C128, XC2C256,XC2C384, and XC2C512 CoolRunner-II devices, but not the XC2C32 or XC2C64. The CLKIN input can onlybe connected to the device gclk<2> pin. The duty cycle of the CLKDV output is 50-50. The CLKDV output canonly connect to clock inputs of synchronous elements. It cannot be used as combinatorial logic, and shouldnot be routed directly to an output pin.
The CLKDV output is reset low by power-on reset circuitry.
Design Entry MethodThis design element can be used in schematics.
VHDL Instantiation TemplateUnless they already exist, copy the following two statements and paste them before the entity declaration.
Library UNISIM;use UNISIM.vcomponents.all;
-- CLK_DIV2: Simple Clock Divide by 2-- CoolRunner-II-- Xilinx HDL Language Template, version 10.1
CLK_DIV2_inst : CLK_DIV2port map (
CLKDV => CLKDV, -- Divided clock outputCLKIN => CLKIN -- Clock input
);
-- End of CLK_DIV2_inst instantiation
Verilog Instantiation Template// CLK_DIV2: Simple Clock Divide by 2// CoolRunner-II// Xilinx HDL Language Template, version 10.1
CLK_DIV2 CLK_DIV2_inst (.CLKDV(CLKDV), // Divided clock output.CLKIN(CLKIN) // Clock input
);
// End of CLK_DIV2_inst instantiation
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 293
Chapter 3: About Design Elements
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries Guide294 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
CLK_DIV2RPrimitive: Global Clock Divide by 2 with Synchronous Reset
Supported ArchitecturesThis design element is supported in the following architectures only:
CoolRunner™-II
IntroductionThis design element divides a user-provided external clock signal gclk<2> by 2.
Only one clock divider may be used per design. The global clock divider is available on the XC2C128, XC2C256,XC2C384, and XC2C512 CoolRunner™-II devices, but not the XC2C32 or XC2C64. The CLKIN and CDRSTinputs can only be connected to the device gclk<2> and CDRST pins. The duty cycle of the CLKDV output is50-50. The CLKDV output can only connect to clock inputs of synchronous elements. It cannot be used ascombinatorial logic, and should not be routed directly to an output pin.
The CDRST input is an active High synchronous reset. If CDRST is input High when the CLKDV output is High,the CLKDV output remains High to complete the last clock pulse, and then goes Low.
The CLKDV output is reset low by power-on reset circuitry.
Design Entry MethodThis design element can be used in schematics.
VHDL Instantiation TemplateUnless they already exist, copy the following two statements and paste them before the entity declaration.
Library UNISIM;use UNISIM.vcomponents.all;
-- CLK_DIV2R: Clock Divide by 2 with Synchronous Reset-- CoolRunner-II-- Xilinx HDL Language Template, version 10.1
CLK_DIV2R_inst : CLK_DIV2Rport map (
CLKDV => CLKDV, -- Divided clock outputCDRST => CDRST, -- Synchronous reset inputCLKIN => CLKIN -- Clock input
);
-- End of CLK_DIV2R_inst instantiation
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 295
Chapter 3: About Design Elements
Verilog Instantiation Template// CLK_DIV2R: Clock Divide by 2 with Synchronous Reset// CoolRunner-II// Xilinx HDL Language Template, version 10.1
CLK_DIV2R CLK_DIV2R_inst (.CLKDV(CLKDV), // Divided clock output.CDRST(CDRST), // Synchronous reset input.CLKIN(CLKIN) // Clock input
);
// End of CLK_DIV2R_inst instantiation
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries Guide296 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
CLK_DIV2RSDPrimitive: Global Clock Divide by 2 with Synchronous Reset and Start Delay
Supported ArchitecturesThis design element is supported in the following architectures only:CoolRunner™-II
IntroductionThis design element divides a user-provided external clock signal gclk<2> by 2.
Only one clock divider may be used per design. The global clock divider is available on the XC2C128, XC2C256,XC2C384, and XC2C512 CoolRunner™-II devices, but not the XC2C32 or XC2C64. The CLKIN and CDRSTinputs can only be connected to the device gclk<2> and CDRST pins. The duty cycle of the CLKDV output is50-50. The CLKDV output can only connect to clock inputs of synchronous elements. It cannot be used ascombinatorial logic, and should not be routed directly to an output pin.
The CDRST input is an active High synchronous reset. If CDRST is input High when the CLKDV output is High,the CLKDV output remains High to complete the last clock pulse, and then goes Low.
The start delay function delays the start of the CLKDV output by (n + 1) clocks, where n is the divisor forthe clock divider.
The CLKDV output is reset low by power-on reset circuitry.
Design Entry MethodThis design element can be used in schematics.
VHDL Instantiation TemplateUnless they already exist, copy the following two statements and paste them before the entity declaration.
Library UNISIM;use UNISIM.vcomponents.all;
-- CLK_DIV2RSD: Clock Divide by 2 with Synchronous Reset and Start-- Delay-- CoolRunner-II-- Xilinx HDL Language Template, version 10.1
CLK_DIV2RSD_inst : CLK_DIV2RSD-- Edit the following generic to specify the number of clock cycles-- to delay before starting.generic map (
DIVIDER_DELAY => 1)port map (
CLKDV => CLKDV, -- Divided clock outputCDRST => CDRST, -- Synchronous reset inputCLKIN => CLKIN -- Clock input
);
-- End of CLK_DIV2RSD_inst instantiation
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 297
Chapter 3: About Design Elements
Verilog Instantiation Template// CLK_DIV2RSD: Clock Divide by 2 with Synchronous Reset and Start// Delay// CoolRunner-II// Xilinx HDL Language Template, version 10.1
CLK_DIV2RSD CLK_DIV2RSD_inst (.CLKDV(CLKDV), // Divided clock output.CDRST(CDRST), // Synchronous reset input.CLKIN(CLKIN) // Clock input
);
// Edit the following defparam to specify the number of clock// cycles to delay before starting. If the instance name to// the clock divider is changed, that change needs to be// reflected in the defparam statements.
defparam CLK_DIV2RSD_inst.DIVIDER_DELAY = 1;
// End of CLK_DIV2RSD_inst instantiation
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries Guide298 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
CLK_DIV2SDPrimitive: Global Clock Divide by 2 with Start Delay
Supported ArchitecturesThis design element is supported in the following architectures only:
CoolRunner™-II
IntroductionThis design element divides a user-provided external clock signal gclk<2> by 2.
Only one clock divider may be used per design. The global clock divider is available on the XC2C128, XC2C256,XC2C384, and XC2C512 CoolRunner-II devices, but not the XC2C32 or XC2C64. The CLKIN input can onlybe connected to the device gclk<2> pin. The duty cycle of the CLKDV output is 50-50. The CLKDV output canonly connect to clock inputs of synchronous elements. It cannot be used as combinatorial logic, and shouldnot be routed directly to an output pin.
The start delay function delays the start of the CLKDV output by (n + 1) clocks, where n is the divisor forthe clock divider.
The CLKDV output is reset low by power-on reset circuitry.
Design Entry MethodThis design element can be used in schematics.
VHDL Instantiation TemplateUnless they already exist, copy the following two statements and paste them before the entity declaration.
Library UNISIM;use UNISIM.vcomponents.all;
-- CLK_DIV2SD: Clock Divide by 2 with Start Delay-- CoolRunner-II-- Xilinx HDL Language Template, version 10.1
CLK_DIV2SD_inst : CLK_DIV2SD-- Edit the following generic to specify the number of clock cycles-- to delay before starting.generic map (
DIVIDER_DELAY => 1)port map (
CLKDV => CLKDV, -- Divided clock outputCLKIN => CLKIN -- Clock input
);
-- End of CLK_DIV2SD_inst instantiation
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 299
Chapter 3: About Design Elements
Verilog Instantiation Template// CLK_DIV2SD: Clock Divide by 2 with Start Delay// CoolRunner-II// Xilinx HDL Language Template, version 10.1
CLK_DIV2SD CLK_DIV2SD_inst (.CLKDV(CLKDV), // Divided clock output.CDRST(CDRST), // Synchronous reset input.CLKIN(CLKIN) // Clock input
);
// Edit the following defparam to specify the number of clock// cycles to delay before starting. If the instance name to// the clock divider is changed, that change needs to be// reflected in the defparam statements.
defparam CLK_DIV2SD_inst.DIVIDER_DELAY = 1;
// End of CLK_DIV2SD_inst instantiation
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries Guide300 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
CLK_DIV4Primitive: Simple Global Clock Divide by 4
Supported ArchitecturesThis design element is supported in the following architectures only:CoolRunner™-II
IntroductionThis design element divides a user-provided external clock signal gclk<2> by 4.
Only one clock divider may be used per design. The global clock divider is available on the XC2C128, XC2C256,XC2C384, and XC2C512 CoolRunner-II devices, but not the XC2C32 or XC2C64. The CLKIN input can onlybe connected to the device gclk<2> pin. The duty cycle of the CLKDV output is 50-50. The CLKDV output canonly connect to clock inputs of synchronous elements. It cannot be used as combinatorial logic, and shouldnot be routed directly to an output pin.
The CLKDV output is reset low by power-on reset circuitry.
Design Entry MethodThis design element can be used in schematics.
VHDL Instantiation TemplateUnless they already exist, copy the following two statements and paste them before the entity declaration.
Library UNISIM;use UNISIM.vcomponents.all;
-- CLK_DIV4: Simple Clock Divide by 4-- CoolRunner-II-- Xilinx HDL Language Template, version 10.1
CLK_DIV4_inst : CLK_DIV4port map (
CLKDV => CLKDV, -- Divided clock outputCLKIN => CLKIN -- Clock input
);
-- End of CLK_DIV4_inst instantiation
Verilog Instantiation Template// CLK_DIV4: Simple Clock Divide by 4// CoolRunner-II// Xilinx HDL Language Template, version 10.1
CLK_DIV4 CLK_DIV4_inst (.CLKDV(CLKDV), // Divided clock output.CLKIN(CLKIN) // Clock input
);
// End of CLK_DIV4_inst instantiation
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 301
Chapter 3: About Design Elements
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries Guide302 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
CLK_DIV4RPrimitive: Global Clock Divide by 4 with Synchronous Reset
Supported ArchitecturesThis design element is supported in the following architectures only:
CoolRunner™-II
IntroductionThis design element divides a user-provided external clock signal gclk<2> by 4.
Only one clock divider may be used per design. The global clock divider is available on the XC2C128, XC2C256,XC2C384, and XC2C512 CoolRunner™-II devices, but not the XC2C32 or XC2C64. The CLKIN and CDRSTinputs can only be connected to the device gclk<2> and CDRST pins. The duty cycle of the CLKDV output is50-50. The CLKDV output can only connect to clock inputs of synchronous elements. It cannot be used ascombinatorial logic, and should not be routed directly to an output pin.
The CDRST input is an active High synchronous reset. If CDRST is input High when the CLKDV output is High,the CLKDV output remains High to complete the last clock pulse, and then goes Low.
The CLKDV output is reset low by power-on reset circuitry.
Design Entry MethodThis design element can be used in schematics.
VHDL Instantiation TemplateUnless they already exist, copy the following two statements and paste them before the entity declaration.
Library UNISIM;use UNISIM.vcomponents.all;
-- CLK_DIV4R: Clock Divide by 4 with Synchronous Reset-- CoolRunner-II-- Xilinx HDL Language Template, version 10.1
CLK_DIV4R_inst : CLK_DIV4Rport map (
CLKDV => CLKDV, -- Divided clock outputCDRST => CDRST, -- Synchronous reset inputCLKIN => CLKIN -- Clock input
);
-- End of CLK_DIV4R_inst instantiation
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 303
Chapter 3: About Design Elements
Verilog Instantiation Template// CLK_DIV4R: Clock Divide by 4 with Synchronous Reset// CoolRunner-II// Xilinx HDL Language Template, version 10.1
CLK_DIV4R CLK_DIV4R_inst (.CLKDV(CLKDV), // Divided clock output.CDRST(CDRST), // Synchronous reset input.CLKIN(CLKIN) // Clock input
);
// End of CLK_DIV4R_inst instantiation
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries Guide304 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
CLK_DIV4RSDPrimitive: Global Clock Divide by 4 with Synchronous Reset and Start Delay
Supported ArchitecturesThis design element is supported in the following architectures only:CoolRunner™-II
IntroductionThis design element divides a user-provided external clock signal gclk<2> by 4.
Only one clock divider may be used per design. The global clock divider is available on the XC2C128, XC2C256,XC2C384, and XC2C512 CoolRunner™-II devices, but not the XC2C32 or XC2C64. The CLKIN and CDRSTinputs can only be connected to the device gclk<2> and CDRST pins. The duty cycle of the CLKDV output is50-50. The CLKDV output can only connect to clock inputs of synchronous elements. It cannot be used ascombinatorial logic, and should not be routed directly to an output pin.
The CDRST input is an active High synchronous reset. If CDRST is input High when the CLKDV output is High,the CLKDV output remains High to complete the last clock pulse, and then goes Low.
The start delay function delays the start of the CLKDV output by (n + 1) clocks, where n is the divisor forthe clock divider.
The CLKDV output is reset low by power-on reset circuitry.
Design Entry MethodThis design element can be used in schematics.
VHDL Instantiation TemplateUnless they already exist, copy the following two statements and paste them before the entity declaration.
Library UNISIM;use UNISIM.vcomponents.all;
-- CLK_DIV4RSD: Clock Divide by 4 with Synchronous Reset and Start-- Delay-- CoolRunner-II-- Xilinx HDL Language Template, version 10.1
CLK_DIV4RSD_inst : CLK_DIV4RSD-- Edit the following generic to specify the number of clock cycles-- to delay before starting.generic map (
DIVIDER_DELAY => 1)port map (
CLKDV => CLKDV, -- Divided clock outputCDRST => CDRST, -- Synchronous reset inputCLKIN => CLKIN -- Clock input
);
-- End of CLK_DIV4RSD_inst instantiation
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 305
Chapter 3: About Design Elements
Verilog Instantiation Template// CLK_DIV4RSD: Clock Divide by 4 with Synchronous Reset and Start// Delay// CoolRunner-II// Xilinx HDL Language Template, version 10.1
CLK_DIV4RSD CLK_DIV4RSD_inst (.CLKDV(CLKDV), // Divided clock output.CDRST(CDRST), // Synchronous reset input.CLKIN(CLKIN) // Clock input
);
// Edit the following defparam to specify the number of clock// cycles to delay before starting. If the instance name to// the clock divider is changed, that change needs to be// reflected in the defparam statements.
defparam CLK_DIV4RSD_inst.DIVIDER_DELAY = 1;
// End of CLK_DIV4RSD_inst instantiation
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries Guide306 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
CLK_DIV4SDPrimitive: Global Clock Divide by 4 with Start Delay
Supported ArchitecturesThis design element is supported in the following architectures only:
CoolRunner™-II
IntroductionThis design element divides a user-provided external clock signal gclk<2> by 4.
Only one clock divider may be used per design. The global clock divider is available on the XC2C128, XC2C256,XC2C384, and XC2C512 CoolRunner-II devices, but not the XC2C32 or XC2C64. The CLKIN input can onlybe connected to the device gclk<2> pin. The duty cycle of the CLKDV output is 50-50. The CLKDV output canonly connect to clock inputs of synchronous elements. It cannot be used as combinatorial logic, and shouldnot be routed directly to an output pin.
The start delay function delays the start of the CLKDV output by (n + 1) clocks, where n is the divisor forthe clock divider.
The CLKDV output is reset low by power-on reset circuitry.
Design Entry MethodThis design element can be used in schematics.
VHDL Instantiation TemplateUnless they already exist, copy the following two statements and paste them before the entity declaration.
Library UNISIM;use UNISIM.vcomponents.all;
-- CLK_DIV4SD: Clock Divide by 4 with Start Delay-- CoolRunner-II-- Xilinx HDL Language Template, version 10.1
CLK_DIV4SD_inst : CLK_DIV4SD-- Edit the following generic to specify the number of clock cycles-- to delay before starting.generic map (
DIVIDER_DELAY => 1)port map (
CLKDV => CLKDV, -- Divided clock outputCLKIN => CLKIN -- Clock input
);
-- End of CLK_DIV4SD_inst instantiation
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 307
Chapter 3: About Design Elements
Verilog Instantiation Template// CLK_DIV4SD: Clock Divide by 4 with Start Delay// CoolRunner-II// Xilinx HDL Language Template, version 10.1
CLK_DIV4SD CLK_DIV4SD_inst (.CLKDV(CLKDV), // Divided clock output.CDRST(CDRST), // Synchronous reset input.CLKIN(CLKIN) // Clock input
);
// Edit the following defparam to specify the number of clock// cycles to delay before starting. If the instance name to// the clock divider is changed, that change needs to be// reflected in the defparam statements.
defparam CLK_DIV4SD_inst.DIVIDER_DELAY = 1;
// End of CLK_DIV4SD_inst instantiation
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries Guide308 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
CLK_DIV6Primitive: Simple Global Clock Divide by 6
Supported ArchitecturesThis design element is supported in the following architectures only:CoolRunner™-II
IntroductionThis design element divides a user-provided external clock signal gclk<2> by 6.
Only one clock divider may be used per design. The global clock divider is available on the XC2C128, XC2C256,XC2C384, and XC2C512 CoolRunner-II devices, but not the XC2C32 or XC2C64. The CLKIN input can onlybe connected to the device gclk<2> pin. The duty cycle of the CLKDV output is 50-50. The CLKDV output canonly connect to clock inputs of synchronous elements. It cannot be used as combinatorial logic, and shouldnot be routed directly to an output pin.
The CLKDV output is reset low by power-on reset circuitry.
Design Entry MethodThis design element can be used in schematics.
VHDL Instantiation TemplateUnless they already exist, copy the following two statements and paste them before the entity declaration.
Library UNISIM;use UNISIM.vcomponents.all;
-- CLK_DIV6: Simple Clock Divide by 6-- CoolRunner-II-- Xilinx HDL Language Template, version 10.1
CLK_DIV6_inst : CLK_DIV6port map (
CLKDV => CLKDV, -- Divided clock outputCLKIN => CLKIN -- Clock input
);
-- End of CLK_DIV6_inst instantiation
Verilog Instantiation Template// CLK_DIV6: Simple Clock Divide by 6// CoolRunner-II// Xilinx HDL Language Template, version 10.1
CLK_DIV6 CLK_DIV6_inst (.CLKDV(CLKDV), // Divided clock output.CLKIN(CLKIN) // Clock input
);
// End of CLK_DIV6_inst instantiation
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 309
Chapter 3: About Design Elements
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries Guide310 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
CLK_DIV6RPrimitive: Global Clock Divide by 6 with Synchronous Reset
Supported ArchitecturesThis design element is supported in the following architectures only:
CoolRunner™-II
IntroductionThis design element divides a user-provided external clock signal gclk<2> by 6.
Only one clock divider may be used per design. The global clock divider is available on the XC2C128, XC2C256,XC2C384, and XC2C512 CoolRunner™-II devices, but not the XC2C32 or XC2C64. The CLKIN and CDRSTinputs can only be connected to the device gclk<2> and CDRST pins. The duty cycle of the CLKDV output is50-50. The CLKDV output can only connect to clock inputs of synchronous elements. It cannot be used ascombinatorial logic, and should not be routed directly to an output pin.
The CDRST input is an active High synchronous reset. If CDRST is input High when the CLKDV output is High,the CLKDV output remains High to complete the last clock pulse, and then goes Low.
The CLKDV output is reset low by power-on reset circuitry.
Design Entry MethodThis design element can be used in schematics.
VHDL Instantiation TemplateUnless they already exist, copy the following two statements and paste them before the entity declaration.
Library UNISIM;use UNISIM.vcomponents.all;
-- CLK_DIV6R: Clock Divide by 6 with Synchronous Reset-- CoolRunner-II-- Xilinx HDL Language Template, version 10.1
CLK_DIV6R_inst : CLK_DIV6Rport map (
CLKDV => CLKDV, -- Divided clock outputCDRST => CDRST, -- Synchronous reset inputCLKIN => CLKIN -- Clock input
);
-- End of CLK_DIV6R_inst instantiation
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 311
Chapter 3: About Design Elements
Verilog Instantiation Template// CLK_DIV6R: Clock Divide by 6 with Synchronous Reset// CoolRunner-II// Xilinx HDL Language Template, version 10.1
CLK_DIV6R CLK_DIV6R_inst (.CLKDV(CLKDV), // Divided clock output.CDRST(CDRST), // Synchronous reset input.CLKIN(CLKIN) // Clock input
);
// End of CLK_DIV6R_inst instantiation
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries Guide312 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
CLK_DIV6RSDPrimitive: Global Clock Divide by 6 with Synchronous Reset and Start Delay
Supported ArchitecturesThis design element is supported in the following architectures only:CoolRunner™-II
IntroductionThis design element divides a user-provided external clock signal gclk<2> by 6.
Only one clock divider may be used per design. The global clock divider is available on the XC2C128, XC2C256,XC2C384, and XC2C512 CoolRunner™-II devices, but not the XC2C32 or XC2C64. The CLKIN and CDRSTinputs can only be connected to the device gclk<2> and CDRST pins. The duty cycle of the CLKDV output is50-50. The CLKDV output can only connect to clock inputs of synchronous elements. It cannot be used ascombinatorial logic, and should not be routed directly to an output pin.
The CDRST input is an active High synchronous reset. If CDRST is input High when the CLKDV output is High,the CLKDV output remains High to complete the last clock pulse, and then goes Low.
The start delay function delays the start of the CLKDV output by (n + 1) clocks, where n is the divisor forthe clock divider.
The CLKDV output is reset low by power-on reset circuitry.
Design Entry MethodThis design element can be used in schematics.
VHDL Instantiation TemplateUnless they already exist, copy the following two statements and paste them before the entity declaration.
Library UNISIM;use UNISIM.vcomponents.all;
-- CLK_DIV6RSD: Clock Divide by 6 with Synchronous Reset and Start-- Delay-- CoolRunner-II-- Xilinx HDL Language Template, version 10.1
CLK_DIV6RSD_inst : CLK_DIV6RSD-- Edit the following generic to specify the number of clock cycles-- to delay before starting.generic map (
DIVIDER_DELAY => 1)port map (
CLKDV => CLKDV, -- Divided clock outputCDRST => CDRST, -- Synchronous reset inputCLKIN => CLKIN -- Clock input
);
-- End of CLK_DIV6RSD_inst instantiation
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 313
Chapter 3: About Design Elements
Verilog Instantiation Template// CLK_DIV6RSD: Clock Divide by 6 with Synchronous Reset and Start// Delay// CoolRunner-II// Xilinx HDL Language Template, version 10.1
CLK_DIV6RSD CLK_DIV6RSD_inst (.CLKDV(CLKDV), // Divided clock output.CDRST(CDRST), // Synchronous reset input.CLKIN(CLKIN) // Clock input
);
// Edit the following defparam to specify the number of clock// cycles to delay before starting. If the instance name to// the clock divider is changed, that change needs to be// reflected in the defparam statements.
defparam CLK_DIV6RSD_inst.DIVIDER_DELAY = 1;
// End of CLK_DIV6RSD_inst instantiation
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries Guide314 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
CLK_DIV6SDPrimitive: Global Clock Divide by 6 with Start Delay
Supported ArchitecturesThis design element is supported in the following architectures only:
CoolRunner™-II
IntroductionThis design element divides a user-provided external clock signal gclk<2> by 6.
Only one clock divider may be used per design. The global clock divider is available on the XC2C128, XC2C256,XC2C384, and XC2C512 CoolRunner-II devices, but not the XC2C32 or XC2C64. The CLKIN input can onlybe connected to the device gclk<2> pin. The duty cycle of the CLKDV output is 50-50. The CLKDV output canonly connect to clock inputs of synchronous elements. It cannot be used as combinatorial logic, and shouldnot be routed directly to an output pin.
The start delay function delays the start of the CLKDV output by (n + 1) clocks, where n is the divisor forthe clock divider.
The CLKDV output is reset low by power-on reset circuitry.
Design Entry MethodThis design element can be used in schematics.
VHDL Instantiation TemplateUnless they already exist, copy the following two statements and paste them before the entity declaration.
Library UNISIM;use UNISIM.vcomponents.all;
-- CLK_DIV6SD: Clock Divide by 6 with Start Delay-- CoolRunner-II-- Xilinx HDL Language Template, version 10.1
CLK_DIV6SD_inst : CLK_DIV6SD-- Edit the following generic to specify the number of clock cycles-- to delay before starting.generic map (
DIVIDER_DELAY => 1)port map (
CLKDV => CLKDV, -- Divided clock outputCLKIN => CLKIN -- Clock input
);
-- End of CLK_DIV4SD_inst instantiation
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 315
Chapter 3: About Design Elements
Verilog Instantiation Template// CLK_DIV6SD: Clock Divide by 6 with Start Delay// CoolRunner-II// Xilinx HDL Language Template, version 10.1
CLK_DIV6SD CLK_DIV6SD_inst (.CLKDV(CLKDV), // Divided clock output.CDRST(CDRST), // Synchronous reset input.CLKIN(CLKIN) // Clock input
);
// Edit the following defparam to specify the number of clock// cycles to delay before starting. If the instance name to// the clock divider is changed, that change needs to be// reflected in the defparam statements.
defparam CLK_DIV6SD_inst.DIVIDER_DELAY = 1;
// End of CLK_DIV6SD_inst instantiation
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries Guide316 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
CLK_DIV8Primitive: Simple Global Clock Divide by 8
Supported ArchitecturesThis design element is supported in the following architectures only:
CoolRunner™-II
IntroductionThis design element divides a user-provided external clock signal gclk<2> by 8.
Only one clock divider may be used per design. The global clock divider is available on the XC2C128, XC2C256,XC2C384, and XC2C512 CoolRunner-II devices, but not the XC2C32 or XC2C64. The CLKIN input can onlybe connected to the device gclk<2> pin. The duty cycle of the CLKDV output is 50-50. The CLKDV output canonly connect to clock inputs of synchronous elements. It cannot be used as combinatorial logic, and shouldnot be routed directly to an output pin.
The CLKDV output is reset low by power-on reset circuitry.
Design Entry MethodThis design element can be used in schematics.
VHDL Instantiation TemplateUnless they already exist, copy the following two statements and paste them before the entity declaration.
Library UNISIM;use UNISIM.vcomponents.all;
-- CLK_DIV8: Simple Clock Divide by 8-- CoolRunner-II-- Xilinx HDL Language Template, version 10.1
CLK_DIV8_inst : CLK_DIV8port map (
CLKDV => CLKDV, -- Divided clock outputCLKIN => CLKIN -- Clock input
);
-- End of CLK_DIV8_inst instantiation
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 317
Chapter 3: About Design Elements
Verilog Instantiation Template// CLK_DIV8: Simple Clock Divide by 8// CoolRunner-II// Xilinx HDL Language Template, version 10.1
CLK_DIV8 CLK_DIV8_inst (.CLKDV(CLKDV), // Divided clock output.CLKIN(CLKIN) // Clock input
);
// End of CLK_DIV8_inst instantiation
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries Guide318 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
CLK_DIV8RPrimitive: Global Clock Divide by 8 with Synchronous Reset
Supported ArchitecturesThis design element is supported in the following architectures only:
CoolRunner™-II
IntroductionThis design element divides a user-provided external clock signal gclk<2> by 8.
Only one clock divider may be used per design. The global clock divider is available on the XC2C128, XC2C256,XC2C384, and XC2C512 CoolRunner™-II devices, but not the XC2C32 or XC2C64. The CLKIN and CDRSTinputs can only be connected to the device gclk<2> and CDRST pins. The duty cycle of the CLKDV output is50-50. The CLKDV output can only connect to clock inputs of synchronous elements. It cannot be used ascombinatorial logic, and should not be routed directly to an output pin.
The CDRST input is an active High synchronous reset. If CDRST is input High when the CLKDV output is High,the CLKDV output remains High to complete the last clock pulse, and then goes Low.
The CLKDV output is reset low by power-on reset circuitry.
Design Entry MethodThis design element can be used in schematics.
VHDL Instantiation TemplateUnless they already exist, copy the following two statements and paste them before the entity declaration.
Library UNISIM;use UNISIM.vcomponents.all;
-- CLK_DIV8R: Clock Divide by 8 with Synchronous Reset-- CoolRunner-II-- Xilinx HDL Language Template, version 10.1
CLK_DIV8R_inst : CLK_DIV8Rport map (
CLKDV => CLKDV, -- Divided clock outputCDRST => CDRST, -- Synchronous reset inputCLKIN => CLKIN -- Clock input
);
-- End of CLK_DIV8R_inst instantiation
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 319
Chapter 3: About Design Elements
Verilog Instantiation Template// CLK_DIV8R: Clock Divide by 8 with Synchronous Reset// CoolRunner-II// Xilinx HDL Language Template, version 10.1
CLK_DIV8R CLK_DIV8R_inst (.CLKDV(CLKDV), // Divided clock output.CDRST(CDRST), // Synchronous reset input.CLKIN(CLKIN) // Clock input
);
// End of CLK_DIV8R_inst instantiation
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries Guide320 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
CLK_DIV8RSDPrimitive: Global Clock Divide by 8 with Synchronous Reset and Start Delay
Supported ArchitecturesThis design element is supported in the following architectures only:CoolRunner™-II
IntroductionThis design element divides a user-provided external clock signal gclk<2> by 8.
Only one clock divider may be used per design. The global clock divider is available on the XC2C128, XC2C256,XC2C384, and XC2C512 CoolRunner™-II devices, but not the XC2C32 or XC2C64. The CLKIN and CDRSTinputs can only be connected to the device gclk<2> and CDRST pins. The duty cycle of the CLKDV output is50-50. The CLKDV output can only connect to clock inputs of synchronous elements. It cannot be used ascombinatorial logic, and should not be routed directly to an output pin.
The CDRST input is an active High synchronous reset. If CDRST is input High when the CLKDV output is High,the CLKDV output remains High to complete the last clock pulse, and then goes Low.
The start delay function delays the start of the CLKDV output by (n + 1) clocks, where n is the divisor forthe clock divider.
The CLKDV output is reset low by power-on reset circuitry.
Design Entry MethodThis design element can be used in schematics.
VHDL Instantiation TemplateUnless they already exist, copy the following two statements and paste them before the entity declaration.
Library UNISIM;use UNISIM.vcomponents.all;
-- CLK_DIV8RSD: Clock Divide by 8 with Synchronous Reset and Start-- Delay-- CoolRunner-II-- Xilinx HDL Language Template, version 10.1
CLK_DIV8RSD_inst : CLK_DIV8RSD-- Edit the following generic to specify the number of clock cycles-- to delay before starting.generic map (
DIVIDER_DELAY => 1)port map (
CLKDV => CLKDV, -- Divided clock outputCDRST => CDRST, -- Synchronous reset inputCLKIN => CLKIN -- Clock input
);
-- End of CLK_DIV8RSD_inst instantiation
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 321
Chapter 3: About Design Elements
Verilog Instantiation Template// CLK_DIV8RSD: Clock Divide by 8 with Synchronous Reset and Start// Delay// CoolRunner-II// Xilinx HDL Language Template, version 10.1
CLK_DIV8RSD CLK_DIV8RSD_inst (.CLKDV(CLKDV), // Divided clock output.CDRST(CDRST), // Synchronous reset input.CLKIN(CLKIN) // Clock input
);
// Edit the following defparam to specify the number of clock// cycles to delay before starting. If the instance name to// the clock divider is changed, that change needs to be// reflected in the defparam statements.
defparam CLK_DIV8RSD_inst.DIVIDER_DELAY = 1;
// End of CLK_DIV8RSD_inst instantiation
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries Guide322 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
CLK_DIV8SDPrimitive: Global Clock Divide by 8 with Start Delay
Supported ArchitecturesThis design element is supported in the following architectures only:
CoolRunner™-II
IntroductionThis design element divides a user-provided external clock signal gclk<2> by 8.
Only one clock divider may be used per design. The global clock divider is available on the XC2C128, XC2C256,XC2C384, and XC2C512 CoolRunner-II devices, but not the XC2C32 or XC2C64. The CLKIN input can onlybe connected to the device gclk<2> pin. The duty cycle of the CLKDV output is 50-50. The CLKDV output canonly connect to clock inputs of synchronous elements. It cannot be used as combinatorial logic, and shouldnot be routed directly to an output pin.
The start delay function delays the start of the CLKDV output by (n + 1) clocks, where n is the divisor forthe clock divider.
The CLKDV output is reset low by power-on reset circuitry.
Design Entry MethodThis design element can be used in schematics.
VHDL Instantiation TemplateUnless they already exist, copy the following two statements and paste them before the entity declaration.
Library UNISIM;use UNISIM.vcomponents.all;
-- CLK_DIV8SD: Clock Divide by 8 with Start Delay-- CoolRunner-II-- Xilinx HDL Language Template, version 10.1
CLK_DIV8SD_inst : CLK_DIV8SD-- Edit the following generic to specify the number of clock cycles-- to delay before starting.generic map (
DIVIDER_DELAY => 1)port map (
CLKDV => CLKDV, -- Divided clock outputCLKIN => CLKIN -- Clock input
);
-- End of CLK_DIV8SD_inst instantiation
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 323
Chapter 3: About Design Elements
Verilog Instantiation Template// CLK_DIV8SD: Clock Divide by 8 with Start Delay// CoolRunner-II// Xilinx HDL Language Template, version 10.1
CLK_DIV8SD CLK_DIV8SD_inst (.CLKDV(CLKDV), // Divided clock output.CDRST(CDRST), // Synchronous reset input.CLKIN(CLKIN) // Clock input
);
// Edit the following defparam to specify the number of clock// cycles to delay before starting. If the instance name to// the clock divider is changed, that change needs to be// reflected in the defparam statements.
defparam CLK_DIV8SD_inst.DIVIDER_DELAY = 1;
// End of CLK_DIV8SD_inst instantiation
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries Guide324 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
COMP16Macro: 16-Bit Identity Comparator
Supported ArchitecturesThis design element is supported in the following architectures only:
• XC9500
• CoolRunner™ XPLA3
• CoolRunner-II
IntroductionThis design element is a 16-bit identity comparator. The equal output (EQ) is high when A15 : A0 and B15 :B0 are equal.
Equality is determined by a bit comparison of the two words. When any two of the corresponding bits fromeach word are not the same, the EQ output is Low.
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 325
Chapter 3: About Design Elements
COMP2Macro: 2-Bit Identity Comparator
Supported ArchitecturesThis design element is supported in the following architectures only:
• XC9500
• CoolRunner™ XPLA3
• CoolRunner-II
IntroductionThis design element is a 2-bit identity comparator. The equal output (EQ) is High when the two words A1 : A0and B1 : B0 are equal.
Equality is determined by a bit comparison of the two words. When any two of the corresponding bits fromeach word are not the same, the EQ output is Low.
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries Guide326 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
COMP4Macro: 4-Bit Identity Comparator
Supported ArchitecturesThis design element is supported in the following architectures only:
• XC9500
• CoolRunner™ XPLA3
• CoolRunner-II
IntroductionThis design element is a 4-bit identity comparator. The equal output (EQ) is high when A3 : A0 and B3 : B0 areequal.
Equality is determined by a bit comparison of the two words. When any two of the corresponding bits fromeach word are not the same, the EQ output is Low.
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 327
Chapter 3: About Design Elements
COMP8Macro: 8-Bit Identity Comparator
Supported ArchitecturesThis design element is supported in the following architectures only:
• XC9500
• CoolRunner™ XPLA3
• CoolRunner-II
IntroductionThis design element is an 8-bit identity comparator. The equal output (EQ) is high when A7 : A0 and B7 :B0 are equal.
Equality is determined by a bit comparison of the two words. When any two of the corresponding bits fromeach word are not the same, the EQ output is Low.
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries Guide328 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
COMPM16Macro: 16-Bit Magnitude Comparator
Supported ArchitecturesThis design element is supported in the following architectures only:• XC9500• CoolRunner™ XPLA3• CoolRunner-II
IntroductionThis design element is a 16-bit magnitude comparator that compare two positive Binary-weighted words. Itcompares A15 : A0 and B15 : B0, where A15 and B15 are the most significant bits.
The greater-than output (GT) is High when A > B, and the less-than output (LT) is High when A < B Whenthe two words are equal, both GT and LT are Low. Equality can be measured with this macro by comparingboth outputs with a NOR gate.
Logic TableInputs Outputs
A7, B7 A6, B6 A5, B5 A4, B4 A3, B3 A2, B2 A1, B1 A0, B0 GT LT
A7>B7 X X X X X X X 1 0
A7<B7 X X X X X X X 0 1
A7=B7 A6>B6 X X X X X X 1 0
A7=B7 A6<B6 X X X X X X 0 1
A7=B7 A6=B6 A5>B5 X X X X X 1 0
A7=B7 A6=B6 A5<B5 X X X X X 0 1
A7=B7 A6=B6 A5=B5 A4>B4 X X X X 1 0
A7=B7 A6=B6 A5=B5 A4<B4 X X X X 0 1
A7=B7 A6=B6 A5=B5 A4=B4 A3>B3 X X X 1 0
A7=B7 A6=B6 A5=B5 A4=B4 A3<B3 X X X 0 1
A7=B7 A6=B6 A5=B5 A4=B4 A3=B3 A2>B2 X X 1 0
A7=B7 A6=B6 A5=B5 A4=B4 A3=B3 A2<B2 X X 0 1
A7=B7 A6=B6 A5=B5 A4=B4 A3=B3 A2=B2 A1>B1 X 1 0
A7=B7 A6=B6 A5=B5 A4=B4 A3=B3 A2=B2 A1<B1 X 0 1
A7=B7 A6=B6 A5=B5 A4=B4 A3=B3 A2=B2 A1=B1 A0>B0 1 0
A7=B7 A6=B6 A5=B5 A4=B4 A3=B3 A2=B2 A1=B1 A0<B0 0 1
A7=B7 A6=B6 A5=B5 A4=B4 A3=B3 A2=B2 A1=B1 A0=B0 0 0
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 329
Chapter 3: About Design Elements
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries Guide330 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
COMPM2Macro: 2-Bit Magnitude Comparator
Supported ArchitecturesThis design element is supported in the following architectures only:• XC9500• CoolRunner™ XPLA3• CoolRunner-II
IntroductionThis design element is a 2-bit magnitude comparator that compare two positive binary-weighted words. Itcompares A1 : A0 and B1 : B0, where A1 and B1 are the most significant bits.
The greater-than output (GT) is High when A > B, and the less-than output (LT) is High when A < B Whenthe two words are equal, both GT and LT are Low. Equality can be measured with this macro by comparingboth outputs with a NOR gate.
Logic TableInputs Outputs
A1 B1 A0 B0 GT LT
0 0 0 0 0 0
0 0 1 0 1 0
0 0 0 1 0 1
0 0 1 1 0 0
1 1 0 0 0 0
1 1 1 0 1 0
1 1 0 1 0 1
1 1 1 1 0 0
1 0 X X 1 0
0 1 X X 0 1
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.• See the appropriate CPLD Data Sheets.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 331
Chapter 3: About Design Elements
COMPM4Macro: 4-Bit Magnitude Comparator
Supported ArchitecturesThis design element is supported in the following architectures only:• XC9500• CoolRunner™ XPLA3• CoolRunner-II
IntroductionThis design element is a 4-bit magnitude comparator that compare two positive Binary-weighted words. Itcompares A3 : A0 and B3 : B0, where A3 and B3 are the most significant bits.
The greater-than output (GT) is High when A > B, and the less-than output (LT) is High when A < B Whenthe two words are equal, both GT and LT are Low. Equality can be measured with this macro by comparingboth outputs with a NOR gate.
Logic TableInputs Outputs
A3, B3 A2, B2 A1, B1 A0, B0 GT LT
A3>B3 X X X 1 0
A3<B3 X X X 0 1
A3=B3 A2>B2 X X 1 0
A3=B3 A2<B2 X X 0 1
A3=B3 A2=B2 A1>B1 X 1 0
A3=B3 A2=B2 A1<B1 X 0 1
A3=B3 A2=A2 A1=B1 A0>B0 1 0
A3=B3 A2=B2 A1=B1 A0<B0 0 1
A3=B3 A2=B2 A1=B1 A0=B0 0 0
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.• See the appropriate CPLD Data Sheets.
CPLD Libraries Guide332 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
COMPM8Macro: 8-Bit Magnitude Comparator
Supported ArchitecturesThis design element is supported in the following architectures only:• XC9500• CoolRunner™ XPLA3• CoolRunner-II
IntroductionThis design element is an 8-bit magnitude comparator that compare two positive Binary-weighted words. Itcompares A7 : A0 and B7 : B0, where A7 and B7 are the most significant bits.
The greater-than output (GT) is High when A > B, and the less-than output (LT) is High when A < B Whenthe two words are equal, both GT and LT are Low. Equality can be measured with this macro by comparingboth outputs with a NOR gate.
Logic TableInputs Outputs
A7, B7 A6, B6 A5, B5 A4, B4 A3, B3 A2, B2 A1, B1 A0, B0 GT LT
A7>B7 X X X X X X X 1 0
A7<B7 X X X X X X X 0 1
A7=B7 A6>B6 X X X X X X 1 0
A7=B7 A6<B6 X X X X X X 0 1
A7=B7 A6=B6 A5>B5 X X X X X 1 0
A7=B7 A6=B6 A5<B5 X X X X X 0 1
A7=B7 A6=B6 A5=B5 A4>B4 X X X X 1 0
A7=B7 A6=B6 A5=B5 A4<B4 X X X X 0 1
A7=B7 A6=B6 A5=B5 A4=B4 A3>B3 X X X 1 0
A7=B7 A6=B6 A5=B5 A4=B4 A3<B3 X X X 0 1
A7=B7 A6=B6 A5=B5 A4=B4 A3=B3 A2>B2 X X 1 0
A7=B7 A6=B6 A5=B5 A4=B4 A3=B3 A2<B2 X X 0 1
A7=B7 A6=B6 A5=B5 A4=B4 A3=B3 A2=B2 A1>B1 X 1 0
A7=B7 A6=B6 A5=B5 A4=B4 A3=B3 A2=B2 A1<B1 X 0 1
A7=B7 A6=B6 A5=B5 A4=B4 A3=B3 A2=B2 A1=B1 A0>B0 1 0
A7=B7 A6=B6 A5=B5 A4=B4 A3=B3 A2=B2 A1=B1 A0<B0 0 1
A7=B7 A6=B6 A5=B5 A4=B4 A3=B3 A2=B2 A1=B1 A0=B0 0 0
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 333
Chapter 3: About Design Elements
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries Guide334 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
CR16CEMacro: 16-Bit Negative-Edge Binary Ripple Counter with Clock Enable and Asynchronous Clear
Supported ArchitecturesThis design element is supported in the following architectures only:
• XC9500
• CoolRunner™ XPLA3
• CoolRunner-II
IntroductionThis design element is a 16-bit cascadable, clearable, binary ripple counter with clock enable and asynchronousclear.
Larger counters can be created by connecting the last Q output of the first stage to the clock input of the nextstage. CLR and CE inputs are connected in parallel. The clock period is not affected by the overall length of aripple counter. The overall clock-to-output propagation is n(tC - Q), where n is the number of stages and the timetC - Q is the C-to-Qz propagation delay of each stage.
This counter is asynchronously cleared, outputs Low, when power is applied.
Logic TableInputs Outputs
CLR CE C Qz : Q0
1 X X 0
0 0 X No Change
0 1 ↓ Inc
z = bit width - 1
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 335
Chapter 3: About Design Elements
CR8CEMacro: 8-Bit Negative-Edge Binary Ripple Counter with Clock Enable and Asynchronous Clear
Supported ArchitecturesThis design element is supported in the following architectures only:• XC9500• CoolRunner™ XPLA3• CoolRunner-II
IntroductionThis design element is an 8-bit cascadable, clearable, binary, ripple counter with clock enable and asynchronousclear.
The asynchronous clear (CLR), when High, overrides all other inputs and causes the Q outputs to go to logiclevel zero. The counter increments when the clock enable input (CE) is High during the High-to-Low clock (C)transition. The counter ignores clock transitions when CE is Low.
Larger counters can be created by connecting the last Q output of the first stage to the clock input of the nextstage. CLR and CE inputs are connected in parallel. The clock period is not affected by the overall length of aripple counter. The overall clock-to-output propagation is n(tC - Q), where n is the number of stages and the timetC - Q is the C-to-Qz propagation delay of each stage.
This counter is asynchronously cleared, outputs Low, when power is applied.
Logic TableInputs Outputs
CLR CE C Qz : Q0
1 X X 0
0 0 X No Change
0 1 ↓ Inc
z = bit width - 1
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.• See the appropriate CPLD Data Sheets.
CPLD Libraries Guide336 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
CRD16CEMacro: 16-Bit Dual-Edge Triggered Binary Ripple Counter with Clock Enable and AsynchronousClear
Supported ArchitecturesThis design element is supported in the following architectures only:CoolRunner™-II
IntroductionThis design element is a dual edge triggered 16-bit cascadable, clearable, binary ripple counter.
The asynchronous clear (CLR), when High, overrides all other inputs and causes the Q outputs to go to logiclevel zero. The counter increments when the clock enable input (CE) is High during the High-to-Low andLow-to-High clock (C) transitions. The counter ignores clock transitions when CE is Low.
Larger counters can be created by connecting the last Q output of the first stage to the clock input of the nextstage. CLR and CE inputs are connected in parallel. The clock period is not affected by the overall length of aripple counter. The overall clock-to-output propagation is n(tC - Q), where n is the number of stages and the timetC - Q is the C-to-Qz propagation delay of each stage.
This counter is asynchronously cleared, outputs Low, when power is applied. For CPLD devices, you cansimulate power-on by applying a High-level pulse on the PRLD global net.
Logic TableInputs Outputs
CLR CE C Qz : Q0
1 X X 0
0 0 X No Change
0 1 ↑ Inc
0 1 ↓ Inc
z = bit width - 1
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.• See the appropriate CPLD Data Sheets.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 337
Chapter 3: About Design Elements
CRD8CEMacro: 8-Bit Dual-Edge Triggered Binary Ripple Counter with Clock Enable and Asynchronous Clear
Supported ArchitecturesThis design element is supported in the following architectures only:CoolRunner™-II
IntroductionThis design element is a dual edge triggered 8-bit cascadable, clearable, binary ripple counter.
The asynchronous clear (CLR), when High, overrides all other inputs and causes the Q outputs to go to logiclevel zero. The counter increments when the clock enable input (CE) is High during the High-to-Low andLow-to-High clock (C) transitions. The counter ignores clock transitions when CE is Low.
Larger counters can be created by connecting the last Q output of the first stage to the clock input of the nextstage. CLR and CE inputs are connected in parallel. The clock period is not affected by the overall length of aripple counter. The overall clock-to-output propagation is n(tC - Q), where n is the number of stages and the timetC - Q is the C-to-Qz propagation delay of each stage.
This counter is asynchronously cleared, outputs Low, when power is applied. For CPLD devices, you cansimulate power-on by applying a High-level pulse on the PRLD global net.
Logic TableInputs Outputs
CLR CE C Qz : Q0
1 X X 0
0 0 X No Change
0 1 ↑ Inc
0 1 ↓ Inc
z = bit width - 1
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.• See the appropriate CPLD Data Sheets.
CPLD Libraries Guide338 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
D2_4EMacro: 2- to 4-Line Decoder/Demultiplexer with Enable
Supported ArchitecturesThis design element is supported in the following architectures only:
• XC9500
• CoolRunner™ XPLA3
• CoolRunner-II
IntroductionThis design element is a decoder/demultiplexer. When the enable (E) input of this element is High, one of fouractive-High outputs (D3 : D0) is selected with a 2-bit binary address (A1 : A0) input. The non-selected outputsare Low. Also, when the E input is Low, all outputs are Low. In demultiplexer applications, the E input is thedata input.
Logic TableInputs Outputs
A1 A0 E D3 D2 D1 D0
X X 0 0 0 0 0
0 0 1 0 0 0 1
0 1 1 0 0 1 0
1 0 1 0 1 0 0
1 1 1 1 0 0 0
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 339
Chapter 3: About Design Elements
D3_8EMacro: 3- to 8-Line Decoder/Demultiplexer with Enable
Supported ArchitecturesThis design element is supported in the following architectures only:• XC9500• CoolRunner™ XPLA3• CoolRunner-II
IntroductionWhen the enable (E) input of the D3_8E decoder/demultiplexer is High, one of eight active-High outputs (D7 :D0) is selected with a 3-bit binary address (A2 : A0) input. The non-selected outputs are Low. Also, when the Einput is Low, all outputs are Low. In demultiplexer applications, the E input is the data input.
Logic TableInputs Outputs
A2 A1 A0 E D7 D6 D5 D4 D3 D2 D1 D0
X X X 0 0 0 0 0 0 0 0 0
0 0 0 1 0 0 0 0 0 0 0 1
0 0 1 1 0 0 0 0 0 0 1 0
0 1 0 1 0 0 0 0 0 1 0 0
0 1 1 1 0 0 0 0 1 0 0 0
1 0 0 1 0 0 0 1 0 0 0 0
1 0 1 1 0 0 1 0 0 0 0 0
1 1 0 1 0 1 0 0 0 0 0 0
1 1 1 1 1 0 0 0 0 0 0 0
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.• See the appropriate CPLD Data Sheets.
CPLD Libraries Guide340 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
D4_16EMacro: 4- to 16-Line Decoder/Demultiplexer with Enable
Supported ArchitecturesThis design element is supported in the following architectures only:
• XC9500
• CoolRunner™ XPLA3
• CoolRunner-II
IntroductionThis design element is a decoder/demultiplexer. When the enable (E) input of this design element is High, oneof 16 active-High outputs (D15 : D0) is selected with a 4-bit binary address (A3 : A0) input. The non-selectedoutputs are Low. Also, when the E input is Low, all outputs are Low. In demultiplexer applications, the Einput is the data input.
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 341
Chapter 3: About Design Elements
FDMacro: D Flip-Flop
Supported ArchitecturesThis design element is supported in the following architectures only:
• XC9500
• CoolRunner™ XPLA3
• CoolRunner-II
IntroductionThis design element is a D-type flip-flop with data input (D) and data output (Q). The data on the D inputs isloaded into the flip-flop during the Low-to-High clock (C) transition.
This flip-flop is asynchronously cleared, outputs Low, when power is applied. For CPLD devices, you cansimulate power-on by applying a High-level pulse on the PRLD global net.
Logic TableInputs Outputs
D C Q
0 ↑ 0
1 ↑ 1
Design Entry MethodThis design element is only for use in schematics.
Available AttributesAttribute Type Allowed Values Default Description
INIT Binary 0, 1 0 Sets the initial value of Q output after configuration
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries Guide342 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
FD16Macro: Multiple D Flip-Flop
Supported ArchitecturesThis design element is supported in the following architectures only:
• XC9500
• CoolRunner™ XPLA3
• CoolRunner-II
IntroductionThis design element is a multiple D-type flip-flops with data inputs (D) and data outputs (Q), with a 16-bitregister, each with a common clock (C). The data on the D inputs is loaded into the flip-flop during theLow-to-High clock (C) transition.
This flip-flop is asynchronously cleared, outputs Low, when power is applied. For CPLD devices, you cansimulate power-on by applying a High-level pulse on the PRLD global net.
Logic TableInputs Outputs
Dz : D0 C Qz : Q0
0 ↑ 0
1 ↑ 1
z = bit-width - 1
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 343
Chapter 3: About Design Elements
FD16CEMacro: 16-Bit Data Register with Clock Enable and Asynchronous Clear
Supported ArchitecturesThis design element is supported in the following architectures only:• XC9500• CoolRunner™ XPLA3• CoolRunner-II
IntroductionThis design element is a 16-bit data register with clock enable and asynchronous clear. When clock enable (CE) isHigh and asynchronous clear (CLR) is Low, the data on the data inputs (D) is transferred to the correspondingdata outputs (Q) during the Low-to-High clock (C) transition. When CLR is High, it overrides all other inputsand resets the data outputs (Q) Low. When CE is Low, clock transitions are ignored.
This register is asynchronously cleared, outputs Low, when power is applied. For CPLD devices, you cansimulate power-on by applying a High-level pulse on the PRLD global net.
Logic TableInputs Outputs
CLR CE Dz : D0 C Qz : Q0
1 X X X 0
0 0 X X No Change
0 1 Dn ↑ Dn
z = bit-width - 1
Design Entry MethodThis design element is only for use in schematics.
Available AttributesAttribute Type Allowed Values Default Description
INIT Binary Any 16-bitValue
All zeros Sets the initial value of Q output after configuration
For More Information• See the appropriate CPLD User Guide.• See the appropriate CPLD Data Sheets.
CPLD Libraries Guide344 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
FD16REMacro: 16-Bit Data Register with Clock Enable and Synchronous Reset
Supported ArchitecturesThis design element is supported in the following architectures only:• XC9500• CoolRunner™ XPLA3• CoolRunner-II
IntroductionThis design element is a 16-bit data registers. When the clock enable (CE) input is High, and the synchronousreset (R) input is Low, the data on the data inputs (D) is transferred to the corresponding data outputs (Q0)during the Low-to-High clock (C) transition. When R is High, it overrides all other inputs and resets the dataoutputs (Q) Low on the Low-to-High clock transition. When CE is Low, clock transitions are ignored.
This register is asynchronously cleared, outputs Low, when power is applied. For CPLD devices, you cansimulate power-on by applying a High-level pulse on the PRLD global net.
Logic TableInputs Outputs
R CE Dz : D0 C Qz : Q0
1 X X ↑ 0
0 0 X X No Change
0 1 Dn ↑ Dn
z = bit-width - 1
Design Entry MethodThis design element is only for use in schematics.
Available AttributesAttribute Type Allowed Values Default Description
INIT Binary Any 16-Bit Value All zeros Sets the initial value of Q output afterconfiguration.
For More Information• See the appropriate CPLD User Guide.• See the appropriate CPLD Data Sheets.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 345
Chapter 3: About Design Elements
FD4Macro: Multiple D Flip-Flop
Supported ArchitecturesThis design element is supported in the following architectures only:
• XC9500
• CoolRunner™ XPLA3
• CoolRunner-II
IntroductionThis design element is a multiple D-type flip-flops with data inputs (D) and data outputs (Q), with a 4-bitregister, each with a common clock (C). The data on the D inputs is loaded into the flip-flop during theLow-to-High clock (C) transition.
This flip-flop is asynchronously cleared, outputs Low, when power is applied. For CPLD devices, you cansimulate power-on by applying a High-level pulse on the PRLD global net.
Logic TableInputs Outputs
Dz : D0 C Qz : Q0
0 ↑ 0
1 ↑ 1
z = bit-width - 1
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries Guide346 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
FD4CEMacro: 4-Bit Data Register with Clock Enable and Asynchronous Clear
Supported ArchitecturesThis design element is supported in the following architectures only:• XC9500• CoolRunner™ XPLA3• CoolRunner-II
IntroductionThis design element is a 4-bit data register with clock enable and asynchronous clear. When clock enable (CE) isHigh and asynchronous clear (CLR) is Low, the data on the data inputs (D) is transferred to the correspondingdata outputs (Q) during the Low-to-High clock (C) transition. When CLR is High, it overrides all other inputsand resets the data outputs (Q) Low. When CE is Low, clock transitions are ignored.
This register is asynchronously cleared, outputs Low, when power is applied. For CPLD devices, you cansimulate power-on by applying a High-level pulse on the PRLD global net.
Logic TableInputs Outputs
CLR CE Dz : D0 C Qz : Q0
1 X X X 0
0 0 X X No Change
0 1 Dn ↑ Dn
z = bit-width - 1
Design Entry MethodThis design element is only for use in schematics.
Available AttributesAttribute Type Allowed Values Default Description
INIT Binary Any 4-Bit Value All zeros Sets the initial value of Q output afterconfiguration.
For More Information• See the appropriate CPLD User Guide.• See the appropriate CPLD Data Sheets.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 347
Chapter 3: About Design Elements
FD8Macro: Multiple D Flip-Flop
Supported ArchitecturesThis design element is supported in the following architectures only:
• XC9500
• CoolRunner™ XPLA3
• CoolRunner-II
IntroductionThis design element is a multiple D-type flip-flops with data inputs (D) and data outputs (Q), with a 8-bitregister, each with a common clock (C). The data on the D inputs is loaded into the flip-flop during theLow-to-High clock (C) transition.
This flip-flop is asynchronously cleared, outputs Low, when power is applied. For CPLD devices, you cansimulate power-on by applying a High-level pulse on the PRLD global net.
Logic TableInputs Outputs
Dz : D0 C Qz : Q0
0 ↑ 0
1 ↑ 1
z = bit-width - 1
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries Guide348 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
FD8CEMacro: 8-Bit Data Register with Clock Enable and Asynchronous Clear
Supported ArchitecturesThis design element is supported in the following architectures only:• XC9500• CoolRunner™ XPLA3• CoolRunner-II
IntroductionThis design element is a 8-bit data register with clock enable and asynchronous clear. When clock enable (CE) isHigh and asynchronous clear (CLR) is Low, the data on the data inputs (D) is transferred to the correspondingdata outputs (Q) during the Low-to-High clock (C) transition. When CLR is High, it overrides all other inputsand resets the data outputs (Q) Low. When CE is Low, clock transitions are ignored.
This register is asynchronously cleared, outputs Low, when power is applied. For CPLD devices, you cansimulate power-on by applying a High-level pulse on the PRLD global net.
Logic TableInputs Outputs
CLR CE Dz : D0 C Qz : Q0
1 X X X 0
0 0 X X No Change
0 1 Dn ↑ Dn
z = bit-width - 1
Design Entry MethodThis design element is only for use in schematics.
Available AttributesAttribute Type Allowed Values Default Description
INIT Binary Any 8-Bit Value All zeros Sets the initial value of Q output afterconfiguration.
For More Information• See the appropriate CPLD User Guide.• See the appropriate CPLD Data Sheets.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 349
Chapter 3: About Design Elements
FD8REMacro: 8-Bit Data Register with Clock Enable and Synchronous Reset
Supported ArchitecturesThis design element is supported in the following architectures only:• XC9500• CoolRunner™ XPLA3• CoolRunner-II
IntroductionThis design element is an 8-bit data register. When the clock enable (CE) input is High, and the synchronous reset(R) input is Low, the data on the data inputs (D) is transferred to the corresponding data outputs (Q0) during theLow-to-High clock (C) transition. When R is High, it overrides all other inputs and resets the data outputs (Q)Low on the Low-to-High clock transition. When CE is Low, clock transitions are ignored.
This register is asynchronously cleared, outputs Low, when power is applied. For CPLD devices, you cansimulate power-on by applying a High-level pulse on the PRLD global net.
Logic TableInputs Outputs
R CE Dz : D0 C Qz : Q0
1 X X ↑ 0
0 0 X X No Change
0 1 Dn ↑ Dn
z = bit-width - 1
Design Entry MethodThis design element is only for use in schematics.
Available AttributesAttribute Type Allowed Values Default Description
INIT Binary Any 8-Bit Value Allzeros
Sets the initial value of Q output afterconfiguration.
For More Information• See the appropriate CPLD User Guide.• See the appropriate CPLD Data Sheets.
CPLD Libraries Guide350 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
FDCMacro: D Flip-Flop with Asynchronous Clear
Supported ArchitecturesThis design element is supported in the following architectures only:
• XC9500
• CoolRunner™ XPLA3
• CoolRunner-II
IntroductionThis design element is a single D-type flip-flop with data (D) and asynchronous clear (CLR) inputs and dataoutput (Q). The asynchronous CLR, when High, overrides all other inputs and sets the (Q) output Low. The dataon the (D) input is loaded into the flip-flop when CLR is Low on the Low-to-High clock transition.
This flip-flop is asynchronously cleared, outputs Low, when power is applied. For CPLD devices, you cansimulate power-on by applying a High-level pulse on the PRLD global net.
Logic TableInputs Outputs
CLR D C Q
1 X X 0
0 D ↑ D
Design Entry MethodThis design element is only for use in schematics.
Available AttributesAttribute Type Allowed Values Default Description
INIT Binary 0, 1 0 Sets the initial value of Q output after configuration
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 351
Chapter 3: About Design Elements
FDCEPrimitive: D Flip-Flop with Clock Enable and Asynchronous Clear
Supported ArchitecturesThis design element is supported in the following architectures only:• XC9500• CoolRunner™ XPLA3• CoolRunner-II
IntroductionThis design element is a single D-type flip-flop with clock enable and asynchronous clear. When clock enable(CE) is High and asynchronous clear (CLR) is Low, the data on the data input (D) of this design element istransferred to the corresponding data output (Q) during the Low-to-High clock (C) transition. When CLR is High,it overrides all other inputs and resets the data output (Q) Low. When CE is Low, clock transitions are ignored.
For XC9500XL and XC9500XV devices, logic connected to the clock enable (CE) input may be implemented usingthe clock enable product term (p-term) in the macrocell, provided the logic can be completely implemented usingthe single p-term available for clock enable without requiring feedback from another macrocell. Only FDCE andFDPE flip-flops may take advantage of the clock-enable p-term.
This flip-flop is asynchronously cleared, outputs Low, when power is applied. For CPLD devices, you cansimulate power-on by applying a High-level pulse on the PRLD global net.
Logic TableInputs Outputs
CLR CE D C Q
1 X X X 0
0 0 X X No Change
0 1 D ↑ D
Design Entry MethodThis design element can be used in schematics.
Available AttributesAttribute Type Allowed Values Default Description
INIT Binary 0 0 Sets the initial value of Q output after configuration.
For Spartan®-6 devices, the INIT value shouldalways match the polarity of the set or reset. In thecase of FDCE, the INIT should be 0. If set to 1, anasynchronous circuit must be created to exhibit thisbehavior, which Xilinx does not recommend.
CPLD Libraries Guide352 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
VHDL Instantiation TemplateUnless they already exist, copy the following two statements and paste them before the entity declaration.
Library UNISIM;use UNISIM.vcomponents.all;
-- FDCE: Single Data Rate D Flip-Flop with Asynchronous Clear and-- Clock Enable (posedge clk). All families.-- Xilinx HDL Libraries Guide, version 11.2
FDCE_inst : FDCEgeneric map (
INIT => ’0’) -- Initial value of register (’0’ or ’1’)port map (
Q => Q, -- Data outputC => C, -- Clock inputCE => CE, -- Clock enable inputCLR => CLR, -- Asynchronous clear inputD => D -- Data input
);
-- End of FDCE_inst instantiation
Verilog Instantiation Template// FDCE: Single Data Rate D Flip-Flop with Asynchronous Clear and// Clock Enable (posedge clk).// All families.// Xilinx HDL Libraries Guide, version 11.2
FDCE #(.INIT(1’b0) // Initial value of register (1’b0 or 1’b1)
) FDCE_inst (.Q(Q), // Data output.C(C), // Clock input.CE(CE), // Clock enable input.CLR(CLR), // Asynchronous clear input.D(D) // Data input
);
// End of FDCE_inst instantiation
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 353
Chapter 3: About Design Elements
FDCPPrimitive: D Flip-Flop with Asynchronous Preset and Clear
Supported ArchitecturesThis design element is supported in the following architectures only:• XC9500• CoolRunner™ XPLA3• CoolRunner-II
IntroductionThis design element is a single D-type flip-flop with data (D), asynchronous preset (PRE) and clear (CLR)inputs, and data output (Q). The asynchronous PRE, when High, sets the (Q) output High; CLR, when High,resets the output Low. Data on the (D) input is loaded into the flip-flop when PRE and CLR are Low on theLow-to-High clock (C) transition.
This flip-flop is asynchronously cleared, outputs Low, when power is applied. For CPLD devices, you cansimulate power-on by applying a High-level pulse on the PRLD global net.
Logic TableInputs Outputs
CLR PRE D C Q
1 X X X 0
0 1 X X 1
0 0 D ↑ D
Design Entry MethodThis design element is only for use in schematics.
Available AttributesAttribute Type Allowed Values Default Description
INIT Binary 0, 1 0 Sets the initial value of Q output afterconfiguration.
CPLD Libraries Guide354 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 355
Chapter 3: About Design Elements
FDCPEPrimitive: D Flip-Flop with Clock Enable and Asynchronous Preset and Clear
Supported ArchitecturesThis design element is supported in the following architectures only:
• XC9500
• CoolRunner™ XPLA3
• CoolRunner-II
IntroductionThis design element is a single D-type flip-flop with data (D), clock enable (CE), asynchronous preset (PRE),and asynchronous clear (CLR) inputs. The asynchronous active high PRE sets the Q output High; that activehigh CLR resets the output Low and has precedence over the PRE input. Data on the D input is loaded into theflip-flop when PRE and CLR are Low and CE is High on the Low-to-High clock (C) transition. When CE is Low,the clock transitions are ignored and the previous value is retained. The FDCPE is generally implemented as aslice or IOB register within the device.
For CPLD devices, you can simulate power-on by applying a High-level pulse on the PRLD global net. For FPGAdevices, upon power-up, the initial value of this component is specified by the INIT attribute. If a subsequentGSR (Global Set/Reset) is asserted, the flop is asynchronously set to the INIT value.
Note While this device supports the use of asynchronous set and reset, it is not generally recommended to beused for in most cases. Use of asynchronous signals pose timing issues within the design that are difficult todetect and control and also have an adverse affect on logic optimization causing a larger design that can consumemore power than if a synchronous set or reset is used.
Logic TableInputs Outputs
CLR PRE CE D C Q
1 X X X X 0
0 1 X X X 1
0 0 0 X X No Change
0 0 1 D ↑ D
CPLD Libraries Guide356 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
Port DescriptionsPort Direction Width Function
Q Output 1 Data output
C Input 1 Clock input
CE Input 1 Clock enable input
CLR Input 1 Asynchronous clear input
D Input 1 Data input
PRE Input 1 Asynchronous set input
Design Entry MethodThis design element can be used in schematics.
Available AttributesAttribute Type Allowed Values Default Description
INIT Binary 0,1 0 Sets the initial value of Q output afterconfiguration and on GSR.
VHDL Instantiation TemplateUnless they already exist, copy the following two statements and paste them before the entity declaration.
Library UNISIM;use UNISIM.vcomponents.all;
-- FDCPE: Single Data Rate D Flip-Flop with Asynchronous Clear, Set and-- Clock Enable (posedge clk).-- Virtex-4/5, Spartan-3/3E/3A/3A DSP-- Xilinx HDL Libraries Guide, version 11.2
FDCPE_inst : FDCPEgeneric map (
INIT => ’0’) -- Initial value of register (’0’ or ’1’)port map (
Q => Q, -- Data outputC => C, -- Clock inputCE => CE, -- Clock enable inputCLR => CLR, -- Asynchronous clear inputD => D, -- Data inputPRE => PRE -- Asynchronous set input
);
-- End of FDCPE_inst instantiation
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 357
Chapter 3: About Design Elements
Verilog Instantiation Template// FDCPE: Single Data Rate D Flip-Flop with Asynchronous Clear, Set and// Clock Enable (posedge clk).// Virtex-4/5, Spartan-3/3E/3A/3A DSP// Xilinx HDL Libraries Guide, version 11.2
FDCPE #(.INIT(1’b0) // Initial value of register (1’b0 or 1’b1)
) FDCPE_inst (.Q(Q), // Data output.C(C), // Clock input.CE(CE), // Clock enable input.CLR(CLR), // Asynchronous clear input.D(D), // Data input.PRE(PRE) // Asynchronous set input
);
// End of FDCPE_inst instantiation
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries Guide358 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
FDDMacro: Dual Edge Triggered D Flip-Flop
Supported ArchitecturesThis design element is supported in the following architectures only:
CoolRunner™-II
IntroductionThis design element is a single dual edge triggered D-type flip-flop with data input (D) and data output (Q). Thedata on the D input is loaded into the flip-flop during the Low-to-High and the High-to-Low clock (C) transitions.
This flip-flop is asynchronously cleared, outputs Low, when power is applied. For CPLD devices, you cansimulate power-on by applying a High-level pulse on the PRLD global net.
Logic TableInputs Outputs
D C Q
0 ↑ 0
1 ↑ 1
0 ↓ 0
1 ↓ 1
Design Entry MethodThis design element is only for use in schematics.
Available AttributesAttribute Type Allowed Values Default Description
INIT Binary 0, 1 0 Sets the initial value of Q output after configuration
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 359
Chapter 3: About Design Elements
FDD16Macro: Multiple Dual Edge Triggered D Flip-Flop
Supported ArchitecturesThis design element is supported in the following architectures only:
CoolRunner™-II
IntroductionThis design element is a multiple dual edge triggered D-type flip-flop with data inputs (D) and data outputs (Q).It is a 16-bit register with a common clock (C). The data on the D inputs is loaded into the flip-flop during theLow-to-High and High-to-Low clock (C) transitions.
This flip-flop is asynchronously cleared, outputs Low, when power is applied. For CPLD devices, you cansimulate power-on by applying a High-level pulse on the PRLD global net.
Logic TableInputs Outputs
Dz : D0 C Qz : Q0
0 ↑ 0
1 ↑ 1
0 ↓ 0
1 ↓ 1
z = bit-width - 1
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries Guide360 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
FDD16CEMacro: 16-Bit Dual Edge Triggered Data Register with Clock Enable and Asynchronous Clear
Supported ArchitecturesThis design element is supported in the following architectures only:
CoolRunner™-II
IntroductionThis design element is a 16-bit data registers with clock enable and asynchronous clear. When clock enable (CE)is High and asynchronous clear (CLR) is Low, the data on the data inputs (D) is transferred to the correspondingdata outputs (Q) during the Low-to-High and High-to-Low clock (C) transitions. When CLR is High, it overridesall other inputs and resets the data outputs (Q) Low. When CE is Low, clock transitions are ignored.
This register is asynchronously cleared, outputs Low, when power is applied. For CPLD devices, you cansimulate power-on by applying a High-level pulse on the PRLD global net.
Logic TableInputs Outputs
CLR CE Dz : D0 C Qz : Q0
1 X X X 0
0 0 X X No Change
0 1 Dn ↑ Dn
0 1 Dn ↓ Dn
z = bit-width - 1
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 361
Chapter 3: About Design Elements
FDD16REMacro: 16-Bit Dual Edge Triggered Data Register with Clock Enable and Synchronous Reset
Supported ArchitecturesThis design element is supported in the following architectures only:
CoolRunner™-II
IntroductionThis design element is a 16-bit data register. When the clock enable (CE) input is High, and the synchronousreset (R) input is Low, the data on the data inputs (D) is transferred to the corresponding data outputs (Q0)during the Low-to-High or High-to-Low clock (C) transition. When R is High, it overrides all other inputs andresets the data outputs (Q) Low on the Low-to-High and High-to-Low clock transitions. When CE is Low,clock transitions are ignored.
This register is asynchronously cleared, outputs Low, when power is applied. For CPLD devices, you cansimulate power-on by applying a High-level pulse on the PRLD global net.
Logic TableInputs Outputs
R CE Dz : D0 C Qz : Q0
1 X X ↑ 0
1 X X ↓ 0
0 0 X X No Change
0 1 Dn ↑ Dn
0 1 Dn ↓ Dn
z = bit-width - 1
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries Guide362 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
FDD4Multiple Dual Edge Triggered D Flip-Flop
Supported ArchitecturesThis design element is supported in the following architectures only:
CoolRunner™-II
IntroductionThis design element is a multiple dual edge triggered D-type flip-flop with data inputs (D) and data outputs (Q).It is a 4-bit register with a common clock (C). The data on the D inputs is loaded into the flip-flop during theLow-to-High and High-to-Low clock (C) transitions.
This flip-flop is asynchronously cleared, outputs Low, when power is applied. For CPLD devices, you cansimulate power-on by applying a High-level pulse on the PRLD global net.
Logic TableInputs Outputs
Dz : D0 C Qz : Q0
0 ↑ 0
1 ↑ 1
0 ↓ 0
1 ↓ 1
z = bit-width - 1
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 363
Chapter 3: About Design Elements
FDD4CEMacro: 4-Bit Dual Edge Triggered Data Register with Clock Enable and Asynchronous Clear
Supported ArchitecturesThis design element is supported in the following architectures only:CoolRunner™-II
IntroductionThis design element is a 4-bit data registers with clock enable and asynchronous clear. When clock enable (CE) isHigh and asynchronous clear (CLR) is Low, the data on the data inputs (D) is transferred to the correspondingdata outputs (Q) during the Low-to-High and High-to-Low clock (C) transitions. When CLR is High, it overridesall other inputs and resets the data outputs (Q) Low. When CE is Low, clock transitions are ignored.
This register is asynchronously cleared, outputs Low, when power is applied. For CPLD devices, you cansimulate power-on by applying a High-level pulse on the PRLD global net.
Logic TableInputs Outputs
CLR CE Dz : D0 C Qz : Q0
1 X X X 0
0 0 X X No Change
0 1 Dn ↑ Dn
0 1 Dn ↓ Dn
z = bit-width - 1
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.• See the appropriate CPLD Data Sheets.
CPLD Libraries Guide364 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
FDD4REMacro: 4-Bit Dual Edge Triggered Data Register with Clock Enable and Synchronous Reset
Supported ArchitecturesThis design element is supported in the following architectures only:CoolRunner™-II
IntroductionThis design element is a 4-bit data register. When the clock enable (CE) input is High, and the synchronous reset(R) input is Low, the data on the data inputs (D) is transferred to the corresponding data outputs (Q0) duringthe Low-to-High or High-to-Low clock (C) transition. When R is High, it overrides all other inputs and resetsthe data outputs (Q) Low on the Low-to-High and High-to-Low clock transitions. When CE is Low, clocktransitions are ignored.
This register is asynchronously cleared, outputs Low, when power is applied. For CPLD devices, you cansimulate power-on by applying a High-level pulse on the PRLD global net.
Logic TableInputs Outputs
R CE Dz : D0 C Qz : Q0
1 X X ↑ 0
1 X X ↓ 0
0 0 X X No Change
0 1 Dn ↑ Dn
0 1 Dn ↓ Dn
z = bit-width - 1
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.• See the appropriate CPLD Data Sheets.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 365
Chapter 3: About Design Elements
FDD8Macro: Multiple Dual Edge Triggered D Flip-Flop
Supported ArchitecturesThis design element is supported in the following architectures only:
CoolRunner™-II
IntroductionThis design element is a multiple dual edge triggered D-type flip-flop with data inputs (D) and data outputs (Q).It is an 8-bit register with a common clock (C). The data on the D inputs is loaded into the flip-flop during theLow-to-High and High-to-Low clock (C) transitions.
This flip-flop is asynchronously cleared, outputs Low, when power is applied. For CPLD devices, you cansimulate power-on by applying a High-level pulse on the PRLD global net.
Logic TableInputs Outputs
Dz : D0 C Qz : Q0
0 ↑ 0
1 ↑ 1
0 ↓ 0
1 ↓ 1
z = bit-width - 1
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries Guide366 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
FDD8CEMacro: 8-Bit Dual Edge Triggered Data Register with Clock Enable and Asynchronous Clear
Supported ArchitecturesThis design element is supported in the following architectures only:
CoolRunner™-II
IntroductionThis design element is a 8-bit data registers with clock enable and asynchronous clear. When clock enable (CE) isHigh and asynchronous clear (CLR) is Low, the data on the data inputs (D) is transferred to the correspondingdata outputs (Q) during the Low-to-High and High-to-Low clock (C) transitions. When CLR is High, it overridesall other inputs and resets the data outputs (Q) Low. When CE is Low, clock transitions are ignored.
This register is asynchronously cleared, outputs Low, when power is applied. For CPLD devices, you cansimulate power-on by applying a High-level pulse on the PRLD global net.
Logic TableInputs Outputs
CLR CE Dz : D0 C Qz : Q0
1 X X X 0
0 0 X X No Change
0 1 Dn ↑ Dn
0 1 Dn ↓ Dn
z = bit-width - 1
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 367
Chapter 3: About Design Elements
FDD8REMacro: 8-Bit Dual Edge Triggered Data Register with Clock Enable and Synchronous Reset
Supported ArchitecturesThis design element is supported in the following architectures only:
CoolRunner™-II
IntroductionThis design element is a 8-bit data register. When the clock enable (CE) input is High, and the synchronous reset(R) input is Low, the data on the data inputs (D) is transferred to the corresponding data outputs (Q0) duringthe Low-to-High or High-to-Low clock (C) transition. When R is High, it overrides all other inputs and resetsthe data outputs (Q) Low on the Low-to-High and High-to-Low clock transitions. When CE is Low, clocktransitions are ignored.
This register is asynchronously cleared, outputs Low, when power is applied. For CPLD devices, you cansimulate power-on by applying a High-level pulse on the PRLD global net.
Logic TableInputs Outputs
R CE Dz : D0 C Qz : Q0
1 X X ↑ 0
1 X X ↓ 0
0 0 X X No Change
0 1 Dn ↑ Dn
0 1 Dn ↓ Dn
z = bit-width - 1
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries Guide368 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
FDDCMacro: D Dual Edge Triggered Flip-Flop with Asynchronous Clear
Supported ArchitecturesThis design element is supported in the following architectures only:CoolRunner™-II
IntroductionThis design element is a single dual edge triggered D-type flip-flop with data (D) and asynchronous clear(CLR) inputs and data output (Q). The asynchronous CLR, when High, overrides all other inputs and sets theQ output Low. The data on the D input is loaded into the flip-flop when CLR is Low on the Low-to-Highand High-to-Low clock (C) transitions.
This flip-flop is asynchronously cleared, outputs Low, when power is applied. For CPLD devices, you cansimulate power-on by applying a High-level pulse on the PRLD global net.
Logic TableInputs Outputs
CLR D C Q
1 X X 0
0 1 ↑ 1
0 1 ↓ 1
0 0 ↑ 0
0 0 ↓ 0
Design Entry MethodThis design element is only for use in schematics.
Available AttributesAttribute Type Allowed Values Default Description
INIT Binary 0, 1 0 Sets the initial value of Q output after configuration
For More Information• See the appropriate CPLD User Guide.• See the appropriate CPLD Data Sheets.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 369
Chapter 3: About Design Elements
FDDCEPrimitive: Dual Edge Triggered D Flip-Flop with Clock Enable and Asynchronous Clear
Supported ArchitecturesThis design element is supported in the following architectures only:
CoolRunner™-II
IntroductionThis design element is a single dual edge triggered D-type flip-flop with clock enable and asynchronous clear.When clock enable (CE) is High and asynchronous clear (CLR) is Low, the data on the data input (D) ofFDDCE is transferred to the corresponding data output (Q) during the Low-to-High and High-to-Low clock(C) transitions. When CLR is High, it overrides all other inputs and resets the data output (Q) Low. WhenCE is Low, clock transitions are ignored.
Logic connected to the clock enable (CE) input may be implemented using the clock enable product term(p-term) in the macrocell, provided the logic can be completely implemented using the single p-term availablefor clock enable without requiring feedback from another macrocell. Only FDDCE and FDDPE flip-flops cantake advantage of the clock-enable p-term.
This flip-flop is asynchronously cleared, outputs Low, when power is applied. For CPLD devices, you cansimulate power-on by applying a High-level pulse on the PRLD global net.
Logic TableInputs Outputs
CLR CE D C Q
1 X X X 0
0 0 X X No Change
0 1 1 ↑ 1
0 1 0 ↑ 0
0 1 1 ↓ 1
0 1 0 ↓ 0
Design Entry MethodThis design element is only for use in schematics.
CPLD Libraries Guide370 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
Available AttributesAttribute Type Allowed Values Default Description
INIT Binary 0, 1 0 Sets the initial value of Q output after configuration
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 371
Chapter 3: About Design Elements
FDDCPPrimitive: Dual Edge Triggered D Flip-Flop Asynchronous Preset and Clear
Supported ArchitecturesThis design element is supported in the following architectures only:CoolRunner™-II
IntroductionThis design element is a single dual edge triggered D-type flip-flop with data (D), asynchronous preset (PRE)and clear (CLR) inputs, and data output (Q). The asynchronous PRE, when High, sets the Q output High; CLR,when High, resets the output Low. Data on the D input is loaded into the flip-flop when PRE and CLR are Lowon the Low-to-High and High-to-Low clock (C) transitions.
This flip-flop is asynchronously cleared, outputs Low, when power is applied. For CPLD devices, you cansimulate power-on by applying a High-level pulse on the PRLD global net.
Logic TableInputs Outputs
CLR PRE D C Q
1 X X X 0
0 1 X X 1
0 0 0 ↑ 0
0 0 1 ↑ 1
0 0 0 ↓ 0
0 0 1 ↓ 1
Design Entry MethodThis design element is only for use in schematics.
Available AttributesAttribute Type Allowed Values Default Description
INIT Binary 0, 1 0 Sets the initial value of Q output after configuration
CPLD Libraries Guide372 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 373
Chapter 3: About Design Elements
FDDCPEMacro: Dual Edge Triggered D Flip-Flop with Clock Enable and Asynchronous Preset and Clear
Supported ArchitecturesThis design element is supported in the following architectures only:CoolRunner™-II
IntroductionThis design element is a single dual edge triggered D-type flip-flop with data (D), clock enable (CE),asynchronous preset (PRE), and asynchronous clear (CLR) inputs and data output (Q). The asynchronous PRE,when High, sets the Q output High; CLR, when High, resets the output Low. Data on the D input is loadedinto the flip-flop when PRE and CLR are Low and CE is High on the Low-to-High and High-to-Low clock (C)transitions. When CE is Low, the clock transitions are ignored.
This flip-flop is asynchronously cleared, outputs Low, when power is applied. For CPLD devices, you cansimulate power-on by applying a High-level pulse on the PRLD global net.
Logic TableInputs Outputs
CLR PRE CE D C Q
1 X X X X 0
0 1 X X X 1
0 0 0 X X No Change
0 0 1 0 ↑ 0
0 0 1 1 ↑ 1
0 0 1 0 ↓ 0
0 0 1 1 ↓ 1
Design Entry MethodThis design element is only for use in schematics.
Available AttributesAttribute Type Allowed Values Default Description
INIT Binary 0, 1 0 Sets the initial value of Q output after configuration
CPLD Libraries Guide374 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 375
Chapter 3: About Design Elements
FDDPMacro: Dual Edge Triggered D Flip-Flop with Asynchronous Preset
Supported ArchitecturesThis design element is supported in the following architectures only:CoolRunner™-II
IntroductionThis design element is a single dual edge triggered D-type flip-flop with data (D) and asynchronous preset(PRE) inputs and data output (Q). The asynchronous PRE, when High, overrides all other inputs and presetsthe Q output High. The data on the D input is loaded into the flip-flop when PRE is Low on the Low-to-Highand High-to-Low clock (C) transitions.
This flip-flop is asynchronously cleared, outputs Low, when power is applied. For CPLD devices, you cansimulate power-on by applying a High-level pulse on the PRLD global net.
Logic TableInputs Outputs
PRE C D Q
1 X X 1
0 ↑ 1 1
0 ↑ 0 0
0 ↓ 1 1
0 ↓ 0 0
Design Entry MethodThis design element is only for use in schematics.
Available AttributesAttribute Type Allowed Values Default Description
INIT Binary 0, 1 0 Sets the initial value of Q output after configuration
For More Information• See the appropriate CPLD User Guide.• See the appropriate CPLD Data Sheets.
CPLD Libraries Guide376 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
FDDPEPrimitive: Dual Edge Triggered D Flip-Flop with Clock Enable and Asynchronous Preset
Supported ArchitecturesThis design element is supported in the following architectures only:CoolRunner™-II
IntroductionThis design element is a single dual edge triggered D-type flip-flop with data (D), clock enable (CE), andasynchronous preset (PRE) inputs and data output (Q). The asynchronous PRE, when High, overrides all otherinputs and sets the Q output High. Data on the D input is loaded into the flip-flop when PRE is Low and CEis High on the Low-to-High and High-to-Low clock (C) transitions. When CE is Low, the clock transitionsare ignored.
Logic connected to the clock enable (CE) input may be implemented using the clock enable product term (p-term)in the macrocell, provided the logic can be completely implemented using the single p-term available for clockenable without requiring feedback from another macrocell. Only FDDCE and FDDPE flip-flops primitives maytake advantage of the clock-enable p-term.
This flip-flop is asynchronously cleared, outputs Low, when power is applied. For CPLD devices, you cansimulate power-on by applying a High-level pulse on the PRLD global net.
Logic TableInputs Outputs
PRE CE D C Q
1 X X X 1
0 0 X X No Change
0 1 0 ↑ 0
0 1 1 ↑ 1
0 1 0 ↓ 0
0 1 1 ↓ 1
Design Entry MethodThis design element is only for use in schematics.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 377
Chapter 3: About Design Elements
Available AttributesAttribute Type Allowed Values Default Description
INIT Binary 0, 1 0 Sets the initial value of Q output after configuration
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries Guide378 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
FDDRMacro: Dual Edge Triggered D Flip-Flop with Synchronous Reset
Supported ArchitecturesThis design element is supported in the following architectures only:CoolRunner™-II
IntroductionThis design element is a single dual edge triggered D-type flip-flop with data (D) and synchronous reset (R)inputs and data output (Q). The synchronous reset (R) input, when High, overrides all other inputs and resets theQ output Low on the Low-to-High and High-to-Low clock (C) transitions. The data on the D input is loaded intothe flip-flop when R is Low during the Low-to-High or High-to-Low clock transitions.
This flip-flop is asynchronously cleared, outputs Low, when power is applied. For CPLD devices, you cansimulate power-on by applying a High-level pulse on the PRLD global net.
Logic TableInputs Outputs
R D C Q
1 X ↑ 0
1 X ↓ 0
0 1 ↑ 1
0 0 ↑ 0
0 1 ↓ 1
0 0 ↓ 0
Design Entry MethodThis design element is only for use in schematics.
Available AttributesAttribute Type Allowed Values Default Description
INIT Binary 0, 1 0 Sets the initial value of Q output after configuration
For More Information• See the appropriate CPLD User Guide.• See the appropriate CPLD Data Sheets.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 379
Chapter 3: About Design Elements
FDDREMacro: Dual Edge Triggered D Flip-Flop with Clock Enable and Synchronous Reset
Supported ArchitecturesThis design element is supported in the following architectures only:CoolRunner™-II
IntroductionFDDRE is a single dual edge triggered D-type flip-flop with data (D), clock enable (CE), and synchronous reset(R) inputs and data output (Q). The synchronous reset (R) input, when High, overrides all other inputs and resetsthe Q output Low on the Low-to-High or High-to-Low clock (C) transition. The data on the D input is loadedinto the flip-flop when R is Low and CE is High during the Low-to-High and High-to-Low clock transitions.
This flip-flop is asynchronously cleared, outputs Low, when power is applied. For CPLD devices, you cansimulate power-on by applying a High-level pulse on the PRLD global net.
Logic TableInputs Outputs
R CE D C Q
1 X X ↑ 0
1 X X ↓ 0
0 0 X X No Change
0 1 1 ↑ 1
0 1 0 ↑ 0
0 1 1 ↓ 1
0 1 0 ↓ 0
Design Entry MethodThis design element is only for use in schematics.
Available AttributesAttribute Type Allowed Values Default Description
INIT Binary 0, 1 0 Sets the initial value of Q output after configuration
CPLD Libraries Guide380 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 381
Chapter 3: About Design Elements
FDDRSMacro: Dual Edge Triggered D Flip-Flop with Synchronous Reset and Set
Supported ArchitecturesThis design element is supported in the following architectures only:
CoolRunner™-II
IntroductionFDDRS is a single dual edge triggered D-type flip-flop with data (D), synchronous set (S), and synchronous reset(R) inputs and data output (Q). The synchronous reset (R) input, when High, overrides all other inputs and resetsthe Q output Low during the Low-to-High or High-to-Low clock (C) transitions. (Reset has precedence over Set.)When S is High and R is Low, the flip-flop is set, output High, during the Low-to-High or High-to-Low clocktransition. When R and S are Low, data on the (D) input is loaded into the flip-flop during the Low-to-High andHigh-to-Low clock transitions.
This flip-flop is asynchronously cleared, outputs Low, when power is applied. For CPLD devices, you cansimulate power-on by applying a High-level pulse on the PRLD global net.
Logic TableInputs Outputs
R S D C Q
1 X X ↑ 0
1 X X ↓ 0
0 1 X ↑ 1
0 1 X ↓ 1
0 0 1 ↑ 1
0 0 1 ↓ 1
0 0 0 ↑ 0
0 0 0 ↓ 0
Design Entry MethodThis design element is only for use in schematics.
CPLD Libraries Guide382 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
Available AttributesAttribute Type Allowed Values Default Description
INIT Binary 0, 1 0 Sets the initial value of Q output after configuration
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 383
Chapter 3: About Design Elements
FDDRSEMacro: Dual Edge Triggered D Flip-Flop with Synchronous Reset and Set and Clock Enable
Supported ArchitecturesThis design element is supported in the following architectures only:CoolRunner™-II
IntroductionFDDRSE is a single dual edge triggered D-type flip-flop with synchronous reset (R), synchronous set (S), andclock enable (CE) inputs and data output (Q). The reset (R) input, when High, overrides all other inputs andresets the Q output Low during the Low-to-High or High-to-Low clock transitions. (Reset has precedence overSet.) When the set (S) input is High and R is Low, the flip-flop is set, output High, during the Low-to-High orHigh-to-Low clock (C) transition. Data on the D input is loaded into the flip-flop when R and S are Low andCE is High during the Low-to-High and High-to-Low clock transitions.
This flip-flop is asynchronously cleared, outputs Low, when power is applied. For CPLD devices, you cansimulate power-on by applying a High-level pulse on the PRLD global net.
Logic TableInputs Outputs
R S CE D C Q
1 X X X ↑ 0
1 X X X ↓ 0
0 1 X X ↑ 1
0 1 X X ↓ 1
0 0 0 X X No Change
0 0 1 1 ↑ 1
0 0 1 0 ↑ 0
0 0 1 1 ↓ 1
0 0 1 0 ↓ 0
Design Entry MethodThis design element is only for use in schematics.
CPLD Libraries Guide384 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
Available AttributesAttribute Type Allowed Values Default Description
INIT Binary 0, 1 0 Sets the initial value of Q output after configuration
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 385
Chapter 3: About Design Elements
FDDSMacro: Dual Edge Triggered D Flip-Flop with Synchronous Set
Supported ArchitecturesThis design element is supported in the following architectures only:CoolRunner™-II
IntroductionFDDS is a single dual edge triggered D-type flip-flop with data (D) and synchronous set (S) inputs and dataoutput (Q). The synchronous set input, when High, sets the Q output High on the Low-to-High or High-to-Lowclock (C) transition. The data on the D input is loaded into the flip-flop when S is Low during the Low-to-Highand High-to-Low clock (C) transitions.
This flip-flop is asynchronously cleared, outputs Low, when power is applied. For CPLD devices, you cansimulate power-on by applying a High-level pulse on the PRLD global net.
Logic TableInputs Outputs
S D C Q
1 X ↑ 1
1 X ↓ 1
0 1 ↑ 1
0 0 ↑ 0
0 1 ↓ 1
0 0 ↓ 0
Design Entry MethodThis design element is only for use in schematics.
Available AttributesAttribute Type Allowed Values Default Description
INIT Binary 0, 1 0 Sets the initial value of Q output after configuration
CPLD Libraries Guide386 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 387
Chapter 3: About Design Elements
FDDSEMacro: D Flip-Flop with Clock Enable and Synchronous Set
Supported ArchitecturesThis design element is supported in the following architectures only:CoolRunner™-II
IntroductionFDDSE is a single dual edge triggered D-type flip-flop with data (D), clock enable (CE), and synchronous set (S)inputs and data output (Q). The synchronous set (S) input, when High, overrides the clock enable (CE) inputand sets the Q output High during the Low-to-High or High-to-Low clock (C) transition. The data on the Dinput is loaded into the flip-flop when S is Low and CE is High during the Low-to-High and High-to-Lowclock (C) transitions.
This flip-flop is asynchronously cleared, outputs Low, when power is applied. For CPLD devices, you cansimulate power-on by applying a High-level pulse on the PRLD global net.
Logic TableInputs Outputs
S CE D C Q
1 X X ↑ 1
1 X X ↓ 1
0 0 X X No Change
0 1 1 ↑ 1
0 1 0 ↑ 0
0 1 1 ↓ 1
0 1 0 ↓ 0
Design Entry MethodThis design element is only for use in schematics.
Available AttributesAttribute Type Allowed Values Default Description
INIT Binary 0, 1 0 Sets the initial value of Q output after configuration
CPLD Libraries Guide388 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 389
Chapter 3: About Design Elements
FDDSRMacro: Dual Edge Triggered D Flip-Flop with Synchronous Set and Reset
Supported ArchitecturesThis design element is supported in the following architectures only:
CoolRunner™-II
IntroductionFDDSR is a single dual edge triggered D-type flip-flop with data (D), synchronous reset (R) and synchronousset (S) inputs and data output (Q). When the set (S) input is High, it overrides all other inputs and sets the Qoutput High during the Low-to-High or High-to-Low clock transition. (Set has precedence over Reset.) Whenreset (R) is High and S is Low, the flip-flop is reset, output Low, on the Low-to-High or High-to-Low clocktransition. Data on the D input is loaded into the flip-flop when S and R are Low on the Low-to-High andHigh-to-Low clock transitions.
This flip-flop is asynchronously cleared, outputs Low, when power is applied. For CPLD devices, you cansimulate power-on by applying a High-level pulse on the PRLD global net.
Logic TableInputs Outputs
S R D C Q
1 X X ↑ 1
1 X X ↓ 1
0 1 X ↑ 0
0 1 X ↓ 0
0 0 1 ↑ 1
0 0 0 ↑ 0
0 0 1 ↓ 1
0 0 0 ↓ 0
Design Entry MethodThis design element is only for use in schematics.
CPLD Libraries Guide390 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
Available AttributesAttribute Type Allowed Values Default Description
INIT Binary 0, 1 0 Sets the initial value of Q output after configuration
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 391
Chapter 3: About Design Elements
FDDSREMacro: Dual Edge Triggered D Flip-Flop with Synchronous Set and Reset and Clock Enable
Supported ArchitecturesThis design element is supported in the following architectures only:CoolRunner™-II
IntroductionFDDSRE is a single dual edge triggered D-type flip-flop with synchronous set (S), synchronous reset (R), andclock enable (CE) inputs and data output (Q). When synchronous set (S) is High, it overrides all other inputs andsets the Q output High during the Low-to-High or High-to-Low clock transition. (Set has precedence over Reset.)When synchronous reset (R) is High and S is Low, output Q is reset Low during the Low-to-High or High-to-Lowclock transition. Data is loaded into the flip-flop when S and R are Low and CE is High during the Low-to-Highand High-to-Low clock transitions. When CE is Low, clock transitions are ignored.
This flip-flop is asynchronously cleared, outputs Low, when power is applied. For CPLD devices, you cansimulate power-on by applying a High-level pulse on the PRLD global net.
Logic TableInputs Outputs
S R CE D C Q
1 X X X ↑ 1
1 X X X ↓ 1
0 1 X X ↑ 0
0 1 X X ↓ 0
0 0 0 X X No Change
0 0 1 1 ↑ 1
0 0 1 0 ↑ 0
0 0 1 1 ↓ 1
0 0 1 0 ↓ 0
Design Entry MethodThis design element is only for use in schematics.
CPLD Libraries Guide392 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
Available AttributesAttribute Type Allowed Values Default Description
INIT Binary 0, 1 0 Sets the initial value of Q output after configuration
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 393
Chapter 3: About Design Elements
FDPMacro: D Flip-Flop with Asynchronous Preset
Supported ArchitecturesThis design element is supported in the following architectures only:• XC9500• CoolRunner™ XPLA3• CoolRunner-II
IntroductionThis design element is a single D-type flip-flop with data (D) and asynchronous preset (PRE) inputs and dataoutput (Q). The asynchronous PRE, when High, overrides all other inputs and presets the (Q) output High. Thedata on the (D) input is loaded into the flip-flop when PRE is Low on the Low-to-High clock (C) transition.
For CPLD devices, this flip-flop is asynchronously cleared, output Low, when power is applied. You can simulatepower-on by applying a High-level pulse on the PRLD global net.
Logic TableInputs Outputs
PRE C D Q
1 X X 1
0 ↑ D D
Design Entry MethodThis design element is only for use in schematics.
Available AttributesAttribute Type Allowed Values Default Description
INIT Binary 0, 1 1 Sets the initial value of Q output after configuration
For More Information• See the appropriate CPLD User Guide.• See the appropriate CPLD Data Sheets.
CPLD Libraries Guide394 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
FDPEPrimitive: D Flip-Flop with Clock Enable and Asynchronous Preset
Supported ArchitecturesThis design element is supported in the following architectures only:• XC9500• CoolRunner™ XPLA3• CoolRunner-II
IntroductionThis design element is a single D-type flip-flop with data (D), clock enable (CE), and asynchronous preset(PRE) inputs and data output (Q). The asynchronous PRE, when High, overrides all other inputs and sets the(Q) output High. Data on the (D) input is loaded into the flip-flop when PRE is Low and CE is High on theLow-to-High clock (C) transition. When CE is Low, the clock transitions are ignored.
For CPLD devices, this flip-flop is asynchronously cleared, output Low, when power is applied. You can simulatepower-on by applying a High-level pulse on the PRLD global net.
Logic TableInputs Outputs
PRE CE D C Q
1 X X X 1
0 0 X X No Change
0 1 D ↑ D
Design Entry MethodThis design element is only for use in schematics.
Available AttributesAttribute Type Allowed Values Default Description
INIT Binary 1 1 Sets the initial value of Q output after configuration.
For Spartan®-6 devices the INIT value should alwaysmatch the polarity of the set or reset. In the case ofFDPE, the init should be 1. If set to 0, an asynchronouscircuit must be created to exhibit this behavior, whichXilinx does not recommend.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 395
Chapter 3: About Design Elements
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries Guide396 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
FDRMacro: D Flip-Flop with Synchronous Reset
Supported ArchitecturesThis design element is supported in the following architectures only:• XC9500• CoolRunner™ XPLA3• CoolRunner-II
IntroductionThis design element is a single D-type flip-flop with data (D) and synchronous reset (R) inputs and data output(Q). The synchronous reset (R) input, when High, overrides all other inputs and resets the (Q) output Low onthe Low-to-High clock (C) transition. The data on the (D) input is loaded into the flip-flop when R is Lowduring the Low-to- High clock transition.
This flip-flop is asynchronously cleared, outputs Low, when power is applied. For CPLD devices, you cansimulate power-on by applying a High-level pulse on the PRLD global net.
Logic TableInputs Outputs
R D C Q
1 X ↑ 0
0 D ↑ D
Design Entry MethodThis design element is only for use in schematics.
Available Attributes
Attribute TypeAllowedValues Default Description
INIT Binary 0, 1 0 Sets the initial value ofQ output after configuration
For More Information• See the appropriate CPLD User Guide.• See the appropriate CPLD Data Sheets.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 397
Chapter 3: About Design Elements
FDREMacro: D Flip-Flop with Clock Enable and Synchronous Reset
Supported ArchitecturesThis design element is supported in the following architectures only:
• XC9500
• CoolRunner™ XPLA3
• CoolRunner-II
IntroductionThis design element is a single D-type flip-flop with data (D), clock enable (CE), and synchronous reset (R) inputsand data output (Q). The synchronous reset (R) input, when High, overrides all other inputs and resets the (Q)output Low on the Low-to-High clock (C) transition. The data on the (D) input is loaded into the flip-flop when Ris Low and CE is High during the Low-to-High clock transition.
This flip-flop is asynchronously cleared, outputs Low, when power is applied. For CPLD devices, you cansimulate power-on by applying a High-level pulse on the PRLD global net.
Logic TableInputs Outputs
R CE D C Q
1 X X ↑ 0
0 0 X X No Change
0 1 D ↑ D
Design Entry MethodThis design element is only for use in schematics.
Available AttributesAttribute Type Allowed Values Default Description
INIT Binary 0 0 Sets the initial value of Q output after configuration.
For Spartan®-6 the INIT value should always matchthe polarity of the set or reset. In the case of FDRE, theINIT should be 0. If set to 1, extra logic is inserted.
CPLD Libraries Guide398 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 399
Chapter 3: About Design Elements
FDRSMacro: D Flip-Flop with Synchronous Reset and Set
Supported ArchitecturesThis design element is supported in the following architectures only:• XC9500• CoolRunner™ XPLA3• CoolRunner-II
IntroductionFDRS is a single D-type flip-flop with data (D), synchronous set (S), and synchronous reset (R) inputs and dataoutput (Q). The synchronous reset (R) input, when High, overrides all other inputs and resets the (Q) output Lowduring the Low-to-High clock (C) transition. (Reset has precedence over Set.) When S is High and R is Low, theflip-flop is set, output High, during the Low-to-High clock transition. When R and S are Low, data on the (D)input is loaded into the flip-flop during the Low-to-High clock transition.
This flip-flop is asynchronously cleared, outputs Low, when power is applied. For CPLD devices, you cansimulate power-on by applying a High-level pulse on the PRLD global net.
Logic TableInputs Outputs
R S D C Q
1 X X ↓ 0
0 1 X ↓ 1
0 0 D ↓ D
Design Entry MethodThis design element is only for use in schematics.
Available Attributes
Attribute TypeAllowedValues Default Description
IN Binary 0, 1 0 Sets the initial value of Q output after configuration.
CPLD Libraries Guide400 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 401
Chapter 3: About Design Elements
FDRSEMacro: D Flip-Flop with Synchronous Reset and Set and Clock Enable
Supported ArchitecturesThis design element is supported in the following architectures only:• XC9500• CoolRunner™ XPLA3• CoolRunner-II
IntroductionFDRSE is a single D-type flip-flop with synchronous reset (R), synchronous set (S), clock enable (CE) inputs.The reset (R) input, when High, overrides all other inputs and resets the Q output Low during the Low-to-Highclock transition. (Reset has precedence over Set.) When the set (S) input is High and R is Low, the flip-flop is set,output High, during the Low-to-High clock (C) transition. Data on the D input is loaded into the flip-flop whenR and S are Low and CE is High during the Low-to-High clock transition.
Upon power-up, the initial value of this component is specified by the INIT attribute. If a subsequent GSR(Global Set/Reset) is asserted, the flop is asynchronously set to the INIT value.
Logic TableInputs Outputs
R S CE D C Q
1 X X X ↑ 0
0 1 X X ↑ 1
0 0 0 X X No Change
0 0 1 1 ↑ 1
0 0 1 0 ↑ 0
Design Entry MethodThis design element can be used in schematics.
Available AttributesAttribute Type Allowed Values Default Description
INIT Binary 0, 1 0 Sets the initial value of Q output after configuration and on GSR.
CPLD Libraries Guide402 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
VHDL Instantiation TemplateUnless they already exist, copy the following two statements and paste them before the entity declaration.
Library UNISIM;use UNISIM.vcomponents.all;
-- FDRSE: Single Data Rate D Flip-Flop with Synchronous Clear, Set and-- Clock Enable (posedge clk).-- Virtex-4/5, Spartan-3/3E/3A/3A DSP-- Xilinx HDL Libraries Guide, version 11.2
FDRSE_inst : FDRSEgeneric map (
INIT => ’0’) -- Initial value of register (’0’ or ’1’)port map (
Q => Q, -- Data outputC => C, -- Clock inputCE => CE, -- Clock enable inputD => D, -- Data inputR => R, -- Synchronous reset inputS => S -- Synchronous set input
);
-- End of FDRSE_inst instantiation
Verilog Instantiation Template// FDRSE: Single Data Rate D Flip-Flop with Synchronous Clear, Set and// Clock Enable (posedge clk).// Virtex-4/5, Spartan-3/3E/3A/3A DSP// Xilinx HDL Libraries Guide, version 11.2
FDRSE #(.INIT(1’b0) // Initial value of register (1’b0 or 1’b1)
) FDRSE_inst (.Q(Q), // Data output.C(C), // Clock input.CE(CE), // Clock enable input.D(D), // Data input.R(R), // Synchronous reset input.S(S) // Synchronous set input
);
// End of FDRSE_inst instantiation
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 403
Chapter 3: About Design Elements
FDSMacro: D Flip-Flop with Synchronous Set
Supported ArchitecturesThis design element is supported in the following architectures only:• XC9500• CoolRunner™ XPLA3• CoolRunner-II
IntroductionFDS is a single D-type flip-flop with data (D) and synchronous set (S) inputs and data output (Q). Thesynchronous set input, when High, sets the Q output High on the Low-to-High clock (C) transition. The data onthe D input is loaded into the flip-flop when S is Low during the Low-to-High clock (C) transition.
For CPLD devices, this flip-flop is asynchronously cleared, output Low, when power is applied. You can simulatepower-on by applying a High-level pulse on the PRLD global net.
Logic TableInputs Outputs
S D C Q
1 X ↑ 1
0 D ↑ D
Design Entry MethodThis design element is only for use in schematics.
Available Attributes
Attribute TypeAllowedValues Default Description
INIT Binary 0, 1 1 Sets the initial value of Q output after configuration.
For More Information• See the appropriate CPLD User Guide.• See the appropriate CPLD Data Sheets.
CPLD Libraries Guide404 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
FDSEMacro: D Flip-Flop with Clock Enable and Synchronous Set
Supported ArchitecturesThis design element is supported in the following architectures only:• XC9500• CoolRunner™ XPLA3• CoolRunner-II
IntroductionFDSE is a single D-type flip-flop with data (D), clock enable (CE), and synchronous set (S) inputs and data output(Q). The synchronous set (S) input, when High, overrides the clock enable (CE) input and sets the Q output Highduring the Low-to-High clock (C) transition. The data on the D input is loaded into the flip-flop when S is Lowand CE is High during the Low-to-High clock (C) transition.
For CPLD devices, this flip-flop is asynchronously cleared, output Low, when power is applied. You can simulatepower-on by applying a High-level pulse on the PRLD global net.
Logic TableInputs Outputs
S CE D C Q
1 X X ↑ 1
0 0 X X No Change
0 1 D ↑ D
Design Entry MethodThis design element is only for use in schematics.
Available Attributes
Attribute TypeAllowedValues Default Description
INIT Binary 1 1 Sets the initial value of Q output after configuration.
For Spartan®-6 devices the INIT value should always match thepolarity of the set or reset. In the case of FDSE, the init should be 1.If set to 0, extra logic is inserted.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 405
Chapter 3: About Design Elements
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries Guide406 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
FDSRD Flip-Flop with Synchronous Set and Reset
Supported ArchitecturesThis design element is supported in the following architectures only:• XC9500• CoolRunner™ XPLA3• CoolRunner-II
IntroductionFDSR is a single D-type flip-flop with data (D), synchronous reset (R) and synchronous set (S) inputs and dataoutput (Q). When the set (S) input is High, it overrides all other inputs and sets the Q output High during theLow-to-High clock transition. (Set has precedence over Reset.) When reset (R) is High and S is Low, the flip-flopis reset, output Low, on the Low-to-High clock transition. Data on the D input is loaded into the flip-flop when Sand R are Low on the Low-to-High clock transition.
This flip-flop is asynchronously cleared, outputs Low, when power is applied. For CPLD devices, you cansimulate power-on by applying a High-level pulse on the PRLD global net.
Logic TableInputs Outputs
S R D C Q
1 X X ↑ 1
0 1 X ↑ 0
0 0 1 ↑ 1
0 0 0 ↑ 0
Design Entry MethodThis design element is only for use in schematics.
Available AttributesAttribute Type Allowed Values Default Description
INIT Binary 0, 1 0 Sets the initial value of Q output after configuration
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 407
Chapter 3: About Design Elements
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries Guide408 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
FDSREMacro: D Flip-Flop with Synchronous Set and Reset and Clock Enable
Supported ArchitecturesThis design element is supported in the following architectures only:• XC9500• CoolRunner™ XPLA3• CoolRunner-II
IntroductionFDSRE is a single D-type flip-flop with synchronous set (S), synchronous reset (R), and clock enable (CE) inputsand data output (Q). When synchronous set (S) is High, it overrides all other inputs and sets the Q outputHigh during the Low-to-High clock transition. (Set has precedence over Reset.) When synchronous reset (R)is High and S is Low, output Q is reset Low during the Low-to-High clock transition. Data is loaded into theflip-flop when S and R are Low and CE is High during the Low-to-high clock transition. When CE is Low,clock transitions are ignored.
This flip-flop is asynchronously cleared, outputs Low, when power is applied. For CPLD devices, you cansimulate power-on by applying a High-level pulse on the PRLD global net.
Logic TableInputs Outputs
S R CE D C Q
1 X X X ↑ 1
0 1 X X ↑ 0
0 0 0 X X No Change
0 0 1 1 ↑ 1
0 0 1 0 ↑ 0
Design Entry MethodThis design element is only for use in schematics.
Available AttributesAttribute Type Allowed Values Default Description
INIT Binary 0, 1 0 Sets the initial value of Q output after configuration
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 409
Chapter 3: About Design Elements
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries Guide410 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
FJKCMacro: J-K Flip-Flop with Asynchronous Clear
Supported ArchitecturesThis design element is supported in the following architectures only:• XC9500• CoolRunner™ XPLA3• CoolRunner-II
IntroductionThis design element is a single J-K-type flip-flop with J, K, and asynchronous clear (CLR) inputs and data output(Q). The asynchronous clear (CLR) input, when High, overrides all other inputs and resets the Q output Low.When CLR is Low, the output responds to the state of the J and K inputs, as shown in the following logictable, during the Low-to-High clock (C) transition.
This flip-flop is asynchronously cleared, outputs Low, when power is applied. For CPLD devices, you cansimulate power-on by applying a High-level pulse on the PRLD global net.
Logic TableInputs Outputs
CLR J K C Q
1 X X X 0
0 0 0 ↑ No Change
0 0 1 ↑ 0
0 1 0 ↑ 1
0 1 1 ↑ Toggle
Design Entry MethodThis design element is only for use in schematics.
Available AttributesAttribute Type Allowed Values Default Description
INIT Binary 0, 1 0 Sets the initial value of Q output after configuration
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 411
Chapter 3: About Design Elements
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries Guide412 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
FJKCEMacro: J-K Flip-Flop with Clock Enable and Asynchronous Clear
Supported ArchitecturesThis design element is supported in the following architectures only:• XC9500• CoolRunner™ XPLA3• CoolRunner-II
IntroductionThis design element is a single J-K-type flip-flop with J, K, clock enable (CE), and asynchronous clear (CLR)inputs and data output (Q). The asynchronous clear (CLR), when High, overrides all other inputs and resets theQ output Low. When CLR is Low and CE is High, Q responds to the state of the J and K inputs, as shown in thefollowing logic table, during the Low-to-High clock transition. When CE is Low, the clock transitions are ignored.
This flip-flop is asynchronously cleared, outputs Low, when power is applied. For CPLD devices, you cansimulate power-on by applying a High-level pulse on the PRLD global net.
Logic TableInputs Outputs
CLR CE J K C Q
1 X X X X 0
0 0 X X X No Change
0 1 0 0 X No Change
0 1 0 1 ↑ 0
0 1 1 0 ↑ 1
0 1 1 1 ↑ Toggle
Design Entry MethodThis design element is only for use in schematics.
Available AttributesAttribute Type Allowed Values Default Description
INIT Binary 0, 1 0 Sets the initial value of Q output after configuration
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 413
Chapter 3: About Design Elements
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries Guide414 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
FJKCPMacro: J-K Flip-Flop with Asynchronous Clear and Preset
Supported ArchitecturesThis design element is supported in the following architectures only:
• XC9500
• CoolRunner™ XPLA3
• CoolRunner-II
IntroductionThis design element is a single J-K-type flip-flop with J, K, asynchronous clear (CLR), and asynchronous preset(PRE) inputs and data output (Q). When the asynchronous clear (CLR) is High, all other inputs are ignored andQ is reset 0. The asynchronous preset (PRE), when High, and CLR set to Low overrides all other inputs andsets the Q output High. When CLR and PRE are Low, Q responds to the state of the J and K inputs during theLow-to-High clock transition, as shown in the following logic table.
This flip-flop is asynchronously cleared, outputs Low, when power is applied. For CPLD devices, you cansimulate power-on by applying a High-level pulse on the PRLD global net.
Logic TableInputs Outputs
CLR PRE J K C Q
1 X X X X 0
0 1 X X X 1
0 0 0 0 X No Change
0 0 0 1 ↑ 0
0 0 1 0 ↑ 1
0 0 1 1 ↑ Toggle
Design Entry MethodThis design element is only for use in schematics.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 415
Chapter 3: About Design Elements
Available AttributesAttribute Type Allowed Values Default Description
INIT Binary 0, 1 0 Sets the initial value of Q output after configuration
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries Guide416 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
FJKCPEMacro: J-K Flip-Flop with Asynchronous Clear and Preset and Clock Enable
Supported ArchitecturesThis design element is supported in the following architectures only:• XC9500• CoolRunner™ XPLA3• CoolRunner-II
IntroductionThis design element is a single J-K-type flip-flop with J, K, asynchronous clear (CLR), asynchronous preset(PRE), and clock enable (CE) inputs and data output (Q). When the asynchronous clear (CLR) is High, all otherinputs are ignored and Q is reset 0. The asynchronous preset (PRE), when High, and CLR set to Low overridesall other inputs and sets the Q output High. When CLR and PRE are Low and CE is High, Q responds to thestate of the J and K inputs, as shown in the following logic table, during the Low-to-High clock transition. Clocktransitions are ignored when CE is Low.
This flip-flop is asynchronously cleared, outputs Low, when power is applied. For CPLD devices, you cansimulate power-on by applying a High-level pulse on the PRLD global net.
Logic TableInputs Outputs
CLR PRE CE J K C Q
1 X X X X X 0
0 1 X X X X 1
0 0 0 0 X X No Change
0 0 1 0 0 X No Change
0 0 1 0 1 ¦ 0
0 0 1 1 0 ¦ 1
0 0 1 1 1 ¦ Toggle
Design Entry MethodThis design element is only for use in schematics.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 417
Chapter 3: About Design Elements
Available AttributesAttribute Type Allowed Values Default Description
INIT Binary 0, 1 0 Sets the initial value of Q output after configuration
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries Guide418 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
FJKPMacro: J-K Flip-Flop with Asynchronous Preset
Supported ArchitecturesThis design element is supported in the following architectures only:• XC9500• CoolRunner™ XPLA3• CoolRunner-II
IntroductionThis design element is a single J-K-type flip-flop with J, K, and asynchronous preset (PRE) inputs and dataoutput (Q). The asynchronous preset (PRE) input, when High, overrides all other inputs and sets the (Q) outputHigh. When (PRE) is Low, the (Q) output responds to the state of the J and K inputs, as shown in the followinglogic table, during the Low-to-High clock transition.
For CPLD devices, this flip-flop is asynchronously cleared, output Low, when power is applied. You can simulatepower-on by applying a High-level pulse on the PRLD global net.
Logic TableInputs Outputs
PRE J K C Q
1 X X X 1
0 0 0 X No Change
0 0 1 ↑ 0
0 1 0 ↑ 1
0 1 1 ↑ Toggle
Design Entry MethodThis design element is only for use in schematics.
Available AttributesAttribute Type Allowed Values Default Description
INIT Binary 0, 1 1 Sets the initial value of Q output after configuration
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 419
Chapter 3: About Design Elements
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries Guide420 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
FJKPEMacro: J-K Flip-Flop with Clock Enable and Asynchronous Preset
Supported ArchitecturesThis design element is supported in the following architectures only:
• XC9500
• CoolRunner™ XPLA3
• CoolRunner-II
IntroductionThis design element is a single J-K-type flip-flop with J, K, clock enable (CE), and asynchronous preset (PRE)inputs and data output (Q). The asynchronous preset (PRE), when High, overrides all other inputs and sets the(Q) output High. When (PRE) is Low and (CE) is High, the (Q) output responds to the state of the J and Kinputs, as shown in the logic table, during the Low-to-High clock (C) transition. When (CE) is Low, clocktransitions are ignored.
For CPLD devices, this flip-flop is asynchronously cleared, output Low, when power is applied. You can simulatepower-on by applying a High-level pulse on the PRLD global net.
Logic TableInputs Outputs
PRE CE J K C Q
1 X X X X 1
0 0 X X X No Change
0 1 0 0 X No Change
0 1 0 1 ↑ 0
0 1 1 0 ↑ 1
0 1 1 1 ↑ Toggle
Design Entry MethodThis design element is only for use in schematics.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 421
Chapter 3: About Design Elements
Available AttributesAttribute Type Allowed Values Default Description
INIT Binary 0, 1 1 Sets the initial value of Q output after configuration
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries Guide422 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
FJKRSEMacro: J-K Flip-Flop with Clock Enable and Synchronous Reset and Set
Supported ArchitecturesThis design element is supported in the following architectures only:• XC9500• CoolRunner™ XPLA3• CoolRunner-II
IntroductionThis design element is a single J-K-type flip-flop with J, K, synchronous reset (R), synchronous set (S), and clockenable (CE) inputs and data output (Q). When synchronous reset (R) is High during the Low-to-High clock (C)transition, all other inputs are ignored and output (Q) is reset Low. When synchronous set (S) is High and (R) isLow, output (Q) is set High. When (R) and (S) are Low and (CE) is High, output (Q) responds to the state ofthe J and K inputs, according to the following logic table, during the Low-to-High clock (C) transition. When(CE) is Low, clock transitions are ignored.
This flip-flop is asynchronously cleared, outputs Low, when power is applied. For CPLD devices, you cansimulate power-on by applying a High-level pulse on the PRLD global net.
Logic TableInputs Outputs
R S CE J K C Q
1 X X X X ↑ 0
0 1 X X X ↑ 1
0 0 0 X X X No Change
0 0 1 0 0 X No Change
0 0 1 0 1 ↑ 0
0 0 1 1 0 ↑ 1
0 0 1 1 0 ↑ 1
0 0 1 1 1 ↑ Toggle
Design Entry MethodThis design element is only for use in schematics.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 423
Chapter 3: About Design Elements
Available AttributesAttribute Type Allowed Values Default Description
INIT Binary 0, 1 0 Sets the initial value of Q output after configuration
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries Guide424 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
FJKSREMacro: J-K Flip-Flop with Clock Enable and Synchronous Set and Reset
Supported ArchitecturesThis design element is supported in the following architectures only:• XC9500• CoolRunner™ XPLA3• CoolRunner-II
IntroductionThis design element is a single J-K-type flip-flop with J, K, synchronous set (S), synchronous reset (R), and clockenable (CE) inputs and data output (Q). When synchronous set (S) is High during the Low-to-High clock (C)transition, all other inputs are ignored and output (Q) is set High. When synchronous reset (R) is High and (S) isLow, output (Q) is reset Low. When (S) and (R) are Low and (CE) is High, output (Q) responds to the state ofthe J and K inputs, as shown in the following logic table, during the Low-to-High clock (C) transition. When(CE) is Low, clock transitions are ignored.
This flip-flop is asynchronously cleared, outputs Low, when power is applied. For CPLD devices, you cansimulate power-on by applying a High-level pulse on the PRLD global net.
Logic TableInputs Outputs
S R CE J K C Q
1 X X X X ↑ 1
0 1 X X X ↑ 0
0 0 0 X X X No Change
0 0 1 0 0 X No Change
0 0 1 0 1 ↑ 0
0 0 1 1 0 ↑ 1
0 0 1 1 1 ↑ Toggle
Design Entry MethodThis design element is only for use in schematics.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 425
Chapter 3: About Design Elements
Available AttributesAttribute Type Allowed Values Default Description
INIT Binary 0, 1 1 Sets the initial value of Q output after configuration
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries Guide426 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
FTCMacro: Toggle Flip-Flop with Asynchronous Clear
Supported ArchitecturesThis design element is supported in the following architectures only:• XC9500• CoolRunner™ XPLA3• CoolRunner-II
IntroductionThis design element is a synchronous, resettable toggle flip-flop. The asynchronous clear (CLR) input, whenHigh, overrides all other inputs and resets the data output (Q) Low. The (Q) output toggles, or changes state,when the toggle enable (T) input is High and (CLR) is Low during the Low-to-High clock transition.
This flip-flop is asynchronously cleared, outputs Low, when power is applied. For CPLD devices, you cansimulate power-on by applying a High-level pulse on the PRLD global net.
Logic TableInputs Outputs
CLR T C Q
1 X X 0
0 0 X No Change
0 1 ↑ Toggle
Design Entry MethodYou can instantiate this element when targeting a CPLD, but not when you are targeting an FPGA.
Available AttributesAttribute Type Allowed Values Default Description
INIT Binary 0, 1 0 Sets the initial value of Q output after configuration
For More Information• See the appropriate CPLD User Guide.• See the appropriate CPLD Data Sheets.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 427
Chapter 3: About Design Elements
FTCEMacro: Toggle Flip-Flop with Clock Enable and Asynchronous Clear
Supported ArchitecturesThis design element is supported in the following architectures only:• XC9500• CoolRunner™ XPLA3• CoolRunner-II
IntroductionThis design element is a toggle flip-flop with toggle and clock enable and asynchronous clear. When theasynchronous clear (CLR) input is High, all other inputs are ignored and the data output (Q) is reset Low. WhenCLR is Low and toggle enable (T) and clock enable (CE) are High, Q output toggles, or changes state, during theLow-to-High clock (C) transition. When CE is Low, clock transitions are ignored.
This flip-flop is asynchronously cleared, outputs Low, when power is applied. For CPLD devices, you cansimulate power-on by applying a High-level pulse on the PRLD global net.
Logic TableInputs Outputs
CLR CE T C Q
1 X X X 0
0 0 X X No Change
0 1 0 X No Change
0 1 1 ↑ Toggle
Design Entry MethodThis design element is only for use in schematics.
Available AttributesAttribute Type Allowed Values Default Description
INIT Binary 0, 1 0 Sets the initial value of Q output after configuration
For More Information• See the appropriate CPLD User Guide.• See the appropriate CPLD Data Sheets.
CPLD Libraries Guide428 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
FTCLEMacro: Toggle/Loadable Flip-Flop with Clock Enable and Asynchronous Clear
Supported ArchitecturesThis design element is supported in the following architectures only:• XC9500• CoolRunner™ XPLA3• CoolRunner-II
IntroductionThis design element is a toggle/loadable flip-flop with toggle and clock enable and asynchronous clear. Whenthe asynchronous clear input (CLR) is High, all other inputs are ignored and output Q is reset Low. When loadenable input (L) is High and CLR is Low, clock enable (CE) is overridden and the data on data input (D) isloaded into the flip-flop during the Low-to-High clock (C) transition. When toggle enable (T) and CE are Highand L and CLR are Low, output Q toggles, or changes state, during the Low- to-High clock transition. WhenCE is Low, clock transitions are ignored.
This flip-flop is asynchronously cleared, outputs Low, when power is applied. For CPLD devices, you cansimulate power-on by applying a High-level pulse on the PRLD global net.
Logic TableInputs Outputs
CLR L CE T D C Q
1 X X X X X 0
0 1 X X D ↑ D
0 0 0 X X X No Change
0 0 1 0 X X No Change
0 0 1 1 X ↑ Toggle
Design Entry MethodThis design element is only for use in schematics.
Available AttributesAttribute Type Allowed Values Default Description
INIT Binary 0, 1 0 Sets the initial value of Q output after configuration
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 429
Chapter 3: About Design Elements
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries Guide430 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
FTCLEXMacro: Toggle/Loadable Flip-Flop with Clock Enable and Asynchronous Clear
Supported ArchitecturesThis design element is supported in the following architectures only:• XC9500• CoolRunner™ XPLA3• CoolRunner-II
IntroductionThis design element is a toggle/loadable flip-flop with toggle and clock enable and asynchronous clear. Whenthe asynchronous clear input (CLR) is High, all other inputs are ignored and output Q is reset Low. When loadenable input (L) is High, CLR is Low, and CE is High, the data on data input (D) is loaded into the flip-flop duringthe Low-to-High clock (C) transition. When toggle enable (T) and CE are High and L and CLR are Low, output Qtoggles, or changes state, during the Low- to-High clock transition. When CE is Low, clock transitions are ignored.
This flip-flop is asynchronously cleared, outputs Low, when power is applied. For CPLD devices, you cansimulate power-on by applying a High-level pulse on the PRLD global net.
Logic TableInputs Outputs
CLR L CE T D C Q
1 X X X X X 0
0 1 X X D ↑ D
0 0 0 X X X No Change
0 0 1 0 X X No Change
0 0 1 1 X ↑ Toggle
Design Entry MethodThis design element is only for use in schematics.
Available AttributesAttribute Type Allowed Values Default Description
INIT Binary 0, 1 0 Sets the initial value of Q output after configuration
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 431
Chapter 3: About Design Elements
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries Guide432 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
FTCPPrimitive: Toggle Flip-Flop with Asynchronous Clear and Preset
Supported ArchitecturesThis design element is supported in the following architectures only:• XC9500• CoolRunner™ XPLA3• CoolRunner-II
IntroductionThis design element is a toggle flip-flop with toggle enable and asynchronous clear and preset. When theasynchronous clear (CLR) input is High, all other inputs are ignored and the output (Q) is reset Low. Whenthe asynchronous preset (PRE) is High and CLR is Low, all other inputs are ignored and Q is set High. Whenthe toggle enable input (T) is High and CLR and PRE are Low, output Q toggles, or changes state, during theLow-to-High clock (C) transition.
This flip-flop is asynchronously cleared, outputs Low, when power is applied. For CPLD devices, you cansimulate power-on by applying a High-level pulse on the PRLD global net.
Logic TableInputs Outputs
CLR PRE T C Q
1 X X X 0
0 1 X X 1
0 0 0 X No Change
0 0 1 ↑ Toggle
Design Entry MethodThis design element is only for use in schematics.
Available AttributesAttribute Type Allowed Values Default Description
INIT Binary 0, 1 0 Sets the initial value of Q output after configuration
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 433
Chapter 3: About Design Elements
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries Guide434 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
FTCPEMacro: Toggle Flip-Flop with Clock Enable and Asynchronous Clear and Preset
Supported ArchitecturesThis design element is supported in the following architectures only:• XC9500• CoolRunner™ XPLA3• CoolRunner-II
IntroductionThis design element is a toggle flip-flop with toggle and clock enable and asynchronous clear and preset. Whenthe asynchronous clear (CLR) input is High, all other inputs are ignored and the output (Q) is reset Low. Whenthe asynchronous preset (PRE) is High and CLR is Low, all other inputs are ignored and Q is set High. When thetoggle enable input (T) and the clock enable input (CE) are High and CLR and PRE are Low, output Q toggles, orchanges state, during the Low-to-High clock (C) transition. Clock transitions are ignored when CE is Low.
This flip-flop is asynchronously cleared, outputs Low, when power is applied. For CPLD devices, you cansimulate power-on by applying a High-level pulse on the PRLD global net.
Logic TableInputs Outputs
CLR PRE CE T C Q
1 X X X X 0
0 1 X X X 1
0 0 0 X X No Change
0 0 1 0 X No Change
0 0 1 1 ↑ Toggle
Design Entry MethodThis design element is only for use in schematics.
Available AttributesAttribute Type Allowed Values Default Description
INIT Binary 0, 1 0 Sets the initial value of Q output after configuration
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 435
Chapter 3: About Design Elements
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries Guide436 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
FTCPLEMacro: Loadable Toggle Flip-Flop with Clock Enable and Asynchronous Clear and Preset
Supported ArchitecturesThis design element is supported in the following architectures only:
• XC9500
• CoolRunner™ XPLA3
• CoolRunner-II
IntroductionThis design element is a loadable toggle flip-flop with toggle and clock enable and asynchronous clear andpreset. When the asynchronous clear (CLR) input is High, all other inputs are ignored and the output (Q) is resetLow. When the asynchronous preset (PRE) is High and CLR is Low, all other inputs are ignored and Q is setHigh. When the load input (L) is High, the clock enable input (CE) is overridden and data on data input (D)is loaded into the flip-flop during the Low-to-High clock transition. When the toggle enable input (T) and theclock enable input (CE) are High and CLR, PRE, and L are Low, output Q toggles, or changes state, during theLow-to-High clock (C) transition. Clock transitions are ignored when CE is Low.
This flip-flop is asynchronously cleared, outputs Low, when power is applied. For CPLD devices, you cansimulate power-on by applying a High-level pulse on the PRLD global net.
Logic TableInputs Outputs
CLR PRE L CE T C D Q
1 X X X X X X 0
0 1 X X X X X 1
0 0 1 X X ↑ 0 0
0 0 1 X X ↑ 1 1
0 0 0 0 X X X No Change
0 0 0 1 0 X X No Change
0 0 0 1 1 ↑ X Toggle
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 437
Chapter 3: About Design Elements
Design Entry MethodThis design element is only for use in schematics.
Available AttributesAttribute Type Allowed Values Default Description
INIT Binary 0, 1 0 Sets the initial value of Q output after configuration
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries Guide438 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
FTDCEMacro: Dual-Edge Triggered Toggle Flip-Flop with Clock Enable and Asynchronous Clear
Supported ArchitecturesThis design element is supported in the following architectures only:CoolRunner™-II
IntroductionThis design element is a dual edge triggered toggle flip-flop with toggle and clock enable and asynchronous clear.When the asynchronous clear (CLR) input is High, all other inputs are ignored and the data output (Q) is resetLow. When CLR is Low and toggle enable (T) and clock enable (CE) are High, Q output toggles, or changes state,during the Low-to-High and High-to-Low clock (C) transitions. When CE is Low, clock transitions are ignored.
This flip-flop is asynchronously cleared, outputs Low, when power is applied. For CPLD devices, you cansimulate power-on by applying a High-level pulse on the PRLD global net.
Logic TableInputs Outputs
CLR CE T C Q
1 X X X 0
0 0 X X No Change
0 1 0 X No Change
0 1 1 ↑ Toggle
0 1 1 ↓ Toggle
Design Entry MethodThis design element is only for use in schematics.
Available AttributesAttribute Type Allowed Values Default Description
INIT Binary 0, 1 0 Sets the initial value of Q output after configuration
For More Information• See the appropriate CPLD User Guide.• See the appropriate CPLD Data Sheets.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 439
Chapter 3: About Design Elements
FTDCLEMacro: Dual-Edge Triggered Toggle/Loadable Flip-Flop with Clock Enable and Asynchronous Clear
Supported ArchitecturesThis design element is supported in the following architectures only:CoolRunner™-II
IntroductionThis design element is a dual edge triggered toggle/loadable flip-flop with toggle and clock enable andasynchronous clear. When the asynchronous clear input (CLR) is High, all other inputs are ignored and output Qis reset Low. When load enable input (L) is High and CLR is Low, clock enable (CE) is overridden and the dataon data input (D) is loaded into the flip-flop during the Low-to-High and High-to-Low clock (C) transitions.When toggle enable (T) and CE are High and L and CLR are Low, output Q toggles, or changes state, during theLow- to-High and High-to-Low clock transitions. When CE is Low, clock transitions are ignored.
This flip-flop is asynchronously cleared, outputs Low, when power is applied. For CPLD devices, you cansimulate power-on by applying a High-level pulse on the PRLD global net.
Logic TableInputs Outputs
CLR L CE T D C Q
1 X X X X X 0
0 1 X X 1 ↑ 1
0 1 X X 1 ↓ 1
0 1 X X 0 ↑ 0
0 1 X X 0 ↓ 0
0 0 0 X X X No Change
0 0 1 0 X X No Change
0 0 1 1 X ↑ Toggle
0 0 1 1 X ↓ Toggle
Design Entry MethodThis design element is only for use in schematics.
CPLD Libraries Guide440 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
Available AttributesAttribute Type Allowed Values Default Description
INIT Binary 0, 1 0 Sets the initial value of Q output after configuration
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 441
Chapter 3: About Design Elements
FTDCLEXMacro: Dual-Edge Triggered Toggle/Loadable Flip-Flop with Clock Enable and Asynchronous Clear
Supported ArchitecturesThis design element is supported in the following architectures only:CoolRunner™-II
IntroductionThis design element is a dual edge triggered toggle/loadable flip-flop with toggle and clock enable andasynchronous clear. When the asynchronous clear input (CLR) is High, all other inputs are ignored and output Qis reset Low. When load enable input (L) is High, CLR is Low, and CE is High, the data on data input (D) isloaded into the flip-flop during the Low-to-High and High-to-Low clock (C) transitions. When toggle enable(T) and CE are High and L and CLR are Low, output Q toggles, or changes state, during the Low- to-High andHigh-to-Low clock transitions. When CE is Low, clock transitions are ignored.
This flip-flop is asynchronously cleared, outputs Low, when power is applied. For CPLD devices, you cansimulate power-on by applying a High-level pulse on the PRLD global net.
Logic TableInputs Outputs
CLR L CE T D C Q
1 X X X X X 0
0 1 1 X 1 ↑ 1
0 1 1 X 1 ↓ 1
0 1 1 X 0 ↑ 0
0 1 1 X 0 ↓ 0
0 0 0 X X X No Change
0 0 1 0 X X No Change
0 0 1 1 X ↑ Toggle
0 0 1 1 X ↓ Toggle
Design Entry MethodThis design element is only for use in schematics.
CPLD Libraries Guide442 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
Available AttributesAttribute Type Allowed Values Default Description
INIT Binary 0, 1 0 Sets the initial value of Q output after configuration
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 443
Chapter 3: About Design Elements
FTDCPPrimitive: Dual-Edge Triggered Toggle Flip-Flop with Asynchronous Clear and Preset
Supported ArchitecturesThis design element is supported in the following architectures only:CoolRunner™-II
IntroductionThis design element is a toggle flip-flop with toggle enable and asynchronous clear and preset. When theasynchronous clear (CLR) input is High, all other inputs are ignored and the output (Q) is reset Low. Whenthe asynchronous preset (PRE) is High and CLR is Low, all other inputs are ignored and Q is set High. Whenthe toggle enable input (T) is High and CLR and PRE are Low, output Q toggles, or changes state, during theLow-to-High and High-to-Low clock (C) transition.
This flip-flop is asynchronously cleared, outputs Low, when power is applied. For CPLD devices, you cansimulate power-on by applying a High-level pulse on the PRLD global net.
Logic TableInputs Outputs
CLR PRE T C Q
1 X X X 0
0 1 X X 1
0 0 0 X No Change
0 0 1 ↑ Toggle
0 0 1 ↓ Toggle
Design Entry MethodThis design element is only for use in schematics.
Available AttributesAttribute Type Allowed Values Default Description
INIT Binary 0, 1 0 Sets the initial value of Q output after configuration
CPLD Libraries Guide444 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 445
Chapter 3: About Design Elements
FTDRSEMacro: Dual-Edge Triggered Toggle Flip-Flop with Synchronous Reset, Set, and Clock Enable
Supported ArchitecturesThis design element is supported in the following architectures only:
CoolRunner™-II
IntroductionThis design element is a dual edge triggered toggle flip-flop with toggle and clock enable and synchronous resetand set. When the synchronous reset input (R) is High, it overrides all other inputs and the data output (Q) isreset Low. When the synchronous set input (S) is High and R is Low, clock enable input (CE) is overridden andoutput Q is set High. (Reset has precedence over Set.) When toggle enable input (T) and CE are High and R andS are Low, output Q toggles, or changes state, during the Low-to-High and High-to-Low clock transitions.
This flip-flop is asynchronously cleared, outputs Low, when power is applied. For CPLD devices, you cansimulate power-on by applying a High-level pulse on the PRLD global net.
Logic TableInputs Outputs
R S CE T C Q
1 X X X ↑ 0
1 X X X ↓ 0
0 1 X X ↑ 1
0 1 X X ↓ 1
0 0 0 X X No Change
0 0 1 0 X No Change
0 0 1 1 ↑ Toggle
0 0 1 1 ↓ Toggle
Design Entry MethodThis design element is only for use in schematics.
CPLD Libraries Guide446 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
Available AttributesAttribute Type Allowed Values Default Description
INIT Binary 0, 1 0 Sets the initial value of Q output after configuration
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 447
Chapter 3: About Design Elements
FTDRSLEMacro: Dual-Edge Triggered Toggle Flip-Flop with Clock Enable and Synchronous Reset and Set
Supported ArchitecturesThis design element is supported in the following architectures only:
CoolRunner™-II
IntroductionThis design element is a dual edge triggered toggle/loadable flip-flop with toggle and clock enable andsynchronous reset and set. The synchronous reset input (R), when High, overrides all other inputs and resets thedata output (Q) Low. (Reset has precedence over Set.) When R is Low and synchronous set input (S) is High, theclock enable input (CE) is overridden and output Q is set High. When R and S are Low and load enable input (L)is High, CE is overridden and data on data input (D) is loaded into the flip-flop during the Low-to-High andHigh-to-Low clock transitions. When R, S, and L are Low and CE is High, output Q toggles, or changes state,during the Low-to-High and High-to-Low clock transitions. When CE is Low, clock transitions are ignored.
This flip-flop is asynchronously cleared, outputs Low, when power is applied. For CPLD devices, you cansimulate power-on by applying a High-level pulse on the PRLD global net.
CPLD Libraries Guide448 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
Logic TableInputs Outputs
R S L CE T D C Q
1 0 X X X X ↑ 0
1 0 X X X X ↓ 0
0 1 X X X X ↑ 1
0 1 X X X X ↓ 1
0 0 1 X X 1 ↑ 1
0 0 1 X X 1 ↓ 1
0 0 1 X X 0 ↑ 0
0 0 1 X X 0 ↓ 0
0 0 0 0 X X X No Change
0 0 0 1 0 X X No Change
0 0 0 1 1 X ↑ Toggle
0 0 0 1 1 X ↓ Toggle
Design Entry MethodThis design element is only for use in schematics.
Available AttributesAttribute Type Allowed Values Default Description
INIT Binary 0, 1 0 Sets the initial value of Q output after configuration
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 449
Chapter 3: About Design Elements
FTPMacro: Toggle Flip-Flop with Asynchronous Preset
Supported ArchitecturesThis design element is supported in the following architectures only:• XC9500• CoolRunner™ XPLA3• CoolRunner-II
IntroductionThis design element is a toggle flip-flop with toggle enable and asynchronous preset. When the asynchronouspreset (PRE) input is High, all other inputs are ignored and output (Q) is set High. When toggle-enable input (T)is High and (PRE) is Low, output (Q) toggles, or changes state, during the Low-to-High clock (C) transition.
For CPLD devices, this flip-flop is asynchronously cleared, output Low, when power is applied. You can simulatepower-on by applying a High-level pulse on the PRLD global net.
Logic TableInputs Outputs
PRE T C Q
1 X X 1
0 0 X No Change
0 1 ↑ Toggle
Design Entry MethodThis design element is only for use in schematics.
Available AttributesAttribute Type Allowed Values Default Description
INIT Binary 0, 1 1 Sets the initial value of Q output after configuration
For More Information• See the appropriate CPLD User Guide.• See the appropriate CPLD Data Sheets.
CPLD Libraries Guide450 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
FTPEMacro: Toggle Flip-Flop with Clock Enable and Asynchronous Preset
Supported ArchitecturesThis design element is supported in the following architectures only:
• XC9500
• CoolRunner™ XPLA3
• CoolRunner-II
IntroductionThis design element is a toggle flip-flop with toggle and clock enable and asynchronous preset. When theasynchronous preset (PRE) input is High, all other inputs are ignored and output (Q) is set High. When thetoggle enable input (T) is High, clock enable (CE) is High, and (PRE) is Low, output (Q) toggles, or changes state,during the Low-to-High clock transition. When (CE) is Low, clock transitions are ignored.
For CPLD devices, this flip-flop is asynchronously cleared, output Low, when power is applied. You can simulatepower-on by applying a High-level pulse on the PRLD global net.
Logic TableInputs Outputs
PRE CE T C Q
1 X X X 1
0 0 X X No Change
0 1 0 X No Change
0 1 1 ↑ Toggle
Design Entry MethodThis design element is only for use in schematics.
Available AttributesAttribute Type Allowed Values Default Description
INIT Binary 0, 1 1 Sets the initial value of Q output after configuration
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 451
Chapter 3: About Design Elements
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries Guide452 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
FTPLEMacro: Toggle/Loadable Flip-Flop with Clock Enable and Asynchronous Preset
Supported ArchitecturesThis design element is supported in the following architectures only:
• XC9500
• CoolRunner™ XPLA3
• CoolRunner-II
IntroductionThis design element is a toggle/loadable flip-flop with toggle and clock enable and asynchronous preset. Whenthe asynchronous preset input (PRE) is High, all other inputs are ignored and output (Q) is set High. When theload enable input (L) is High and (PRE) is Low, the clock enable (CE) is overridden and the data (D) is loadedinto the flip-flop during the Low-to-High clock transition. When L and PRE are Low and toggle-enable input(T) and (CE) are High, output (Q) toggles, or changes state, during the Low-to-High clock transition. When(CE) is Low, clock transitions are ignored.
For CPLD devices, this flip-flop is asynchronously cleared, output Low, when power is applied. You can simulatepower-on by applying a High-level pulse on the PRLD global net.
Logic TableInputs Outputs
PRE L CE T D C Q
1 X X X X X 1
0 1 X X D ↑ D
0 0 0 X X X No Change
0 0 1 0 X X No Change
0 0 1 1 X ↑ Toggle
Design Entry MethodThis design element is only for use in schematics.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 453
Chapter 3: About Design Elements
Available AttributesAttribute Type Allowed Values Default Description
INIT Binary 0, 1 1 Sets the initial value of Q output after configuration
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries Guide454 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
FTRSEMacro: Toggle Flip-Flop with Clock Enable and Synchronous Reset and Set
Supported ArchitecturesThis design element is supported in the following architectures only:• XC9500• CoolRunner™ XPLA3• CoolRunner-II
IntroductionThis design element is a toggle flip-flop with toggle and clock enable and synchronous reset and set. When thesynchronous reset input (R) is High, it overrides all other inputs and the data output (Q) is reset Low. When thesynchronous set input (S) is High and (R) is Low, clock enable input (CE) is overridden and output (Q) is setHigh. (Reset has precedence over Set.) When toggle enable input (T) and (CE) are High and (R) and (S) are Low,output (Q) toggles, or changes state, during the Low-to-High clock transition.
This flip-flop is asynchronously cleared, outputs Low, when power is applied. For CPLD devices, you cansimulate power-on by applying a High-level pulse on the PRLD global net.
Logic TableInputs Outputs
R S CE T C Q
1 X X X ↑ 0
0 1 X X ↑ 1
0 0 0 X X No Change
0 0 1 0 X No Change
0 0 1 1 ↑ Toggle
Design Entry MethodThis design element is only for use in schematics.
Available AttributesAttribute Type Allowed Values Default Description
INIT Binary 0, 1 0 Sets the initial value of Q output after configuration
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 455
Chapter 3: About Design Elements
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries Guide456 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
FTRSLEMacro: Toggle/Loadable Flip-Flop with Clock Enable and Synchronous Reset and Set
Supported ArchitecturesThis design element is supported in the following architectures only:
• XC9500
• CoolRunner™ XPLA3
• CoolRunner-II
IntroductionThis design element is a toggle/loadable flip-flop with toggle and clock enable and synchronous reset and set.The synchronous reset input (R), when High, overrides all other inputs and resets the data output (Q) Low.(Reset has precedence over Set.) When R is Low and synchronous set input (S) is High, the clock enable input(CE) is overridden and output Q is set High. When R and S are Low and load enable input (L) is High, CE isoverridden and data on data input (D) is loaded into the flip-flop during the Low-to-High clock transition. WhenR, S, and L are Low, CE is High and T is High, output Q toggles, or changes state, during the Low-to-High clocktransition. When CE is Low, clock transitions are ignored.
This flip-flop is asynchronously cleared, outputs Low, when power is applied. For CPLD devices, you cansimulate power-on by applying a High-level pulse on the PRLD global net.
Logic TableInputs Outputs
R S L CE T D C Q
1 0 X X X X ↑ 0
0 1 X X X X ↑ 1
0 0 1 X X 1 ↑ 1
0 0 1 X X 0 ↑ 0
0 0 0 0 X X X No Change
0 0 0 1 0 X X No Change
0 0 0 1 1 X ↑ Toggle
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 457
Chapter 3: About Design Elements
Design Entry MethodThis design element is only for use in schematics.
Available AttributesAttribute Type Allowed Values Default Description
INIT Binary 0, 1 0 Sets the initial value of Q output after configuration
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries Guide458 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
FTSREMacro: Toggle Flip-Flop with Clock Enable and Synchronous Set and Reset
Supported ArchitecturesThis design element is supported in the following architectures only:• XC9500• CoolRunner™ XPLA3• CoolRunner-II
IntroductionThis design element is a toggle flip-flop with toggle and clock enable and synchronous set and reset. Thesynchronous set input, when High, overrides all other inputs and sets data output (Q) High. (Set has precedenceover Reset.) When synchronous reset input (R) is High and S is Low, clock enable input (CE) is overridden andoutput Q is reset Low. When toggle enable input (T) and CE are High and S and R are Low, output Q toggles, orchanges state, during the Low-to-High clock transition. When CE is Low, clock transitions are ignored.
This flip-flop is asynchronously cleared, outputs Low, when power is applied. For CPLD devices, you cansimulate power-on by applying a High-level pulse on the PRLD global net.
Logic TableInputs Outputs
S R CE T C Q
1 X X X ↑ 1
0 1 X X ↑ 0
0 0 0 X X No Change
0 0 1 0 X No Change
0 0 1 1 ↑ Toggle
Design Entry MethodThis design element is only for use in schematics.
Available AttributesAttribute Type Allowed Values Default Description
INIT Binary 0, 1 1 Sets the initial value of Q output after configuration
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 459
Chapter 3: About Design Elements
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries Guide460 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
FTSRLEMacro: Toggle/Loadable Flip-Flop with Clock Enable and Synchronous Set and Reset
Supported ArchitecturesThis design element is supported in the following architectures only:• XC9500• CoolRunner™ XPLA3• CoolRunner-II
IntroductionThis design element is a toggle/loadable flip-flop with toggle and clock enable and synchronous set and reset.The synchronous set input (S), when High, overrides all other inputs and sets data output (Q) High. (Set hasprecedence over Reset.) When synchronous reset (R) is High and (S) is Low, clock enable input (CE) is overriddenand output (Q) is reset Low. When load enable input (L) is High and S and R are Low, CE is overridden and dataon data input (D) is loaded into the flip-flop during the Low-to-High clock transition. When the toggle enableinput (T) and (CE) are High and (S), (R), and (L) are Low, output (Q) toggles, or changes state, during the Low-to-High clock transition. When (CE) is Low, clock transitions are ignored.
For CPLD devices, you can simulate power-on by applying a High-level pulse on the PRLD global net.
Logic TableInputs Outputs
S R L CE T D C Q
1 X X X X X ↑ 1
0 1 X X X X ↑ 0
0 0 1 X X 1 ↑ 1
0 0 1 X X 0 ↑ 0
0 0 0 0 X X X No Change
0 0 0 1 0 X X No Change
0 0 0 1 1 X ↑ Toggle
Design Entry MethodThis design element is only for use in schematics.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 461
Chapter 3: About Design Elements
Available AttributesAttribute Type Allowed Values Default Description
INIT Binary 0, 1 1 Sets the initial value of Q output after configuration
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries Guide462 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
GNDPrimitive: Ground-Connection Signal Tag
Supported ArchitecturesThis design element is supported in the following architectures only:
• XC9500
• CoolRunner™ XPLA3
• CoolRunner-II
IntroductionThe GND signal tag, or parameter, forces a net or input function to a Low logic level. A net tied to GND cannothave any other source.
When the logic-trimming software or fitter encounters a net or input function tied to GND, it removes any logicthat is disabled by the GND signal. The GND signal is only implemented when the disabled logic cannotbe removed.
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 463
Chapter 3: About Design Elements
IBUFPrimitive: Input Buffer
Supported ArchitecturesThis design element is supported in the following architectures only:
• XC9500
• CoolRunner™ XPLA3
• CoolRunner-II
IntroductionThis design element is automatically inserted (inferred) by the synthesis tool to any signal directly connectedto a top-level input or in-out port of the design. You should generally let the synthesis tool infer this buffer.However, it can be instantiated into the design if required. In order to do so, connect the input port (I) directly tothe associated top-level input or in-out port, and connect the output port (O) to the logic sourced by that port.Modify any necessary generic maps (VHDL) or named parameter value assignment (Verilog) in order to changethe default behavior of the component.
Port DescriptionsPort Direction Width Function
O Output 1 Buffer output
I Input 1 Buffer input
Design Entry MethodThis design element can be used in schematics.
In general, this element is inferred by the synthesis tool for any specified top-level input port to the design. It isgenerally not necessary to specify them in the source code. However, if desired, they be manually instantiated byeither copying the instantiation code from the appropriate Libraries Guide HDL template and pasting it into thetop-level entity/module of your code. It is recommended to always put all I/O components on the top-level of thedesign to help facilitate hierarchical design methods. Connect the I port directly to the top-level input port of thedesign and the O port to the logic in which this input is to source. Specify the desired generic/defparam values inorder to configure the proper behavior of the buffer.
Available AttributesAttribute Type Allowed Values Default Description
IOSTANDARD String See Data Sheet. "DEFAULT" Assigns an I/O standard to the element.
CPLD Libraries Guide464 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
VHDL Instantiation TemplateUnless they already exist, copy the following two statements and paste them before the entity declaration.
Library UNISIM;use UNISIM.vcomponents.all;
-- IBUF: Single-ended Input Buffer-- All devices-- Xilinx HDL Libraries Guide, version 11.2
IBUF_inst : IBUFgeneric map (
IBUF_DELAY_VALUE => "0", -- Specify the amount of added input delay for buffer,-- "0"-"12" (Spartan-3E)-- "0"-"16" (Spartan-3A)
IFD_DELAY_VALUE => "AUTO", -- Specify the amount of added delay for input register,-- "AUTO", "0"-"6" (Spartan-3E)-- "AUTO", "0"-"8" (Spartan-3A)
IOSTANDARD => "DEFAULT")port map (
O => O, -- Buffer outputI => I -- Buffer input (connect directly to top-level port)
);
-- End of IBUF_inst instantiation
Verilog Instantiation Template// IBUF: Single-ended Input Buffer// All devices// Xilinx HDL Libraries Guide, version 11.2
IBUF #(.IBUF_DELAY_VALUE("0"), // Specify the amount of added input delay for
// the buffer: "0"-"12" (Spartan-3E)// "0"-"16" (Spartan-3A)
.IFD_DELAY_VALUE("AUTO"), // Specify the amount of added delay for input// register: "AUTO", "0"-"6" (Spartan-3E)// "AUTO", "0"-"8" (Spartan-3A)
.IOSTANDARD("DEFAULT") // Specify the input I/O standard)IBUF_inst (
.O(O), // Buffer output
.I(I) // Buffer input (connect directly to top-level port));
// End of IBUF_inst instantiation
For More Information• See the appropriate CPLD User Guide.
• See the appropriate EDK documentation.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 465
Chapter 3: About Design Elements
IBUF16Macro: 16-Bit Input Buffer
Supported ArchitecturesThis design element is supported in the following architectures only:
• XC9500
• CoolRunner™ XPLA3
• CoolRunner-II
IntroductionInput Buffers isolate the internal circuit from the signals coming into the chip. This design element is containedin input/output blocks (IOBs) and allows the specification of the particular I/O Standard to configure the I/O. Ingeneral, an this element should be used for all single-ended data input or bidirectional pins.
Design Entry MethodThis design element can be used in schematics.
In general, this element is inferred by the synthesis tool for any specified top-level input port to the design. It isgenerally not necessary to specify them in the source code. However, if desired, they be manually instantiated byeither copying the instantiation code from the appropriate Libraries Guide HDL template and pasting it into thetop-level entity/module of your code. It is recommended to always put all I/O components on the top-level of thedesign to help facilitate hierarchical design methods. Connect the I port directly to the top-level input port of thedesign and the O port to the logic in which this input is to source. Specify the desired generic/defparam values inorder to configure the proper behavior of the buffer.
Available AttributesAttribute Type Allowed Values Default Description
IOSTANDARD String See Data Sheet. "DEFAULT" Assigns an I/O standard to the element.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries Guide466 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
IBUF4Macro: 4-Bit Input Buffer
Supported ArchitecturesThis design element is supported in the following architectures only:
• XC9500
• CoolRunner™ XPLA3
• CoolRunner-II
IntroductionInput Buffers isolate the internal circuit from the signals coming into the chip. This design element is containedin input/output blocks (IOBs) and allows the specification of the particular I/O Standard to configure the I/O. Ingeneral, an this element should be used for all single-ended data input or bidirectional pins.
Design Entry MethodThis design element can be used in schematics.
In general, this element is inferred by the synthesis tool for any specified top-level input port to the design. It isgenerally not necessary to specify them in the source code. However, if desired, they be manually instantiated byeither copying the instantiation code from the appropriate Libraries Guide HDL template and pasting it into thetop-level entity/module of your code. It is recommended to always put all I/O components on the top-level of thedesign to help facilitate hierarchical design methods. Connect the I port directly to the top-level input port of thedesign and the O port to the logic in which this input is to source. Specify the desired generic/defparam values inorder to configure the proper behavior of the buffer.
Available AttributesAttribute Type Allowed Values Default Description
IOSTANDARD String See Data Sheet. "DEFAULT" Assigns an I/O standard to the element.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 467
Chapter 3: About Design Elements
IBUF8Macro: 8-Bit Input Buffer
Supported ArchitecturesThis design element is supported in the following architectures only:
• XC9500
• CoolRunner™ XPLA3
• CoolRunner-II
IntroductionInput Buffers isolate the internal circuit from the signals coming into the chip. This design element is containedin input/output blocks (IOBs) and allows the specification of the particular I/O Standard to configure the I/O. Ingeneral, an this element should be used for all single-ended data input or bidirectional pins.
Design Entry MethodThis design element can be used in schematics.
In general, this element is inferred by the synthesis tool for any specified top-level input port to the design. It isgenerally not necessary to specify them in the source code. However, if desired, they be manually instantiated byeither copying the instantiation code from the appropriate Libraries Guide HDL template and pasting it into thetop-level entity/module of your code. It is recommended to always put all I/O components on the top-level of thedesign to help facilitate hierarchical design methods. Connect the I port directly to the top-level input port of thedesign and the O port to the logic in which this input is to source. Specify the desired generic/defparam values inorder to configure the proper behavior of the buffer.
Available AttributesAttribute Type Allowed Values Default Description
IOSTANDARD String See Data Sheet. "DEFAULT" Assigns an I/O standard to the element.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries Guide468 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
INVPrimitive: Inverter
Supported ArchitecturesThis design element is supported in the following architectures only:
• XC9500
• CoolRunner™ XPLA3
• CoolRunner-II
IntroductionThis design element is a single inverter that identifies signal inversions in a schematic.
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 469
Chapter 3: About Design Elements
INV16Macro: 16 Inverters
Supported ArchitecturesThis design element is supported in the following architectures only:
• XC9500
• CoolRunner™ XPLA3
• CoolRunner-II
IntroductionThis design element is a multiple inverter that identifies signal inversions in a schematic.
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries Guide470 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
INV4Macro: Four Inverters
Supported ArchitecturesThis design element is supported in the following architectures only:
• XC9500
• CoolRunner™ XPLA3
• CoolRunner-II
IntroductionThis design element is a multiple inverter that identifies signal inversions in a schematic.
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 471
Chapter 3: About Design Elements
INV8Macro: Eight Inverters
Supported ArchitecturesThis design element is supported in the following architectures only:
• XC9500
• CoolRunner™ XPLA3
• CoolRunner-II
IntroductionThis design element is a multiple inverter that identifies signal inversions in a schematic.
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries Guide472 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
IOBUFEPrimitive: Bi-Directional Buffer
Supported ArchitecturesThis design element is supported in the following architectures only:• XC9500• CoolRunner™ XPLA3• CoolRunner-II
IntroductionThis design element is a bi-directional buffer that is a composite of the IBUF and OBUFE elements. The Ooutput is X (unknown) when IO (input/output) is Z. You can also implement IOBUFEs as interconnectionsof their component elements.
Logic TableInputs Bidirectional Outputs
E I IO O
0 0 Z X
0 1 Z X
1 0 0 0
1 1 1 1
Design Entry MethodThis design element is only for use in schematics.
VHDL Instantiation TemplateUnless they already exist, copy the following two statements and paste them before the entity declaration.
Library UNISIM;use UNISIM.vcomponents.all;
-- IOBUFE: Bi-Directional Buffer-- XC9500XL/CoolRunner-II/XPLA-3-- Xilinx HDL Language Template, version 10.1
IOBUFE_inst : IOBUFEport map (O => user_O,IO => user_IO,I => user_I,E => user_E);
-- End of IOBUFE_inst instantiation
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 473
Chapter 3: About Design Elements
Verilog Instantiation Template// IOBUFE: Bi-Directional Buffer// XC9500XL/CoolRunner-II/XPLA-3// Xilinx HDL Language Template, version 10.1
IOBUFE IOBUFE_inst (.O (user_O),.IO (user_IO),.I (user_I),.E (user_E));
// End of IOBUFE_inst instantiation
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries Guide474 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
KEEPERPrimitive: KEEPER Symbol
Supported ArchitecturesThis design element is supported in the following architectures only:
CoolRunner™-II
IntroductionThe design element is a weak keeper element that retains the value of the net connected to its bidirectional O pin.For example, if a logic 1 is being driven onto the net, KEEPER drives a weak/resistive 1 onto the net. If the netdriver is then 3-stated, KEEPER continues to drive a weak/resistive 1 onto the net.
Port DescriptionsName Direction Width Function
O Output 1-Bit Keeper output
Design Entry MethodThis design element can be used in schematics.
This element can be connected to a net in the following locations on a top-level schematic file:
• A net connected to an input IO Marker
• A net connected to both an output IO Marker and 3-statable IO element, such as an OBUFT.
VHDL Instantiation TemplateUnless they already exist, copy the following two statements and paste them before the entity declaration.
Library UNISIM;use UNISIM.vcomponents.all;
-- KEEPER: I/O Buffer Weak Keeper-- All FPGA, CoolRunner-II-- Xilinx HDL Libraries Guide, version 11.2
KEEPER_inst : KEEPERport map (
O => O -- Keeper output (connect directly to top-level port));
-- End of KEEPER_inst instantiation
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 475
Chapter 3: About Design Elements
Verilog Instantiation Template// KEEPER: I/O Buffer Weak Keeper// All FPGA, CoolRunner-II// Xilinx HDL Libraries Guide, version 11.2
KEEPER KEEPER_inst (.O(O) // Keeper output (connect directly to top-level port)
);
// End of KEEPER_inst instantiation
For More Information• See the appropriate CPLD User Guide.
• See the appropriate EDK documentation.
CPLD Libraries Guide476 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
LDPrimitive: Transparent Data Latch
Supported ArchitecturesThis design element is supported in the following architectures only:• XC9500• CoolRunner™ XPLA3• CoolRunner-II
IntroductionLD is a transparent data latch. The data output (Q) of the latch reflects the data (D) input while the gate enable(G) input is High. The data on the (D) input during the High-to-Low gate transition is stored in the latch. Thedata on the (Q) output remains unchanged as long as (G) remains Low.
This latch is asynchronously cleared, outputs Low, when power is applied. For CPLD devices, you can simulatepower-on by applying a High-level pulse on the PRLD global net.
Logic TableInputs Outputs
G D Q
1 D D
0 X No Change
↓ D D
Design Entry MethodThis design element is only for use in schematics.
Available AttributesAttribute Type Allowed Values Default Description
INIT Binary 0, 1 0 Sets the initial value of Q output after configuration
For More Information• See the appropriate CPLD User Guide.• See the appropriate CPLD Data Sheets.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 477
Chapter 3: About Design Elements
LD16Macro: Multiple Transparent Data Latch
Supported ArchitecturesThis design element is supported in the following architectures only:• XC9500• CoolRunner™ XPLA3• CoolRunner-II
IntroductionThis design element has 16 transparent data latches with a common gate enable (G). The data output (Q) of thelatch reflects the data (D) input while the gate enable (G) input is High. The data on the (D) input during theHigh-to-Low gate transition is stored in the latch. The data on the (Q) output remains unchanged as long as(G) remains Low.
This latch is asynchronously cleared, outputs Low, when power is applied. For CPLD devices, you can simulatepower-on by applying a High-level pulse on the PRLD global net.
Logic TableInputs Outputs
G D Q
1 Dn Dn
0 X No Change
↓ Dn Dn
Design Entry MethodThis design element is only for use in schematics.
Available AttributesAttribute Type Allowed Values Default Description
INIT Binary Any 16-Bit Value All zeros Sets the initial value of Q output afterconfiguration
For More Information• See the appropriate CPLD User Guide.• See the appropriate CPLD Data Sheets.
CPLD Libraries Guide478 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
LD4Macro: Multiple Transparent Data Latch
Supported ArchitecturesThis design element is supported in the following architectures only:• XC9500• CoolRunner™ XPLA3• CoolRunner-II
IntroductionThis design element has four transparent data latches with a common gate enable (G). The data output (Q) of thelatch reflects the data (D) input while the gate enable (G) input is High. The data on the (D) input during theHigh-to-Low gate transition is stored in the latch. The data on the (Q) output remains unchanged as long as(G) remains Low.
This latch is asynchronously cleared, outputs Low, when power is applied. For CPLD devices, you can simulatepower-on by applying a High-level pulse on the PRLD global net.
Logic TableInputs Outputs
G D Q
1 Dn Dn
0 X No Change
↓ Dn Dn
Design Entry MethodThis design element is only for use in schematics.
Available Attributes
Attribute TypeAllowedValues Default Description
INIT Binary Any 4-Bit Value All zeros Sets the initial value of Q output after configuration
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 479
Chapter 3: About Design Elements
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries Guide480 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
LD8Macro: Multiple Transparent Data Latch
Supported ArchitecturesThis design element is supported in the following architectures only:• XC9500• CoolRunner™ XPLA3• CoolRunner-II
IntroductionThis design element has 8 transparent data latches with a common gate enable (G). The data output (Q) of thelatch reflects the data (D) input while the gate enable (G) input is High. The data on the (D) input during theHigh-to-Low gate transition is stored in the latch. The data on the (Q) output remains unchanged as long as(G) remains Low.
This latch is asynchronously cleared, outputs Low, when power is applied. For CPLD devices, you can simulatepower-on by applying a High-level pulse on the PRLD global net.
Logic TableInputs Outputs
G D Q
1 Dn Dn
0 X No Change
↓ Dn Dn
Design Entry MethodThis design element is only for use in schematics.
Available AttributesAttribute Type Allowed Values Default Description
INIT Binary Any 8-Bit Value All zeros Sets the initial value of Q output after configuration
For More Information• See the appropriate CPLD User Guide.• See the appropriate CPLD Data Sheets.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 481
Chapter 3: About Design Elements
LDCPrimitive: Macro: Transparent Data Latch with Asynchronous Clear
Supported ArchitecturesThis design element is supported in the following architectures only:• XC9500• CoolRunner™ XPLA3• CoolRunner-II
IntroductionThis design element is a transparent data latch with asynchronous clear. When the asynchronous clear input(CLR) is High, it overrides the other inputs and resets the data (Q) output Low. (Q) reflects the data (D) inputwhile the gate enable (G) input is High and (CLR) is Low. The data on the (D) input during the High-to-Low gatetransition is stored in the latch. The data on the (Q) output remains unchanged as long as (G) remains low.
This latch is asynchronously cleared, outputs Low, when power is applied. For CPLD devices, you can simulatepower-on by applying a High-level pulse on the PRLD global net.
Logic TableInputs Outputs
CLR G D Q
1 X X 0
0 1 D D
0 0 X No Change
0 ↓ D D
Design Entry MethodThis design element is only for use in schematics.
Available AttributesAttribute Type Allowed Values Default Description
INIT Binary 0, 1 0 Sets the initial value of Q output afterconfiguration.
For More Information• See the appropriate CPLD User Guide.• See the appropriate CPLD Data Sheets.
CPLD Libraries Guide482 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
LDCPPrimitive: Transparent Data Latch with Asynchronous Clear and Preset
Supported ArchitecturesThis design element is supported in the following architectures only:• XC9500• CoolRunner™ XPLA3• CoolRunner-II
IntroductionThe design element is a transparent data latch with data (D), asynchronous clear (CLR) and preset (PRE) inputs.When CLR is High, it overrides the other inputs and resets the data (Q) output Low. For XC9500 devices, whenPRE is High and CLR is low, it presets the data (Q) output High. For CoolRunner™-II and CoolRunner™XPLA3, PRE is a lower precedence than the gate (G) or data (D) inputs, and so has no influence on them. Qreflects the data (D) input while the gate (G) input is High and CLR and PRE are Low. The data on the D inputduring the High-to-Low gate transition is stored in the latch. The data on the Q output remains unchanged aslong as G remains Low.
This latch is asynchronously cleared, outputs Low, when power is applied. For CPLD devices, you can simulatepower-on by applying a High-level pulse on the PRLD global net.
Logic TableInputs Outputs
CLR PRE G D Q
1 X X X 0
0 X 1 X 1
0 0 1 D D
0 0 0 X No Change
0 0 ↓ D D
Design Entry MethodThis design element is only for use in schematics.
Available AttributesAttribute Type Allowed Values Default Description
INIT Integer 0, 1 0 Specifies the initial value upon power-up or theassertion of GSR for the (Q) port.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 483
Chapter 3: About Design Elements
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries Guide484 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
LDGPrimitive: Transparent Datagate Latch
Supported ArchitecturesThis design element is supported in the following architectures only:
CoolRunner™-II
IntroductionThis design element is a transparent DataGate latch used for gating input signals to decrease power dissipation.The data output (Q) of the latch reflects the data (D) input while the gate enable (G) input is Low. The data onthe D input during the Low-to-High gate transition is stored in the latch. The data on the Q output remainsunchanged as long as G remains High.
The D input(s) of the LDG must be connected to a device input pad(s) and must have no other fan-outs (must notbranch). The CPLD fitter maps the G input to the device’s DataGate Enable control pin (DGE). There must beno more than one DataGate Enable signal in the design. The DataGate Enable signal may be driven either bya device input pin or any on-chip logic source. The DataGate Enable signal may be reused by other ordinarylogic in the design.
This latch is asynchronously cleared, outputs Low, when power is applied. For CPLD devices, you can simulatepower-on by applying a High-level pulse on the PRLD global net.
Logic TableInputs Outputs
G D Q
0 0 0
0 1 1
1 X No Change
↑ D D
Design Entry MethodThis design element is only for use in schematics.
Available AttributesAttribute Type Allowed Values Default Description
INIT Binary 0, 1 0 Sets the initial value of Q output after configuration
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 485
Chapter 3: About Design Elements
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries Guide486 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
LDG16Macro: 16-bit Transparent Datagate Latch
Supported ArchitecturesThis design element is supported in the following architectures only:CoolRunner™-II
IntroductionThis design element has 16 transparent DataGate latches with a common gate enable (G). These latches are usedto gate input signals in order to decrease power dissipation during periods when activity on the input pins isnot of interest to the CPLD. The data output (Q) of the latch reflects the data (D) input while the gate enable(G) input is Low. The data on the D input during the Low-to-High gate transition is stored in the latch. Thedata on the Q output remains unchanged as long as G remains High.
The D input(s) of the LDG must be connected to a device input pad(s) and must have no other fan-outs (must notbranch). The CPLD fitter maps the G input to the device’s DataGate Enable control pin (DGE). There must beno more than one DataGate Enable signal in the design. The DataGate Enable signal may be driven either bya device input pin or any on-chip logic source. The DataGate Enable signal may be reused by other ordinarylogic in the design.
This latch is asynchronously cleared, outputs Low, when power is applied. For CPLD devices, you can simulatepower-on by applying a High-level pulse on the PRLD global net.
Logic TableInputs Outputs
G D Q
0 0 0
0 1 1
1 X No Change
↑ D D
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.• See the appropriate CPLD Data Sheets.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 487
Chapter 3: About Design Elements
LDG4Macro: 4-Bit Transparent Datagate Latch
Supported ArchitecturesThis design element is supported in the following architectures only:CoolRunner™-II
IntroductionThis design element has 4 transparent DataGate latches with a common gate enable (G). These latches are usedto gate input signals in order to decrease power dissipation during periods when activity on the input pins isnot of interest to the CPLD. The data output (Q) of the latch reflects the data (D) input while the gate enable(G) input is Low. The data on the D input during the Low-to-High gate transition is stored in the latch. Thedata on the Q output remains unchanged as long as G remains High.
The D input(s) of the LDG must be connected to a device input pad(s) and must have no other fan-outs (must notbranch). The CPLD fitter maps the G input to the device’s DataGate Enable control pin (DGE). There must beno more than one DataGate Enable signal in the design. The DataGate Enable signal may be driven either bya device input pin or any on-chip logic source. The DataGate Enable signal may be reused by other ordinarylogic in the design.
This latch is asynchronously cleared, outputs Low, when power is applied. For CPLD devices, you can simulatepower-on by applying a High-level pulse on the PRLD global net.
Logic TableInputs Outputs
G D Q
0 0 0
0 1 1
1 X No Change
↑ D D
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.• See the appropriate CPLD Data Sheets.
CPLD Libraries Guide488 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
LDG8Macro: 8-Bit Transparent Datagate Latch
Supported ArchitecturesThis design element is supported in the following architectures only:CoolRunner™-II
IntroductionThis design element has 8 transparent DataGate latches with a common gate enable (G). These latches are usedto gate input signals in order to decrease power dissipation during periods when activity on the input pins isnot of interest to the CPLD. The data output (Q) of the latch reflects the data (D) input while the gate enable(G) input is Low. The data on the D input during the Low-to-High gate transition is stored in the latch. Thedata on the Q output remains unchanged as long as G remains High.
The D input(s) of the LDG must be connected to a device input pad(s) and must have no other fan-outs (must notbranch). The CPLD fitter maps the G input to the device’s DataGate Enable control pin (DGE). There must beno more than one DataGate Enable signal in the design. The DataGate Enable signal may be driven either bya device input pin or any on-chip logic source. The DataGate Enable signal may be reused by other ordinarylogic in the design.
This latch is asynchronously cleared, outputs Low, when power is applied. For CPLD devices, you can simulatepower-on by applying a High-level pulse on the PRLD global net.
Logic TableInputs Outputs
G D Q
0 0 0
0 1 1
1 X No Change
↑ D D
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.• See the appropriate CPLD Data Sheets.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 489
Chapter 3: About Design Elements
LDPPrimitive: Macro: Transparent Data Latch with Asynchronous Preset
Supported ArchitecturesThis design element is supported in the following architectures only:• XC9500• CoolRunner™ XPLA3• CoolRunner-II
IntroductionThis design element is a transparent data latch with asynchronous preset (PRE). For XC9500 devices, whenPRE is High it overrides the other inputs and presets the data (Q) output High. For CoolRunner™-II andCoolRunner™ XPLA3, PRE is a lower precedence than the gate (G) or data (D) inputs, and so has no influenceon them. Q reflects the data (D) input while gate (G) input is High and PRE is Low. The data on the (D) inputduring the High-to-Low gate transition is stored in the latch. The data on the Q output remains unchanged aslong as G remains Low.
The latch is asynchronously preset, output High, when power is applied.
Logic TableInputs Outputs
PRE G D Q
1 X X 1
0 1 0 0
0 1 1 1
0 0 X No Change
0 ↓ D D
Design Entry MethodThis design element is only for use in schematics.
Available AttributesAttribute Type Allowed Values Default Description
INIT Binary 0, 1 1 Specifies the initial value upon power-up or theassertion of GSR for the Q port.
CPLD Libraries Guide490 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 491
Chapter 3: About Design Elements
M16_1EMacro: 16-to-1 Multiplexer with Enable
Supported ArchitecturesThis design element is supported in the following architectures only:
• XC9500
• CoolRunner™ XPLA3
• CoolRunner-II
IntroductionThis design element is a 16-to-1 multiplexer with enable. When the enable input (E) is High, the M16_1Emultiplexer chooses one data bit from 16 sources (D15 : D0) under the control of the select inputs (S3 : S0). Theoutput (O) reflects the state of the selected input as shown in the logic table. When (E) is Low, the output is Low.
CPLD Libraries Guide492 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
Logic TableInputs Outputs
E S3 S2 S1 S0 D15-D0 O
0 X X X X X 0
1 0 0 0 0 D0 D0
1 0 0 0 1 D1 D1
1 0 0 1 0 D2 D2
1 0 0 1 1 D3 D3...
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
1 1 1 0 0 D12 D12
1 1 1 0 1 D13 D13
1 1 1 1 0 D14 D14
1 1 1 1 1 D15 D15
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 493
Chapter 3: About Design Elements
M2_1Macro: 2-to-1 Multiplexer
Supported ArchitecturesThis design element is supported in the following architectures only:
• XC9500
• CoolRunner™ XPLA3
• CoolRunner-II
IntroductionThis design element chooses one data bit from two sources (D1 or D0) under the control of the select input (S0).The output (O) reflects the state of the selected data input. When Low, S0 selects D0 and when High, S0 selects D1.
Logic TableInputs Outputs
S0 D1 D0 O
1 D1 X D1
0 X D0 D0
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries Guide494 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
M2_1B1Macro: 2-to-1 Multiplexer with D0 Inverted
Supported ArchitecturesThis design element is supported in the following architectures only:
• XC9500
• CoolRunner™ XPLA3
• CoolRunner-II
IntroductionThis design element chooses one data bit from two sources (D1 or D0) under the control of select input (S0).When S0 is Low, the output (O) reflects the inverted value of (D0). When S0 is High, (O) reflects the state of D1.
Logic TableInputs Outputs
S0 D1 D0 O
1 1 X 1
1 0 X 0
0 X 1 0
0 X 0 1
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 495
Chapter 3: About Design Elements
M2_1B2Macro: 2-to-1 Multiplexer with D0 and D1 Inverted
Supported ArchitecturesThis design element is supported in the following architectures only:
• XC9500
• CoolRunner™ XPLA3
• CoolRunner-II
IntroductionThis design element chooses one data bit from two sources (D1 or D0) under the control of select input (S0). WhenS0 is Low, the output (O) reflects the inverted value of D0. When S0 is High, O reflects the inverted value of D1.
Logic TableInputs Outputs
S0 D1 D0 O
1 1 X 0
1 0 X 1
0 X 1 0
0 X 0 1
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries Guide496 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
M2_1EMacro: 2-to-1 Multiplexer with Enable
Supported ArchitecturesThis design element is supported in the following architectures only:
• XC9500
• CoolRunner™ XPLA3
• CoolRunner-II
IntroductionThis design element is a 2-to-1 multiplexer with enable. When the enable input (E) is High, the M2_1E choosesone data bit from two sources (D1 or D0) under the control of select input (S0). When Low, S0 selects D0 andwhen High, S0 selects D1. When (E) is Low, the output is Low.
Logic TableInputs Outputs
E S0 D1 D0 O
0 X X X 0
1 0 X 1 1
1 0 X 0 0
1 1 1 X 1
1 1 0 X 0
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 497
Chapter 3: About Design Elements
M4_1EMacro: 4-to-1 Multiplexer with Enable
Supported ArchitecturesThis design element is supported in the following architectures only:
• XC9500
• CoolRunner™ XPLA3
• CoolRunner-II
IntroductionThis design element is a 4-to-1 multiplexer with enable. When the enable input (E) is High, the M4_1Emultiplexerchooses one data bit from four sources (D3, D2, D1, or D0) under the control of the select inputs (S1 : S0). Theoutput (O) reflects the state of the selected input as shown in the logic table. When (E) is Low, the output is Low.
Logic TableInputs Outputs
E S1 S0 D0 D1 D2 D3 O
0 X X X X X X 0
1 0 0 D0 X X X D0
1 0 1 X D1 X X D1
1 1 0 X X D2 X D2
1 1 1 X X X D3 D3
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries Guide498 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
M8_1EMacro: 8-to-1 Multiplexer with Enable
Supported ArchitecturesThis design element is supported in the following architectures only:• XC9500• CoolRunner™ XPLA3• CoolRunner-II
IntroductionThis design element is an 8-to-1 multiplexer with enable. When the enable input (E) is High, the M8_1Emultiplexer chooses one data bit from eight sources (D7 : D0) under the control of the select inputs (S2 : S0). Theoutput (O) reflects the state of the selected input as shown in the logic table. When (E) is Low, the output is Low.
Logic TableInputs Outputs
E S2 S1 S0 D7-D0 O
0 X X X X 0
1 0 0 0 D0 D0
1 0 0 1 D1 D1
1 0 1 0 D2 D2
1 0 1 1 D3 D3
1 1 0 0 D4 D4
1 1 0 1 D5 D5
1 1 1 0 D6 D6
1 1 1 1 D7 D7
Design Entry MethodThis design element is only for use in schematics.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 499
Chapter 3: About Design Elements
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries Guide500 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
NAND2Primitive: 2-Input NAND Gate with Non-Inverted Inputs
Supported ArchitecturesThis design element is supported in the following architectures only:
• XC9500
• CoolRunner™ XPLA3
• CoolRunner-II
IntroductionNAND gates of up to five inputs are available in any combination of inverting and non-inverting inputs. NANDgates of six to nine inputs, 12 inputs, and 16 inputs are available with only non-inverting inputs. To invert inputs,use external inverters. Because each input uses a CLB resource, replace gates with unused inputs with gateshaving the necessary number of inputs.
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 501
Chapter 3: About Design Elements
NAND2B1Primitive: 2-Input NAND Gate with 1 Inverted and 1 Non-Inverted Inputs
Supported ArchitecturesThis design element is supported in the following architectures only:
• XC9500
• CoolRunner™ XPLA3
• CoolRunner-II
IntroductionNAND gates of up to five inputs are available in any combination of inverting and non-inverting inputs. NANDgates of six to nine inputs, 12 inputs, and 16 inputs are available with only non-inverting inputs. To invert inputs,use external inverters. Because each input uses a CLB resource, replace gates with unused inputs with gateshaving the necessary number of inputs.
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries Guide502 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
NAND2B2Primitive: 2-Input NAND Gate with Inverted Inputs
Supported ArchitecturesThis design element is supported in the following architectures only:
• XC9500
• CoolRunner™ XPLA3
• CoolRunner-II
IntroductionNAND gates of up to five inputs are available in any combination of inverting and non-inverting inputs. NANDgates of six to nine inputs, 12 inputs, and 16 inputs are available with only non-inverting inputs. To invert inputs,use external inverters. Because each input uses a CLB resource, replace gates with unused inputs with gateshaving the necessary number of inputs.
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 503
Chapter 3: About Design Elements
NAND3Primitive: 3-Input NAND Gate with Non-Inverted Inputs
Supported ArchitecturesThis design element is supported in the following architectures only:
• XC9500
• CoolRunner™ XPLA3
• CoolRunner-II
IntroductionNAND gates of up to five inputs are available in any combination of inverting and non-inverting inputs. NANDgates of six to nine inputs, 12 inputs, and 16 inputs are available with only non-inverting inputs. To invert inputs,use external inverters. Because each input uses a CLB resource, replace gates with unused inputs with gateshaving the necessary number of inputs.
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries Guide504 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
NAND3B1Primitive: 3-Input NAND Gate with 1 Inverted and 2 Non-Inverted Inputs
Supported ArchitecturesThis design element is supported in the following architectures only:
• XC9500
• CoolRunner™ XPLA3
• CoolRunner-II
IntroductionNAND gates of up to five inputs are available in any combination of inverting and non-inverting inputs. NANDgates of six to nine inputs, 12 inputs, and 16 inputs are available with only non-inverting inputs. To invert inputs,use external inverters. Because each input uses a CLB resource, replace gates with unused inputs with gateshaving the necessary number of inputs.
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 505
Chapter 3: About Design Elements
NAND3B2Primitive: 3-Input NAND Gate with 2 Inverted and 1 Non-Inverted Inputs
Supported ArchitecturesThis design element is supported in the following architectures only:
• XC9500
• CoolRunner™ XPLA3
• CoolRunner-II
IntroductionNAND gates of up to five inputs are available in any combination of inverting and non-inverting inputs. NANDgates of six to nine inputs, 12 inputs, and 16 inputs are available with only non-inverting inputs. To invert inputs,use external inverters. Because each input uses a CLB resource, replace gates with unused inputs with gateshaving the necessary number of inputs.
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries Guide506 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
NAND3B3Primitive: 3-Input NAND Gate with Inverted Inputs
Supported ArchitecturesThis design element is supported in the following architectures only:
• XC9500
• CoolRunner™ XPLA3
• CoolRunner-II
IntroductionNAND gates of up to five inputs are available in any combination of inverting and non-inverting inputs. NANDgates of six to nine inputs, 12 inputs, and 16 inputs are available with only non-inverting inputs. To invert inputs,use external inverters. Because each input uses a CLB resource, replace gates with unused inputs with gateshaving the necessary number of inputs.
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 507
Chapter 3: About Design Elements
NAND4Primitive: 4-Input NAND Gate with Non-Inverted Inputs
Supported ArchitecturesThis design element is supported in the following architectures only:
• XC9500
• CoolRunner™ XPLA3
• CoolRunner-II
IntroductionNAND gates of up to five inputs are available in any combination of inverting and non-inverting inputs. NANDgates of six to nine inputs, 12 inputs, and 16 inputs are available with only non-inverting inputs. To invert inputs,use external inverters. Because each input uses a CLB resource, replace gates with unused inputs with gateshaving the necessary number of inputs.
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries Guide508 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
NAND4B1Primitive: 4-Input NAND Gate with 1 Inverted and 3 Non-Inverted Inputs
Supported ArchitecturesThis design element is supported in the following architectures only:
• XC9500
• CoolRunner™ XPLA3
• CoolRunner-II
IntroductionNAND gates of up to five inputs are available in any combination of inverting and non-inverting inputs. NANDgates of six to nine inputs, 12 inputs, and 16 inputs are available with only non-inverting inputs. To invert inputs,use external inverters. Because each input uses a CLB resource, replace gates with unused inputs with gateshaving the necessary number of inputs.
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 509
Chapter 3: About Design Elements
NAND4B2Primitive: 4-Input NAND Gate with 2 Inverted and 2 Non-Inverted Inputs
Supported ArchitecturesThis design element is supported in the following architectures only:
• XC9500
• CoolRunner™ XPLA3
• CoolRunner-II
IntroductionNAND gates of up to five inputs are available in any combination of inverting and non-inverting inputs. NANDgates of six to nine inputs, 12 inputs, and 16 inputs are available with only non-inverting inputs. To invert inputs,use external inverters. Because each input uses a CLB resource, replace gates with unused inputs with gateshaving the necessary number of inputs.
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries Guide510 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
NAND4B3Primitive: 4-Input NAND Gate with 3 Inverted and 1 Non-Inverted Inputs
Supported ArchitecturesThis design element is supported in the following architectures only:
• XC9500
• CoolRunner™ XPLA3
• CoolRunner-II
IntroductionNAND gates of up to five inputs are available in any combination of inverting and non-inverting inputs. NANDgates of six to nine inputs, 12 inputs, and 16 inputs are available with only non-inverting inputs. To invert inputs,use external inverters. Because each input uses a CLB resource, replace gates with unused inputs with gateshaving the necessary number of inputs.
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 511
Chapter 3: About Design Elements
NAND4B4Primitive: 4-Input NAND Gate with Inverted Inputs
Supported ArchitecturesThis design element is supported in the following architectures only:
• XC9500
• CoolRunner™ XPLA3
• CoolRunner-II
IntroductionNAND gates of up to five inputs are available in any combination of inverting and non-inverting inputs. NANDgates of six to nine inputs, 12 inputs, and 16 inputs are available with only non-inverting inputs. To invert inputs,use external inverters. Because each input uses a CLB resource, replace gates with unused inputs with gateshaving the necessary number of inputs.
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries Guide512 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
NAND5Primitive: 5-Input NAND Gate with Non-Inverted Inputs
Supported ArchitecturesThis design element is supported in the following architectures only:
• XC9500
• CoolRunner™ XPLA3
• CoolRunner-II
IntroductionNAND gates of up to five inputs are available in any combination of inverting and non-inverting inputs. NANDgates of six to nine inputs, 12 inputs, and 16 inputs are available with only non-inverting inputs. To invert inputs,use external inverters. Because each input uses a CLB resource, replace gates with unused inputs with gateshaving the necessary number of inputs.
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 513
Chapter 3: About Design Elements
NAND5B1Primitive: 5-Input NAND Gate with 1 Inverted and 4 Non-Inverted Inputs
Supported ArchitecturesThis design element is supported in the following architectures only:
• XC9500
• CoolRunner™ XPLA3
• CoolRunner-II
IntroductionNAND gates of up to five inputs are available in any combination of inverting and non-inverting inputs. NANDgates of six to nine inputs, 12 inputs, and 16 inputs are available with only non-inverting inputs. To invert inputs,use external inverters. Because each input uses a CLB resource, replace gates with unused inputs with gateshaving the necessary number of inputs.
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries Guide514 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
NAND5B2Primitive: 5-Input NAND Gate with 2 Inverted and 3 Non-Inverted Inputs
Supported ArchitecturesThis design element is supported in the following architectures only:
• XC9500
• CoolRunner™ XPLA3
• CoolRunner-II
IntroductionNAND gates of up to five inputs are available in any combination of inverting and non-inverting inputs. NANDgates of six to nine inputs, 12 inputs, and 16 inputs are available with only non-inverting inputs. To invert inputs,use external inverters. Because each input uses a CLB resource, replace gates with unused inputs with gateshaving the necessary number of inputs.
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 515
Chapter 3: About Design Elements
NAND5B3Primitive: 5-Input NAND Gate with 3 Inverted and 2 Non-Inverted Inputs
Supported ArchitecturesThis design element is supported in the following architectures only:
• XC9500
• CoolRunner™ XPLA3
• CoolRunner-II
IntroductionNAND gates of up to five inputs are available in any combination of inverting and non-inverting inputs. NANDgates of six to nine inputs, 12 inputs, and 16 inputs are available with only non-inverting inputs. To invert inputs,use external inverters. Because each input uses a CLB resource, replace gates with unused inputs with gateshaving the necessary number of inputs.
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries Guide516 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
NAND5B4Primitive: 5-Input NAND Gate with 4 Inverted and 1 Non-Inverted Inputs
Supported ArchitecturesThis design element is supported in the following architectures only:
• XC9500
• CoolRunner™ XPLA3
• CoolRunner-II
IntroductionNAND gates of up to five inputs are available in any combination of inverting and non-inverting inputs. NANDgates of six to nine inputs, 12 inputs, and 16 inputs are available with only non-inverting inputs. To invert inputs,use external inverters. Because each input uses a CLB resource, replace gates with unused inputs with gateshaving the necessary number of inputs.
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 517
Chapter 3: About Design Elements
NAND5B5Primitive: 5-Input NAND Gate with Inverted Inputs
Supported ArchitecturesThis design element is supported in the following architectures only:
• XC9500
• CoolRunner™ XPLA3
• CoolRunner-II
IntroductionNAND gates of up to five inputs are available in any combination of inverting and non-inverting inputs. NANDgates of six to nine inputs, 12 inputs, and 16 inputs are available with only non-inverting inputs. To invert inputs,use external inverters. Because each input uses a CLB resource, replace gates with unused inputs with gateshaving the necessary number of inputs.
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries Guide518 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
NAND6Macro: 6-Input NAND Gate with Non-Inverted Inputs
Supported ArchitecturesThis design element is supported in the following architectures only:
• XC9500
• CoolRunner™ XPLA3
• CoolRunner-II
IntroductionNAND gates of up to five inputs are available in any combination of inverting and non-inverting inputs. NANDgates of six to nine inputs, 12 inputs, and 16 inputs are available with only non-inverting inputs. To invert inputs,use external inverters. Because each input uses a CLB resource, replace gates with unused inputs with gateshaving the necessary number of inputs.
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 519
Chapter 3: About Design Elements
NAND7Macro: 7-Input NAND Gate with Non-Inverted Inputs
Supported ArchitecturesThis design element is supported in the following architectures only:
• XC9500
• CoolRunner™ XPLA3
• CoolRunner-II
IntroductionNAND gates of up to five inputs are available in any combination of inverting and non-inverting inputs. NANDgates of six to nine inputs, 12 inputs, and 16 inputs are available with only non-inverting inputs. To invert inputs,use external inverters. Because each input uses a CLB resource, replace gates with unused inputs with gateshaving the necessary number of inputs.
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries Guide520 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
NAND8Macro: 8-Input NAND Gate with Non-Inverted Inputs
Supported ArchitecturesThis design element is supported in the following architectures only:
• XC9500
• CoolRunner™ XPLA3
• CoolRunner-II
IntroductionNAND gates of up to five inputs are available in any combination of inverting and non-inverting inputs. NANDgates of six to nine inputs, 12 inputs, and 16 inputs are available with only non-inverting inputs. To invert inputs,use external inverters. Because each input uses a CLB resource, replace gates with unused inputs with gateshaving the necessary number of inputs.
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 521
Chapter 3: About Design Elements
NAND9Macro: 9-Input NAND Gate with Non-Inverted Inputs
Supported ArchitecturesThis design element is supported in the following architectures only:
• XC9500
• CoolRunner™ XPLA3
• CoolRunner-II
IntroductionNAND gates of up to five inputs are available in any combination of inverting and non-inverting inputs. NANDgates of six to nine inputs, 12 inputs, and 16 inputs are available with only non-inverting inputs. To invert inputs,use external inverters. Because each input uses a CLB resource, replace gates with unused inputs with gateshaving the necessary number of inputs.
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries Guide522 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
NOR2Primitive: 2-Input NOR Gate with Non-Inverted Inputs
Supported ArchitecturesThis design element is supported in the following architectures only:
• XC9500
• CoolRunner™ XPLA3
• CoolRunner-II
IntroductionNOR gates of up to five inputs are available in any combination of inverting and non-inverting inputs. NORgates of six to nine inputs, 12 inputs, and 16 inputs are available only with non-inverting inputs. To invert someor all inputs, use external inverters. Because each input uses a CLB resource, replace gates with unused inputswith gates having the necessary number of inputs.
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 523
Chapter 3: About Design Elements
NOR2B1Primitive: 2-Input NOR Gate with 1 Inverted and 1 Non-Inverted Inputs
Supported ArchitecturesThis design element is supported in the following architectures only:
• XC9500
• CoolRunner™ XPLA3
• CoolRunner-II
IntroductionNOR gates of up to five inputs are available in any combination of inverting and non-inverting inputs. NORgates of six to nine inputs, 12 inputs, and 16 inputs are available only with non-inverting inputs. To invert someor all inputs, use external inverters. Because each input uses a CLB resource, replace gates with unused inputswith gates having the necessary number of inputs.
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries Guide524 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
NOR2B2Primitive: 2-Input NOR Gate with Inverted Inputs
Supported ArchitecturesThis design element is supported in the following architectures only:
• XC9500
• CoolRunner™ XPLA3
• CoolRunner-II
IntroductionNOR gates of up to five inputs are available in any combination of inverting and non-inverting inputs. NORgates of six to nine inputs, 12 inputs, and 16 inputs are available only with non-inverting inputs. To invert someor all inputs, use external inverters. Because each input uses a CLB resource, replace gates with unused inputswith gates having the necessary number of inputs.
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 525
Chapter 3: About Design Elements
NOR3Primitive: 3-Input NOR Gate with Non-Inverted Inputs
Supported ArchitecturesThis design element is supported in the following architectures only:
• XC9500
• CoolRunner™ XPLA3
• CoolRunner-II
IntroductionNOR gates of up to five inputs are available in any combination of inverting and non-inverting inputs. NORgates of six to nine inputs, 12 inputs, and 16 inputs are available only with non-inverting inputs. To invert someor all inputs, use external inverters. Because each input uses a CLB resource, replace gates with unused inputswith gates having the necessary number of inputs.
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries Guide526 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
NOR3B1Primitive: 3-Input NOR Gate with 1 Inverted and 2 Non-Inverted Inputs
Supported ArchitecturesThis design element is supported in the following architectures only:
• XC9500
• CoolRunner™ XPLA3
• CoolRunner-II
IntroductionNOR gates of up to five inputs are available in any combination of inverting and non-inverting inputs. NORgates of six to nine inputs, 12 inputs, and 16 inputs are available only with non-inverting inputs. To invert someor all inputs, use external inverters. Because each input uses a CLB resource, replace gates with unused inputswith gates having the necessary number of inputs.
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 527
Chapter 3: About Design Elements
NOR3B2Primitive: 3-Input NOR Gate with 2 Inverted and 1 Non-Inverted Inputs
Supported ArchitecturesThis design element is supported in the following architectures only:
• XC9500
• CoolRunner™ XPLA3
• CoolRunner-II
IntroductionNOR gates of up to five inputs are available in any combination of inverting and non-inverting inputs. NORgates of six to nine inputs, 12 inputs, and 16 inputs are available only with non-inverting inputs. To invert someor all inputs, use external inverters. Because each input uses a CLB resource, replace gates with unused inputswith gates having the necessary number of inputs.
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries Guide528 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
NOR3B3Primitive: 3-Input NOR Gate with Inverted Inputs
Supported ArchitecturesThis design element is supported in the following architectures only:
• XC9500
• CoolRunner™ XPLA3
• CoolRunner-II
IntroductionNOR gates of up to five inputs are available in any combination of inverting and non-inverting inputs. NORgates of six to nine inputs, 12 inputs, and 16 inputs are available only with non-inverting inputs. To invert someor all inputs, use external inverters. Because each input uses a CLB resource, replace gates with unused inputswith gates having the necessary number of inputs.
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 529
Chapter 3: About Design Elements
NOR4Primitive: 4-Input NOR Gate with Non-Inverted Inputs
Supported ArchitecturesThis design element is supported in the following architectures only:
• XC9500
• CoolRunner™ XPLA3
• CoolRunner-II
IntroductionNOR gates of up to five inputs are available in any combination of inverting and non-inverting inputs. NORgates of six to nine inputs, 12 inputs, and 16 inputs are available only with non-inverting inputs. To invert someor all inputs, use external inverters. Because each input uses a CLB resource, replace gates with unused inputswith gates having the necessary number of inputs.
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries Guide530 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
NOR4B1Primitive: 4-Input NOR Gate with 1 Inverted and 3 Non-Inverted Inputs
Supported ArchitecturesThis design element is supported in the following architectures only:
• XC9500
• CoolRunner™ XPLA3
• CoolRunner-II
IntroductionNOR gates of up to five inputs are available in any combination of inverting and non-inverting inputs. NORgates of six to nine inputs, 12 inputs, and 16 inputs are available only with non-inverting inputs. To invert someor all inputs, use external inverters. Because each input uses a CLB resource, replace gates with unused inputswith gates having the necessary number of inputs.
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 531
Chapter 3: About Design Elements
NOR4B2Primitive: 4-Input NOR Gate with 2 Inverted and 2 Non-Inverted Inputs
Supported ArchitecturesThis design element is supported in the following architectures only:
• XC9500
• CoolRunner™ XPLA3
• CoolRunner-II
IntroductionNOR gates of up to five inputs are available in any combination of inverting and non-inverting inputs. NORgates of six to nine inputs, 12 inputs, and 16 inputs are available only with non-inverting inputs. To invert someor all inputs, use external inverters. Because each input uses a CLB resource, replace gates with unused inputswith gates having the necessary number of inputs.
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries Guide532 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
NOR4B3Primitive: 4-Input NOR Gate with 3 Inverted and 1 Non-Inverted Inputs
Supported ArchitecturesThis design element is supported in the following architectures only:
• XC9500
• CoolRunner™ XPLA3
• CoolRunner-II
IntroductionNOR gates of up to five inputs are available in any combination of inverting and non-inverting inputs. NORgates of six to nine inputs, 12 inputs, and 16 inputs are available only with non-inverting inputs. To invert someor all inputs, use external inverters. Because each input uses a CLB resource, replace gates with unused inputswith gates having the necessary number of inputs.
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 533
Chapter 3: About Design Elements
NOR4B4Primitive: 4-Input NOR Gate with Inverted Inputs
Supported ArchitecturesThis design element is supported in the following architectures only:
• XC9500
• CoolRunner™ XPLA3
• CoolRunner-II
IntroductionNOR gates of up to five inputs are available in any combination of inverting and non-inverting inputs. NORgates of six to nine inputs, 12 inputs, and 16 inputs are available only with non-inverting inputs. To invert someor all inputs, use external inverters. Because each input uses a CLB resource, replace gates with unused inputswith gates having the necessary number of inputs.
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries Guide534 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
NOR5Primitive: 5-Input NOR Gate with Non-Inverted Inputs
Supported ArchitecturesThis design element is supported in the following architectures only:
• XC9500
• CoolRunner™ XPLA3
• CoolRunner-II
IntroductionNOR gates of up to five inputs are available in any combination of inverting and non-inverting inputs. NORgates of six to nine inputs, 12 inputs, and 16 inputs are available only with non-inverting inputs. To invert someor all inputs, use external inverters. Because each input uses a CLB resource, replace gates with unused inputswith gates having the necessary number of inputs.
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 535
Chapter 3: About Design Elements
NOR5B1Primitive: 5-Input NOR Gate with 1 Inverted and 4 Non-Inverted Inputs
Supported ArchitecturesThis design element is supported in the following architectures only:
• XC9500
• CoolRunner™ XPLA3
• CoolRunner-II
IntroductionNOR gates of up to five inputs are available in any combination of inverting and non-inverting inputs. NORgates of six to nine inputs, 12 inputs, and 16 inputs are available only with non-inverting inputs. To invert someor all inputs, use external inverters. Because each input uses a CLB resource, replace gates with unused inputswith gates having the necessary number of inputs.
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries Guide536 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
NOR5B2Primitive: 5-Input NOR Gate with 2 Inverted and 3 Non-Inverted Inputs
Supported ArchitecturesThis design element is supported in the following architectures only:
• XC9500
• CoolRunner™ XPLA3
• CoolRunner-II
IntroductionNOR gates of up to five inputs are available in any combination of inverting and non-inverting inputs. NORgates of six to nine inputs, 12 inputs, and 16 inputs are available only with non-inverting inputs. To invert someor all inputs, use external inverters. Because each input uses a CLB resource, replace gates with unused inputswith gates having the necessary number of inputs.
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 537
Chapter 3: About Design Elements
NOR5B3Primitive: 5-Input NOR Gate with 3 Inverted and 2 Non-Inverted Inputs
Supported ArchitecturesThis design element is supported in the following architectures only:
• XC9500
• CoolRunner™ XPLA3
• CoolRunner-II
IntroductionNOR gates of up to five inputs are available in any combination of inverting and non-inverting inputs. NORgates of six to nine inputs, 12 inputs, and 16 inputs are available only with non-inverting inputs. To invert someor all inputs, use external inverters. Because each input uses a CLB resource, replace gates with unused inputswith gates having the necessary number of inputs.
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries Guide538 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
NOR5B4Primitive: 5-Input NOR Gate with 4 Inverted and 1 Non-Inverted Inputs
Supported ArchitecturesThis design element is supported in the following architectures only:
• XC9500
• CoolRunner™ XPLA3
• CoolRunner-II
IntroductionNOR gates of up to five inputs are available in any combination of inverting and non-inverting inputs. NORgates of six to nine inputs, 12 inputs, and 16 inputs are available only with non-inverting inputs. To invert someor all inputs, use external inverters. Because each input uses a CLB resource, replace gates with unused inputswith gates having the necessary number of inputs.
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 539
Chapter 3: About Design Elements
NOR5B5Primitive: 5-Input NOR Gate with Inverted Inputs
Supported ArchitecturesThis design element is supported in the following architectures only:
• XC9500
• CoolRunner™ XPLA3
• CoolRunner-II
IntroductionNOR gates of up to five inputs are available in any combination of inverting and non-inverting inputs. NORgates of six to nine inputs, 12 inputs, and 16 inputs are available only with non-inverting inputs. To invert someor all inputs, use external inverters. Because each input uses a CLB resource, replace gates with unused inputswith gates having the necessary number of inputs.
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries Guide540 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
NOR6Macro: 6-Input NOR Gate with Non-Inverted Inputs
Supported ArchitecturesThis design element is supported in the following architectures only:
• XC9500
• CoolRunner™ XPLA3
• CoolRunner-II
IntroductionNOR gates of up to five inputs are available in any combination of inverting and non-inverting inputs. NORgates of six to nine inputs, 12 inputs, and 16 inputs are available only with non-inverting inputs. To invert someor all inputs, use external inverters. Because each input uses a CLB resource, replace gates with unused inputswith gates having the necessary number of inputs.
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 541
Chapter 3: About Design Elements
NOR7Macro: 7-Input NOR Gate with Non-Inverted Inputs
Supported ArchitecturesThis design element is supported in the following architectures only:
• XC9500
• CoolRunner™ XPLA3
• CoolRunner-II
IntroductionNOR gates of up to five inputs are available in any combination of inverting and non-inverting inputs. NORgates of six to nine inputs, 12 inputs, and 16 inputs are available only with non-inverting inputs. To invert someor all inputs, use external inverters. Because each input uses a CLB resource, replace gates with unused inputswith gates having the necessary number of inputs.
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries Guide542 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
NOR8Macro: 8-Input NOR Gate with Non-Inverted Inputs
Supported ArchitecturesThis design element is supported in the following architectures only:
• XC9500
• CoolRunner™ XPLA3
• CoolRunner-II
IntroductionNOR gates of up to five inputs are available in any combination of inverting and non-inverting inputs. NORgates of six to nine inputs, 12 inputs, and 16 inputs are available only with non-inverting inputs. To invert someor all inputs, use external inverters. Because each input uses a CLB resource, replace gates with unused inputswith gates having the necessary number of inputs.
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 543
Chapter 3: About Design Elements
NOR9Macro: 9-Input NOR Gate with Non-Inverted Inputs
Supported ArchitecturesThis design element is supported in the following architectures only:
• XC9500
• CoolRunner™ XPLA3
• CoolRunner-II
IntroductionNOR gates of up to five inputs are available in any combination of inverting and non-inverting inputs. NORgates of six to nine inputs, 12 inputs, and 16 inputs are available only with non-inverting inputs. To invert someor all inputs, use external inverters. Because each input uses a CLB resource, replace gates with unused inputswith gates having the necessary number of inputs.
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries Guide544 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
OBUFPrimitive: Output Buffer
Supported ArchitecturesThis design element is supported in the following architectures only:
• XC9500
• CoolRunner™ XPLA3
• CoolRunner-II
IntroductionThis design element is a simple output buffer used to drive output signals to the FPGA device pins that do notneed to be 3-stated (constantly driven). Either an OBUF, OBUFT, OBUFDS, or OBUFTDS must be connected toevery output port in the design.
This element isolates the internal circuit and provides drive current for signals leaving a chip. It exists ininput/output blocks (IOB). Its output (O) is connected to an OPAD or an IOPAD. The interface standard usedby this element is LVTTL. Also, this element has selectable drive and slew rates using the DRIVE and SLOWor FAST constraints. The defaults are DRIVE=12 mA and SLOW slew.
Port DescriptionsPort Direction Width Function
O Output 1 Output of OBUF to be connected directly to top-level outputport.
I Input 1 Input of OBUF. Connect to the logic driving the output port.
Design Entry MethodThis design element can be used in schematics.
Available AttributesAttribute Type Allowed Values Default Description
IOSTANDARD String See Data Sheet "DEFAULT" Assigns an I/O standard to the element.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 545
Chapter 3: About Design Elements
VHDL Instantiation TemplateUnless they already exist, copy the following two statements and paste them before the entity declaration.
Library UNISIM;use UNISIM.vcomponents.all;
-- OBUF: Single-ended Output Buffer-- All devices-- Xilinx HDL Libraries Guide, version 11.2
OBUF_inst : OBUFgeneric map (
DRIVE => 12,IOSTANDARD => "DEFAULT",SLEW => "SLOW")
port map (O => O, -- Buffer output (connect directly to top-level port)I => I -- Buffer input
);
-- End of OBUF_inst instantiation
Verilog Instantiation Template// OBUF: Single-ended Output Buffer// All devices// Xilinx HDL Libraries Guide, version 11.2
OBUF #(.DRIVE(12), // Specify the output drive strength.IOSTANDARD("DEFAULT"), // Specify the output I/O standard.SLEW("SLOW") // Specify the output slew rate
) OBUF_inst (.O(O), // Buffer output (connect directly to top-level port).I(I) // Buffer input
);
// End of OBUF_inst instantiation
For More Information• See the appropriate CPLD User Guide.
• See the appropriate EDK documentation.
CPLD Libraries Guide546 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
OBUF16Macro: 16-Bit Output Buffer
Supported ArchitecturesThis design element is supported in the following architectures only:
• XC9500
• CoolRunner™ XPLA3
• CoolRunner-II
IntroductionThis design element is a multiple output buffer.
This element isolates the internal circuit and provides drive current for signals leaving a chip. It exists ininput/output blocks (IOB). Its output (O) is connected to an OPAD or an IOPAD. The interface standard usedby this element is LVTTL. Also, this element has selectable drive and slew rates using the DRIVE and SLOWor FAST constraints. The defaults are DRIVE=12 mA and SLOW slew.
Design Entry MethodThis design element can be used in schematics.
Available AttributesAttribute Type Allowed Values Default Description
IOSTANDARD String See Data Sheet "DEFAULT" Assigns an I/O standard to the element.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 547
Chapter 3: About Design Elements
OBUF4Macro: 4-Bit Output Buffer
Supported ArchitecturesThis design element is supported in the following architectures only:
• XC9500
• CoolRunner™ XPLA3
• CoolRunner-II
IntroductionThis design element is a multiple output buffer.
This element isolates the internal circuit and provides drive current for signals leaving a chip. It exists ininput/output blocks (IOB). Its output (O) is connected to an OPAD or an IOPAD. The interface standard usedby this element is LVTTL. Also, this element has selectable drive and slew rates using the DRIVE and SLOWor FAST constraints. The defaults are DRIVE=12 mA and SLOW slew.
Design Entry MethodThis design element can be used in schematics.
Available AttributesAttribute Type Allowed Values Default Description
IOSTANDARD String See Data Sheet "DEFAULT" Assigns an I/O standard to the element.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries Guide548 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
OBUF8Macro: 8-Bit Output Buffer
Supported ArchitecturesThis design element is supported in the following architectures only:
• XC9500
• CoolRunner™ XPLA3
• CoolRunner-II
IntroductionThis design element is a multiple output buffer.
This element isolates the internal circuit and provides drive current for signals leaving a chip. It exists ininput/output blocks (IOB). Its output (O) is connected to an OPAD or an IOPAD. The interface standard usedby this element is LVTTL. Also, this element has selectable drive and slew rates using the DRIVE and SLOWor FAST constraints. The defaults are DRIVE=12 mA and SLOW slew.
Design Entry MethodThis design element can be used in schematics.
Available AttributesAttribute Type Allowed Values Default Description
IOSTANDARD String See Data Sheet "DEFAULT" Assigns an I/O standard to the element.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 549
Chapter 3: About Design Elements
OBUFEMacro: 3-State Output Buffer with Active-High Output Enable
Supported ArchitecturesThis design element is supported in the following architectures only:
• XC9500
• CoolRunner™ XPLA3
• CoolRunner-II
IntroductionThis design element is a 3-state buffer with input I, output O, and active-High output enable (E).
When E is High, data on the inputs of the buffers is transferred to the corresponding outputs. When E is Low,the output is High impedance (off or Z state). This design element isolates the internal circuit and providesdrive current for signals leaving a chip. It is connected to an OPAD or an IOPAD, and its input is connected tothe internal circuit.
Logic TableInputs Outputs
E I O
0 X Z
1 1 1
1 0 0
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries Guide550 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
OBUFE16Macro: 16-Bit 3-State Output Buffer with Active-High Output Enable
Supported ArchitecturesThis design element is supported in the following architectures only:
• XC9500
• CoolRunner™ XPLA3
• CoolRunner™-II
IntroductionThis design element is a 3-state buffer with input I15-I0, output O15-O0, and active-High output enable (E).
When E is High, data on the inputs of the buffers is transferred to the corresponding outputs. When E is Low,the output is High impedance (off or Z state). This design element isolates the internal circuit and providesdrive current for signals leaving a chip. It is connected to an OPAD or an IOPAD, and its input is connected tothe internal circuit.
Logic TableInputs Outputs
E I O
0 X Z
1 1 1
1 0 0
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 551
Chapter 3: About Design Elements
OBUFE4Macro: 4-Bit 3-State Output Buffer with Active-High Output Enable
Supported ArchitecturesThis design element is supported in the following architectures only:
• XC9500
• CoolRunner™ XPLA3
• CoolRunner™-II
IntroductionThis design element is a 3-state buffer with input I3-I0, output O3-O0, and active-High output enable (E).
When E is High, data on the inputs of the buffers is transferred to the corresponding outputs. When E is Low,the output is High impedance (off or Z state). This design element isolates the internal circuit and providesdrive current for signals leaving a chip. It is connected to an OPAD or an IOPAD, and its input is connected tothe internal circuit.
Logic TableInputs Outputs
E I O
0 X Z
1 1 1
1 0 0
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries Guide552 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
OBUFE8Macro: 8-Bit 3-State Output Buffer with Active-High Output Enable
Supported ArchitecturesThis design element is supported in the following architectures only:
• XC9500
• CoolRunner™ XPLA3
• CoolRunner™-II
IntroductionThis design element is a 3-state buffer with input I7-I0, output O7-O0, and active-High output enable (E).
When E is High, data on the inputs of the buffers is transferred to the corresponding outputs. When E is Low,the output is High impedance (off or Z state). This design element isolates the internal circuit and providesdrive current for signals leaving a chip. It is connected to an OPAD or an IOPAD, and its input is connected tothe internal circuit.
Logic TableInputs Outputs
E I O
0 X Z
1 1 1
1 0 0
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 553
Chapter 3: About Design Elements
OBUFTPrimitive: 3-State Output Buffer with Active Low Output Enable
Supported ArchitecturesThis design element is supported in the following architectures only:• XC9500• CoolRunner™ XPLA3• CoolRunner-II
IntroductionThis design element is a single, 3-state output buffer with input I, output O, and active-Low output enables (T).This element uses the LVTTL standard and has selectable drive and slew rates using the DRIVE and SLOW orFAST constraints. The defaults are DRIVE=12 mA and SLOW slew.
When T is Low, data on the inputs of the buffers is transferred to the corresponding outputs. When T is High, theoutput is high impedance (off or Z state). OBUFTs are generally used when a single-ended output is neededwith a 3-state capability, such as the case when building bidirectional I/O.
Logic TableInputs Outputs
T I O
1 X Z
0 I F
Port DescriptionsPort Direction Width Function
O Output 1 Buffer output (connect directly to top-level port)
I Input 1 Buffer input
T Input 1 3-state enable input
Design Entry MethodThis design element can be used in schematics.
Available AttributesAttribute Type Allowed Values Default Description
IOSTANDARD String See Data Sheet "DEFAULT" Assigns an I/O standard to the element.
CPLD Libraries Guide554 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
VHDL Instantiation TemplateUnless they already exist, copy the following two statements and paste them before the entity declaration.
Library UNISIM;use UNISIM.vcomponents.all;
-- OBUFT: Single-ended 3-state Output Buffer-- All devices-- Xilinx HDL Libraries Guide, version 11.2
OBUFT_inst : OBUFTgeneric map (
DRIVE => 12,IOSTANDARD => "DEFAULT",SLEW => "SLOW")
port map (O => O, -- Buffer output (connect directly to top-level port)I => I, -- Buffer inputT => T -- 3-state enable input
);
-- End of OBUFT_inst instantiation
Verilog Instantiation Template// OBUFT: Single-ended 3-state Output Buffer// All devices// Xilinx HDL Libraries Guide, version 11.2
OBUFT #(.DRIVE(12), // Specify the output drive strength.IOSTANDARD("DEFAULT"), // Specify the output I/O standard.SLEW("SLOW") // Specify the output slew rate
) OBUFT_inst (.O(O), // Buffer output (connect directly to top-level port).I(I), // Buffer input.T(T) // 3-state enable input
);
// End of OBUFT_inst instantiation
For More Information• See the appropriate CPLD User Guide.
• See the appropriate EDK documentation.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 555
Chapter 3: About Design Elements
OBUFT16Macro: 16-Bit 3-State Output Buffer with Active Low Output Enable
Supported ArchitecturesThis design element is supported in the following architectures only:• XC9500• CoolRunner™ XPLA3• CoolRunner-II
IntroductionThis design element is a multiple, 3-state output buffer with input I, output O, and active-Low output enables(T). This element uses the LVTTL standard and has selectable drive and slew rates using the DRIVE and SLOWor FAST constraints. The defaults are DRIVE=12 mA and SLOW slew.
When T is Low, data on the inputs of the buffers is transferred to the corresponding outputs. When T is High, theoutput is high impedance (off or Z state). OBUFTs are generally used when a single-ended output is neededwith a 3-state capability, such as the case when building bidirectional I/O.
Logic TableInputs Outputs
T I O
1 X Z
0 I F
Design Entry MethodThis design element is only for use in schematics.
Available AttributesAttribute Type Allowed Values Default Description
IOSTANDARD String See Data Sheet "DEFAULT" Assigns an I/O standard to the element.
For More Information• See the appropriate CPLD User Guide.• See the appropriate CPLD Data Sheets.
CPLD Libraries Guide556 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
OBUFT4Macro: 4-Bit 3-State Output Buffers with Active-Low Output Enable
Supported ArchitecturesThis design element is supported in the following architectures only:• XC9500• CoolRunner™ XPLA3• CoolRunner-II
IntroductionThis design element is a multiple, 3-state output buffer with input I, output O, and active-Low output enables(T). This element uses the LVTTL standard and has selectable drive and slew rates using the DRIVE and SLOWor FAST constraints. The defaults are DRIVE=12 mA and SLOW slew.
When T is Low, data on the inputs of the buffers is transferred to the corresponding outputs. When T is High, theoutput is high impedance (off or Z state). OBUFTs are generally used when a single-ended output is neededwith a 3-state capability, such as the case when building bidirectional I/O.
Logic TableInputs Outputs
T I O
1 X Z
0 I F
Design Entry MethodThis design element is only for use in schematics.
Available AttributesAttribute Type Allowed Values Default Description
IOSTANDARD String See Data Sheet "DEFAULT" Assigns an I/O standard to the element.
For More Information• See the appropriate CPLD User Guide.• See the appropriate CPLD Data Sheets.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 557
Chapter 3: About Design Elements
OBUFT8Macro: 8-Bit 3-State Output Buffers with Active-Low Output Enable
Supported ArchitecturesThis design element is supported in the following architectures only:• XC9500• CoolRunner™ XPLA3• CoolRunner-II
IntroductionThis design element is a multiple, 3-state output buffer with input I, output O, and active-Low output enables(T). This element uses the LVTTL standard and has selectable drive and slew rates using the DRIVE and SLOWor FAST constraints. The defaults are DRIVE=12 mA and SLOW slew.
When T is Low, data on the inputs of the buffers is transferred to the corresponding outputs. When T is High, theoutput is high impedance (off or Z state). OBUFTs are generally used when a single-ended output is neededwith a 3-state capability, such as the case when building bidirectional I/O.
Logic TableInputs Outputs
T I O
1 X Z
0 I F
Design Entry MethodThis design element is only for use in schematics.
Available AttributesAttribute Type Allowed Values Default Description
IOSTANDARD String See Data Sheet "DEFAULT" Assigns an I/O standard to the element.
For More Information• See the appropriate CPLD User Guide.• See the appropriate CPLD Data Sheets.
CPLD Libraries Guide558 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
OR2Primitive: 2-Input OR Gate with Non-Inverted Inputs
Supported ArchitecturesThis design element is supported in the following architectures only:
• XC9500
• CoolRunner™ XPLA3
• CoolRunner-II
IntroductionOR functions of up to five inputs are available in any combination of inverting and non-inverting inputs. ORfunctions of six to nine inputs, 12 inputs, and 16 inputs are available with only non-inverting inputs. To invertsome or all inputs, use external inverters. Because each input uses a CLB resource, replace functions with unusedinputs with functions having the necessary number of inputs.
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 559
Chapter 3: About Design Elements
OR2B1Primitive: 2-Input OR Gate with 1 Inverted and 1 Non-Inverted Inputs
Supported ArchitecturesThis design element is supported in the following architectures only:
• XC9500
• CoolRunner™ XPLA3
• CoolRunner-II
IntroductionOR functions of up to five inputs are available in any combination of inverting and non-inverting inputs. ORfunctions of six to nine inputs, 12 inputs, and 16 inputs are available with only non-inverting inputs. To invertsome or all inputs, use external inverters. Because each input uses a CLB resource, replace functions with unusedinputs with functions having the necessary number of inputs.
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries Guide560 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
OR2B2Primitive: 2-Input OR Gate with Inverted Inputs
Supported ArchitecturesThis design element is supported in the following architectures only:
• XC9500
• CoolRunner™ XPLA3
• CoolRunner-II
IntroductionOR functions of up to five inputs are available in any combination of inverting and non-inverting inputs. ORfunctions of six to nine inputs, 12 inputs, and 16 inputs are available with only non-inverting inputs. To invertsome or all inputs, use external inverters. Because each input uses a CLB resource, replace functions with unusedinputs with functions having the necessary number of inputs.
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 561
Chapter 3: About Design Elements
OR3Primitive: 3-Input OR Gate with Non-Inverted Inputs
Supported ArchitecturesThis design element is supported in the following architectures only:
• XC9500
• CoolRunner™ XPLA3
• CoolRunner-II
IntroductionOR functions of up to five inputs are available in any combination of inverting and non-inverting inputs. ORfunctions of six to nine inputs, 12 inputs, and 16 inputs are available with only non-inverting inputs. To invertsome or all inputs, use external inverters. Because each input uses a CLB resource, replace functions with unusedinputs with functions having the necessary number of inputs.
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries Guide562 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
OR3B1Primitive: 3-Input OR Gate with 1 Inverted and 2 Non-Inverted Inputs
Supported ArchitecturesThis design element is supported in the following architectures only:
• XC9500
• CoolRunner™ XPLA3
• CoolRunner-II
IntroductionOR functions of up to five inputs are available in any combination of inverting and non-inverting inputs. ORfunctions of six to nine inputs, 12 inputs, and 16 inputs are available with only non-inverting inputs. To invertsome or all inputs, use external inverters. Because each input uses a CLB resource, replace functions with unusedinputs with functions having the necessary number of inputs.
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 563
Chapter 3: About Design Elements
OR3B2Primitive: 3-Input OR Gate with 2 Inverted and 1 Non-Inverted Inputs
Supported ArchitecturesThis design element is supported in the following architectures only:
• XC9500
• CoolRunner™ XPLA3
• CoolRunner-II
IntroductionOR functions of up to five inputs are available in any combination of inverting and non-inverting inputs. ORfunctions of six to nine inputs, 12 inputs, and 16 inputs are available with only non-inverting inputs. To invertsome or all inputs, use external inverters. Because each input uses a CLB resource, replace functions with unusedinputs with functions having the necessary number of inputs.
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries Guide564 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
OR3B3Primitive: 3-Input OR Gate with Inverted Inputs
Supported ArchitecturesThis design element is supported in the following architectures only:
• XC9500
• CoolRunner™ XPLA3
• CoolRunner-II
IntroductionOR functions of up to five inputs are available in any combination of inverting and non-inverting inputs. ORfunctions of six to nine inputs, 12 inputs, and 16 inputs are available with only non-inverting inputs. To invertsome or all inputs, use external inverters. Because each input uses a CLB resource, replace functions with unusedinputs with functions having the necessary number of inputs.
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 565
Chapter 3: About Design Elements
OR4Primitive: 4-Input OR Gate with Non-Inverted Inputs
Supported ArchitecturesThis design element is supported in the following architectures only:
• XC9500
• CoolRunner™ XPLA3
• CoolRunner-II
IntroductionOR functions of up to five inputs are available in any combination of inverting and non-inverting inputs. ORfunctions of six to nine inputs, 12 inputs, and 16 inputs are available with only non-inverting inputs. To invertsome or all inputs, use external inverters. Because each input uses a CLB resource, replace functions with unusedinputs with functions having the necessary number of inputs.
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries Guide566 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
OR4B1Primitive: 4-Input OR Gate with 1 Inverted and 3 Non-Inverted Inputs
Supported ArchitecturesThis design element is supported in the following architectures only:
• XC9500
• CoolRunner™ XPLA3
• CoolRunner-II
IntroductionOR functions of up to five inputs are available in any combination of inverting and non-inverting inputs. ORfunctions of six to nine inputs, 12 inputs, and 16 inputs are available with only non-inverting inputs. To invertsome or all inputs, use external inverters. Because each input uses a CLB resource, replace functions with unusedinputs with functions having the necessary number of inputs.
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 567
Chapter 3: About Design Elements
OR4B2Primitive: 4-Input OR Gate with 2 Inverted and 2 Non-Inverted Inputs
Supported ArchitecturesThis design element is supported in the following architectures only:
• XC9500
• CoolRunner™ XPLA3
• CoolRunner-II
IntroductionOR functions of up to five inputs are available in any combination of inverting and non-inverting inputs. ORfunctions of six to nine inputs, 12 inputs, and 16 inputs are available with only non-inverting inputs. To invertsome or all inputs, use external inverters. Because each input uses a CLB resource, replace functions with unusedinputs with functions having the necessary number of inputs.
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries Guide568 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
OR4B3Primitive: 4-Input OR Gate with 3 Inverted and 1 Non-Inverted Inputs
Supported ArchitecturesThis design element is supported in the following architectures only:
• XC9500
• CoolRunner™ XPLA3
• CoolRunner-II
IntroductionOR functions of up to five inputs are available in any combination of inverting and non-inverting inputs. ORfunctions of six to nine inputs, 12 inputs, and 16 inputs are available with only non-inverting inputs. To invertsome or all inputs, use external inverters. Because each input uses a CLB resource, replace functions with unusedinputs with functions having the necessary number of inputs.
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 569
Chapter 3: About Design Elements
OR4B4Primitive: 4-Input OR Gate with Inverted Inputs
Supported ArchitecturesThis design element is supported in the following architectures only:
• XC9500
• CoolRunner™ XPLA3
• CoolRunner-II
IntroductionOR functions of up to five inputs are available in any combination of inverting and non-inverting inputs. ORfunctions of six to nine inputs, 12 inputs, and 16 inputs are available with only non-inverting inputs. To invertsome or all inputs, use external inverters. Because each input uses a CLB resource, replace functions with unusedinputs with functions having the necessary number of inputs.
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries Guide570 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
OR5Primitive: 5-Input OR Gate with Non-Inverted Inputs
Supported ArchitecturesThis design element is supported in the following architectures only:
• XC9500
• CoolRunner™ XPLA3
• CoolRunner-II
IntroductionOR functions of up to five inputs are available in any combination of inverting and non-inverting inputs. ORfunctions of six to nine inputs, 12 inputs, and 16 inputs are available with only non-inverting inputs. To invertsome or all inputs, use external inverters. Because each input uses a CLB resource, replace functions with unusedinputs with functions having the necessary number of inputs.
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 571
Chapter 3: About Design Elements
OR5B1Primitive: 5-Input OR Gate with 1 Inverted and 4 Non-Inverted Inputs
Supported ArchitecturesThis design element is supported in the following architectures only:
• XC9500
• CoolRunner™ XPLA3
• CoolRunner-II
IntroductionOR functions of up to five inputs are available in any combination of inverting and non-inverting inputs. ORfunctions of six to nine inputs, 12 inputs, and 16 inputs are available with only non-inverting inputs. To invertsome or all inputs, use external inverters. Because each input uses a CLB resource, replace functions with unusedinputs with functions having the necessary number of inputs.
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries Guide572 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
OR5B2Primitive: 5-Input OR Gate with 2 Inverted and 3 Non-Inverted Inputs
Supported ArchitecturesThis design element is supported in the following architectures only:
• XC9500
• CoolRunner™ XPLA3
• CoolRunner-II
IntroductionOR functions of up to five inputs are available in any combination of inverting and non-inverting inputs. ORfunctions of six to nine inputs, 12 inputs, and 16 inputs are available with only non-inverting inputs. To invertsome or all inputs, use external inverters. Because each input uses a CLB resource, replace functions with unusedinputs with functions having the necessary number of inputs.
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 573
Chapter 3: About Design Elements
OR5B3Primitive: 5-Input OR Gate with 3 Inverted and 2 Non-Inverted Inputs
Supported ArchitecturesThis design element is supported in the following architectures only:
• XC9500
• CoolRunner™ XPLA3
• CoolRunner-II
IntroductionOR functions of up to five inputs are available in any combination of inverting and non-inverting inputs. ORfunctions of six to nine inputs, 12 inputs, and 16 inputs are available with only non-inverting inputs. To invertsome or all inputs, use external inverters. Because each input uses a CLB resource, replace functions with unusedinputs with functions having the necessary number of inputs.
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries Guide574 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
OR5B4Primitive: 5-Input OR Gate with 4 Inverted and 1 Non-Inverted Inputs
Supported ArchitecturesThis design element is supported in the following architectures only:
• XC9500
• CoolRunner™ XPLA3
• CoolRunner-II
IntroductionOR functions of up to five inputs are available in any combination of inverting and non-inverting inputs. ORfunctions of six to nine inputs, 12 inputs, and 16 inputs are available with only non-inverting inputs. To invertsome or all inputs, use external inverters. Because each input uses a CLB resource, replace functions with unusedinputs with functions having the necessary number of inputs.
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 575
Chapter 3: About Design Elements
OR5B5Primitive: 5-Input OR Gate with Inverted Inputs
Supported ArchitecturesThis design element is supported in the following architectures only:
• XC9500
• CoolRunner™ XPLA3
• CoolRunner-II
IntroductionOR functions of up to five inputs are available in any combination of inverting and non-inverting inputs. ORfunctions of six to nine inputs, 12 inputs, and 16 inputs are available with only non-inverting inputs. To invertsome or all inputs, use external inverters. Because each input uses a CLB resource, replace functions with unusedinputs with functions having the necessary number of inputs.
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries Guide576 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
OR6Macro: 6-Input OR Gate with Non-Inverted Inputs
Supported ArchitecturesThis design element is supported in the following architectures only:
• XC9500
• CoolRunner™ XPLA3
• CoolRunner-II
IntroductionOR functions of up to five inputs are available in any combination of inverting and non-inverting inputs. ORfunctions of six to nine inputs, 12 inputs, and 16 inputs are available with only non-inverting inputs. To invertsome or all inputs, use external inverters. Because each input uses a CLB resource, replace functions with unusedinputs with functions having the necessary number of inputs.
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 577
Chapter 3: About Design Elements
OR7Macro: 7-Input OR Gate with Non-Inverted Inputs
Supported ArchitecturesThis design element is supported in the following architectures only:
• XC9500
• CoolRunner™ XPLA3
• CoolRunner-II
IntroductionOR functions of up to five inputs are available in any combination of inverting and non-inverting inputs. ORfunctions of six to nine inputs, 12 inputs, and 16 inputs are available with only non-inverting inputs. To invertsome or all inputs, use external inverters. Because each input uses a CLB resource, replace functions with unusedinputs with functions having the necessary number of inputs.
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries Guide578 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
OR8Macro: 8-Input OR Gate with Non-Inverted Inputs
Supported ArchitecturesThis design element is supported in the following architectures only:
• XC9500
• CoolRunner™ XPLA3
• CoolRunner-II
IntroductionOR functions of up to five inputs are available in any combination of inverting and non-inverting inputs. ORfunctions of six to nine inputs, 12 inputs, and 16 inputs are available with only non-inverting inputs. To invertsome or all inputs, use external inverters. Because each input uses a CLB resource, replace functions with unusedinputs with functions having the necessary number of inputs.
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 579
Chapter 3: About Design Elements
OR9Macro: 9-Input OR Gate with Non-Inverted Inputs
Supported ArchitecturesThis design element is supported in the following architectures only:
• XC9500
• CoolRunner™ XPLA3
• CoolRunner-II
IntroductionOR functions of up to five inputs are available in any combination of inverting and non-inverting inputs. ORfunctions of six to nine inputs, 12 inputs, and 16 inputs are available with only non-inverting inputs. To invertsome or all inputs, use external inverters. Because each input uses a CLB resource, replace functions with unusedinputs with functions having the necessary number of inputs.
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries Guide580 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
PULLDOWNPrimitive: Resistor to GND for Input Pads, Open-Drain, and 3-State Outputs
Supported ArchitecturesThis design element is supported in the following architectures only:
CoolRunner-II
IntroductionThis resistor element is connected to input, output, or bidirectional pads to guarantee a logic Low level fornodes that might float.
Port DescriptionsPort Direction Width Function
O Output 1 Pulldown output (connect directly to top level port)
Design Entry MethodThis design element can be used in schematics.
This element can be connected to a net in the following locations on a top-level schematic file:
• A net connected to an input IO Marker.
• A net connected to both an output IO Marker and 3-statable IO element, such as an OBUFT.
VHDL Instantiation TemplateUnless they already exist, copy the following two statements and paste them before the entity declaration.
Library UNISIM;use UNISIM.vcomponents.all;
-- PULLDOWN: I/O Buffer Weak Pull-down-- All FPGA-- Xilinx HDL Libraries Guide, version 11.2
PULLDOWN_inst : PULLDOWNport map (
O => O -- Pulldown output (connect directly to top-level port));
-- End of PULLDOWN_inst instantiation
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 581
Chapter 3: About Design Elements
Verilog Instantiation Template// PULLDOWN: I/O Buffer Weak Pull-down// All FPGA// Xilinx HDL Libraries Guide, version 11.2
PULLDOWN PULLDOWN_inst (.O(O) // Pulldown output (connect directly to top-level port)
);
// End of PULLDOWN_inst instantiation
For More Information• See the appropriate CPLD User Guide.
• See the appropriate EDK documentation.
CPLD Libraries Guide582 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
PULLUPPrimitive: Resistor to VCC for Input PADs, Open-Drain, and 3-State Outputs
Supported ArchitecturesThis design element is supported in the following architectures only:
• CoolRunner™ XPLA3
• CoolRunner-II
IntroductionThis design element allows for an input, 3-state output or bi-directional port to be driven to a weak highvalue when not being driven by an internal or external source. This element establishes a High logic level foropen-drain elements and macros when all the drivers are off.
Port DescriptionsPort Direction Width Function
O Output 1 Pullup output (connect directly to top level port)
Design Entry MethodThis design element can be used in schematics.
This element can be connected to a net in the following locations on a top-level schematic file:
• A net connected to an input IO Marker
• A net connected to both an output IO Marker and 3-statable IO element, such as an OBUFT.
VHDL Instantiation TemplateUnless they already exist, copy the following two statements and paste them before the entity declaration.
Library UNISIM;use UNISIM.vcomponents.all;
-- PULLUP: I/O Buffer Weak Pull-up-- All FPGA, CoolRunner-II-- Xilinx HDL Libraries Guide, version 11.2
PULLUP_inst : PULLUPport map (
O => O -- Pullup output (connect directly to top-level port));
-- End of PULLUP_inst instantiation
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 583
Chapter 3: About Design Elements
Verilog Instantiation Template// PULLUP: I/O Buffer Weak Pull-up// All FPGA, CoolRunner-II// Xilinx HDL Libraries Guide, version 11.2
PULLUP PULLUP_inst (.O(O) // Pullup output (connect directly to top-level port)
);
// End of PULLUP_inst instantiation
For More Information• See the appropriate CPLD User Guide.
• See the appropriate EDK documentation.
CPLD Libraries Guide584 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
SR16CEMacro: 16-Bit Serial-In Parallel-Out Shift Register with Clock Enable and Asynchronous Clear
Supported ArchitecturesThis design element is supported in the following architectures only:
• XC9500
• CoolRunner™ XPLA3
• CoolRunner-II
IntroductionThis design element is a shift register with a shift-left serial input (SLI), parallel outputs (Q), and clock enable(CE) and asynchronous clear (CLR) inputs. The (CLR) input, when High, overrides all other inputs and resets thedata outputs (Q) Low. When (CE) is High and (CLR) is Low, the data on the SLI input is loaded into the firstbit of the shift register during the Low-to- High clock (C) transition and appears on the (Q0) output. Duringsubsequent Low-to- High clock transitions, when (CE) is High and (CLR) is Low, data shifts to the next highestbit position as new data is loaded into (Q0) (SLI→Q0, Q0→Q1, Q1→Q2, and so forth). The register ignores clocktransitions when (CE) is Low.
Registers can be cascaded by connecting the last (Q) output of one stage to the SLI input of the next stageand connecting clock, (CE), and (CLR) in parallel.
This register is asynchronously cleared, outputs Low, when power is applied.
Logic TableInputs Outputs
CLR CE SLI C Q0 Qz : Q1
1 X X X 0 0
0 0 X X No Change No Change
0 1 SLI ↑ SLI qn-1
z = bit width - 1
qn-1 = state of referenced output one setup time prior to active clock transition
Design Entry MethodThis design element is only for use in schematics.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 585
Chapter 3: About Design Elements
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries Guide586 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
SR16CLEMacro: 16-Bit Loadable Serial/Parallel-In Parallel-Out Shift Register with Clock Enable andAsynchronous Clear
Supported ArchitecturesThis design element is supported in the following architectures only:• XC9500• CoolRunner™ XPLA3• CoolRunner-II
IntroductionThis design element is a shift register with a shift-left serial input (SLI), parallel inputs (D), parallel outputs (Q),and three control inputs: clock enable (CE), load enable (L), and asynchronous clear (CLR) . The register ignoresclock transitions when (L) and (CE) are Low. The asynchronous (CLR), when High, overrides all other inputsand resets the data outputs (Q) Low. When (L) is High and (CLR) is Low, data on the Dn -D0 inputs is loadedinto the corresponding Qn -(Q0) bits of the register.
When (CE) is High and (L) and (CLR) are Low, data on the SLI input is loaded into the first bit of the shiftregister during the Low-to-High clock (C) transition and appears on the (Q0) output. During subsequent clocktransitions, when (CE) is High and (L) and (CLR) are Low, the data shifts to the next highest bit position as newdata is loaded into (Q)0 (for example, SLI→Q0, Q0→Q1, and Q1→Q2).
Registers can be cascaded by connecting the last (Q) output of one stage to the SLI input of the next stage andconnecting clock, (CE), (L), and (CLR) inputs in parallel.
This register is asynchronously cleared, outputs Low, when power is applied.
Logic TableInputs Outputs
CLR L CE SLI Dn : D0 C Q0 Qz : Q1
1 X X X X X 0 0
0 1 X X Dn : D0 ↑ D0 Dn
0 0 1 SLI X ↑ SLI qn-1
0 0 0 X X X No Change No Change
z = bitwidth -1
qn-1 = state of referenced output one setup time prior to active clock transition
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 587
Chapter 3: About Design Elements
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries Guide588 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
SR16CLEDMacro: 16-Bit Shift Register with Clock Enable and Asynchronous Clear
Supported ArchitecturesThis design element is supported in the following architectures only:• XC9500• CoolRunner™ XPLA3• CoolRunner-II
IntroductionThis design element is a shift register with shift-left (SLI) and shift-right (SRI) serial inputs, parallel inputs (D),parallel outputs (Q), and four control inputs: clock enable (CE), load enable (L), shift left/right (LEFT), andasynchronous clear (CLR). The register ignores clock transitions when (CE) and (L) are Low. The asynchronousclear, when High, overrides all other inputs and resets the data outputs (Qn) Low.
When (L) is High and (CLR) is Low, the data on the (D) inputs is loaded into the corresponding (Q) bits of theregister. When (CE) is High and (L) and (CLR) are Low, data is shifted right or left, depending on the state of theLEFT input. If LEFT is High, data on the SLI is loaded into (Q0) during the Low-to-High clock transition andshifted left (for example, to Q1 or Q2) during subsequent clock transitions. If LEFT is Low, data on the SRI isloaded into the last (Q) output during the Low-to-High clock transition and shifted right during subsequentclock transitions. The logic tables indicate the state of the (Q) outputs under all input conditions.
This register is asynchronously cleared, outputs Low, when power is applied.
Logic TableInputs Outputs
CLR L CE LEFT SLI SRID15 :D0 C Q0 Q15
Q14 :Q1
1 X X X X X X X 0 0 0
0 1 X X X X D15 : D0 ↑ D0 D15 Dn
0 0 0 X X X X X NoChange
NoChange
NoChange
0 0 1 1 SLI X X ↑ SLI q14 qn-1
0 0 1 0 X SRI X ↑ q1 SRI qn+1
qn-1 or qn+1 = state of referenced output one setup time prior to active clock transition.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 589
Chapter 3: About Design Elements
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries Guide590 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
SR16REMacro: 16-Bit Serial-In Parallel-Out Shift Register with Clock Enable and Synchronous Reset
Supported ArchitecturesThis design element is supported in the following architectures only:
• XC9500
• CoolRunner™ XPLA3
• CoolRunner-II
IntroductionThis design element is a shift register with shift-left serial input (SLI), parallel outputs (Qn), clock enable (CE),and synchronous reset (R) inputs. The R input, when High, overrides all other inputs during the Low-to-Highclock (C) transition and resets the data outputs (Q) Low.
When (CE) is High and (R) is Low, the data on the (SLI) is loaded into the first bit of the shift register duringthe Low-to-High clock (C) transition and appears on the (Q0) output. During subsequent Low-to-High clocktransitions, when (CE) is High and R is Low, data shifts to the next highest bit position as new data is loaded into(Q0) (for example, SLI→Q0, Q0→Q1, and Q1→Q2). The register ignores clock transitions when (CE) is Low.
Registers can be cascaded by connecting the last (Q) output of one stage to the SLI input of the next stage andconnecting clock, (CE), and (R) in parallel.
This register is asynchronously cleared, outputs Low, when power is applied.
Logic TableInputs Outputs
R CE SLI C Q0 Qz : Q1
1 X X ↑ 0 0
0 0 X X No Change No Change
0 1 SLI ↑ SLI qn-1
z = bitwidth -1
qn-1 = state of referenced output one setup time prior to active clock transition
Design Entry MethodThis design element is only for use in schematics.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 591
Chapter 3: About Design Elements
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries Guide592 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
SR16RLEMacro: 16-Bit Loadable Serial/Parallel-In Parallel-Out Shift Register with Clock Enable andSynchronous Reset
Supported ArchitecturesThis design element is supported in the following architectures only:
• XC9500
• CoolRunner™ XPLA3
• CoolRunner-II
IntroductionThis design element is a shift register with shift-left serial input (SLI), parallel inputs (D), parallel outputs (Q),and three control inputs: clock enable (CE), load enable (L), and synchronous reset (R). The register ignores clocktransitions when (L) and (CE) are Low. The synchronous (R), when High, overrides all other inputs during theLow-to-High clock (C) transition and resets the data outputs (Q) Low. When (L) is High and (R) is Low duringthe Low-to-High clock transition, data on the (D) inputs is loaded into the corresponding Q bits of the register.
When (CE) is High and (L) and (R) are Low, data on the (SLI) input is loaded into the first bit of the shiftregister during the Low-to-High clock (C) transition and appears on the Q0 output. During subsequent clocktransitions, when (CE) is High and (L) and (R) are Low, the data shifts to the next highest bit position as newdata is loaded into Q0.
Registers can be cascaded by connecting the last Q output of one stage to the SLI input of the next stage andconnecting clock, (CE), (L), and (R) inputs in parallel.
This register is asynchronously cleared, outputs Low, when power is applied.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 593
Chapter 3: About Design Elements
Logic TableInputs Outputs
R L CE SLI Dz : D0 C Q0 Qz : Q1
1 X X X X ↑ 0 0
0 1 X X Dz : D0 ↑ D0 Dn
0 0 1 SLI X ↑ SLI qn-1
0 0 0 X X X No Change No Change
z = bitwidth -1
qn-1 = state of referenced output one setup time prior to active clock transition
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries Guide594 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
SR16RLEDMacro: 16-Bit Shift Register with Clock Enable and Synchronous Reset
Supported ArchitecturesThis design element is supported in the following architectures only:
• XC9500
• CoolRunner™ XPLA3
• CoolRunner-II
IntroductionThis design element is a shift register with shift-left (SLI) and shift-right (SRI) serial inputs, parallel inputs (D),parallel outputs (Q) and four control inputs — clock enable (CE), load enable (L), shift left/right (LEFT), andsynchronous reset (R). The register ignores clock transitions when (CE) and (L) are Low. The synchronous (R),when High, overrides all other inputs during the Low-to-High clock (C) transition and resets the data outputs(Q) Low. When (L) is High and (R) is Low during the Low-to-High clock transition, the data on the (D) inputs isloaded into the corresponding (Q) bits of the register.
When (CE) is High and (L) and (R) are Low, data shifts right or left, depending on the state of the LEFT input.If LEFT is High, data on (SLI) is loaded into (Q0) during the Low-to-High clock transition and shifted left (forexample, to Q1 and Q2) during subsequent clock transitions. If LEFT is Low, data on the (SRI) is loaded into thelast (Q) output during the Low-to-High clock transition and shifted right ) during subsequent clock transitions.The logic tables below indicates the state of the (Q) outputs under all input conditions.
This register is asynchronously cleared, outputs Low, when power is applied.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 595
Chapter 3: About Design Elements
Logic TableInputs Outputs
R L CE LEFT SLI SRI D15:D0 C Q0 Q15 Q14:Q1
1 X X X X X X ↑ 0 0 0
0 1 X X X X D15:D0 ↑ D0 D15 Dn
0 0 0 X X X X X NoChange
NoChange
NoChange
0 0 1 1 SLI X X ↑ SLI q14 qn-1
0 0 1 0 X SRI X ↑ q1 SRI qn+1
qn-1 or qn+1 = state of referenced output one setup time prior to active clock transition
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries Guide596 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
SR4CEMacro: 4-Bit Serial-In Parallel-Out Shift Register with Clock Enable and Asynchronous Clear
Supported ArchitecturesThis design element is supported in the following architectures only:
• XC9500
• CoolRunner™ XPLA3
• CoolRunner-II
IntroductionThis design element is a shift register with a shift-left serial input (SLI), parallel outputs (Q), and clock enable(CE) and asynchronous clear (CLR) inputs. The (CLR) input, when High, overrides all other inputs and resets thedata outputs (Q) Low. When (CE) is High and (CLR) is Low, the data on the SLI input is loaded into the firstbit of the shift register during the Low-to- High clock (C) transition and appears on the (Q0) output. Duringsubsequent Low-to- High clock transitions, when (CE) is High and (CLR) is Low, data shifts to the next highestbit position as new data is loaded into (Q0) (SLI→Q0, Q0→Q1, Q1→Q2, and so forth). The register ignores clocktransitions when (CE) is Low.
Registers can be cascaded by connecting the last (Q) output of one stage to the SLI input of the next stageand connecting clock, (CE), and (CLR) in parallel.
This register is asynchronously cleared, outputs Low, when power is applied.
Logic TableInputs Outputs
CLR CE SLI C Q0 Qz : Q1
1 X X X 0 0
0 0 X X No Change No Change
0 1 SLI ↑ SLI qn-1
z = bit width - 1
qn-1 = state of referenced output one setup time prior to active clock transition
Design Entry MethodThis design element is only for use in schematics.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 597
Chapter 3: About Design Elements
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries Guide598 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
SR4CLEMacro: 4-Bit Loadable Serial/Parallel-In Parallel-Out Shift Register with Clock Enable andAsynchronous Clear
Supported ArchitecturesThis design element is supported in the following architectures only:
• XC9500
• CoolRunner™ XPLA3
• CoolRunner-II
IntroductionThis design element is a shift register with a shift-left serial input (SLI), parallel inputs (D), parallel outputs (Q),and three control inputs: clock enable (CE), load enable (L), and asynchronous clear (CLR) . The register ignoresclock transitions when (L) and (CE) are Low. The asynchronous (CLR), when High, overrides all other inputsand resets the data outputs (Q) Low. When (L) is High and (CLR) is Low, data on the Dn -D0 inputs is loadedinto the corresponding Qn -(Q0) bits of the register.
When (CE) is High and (L) and (CLR) are Low, data on the SLI input is loaded into the first bit of the shiftregister during the Low-to-High clock (C) transition and appears on the (Q0) output. During subsequent clocktransitions, when (CE) is High and (L) and (CLR) are Low, the data shifts to the next highest bit position as newdata is loaded into (Q)0 (for example, SLI→Q0, Q0→Q1, and Q1→Q2).
Registers can be cascaded by connecting the last (Q) output of one stage to the SLI input of the next stage andconnecting clock, (CE), (L), and (CLR) inputs in parallel.
This register is asynchronously cleared, outputs Low, when power is applied.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 599
Chapter 3: About Design Elements
Logic TableInputs Outputs
CLR L CE SLI Dn : D0 C Q0 Qz : Q1
1 X X X X X 0 0
0 1 X X Dn : D0 ↑ D0 Dn
0 0 1 SLI X ↑ SLI qn-1
0 0 0 X X X No Change No Change
z = bitwidth -1
qn-1 = state of referenced output one setup time prior to active clock transition
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries Guide600 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
SR4CLEDMacro: 4-Bit Shift Register with Clock Enable and Asynchronous Clear
Supported ArchitecturesThis design element is supported in the following architectures only:
• XC9500
• CoolRunner™ XPLA3
• CoolRunner-II
IntroductionThis design element is a shift register with shift-left (SLI) and shift-right (SRI) serial inputs, parallel inputs (D),parallel outputs (Q), and four control inputs: clock enable (CE), load enable (L), shift left/right (LEFT), andasynchronous clear (CLR). The register ignores clock transitions when (CE) and (L) are Low. The asynchronousclear, when High, overrides all other inputs and resets the data outputs (Qn) Low.
When (L) is High and (CLR) is Low, the data on the (D) inputs is loaded into the corresponding (Q) bits of theregister. When (CE) is High and (L) and (CLR) are Low, data is shifted right or left, depending on the state of theLEFT input. If LEFT is High, data on the SLI is loaded into (Q0) during the Low-to-High clock transition andshifted left (for example, to Q1 or Q2) during subsequent clock transitions. If LEFT is Low, data on the SRI isloaded into the last (Q) output during the Low-to-High clock transition and shifted right during subsequentclock transitions. The logic tables indicate the state of the (Q) outputs under all input conditions.
This register is asynchronously cleared, outputs Low, when power is applied.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 601
Chapter 3: About Design Elements
Logic TableInputs Outputs
CLR L CE LEFT SLI SRI D3 : D0 C Q0 Q3 Q2 : Q1
1 X X X X X X X 0 0 0
0 1 X X X X D3– D0 ↑ D0 D3 Dn
0 0 0 X X X X X NoChange
NoChange
NoChange
0 0 1 1 SLI X X ↑ SLI q2 qn-1
0 0 1 0 X SRI X ↑ q1 SRI qn+1
qn-1 and qn+1 = state of referenced output one setup time prior to active clock transition.
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries Guide602 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
SR4REMacro: 4-Bit Serial-In Parallel-Out Shift Register with Clock Enable and Synchronous Reset
Supported ArchitecturesThis design element is supported in the following architectures only:
• XC9500
• CoolRunner™ XPLA3
• CoolRunner-II
IntroductionThis design element is a shift register with shift-left serial input (SLI), parallel outputs (Qn), clock enable (CE),and synchronous reset (R) inputs. The R input, when High, overrides all other inputs during the Low-to-Highclock (C) transition and resets the data outputs (Q) Low.
When (CE) is High and (R) is Low, the data on the (SLI) is loaded into the first bit of the shift register duringthe Low-to-High clock (C) transition and appears on the (Q0) output. During subsequent Low-to-High clocktransitions, when (CE) is High and R is Low, data shifts to the next highest bit position as new data is loaded into(Q0) (for example, SLI→Q0, Q0→Q1, and Q1→Q2). The register ignores clock transitions when (CE) is Low.
Registers can be cascaded by connecting the last (Q) output of one stage to the SLI input of the next stage andconnecting clock, (CE), and (R) in parallel.
This register is asynchronously cleared, outputs Low, when power is applied.
Logic TableInputs Outputs
R CE SLI C Q0 Qz : Q1
1 X X ↑ 0 0
0 0 X X No Change No Change
0 1 SLI ↑ SLI qn-1
z = bitwidth -1
qn-1 = state of referenced output one setup time prior to active clock transition
Design Entry MethodThis design element is only for use in schematics.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 603
Chapter 3: About Design Elements
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries Guide604 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
SR4RLEMacro: 4-Bit Loadable Serial/Parallel-In Parallel-Out Shift Register with Clock Enable andSynchronous Reset
Supported ArchitecturesThis design element is supported in the following architectures only:
• XC9500
• CoolRunner™ XPLA3
• CoolRunner-II
IntroductionThis design element is a shift register with shift-left serial input (SLI), parallel inputs (D), parallel outputs (Q),and three control inputs: clock enable (CE), load enable (L), and synchronous reset (R). The register ignores clocktransitions when (L) and (CE) are Low. The synchronous (R), when High, overrides all other inputs during theLow-to-High clock (C) transition and resets the data outputs (Q) Low. When (L) is High and (R) is Low duringthe Low-to-High clock transition, data on the (D) inputs is loaded into the corresponding Q bits of the register.
When (CE) is High and (L) and (R) are Low, data on the (SLI) input is loaded into the first bit of the shiftregister during the Low-to-High clock (C) transition and appears on the Q0 output. During subsequent clocktransitions, when (CE) is High and (L) and (R) are Low, the data shifts to the next highest bit position as newdata is loaded into Q0.
Registers can be cascaded by connecting the last Q output of one stage to the SLI input of the next stage andconnecting clock, (CE), (L), and (R) inputs in parallel.
This register is asynchronously cleared, outputs Low, when power is applied.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 605
Chapter 3: About Design Elements
Logic TableInputs Outputs
R L CE SLI Dz : D0 C Q0 Qz : Q1
1 X X X X ↑ 0 0
0 1 X X Dz : D0 ↑ D0 Dn
0 0 1 SLI X ↑ SLI qn-1
0 0 0 X X X No Change No Change
z = bitwidth -1
qn-1 = state of referenced output one setup time prior to active clock transition
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries Guide606 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
SR4RLEDMacro: 4-Bit Shift Register with Clock Enable and Synchronous Reset
Supported ArchitecturesThis design element is supported in the following architectures only:
• XC9500
• CoolRunner™ XPLA3
• CoolRunner-II
IntroductionThis design element is a shift register with shift-left (SLI) and shift-right (SRI) serial inputs, parallel inputs (D),parallel outputs (Q) and four control inputs — clock enable (CE), load enable (L), shift left/right (LEFT), andsynchronous reset (R). The register ignores clock transitions when (CE) and (L) are Low. The synchronous (R),when High, overrides all other inputs during the Low-to-High clock (C) transition and resets the data outputs(Q) Low. When (L) is High and (R) is Low during the Low-to-High clock transition, the data on the (D) inputs isloaded into the corresponding (Q) bits of the register.
When (CE) is High and (L) and (R) are Low, data shifts right or left, depending on the state of the LEFT input.If LEFT is High, data on (SLI) is loaded into (Q0) during the Low-to-High clock transition and shifted left (forexample, to Q1 and Q2) during subsequent clock transitions. If LEFT is Low, data on the (SRI) is loaded into thelast (Q) output during the Low-to-High clock transition and shifted right ) during subsequent clock transitions.The logic tables below indicates the state of the (Q) outputs under all input conditions.
This register is asynchronously cleared, outputs Low, when power is applied.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 607
Chapter 3: About Design Elements
Logic TableInputs Outputs
R L CE LEFT SLI SRI D3 : D0 C Q0 Q3 Q2 : Q1
1 X X X X X X ↑ 0 0 0
0 1 X X X X D3 : D0 ↑ D0 D3 Dn
0 0 0 X X X X X NoChange
NoChange
NoChange
0 0 1 1 SLI X X ↑ SLI q2 qn-1
0 0 1 0 X SRI X ↑ q1 SRI qn+1
qn-1 or qn+1 = state of referenced output one setup time prior to active clock transition
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries Guide608 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
SR8CEMacro: 8-Bit Serial-In Parallel-Out Shift Register with Clock Enable and Asynchronous Clear
Supported ArchitecturesThis design element is supported in the following architectures only:
• XC9500
• CoolRunner™ XPLA3
• CoolRunner-II
IntroductionThis design element is a shift register with a shift-left serial input (SLI), parallel outputs (Q), and clock enable(CE) and asynchronous clear (CLR) inputs. The (CLR) input, when High, overrides all other inputs and resets thedata outputs (Q) Low. When (CE) is High and (CLR) is Low, the data on the SLI input is loaded into the firstbit of the shift register during the Low-to- High clock (C) transition and appears on the (Q0) output. Duringsubsequent Low-to- High clock transitions, when (CE) is High and (CLR) is Low, data shifts to the next highestbit position as new data is loaded into (Q0) (SLI→Q0, Q0→Q1, Q1→Q2, and so forth). The register ignores clocktransitions when (CE) is Low.
Registers can be cascaded by connecting the last (Q) output of one stage to the SLI input of the next stageand connecting clock, (CE), and (CLR) in parallel.
This register is asynchronously cleared, outputs Low, when power is applied.
Logic TableInputs Outputs
CLR CE SLI C Q0 Qz : Q1
1 X X X 0 0
0 0 X X No Change No Change
0 1 SLI ↑ SLI qn-1
z = bit width - 1
qn-1 = state of referenced output one setup time prior to active clock transition
Design Entry MethodThis design element is only for use in schematics.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 609
Chapter 3: About Design Elements
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries Guide610 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
SR8CLEMacro: 8-Bit Loadable Serial/Parallel-In Parallel-Out Shift Register with Clock Enable andAsynchronous Clear
Supported ArchitecturesThis design element is supported in the following architectures only:• XC9500• CoolRunner™ XPLA3• CoolRunner-II
IntroductionThis design element is a shift register with a shift-left serial input (SLI), parallel inputs (D), parallel outputs (Q),and three control inputs: clock enable (CE), load enable (L), and asynchronous clear (CLR) . The register ignoresclock transitions when (L) and (CE) are Low. The asynchronous (CLR), when High, overrides all other inputsand resets the data outputs (Q) Low. When (L) is High and (CLR) is Low, data on the Dn -D0 inputs is loadedinto the corresponding Qn -(Q0) bits of the register.
When (CE) is High and (L) and (CLR) are Low, data on the SLI input is loaded into the first bit of the shiftregister during the Low-to-High clock (C) transition and appears on the (Q0) output. During subsequent clocktransitions, when (CE) is High and (L) and (CLR) are Low, the data shifts to the next highest bit position as newdata is loaded into (Q)0 (for example, SLI→Q0, Q0→Q1, and Q1→Q2).
Registers can be cascaded by connecting the last (Q) output of one stage to the SLI input of the next stage andconnecting clock, (CE), (L), and (CLR) inputs in parallel.
This register is asynchronously cleared, outputs Low, when power is applied.
Logic TableInputs Outputs
CLR L CE SLI Dn : D0 C Q0 Qz : Q1
1 X X X X X 0 0
0 1 X X Dn : D0 ↑ D0 Dn
0 0 1 SLI X ↑ SLI qn-1
0 0 0 X X X No Change No Change
z = bitwidth -1
qn-1 = state of referenced output one setup time prior to active clock transition
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 611
Chapter 3: About Design Elements
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries Guide612 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
SR8CLEDMacro: 8-Bit Shift Register with Clock Enable and Asynchronous Clear
Supported ArchitecturesThis design element is supported in the following architectures only:• XC9500• CoolRunner™ XPLA3• CoolRunner-II
IntroductionThis design element is a shift register with shift-left (SLI) and shift-right (SRI) serial inputs, parallel inputs (D),parallel outputs (Q), and four control inputs: clock enable (CE), load enable (L), shift left/right (LEFT), andasynchronous clear (CLR). The register ignores clock transitions when (CE) and (L) are Low. The asynchronousclear, when High, overrides all other inputs and resets the data outputs (Qn) Low.
When (L) is High and (CLR) is Low, the data on the (D) inputs is loaded into the corresponding (Q) bits of theregister. When (CE) is High and (L) and (CLR) are Low, data is shifted right or left, depending on the state of theLEFT input. If LEFT is High, data on the SLI is loaded into (Q0) during the Low-to-High clock transition andshifted left (for example, to Q1 or Q2) during subsequent clock transitions. If LEFT is Low, data on the SRI isloaded into the last (Q) output during the Low-to-High clock transition and shifted right during subsequentclock transitions. The logic tables indicate the state of the (Q) outputs under all input conditions.
This register is asynchronously cleared, outputs Low, when power is applied.
Logic TableInputs Outputs
CLR L CE LEFT SLI SRI D7 : D0 C Q0 Q7 Q6 : Q1
1 X X X X X X X 0 0 0
0 1 X X X X D7 : D0 ↑ D0 D7 Dn
0 0 0 X X X X X NoChange
NoChange
NoChange
0 0 1 1 SLI X X ↑ SLI q6 qn-1
0 0 1 0 X SRI X ↑ q1 SRI qn+1
qn-1 or qn+1 = state of referenced output one setup time prior to active clock transition.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 613
Chapter 3: About Design Elements
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries Guide614 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
SR8REMacro: 8-Bit Serial-In Parallel-Out Shift Register with Clock Enable and Synchronous Reset
Supported ArchitecturesThis design element is supported in the following architectures only:
• XC9500
• CoolRunner™ XPLA3
• CoolRunner-II
IntroductionThis design element is a shift register with shift-left serial input (SLI), parallel outputs (Qn), clock enable (CE),and synchronous reset (R) inputs. The R input, when High, overrides all other inputs during the Low-to-Highclock (C) transition and resets the data outputs (Q) Low.
When (CE) is High and (R) is Low, the data on the (SLI) is loaded into the first bit of the shift register duringthe Low-to-High clock (C) transition and appears on the (Q0) output. During subsequent Low-to-High clocktransitions, when (CE) is High and R is Low, data shifts to the next highest bit position as new data is loaded into(Q0) (for example, SLI→Q0, Q0→Q1, and Q1→Q2). The register ignores clock transitions when (CE) is Low.
Registers can be cascaded by connecting the last (Q) output of one stage to the SLI input of the next stage andconnecting clock, (CE), and (R) in parallel.
This register is asynchronously cleared, outputs Low, when power is applied.
Logic TableInputs Outputs
R CE SLI C Q0 Qz : Q1
1 X X ↑ 0 0
0 0 X X No Change No Change
0 1 SLI ↑ SLI qn-1
z = bitwidth -1
qn-1 = state of referenced output one setup time prior to active clock transition
Design Entry MethodThis design element is only for use in schematics.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 615
Chapter 3: About Design Elements
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries Guide616 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
SR8RLEMacro: 8-Bit Loadable Serial/Parallel-In Parallel-Out Shift Register with Clock Enable andSynchronous Reset
Supported ArchitecturesThis design element is supported in the following architectures only:
• XC9500
• CoolRunner™ XPLA3
• CoolRunner-II
IntroductionThis design element is a shift register with shift-left serial input (SLI), parallel inputs (D), parallel outputs (Q),and three control inputs: clock enable (CE), load enable (L), and synchronous reset (R). The register ignores clocktransitions when (L) and (CE) are Low. The synchronous (R), when High, overrides all other inputs during theLow-to-High clock (C) transition and resets the data outputs (Q) Low. When (L) is High and (R) is Low duringthe Low-to-High clock transition, data on the (D) inputs is loaded into the corresponding Q bits of the register.
When (CE) is High and (L) and (R) are Low, data on the (SLI) input is loaded into the first bit of the shiftregister during the Low-to-High clock (C) transition and appears on the Q0 output. During subsequent clocktransitions, when (CE) is High and (L) and (R) are Low, the data shifts to the next highest bit position as newdata is loaded into Q0.
Registers can be cascaded by connecting the last Q output of one stage to the SLI input of the next stage andconnecting clock, (CE), (L), and (R) inputs in parallel.
This register is asynchronously cleared, outputs Low, when power is applied.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 617
Chapter 3: About Design Elements
Logic TableInputs Outputs
R L CE SLI Dz : D0 C Q0 Qz : Q1
1 X X X X ↑ 0 0
0 1 X X Dz : D0 ↑ D0 Dn
0 0 1 SLI X ↑ SLI qn-1
0 0 0 X X X No Change No Change
z = bitwidth -1
qn-1 = state of referenced output one setup time prior to active clock transition
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries Guide618 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
SR8RLEDMacro: 8-Bit Shift Register with Clock Enable and Synchronous Reset
Supported ArchitecturesThis design element is supported in the following architectures only:
• XC9500
• CoolRunner™ XPLA3
• CoolRunner-II
IntroductionThis design element is a shift register with shift-left (SLI) and shift-right (SRI) serial inputs, parallel inputs (D),parallel outputs (Q) and four control inputs — clock enable (CE), load enable (L), shift left/right (LEFT), andsynchronous reset (R). The register ignores clock transitions when (CE) and (L) are Low. The synchronous (R),when High, overrides all other inputs during the Low-to-High clock (C) transition and resets the data outputs(Q) Low. When (L) is High and (R) is Low during the Low-to-High clock transition, the data on the (D) inputs isloaded into the corresponding (Q) bits of the register.
When (CE) is High and (L) and (R) are Low, data shifts right or left, depending on the state of the LEFT input.If LEFT is High, data on (SLI) is loaded into (Q0) during the Low-to-High clock transition and shifted left (forexample, to Q1 and Q2) during subsequent clock transitions. If LEFT is Low, data on the (SRI) is loaded into thelast (Q) output during the Low-to-High clock transition and shifted right ) during subsequent clock transitions.The logic tables below indicates the state of the (Q) outputs under all input conditions.
This register is asynchronously cleared, outputs Low, when power is applied.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 619
Chapter 3: About Design Elements
Logic TableInputs Outputs
R L CE LEFT SLI SRI D7 : D0 C Q0 Q7 Q6 : Q1
1 X X X X X X ↑ 0 0 0
0 1 X X X X D7 : D0 ↑ D0 D7 Dn
0 0 0 X X X X X NoChange
NoChange
NoChange
0 0 1 1 SLI X X ↑ SLI q6 qn-1
0 0 1 0 X SRI X ↑ q1 SRI qn+1
qn-1 or qn+1 = state of referenced output one setup time prior to active clock transition
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries Guide620 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
SRD16CEMacro: 16-Bit Serial-In Parallel-Out Dual Edge Triggered Shift Register with Clock Enable andAsynchronous Clear
Supported ArchitecturesThis design element is supported in the following architectures only:CoolRunner™-II
IntroductionThis design element is a dual edge triggered shift register with a shift-left serial input (SLI), parallel outputs (Q),clock enable (CE) and asynchronous clear (CLR) inputs. The CLR input, when High, overrides all other inputsand resets the data outputs (Q) Low. When CE is High and CLR is Low, the data on the SLI input is loaded intothe first bit of the shift register during the Low-to-High (or High-to-Low) clock (C) transition and appears on theQ0 output. During subsequent clock transitions, when CE is High and CLR is Low, data shifts to the next highestbit position as new data is loaded into Q0. The register ignores clock transitions when CE is Low.
Registers can be cascaded by connecting the last Q output of one stage to the SLI input of the next stage andconnecting clock, CE, and CLR in parallel.
This register is asynchronously cleared, outputs Low, when power is applied.
The power-on condition can be simulated by applying a High-level pulse on the PRLD global net.
Logic TableInputs Outputs
CLR CE SLI C Q0 Qz : Q1
1 X X X 0 0
0 0 X X No Change No Change
0 1 1 ↑ 1 qn-1
0 1 1 ↓ 1 qn-1
0 1 0 ↑ 0 qn-1
0 1 0 ↓ 0 qn-1
z = bitwidth -1
qn-1 = state of referenced output one setup time prior to active clock transition
Design Entry MethodThis design element is only for use in schematics.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 621
Chapter 3: About Design Elements
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries Guide622 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
SRD16CLEMacro: 16-Bit Loadable Serial/Parallel-In Parallel-Out Dual Edge Triggered Shift Register withClock Enable and Asynchronous Clear
Supported ArchitecturesThis design element is supported in the following architectures only:
CoolRunner™-II
IntroductionThis design element is a dual edge triggered shift register with a shift-left serial input (SLI), parallel inputs (D),parallel outputs (Q), and three control inputs: clock enable (CE), load enable (L), and asynchronous clear (CLR).The register ignores clock transitions when L and CE are Low. The asynchronous CLR, when High, overrides allother inputs and resets the data outputs (Q) Low. When L is High and CLR is Low, data on the Dn:D0 inputs isloaded into the corresponding Qn:Q0 bits of the register. When CE is High and L and CLR are Low, data onthe SLI input is loaded into the first bit of the shift register during the Low-to-High (or High-to-Low) clock (C)transition and appears on the Q0 output. During subsequent clock transitions, when CE is High and L and CLRare Low, the data shifts to the next highest bit position as new data is loaded into Q0.
Registers can be cascaded by connecting the last Q output of one stage to the SLI input of the next stage andconnecting clock, CE, L, and CLR inputs in parallel.
This register is asynchronously cleared, outputs Low, when power is applied. The power-on condition can besimulated by applying a High-level pulse on the PRLD global net.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 623
Chapter 3: About Design Elements
Logic TableInputs Outputs
CLR L CE SLI Dn:D0 C Q0 Qz:Q1
1 X X X X X 0 0
0 1 X X Dn:D0 ↑ D0 Dn
0 1 X X Dn:D0 ↓ D0 Dn
0 0 1 SLI X ↑ SLI qn-1
0 0 1 SLI X ↓ SLI qn-1
0 0 0 X X X No Change No Change
z = bitwidth -1
qn-1 = state of referenced output one setup time prior to active clock transition
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries Guide624 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
SRD16CLEDMacro: 16-Bit Dual Edge Triggered Shift Register with Clock Enable and Asynchronous Clear
Supported ArchitecturesThis design element is supported in the following architectures only:
CoolRunner™-II
IntroductionThis design element is a dual edge triggered shift register with shift-left (SLI) and shift-right (SRI) serial inputs,parallel inputs (D), parallel outputs (Q), and four control inputs: clock enable (CE), load enable (L), shift left/right(LEFT), and asynchronous clear (CLR). The register ignores clock transitions when CE and L are Low. Theasynchronous clear, when High, overrides all other inputs and resets the data outputs (Qn) Low. When L is Highand CLR is Low, the data on the D inputs is loaded into the corresponding Q bits of the register. When CE isHigh and L and CLR are Low, data is shifted right or left, depending on the state of the LEFT input. If LEFT isHigh, data on the SLI is loaded into Q0 during the Low-to-High or High-to-Low clock transition and shifted leftduring subsequent clock transitions. If LEFT is Low, data on the SRI is loaded into the last Q output duringthe Low-to-High or High-to-Low clock transition and shifted right during subsequent clock transitions. Thelogic table indicates the state of the Q outputs under all input conditions.
This register is asynchronously cleared, outputs Low, when power is applied. The power-on condition can besimulated by applying a High-level pulse on the PRLD global net.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 625
Chapter 3: About Design Elements
Logic TableInputs Outputs
CLR L CE LEFT SLI SRID15 :D0 C Q0 Q15
Q14 :Q1
1 X X X X X X X 0 0 0
0 1 X X X X D15 : D0 ↑ D0 D15 Dn
0 1 X X X X D15 : D0 ↓ D0 D15 Dn
0 0 0 X X X X X NoChange
NoChange
NoChange
0 0 1 1 SLI X X ↑ SLI q14 qn-1
0 0 1 1 SLI X X ↓ SLI q14 qn-1
0 0 1 0 X SRI X ↑ q1 SRI qn+1
0 0 1 0 X SRI X ↓ q1 SRI qn+1
qn-1 or qn+1 = state of referenced output one setup time prior to active clock transition.
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries Guide626 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
SRD16REMacro: 16-Bit Serial-In Parallel-Out Dual Edge Triggered Shift Register with Clock Enable andSynchronous Reset
Supported ArchitecturesThis design element is supported in the following architectures only:
CoolRunner™-II
IntroductionThis design element is a dual edge triggered shift register with shift-left serial input (SLI), parallel outputs (Qn),clock enable (CE), and synchronous reset (R) inputs. The R input, when High, overrides all other inputs duringthe Low-to-High or High-to-Low clock (C) transition and resets the data outputs (Q) Low. When CE is Highand R is Low, the data on the SLI is loaded into the first bit of the shift register during the Low-to-High clock orHigh-to-Low (C) transition and appears on the Q0 output. During subsequent clock transitions, when CE isHigh and R is Low, data shifts to the next highest bit position as new data is loaded into Q0. The registerignores clock transitions when CE is Low.
Registers can be cascaded by connecting the last Q output of one stage to the SLI input of the next stage andconnecting clock, CE, and R in parallel.
This register is asynchronously cleared, outputs Low, when power is applied. The power-on condition can besimulated by applying a High-level pulse on the PRLD global net.
Logic TableInputs Outputs
R CE SLI C Q0 Qz:Q1
1 X X ↑ 0 0
1 X X ↓ 0 0
0 0 X X No Change No Change
0 1 1 ↑ 1 qn-1
0 1 1 ↓ 1 qn-1
0 1 0 ↑ 0 qn-1
0 1 0 ↓ 0 qn-1
z = bitwidth -1
qn-1 = state of referenced output one setup time prior to active clock transition
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 627
Chapter 3: About Design Elements
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries Guide628 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
SRD16RLEMacro: 16-Bit Loadable Serial/Parallel-In Parallel-Out Dual Edge Triggered Shift Register withClock Enable and Synchronous Reset
Supported ArchitecturesThis design element is supported in the following architectures only:
CoolRunner™-II
IntroductionThis design element is a dual edge triggered shift register with shift-left serial input (SLI), parallel inputs (D),parallel outputs (Q), and three control inputs: clock enable (CE), load enable (L), and synchronous reset (R). Theregister ignores clock transitions when L and CE are Low. The synchronous R, when High, overrides all otherinputs during the Low-to-High or High-to-Low clock (C) transition and resets the data outputs (Q) Low. When Lis High and R is Low, data on the D inputs is loaded into the corresponding Q bits of the register. When CE is Highand L and R are Low, data on the SLI input is loaded into the first bit of the shift register during the Low-to-Highor High-to-Low clock (C) transition and appears on the Q0 output. During subsequent clock transitions, whenCE is High and L and R are Low, the data shifts to the next highest bit position as new data is loaded into Q0.
Registers can be cascaded by connecting the last Q output of one stage to the SLI input of the next stage andconnecting clock, CE, L, and R inputs in parallel.
This register is asynchronously cleared, outputs Low, when power is applied. The power-on condition can besimulated by applying a High-level pulse on the PRLD global net.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 629
Chapter 3: About Design Elements
Logic TableInputs Outputs
R L CE SLI Dz:D0 C Q0 Qz:Q1
1 X X X X ↑ 0 0
1 X X X X ↓ 0 0
0 1 X X Dz:D0 ↑ D0 Dn
0 1 X X Dz:D0 ↓ D0 Dn
0 0 1 SLI X ↑ SLI qn-1
0 0 1 SLI X ↓ SLI qn-1
0 0 0 X X X No Change No Change
z = bitwidth -1
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries Guide630 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
SRD16RLEDMacro: 16-Bit Dual Edge Triggered Shift Register with Clock Enable and Synchronous Reset
Supported ArchitecturesThis design element is supported in the following architectures only:
CoolRunner™-II
IntroductionThis design element is a dual edge triggered shift register with shift-left (SLI) and shift-right (SRDI) serialinputs, parallel inputs (D), parallel outputs (Q), and four control inputs — clock enable (CE), load enable (L),shift left/right (LEFT), and synchronous reset (R). The register ignores clock transitions when CE and L areLow. The synchronous R, when High, overrides all other inputs during the Low-to-High or High-to-Lowclock (C) transition and resets the data outputs (Q) Low. When L is High and R is Low, the data on the Dinputs is loaded into the corresponding Q bits of the register. When CE is High and L and R are Low, data isshifted right or left, depending on the state of the LEFT input. If LEFT is High, data on SLI is loaded into Q0during the Low-to-High or High-to-Low clock transition and shifted left (to Q1, Q2, etc.) during subsequentclock transitions. If LEFT is Low, data on the SRDI is loaded into the last Q output during the Low-to-High orHigh-to-Low clock transition and shifted right during subsequent clock transitions. The logic table indicatesthe state of the Q outputs under all input conditions.
This register is asynchronously cleared, outputs Low, when power is applied. The power-on condition can besimulated by applying a High-level pulse on the PRLD global net.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 631
Chapter 3: About Design Elements
Logic TableInputs Outputs
R L CE LEFT SLI SRDID15 :D0 C Q0 Q15
Q14 :Q1
1 X X X X X X ↑ 0 0 0
1 X X X X X X ↓ 0 0 0
0 1 X X X X D15 : D0 ↑ D0 D15 Dn
0 1 X X X X D15 : D0 ↓ D0 D15 Dn
0 0 0 X X X X X NoChange
NoChange
NoChange
0 0 1 1 SLI X X ↑ SLI q14 qn-1
0 0 1 1 SLI X X ↓ SLI q14 qn-1
0 0 1 0 X SRDI X ↑ q1 SRDI qn+1
0 0 1 0 X SRDI X ↓ q1 SRDI qn+1
qn-1 or qn+1 = state of referenced output one setup time prior to active clock transition
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries Guide632 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
SRD4CEMacro: 4-Bit Serial-In Parallel-Out Dual Edge Triggered Shift Register with Clock Enable andAsynchronous Clear
Supported ArchitecturesThis design element is supported in the following architectures only:CoolRunner™-II
IntroductionThis design element is a dual edge triggered shift register with a shift-left serial input (SLI), parallel outputs (Q),clock enable (CE) and asynchronous clear (CLR) inputs. The CLR input, when High, overrides all other inputsand resets the data outputs (Q) Low. When CE is High and CLR is Low, the data on the SLI input is loaded intothe first bit of the shift register during the Low-to-High (or High-to-Low) clock (C) transition and appears on theQ0 output. During subsequent clock transitions, when CE is High and CLR is Low, data shifts to the next highestbit position as new data is loaded into Q0. The register ignores clock transitions when CE is Low.
Registers can be cascaded by connecting the last Q output of one stage to the SLI input of the next stage andconnecting clock, CE, and CLR in parallel.
This register is asynchronously cleared, outputs Low, when power is applied.
The power-on condition can be simulated by applying a High-level pulse on the PRLD global net.
Logic TableInputs Outputs
CLR CE SLI C Q0 Qz : Q1
1 X X X 0 0
0 0 X X No Change No Change
0 1 1 ↑ 1 qn-1
0 1 1 ↓ 1 qn-1
0 1 0 ↑ 0 qn-1
0 1 0 ↓ 0 qn-1
z = bitwidth -1
qn-1 = state of referenced output one setup time prior to active clock transition
Design Entry MethodThis design element is only for use in schematics.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 633
Chapter 3: About Design Elements
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries Guide634 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
SRD4CLEMacro: 4-Bit Loadable Serial/Parallel-In Parallel-Out Dual Edge Triggered Shift Register withClock Enable and Asynchronous Clear
Supported ArchitecturesThis design element is supported in the following architectures only:
CoolRunner™-II
IntroductionThis design element is a dual edge triggered shift register with a shift-left serial input (SLI), parallel inputs (D),parallel outputs (Q), and three control inputs: clock enable (CE), load enable (L), and asynchronous clear (CLR).The register ignores clock transitions when L and CE are Low. The asynchronous CLR, when High, overrides allother inputs and resets the data outputs (Q) Low. When L is High and CLR is Low, data on the Dn:D0 inputs isloaded into the corresponding Qn:Q0 bits of the register. When CE is High and L and CLR are Low, data onthe SLI input is loaded into the first bit of the shift register during the Low-to-High (or High-to-Low) clock (C)transition and appears on the Q0 output. During subsequent clock transitions, when CE is High and L and CLRare Low, the data shifts to the next highest bit position as new data is loaded into Q0.
Registers can be cascaded by connecting the last Q output of one stage to the SLI input of the next stage andconnecting clock, CE, L, and CLR inputs in parallel.
This register is asynchronously cleared, outputs Low, when power is applied. The power-on condition can besimulated by applying a High-level pulse on the PRLD global net.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 635
Chapter 3: About Design Elements
Logic TableInputs Outputs
CLR L CE SLI Dn:D0 C Q0 Qz:Q1
1 X X X X X 0 0
0 1 X X Dn:D0 ↑ D0 Dn
0 1 X X Dn:D0 ↓ D0 Dn
0 0 1 SLI X ↑ SLI qn-1
0 0 1 SLI X ↓ SLI qn-1
0 0 0 X X X No Change No Change
z = bitwidth -1
qn-1 = state of referenced output one setup time prior to active clock transition
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries Guide636 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
SRD4CLEDMacro: 4-Bit Dual Edge Triggered Shift Register with Clock Enable and Asynchronous Clear
Supported ArchitecturesThis design element is supported in the following architectures only:
CoolRunner™-II
IntroductionThis design element is a dual edge triggered shift register with shift-left (SLI) and shift-right (SRI) serial inputs,parallel inputs (D), parallel outputs (Q), and four control inputs: clock enable (CE), load enable (L), shift left/right(LEFT), and asynchronous clear (CLR). The register ignores clock transitions when CE and L are Low. Theasynchronous clear, when High, overrides all other inputs and resets the data outputs (Qn) Low. When L is Highand CLR is Low, the data on the D inputs is loaded into the corresponding Q bits of the register. When CE isHigh and L and CLR are Low, data is shifted right or left, depending on the state of the LEFT input. If LEFT isHigh, data on the SLI is loaded into Q0 during the Low-to-High or High-to-Low clock transition and shifted leftduring subsequent clock transitions. If LEFT is Low, data on the SRI is loaded into the last Q output duringthe Low-to-High or High-to-Low clock transition and shifted right during subsequent clock transitions. Thelogic table indicates the state of the Q outputs under all input conditions.
This register is asynchronously cleared, outputs Low, when power is applied. The power-on condition can besimulated by applying a High-level pulse on the PRLD global net.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 637
Chapter 3: About Design Elements
Logic TableInputs Outputs
CLR L CE LEFT SLI SRI D3:D0 C Q0 Q3 Q2:Q1
1 X X X X X X X 0 0 0
0 1 X X X X D3:D0 ↑ D0 D3 Dn
0 1 X X X X D3:D0 ↓ D0 D3 Dn
0 0 0 X X X X X NoChange
NoChange
NoChange
0 0 1 1 SLI X X ↑ SLI q2 qn-1
0 0 1 1 SLI X X ↓ SLI q2 qn-1
0 0 1 0 X SRI X ↑ q1 SRI qn+1
0 0 1 0 X SRI X ↓ q1 SRI qn+1
qn-1 and qn+1 = state of referenced output one setup time prior to active clock transition
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries Guide638 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
SRD4REMacro: 4-Bit Serial-In Parallel-Out Dual Edge Triggered Shift Register with Clock Enable andSynchronous Reset
Supported ArchitecturesThis design element is supported in the following architectures only:
CoolRunner™-II
IntroductionThis design element is a dual edge triggered shift register with shift-left serial input (SLI), parallel outputs (Qn),clock enable (CE), and synchronous reset (R) inputs. The R input, when High, overrides all other inputs duringthe Low-to-High or High-to-Low clock (C) transition and resets the data outputs (Q) Low. When CE is Highand R is Low, the data on the SLI is loaded into the first bit of the shift register during the Low-to-High clock orHigh-to-Low (C) transition and appears on the Q0 output. During subsequent clock transitions, when CE isHigh and R is Low, data shifts to the next highest bit position as new data is loaded into Q0. The registerignores clock transitions when CE is Low.
Registers can be cascaded by connecting the last Q output of one stage to the SLI input of the next stage andconnecting clock, CE, and R in parallel.
This register is asynchronously cleared, outputs Low, when power is applied. The power-on condition can besimulated by applying a High-level pulse on the PRLD global net.
Logic TableInputs Outputs
R CE SLI C Q0 Qz:Q1
1 X X ↑ 0 0
1 X X ↓ 0 0
0 0 X X No Change No Change
0 1 1 ↑ 1 qn-1
0 1 1 ↓ 1 qn-1
0 1 0 ↑ 0 qn-1
0 1 0 ↓ 0 qn-1
z = bitwidth -1
qn-1 = state of referenced output one setup time prior to active clock transition
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 639
Chapter 3: About Design Elements
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries Guide640 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
SRD4RLEMacro: 4-Bit Loadable Serial/Parallel-In Parallel-Out Dual Edge Triggered Shift Register withClock Enable and Synchronous Reset
Supported ArchitecturesThis design element is supported in the following architectures only:
CoolRunner™-II
IntroductionThis design element is a dual edge triggered shift register with shift-left serial input (SLI), parallel inputs (D),parallel outputs (Q), and three control inputs: clock enable (CE), load enable (L), and synchronous reset (R). Theregister ignores clock transitions when L and CE are Low. The synchronous R, when High, overrides all otherinputs during the Low-to-High or High-to-Low clock (C) transition and resets the data outputs (Q) Low. When Lis High and R is Low, data on the D inputs is loaded into the corresponding Q bits of the register. When CE is Highand L and R are Low, data on the SLI input is loaded into the first bit of the shift register during the Low-to-Highor High-to-Low clock (C) transition and appears on the Q0 output. During subsequent clock transitions, whenCE is High and L and R are Low, the data shifts to the next highest bit position as new data is loaded into Q0.
Registers can be cascaded by connecting the last Q output of one stage to the SLI input of the next stage andconnecting clock, CE, L, and R inputs in parallel.
This register is asynchronously cleared, outputs Low, when power is applied. The power-on condition can besimulated by applying a High-level pulse on the PRLD global net.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 641
Chapter 3: About Design Elements
Logic TableInputs Outputs
R L CE SLI Dz:D0 C Q0 Qz:Q1
1 X X X X ↑ 0 0
1 X X X X ↓ 0 0
0 1 X X Dz:D0 ↑ D0 Dn
0 1 X X Dz:D0 ↓ D0 Dn
0 0 1 SLI X ↑ SLI qn-1
0 0 1 SLI X ↓ SLI qn-1
0 0 0 X X X No Change No Change
z = bitwidth -1
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries Guide642 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
SRD4RLEDMacro: 4-Bit Dual Edge Triggered Shift Register with Clock Enable and Synchronous Reset
Supported ArchitecturesThis design element is supported in the following architectures only:
CoolRunner™-II
IntroductionThis design element is a dual edge triggered shift register with shift-left (SLI) and shift-right (SRDI) serialinputs, parallel inputs (D), parallel outputs (Q), and four control inputs — clock enable (CE), load enable (L),shift left/right (LEFT), and synchronous reset (R). The register ignores clock transitions when CE and L areLow. The synchronous R, when High, overrides all other inputs during the Low-to-High or High-to-Lowclock (C) transition and resets the data outputs (Q) Low. When L is High and R is Low, the data on the Dinputs is loaded into the corresponding Q bits of the register. When CE is High and L and R are Low, data isshifted right or left, depending on the state of the LEFT input. If LEFT is High, data on SLI is loaded into Q0during the Low-to-High or High-to-Low clock transition and shifted left (to Q1, Q2, etc.) during subsequentclock transitions. If LEFT is Low, data on the SRDI is loaded into the last Q output during the Low-to-High orHigh-to-Low clock transition and shifted right during subsequent clock transitions. The logic table indicatesthe state of the Q outputs under all input conditions.
This register is asynchronously cleared, outputs Low, when power is applied. The power-on condition can besimulated by applying a High-level pulse on the PRLD global net.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 643
Chapter 3: About Design Elements
Logic TableInputs Outputs
R L CE LEFT SLI SRDI D3:D0 C Q0 Q3 Q2:Q1
1 X X X X X X↑ ↑ 0 0 0
1 X X X X X X ↓ 0 0 0
0 1 X X X X D3 : D0 ↑ D0 D3 Dn
0 1 X X X X D3 : D0 ↓ D0 D3 Dn
0 0 0 X X X X X NoChange
NoChange
NoChange
0 0 1 1 SLI X X ↑ SLI q2 qn-1
0 0 1 1 SLI X X ↓ SLI q2 qn-1
0 0 1 0 X SRDI X ↑ q1 SRDI qn+1
0 0 1 0 X SRDI X ↓ q1 SRDI qn+1
qn-1 or qn+1 = state of referenced output one setup time prior to active clock transition
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries Guide644 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
SRD8CEMacro: 8-Bit Serial-In Parallel-Out Dual Edge Triggered Shift Register with Clock Enable andAsynchronous Clear
Supported ArchitecturesThis design element is supported in the following architectures only:CoolRunner™-II
IntroductionThis design element is a dual edge triggered shift register with a shift-left serial input (SLI), parallel outputs (Q),clock enable (CE) and asynchronous clear (CLR) inputs. The CLR input, when High, overrides all other inputsand resets the data outputs (Q) Low. When CE is High and CLR is Low, the data on the SLI input is loaded intothe first bit of the shift register during the Low-to-High (or High-to-Low) clock (C) transition and appears on theQ0 output. During subsequent clock transitions, when CE is High and CLR is Low, data shifts to the next highestbit position as new data is loaded into Q0. The register ignores clock transitions when CE is Low.
Registers can be cascaded by connecting the last Q output of one stage to the SLI input of the next stage andconnecting clock, CE, and CLR in parallel.
This register is asynchronously cleared, outputs Low, when power is applied.
The power-on condition can be simulated by applying a High-level pulse on the PRLD global net.
Logic TableInputs Outputs
CLR CE SLI C Q0 Qz : Q1
1 X X X 0 0
0 0 X X No Change No Change
0 1 1 ↑ 1 qn-1
0 1 1 ↓ 1 qn-1
0 1 0 ↑ 0 qn-1
0 1 0 ↓ 0 qn-1
z = bitwidth -1
qn-1 = state of referenced output one setup time prior to active clock transition
Design Entry MethodThis design element is only for use in schematics.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 645
Chapter 3: About Design Elements
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries Guide646 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
SRD8CLEMacro: 8-Bit Loadable Serial/Parallel-In Parallel-Out Dual Edge Triggered Shift Register withClock Enable and Asynchronous Clear
Supported ArchitecturesThis design element is supported in the following architectures only:
CoolRunner™-II
IntroductionThis design element is a dual edge triggered shift register with a shift-left serial input (SLI), parallel inputs (D),parallel outputs (Q), and three control inputs: clock enable (CE), load enable (L), and asynchronous clear (CLR).The register ignores clock transitions when L and CE are Low. The asynchronous CLR, when High, overrides allother inputs and resets the data outputs (Q) Low. When L is High and CLR is Low, data on the Dn:D0 inputs isloaded into the corresponding Qn:Q0 bits of the register. When CE is High and L and CLR are Low, data onthe SLI input is loaded into the first bit of the shift register during the Low-to-High (or High-to-Low) clock (C)transition and appears on the Q0 output. During subsequent clock transitions, when CE is High and L and CLRare Low, the data shifts to the next highest bit position as new data is loaded into Q0.
Registers can be cascaded by connecting the last Q output of one stage to the SLI input of the next stage andconnecting clock, CE, L, and CLR inputs in parallel.
This register is asynchronously cleared, outputs Low, when power is applied. The power-on condition can besimulated by applying a High-level pulse on the PRLD global net.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 647
Chapter 3: About Design Elements
Logic TableInputs Outputs
CLR L CE SLI Dn:D0 C Q0 Qz:Q1
1 X X X X X 0 0
0 1 X X Dn:D0 ↑ D0 Dn
0 1 X X Dn:D0 ↓ D0 Dn
0 0 1 SLI X ↑ SLI qn-1
0 0 1 SLI X ↓ SLI qn-1
0 0 0 X X X No Change No Change
z = bitwidth -1
qn-1 = state of referenced output one setup time prior to active clock transition
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries Guide648 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
SRD8CLEDMacro: 8-Bit Dual Edge Triggered Shift Register with Clock Enable and Asynchronous Clear
Supported ArchitecturesThis design element is supported in the following architectures only:
CoolRunner™-II
IntroductionThis design element is a dual edge triggered shift register with shift-left (SLI) and shift-right (SRI) serial inputs,parallel inputs (D), parallel outputs (Q), and four control inputs: clock enable (CE), load enable (L), shift left/right(LEFT), and asynchronous clear (CLR). The register ignores clock transitions when CE and L are Low. Theasynchronous clear, when High, overrides all other inputs and resets the data outputs (Qn) Low. When L is Highand CLR is Low, the data on the D inputs is loaded into the corresponding Q bits of the register. When CE isHigh and L and CLR are Low, data is shifted right or left, depending on the state of the LEFT input. If LEFT isHigh, data on the SLI is loaded into Q0 during the Low-to-High or High-to-Low clock transition and shifted leftduring subsequent clock transitions. If LEFT is Low, data on the SRI is loaded into the last Q output duringthe Low-to-High or High-to-Low clock transition and shifted right during subsequent clock transitions. Thelogic table indicates the state of the Q outputs under all input conditions.
This register is asynchronously cleared, outputs Low, when power is applied. The power-on condition can besimulated by applying a High-level pulse on the PRLD global net.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 649
Chapter 3: About Design Elements
Logic TableInputs Outputs
CLR L CE LEFT SLI SRI D7:D0 C Q0 Q7 Q6:Q1
1 X X X X X X X 0 0 0
0 1 X X X X D7:D0 ↑ D0 D7 Dn
0 1 X X X X D7:D0 ↓ D0 D7 Dn
0 0 0 X X X X X NoChange
NoChange
NoChange
0 0 1 1 SLI X X ↑ SLI q6 qn-1
0 0 1 1 SLI X X ↓ SLI q6 qn-1
0 0 1 0 X SRI X ↑ q1 SRI qn+1
0 0 1 0 X SRI X ↓ q1 SRI qn+1
qn-1 or qn+1 = state of referenced output one setup time prior to active clock transition
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries Guide650 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
SRD8REMacro: 8-Bit Serial-In Parallel-Out Dual Edge Triggered Shift Register with Clock Enable andSynchronous Reset
Supported ArchitecturesThis design element is supported in the following architectures only:
CoolRunner™-II
IntroductionThis design element is a dual edge triggered shift register with shift-left serial input (SLI), parallel outputs (Qn),clock enable (CE), and synchronous reset (R) inputs. The R input, when High, overrides all other inputs duringthe Low-to-High or High-to-Low clock (C) transition and resets the data outputs (Q) Low. When CE is Highand R is Low, the data on the SLI is loaded into the first bit of the shift register during the Low-to-High clock orHigh-to-Low (C) transition and appears on the Q0 output. During subsequent clock transitions, when CE isHigh and R is Low, data shifts to the next highest bit position as new data is loaded into Q0. The registerignores clock transitions when CE is Low.
Registers can be cascaded by connecting the last Q output of one stage to the SLI input of the next stage andconnecting clock, CE, and R in parallel.
This register is asynchronously cleared, outputs Low, when power is applied. The power-on condition can besimulated by applying a High-level pulse on the PRLD global net.
Logic TableInputs Outputs
R CE SLI C Q0 Qz:Q1
1 X X ↑ 0 0
1 X X ↓ 0 0
0 0 X X No Change No Change
0 1 1 ↑ 1 qn-1
0 1 1 ↓ 1 qn-1
0 1 0 ↑ 0 qn-1
0 1 0 ↓ 0 qn-1
z = bitwidth -1
qn-1 = state of referenced output one setup time prior to active clock transition
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 651
Chapter 3: About Design Elements
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries Guide652 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
SRD8RLEMacro: 8-Bit Loadable Serial/Parallel-In Parallel-Out Dual Edge Triggered Shift Register withClock Enable and Synchronous Reset
Supported ArchitecturesThis design element is supported in the following architectures only:
CoolRunner™-II
IntroductionThis design element is a dual edge triggered shift register with shift-left serial input (SLI), parallel inputs (D),parallel outputs (Q), and three control inputs: clock enable (CE), load enable (L), and synchronous reset (R). Theregister ignores clock transitions when L and CE are Low. The synchronous R, when High, overrides all otherinputs during the Low-to-High or High-to-Low clock (C) transition and resets the data outputs (Q) Low. When Lis High and R is Low, data on the D inputs is loaded into the corresponding Q bits of the register. When CE is Highand L and R are Low, data on the SLI input is loaded into the first bit of the shift register during the Low-to-Highor High-to-Low clock (C) transition and appears on the Q0 output. During subsequent clock transitions, whenCE is High and L and R are Low, the data shifts to the next highest bit position as new data is loaded into Q0.
Registers can be cascaded by connecting the last Q output of one stage to the SLI input of the next stage andconnecting clock, CE, L, and R inputs in parallel.
This register is asynchronously cleared, outputs Low, when power is applied. The power-on condition can besimulated by applying a High-level pulse on the PRLD global net.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 653
Chapter 3: About Design Elements
Logic TableInputs Outputs
R L CE SLI Dz:D0 C Q0 Qz:Q1
1 X X X X ↑ 0 0
1 X X X X ↓ 0 0
0 1 X X Dz:D0 ↑ D0 Dn
0 1 X X Dz:D0 ↓ D0 Dn
0 0 1 SLI X ↑ SLI qn-1
0 0 1 SLI X ↓ SLI qn-1
0 0 0 X X X No Change No Change
z = bitwidth -1
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries Guide654 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
SRD8RLEDMacro: 8-Bit Dual Edge Triggered Shift Register with Clock Enable and Synchronous Reset
Supported ArchitecturesThis design element is supported in the following architectures only:
CoolRunner™-II
IntroductionThis design element is a dual edge triggered shift register with shift-left (SLI) and shift-right (SRDI) serialinputs, parallel inputs (D), parallel outputs (Q), and four control inputs — clock enable (CE), load enable (L),shift left/right (LEFT), and synchronous reset (R). The register ignores clock transitions when CE and L areLow. The synchronous R, when High, overrides all other inputs during the Low-to-High or High-to-Lowclock (C) transition and resets the data outputs (Q) Low. When L is High and R is Low, the data on the Dinputs is loaded into the corresponding Q bits of the register. When CE is High and L and R are Low, data isshifted right or left, depending on the state of the LEFT input. If LEFT is High, data on SLI is loaded into Q0during the Low-to-High or High-to-Low clock transition and shifted left (to Q1, Q2, etc.) during subsequentclock transitions. If LEFT is Low, data on the SRDI is loaded into the last Q output during the Low-to-High orHigh-to-Low clock transition and shifted right during subsequent clock transitions. The logic table indicatesthe state of the Q outputs under all input conditions.
This register is asynchronously cleared, outputs Low, when power is applied. The power-on condition can besimulated by applying a High-level pulse on the PRLD global net.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 655
Chapter 3: About Design Elements
Logic TableInputs Outputs
R L CE LEFT SLI SRDI D7 : D0 C Q0 Q7 Q6 : Q1
1 X X X X X X ↑ 0 0 0
1 X X X X X X ↓ 0 0 0
0 1 X X X X D7 : D0 ↑ D0 D7 Dn
0 1 X X X X D7 : D0 ↓ D0 D7 Dn
0 0 0 X X X X X NoChange
NoChange
NoChange
0 0 1 1 SLI X X ↑ SLI q6 qn-1
0 0 1 1 SLI X X ↓ SLI q6 qn-1
0 0 1 0 X SRDI X ↑ q1 SRDI qn+1
0 0 1 0 X SRDI X ↓ q1 SRDI qn+1
qn-1 or qn+1 = state of referenced output one setup time prior to active clock transition
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries Guide656 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
VCCPrimitive: VCC-Connection Signal Tag
Supported ArchitecturesThis design element is supported in the following architectures only:
• XC9500
• CoolRunner™ XPLA3
• CoolRunner-II
IntroductionThis design element serves as a signal tag, or parameter, that forces a net or input function to a logic High level.A net tied to this element cannot have any other source.
When the placement and routing software encounters a net or input function tied to this element, it removes anylogic that is disabled by the Vcc signal, which is only implemented when the disabled logic cannot be removed.
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 657
Chapter 3: About Design Elements
XNOR2Primitive: 2-Input XNOR Gate with Non-Inverted Inputs
Supported ArchitecturesThis design element is supported in the following architectures only:
• XC9500
• CoolRunner™ XPLA3
• CoolRunner-II
IntroductionXNOR functions of up to nine inputs are available. All inputs are non-inverting. Because each input uses a CLBresource, replace functions with unused inputs with functions having the necessary number of inputs.
Logic TableInput Output
I0 ... Iz O
Odd number of 1 0
Even number of 1 1
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries Guide658 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
XNOR3Primitive: 3-Input XNOR Gate with Non-Inverted Inputs
Supported ArchitecturesThis design element is supported in the following architectures only:
• XC9500
• CoolRunner™ XPLA3
• CoolRunner-II
IntroductionXNOR functions of up to nine inputs are available. All inputs are non-inverting. Because each input uses a CLBresource, replace functions with unused inputs with functions having the necessary number of inputs.
Logic TableInput Output
I0 ... Iz O
Odd number of 1 0
Even number of 1 1
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 659
Chapter 3: About Design Elements
XNOR4Primitive: 4-Input XNOR Gate with Non-Inverted Inputs
Supported ArchitecturesThis design element is supported in the following architectures only:
• XC9500
• CoolRunner™ XPLA3
• CoolRunner-II
IntroductionXNOR functions of up to nine inputs are available. All inputs are non-inverting. Because each input uses a CLBresource, replace functions with unused inputs with functions having the necessary number of inputs.
Logic TableInput Output
I0 ... Iz O
Odd number of 1 0
Even number of 1 1
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries Guide660 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
XNOR5Primitive: 5-Input XNOR Gate with Non-Inverted Inputs
Supported ArchitecturesThis design element is supported in the following architectures only:
• XC9500
• CoolRunner™ XPLA3
• CoolRunner-II
IntroductionXNOR functions of up to nine inputs are available. All inputs are non-inverting. Because each input uses a CLBresource, replace functions with unused inputs with functions having the necessary number of inputs.
Logic TableInput Output
I0 ... Iz O
Odd number of 1 0
Even number of 1 1
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 661
Chapter 3: About Design Elements
XNOR6Macro: 6-Input XNOR Gate with Non-Inverted Inputs
Supported ArchitecturesThis design element is supported in the following architectures only:
• XC9500
• CoolRunner™ XPLA3
• CoolRunner-II
IntroductionXNOR functions of up to nine inputs are available. All inputs are non-inverting. Because each input uses a CLBresource, replace functions with unused inputs with functions having the necessary number of inputs.
Logic TableInput Output
I0 ... Iz O
Odd number of 1 0
Even number of 1 1
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries Guide662 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
XNOR7Macro: 7-Input XNOR Gate with Non-Inverted Inputs
Supported ArchitecturesThis design element is supported in the following architectures only:
• XC9500
• CoolRunner™ XPLA3
• CoolRunner-II
IntroductionXNOR functions of up to nine inputs are available. All inputs are non-inverting. Because each input uses a CLBresource, replace functions with unused inputs with functions having the necessary number of inputs.
Logic TableInput Output
I0 ... Iz O
Odd number of 1 0
Even number of 1 1
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 663
Chapter 3: About Design Elements
XNOR8Macro: 8-Input XNOR Gate with Non-Inverted Inputs
Supported ArchitecturesThis design element is supported in the following architectures only:
• XC9500
• CoolRunner™ XPLA3
• CoolRunner-II
IntroductionXNOR functions of up to nine inputs are available. All inputs are non-inverting. Because each input uses a CLBresource, replace functions with unused inputs with functions having the necessary number of inputs.
Logic TableInput Output
I0 ... Iz O
Odd number of 1 0
Even number of 1 1
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries Guide664 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
XNOR9Macro: 9-Input XNOR Gate with Non-Inverted Inputs
Supported ArchitecturesThis design element is supported in the following architectures only:
• XC9500
• CoolRunner™ XPLA3
• CoolRunner-II
IntroductionXNOR functions of up to nine inputs are available. All inputs are non-inverting. Because each input uses a CLBresource, replace functions with unused inputs with functions having the necessary number of inputs.
Logic TableInput Output
I0 ... Iz O
Odd number of 1 0
Even number of 1 1
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 665
Chapter 3: About Design Elements
XOR2Primitive: 2-Input XOR Gate with Non-Inverted Inputs
Supported ArchitecturesThis design element is supported in the following architectures only:
• XC9500
• CoolRunner™ XPLA3
• CoolRunner-II
IntroductionXOR functions of up to nine inputs are available. All inputs are non-inverting. Because each input uses a CLBresource, replace functions with unused inputs with functions having the necessary number of inputs.
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries Guide666 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
XOR3Primitive: 3-Input XOR Gate with Non-Inverted Inputs
Supported ArchitecturesThis design element is supported in the following architectures only:
• XC9500
• CoolRunner™ XPLA3
• CoolRunner-II
IntroductionXOR functions of up to nine inputs are available. All inputs are non-inverting. Because each input uses a CLBresource, replace functions with unused inputs with functions having the necessary number of inputs.
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 667
Chapter 3: About Design Elements
XOR4Primitive: 4-Input XOR Gate with Non-Inverted Inputs
Supported ArchitecturesThis design element is supported in the following architectures only:
• XC9500
• CoolRunner™ XPLA3
• CoolRunner-II
IntroductionXOR functions of up to nine inputs are available. All inputs are non-inverting. Because each input uses a CLBresource, replace functions with unused inputs with functions having the necessary number of inputs.
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries Guide668 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
XOR5Primitive: 5-Input XOR Gate with Non-Inverted Inputs
Supported ArchitecturesThis design element is supported in the following architectures only:
• XC9500
• CoolRunner™ XPLA3
• CoolRunner-II
IntroductionXOR functions of up to nine inputs are available. All inputs are non-inverting. Because each input uses a CLBresource, replace functions with unused inputs with functions having the necessary number of inputs.
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 669
Chapter 3: About Design Elements
XOR6Macro: 6-Input XOR Gate with Non-Inverted Inputs
Supported ArchitecturesThis design element is supported in the following architectures only:
• XC9500
• CoolRunner™ XPLA3
• CoolRunner-II
IntroductionXOR functions of up to nine inputs are available. All inputs are non-inverting. Because each input uses a CLBresource, replace functions with unused inputs with functions having the necessary number of inputs.
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries Guide670 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
XOR7Macro: 7-Input XOR Gate with Non-Inverted Inputs
Supported ArchitecturesThis design element is supported in the following architectures only:
• XC9500
• CoolRunner™ XPLA3
• CoolRunner-II
IntroductionXOR functions of up to nine inputs are available. All inputs are non-inverting. Because each input uses a CLBresource, replace functions with unused inputs with functions having the necessary number of inputs.
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 671
Chapter 3: About Design Elements
XOR8Macro: 8-Input XOR Gate with Non-Inverted Inputs
Supported ArchitecturesThis design element is supported in the following architectures only:
• XC9500
• CoolRunner™ XPLA3
• CoolRunner-II
IntroductionXOR functions of up to nine inputs are available. All inputs are non-inverting. Because each input uses a CLBresource, replace functions with unused inputs with functions having the necessary number of inputs.
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries Guide672 www.xilinx.com UG606 (v 11.3) September 16, 2009
Chapter 3: About Design Elements
XOR9Macro: 9-Input XOR Gate with Non-Inverted Inputs
Supported ArchitecturesThis design element is supported in the following architectures only:
• XC9500
• CoolRunner™ XPLA3
• CoolRunner-II
IntroductionXOR functions of up to nine inputs are available. All inputs are non-inverting. Because each input uses a CLBresource, replace functions with unused inputs with functions having the necessary number of inputs.
Design Entry MethodThis design element is only for use in schematics.
For More Information• See the appropriate CPLD User Guide.
• See the appropriate CPLD Data Sheets.
CPLD Libraries GuideUG606 (v 11.3) September 16, 2009 www.xilinx.com 673