Droplet
A droplet is a complete semiconductor design delivered as manufacturing-ready design data rather than as a physical silicon die. The term is primarily used to describe a finished system-on-chip (SoC) or chiplet design that customers can manufacture through their own production channels.
A droplet typically contains the final physical layout of the design, its intellectual property cores, interface circuitry and electrostatic-discharge protection. It is generally delivered as a Graphic Design System (GDS) file or an equivalent foundry-ready design database.
The term is not formally standardized across the semiconductor industry. Its meaning may consequently vary between vendors.
Concept
A droplet occupies an intermediate position between a conventional semiconductor IP core and a physical chiplet.
A conventional IP core provides a reusable functional block that must be integrated with other components to create a complete integrated circuit. A droplet extends this model by supplying the physical design of an entire chip, chiplet or subsystem that is substantially ready for fabrication.
Unlike a physical chiplet, the droplet itself is not manufactured silicon. The customer receives the design files and remains responsible for fabrication, packaging and, depending on the commercial arrangement, final manufacturing sign-off.
Contents
A semiconductor droplet may include:
- a complete SoC, chiplet or subsystem design;
- hardened analog and digital macros;
- integrated semiconductor IP cores;
- input/output and interface circuitry;
- electrostatic-discharge protection;
- power-management and monitoring functions;
- physical layout information;
- process-specific implementation data; and
- documentation required for integration and manufacturing.
The exact contents depend on the vendor, application and foundry process.
Comparison with other semiconductor deliverables
| Characteristic | IP core | Droplet | Chiplet |
|---|---|---|---|
| Delivered as | Design files | Complete manufacturing-ready design | Physical unpackaged die |
| Typical scope | Individual function or subsystem | Finished chip, chiplet or major subsystem | Manufactured functional component |
| Physical silicon supplied | No | No | Yes |
| Customer fabrication required | Yes | Yes | No |
| Integration work | Usually extensive | Reduced, but still required | Primarily package-level |
| Process dependency | Soft IP may be portable; hard IP is process-specific | Generally process-specific | Already fabricated |
| Typical commercial model | Licence and royalties | Design licence, manufacturing rights or custom agreement | Component purchase or supply agreement |
Difference from a chiplet
A chiplet is a physical semiconductor die designed for integration with other dies in a common package. It may be mounted on an organic substrate, silicon interposer or redistribution layer, or vertically stacked in a 3D configuration.
A droplet, by contrast, is the digital representation of a finished semiconductor design. It can potentially be manufactured as a standalone chip or as a chiplet, but no physical die is supplied as part of the droplet itself.
The distinction can be summarized as follows:
A chiplet is manufactured silicon; a droplet is a design that can be manufactured as silicon.
This approach allows customers with established foundry and packaging relationships to control their own manufacturing flow while acquiring a substantially complete design from an external provider.
Difference from a hard macro
A hard macro is a physical implementation of a specific semiconductor IP function, optimized for a particular manufacturing process. Examples include analog-to-digital converters, phase-locked loops, memory blocks and high-speed interface PHYs.
A droplet may contain several hard macros, but its scope is broader. It represents an entire chip, chiplet or self-contained subsystem rather than an individual functional block.
Some industry observers nevertheless use droplet more broadly for a hardened subsystem that cannot operate independently and must be surrounded by other functions. Under this interpretation, the boundary between a droplet and a large hard macro is not always clear.
Related Blogs
Featured Content
- Starscream: Reimagining LLM Sharding on AMD Instinct GPUs with GPU Partitioning
- JEDEC® Announces Creation of JC-14.8 Subcommittee on System Level Reliability Testing (SLRT); Invites Industry Participation
- UCIe Consortium Advances from Chiplet Connectivity to System-Level Integration with UCIe 4.0 Specification
- Netherlands and Taiwan Launch Four Joint Photonics R&D Projects
- ASRA and imec release joint architectural requirements for interoperable automotive chiplets
- Crealights’ Self-Developed Silicon Photonics Chip “Greyhound” Makes Its Appearance at CIIE, Showcasing a “Chinese Solution for the Token Economy”
- Tri-Stack-PIM: A Heterogeneous Multi-Die 3D-Integrated Processing-in-Memory Architecture for Efficient LLM Inference
- CU-3D: A Scalable Legality-Aware RTL-to-GDS Flow for 3D-IC Physical Design
- Staera Semiconductor Emerges from Stealth with US$4.6 Million to Build Light into the Chip and Break AI's Data Bottleneck
- The chip beneath the chips: Why silicon interposers matter more than ever
- Vertical Compute expands partnership with imec to accelerate commercial manufacturing of Vertically Integrated Memory (VIM)
- Imec advances Europe's silicon interposer technology capabilities through NanoIC pilot line, paving the way for open chiplet design
- When Every Chiplet Passes, Who Fixes the Package?
- Beyond Host-Side Control: HBM Controller Partitioning Across Host and HBM Base Dies
- The European Chip Ecosystem