we hereby provide an add-on to our CDNLive-EMEA 2019 Techtorial V talk.
The package contains three executable appCell examples:
We also provide demo layouts, the appCell source codes and a small SKILL script that demonstrates the integration into Virtuoso.
The attached PDF file describes the appCell examples as well as the steps to run the examples and to open the source code files.
Please consider to share your thoughts and examples as well in the PCell Designer Community Forum. We hope you find the provided appCellDemoLib examples helpful and inspiring.
I am still not sure about what exactly is appCell and how it is different from Classic pcell that we design?
Can we use appCell as an alternative for Pcell?
Also if anyone has any documentation on Cadence Pcell Designer Tool please Share, It will be Helpful
Thank & Regards,
The point of an appCell is that it operates on an existing layout (not just a layout, but most appCells so far have been layout-focused), whereas a PCell creates a layout variant from scratch based on a set of parameters. So put another way, when you instantiate a PCell, you give it a set of parameters and it creates (in memory) a new subMaster cellView for that variant (that combination of parameters), and then populates that subMaster with geometries, instances and connectivity based on the PCell code. With an appCell, you provide a set of parameters and a cellView to work on, and it then has access to the geometries, instances and connectivity that is already present and can modify the content or add additional content based on that.
With PCell Designer, you can then create methods for your appCell using the same user interface normally used for creating PCells, but with a different purpose. You can use the same geometric queries and high level commands to construct utilities. There's then a form you can use to publish the method as an appCell and choose what the form (if needed) looks like for your appCell.
The resulting appCell is then published into a library (so you don't need to ship SKILL code around) and there's a simple function call to execute the appCell method from your shipped library that can then be assigned to a bind key, menu or toolbar.
So I wouldn't say it's an alternative to a PCell - it's using PCell technology for creating layout (or schematic/symbol) utilities.
As for documentation, we have some conventional Cadence documentation that is currently under construction (it will then end up on support.cadence.com). In the meantime we do have two rapid adoption kits on support.cadence.com and we usually provide a PDF with some documentation/training to existing customers. I'm not sure what organisation you're from - but if you send me a friend request with your contact details I can ensure that we work with you to provide that (note, this is not an invitation for everyone to send me forum friend requests - I normally ignore those as it's better to ask questions in the forums or log support requests; I don't have the capacity to respond to direct questions from the whole world!)
Thank You Very much for your quick response and detailed explanation on working and usage of appCell. This will surely help me and my team in exploring it and implementing it in our work.