Get email delivery of the Cadence blog featured here
SoC-Encounter has automatic partition
pin assignment capabilites. The tool also allows us to provide guidance
on where partition pins should/should not be allowed to go. However, it
is sometimes useful for certain pins to be placed at certain coordinates,
layers, and/or order. When this level of control is needed, the Pin
Editor can help automate the task of moving pins to their desired
locations. This demo shows the basics of how to use the Pin Editor:
If the video fails to embed, please
TCL commands relevant to this video:
Question of the Day: Have you used the
Pin Editor? What do you like/dislike about it?
I am using it since 6.1 , Now with SOC 7.1 and 8.1 Its far far better than 6.1,
Bob you also need to mention that pineditor dumps editPin cmd for any pin spreading/placing action through pin editor. That really helps some times if one want to redo all actions he did through GUI.
Hi "spojer"! Thanks for your comment too! I think we're all in agreement that the Pin Editor has come a long way in terms of bugginess. It's pretty good these days! If others happen to see your note about "ptngUseLayerM1" I thought to mention a couple of things. First, you can sometimes find more information about globals like this via the "Design->Global Variables..." form. In this case, this variable is documented as follows: "Enable pin related commands to allow pins to be placed on layer M1". It's a little non-intuitive to have to go to this other form for something that might be commonly used- I've passed your feedback along to our developers and suggested that we might want to include a button that toggles this value on the Pin Editor form. Thanks for mentioning it!
I've been using the pin editor since release 4.2. It was really buggy at that time, especially when M1 pins had to be placed on non preferred direction.
Since 7.1 the pin editor works fine - when I do not forget 'set ptngUseLayerM1 1'.
Thanks for checking in! I tend to agree with that sentiment. It used to be a buggy on top of being complex conceptually. Now, once you get the hang of it, it seems pretty reliable and powerful. Let us know if you run across any problems with it or suggestions for improvement. It's always good to hear feedback from users like yourself.
PS I haven't forgotten about your timing budgeting issue! Just a little busy lately. :)
The pin editor had been an object of ire for me for a long time because I could see how powerful it could be were it not so full of bugs. It was actually dangerous to use because it's behaviour was so unpredictible - it would misplace pins without me realizing it or crash the tool altogher. I was happy to see that by version 7.1 the bugs seem to have been worked out and now works very nicely. It's now the powerful tool that I knew it could be!