MunEDA Analog Productivity Tools within InPlay Design Environment
Russell Mohn
Russell is the Co-Founder and Vice President of RF Design at InPlay Inc. and his team has been using WiCkeD from MunEDA for several years. We thought the rest of the world would like to learn about his experiences.
What does InPlay do?
InPlay is a fabless semiconductor company. We design and develop chips that enable wireless connectivity in applications that require low-latency, many devices, and low power … all at the same time. We are also enabling a new generation of active RFID smart sensors and beacons with our NanoBeacon product line. It doesn’t require firmware. The BOM is tiny. And power consumption is very low, so it can be powered by unique batteries and energy harvesting technologies.
What type of circuits do you design?
We design and develop all the necessary circuits for a radio transceiver. Some examples are low noise amplifiers, mixers, programmable amplifiers, analog to digital converters, digital to analog converters, low-drop out regulators, phase locked loops, power amplifiers. We also design the power management circuit necessary for the chip, which includes DCDC converters, really low power oscillators, references, and regulators.
Which MunEDA tools do you use?
We use WiCkeD and SPT.
How do you apply the MunEDA tools to your day-to-day job?
We’ve done some porting work over the past couple years. It was necessary with the foundry wafer shortage, especially for startup companies like us. Using SPT to get the schematics all ported over has been really helpful.
We also use WiCkeD for both optimization and for design centering over process/voltage/temperature variation. If the circuit is small enough, an opamp for example, after choosing the right topology, the optimizer can do the work of a designer to get the needed performance, all while keeping the design centered over PVT.
We’ve also used it for intractable RF matching/filtering tasks and for worst case analysis on startup issues for metastable circuits.
What value do you see from the MunEDA tools?
I see the MunEDA tools as basically another designer on my team. This is huge since we’re a small team, so the impact has been significant.
How about the learning curve?
MunEDA’s support is really great; they care about their customers, no matter how small. The learning curve is not too bad after some built-in tutorials. I see value from the tools every time I use them, from the first time, until now.
What advice would you give a circuit designer considering the MunEDA tools?
I would advise that they keep an open mind, and really look at the resulting data. I think many designers would be happy by the amount of time they can save, and the insight they can gain into the trade-offs in their designs.