CANbus Modules are now connected
This commit is contained in:
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
@@ -0,0 +1 @@
|
||||
Change Component Designator: Old Designator=X? New Designator=X1
|
||||
@@ -0,0 +1 @@
|
||||
Change Component Designator: Old Designator=X? New Designator=X2
|
||||
File diff suppressed because one or more lines are too long
File diff suppressed because one or more lines are too long
@@ -6,9 +6,18 @@ When connecting the MCU to the programmer via the JTAG interface, it is possible
|
||||
|
||||
|
||||
|
||||
# Microcontroller Peripheral Connections
|
||||
# Microcontroller Connections
|
||||
|
||||
Universal Serial Communication Interfaces (USCIs):
|
||||
The board is going to be organized to the best of our abilities to be organized as such:
|
||||
|
||||
- Left Side:
|
||||
- Peripherals for communicating with/controlling the Sunseeker vehicle
|
||||
- Right Side:
|
||||
- Peripherals for communicating with users
|
||||
|
||||
|
||||
|
||||
#### Universal Serial Communication Interfaces (USCIs):
|
||||
|
||||
- A - Supporting up to four total of UART and/or SPI
|
||||
- A0 [SPI]:
|
||||
@@ -31,4 +40,4 @@ Universal Serial Communication Interfaces (USCIs):
|
||||
|
||||
|
||||
|
||||
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.
|
||||
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. In Texas Instruments SLAS655G Document [Page 7] has a pin diagram showing the physical location of where each pin is physically located.
|
||||
Reference in New Issue
Block a user