Breakout Boards: How to Choose, Connect and Validate One

Although two breakout boards may use the same chip, they are typically designed to work under different power, logic, wiring, and configuration conditions. This is because of the individual PCB around the device, i.e., regulators, level shifters, pull-ups, filters, protection, jumpers, connectors, and routing all affect what the host can do.

A breakout board connects a difficult device to pads, headers, or connectors that allow access to the device’s connections. This means that the exact breakout board and its revision must be used to ensure correct operation, rather than relying on the chip’s name or a similar-looking photograph of the board. The same care must be taken when transferring the prototype to a custom PCB or PCBA.

What Is a Breakout Board?

A breakout board is a PCBA or small PCB designed to assist in connecting, probing, and prototyping components that would otherwise be difficult to connect, probe, or prototype due to their configuration. The terminology of breakout boards defines the function of the board rather than a defined electrical class; two products with the same category label may carry different circuitry and limits.

The term breakout refers to routing connections that are difficult to reach to pads, headers, test points, terminals, or other accessible connectors. By doing this, you can turn a SMD into something easy to wire on a breadboard, use bench equipment to measure the device, or connect to a development platform without designing the final PCB first.

However, the use of a breakout board does not alter the requirements of the device mounted to it. It does, however, require the full schematic and documentation to define the complete interface details in cases where active or passive support parts are used; the main IC datasheet alone does not define the board-level interface required.

Common Types of Breakout Boards

A useful way to classify breakout boards is based on what is exposed and what board-level circuitry is added, as well as what engineering tasks are being simplified by the breakout board. Using a classification system like this makes sure that a passive SMD adapter is not treated as an electrical equivalent to an active sensor module.

Sensor Breakout Boards

Sensor breakout boards expose a range of sensors including temperature, humidity, pressure, acceleration, angular rate, magnetic field, light, gas, distance, vibration, RFID, and current via different connection methods, typically analog outputs, I2C, SPI, UART, or interrupt and address-select pins.

What determines if two sensor breakout boards are compatible is not the sensing element, but what other circuitry has been added around that sensing element. The surrounding circuitry may include a regulator, logic translator, bus pull-ups, filtering, calibration memory, an ADC, or an amplifier, or it may be only copper fanout traces.

If several sensor breakout boards using I2C are connected on the same bus, the overall amount of combined pull-up circuitry can cause the effective pull-up resistance to fall too low, which may create intermittent read errors that appear to be a malfunctioning sensor when, in fact, they are caused by circuit loading.

For environmental sensors, make sure to consider whether nearby heat-generating components or the PCB itself affect the sensor output readings. Just because a sensor breakout board exists, it does not imply that the sensor’s measurement accuracy, isolation, or safety characteristics are suitable for gas or electrical current measurements or for anything that is located close to a mains power source.

IC Package Adapter Boards

An adapter for a package is designed to accommodate assemblies that utilize various package types with fine-pitch or underside terminals, including SOIC, SOP, SSOP, MSOP, TSSOP, SOT, QFP, TQFP, LQFP, QFN, DFN, LGA, and BGA. To achieve this, an adapter provides larger pads or through-hole mounting headers so that assemblies can be easily soldered, probed, or placed on a standard breadboard.

The difficulty in engineering for an adapter scales with the complexity of the package itself. For instance, designing a TQFP adapter can be as simple as determining a footprint and routing traces to a fanout pattern. In contrast, an adapter using QFN and DFN packages requires appropriate handling of the exposed pads for thermal management, and thermal vias may also be required for proper heat dissipation. BGA adapters need to have escape routing implemented, and it is usually implemented on multiple layers using controlled vias and a connector strategy dissimilar to a traditional 2.54 mm breadboard header.

Additionally, matching the package family name is inadequate; you must verify that the body’s dimensions, the quantity of pins in the package, the pin pitch, the exposed-pad geometry, and the pin-one orientation are correct, and that high-speed or sensitive signals remain within specification after passing through the adapter and its connectors.

Generic SMT Carrier Boards

A universal SMT carrier is a reusable pad pattern that can accommodate many different types of components by using interchangeable sockets and multi-footprint patterns. This versatility allows for evaluation of new designs, soldering practice, or reaching devices that have no dedicated breakout.

Carriers that fit multiple component types cannot ensure that a carrier will have all of the decoupling, thermal path, reference planes, bias network, or signal conditioning that an individual component would need. Even if a component fits the pads of a carrier, if the component’s datasheet specifies that it must have an external decoupling capacitor or a bias resistor, it may not function at all. Therefore, the only assurance that a carrier provides is the mechanical and electrical fan-out, not a fully functioning circuit.

Custom Breakout Boards

Custom breakout boards are designed for a specific component or test requirement and not for an off-the-shelf footprint. These boards provide a way to expose non-visible pins, create dedicated test points, reproduce an original circuit, or connect a new device to existing laboratory apparatus.

Custom breakout boards can involve higher cost and longer turnaround time than generic adapters, but they are worth their cost if the measurements enabled by the custom breakout board cannot be obtained by any other method. For example, a custom breakout board preserves critical trace lengths, grounding, thermal copper, differential pairs, and fixture access that are not guaranteed by generic carriers. Custom breakout boards can also be useful in situations where using a generic breakout can hinder measurement of the performance of an assembly. An example would be crosstalk masked by a shared ground plane or a timing violation masked by breadboard wiring that only appears at full clock speed.

Microcontroller Breakout Boards

“Microcontroller Breakout Boards” includes two types of products with similar names: those that provide connections to a microcontroller or processor, and those that connect to GPIO headers of existing functional platforms; one is used for providing access to a bare computing device, while the other provides multiple options for interfacing with already working devices.

A microcontroller breakout board typically has added GPIO pins, power-domain pins, reset and boot mode pins, clock pins, programming interfaces, LEDs, buttons, crystals, regulators, and USB circuitry; at this point, it becomes very similar to a development board.

When comparing two different boards, check to ensure that boot configurations, regulator capabilities, oscillator sources, USB implementations, debug connectors, flash memory, and host-voltage assumptions are all comparable, as boards that share the same microcontroller may start up differently and expose pins differently.

RF Communication Breakout Boards

“RF Communication Breakout Boards” allow for a simplified evaluation of various types of communication devices, such as Bluetooth, Wi-Fi, Zigbee, NFC, GPS/GNSS, Cellular Modems, Ethernet, and dedicated RF Transceivers. These products either provide a complete module, a standalone radio IC, a connector for an antenna, or a way of controlling the device via a Serial interface.

The power requirements of RF devices are almost as critical as their digital pinout; be aware of voltage regulation limits, peak current draw during transmit, antenna type and distance from other components, impedance matching, ground reference point, and whether the board contains a pre-certified module or a bare radio IC that requires its own certification path.

If a wireless link works well on a test bench, it will not necessarily work in an enclosed environment unless the effects of housing, shielding, and component placement are considered. Connector placement, cable losses, ground configuration, and emissions characteristics may all vary when the breakout board transitions from the bench to a custom PCB.

Digital Interface Converter Boards

Active protocol breakout boards translate between communication interfaces including USB-to-UART, TTL-to-RS-232, TTL-to-RS-485, CAN transceivers, Level Translation ICs, Bridge ICs, and Parallel-to-Serial Converters. In addition, several products marketed as communication modules will also support protocol conversion, since the key purpose for many of these devices is to convert one protocol to another rather than permit wireless communications.

Matching the labeled connectors at both ends of your respective wires or cables is not a means of selecting an appropriate protocol converter; technical selection requires checking the actual transceivers used, the logic levels supported, the type of termination and biasing provided, the half/full duplex capability, the amount of isolation provided, the USB voltage domain for the specified device, and the maximum data transfer rate supported by the USB-to-UART bridge itself. A bridge may still produce corrupted data below its nominal maximum rate if required flow control or buffering is not supported.

When dealing with differential or high-speed interfaces, the actual physical arrangement of fanout becomes part of the electrical circuit; the quality of the connectors used, stub lengths, and reference plane continuity will all impact the quality of the signal as it propagates through the electrical circuit, even if the protocol name on the container is accurate.

Connector Breakout Boards

Connector breakout boards have been created for a variety of high-density and unusual connector types, such as USB, USB-C, HDMI, FFC/FPC, JST, Board-to-Board, Edge Connectors, and Miniature Coaxial Connectors; they allow the end user to gain access to each connector pin or terminal, perform continuity checks, and support harness development. If you want to check if your wires are connected correctly with a passive breakout board, you will see continuity on each pin on your multimeter. A USB, HDMI, high-speed serial, RF, or differential pair connection may degrade as the connection length increases due to uncontrolled impedance and poor return paths.

Selecting passive breakout boards has a variety of considerations including how many contacts there are, the pitch between contacts, the direction of the mating end of the connector, whether the connector is keyed to fit correctly only one way, how the shield is connected, the current ratings of the contacts, and how to relieve the strain on the cable.

For boards using FFC/FPC, it is worth confirming whether the connector is top- or bottom-contact, as improperly inserting a cable into a connector will not connect a signal and yet may look like it is properly seated.

Power Breakout Boards

Power breakout boards are all forms of linear regulators, DC-DC buck regulators, load switches, power distribution boards, battery chargers and monitors, and boards dividing a single input into multiple protected or regulated outputs for conversion, distribution, measurement, or protection.

The true specifications of a board must meet what a system requires, not what the product listing states as nominal voltage; check the input/output ranges, continuous/peak current flows, dropout/duty cycle limits, thermal derating, and reverse-polarity handling, as a board that carries a rating of “5 A” might only sustain that current due to the airflow supplied by a bench setup.

Battery boards have several specifications you will want to check, such as cell chemistry, number of series cells, charging profile, protection levels, and equalizing behavior; having a prototype power module may help to make evaluations easier, but the prototype’s thermal path and safety implementations still need to be reviewed before using the design for production.

Signal Conditioning Breakout Boards

Signal-conditioning breakout boards are used to prepare an analog/mixed-signal input for use with either a controller or an instrument. Examples of conditioning would be amplifying, filtering, isolating, level translating, buffering, sensing currents, exciting bridge circuits, interfacing with thermocouples, as well as using ADCs and DACs for analog-to-digital and digital-to-analog conversion.

While signal conditioning is a more extensive process than a simple pin adapter, the actual performance of a board will depend on its component values in addition to those of a sensor, which together determine its gain, bandwidth, offset, noise, common-mode voltage range, and input impedance. An example would be if a signal reads clean at room temperature, it may drift once the board’s reference voltage or filter network reacts differently to temperature changes.

It is best practice to document the gain settings, filter networks, reference voltage, and sample rate settings used for doing characterization; failing to do this may cause the actual performance seen during characterization to be attributed incorrectly to the sensor or IC.

Display Breakout Boards

Breakout boards for displays can reduce the complexity of connecting OLED, LCD, TFT, LED-driver, and touch-controller devices with small-pitch connectors, multiple power supply voltages, and the need to provide a connector, backlight driver, charge pump, voltage regulator, or a communication protocol bridge to the display panel.

Displays with a common diagonal dimension and connector pitch may not be interchangeable with each other unless their controller IC, pin order, timing signals, and power sequence are identical. Replacing one display with another can result in a blank screen even if all physical connections to each other are identical.

Before any display replacement is assumed to be a “compatible” replacement, verify the logic voltage of the display separately from the panel or backlight voltage, confirm the maximum current that the device will require, check for reset timing, determine which interface mode is being used, verify that the display is using the correct controller IC, and verify that the initialization sequence is appropriate for the display.

Storage Breakout Boards

Breakout boards for memory and other forms of storage expose the pinout for EEPROM, flash, FRAM, SRAM, and SD or microSD sockets. These breakout boards are typically used to test methods of data logging, storing configuration information, providing boot media, and performing firmware updates before the final version of the PCB has been established.

Storage type may determine reliability, but interface details such as supply and logic voltage, interface mode, chip-select behavior, write-protect pins, pull-ups, and card-detect signals play a larger role. For example, a card that works properly in the 1 MHz SPI mode may exhibit write errors at 8 MHz due to the breadboard wiring becoming the limiting factor. Before concluding that a storage device is defective, if errors occur only at higher clock rates, examine protocol, power integrity, and interconnect effects separately.

Audio Breakout Boards

Audio Breakout Boards permit evaluation of the audio path before final layout of the analog, digital, and power sections. They include microphones, preamps, codecs, ADCs, DACs, I2S interfaces, headphone drivers and amplifiers.

The noise found on many audio breakout boards is not caused by the IC itself. Signals can pick up noise from USB power lines or breadboard ground-return impedance if analog line lengths are very long, or the use of wires on a breadboard can introduce audible hiss or hum. The noise may stop after soldering the same circuit onto an appropriate PCB with a proper ground plane.

Before trying to troubleshoot a noise problem with the codec/DACs, check to see if the breakout has separate analog and digital power supplies, microphone biasing or coupling, gain, sample rate, or whether the breakout has its own amplifier or just converts the signal.

Module Carrier Boards

Module carriers utilize castellated pads, board-to-board connectors, or mezzanine connectors to receive a module (e.g., wireless modules, computing modules, GNSS receivers, and sensor modules) instead of separately mounting the device without a PCB.

The carrier’s primary role is to provide the correct integration conditions as defined by the vendor. For example, the carrier must provide the same power-sequencing, antenna keep-out, and boot-strapping conditions the vendor had on their own board to ensure the module operates correctly. Powering a module up in the wrong order will result in a boot failure that looks like a broken module.

When converting from a carrier board to a custom control board, maintain the connector pin-out, keep-out regions, and vendor-defined power sequencing and integration conditions; these considerations are more significant than the dimensions of the carrier itself.

Application-Specific Breakout Boards

Application-Specific Breakout Boards combine several devices to accomplish a single task (e.g., motor control, battery monitoring, data logging, motion tracking, GPS positioning, and actuator drive). Application-Specific Breakouts are between a single device breakout and a full development board.

Application-Specific Breakouts can offer the fastest proof of concept for a new idea but may contain hidden dependencies. For instance, a motor control breakout may already be supported by its gate driver, current-sensing circuit, and any required flyback paths and thermal-protective devices needed to make the motor-control demo functional. When the motor-control demo is collapsed onto the final board, it is easy to forget to incorporate those items in the final product.

Use the task-level schematic, not the demo result, as the source of truth: track which protection, sensing, and biasing devices made the prototype functional, and determine which will be included in the final product.

What Changes Between a Chip and Its Breakout Board?

PCB breakouts have a few common electrical configurations that can apply to all breakouts:

1. Passive adapter: The primary function of a passive adapter PCB breakout is to connect a device package, connector, or IC with a very small pitch to larger pad or header locations without intentionally changing the electrical interface of the main device.
2. Regulated or level-shifted module: A PCB breakout designed to allow a host to communicate with a device through a different logic level or to provide different documented power conditions is referred to as a level-shifted or regulated PCB breakout module.
3. Interface-specific module: These types of PCB breakout modules adapt the signals from a device to those used by a specific system or sub-system within your application. Examples include connectors, transceivers, filters, protection circuits, etc.

The example of Adafruit’s SMT Breakout PCB as a passive adapter illustrates how a passive PCB can support an SMD (SOIC, MSOP, TSSOP) package by using connection pads for the SMD package but without adding a voltage regulator or logic converter to the PCB.

In some cases, an integrated sensor or interface module may contain several components (i.e., active/passive) located around the same PCB, and the components should appear on the PCB schematic and may also be documented separately in component data sheets. Therefore, you must refer to the PCB schematic and component data sheets to determine the functions and locations of the components.

Same Chip, Different Board: The BME280 Compatibility Test

The same chip on different boards and revision numbers can have different compatibility requirements. It is essential to have the correct revision for compatibility testing; for example, compatibility with a BME280 board will be determined based on the exact BME280 board and revision, not based on the sensor name, because Bosch specifies the sensor while Adafruit and SparkFun document different board-level specifications for their BME280 breakouts.

In many cases, practical risks occur when wiring diagrams are copied from one board to another instead of reading the documentation of the original boards. For example, you can apply 5 V host logic from an Arduino to the SPI header of a SparkFun board (based on an Adafruit-style tutorial) and end up overvolting the BME280 SPI lines, but 5 V host logic can be compatible with the I2C header of the SparkFun board and safe on the Adafruit board altogether. This type of overvoltage may cause unreliable operation or device damage rather than an immediate, obvious failure.

With respect to address configuration, a single matching parameter is inadequate to ensure compatibility. While both families of breakout boards may have I2C addresses of 0x76 and 0x77, the jumper configurations and pull-up network topologies may differ significantly, making it necessary to verify address, logic voltage, parallel pull-up loading, and jumper states in conjunction with each other when operating on the same bus.

Breakout Board Verification Before Power-Up

The selection of a board should occur prior to any wiring. Preferably, the documentation for the selected board should include a detailed description of the exact components, board revisions, schematics, pinouts, electrical limitations, dimensions, connection details, and software assumptions, as well as an explanation of how all power and signal paths of interest are connected to the host.

Select the Exact Board

Record the manufacturer, product name, SKU, and revision, and check to see if the board actually contains and connects to the specific component and interface that you want to test. Photos of similar-looking products can conceal significant differences, such as different regulators, translators, pull-up resistances, connector types, or PCB revisions; in addition, descriptions provided by resellers cannot replace the manufacturer’s documentation.

Before purchasing a board, check the board’s header and connector types; dimensions; mounting and soldering specifications; whether schematic diagrams are available; whether a library or example code is available; and whether the board is intended solely for prototyping or whether it will be used as a module.

Read the Chip Datasheet

The datasheet should be used to provide information regarding the recommended operating conditions of the device, absolute maximum ratings, pin functions, interface timing, thermal operating conditions, and startup requirements. Be sure to keep the boundary of the device and breakout board distinct; the supply pin of a device does not necessarily equal the Vin pin of a breakout when there is regulation, protection, or conversion circuitry on the board.

Read the Board Schematic or Pinout

When you receive a breakout board, follow the power path from the external connector through to the device and note the regulators, level shifters, pull-up resistors, capacitors for noise suppression, protection devices, jumpers used for setting address, chip-select signals, connectors, and test points. Understanding the schematics of two boards that utilize the same IC can help explain why the two board designs can provide different limit ratings for the host.

If a schematic is unavailable, you can use the pinout, component designators, and part markings as partial evidence of the board’s function; however, the uncertainty surrounding the function of the components should remain visible until further investigation is conducted. You should not assume that a component is a regulator, translator, or protection device based solely upon how the package appears.

Check the Host Platform

You should verify the host’s supply voltage and logic voltage, pin configuration, available bus types, maximum current capacity, existing pull-up resistances, library assumptions, and common reference ground. The host guide will assist with wiring; you must still follow the limitations of the breakout and ensure that all connections are safe to make.

When dealing with missing documentation for boards, do not simply reference a comparable board for existing limits or restrictions. Insufficient or missing documentation creates complex integration issues; this is true even if the current bench test works correctly.

Connect and Test the Board in a Safe Order

When connecting the board for testing, proceed carefully and methodically. Start with low-risk tests (voltage and current) and proceed to complete system tests once you understand and confirm the board will operate as expected; the first useful milestone is an idle state plus at least some identification or response to communication — this will be significantly short of the completed application.

1. Confirm all pin locations, orientation, header requirements, connector keys, mechanical fit, etc.
2. Verify and set all jumpers associated with the board for address, chip selects, boot modes, or interfacing before powering on.
3. Connect the documented power supply, common reference ground, and selected interface with power off.
4. Whenever practical, use a current-limited power supply. Confirm all expected supply voltages and idle current levels before enabling the load.
5. Perform a bus scan, an identification read, a loopback test, a status query, or some other minimal communication test that is appropriate for the board.
6. Document the board revision number, jumper configuration, host, library or firmware version, supply voltage, and successful test results.

Typical bench instrumentation to use for testing includes digital multimeters, oscilloscopes, logic analyzers, and thermometers, as well as current-limited power supplies. Start with electrical tests of continuity, polarity and voltage at all supply rails, and idle current, and proceed through electrical tests of startup timing, edge quality, protocol decoding, ripple voltage or thermal characteristics only after the board fails to operate or demonstrate expected results when powered up.

The mechanical fit of the board is not the same thing as proof of electrical functionality; just because a board fits the 0.1-inch (2.54 mm) grid of a solderless breadboard does not mean the board width, center gap, power-rail continuity, solder joints, or orientation are correct; the solder quality of either a header or wire connectors must also be verified on the actual board assembly, because a poorly soldered header can appear temporarily functional until someone moves the cable. The mechanical footprint of the board may fit for proper mechanical alignment while routing power incorrectly to the wrong pin entirely, thus creating a situation where power is not applied as intended and could damage the board.

Breakout Board Applications

The meaning of a breakout board differs depending on the engineering effort. The illustrations below provide examples of what the breakout board provides in each context, what the prototype can demonstrate, and what aspects of the result must be confirmed before the final design can be completed for production purposes.

IoT Sensor Nodes

When a prototype is designed for an IoT application, there are typically multiple environmental and position sensors that must be utilized well before the enclosure, power supply, radio, and final PCB design have been established. The breakout board allows the project team to test and confirm the sensor range, communication protocol (I2C/SPI), addressing, interrupts, sampling strategy, and firmware using swappable modules without the necessity of committing each component to the first PCB iteration.

The breakout board also allows for system-level interactions that can sometimes be missed during testing of individual sensors. For example: Multiple I2C-based systems (breakout boards) can add parallel pull-ups to a signal line and introduce conflicts into the address space of the different sensors. In addition, wireless transmission can interfere with the power supply rails to the sensor. Additionally, the presence of an on-module regulator or level-shifting circuit can give a misleading representation of the sensor’s tolerance to noise, since the bare sensor itself will not have these features.

As sensors migrate from prototype stage to the final production stage, it is very important to document exact revision level, bus voltage, resistance values, address state, sample rate, calibration, thermal placement, and power characteristics for each sensor. For example, an environmental temperature sensor that provides a perfectly stable reading on its breakout board due to the PCB’s physical size could develop a measurable temperature offset if the temperature sensor is placed in close proximity to the voltage regulator on the final design.

Robotics Motion Control

As with other robotics prototypes, the purpose of the robotics prototype is to combine several different types of sensors and actuators. Examples include the IMU, the encoder, the distance sensors, the motor driver, and current sensor modules. Breakout boards enable separating each individual function; proving out the basic direction and feedback; inspecting PWM or bus communications; replacing a single module without having to redesign the entire controller or system.

When designing a motion system, there are factors that you don’t necessarily see in a static “bench” demo, for example, motor current transients; ground bounce; connector movement; EMI; vibration; supply droop, etc. These factors can interfere with the logic or sensor reading from your motion system. On the other hand, if you have a driver breakout or test board, you may have flyback paths, current limiting, and gate driver circuits that your completed PCB will need to replicate.

It is also vital that you record the load currents, supply behavior, fault states, and motor & sensor grounding, including test conditions with board-level protection active during successful tests. An IMU may read “clean” on the bench, but you may see gyro drift as soon as you place it next to the motor driver’s switching noise when mounted on the final assembly layout.

Wearable Electronics

Wearables also utilize breakouts for evaluating motion sensors; optical sensors; haptic drivers; microphones; wireless modules; displays; and power management systems prior to securing the mechanical stack. Breakouts enable users to quickly test firmware and perform feature testing; however, due to their size and spacing, they may create a substantially different electrical and thermal environment than the final compact assembly.

As wearable products shrink, items such as battery life; temperature rise; sensor placement; flexibility; antenna clearance; cable strain, and whether the product is placed against the skin or inside of a housing become more critical. When a module is mounted on a table, it can behave differently than when the regulator, sensor, radio and battery are all packed closely together within one wearable enclosure.

The breakout phase of development allows the user to capture data about the module while it is powered and while it is in a low power state, the wake-up characteristics of the module, thermal offset of the module, and radio current peaks. For example, a radio module with high transmit-current peaks when used with a breakout board can brown out a coin cell battery supply when it is connected directly into the small board of the wearable, even though the same pinout configuration is used.

Communication Interface Prototyping

Breakout boards for communication protocols and peripheral modules allow for the testing of various types of interfaces and peripheral modules such as USB, UART, RS-485, CAN, Ethernet, Bluetooth, Wi-Fi, GNSS, display modules, data storage devices, etc. They are particularly helpful in determining if the issue with a communication system is related to the protocol, firmware or electrical interface.

A successful link must also be verified at the correct layer. Verify that the voltage levels for the logic signals are correct, check for proper configuration of the transceiver, verify that the cabling and connector limitations are sufficient, check for correct clock or baud rate assumptions, verify that the reset pin for the transceiver is functioning correctly, check to see if the data has sufficient margin for data rate, and determine if the breakout board incorporates ESD protection, isolation from ground, level-translated signals, or any other signal conditioning that may not be available in the next version of the PCB.

In the case of high-speed, RF, or noise-sensitive interfaces, never treat traces on a breadboard as performance references. The purpose of breakouts is to provide verification of device-level control functionality while leaving signal integrity, EMC performance, antenna performance, connector loss, and production layout to be verified on controlled hardware.

Hardware Bring-Up

The primary function of a breakout during board bring-up is access. The breakout board provides exposed pins, test points, and configuration jumpers, as well as working support circuitry, allowing an engineer to measure rail ramp characteristics, reset timing behavior, clock behavior, rate of bus transactions, analog outputs, current draw, temperature behavior, and fault responses through measuring instruments without the difficulty of probing buried pins located on a densely populated product board.

This access and visibility also provides an advantage for breakout boards when they are being utilized in Engineering Training Benches; the relationship between any pin listed in the datasheet, its physical connection, and an instrument measurement will be more evident. Engineers who utilize breakout boards for training will be able to view the interface of the device itself rather than making assumptions based on the idea that the breakout board has simplified or overridden the electrical requirements for that device.

Labeling captures for characterization studies (the revision of the board, firmware revision, location of probe points, instrument settings, supply condition of the component being tested, current load of the component being tested, ambient temperature of the component being tested, and the set pass criteria) will aid the next design team in reproducing the same behavior under the documented conditions. Without these captures, the next design team may misattribute board-level behavior back to the IC itself.

Low-Volume System Integration

The breakout board or module carrier can temporarily integrate a component into a prototype, fixture, laboratory instrument, retrofit, or a low-volume assembly when a particular component is difficult to mount directly to the assembly. It reduces the risk associated with fine-pitch assembly and can create a replaceable sub-module while the system architecture is undergoing development.

Prior to using a catalog breakout board as a permanent component of the finished product, one should confirm the connection retention, vibration behavior, thermal behavior, lifecycle, sourcing, test access, and any safety or regulatory limitations that may apply.

While troubleshooting, one may require a temporary adapter to reconnect to a component package that is not available or has an incorrect connector type. One should treat these types of adapters and connector breakouts as controlled adapters that are documented to have certain limits. One should never consider that the modified assembly has the same mechanical, electrical, or qualification status as the original design.

Breakout Board, Breadboard, Development Board, or Shield?

When product listings fail to differentiate between the four types of products mentioned above, it can lead to actual errors when ordering products. An example would be a customer ordering a breakout board when their project really needed a development board with programming and debugging capabilities, or ordering a shield that only works with a specific ecosystem’s header spacing.

Categories can be used in conjunction with one another, but the categories do not become interchangeable; that is to say there is no substitution of function or capability between them. For example, a development board may control a sensor breakout via a breadboard connection to the development board. However, the sensor breakout could also have been implemented as an independent breakout; thus, the combination of the two adds an additional layer of complexity with respect to managing multiple voltage domains and other technical requirements including connector types and locations, pin assignments, and associated documentation for each component/board involved.

When Should a Breakout Prototype Move to a Custom PCB?

The breakout board stage should be transitioned into a custom PCB when product requirements for size, interconnects, reliability, power, thermal behavior, sourcing, testing, or compliance cannot be satisfactorily demonstrated by using a bench-top module. The fact that a working prototype proves that there was a functioning configuration on the bench does not guarantee that all of the aforementioned aspects will be reproduced on the production PCB.

Preserve the Breakout Dependencies

Prior to replacing the breakout board with the custom PCB, it is essential to capture all details of the breakout board including the exact part number/SKU, revision number, schematic, BOM, power domains, logic domains, connection configurations (interface mode, address or chip-select state, jumpers, pull-ups, regulators, level shifters, filters, protection parts, connectors, firmware, libraries, calibration, and startup behavior). All details including mechanical, thermal, power disturbances, environmental conditions, etc. should also be captured as these factors contributed to the successful development of the prototype.

Convert those captured dependencies into controlled design inputs (e.g., annotated schematics, pin maps, current budget, footprints, tolerances, approvals for component substitutions, bring-up checks, and known fault signatures) — so that the reasons for the successful operation of the prototype will be available for use by design, sourcing, assembly, and test groups as references; the final completed PCB will be put into service by folks other than the individuals that built the prototype. When establishing custom-board bring-up, only collect the required measurements to evaluate the new implementation against the prototype (e.g., rail ramp, inrush, reset timing, bus waveforms, analog performance, temperature, connector characteristics) and ensure each measurement is labeled with reference to its probe point, instrument state, firmware version, sample identifier, operating condition and acceptance criterion for replicability.

Prototype Success Is Not Production Suitability

Although excellent for exploration or experimentation, prototypes may never become suitable for production until definitive assessments have been made as to a component/module’s active support status, supply chain reliability, accuracy and power performance, and identification of potential material/safety/isolation/lifecycle issues at the downstream level.

This matters especially for modules that may conceal large currents (e.g., heaters), mains-connected sensors, radios and obsolete parts under a user-friendly header.

Creepage, clearance, isolation, thermal path, antenna condition, emission levels and regulatory limitations are considerations of the finished implementation, while a working hobby/evaluation module provides none of these assurances by default.

Breadboards contribute parasitic resistance, inductance, and capacitance, whereas a breadboard’s power and ground structures do not visually resemble those of the final PCB layout.

As edge rates increase, electrical noise margins may diminish and, therefore, analog/RF behaviors can become increasingly sensitive.

Therefore, the custom-board layout is an integral component of the circuit and must undergo validation on prototype hardware representative of the actual design on which it is ultimately intended to be implemented.

Particular vendor evaluation products carry restrictions specifying that the evaluation board or module is for use in development, testing or evaluation and not for finished products; thus, checking terms for individual modules or evaluation boards versus assuming all breakouts, carriers or evaluation boards can be used in the same manner is necessary.

First Checks When a Breakout Board Does Not Respond

To troubleshoot quickly when a breakout board fails to respond, always begin with the measurement that indicates failure, rather than going through a full checklist each time you experience a symptom.

The address for an I2C device can be verified by confirming the actual address state and then checking the voltage domain and the pull-up load on the circuit. It is also possible for two different boards to have the same address options (0x76/0x77) and still use different pull-up or level-shifting circuitry. Therefore, when dealing with SPI devices, it is important to verify the chip select, start-up state, and the interface mode of the device before changing libraries or switching out hardware.

To test for intermittent performance issues, physical testing may be required. For example, moving a header and cable gently can reveal a poor solder joint that can be found by physically inspecting each of the supporting hardware components. Also, measuring the voltage across the separate rail segments of the breadboard can reveal broken segments that would otherwise be hidden by the printed lines. Results from these physical tests separate connection issues from configuration and software problems, but do not guarantee that the breakout board is defective.

Conclusion

The chip number identifies the main device. The exact breakout board defines the host-side power, logic, connector, and support-circuit conditions that allow that device to be used in a prototype. Therefore, classify each board, examine the board schematic or pinout, verify the board with the device and host, and record any board-level dependencies found during your testing before creating a custom PCB.