What Is Board Bring-Up?

The board bring up process involves testing and making sure that the manufactured PCB works correctly, and then bringing up its hardware functionalities via firmware in a systematic manner. It begins with basic functionalities like power rails, current consumption, resets, clocks, programmability and booting mode.

And only after verifying these functions can the board bring up progress to functionalities like memory, interfaces, sensors, radios, displays, storage devices, actuators, and applications.

This order is important because the firmware engineers should not waste time debugging the application software when the problem is just a wrong polarity for the reset line, missing pull up resistor, instable power rail, wrong load capacitor, or wrong pin functionality configuration.

A disciplined bring-up process normally includes:

  • Schematic, PCB layout and BOM review before power is applied
  • Power-rail, current-consumption and thermal checks
  • SWD, JTAG, UART or USB debug access validation
  • Reset, bootloader and clock-tree verification
  • GPIO, ADC, PWM, timers and interrupt testing
  • External flash, EEPROM, RAM and SD-card integration
  • I2C, SPI, UART, CAN/CAN FD, USB, Ethernet and RS-485 testing
  • Sensor, display, motor, battery-management and radio driver enablement
  • Fault handling, watchdogs, low-power modes and production diagnostics

The outcome is more than "the board turns on." It is a documented and repeatable firmware foundation that enables the next engineering stage with less risk.

HAL, BSP and Device Driver Development

Hardware Abstraction Layer is the separation of product logic from board specifics. Without proper HAL, the application code will be tightly coupled to specific MCU, pinout and library of specific vendor. In this case, even minor change of the hardware, MCU or new version of the product will cost additional money.

The services provided by our HAL Development include interface definition for GPIO, timers, non-volatile storage, communication protocols, sensors, states and identification of the device. Application calls stable interface, but the board-specific code below is changed.

The Board Support Package is a set of all configurations for one specific board of the product. The board support package can include clock configuration, pinout map, startup code, link scripts, device tree, boot configuration and others.

For RTOS-based systems, we can integrate FreeRTOS, Zephyr, ThreadX or an appropriate vendor framework while keeping drivers modular and testable.

Our device driver development covers both standard peripherals and custom components, including:

  • I2C, SPI and UART sensor drivers
  • BLE, Wi-Fi, LoRaWAN, Thread, Zigbee and cellular modules
  • Touch controllers, LCD/OLED/e-paper displays and LEDs
  • GNSS/GPS, accelerometer, gyroscope and environmental sensors
  • Motor-control, relay, valve and actuator interfaces
  • BMS, fuel-gauge, charging and power-management ICs
  • CAN/CAN FD, Modbus, RS-485, Ethernet and USB devices
  • Secure elements, NFC, RFID, fingerprint readers and access-control modules
  • External NOR/NAND flash, FRAM, EEPROM and file systems

We do not treat drivers as isolated code snippets. Each driver is designed around real hardware timing, interrupt behaviour, error recovery, bus contention, power consumption and system safety.

Our Board Bring-Up Methodology

1. Review Before Debugging

We start off with looking at the schematic, PCB layout, bill of materials, MCU data sheet, reference design, and any other manufacturing related material that may be available. This allows us to know what potential hazards we might encounter prior to wasting our lab time, such as wrong voltage domains, unconnected pins, etc.

2. Establish a Reliable Debug Foundation

We validate the programming and debug path first. Depending on the platform, this may include SWD, JTAG, UART bootloader, USB DFU or a vendor programmer. We confirm that the MCU can be identified consistently, flash can be erased and programmed, and reset behaviour is predictable.

3. Enable Hardware in the Correct Order

Our engineers employ firmware steps that are easy to test, rather than turning on all subsystems simultaneously. An initial GPIO test might be followed by checking the clock, followed by logging over serial, testing memory, probing buses, identifying sensors, and testing communications. At each step, uncertainty is reduced and evidence accumulated for the bring-up report.

4. Build Production-Ready Software Foundations

Once the board is stable, we structure drivers, HAL modules, diagnostic hooks, fault codes, watchdog behavior, and power states for maintenance purposes. Secure booting, signed firmware images, OTA updates, test firmware, and serial number programming are some other aspects that we could also incorporate into our platform.

Case Study: EVT Board Bring-Up and Firmware Foundation for a BLE Smart Ring

BLE smart ring EVT board bring-up and firmware foundation using Nordic nRF52
Client

Client: North American Wearable Technology Start-up

Adequate Infosoft assisted a North American technology start-up company that was designing a small Bluetooth Low Energy smart ring for use in lifestyle and wearables industry.

The client was already in the EVT phase with the early hardware design and needed an embedded development partner that would help build a reliable firmware base, validate the board and get ready for further DVT and manufacturing phases.

The device had strict physical and electronic specifications as it had to be small in size, consume less power and still be able to communicate through touch, gestures, LEDs, haptics and BLE.

In an early wearable prototype, even a small issue in wake-up timing, peripheral configuration or current leakage can significantly affect usability and battery life.

Engineering Approach

Bring-Up and Low-Level Engineering Approach

The process started with the validation of the firmware environment, debugging capabilities, and MCU board configuration for a Nordic nRF52 family platform.

We created repeatable development workflows and validated GPIO, interrupts, peripherals timing, and low power mode transition behavior. This way, our team could quickly separate board-level problems from firmware integration problems at an early stage of the EVT.

We designed the firmware using low-level modules that can be reused instead of hardware calls inside the product functionalities. A HAL layer was used to control GPIOs, timers, LED channels, haptic output, and power modes of the board.

This helped us modify the pinout and hardware behavior in future PCB designs without modifying gesture and BLE code.

For the user-interaction layer, we developed driver-level control for touch input, haptic feedback and LED indicators. Gesture input was translated into defined operating modes, while the firmware controlled feedback timing so the ring remained responsive without wasting power. We also implemented event-driven handling so the MCU could spend more time in low-power states rather than continuously polling peripherals.

The BLE functionality was implemented separately, as a module that has well-defined interfaces with the rest of the application code.

The system provided robust pairing and connection flows while maintaining synchronization between the radio operations, user interaction and the power states. That was necessary due to the possibility of unstable behavior of wearable products when a radio event conflicts with the sensors.

The project also included firmware architecture work to support future expansion. The client required a design that could evolve as final hardware decisions, product features and manufacturing requirements became clearer. By separating board support, device drivers, HAL services and higher-level application logic, the firmware was positioned for safer updates through the subsequent DVT and PVT stages.

This resulted in an EVT-capable embedded platform that provided the customer with an obvious path from prototype testing to a more advanced wearable device.

This showed that, in addition to booting the device, the success of the board bring-up is determined by the creation of robust testable low-level software for the evolving hardware product.

Full project reference: ble-smart-ring-firmware-development-using-nordic-nrf52

Relevant Adequate Infosoft Delivery Experience

Our related case studies show hands-on experience across custom hardware, embedded firmware, sensors, wireless connectivity and production-focused validation.

Smart Electricity Meter Using Silicon Labs EFR32FG23
Smart Energy

Smart Electricity Meter Using Silicon Labs EFR32FG23

Smart electricity meter based on the Silicon Labs EFR32FG23 that uses sub-GHz wireless communication, 4 layers printed circuit board and low-power embedded firmware. The design of this system focuses on hardware, wireless connectivity, and power efficiency aspects of designing smart meters.

Read the smart meter case study
STM32-Based Industrial Gas Leak Detection Device
Industrial Safety

STM32-Based Industrial Gas Leak Detection Device

An STM32-based industrial gas leak detection device integrates sensor acquisition, calibration and edge processing to support gas monitoring in petrochemical environments. LoRaWAN and BLE Mesh connectivity enable data communication across industrial monitoring systems, while embedded firmware coordinates sensor readings and processing for improved visibility into potential gas-related risks.

Read the gas leak detection case study
Nordic nRF52840-Based BLE Smart Lock Platform
Access Control

Nordic nRF52840-Based BLE Smart Lock Platform

This BLE-enabled smart lock platform combines Nordic nRF52840 technology, custom hardware and embedded firmware with RFID and fingerprint authentication. Cloud-connected access control supports connected lock management, bringing together multiple access methods and wireless communication in an integrated smart locking solution.

Read the smart lock case study
STM32-Based IoT Vibration Monitoring Device
Condition Monitoring

STM32-Based IoT Vibration Monitoring Device

A vibration monitoring IoT system based on STM32 wireless microcontrollers incorporates unique PCB design and data acquisition as well as wireless communication by means of RTOS. It is possible to apply such an IoT device for vibration and condition monitoring in order to collect equipment data and predict machine maintenance.

Read the vibration monitoring case study
ESP32 and Thread Mesh HVAC Automation Platform
HVAC

ESP32 and Thread Mesh HVAC Automation Platform

The HVAC automation solution is built on the use of ESP32 hardware combined with Thread Mesh networking and firmware for the implementation of intelligent zone control. The cloud software as well as the mobile application interface links the control system with the user interface for HVAC management.

Read the HVAC automation case study

Why Low-Level Firmware Quality Matters

Low quality low-level firmware is usually encountered as an occasional problem of the product: sensor disappearing, loss of connection upon wake from sleep, board malfunctioning only at low temperatures, and reset of the device during motor activity.

These problems can cost quite a lot since they are not a simple application error but may relate to such things as electrical behavior, timing, interrupt priorities, race conditions, or power sequences.

An experienced board bring-up engineer decreases that cycle. We use serial traces, logic analyzers, oscilloscopes, protocol analyzers, current measurement, and debugger watchpoints for identification of the root cause of the problem.

We are also straightforward in our documentation of the limits. If there is a need for hardware changes, we specify those clearly and make sensible suggestions.

Testing, Documentation and Handover

A successful engagement at the firmware level will provide your team with useful engineering artifacts beyond just the binary artifact. Depending upon the scope of the project, we could be delivering source code, BSP/HAL architecture, driver APIs, board configurations, test utilities, bring up instructions, list of known issues along with recommendations for the next PCB version.

We coordinate with your internal engineering team, hardware designer or even manufacturing partner to make sure that the decision making process is documented. It is very helpful during the transition into certification phase and pilot production.

Start Your Board Bring-Up Project

If you own a brand-new PCB or prototype, or if you possess an unstable device and need low-level firmware, Adequate Infosoft will assist in making the transition from hardware validation to a full-fledged embedded software system. You just need to provide us with the schematic, board description, and required product functionality.

Frequently Asked Questions

What is required to begin board Bring-up?

In general, we require the schematic, the PCB layout or Gerber file, the BOM, the MCU and component part numbers, the programming interface information, the existing firmware if any, and the list of the expected functionality. The sample board and hardware problems are also helpful.

Can you help if our custom board does not boot?

Yes. We can investigate the power, reset, boot configuration, clock source, programming interface and startup firmware. We use a staged method to identify whether the problem is hardware, configuration or software.

Do you work with existing vendor HALs?

Yes. We can use and structure vendor HALs such as STM32Cube HAL, Nordic SDK/Zephyr drivers, ESP-IDF, Silicon Labs SDKs or TI SDKs. Where required, we create custom abstractions to reduce vendor lock-in and improve code maintainability.

Can a driver be developed for a custom sensor/IC?

Yes, it is possible. The driver is developed using the data sheet and reference design of the component. It involves initializations, register configurations, interrupt handling, calibration, error handling, and interface through I2C, SPI, UART, or other supported interfaces.

Do you offer production testing and firmware upgrades?

Yes, we can offer firmware for manufacturing tests, serial number provisioning, debug commands, factory programming, bootloading, and OTA update firmware architecture.

Which industries do you cater to?

We offer board bring-up and driver development for IoT, industrial automation, smart homes, access control, wearable devices, healthcare devices, energy, EV charging, GPS tracking, security devices, and consumer devices.

Ashok Patel
Ashok Patel
Senior Engineering Project Manager
AI/ML, DevOps, Data Science & Automation | IoT & C#/.NET | Azure & AWS Expert | Certified AI & Cloud Engineer | 1,500+ LinkedIn Followers