Get email delivery of the Cadence blog featured here
A while back I visited a customer I see on a fairly regular basis. As soon as I entered the building, my primary contact asked if I'd stop off to talk with a colleague of his who had an Encounter problem. It was a bad one -- he was dead in the water and he couldn't get past the issue.
It's fairly unusual to look at a problem as an application engineer, and make quick suggestions that resolve problems. Especially lately, it seems. Invariably, the problems I see are complicated multi-variable things that take a lot of time and effort to pinpoint. But this one was different. It took me less than a minute to diagnose this problem and resolve it with the user. This scenario got me thinking that sharing these little tidbits would be an interesting addition to the blog. Challenges like this become a "puzzle" of sorts; I share some symptoms and clues, and you can take a crack at it and learn a little bit about how Encounter works along the way.
So here's the first puzzler:
The designer I visited was attempting to perform floorplanning operations in the tool. He inherited a database from another designer and needed to refine the solution to derive better fence locations and sizes. However, there was one big problem -- he couldn't see any fences in the design! Here is what the designer saw when he looked at the floorplan in Encounter:
The following is what he expected to see (5 fences):
The strange thing was that when the original designer was working on the database he could see the fences. We checked to make sure Guides/Regions/Fences/Modules were all visible and selected -- they were. We found one simple setting that, when changed, made the fences visible.
Do you think you know what's going on here? And why could one designer see the fences while the other could not? If you have an idea, leave a comment below.
Check back on Friday for the answer. Or better yet subscribe to the Digital Implementation blogs to get new content delivered to your inbox or favorite feed reader.
@Kari that's a very good point you raise. That can indeed happen as well- thanks for sharing!
I actually had a different answer. My answer assumes that these fences are a couple of layers down in the hierarchy, in which case they would not show up until you press the "hierarchy down" button the appropriate number of times. Of course, the first designer would have had to do the same thing - I wasn't sure if the first designer saw the fences immediately on loading the design, or just was able to see them at some point during his session. I just wanted to mention this, because it has also been a "where did my fences go" moment for folks before.
Man you're good. I'll have to kick up the degree of difficulty a notch for puzzler #2. I'll post a little further discussion around this soon but you nailed it.
Thanks for participating!
Well, assuming no explicit sourcing of local scripts (enc.pref.tcl) and no command-line typing of this setPreference setting, I'm going to guess that the original engineer had the following line in their ~/enc.tcl file:
setPreference MinFPModuleSize 0
Jason- you're spot on with the Min. Floorplan Module Size setting. For extra credit, what was it that one designer could see them yet when the other looked at the same database they could not see them?
Well, there's the obvious questions:
a) Are they in "floorplan view"?
b) Are the fences empty (you have to tell EDI to keep empty modules by setting the "Min. Floorplan Module Size" entry setting in the preferences)?
If not that, I don't know what it could be.