Exergie/NeoECU-Hardware
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Initial CAN Physical Layer spec

Browse Source
This commit is contained in:
h3cx
2026-09-11 19:24:15 +02:00
parent f8d111ef5c
commit f97a2c6a6c
8 changed files with 394 additions and 8 deletions
Download Patch File Download Diff File Expand all files Collapse all files
Architecture/IO_ARCHITECTURE.md
+6 -3
View File
@@ -31,8 +31,9 @@ temperature and pressure sensors, and an external starter switch.
| Analogue outputs | Reserve 2 MCU/output paths | Future 0-5 V output capability; not a V1 requirement |
The provisional generic digital I/O counts are planning values, not a frozen
connector or pin budget. CAN and its physical layer are intentionally outside
the scope of this document.
connector or pin budget. CAN is defined separately in
[CAN_PHYSICAL_LAYER.md](IO_MODULES/CAN_PHYSICAL_LAYER.md); its final connector
pin allocation remains part of the overall STM32 and harness pin budget.
## Power-Domain Rules
@@ -259,4 +260,6 @@ included unless a future peripheral explicitly requires it.
components for generic digital inputs.
5. Select the STM32H747 package and complete a pin assignment that preserves
all timer, ADC, optional DAC, debug, and communications resources.
6. Define CAN and other communications interfaces separately.
6. Complete the CAN connector and STM32 pin allocation defined in
[CAN_PHYSICAL_LAYER.md](IO_MODULES/CAN_PHYSICAL_LAYER.md), alongside any
other required communications interfaces.