pin contention - TLE8888 + CS + BT

[rusefi]

TL,DR: do we have ANOTHER set of UART pins exposed on MRE not PC10&PC11?

How do we get MRE to

1. obviously keep using SPI for TLE8888
2. have different SPI for SD card
3. and also have UART for Bluetooth?

TLE8888 uses TBD pins which conveniently could be multiplexed to SPI1 or SPI3
SD card ideally should be running on a different SPI to reduce contention. We have complete SPI exposed which uses PC10&PC11

so if PC10 and PC11 is used by SPI for SD, do we have another pair of pins exposed on all the little random vias? if not, what would be the minimal HW change to have uart exposed without sharing pins with SPI?

[rusefi]

@ksmola since you did UART recently poke :)

[rusefi]

see table on the bottom of https://github.com/rusefi/rusefi/wiki/Hardware_microRusEfi_wiring

[rusefi]

[rusefi]

how about PB10 & PB11 which are used for SPI Flash right now? Does SPI use them simply as GPIO. We better use PE0 and PC13 for SPI Flash GPIO and PB10 & PB11 for UART

[jharvey]

I'm not following the request. Is this correct?
PB10 on SD card --> PE0 WP
PB11 on SD card --> PC13 HOLD
Then we want
PB10 to a via for UART via soldered wire
PB11 to a via for UART via soldered wire

[rusefi]

The request:
before the change PB10 PB11 were routed to SPI Flash (not SD card)
PE0 PC13 were available to outside world via VIAs

The request:
swap pin usage. use PE0 PC13 to control SPI Flash
make PB10 PB11 available to outside world via VIAs

@jharvey

[jharvey]

My key concern is if PE0 or PC13 should be connected to the flash traced called HOLD? I have committed a draft copy. Did I get the correct signal to the correct pin? If they are flipped does that matter? Is the PCB as it's drawn now correct and ready for MFG files?

[rusefi]

Does not matter which one is which, it's GPIO so full programmatic control

[jharvey]

Thanks for the verification. This is routed, so we can close it.

[rusefi]

Before the change, 0.5.1 and older

HOLD=PB11=UART3 RX
PB10=UART3 TX

@Abricosvw