Single-pair Ethernet and power: approach selection, bench structure and evaluation preparation

Choose the approach that answers the current question

Sources: Official CN0575 materials, official TIDA-010261 materials. Both are reference designs for bench development. They are not one interchangeable set of finished products.

Selection guidance: if the immediate question is how an existing Linux application can obtain sensor data, start by examining CN0575 hardware and image preparation. If you need to evaluate how analog sampling, edge processing and reporting can be integrated into one embedded node, TIDA-010261 is closer to that task, provided board-fabrication and software-adaptation resources are confirmed first. If you only want to verify a particular cable, either development approach may exceed what is needed. Compatible endpoint devices that already work together are usually a more suitable comparison baseline. This is engineering guidance based on evaluation tasks, not a ranking of manufacturer performance.

Draw data and power as separate paths first

The following functional relationships are compiled from the reference designs. They help allocate bench-preparation work. They do not imply that the two designs can connect directly, or replace a wiring diagram for the specific board.

CN0575: the relationship between the Linux host and the single-pair link

1. Raspberry Pi / Linux application↔
2. SPI↔
3. ADIN1110 MAC-PHY↔
4. On-board coupling network and single-pair cable↔
5. Compatible link partner

1. Compatible power sourcing equipment (PSE)→
2. Single-pair cable and on-board power network→
3. LTC9111 powered-device (PD) control and downstream supplies→
4. On-board loads / Raspberry Pi

Carrying data and power on the same cable does not mean both functions will work automatically. The data link requires checking endpoint modes and the application. Power over the same pair also depends on PSE capability, the powered-device class and board settings. A media converter’s data interface does not establish that it supplies the required power. CN0575 function and power description

TIDA-010261: analog sampling, embedded processing and upload

1. Analog front end / evaluation module→
2. AM2434 application processing↔
3. DP83TD510E PHY↔
4. On-board interface and single-pair cable↔
5. Compatible link partner

1. PoDL Type E, Class 12 powered-device path in the manufacturer's configuration
2. Supported auxiliary-power configuration

Power selection: Use the PoDL Type E, Class 12 powered-device path in the manufacturer's configuration, or evaluate with its supported auxiliary-power configuration. See the design guide for specific settings and switching conditions.

Beyond Ethernet, this approach integrates the analog-front-end interface, application firmware and power control. The manufacturer’s materials provide entry points for design and debugging; the implementing team still needs to arrange board acquisition, startup and software adaptation. Diagram arrows show functional relationships and do not imply that two power supplies can be connected directly in parallel. TIDA-010261 overview

Turn approach selection into a preparation decision

Suppose a team already has a Raspberry Pi data application and wants to evaluate a single-pair link. CN0575 deserves examination first because it is close to the existing host and development environment. That judgment is not yet a purchase order. The team should obtain the complete user guide, check the image and device tree, link partner and power arrangement, then determine whether the boards and cable can form a complete bench setup.

If the actual goal changes to building an embedded node that connects an analog front end, and the team already has resources for board fabrication, startup debugging and firmware adaptation, TIDA-010261 materials are closer to the task. Procurement should then receive a versioned BOM and an engineering-preparation checklist. The fact that the complete validation board is not sold must be included in scheduling.

If the goal is simply to compare two cables, it is more suitable to establish a baseline with compatible endpoint devices that already work together. Changing the development platform, firmware and cable in the same comparison makes it difficult to identify which change caused an anomaly. These are engineering-selection recommendations for hypothetical scenarios; they provide neither measured results nor a cost ranking of the approaches.

List procurement and software preparations together

CN0575: check the complete bench, not just one board

The evaluation section of the official Circuit Note Rev. A lists the CN0575 board, Raspberry Pi 3B+ or later, host computer, single-pair cable, RJ45/USB connections and example scripts. The connection procedure uses EVAL-ADIN1100-EBZ as the link partner and requires power to match the board settings. The Raspberry Pi needs the corresponding Kuiper Linux and device tree. Evaluation section, page 6

Use this material to build your bench checklist, but do not infer that a media-converter board provides every PoDL/SPoE power function. Check the data partner, power injection method, powered-board jumpers and supply separately. Wire according to the board revision in hand and the manufacturer’s guide. Access to the linked detailed user guide was restricted during research for this article. Obtain it before procurement, especially to confirm the image, partner and jumper steps. Design files have download entry points; check the actual file versions, terms of use and component availability before ordering as well.

TIDA-010261: resolve board fabrication and startup before connecting the actual sensor

The TIDMBP8 schematic, TIDMBP9 BOM and TIDUF34A design guide are directly available. Section 4 of the guide covers debug interfaces, startup and software preparation. Without a compatible link partner that supplies power, its auxiliary supply path allows data evaluation using an external 24 V, 0.5 A supply with a media converter that does not supply power over the link. This power condition applies only to that reference board. Hardware requirements §4.1

Include the software sections, design files and hardware-debugging conditions in the preparation checklist. BOM pricing alone does not represent the cost of completing this approach. Comparable board lead times, integration hours and complete bench quotations were not obtained for this article, so it does not rank total cost.

Sequence bench trials so that results can be explained

The following is a proposed trial sequence. Before use, fill in both endpoint boards, firmware, cable drawings, connection arrangements, application-data criteria and permitted component conditions. Use only power paths explicitly supported by the manufacturer. Switch configurations with power off, following the relevant guide.

The 1,000 m distance in CN0575 materials is associated with 2.4 Vpp mode. Using 2.4 Vpp also requires both endpoints to advertise support and negotiate it. The target cable’s power capability, connectors and environment remain separate validation tasks. CN0575 physical-interface and negotiation description

Record “indicator lit/link established,” “valid data received by the application” and “stable operation under the target power arrangement” separately. These are three different observations. If the short-link baseline does not work, check endpoint configuration, image/firmware, partner and wiring first, rather than immediately blaming the long cable. If an anomaly occurs only with power over the same pair, preserve and inspect power establishment, PD input and reset timing next. The symptom alone does not prove that cable voltage drop is the cause. Stop that trial condition if temperature rise is abnormal, a component exceeds its permitted conditions or wiring is uncertain, and investigate using the component and board documentation.

What should be checked next when an anomaly appears?

The following checks follow the B01–B04 comparisons. Use them to choose the next evidence to collect; symptoms alone cannot assign fault to a component or cable.

Handing these records and the untested scope to the next engineer supports a decision to continue, modify or add tests more effectively than a single “link connected” screenshot.

Plan and record files you can adapt directly

The bench-evaluation toolkit contains a bench plan and results sheet, a completed example plan and field instructions. The files place conditions, variables and result fields together, making it easier to retain failed conditions instead of capturing only one successful connection.

The example assumes a team with compatible endpoint devices comparing a 1 m baseline cable with a 20 m target cable and planning to check power over the same pair with power negotiation. These lengths are demonstration inputs, not recommended limits. Each example row specifies what changes, what stays constant and what to observe. Measured counts, voltages, reset counts and conclusions are all blank because no testing has been performed. Replace the devices and conditions, complete the documentation and criteria, and the plan can be handed to the person carrying out the trials.

You can define completion of this trial round as follows: every planned condition has a clear configuration and logs; failures lead to a next diagnostic check; power and data each have their own assessment; unverified environments, lengths and loads are listed separately. This result can support continuing the design, modifying it or stopping this approach. Production qualification, EMC, durability and final application acceptance require their own validation.

When preparing target-cable conditions, read the wire gauge and conductor selection guide. When organizing validation conclusions, read how to review a cable assembly test report.

Source versions: CN0575 Circuit Note Rev. A; TIDA-010261, design guide TIDUF34A (2025-08); manufacturer public materials accessed 2026-09-23. Confirm matching BOM, schematic and board versions for the actual setup. MTTJ used AI for research reading and editing. This article provides a document comparison and proposed trial tools; the two reference designs have not been physically reproduced for it.