Skip to content

Cryptographic IP cores and programmable crypto hardware

A cryptographic IP core is a licensable hardware design implementing a cryptographic function, integrated into a customer's own silicon. Programmable cores cost area and power relative to fixed ones, and buy the ability to change what the silicon computes after it ships.

What is licensed

A design, in a form the customer's process can implement, plus the verification collateral and integration guidance that make it usable. Delivered as synthesisable RTL or as a hardened block, depending on how much of the physical implementation the vendor performs.

What is not delivered is a certificate. An evaluation covers a specific implementation, and the customer's silicon is a different device needing its own evidence — the same point that applies to licensing an entropy source.

Fixed against programmable cores

A fixed core implements one function. It is small, fast and efficient, and it does exactly what it was taped out to do.

A programmable core implements a class of functions, with the specific behaviour set by configuration or microcode. It costs area and switching energy, and it can be updated to a revised parameter set or a different algorithm without new silicon.

What agility costs in silicon

Real area and real power. Configurability means multiplexers, wider datapaths and control logic that a fixed implementation simply does not have. On a constrained device that overhead can be the difference between fitting and not.

The honest framing is that agility is a feature with a price, priced in area and watts, bought against the probability of change. During a standards transition that probability is high enough that the price is usually worth paying for anything long-lived.

Integration realities

  • Verification is the customer's problem in their context, whatever the vendor delivers.
  • Physical implementation — timing closure, power, placement — is where schedule is actually lost.
  • Test access matters, particularly for anything with an entropy source, which must be observable before conditioning or it cannot be characterised.
  • Certification is the customer's, and the transferable part is methodology rather than the certificate.

Where this connects

A cryptographic core and an entropy core in the same design, from the same supplier, with one integration effort and one evaluation boundary, is the argument the chiplet makes in packaged form.