DDR5 Rx Testing is a Whole New Ballgame – #28

Receiver testing (Rx) was never a concern for DDR design. Until now. The margin for error ran out, and now Rx testing is getting standardized. We sit down with Stephanie Rubalcava to explore the challenges of this new ground.

Receiver testing (Rx) was never a concern for DDR design. Until now. The margin for error ran out, and now Rx testing is getting standardized. We sit down with Stephanie Rubalcava to explore the challenges of this new ground.





This is the first time in the industry that high-accuracy, standardized receiver measurements need to be done

DDR is very different from traditional memory in terms of testing

Process of getting specs defined

What a DDR receiver test (DDR Rx Test) looks like

Even being just 100 mV off when testing can make a part appear to fail

The BERT sends out a signal to test the channel, but what’s really being tested is the DIMM and device’s ability to receive data under certain conditions

Receiver types across different devices? There’s a DQS data clock signal, and a data signal. There are also command and address lines in DDR.

For Rx testing, we’re calibrating the signal going into the receiver

JEDEC develops a lot of the testing standards

Two components of test standards: compliance and characterization. Compliance asks “do I meet the spec?” Characterization asks “how well does my system perform, and where is my fail point?”

Receiver test as whole is a challenge for engineers

They need new kinds of calibration, DDR fixtures, and tests.

DDR Transmitters (DDR Tx) are progressing with DDR5 as well as receivers. We do have the DDR Tx history testing all the way back to DDR1.

There are similar specifications for characteristics of DDR transmitters and DDR receivers.

DDR Transmitter testing is at “the ball of the part” and checks for signal characteristics.



How to Price Your Electronics Hardware Project – #14

Pricing a new hardware product in a global economy with regional pricing, psychological factors, and the challenges of pricing in white space. This week’s guest is Brig Asay. Hosted by Daniel Bogdanoff and Mike Hoffman, EEs Talk Tech is a twice-monthly electrical engineering podcast discussing tech trends and industry news from an electrical engineer’s perspective.

Daniel Bogdanoff and Mike Hoffman sit down with Brig Asay to talk about how to price a hardware project. Listen in as they discuss the complexities of pricing a new hardware product in a global economy.

Follow Brig Asay on Yelp @baasay.

Video Version (YouTube):

Audio Only:

0:00 Intro

How should you price hardware?


Tell us in the comments what you think our green screen should be!


Economics 101: Supply & Demand

This is how we generally set prices for hardware


Top down pricing takes into account your cost of manufacturing.

But if you price based on production costs, you’re going to fail in your pricing.

It’s all about what consumers are willing to pay.


Pharmaceutical companies are the example of bad pricing schemes. They justify high prices based on high R&D costs.

But the reality is that consumers don’t care about R&D costs. They care about how bad they need the product, and this will determine how much they are willing to pay.


Someone on EEVblog hacked a 3000T, reverse engineering it to make it a 1 GHz scope.



The newer the idea, the harder it is to price because there’s no real market value.

Talking to potential customers is a good way to start pricing in white space.


Marketing 101: Who are your customers?

Determining who you are trying to sell to and talking with them can help with pricing.

Competitor pricing is a good baseline, but then you often get into value-based pricing.


Spreadsheets are the killer of pricing. They compete with your gut feeling.

$10K per GHz of bandwidth is a standard in oscilloscope pricing, but it doesn’t always apply. When we came out with the Infiniium Z-Series, a 63 GHz scope, we knew the market couldn’t support a $630K price.


Price/volume curve = Supply and demand chart


Different regions have different pricing expectations.

Currency, cultural expectations, and import taxes all come into play when considering regional pricing.

Should a small company even worry about regional pricing?


You need to be willing to adjust pricing.

Dynamics of the market and the value of your product can change over time.

If you’re not selling anything, you need to adjust your price.

Priced too low and people may have the perception that you’re selling a low-quality product.


Pricing too low may also inadvertently shrink your market size.

Overly undercutting your competitor may hurt you in the long-run.


Does the psychological side to pricing always apply?

What’s the stigma around prices ending in a 9 or 8?


Stupid Questions with Mike:

What is your favorite price and why?

What is your favorite currency and why?


Tell us about your software or hardware project in the comments!