rusefi / hw_microRusEfi

microRusEfi board for rusEfi ECU
66 stars 36 forks source link

test pads for TTL pins #119

Closed rusefi closed 4 years ago

rusefi commented 5 years ago

Low-probability scenario: remote tuning via a data modem, data modems probably prefer TTL RS232, can we expose test pads for one of stm32 uart devices?

DonaldBecker commented 5 years ago

In my layout I added a 2x5 pin SMD header that brought out pins that could be mapped.

5V 12V PB8 3.3V PC11 PD0 PA15 PC10 GND PC12

These can be mapped to: Pin Some interesting functions PB8 I2C1_SCL/CAN1_RX PC11 SPI3_MISO / UART4_RX/ USART3_RX PD0 CAN1_RX (Better would be PB9 I2C1_SDA/CAN1_TX) PA15 SPI3_NSS PC10 SPI3_SCK/ UART4_TX/ USART3_TX PC12 SPI3_MOSI/UART5_TX/ USART3_CK

My layout should be considered a proposal rather than a settled design. These are exactly the decisions that end up being "it would have been so much more useful if you made this minor change".

The intent was that this header could be used for a controlling a SPI device, adding serial communication over bluetooth or WiFi, or adding a SPI memory chip. Note that 8 of the pins directly map to a SPI flash pinout.

Obvious drawbacks:

The pads are for a 0.1" spaced header, which takes a bunch of room. Unlike the programming header there isn't a specific reason for this. A 0.05" / 1.27mm header would allow more pins or a smaller footprint. The header should be female or shrouded to avoid pins being exposed to accidental contact, especially as 12V is on a vulnerable outside edge.

DonaldBecker commented 4 years ago

For 0.4.6 I've updated the communication header pinout to use PB9 instead of PD0. This allows it to support I2C or CAN (I2C Ch2 or CAN Ch1)

5V 12V PB8 3.3V PC11 PB9 PA15 PC10 GND PC12

Pin Pin assignment options PB8 I2C1_SCL/CAN1_RX PC11 SPI3_MISO / UART4_RX/ USART3_RX PB9 I2C1_SDA/CAN1_TX PA15 SPI3_NSS PC10 SPI3_SCK/ UART4_TX/ USART3_TX PC12 SPI3_MOSI/UART5_TX/ USART3_CK

jharvey commented 4 years ago

This is obsolete, suggest closing this issue