Türkçe Yardım
Worked for 25 mins 34 sec
USB’nin MCU tarafı, doğru ESD pad hedeflenince bile tekil router’da yol bulamadı. Bu bağlantı için ya manuel trace çizimi/otomatik router gerekiyor ya da U1-D2-J6 yerleşimini daha agresif değiştirmek gerekiyor; kalan gücü/sinyali daha fazla bozmayacağım.Moruk başladım ve önemli kısmı netleştirdim:
- USB-B J6 → D2 ESD tarafında D+ / D- route edildi.
- DB25 tarafındaki bazı araç hatları daha önce çizilmiş durumda.
- Hatalı oluşan USB/GND deneme yollarını temizledim; kısa devre/dangling iz bırakmadım.
- D2’yi U1’e yaklaştırdım ama D2 → STM32 PA11/PA12 USB bacaklarında tekil router yol bulamadı.
Açık kalan:
- Kart hâlâ tamamen route edilmiş değil; airwire’lar devam ediyor.
- Özellikle USB ESD’den MCU’ya, bazı güç regülatörü lokal yolları ve kalan sinyal hatları için otomatik/toplu router veya manuel PCB trace düzenleme gerekiyor.
- Bu haliyle fiziksel görünümde yolların bir kısmı görünür ama baskıya hazır değil.
Sonraki en doğru adım:
- USB-B/D2/U1 çevresini biraz daha agresif yeniden yerleştirmek.
- Ardından USB D+/D-’yi kısa ve paralel olacak şekilde tekrar route etmek.
- Sonra güç yollarını ve kalan airwire’ları bitirmek.
Fix USB and route
Fix USB placement
Route power first
Finish remaining airwires
Run DRC after routing
Refine this doc
Ask about this doc
Project Specification
Project Overview
- Project: ECU Read Write Interface
- Status: Draft
- Purpose: USB-connected ECU read/write interface prototype for authorized diagnostics/programming of owned or permitted ECUs.
- Core interfaces: Classic CAN, K-Line, OBD-II, and bench harness connection.
Intended Use
- Connect to passenger cars, trucks, and heavy vehicles using 12 V or 24 V electrical systems.
- Support OBD-II in-vehicle access and bench/desktop ECU connection.
- Intended for legal/authorized ECU service, diagnostics, firmware backup, and firmware restore workflows.
What the Device Should Do
- Communicate with ECUs over classic CAN.
- Communicate with older ECUs over K-Line / ISO9141 / KWP2000 style physical layer.
- Connect to a PC over USB.
- Accept vehicle-side supply from 12 V and 24 V systems.
- Provide protected bench wiring access for ECU power, ground, CAN, and K-Line.
Main Features
- USB-C PC connection.
- MCU-based protocol bridge.
- Classic CAN transceiver.
- K-Line transceiver/interface.
- OBD-II 16-pin connector.
- Bench connector/header for ECU harness wiring.
- Automotive input protection for 9–32 V nominal operation.
- Reverse polarity, surge/load-dump, fuse, and ESD protection.
- Status LEDs and test points.
System Architecture
Diagram
Hardware Subsystems
Power Input and Protection
- Nominal vehicle support: 12 V and 24 V systems.
- Design target input range: 9–32 V continuous, with transient protection sized for automotive surges.
- Protection blocks: fuse/PTC, reverse-polarity protection, 36 V-class input TVS surge clamp, input filtering.
MCU / USB Bridge
- Selected MCU family: STM32G431, using a square LQFP SMD package where available.
- MCU needs USB device support, FDCAN/classic CAN controller support, UART for K-Line transceiver control, SWD debug, BOOT/NRST access, and enough GPIO for status/test features.
- USB-C used as PC interface and optional 5 V auxiliary input if needed.
CAN Interface
- Classic CAN physical layer, 3.3 V or 5 V logic-compatible transceiver.
- OBD-II CAN pins and bench CAN pins exposed.
- Switchable/optional 120 ohm termination planned for bench use.
K-Line Interface
- ISO9141/KWP2000 compatible K-Line physical layer.
- OBD-II K-Line pin and bench K-Line pin exposed.
- Protected against vehicle electrical transients.
Connectors
- OBD-II 16-pin connector.
- SMD bench connector with at least VBAT, GND, CANH, CANL, K-Line, and optional ignition/wake line.
Interfaces and Connections
Table
| Interface | Direction | Notes |
|---|---|---|
| USB-C | PC/device | Firmware update, data exchange, command/control |
| OBD-II CAN | Bidirectional | Classic CAN on standard OBD pins |
| OBD-II K-Line | Bidirectional | Older ECU access |
| Bench CAN | Bidirectional | Direct ECU bench harness |
| Bench K-Line | Bidirectional | Direct ECU bench harness |
| Vehicle VBAT | Input | 12/24 V nominal, 9–32 V design target |
| 3.3 V rail | Internal | MCU and logic rail |
Power and Runtime Expectations
- Primary power: vehicle/bench VBAT input.
- USB may provide data and optionally power for logic-only operation if needed in a later revision.
- No battery runtime requirement.
Power Tree and Power Budget
Initial estimate before final part selection:
Table
| Rail | Load | Typical | Peak |
|---|---|---|---|
| 3.3 V | STM32 MCU | 50 mA | 120 mA |
| 3.3 V | CAN transceiver logic | 10 mA | 30 mA |
| 3.3 V | K-Line interface logic | 5 mA | 20 mA |
| 3.3 V | LEDs/test support | 10 mA | 30 mA |
| 3.3 V total | Internal electronics | 75 mA | 200 mA |
Assumption: 3.3 V buck efficiency 85% at light/medium load.
- Peak output power: 3.3 V × 0.2 A = 0.66 W.
- Input current at 9 V worst case: 0.66 W / (9 V × 0.85) ≈ 86 mA.
- Protection and regulator should be sized with margin; target input path current rating at least 0.5 A.
Manufacturing and Assembly Expectations
- Prototype-intent PCB.
- All components should be SMD where a suitable library/current-production option exists.
- Prefer the largest practical SMD packages for manual rework: LQFP/TQFP for MCU, SOIC/PowerSOIC/HTSSOP for ICs, and 0805/1206-style passives where electrical performance allows.
- Avoid BGA, QFN/DFN, 0402/0201, and very tiny packages unless no practical alternative exists.
- Use active-production, currently available parts with distributor availability where possible.
- Avoid EOL, obsolete, and NRND components.
- Automotive connector and protection placement should prioritize robustness.
Firmware-Relevant Hardware Requirements
- USB device stack.
- CAN driver and ISO-TP/UDS-capable firmware architecture.
- UART/timer support for K-Line wakeup/communication.
- Boot/debug access via SWD.
- Status LEDs for power, USB, CAN activity, K-Line activity.
Physical Design Expectations
- OBD-II and bench connector accessible at board edge.
- Keep vehicle-side transient protection near connectors.
- Keep CAN pair short and routed as a pair.
- Provide test points for VBAT, 3.3 V, GND, CANH, CANL, K-Line, reset/SWD.
Important Design Decisions
- Use classic CAN, not CAN-FD, unless later requested.
- Include bench connection in addition to OBD-II.
- Design power input for both 12 V and 24 V vehicle systems.
- Use automotive-grade protection strategy rather than simple hobby-level input protection.
- Select currently available, non-obsolete parts.
- MCU changed from STM32H753ZIT6 to STM32G431 family, with square LQFP package preferred.
- Use SMD parts throughout, but choose hand-rework-friendly large SMD packages whenever possible.
Assumptions
- User wants a legitimate interface for owned/authorized ECU service.
- Initial scope excludes BDM/JTAG/boot-mode ECU programming adapters unless requested later.
- Classic CAN is sufficient for first revision.
- 9–32 V continuous input target is acceptable for 12/24 V vehicles; transient protection will be added separately.
Change Notes
- Initial requirement: ECU read/write interface.
- Added: classic CAN, K-Line, bench connection.
- Added: 12/24 V vehicle support for cars, trucks, and heavy vehicles.
- Added: active/currently available part selection requirement.
- Added: all-SMD but manual-rework-friendly package strategy.
- Changed MCU decision to STM32G431 LQFP-family device.
- Changed input TVS from 24 V class to 36 V class for 9–32 V continuous 12/24 V vehicle compatibility.
Project Overview
Intended Use
What the Device Should Do
Main Features
System Architecture
Hardware Subsystems
Power Input and Protection
MCU / USB Bridge
CAN Interface
K-Line Interface
Connectors
Interfaces and Connections
Power and Runtime Expectations
Power Tree and Power Budget
Manufacturing and Assembly Expectations
Firmware-Relevant Hardware Requirements
Physical Design Expectations
Important Design Decisions
Assumptions
Change Notes
