"John_H" wrote:

> Did I miss something and all your macros broke when you included only one
> RPM_GRID macro?

I think they did. I say "I think" because this was several layers back (and
days) in a troubleshooting session and I don't remember. I'm reasonably
certain that this is what happened:

1- Existing macro with regular grid consisting of several RPMs instantiated
at the macro's top level.
2- The macro was built with the lower-left component at X0Y0 (SRL)
3- Had problems with multipliers
4- Decided to use RPM_GRID for the multiplier
5- The macro broke (wouldn't implement)
6- Converted all sub-macros to RPM_GRID
7- Had other problems
8- Went back to a non RPM_GRID implementation and used timing attributes to
pull the multiplier into the right location.
9- Moved on

I have to say that Xilinx has been very supportive. We are looking into a
number of the things I've run into over the last couple of weeks. While no
vendor can and will offer perfection, the difference might very well be in
the way the user base is supported.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Martin Euredjian

To send private email:
[email protected]
where
"0_0_0_0_" = "martineu"