Updated Doxygen

This commit is contained in:
William Miceli
2021-02-16 21:28:01 -05:00
parent 5148ac3166
commit 80e2fdcd2f
530 changed files with 52222 additions and 186 deletions

View File

@@ -96,8 +96,20 @@ $(document).ready(function(){initNavTree('design_choices.html',''); initResizabl
JTAG Interface</h1>
<p>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.</p>
<h1><a class="anchor" id="autotoc_md3"></a>
Microcontroller Peripheral Connections</h1>
<p>Universal Serial Communication Interfaces (USCIs):</p>
Microcontroller Connections</h1>
<p>The board is going to be organized to the best of our abilities to be organized as such:</p>
<ul>
<li>Left Side:<ul>
<li>Peripherals for communicating with/controlling the Sunseeker vehicle</li>
</ul>
</li>
<li>Right Side:<ul>
<li>Peripherals for communicating with users</li>
</ul>
</li>
</ul>
<h4><a class="anchor" id="autotoc_md4"></a>
Universal Serial Communication Interfaces (USCIs):</h4>
<ul>
<li>A - Supporting up to four total of UART and/or SPI<ul>
<li>A0 [SPI]:<ul>
@@ -107,11 +119,11 @@ Microcontroller Peripheral Connections</h1>
</li>
<li>A1:</li>
<li>A2 [UART]:<ul>
<li>RS-232 Transceiver (STMicroelectronics ST232CDR)</li>
<li>USB to UART Bridge (Future Technology Devices International FT230XS-R)</li>
</ul>
</li>
<li>A3 [UART]:<ul>
<li>USB to UART Bridge (Future Technology Devices International FT230XS-R)</li>
<li>RS-232 Transceiver (STMicroelectronics ST232CDR)</li>
</ul>
</li>
</ul>
@@ -119,22 +131,23 @@ Microcontroller Peripheral Connections</h1>
<li>B - Supporting up to four total of I2C and/or SPI<ul>
<li>B0 [SPI]:<ul>
<li>SD Card</li>
<li>GPS Receiver (Maxim Integrated MAX2771ETI+T)</li>
<li>GPS Receiver (U-Blox NEO-M8Q-01A)</li>
</ul>
</li>
<li>B1 [SPI]:<ul>
<li>Bluetooth/Wi-Fi (Espressif Systems ESP32-WROVER-IE (8MB))</li>
</ul>
</li>
<li>B2 [I2C]:<ul>
<li>Inertial Measurement Unit (TDK InvenSense ICM-20600)</li>
<li>B1 [I2C]:<ul>
<li>Inertial Measurement Unit (TDK InvenSense ICM-20948)</li>
<li>Real-Time Clock/Calendar (Microchip Technology MCP7940MT-I/SN)</li>
</ul>
</li>
<li>B2:</li>
<li>B3 [SPI]:<ul>
<li>Bluetooth/Wi-Fi (Espressif Systems ESP32-WROVER-IE (8MB))</li>
</ul>
</li>
</ul>
<p>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. </p>
</li>
</ul>
<p>In addition to trying to keep the MCU and PCB organized with the left-side being to do with the Sunseeker vehicle and the right side to be peripherals interacting with users, we tried to also load-balance the USCI modules, as well as have the SPI protocol be 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. </p>
</div></div><!-- contents -->
</div><!-- PageDoc -->
</div><!-- doc-content -->
@@ -142,7 +155,7 @@ Microcontroller Peripheral Connections</h1>
<div id="nav-path" class="navpath"><!-- id is needed for treeview function! -->
<ul>
<li class="navelem"><a class="el" href="hardware.html">Hardware</a></li>
<li class="footer">Generated on Sat Feb 6 2021 19:02:29 for 2020-2021 Sunseeker Telemetry and Lighting System by <a href="https://www.doxygen.org/index.html"><img class="footer" src="doxygen.svg" width="104" height="31" alt="doxygen"/></a> 1.9.1 </li>
<li class="footer">Generated on Tue Feb 16 2021 21:27:07 for 2020-2021 Sunseeker Telemetry and Lighting System by <a href="https://www.doxygen.org/index.html"><img class="footer" src="doxygen.svg" width="104" height="31" alt="doxygen"/></a> 1.9.1 </li>
</ul>
</div>
</body>