1. Home
  2. Field-Programmable Gate Arrays
  3. MUXCY and XORCY local outputs (LO)

MUXCY and XORCY local outputs (LO)

I think I finally got a grip on the legal connections for the LO output on MUXFx primitive objects, but what are the legal connections for the LO outputs on MUXCY and XORCY primitive objects? Does Xilinx have a document somewhere discussing this? It seems mapper does not automatically swap the O to LO to improve timing. Why is that? It seems that XST and Synplify infer about 90% LO and 10% O. I need to know the rules to make my tool do that. Thanks for your time.

--
Prepend a 'b' to email me. Thanks.
Reply to
Brannon King
Loading thread data ...

I think the mapper doesn't strike much of a difference. I've been using the "O" only for my manually instantiated primitives without complaints from either Synplify or the Xilinx back end tools.

O
Reply to
John_H

ElectronDepot website is not affiliated with any of the manufacturers or service providers discussed here. All logos and trade names are the property of their respective owners.