34 lines
1.1 KiB
Markdown
34 lines
1.1 KiB
Markdown
@page designChoices Design Choices
|
|
|
|
# JTAG Interface
|
|
|
|
When connecting the MCU to the programmer via the JTAG interface, it is possible for a local power supply connected to the MCU to be used or for power from the debugging/programming adapter to be used. Since having power supplied to the MCU from the debugging/programming adapter can be useful for use outside of the Sunseeker vehicle, we chose to use that.
|
|
|
|
|
|
|
|
# Microcontroller Peripheral Connections
|
|
|
|
Universal Serial Communication Interfaces (USCIs):
|
|
|
|
- A - Supporting up to four total of UART and/or SPI
|
|
- A0 [SPI]:
|
|
- CANbus Controller 1 (Primary)
|
|
- CANbus Controller 2 (Secondary)
|
|
- A1:
|
|
- A2 [UART]:
|
|
- RS-232 Transceiver
|
|
- A3 [UART]:
|
|
- USB to UART Bridge
|
|
- B - Supporting up to four total of I2C and/or SPI
|
|
- B0 [SPI]:
|
|
- SD Card
|
|
- GPS Receiver
|
|
- B1 [SPI]:
|
|
- Bluetooth/Wi-Fi
|
|
- B2 [I2C]:
|
|
- Inertial Measurement Unit
|
|
- Real-Time Clock/Calendar
|
|
|
|
|
|
|
|
The thinking behind this so far, is to try and balance the load between the modules with SPI protocol being used in more high data-rate peripherals and I2C used with lower or less-used peripherals. |