Linux-Based TI DS90UB949 Serializer Prototype with 24V Power Circuitry
Prototype board for a TI DS90UB949 serializer with an embedded Linux processor, HDMI input, Ethernet, I2C backchannel control, and 24V DC input power.
Advanced Project
— This is advanced because it combines a Linux-capable SoC, HDMI high-speed signaling, Ethernet PHY design, I2C control, and a multi-rail 24V power tree on a custom prototype PCB.
Assumptions:
- The board is a prototype carrier/custom PCB around the DS90UB949, not a fully production-hardened design.
- The user wants a practical Linux-capable SoC/module rather than a bare application processor plus custom DDR design.
- HDMI is intended as an input source into the serializer-side system, so an HDMI receiver path is needed.
- The 24V input is an external DC supply, so onboard DC/DC conversion is required to generate 5V/3.3V and any SoC rails.
Bill of Materials
Compatibility Notes
- AM3358BZCZ100 and ADV7619KSVZ both operate in the 3.3V logic ecosystem, which simplifies I2C and control interfacing.
- The AM3358BZCZ100 control path uses I2C backchannel-style management, so a level translator such as AM3358BZCZ100 or AM3358BZCZ100 may be needed if any rail domains differ.
- DP83848MPHPEP expects a proper RMII/MII connection to the SoC MAC plus the usual magnetics and RJ45 circuitry; it is not a standalone network solution.
- 24V input cannot be fed directly to the SoC or HDMI/Ethernet parts; you need at least one efficient buck stage for 5V/3.3V and likely additional rails for the processor core and DDR.
- If you use LD1117V33 anywhere on the board, keep its input voltage low enough to avoid excessive dissipation; do not drop 24V straight into it.
You'll Also Need
- DS90UB949 serializer itself was not provided in the database, so you will need to source the actual serializer IC separately.
- You will need the SoC support components: DDR memory, boot flash, crystal/oscillator, reset circuitry, and any required PMIC or buck regulators not explicitly listed here.
- HDMI requires connectors, ESD protection, and likely a receiver-side reference design implementation around ADV7619KSVZ.
- Ethernet requires RJ45 connector, magnetics, termination parts, and ESD protection.
- A custom PCB, programming/debug headers, and test points are required for bring-up.
- You will need passive components for all power rails: inductors, bulk capacitors, decoupling capacitors, feedback resistors, and possibly ferrites.
Estimated BOM Cost: $245-275 (based on live distributor pricing)
Design Considerations
Power Architecture
Do not try to derive all rails from a single linear regulator off 24V; the heat will be excessive and the board will be unreliable. Use a front-end buck stage from 24V to an intermediate rail such as 5V or 3.3V, then local bucks/LDOs for the SoC core and analog rails. For a Linux SoC, the total rail count usually grows quickly, so plan the power tree before routing the PCB.
HDMI Receive Path
ADV7619KSVZ is the right functional block, but HDMI routing and ESD protection matter a lot more than people expect. Keep the HDMI connector close to the receiver, maintain controlled impedance, and follow the reference layout for differential pairs and hot-plug handling. If the source is noisy or the cable is long, signal integrity problems will show up before firmware issues do.
Linux SoC Bring-Up
AM3358BZCZ100 is a good prototype SoC, but custom board bring-up still requires DDR tuning, boot configuration, and power sequencing. Budget time for serial console access, JTAG or recovery boot paths, and a minimal bootloader image before attempting the full video pipeline. A watchdog and a known-good recovery image are worth adding early.
Ethernet Reliability
DP83848MPHPEP is straightforward, but the magnetics, RJ45, and PHY clocking are where prototype failures usually happen. Keep the PHY close to the connector, route the differential pairs cleanly, and include ESD protection on the cable side. Verify link-up with a scope and a known-good switch before blaming software.
I2C Backchannel Control
The AM3358BZCZ100 control plane will likely share I2C with other devices, so bus capacitance and pull-up sizing matter. If the board spans multiple voltage domains, use AM3358BZCZ100 or AM3358BZCZ100 only where needed and keep the bus short and clean. For a prototype, a slow I2C clock and strong pull-up discipline will save a lot of debug time.
Prototype Scope Control
This is not a beginner board because it combines Linux, HDMI, Ethernet, and multi-rail power on one custom PCB. The fastest path is to prototype the SoC on an existing module or reference carrier, then integrate the HDMI and serializer path in stages. Trying to validate everything at once usually makes debugging ambiguous and slow.
Want to customize this project or build something different?
Try the Project Advisor


