If you do any kind of multi-gigabit SerDes design, you’ve probably come across the acronym, AMI - Algorithmic Modeling Interface. AMI is essential a fast behavioral model of multi-gigabit transmitters and receivers. Standard IBIS models are good for regular switching edges up to some surprisingly fast speeds, but when you start adding in things like pre-emphasis, and equalization on those edge, the old IBIS I-V tables just don’t cut it any more. So how do you account for those kinds of behaviors? There are options, but the most common today is SPICE, and not just any ol’ SPICE, it’s typically HSPICE encrypted models because that’s the easiest thing for an IC company to deliver. That means that you’re locked into one vendor for your signal integrity simulation - that’s generally not good for you and not good for the industry either.
So out of this need drove the creation of AMI. AMI was approved as part of the IBIS 5.0 modeling specification and was designed to characterize things like pre-emphasis, equalization, clock recovery, etc in a transceiver. Beyond just the characterization, the intent of AMI is to deliver fast time domain simulation results on a vendor independent platform (this is nothing new for IBIS - it’s been the standards mantra since its inception). There’s nothing worse than having to wait a half a day to get the results from one SPICE simulation and the hope is that AMI can fix that through behavioral modeling. Mentor has been an active part of this process with Arpad Muranyi, modeling guru and IBIS advocate, being the chair of the IBIS ATM (Advanced Technology Modeling) Task Group which created the AMI specification.
There is quite a bit of interest in AMI to say the least, but there’s probably a few things you should know if you’re looking into these models. As we work with silicon vendors, it’s becoming more clear that SPICE may still be a requirement with AMI. The thing with AMI models is that they expect an analog input waveform. Hopefully this can come from a traditional analog IBIS model, but that may not always be sufficient, especially if you have AC coupling in your channel. So now you’ve got SPICE back in the picture to create the analog behavior. So what does AMI buy you then? Well for one, if you’re doing SPICE simulations, most likely the majority of your simulation time is consumed by the receiver and modeling it’s equalization behavior (that’s a broad generalization but I’d say it’s typically true from the models I’ve seen). The AMI model can replace all that time intensive simulation in SPICE. It can also be used to model the clock recovery, something you’re not going to get out of your SPICE simulations either. Also, once the channel has been characterized with the analog waveform, you can now start to do some real number crunching. Instead of being limited to a few thousand bits of simulation time, you can quickly get millions of bits of data in a matter of minutes. So there is definite value, even if it isn’t exactly what you might have initially expected from this modeling standard.
The first availability of AMI support will be right around the corner in Mentor’s analysis tools- delivered first in HyperLynx SI. If you want to see the first incarnation of this, check out the following webinar that we’re delivering with Xilinx on Jan 28th -Multi-GHz Channel Analysis using HyperLynx and Xilinx’ IBIS-AMI Models. We’ll be covering the Xilinx Virtex 5 AMI models and showing some pretty cool outputs that you can get from this design kit in HyperLynx, including 3D eye density plots.