Hello! now
tms@lcdchip.com
Custom Electronics Development & PCBA Manufacturing Guide
A custom PCBA project does not begin with PCB layout and does not end when the first prototype powers on. A production-ready electronic assembly must satisfy product requirements, electrical performance, mechanical constraints, thermal limits, software behavior, manufacturability, testability, supply-chain availability, compliance and long-term service needs.
This guide explains a practical development process for Android motherboards, AI edge controllers, digital signage boards, industrial display systems and embedded smart terminals. It covers product definition, architecture, schematic design, PCB layout, DFX review, EVT, DVT, PVT, pilot production, test fixtures, quality control and mass-production release.
What Is Custom PCBA Development?
A printed circuit board assembly, or PCBA, combines a fabricated PCB with mounted electronic components, connectors, programmed devices and other assembly processes required to perform a defined product function.
Custom PCBA development means adapting or creating that assembly for a specific product. The scope may range from modifying an existing validated motherboard to designing a completely new board, firmware image, display cable, enclosure interface and production test system.
Processor, memory, storage, power, interfaces, protection and peripheral circuits.
Layer stack, placement, routing, impedance, thermal paths and mechanical constraints.
Bootloader, operating system, drivers, APIs, application services and recovery.
SMT, through-hole assembly, programming, inspection, testing and traceability.
Functional, thermal, electrical, reliability, EMC and environmental testing.
BOM availability, change control, repair strategy and long-term production support.
Not Every Project Needs a Fully Custom PCB
A custom design can optimize dimensions, interfaces and cost, but it also creates engineering, validation, tooling and supply-chain work. The first decision should therefore be whether the product truly requires a new PCB.
- Prototype or low-volume product
- Existing board fits the enclosure
- Required interfaces are already available
- Firmware customization is sufficient
- Time to market is the priority
- Connector or cable changes are required
- Some unused interfaces can be removed
- Display, camera or peripheral adaptation is needed
- Board outline is mostly acceptable
- Existing BSP can be reused
- Strict board dimensions or mounting points
- Special display or camera architecture
- High production volume
- Integrated power or backlight circuits
- Unique interfaces or certification needs
Reusing a validated computing platform can reduce risk because the processor, memory, high-speed interfaces and operating system have already passed substantial engineering work. Customization can then focus on the product-specific functions that create commercial value.
EVT, DVT and PVT Definitions
EVT, DVT and PVT are widely used development-stage names, but the exact gate criteria vary by company. The important point is not the label. Each stage must have a defined objective, build configuration, test plan, acceptance criteria and release decision.
| Stage | Main Question | Typical Focus | Expected Result |
|---|---|---|---|
| Requirements | What must the product do? | Functions, performance, cost, dimensions, environment and compliance | Approved product requirements specification |
| Architecture | Can the proposed platform meet the requirements? | Processor, interfaces, power, display, camera, network and software | Feasible system architecture and risk register |
| EVT | Does the engineering design work? | Core functions, circuits, interfaces, firmware and major risks | Corrected design ready for full validation |
| DVT | Does the final design meet the product requirements? | Mechanical, thermal, reliability, EMC, software and user scenarios | Design release candidate |
| PVT | Can the factory build and test it repeatedly? | Assembly process, yield, fixtures, work instructions and traceability | Approved production process |
| Mass Production | Can quality and supply be maintained at volume? | Process control, supplier quality, changes, yield and field feedback | Stable production and lifecycle management |
Phase 1: Product Requirements Definition
Many hardware problems originate before the schematic is drawn. A vague requirement such as "an RK3588 Android board with many interfaces" does not define a product. It does not explain display combinations, camera bandwidth, environmental limits, power architecture or how the system will be tested.
Product Requirements Checklist
Requirements Must Be Testable
"The board must run cool" is not a testable requirement. "The processor shall not enter thermal throttling during two hours of 4K playback inside the final enclosure at the specified ambient temperature" is testable.
No start condition, endpoint or time limit is defined.
Defines power-on state, endpoint and measurable acceptance limit.
Phase 2: Feasibility and System Architecture
The feasibility stage converts product requirements into an implementable architecture. This is where the team confirms whether the selected processor, memory, power system, interfaces and software platform can operate together.
Architecture Review Questions
- Can all required display outputs operate simultaneously?
- Do cameras and USB devices exceed shared bus bandwidth?
- Is the memory capacity sufficient for peak workload?
- Does the processor support every required driver and operating-system version?
- Can the input supply support processor, display, backlight and peripheral startup current?
- Are connector locations compatible with the enclosure and cable paths?
- Is the proposed thermal solution realistic inside the final product?
- Are critical components available for the intended product lifetime?
Phase 3: Schematic Design and Component Selection
The schematic defines how the processor, power rails, memory, interfaces, protection circuits and connectors work together. A correct logical connection is only the starting point; component ratings, sequencing, tolerances and abnormal conditions must also be reviewed.
- Input voltage range
- Rail current margin
- Power sequence
- Transient response
- Protection and reset
- Reference design use
- Termination
- ESD protection
- Clock architecture
- Connector bandwidth
- Lifecycle status
- Approved alternatives
- Lead time
- Package availability
- Cost risk
- UART console
- Test points
- Recovery mode
- Programming interface
- Current measurement
Component Derating and Margin
Components should not be selected only because their nominal ratings equal the expected operating condition. Voltage, current, temperature, tolerance and transient margin must be considered, especially for power components, connectors, protection devices and backlight drivers.
Phase 4: PCB Layout and Stack-Up
PCB layout determines whether the schematic can operate reliably in physical form. Placement, return-current paths, impedance, pair matching, via transitions, copper area and component temperature all influence the finished board.
PCB Layout Checklist
- Define the stack-up and controlled-impedance requirements before routing.
- Place memory close to the processor and follow the platform routing strategy.
- Maintain continuous reference planes under high-speed signals.
- Keep switching power nodes away from sensitive clocks, RF and display lanes.
- Match differential pairs and relevant bus groups.
- Minimize unnecessary layer changes and via stubs.
- Place ESD protection close to external connectors.
- Provide copper and airflow for processors and power components.
- Check connector accessibility after enclosure assembly.
- Include sufficient test points for production and failure analysis.
DFX: Design for More Than Functionality
A board can pass a laboratory functional test and still be expensive to manufacture, difficult to inspect, impossible to repair or unreliable in service. DFX reviews address these risks before production tooling and large material purchases.
| Review | Main Objective | Example Questions |
|---|---|---|
| DFM | Make the PCB repeatable to fabricate | Are trace, space, drill, annular ring and stack-up within supplier capability? |
| DFA | Make assembly stable and efficient | Are footprints, spacing, polarity marks and component orientations suitable for SMT? |
| DFT | Make faults detectable | Can critical rails, buses and functions be accessed by test points or fixtures? |
| DFR | Meet the expected service life | Are thermal cycles, vibration, humidity and solder-joint stress considered? |
| DFC | Control total product cost | Can expensive components, layer count, assembly steps or test time be reduced? |
| DFS | Support repair and field recovery | Can firmware be recovered and replaceable modules be accessed safely? |
BOM Management and Supply-Chain Risk
A technically ideal design can fail commercially if critical components are unavailable, allocated, obsolete or sourced from an uncontrolled channel. BOM strategy should begin during architecture selection rather than after the design is complete.
Standard packages, stable demand and qualified alternatives.
Available today, but requires lifecycle and lead-time monitoring.
No practical substitute without PCB or firmware redesign.
Lifecycle transition, counterfeit exposure or unstable availability.
BOM Control Fields
- Manufacturer and complete manufacturer part number
- Package, value, tolerance, voltage and temperature rating
- Approved manufacturer list and approved vendor list
- Lifecycle and last-time-buy status
- Standard and maximum lead time
- Minimum order quantity and packaging type
- Approved alternatives and required qualification tests
- Firmware dependency or calibration data
- Change-notification responsibility
Design Release Package
Manufacturing should not begin from an informal collection of files. A controlled release package reduces interpretation errors and ensures that PCB fabrication, assembly, programming and inspection use the same revision.
EVT: Engineering Validation Test
EVT is the first stage where the proposed electrical design is built and exercised as a system. The objective is to discover design errors and high-risk behavior while changes are still expected.
Electrical function, interfaces, power, boot, firmware and architecture risks.
Small engineering build with extensive measurement and rework access.
Component values, routing, protection, connectors, thermal solution and firmware.
EVT Test Categories
- Input range
- Rail voltages
- Startup sequence
- Ripple and transient response
- Boot reliability
- Memory stress
- Storage read/write
- RTC and watchdog
- Display and touch
- USB and Ethernet
- Serial, GPIO and CAN
- Camera and audio
- Driver loading
- API operation
- Recovery mode
- Application startup
- SoC temperature
- Regulator temperature
- Throttling behavior
- Heat-sink contact
- UART logs
- Current measurement
- Test-point access
- Failure reproduction
EVT Exit Criteria
- All critical product functions operate on representative hardware.
- Major power, thermal and interface risks have corrective actions.
- Known defects are documented and assigned.
- Required PCB changes are reviewed.
- The next hardware revision has a controlled change list.
- The DVT test plan is approved.
DVT: Design Validation Test
DVT verifies that the near-final product design meets the approved requirements. Testing should use representative PCB, enclosure, cables, display, power supply, firmware and production-intent components.
Complete product performance, reliability, mechanical integration and compliance readiness.
Production-intent design with controlled components, cables and firmware.
Limited corrections rather than major platform or architecture changes.
DVT Test Categories
All functions, peripherals and application workflows.
Mounting, connector access, cable strain and enclosure tolerances.
Final enclosure, maximum load and target ambient temperature.
Temperature, humidity, vibration or other project-specific stress.
Power interruption, brownout, surge, ESD and recovery behavior.
Long operation, watchdog, update, rollback and storage-full behavior.
EMC, safety and market requirements applicable to the finished product.
Power cycles, interface insertion, cable movement and extended operation.
DVT Exit Criteria
- Product requirements are traced to completed test results.
- Critical and major defects are closed or formally accepted.
- Mechanical drawings and production-intent enclosure are released.
- Firmware and configuration are controlled.
- Compliance risks are understood before certification testing.
- The hardware design is approved for production validation.
PVT: Production Validation Test
PVT validates the production process rather than redesigning the product. The boards should be built using the intended factory, equipment, tooling, materials, work instructions, programming process and test fixtures.
Yield, cycle time, process stability, test coverage and operator instructions.
Pilot production using released manufacturing data and production-intent tooling.
Process optimization, fixture corrections and documentation improvements.
PVT Validation Areas
- PCB fabrication yield and incoming inspection
- Solder-paste printing and stencil performance
- SMT placement accuracy and component orientation
- Reflow profile and solder-joint quality
- Through-hole and manual assembly operations
- Programming time and firmware verification
- Functional-test coverage and false-failure rate
- Fixture repeatability and maintenance
- Operator work instructions and training
- Serial-number and test-result traceability
- Packaging and shipping protection
PVT Metrics
Production Test Strategy
A strong production test does not attempt to repeat every DVT test. It detects manufacturing defects quickly and consistently while confirming the functions most likely to fail because of assembly, programming or component variation.
Possible Test Methods
| Method | Best Used For | Important Limitation |
|---|---|---|
| AOI | Placement, polarity and visible solder defects | Cannot prove complete electrical function |
| X-ray | Hidden solder joints such as BGA or bottom-terminated parts | Requires interpretation and does not replace functional testing |
| Flying Probe | Low-volume electrical checking without a dedicated fixture | Slower than a production fixture |
| ICT | High-volume node and component-level checking | Requires test access and dedicated tooling |
| Functional Test | Boot, interfaces, communication and real product functions | Coverage depends on the fixture and test software |
| Burn-In or Stress Test | Early-life failures and thermal stability | Adds time, equipment and operating cost |
Design for Testability
Testability must be included in the PCB layout. Adding test points after the board is routed may be impossible without compromising signal integrity, enclosure clearance or component placement.
Recommended Production Test Access
- Input voltage and every critical power rail
- Ground references distributed across the board
- Reset, boot-mode and recovery signals
- Programming or flashing interface
- UART debug console
- Critical communication buses where practical
- Current-measurement or isolation points
- Board identification and revision data
Firmware, Programming and Configuration Control
A production PCBA is defined by both hardware and software. Two physically identical boards may behave differently if bootloaders, device trees, calibration data, security keys or application versions differ.
Production Software Controls
- Approved firmware checksum and version
- Board-revision compatibility
- Programming tool and procedure
- Unique serial number or device identity
- MAC address and network identity management
- Calibration-data storage and backup
- Secure-key handling where applicable
- Post-programming verification
- Recovery procedure for failed programming
- Update and rollback strategy after shipment
Thermal Validation
Bench testing with an open board is not sufficient for a product that will operate inside a sealed or narrow enclosure. Thermal validation must use representative workload, display brightness, network activity, peripheral load and mechanical construction.
Thermal Tests
- Idle and maximum sustained workload
- Simultaneous CPU, GPU, NPU and video workload
- Maximum display brightness
- Wi-Fi, Ethernet and storage activity
- All powered USB and peripheral devices connected
- Final heat sink and thermal pad
- Final enclosure and mounting orientation
- Highest expected ambient temperature
- Thermal throttling and restart monitoring
EMC and Compliance Planning
Compliance cannot reliably be added after the PCB and enclosure are finished. Connector protection, filtering, grounding, shielding, cable construction and power architecture should be considered during design.
Clocks, switching regulators, display interfaces, cables and enclosure openings.
ESD, electrical fast transients, surge and RF disturbance where applicable.
Voltage, current, insulation, temperature, fire enclosure and power supply.
Substance restrictions and documentation required by the target market.
The applicable requirements depend on the finished product, installation, market and industry. A PCBA test report does not automatically certify the complete end product.
Configuration and Engineering Change Control
Once a design enters validation, uncontrolled changes can invalidate previous test results. Every PCB, BOM, firmware, cable and mechanical revision should be identifiable.
Describe the problem, reason and affected products.
Evaluate electrical, software, supply, test and compliance effects.
Define the tests required to approve the change.
Update controlled files and effective production date.
Changes That Require Special Attention
- Processor, memory or storage substitution
- Power regulator or inductor change
- PCB stack-up, material or copper-weight change
- Display, camera or wireless-module replacement
- Firmware, bootloader or device-tree change
- Connector, cable or pinout change
- Factory, solder paste or assembly-process change
- Critical component supplier change
Mass Production Ramp
Mass production should begin only after product design and production process are both released. Initial volume should still be monitored closely because supplier variation, operator learning and material batches may expose new issues.
Close monitoring, full data collection and rapid engineering response.
Confirm yield, takt time, fixture capacity and material flow.
Operate with defined process limits, audit and change control.
Ongoing Production Controls
- Incoming material inspection
- Moisture-sensitive component control
- Stencil, printing and reflow process monitoring
- AOI and functional-test result analysis
- Yield and defect trend review
- Calibration and fixture maintenance
- Serial-number and lot traceability
- Golden sample control
- Outgoing inspection and packaging verification
Common Reasons PCBA Projects Fail
Display, connector or enclosure requirements change after layout release.
The design works in engineering but cannot be tested efficiently at volume.
A critical component becomes unavailable before production begins.
Hardware and software versions are not controlled as one product configuration.
The system overheats only after installation in the final enclosure.
One hand-reworked board works, but process variation is not understood.
Root cause becomes difficult to isolate between PCB, BOM and firmware revisions.
Teams disagree about whether a test result is acceptable.
Development Gate Deliverables
| Gate | Required Deliverables |
|---|---|
| Requirements Gate | Product requirements, use cases, target cost, schedule and acceptance criteria |
| Architecture Gate | Block diagram, platform decision, power estimate, interface matrix and risk register |
| Design Release | Schematic, PCB data, BOM, drawings, firmware plan and manufacturing notes |
| EVT Gate | EVT report, defect list, measurements, rework records and next-revision changes |
| DVT Gate | Requirement traceability, validation reports, compliance status and design release approval |
| PVT Gate | Yield report, fixtures, test software, work instructions, traceability and process approval |
| MP Gate | Released BOM, firmware, golden sample, quality plan and change-control process |
Example PCBA Development Plan for a Smart Display Terminal
1080p LCD, USB touch, camera, Wi-Fi, Ethernet, speakers and automatic startup.
Validated Android SoC platform, eDP/LVDS display, USB camera and 12V input.
Validate display timing, camera bandwidth, audio, boot, APIs and power rails.
Test final enclosure, thermal performance, ESD, cable retention and application stability.
Validate SMT build, firmware programming, display fixture, camera test and traceability.
Control panel, touch, cable, PCBA and firmware revisions through production.
How LCDChip Platforms Can Shorten Development
Starting from an existing motherboard platform can shorten the feasibility and EVT stages when the base processor, memory, operating system and primary interfaces already match the application.
Android Display Platforms
Platforms for Full HD LVDS, HDMI input, 4K V-by-One, touch displays and integrated commercial screens.
View Digital Signage SolutionsEmbedded AI Platforms
RK3568, RK3576 and RK3588 platforms for edge AI, access control, multi-screen terminals, cameras and industrial I/O.
View AI Terminal SolutionsCustom PCBA Evaluation
Submit the product requirements, interfaces, drawings, expected quantity and development schedule for technical evaluation.
Submit a Project RFQHow to Prepare a Custom PCBA RFQ
A strong RFQ allows the engineering team to evaluate feasibility, identify missing requirements and estimate development risk before quotation.
Recommended RFQ Information
- Product description and application scenario
- Functional block diagram or reference product
- Required processor, operating system or preferred platform
- LCD model, resolution, interface and touch specification
- Camera quantity, interface, resolution and frame rate
- USB, serial, GPIO, CAN, relay and other I/O requirements
- Ethernet, Wi-Fi, Bluetooth, 4G and antenna requirements
- Audio input, output and amplifier requirements
- Input power, battery or PoE requirements
- Board outline, mounting holes and connector direction
- Operating temperature and environmental conditions
- Firmware, APIs, application and OTA requirements
- Target certifications and sales markets
- Prototype quantity and expected annual volume
- Target cost and project schedule
Planning a Custom Motherboard or PCBA Project?
```Send the product requirements, display and camera specifications, interface list, mechanical drawings, operating environment and volume target. LCDChip can help evaluate a standard platform, controlled customization or complete custom PCBA development.
View Solutions & PCBA Submit RFQ ```FAQ: Custom PCBA Development
What is the difference between PCB and PCBA?
A PCB is the bare printed circuit board. A PCBA is the assembled board with electronic components, connectors and other manufacturing processes completed.
What does EVT mean in hardware development?
EVT means Engineering Validation Test. It verifies that the proposed electrical design, firmware and core interfaces work and identifies changes required for the next revision.
What is tested during DVT?
DVT validates the near-final product against functional, mechanical, thermal, environmental, reliability, software and compliance requirements.
What is the purpose of PVT?
PVT verifies that the factory can assemble, program, inspect and test the released design repeatedly using production-intent processes and tooling.
When should a project use a standard motherboard?
A standard board is suitable when its dimensions, interfaces, performance and software already meet the product requirements, especially for prototypes and lower-volume projects.
What is DFM in PCBA development?
DFM means Design for Manufacturability. It reviews whether the PCB can be fabricated and assembled consistently using realistic production capabilities.
Why is design for testability important?
Testability allows production equipment to access critical power rails, programming interfaces and functions so assembly defects can be detected quickly and consistently.
What files are needed for PCBA manufacturing?
A controlled package normally includes PCB manufacturing data, fabrication and assembly drawings, BOM, placement data, programming files, test specifications and revision records.
How long does custom PCBA development take?
The schedule depends on design complexity, software scope, prototype iterations, component lead times, testing and certification. A realistic plan should include time for correction and revalidation.
What information should be included in a custom PCBA inquiry?
Include the application, functional requirements, interfaces, display and camera specifications, board dimensions, power, operating environment, software needs, quantity, target cost and schedule.
