This commit is contained in:
Aiden
2026-05-14 00:58:14 +10:00
parent 861b16118c
commit 2ab54be5ec
44 changed files with 3012 additions and 1 deletions

View File

@@ -118,6 +118,99 @@ Useful implication:
- `CN1` is now the strongest candidate for the board-side harness/IO connector
that should be traced against the external 10-pin cable assembly
### `CN1` Continuity Mapping
Based on your continuity tracing and the board silkscreen numbering:
| `CN1` pin | Observed function | Internal wire color | External 10-pin |
| --- | --- | --- | --- |
| `1` | `VBS (X) IN` | white | pin `2` |
| `2` | `VBS (G) IN` | blue | pin `3` |
| `3` | data ground | grey | pin `5` |
| `4` | data `RCP -> CCU` | yellow | pin `4` |
| `5` | data `CCU -> RCP` | orange | pin `7` |
| `6` | data ground | brown | pin `6` |
| `7` | ground | black | pin `9` |
| `8` | `DC+` | red | pin `10` |
Important observations:
- `CN1` pin `7` is the main ground path and maps to external pin `9`
- `CN1` pin `8` is DC power and maps to external pin `10`
- the serial pair is now clearly confirmed at the board level:
- `CN1` pin `4` / external pin `4` = `RCP -> CCU`
- `CN1` pin `5` / external pin `7` = `CCU -> RCP`
- there are **two additional non-serial signal inputs** on external pins `2`
and `3`
- there are **two separate data-ground/return lines** on external pins `5` and
`6`
Very important electrical note from tracing:
- the two data-ground lines (`CN1` pins `3` and `6`) were observed as **not
connected to common ground**
That strongly suggests the connector is not just:
- power
- one TX line
- one RX line
Instead, it likely carries a mixed signal set with at least:
- analog/video-related inputs
- serial/control
- separate signal returns
- power/common ground
Refined grounding observation:
- the separate data grounds appear to connect to common ground **through small
ceramic capacitors** near the connector
- the relevant parts are labeled:
- `C55`
- `C56`
This changes the interpretation from "totally isolated grounds" to something
more like:
- DC-isolated or not directly hard-tied
- but AC-coupled / noise-referenced to common ground
That is a very plausible arrangement for:
- signal-return noise control
- EMI filtering
- keeping the data pair referenced without fully hard-bonding the return paths
### Manual Cross-Check: External Connector Signals
The manual fragment for the external connector aligns very strongly with the
continuity map we traced:
| External pin | Manual signal | Notes |
| --- | --- | --- |
| `1` | `(SPARE)` | matches the fact that it has not appeared on `CN1` |
| `2` | `VBS (X) IN` | manual notes `1.0 Vp-p, sync negative` |
| `3` | `VBS (G) IN` | confirms a second VBS input line |
| `4` | `S. DATA (RCP -> CCU)` | matches traced serial-out line |
| `5` | `S. DATA GND` | matches traced separate data ground |
| `6` | `S. DATA GND` | matches traced separate data ground |
| `7` | `S. DATA (CCU -> RCP)` | matches traced serial-in line |
This is a strong confirmation that the harness tracing is fundamentally right.
Big implication:
- `VBS (X) IN` and `VBS (G) IN` are not mystery wires anymore
- they are documented inputs and are likely meaningful to normal panel
operation
- the wake/session problem may therefore depend on more than serial traffic,
although board-level routing now suggests that may vary by revision/options
The manual wording also strengthens the idea that these are likely
video/reference-style inputs rather than general-purpose logic lines.
### H8 / DIP Area
- the H8 marking is now clearly readable in-package as:
@@ -163,6 +256,117 @@ Working interpretation:
- nearby resistor-network and option-footprint areas also fit the picture of a
configurable CPU/control board with variant population options
### Serial Interface Confirmation
Tracing from the connector into the board:
- external pin `4` / `CN1` pin `4` goes to a `MAX202` device at package pad
`14`
- external pin `7` / `CN1` pin `5` goes to the same `MAX202` device at package
pad `13`
- no other `CN1` pins were observed going to that `MAX202`
Observed marking on the interface chip:
- `MAX202`
- `CSE 0107`
Interpretation:
- this is a very strong confirmation that the PT2 serial path is carried as a
real RS-232-style interface through a dedicated line transceiver
- it also strongly implies the other connector lines (`1`, `2`, `3`, `6`) are
**not** just extra serial handshake pins to the same interface chip
- the wake/session problem may therefore involve:
- analog/video sense inputs
- separate return/reference behavior
- or higher-level protocol/state expectations beyond the RS-232 channel alone
Refined serial-ground read:
- because the two `S. DATA GND` lines are capacitor-coupled to common ground,
the serial interface likely expects a somewhat cleaner/dedicated return
structure than a naive "everything tied straight together" hookup
- this does **not** by itself explain the missing wake/session behavior
- but it does support the idea that Sony treated the remote link as a proper
interface with controlled grounding rather than as a casual single-ground
wiring bundle
### Important Open Electrical Discrepancy
The manual fragment for external pin `7` appears to describe:
- `Zi >= 10 kohm`
- high/open state around `4.5 +/- 0.5 V`
- low state around `0 +/- 0.5 V`
That does **not** read like a classic bipolar RS-232-level description.
But the board tracing currently shows external pin `7` going into the `MAX202`
at pad `13` (`R1IN` on a standard MAX202 pinout), while external pin `4` goes
to pad `14` (`T1OUT`).
So there is now a real discrepancy to resolve:
1. the manual signal description for pin `7` looks logic/open style
2. the board tracing looks like an RS-232 transceiver path
Possible explanations to keep open for now:
- the manual fragment may describe behavior at a different system boundary or
for a slightly different revision/context
- the Sony interface may be electrically unusual despite using a `MAX202`
- there may be surrounding circuitry affecting how the line behaves at the
connector
For now, the safest conclusion is:
- the signal names are strongly confirmed
- the exact electrical behavior still needs reconciliation
### Board Construction / Routing Note
- The board appears to be a **2-layer PCB**
- Components are populated on only **one side**
- With transmitted light, traces appear visible on the opposite side, with no
obvious evidence of hidden inner layers
This matters because it makes visual trace-following more trustworthy and makes
the connector routing conclusions stronger.
### VBS Routing Observation
New tracing observation:
- `VBS (X) IN` and `VBS (G) IN` do **not** appear to run into the CPU/serial
section directly
- instead, they route to the side of the board toward an **empty connector
position labeled `CN5`**
- the only other obvious trace associated with that area appears to be ground
Working interpretation:
- the VBS lines may be routed primarily to an **unpopulated optional connector
or daughterboard position**
- this could mean:
- the TX7 PCB was designed for a variant that used the VBS signals more
directly
- this particular board revision does not currently use them in the populated
build
- or the signals are simply passed through / made available without deep
local processing
Why this matters:
- this weakens the earlier "VBS is definitely the missing wake input" theory
- it does **not** eliminate it completely
- but it does suggest the most immediate wake/session logic is still more likely
to live in:
- the serial path
- the DIP/boot configuration
- optional/unpopulated variant circuitry
- or retained configuration in NVRAM/firmware
## Additional Silkscreen / Board Markings
Observed so far:
@@ -571,3 +775,36 @@ Only if something changes meaningfully, then test:
useful result.
- If one setting produces a dramatically different boot state, stop and record
it before going wider.
## DIP Switch First-Pass Results
The first single-bit sweep produced a useful answer:
- the DIP switches are **not** inert
- but they do **not** seem to act like a blunt "service mode on/off" in the
simplest sense
What changed visibly:
- user reported that the first tested DIP setting briefly showed a **small
cursor on the LCD**
- the other single-bit settings looked the same visually
What changed serially:
- `S3-1` shifted the `A0 -> 90` startup family from:
- `07 80 64 40 30 C9`
to:
- `07 80 E4 40 30 49`
- `S2-3` suppressed the `A0 -> 90` branch entirely in the first pass
- `S2-1` left `A0 -> 90` alive but appears to have flattened `A0 -> AF`
Best current hardware interpretation:
- the DIP banks very likely participate in **startup personality / mode
selection**
- they may not directly control "active vs inactive panel"
- but they clearly can steer which startup-family surface the firmware exposes
This is consistent with the earlier suspicion that `S2` + `S3` form a boot-time
configuration byte rather than casual front-panel options.