doc: Fix spelling errors in .rst files
Fix spelling errors in assorted .rst files. The errors were found using a tool called 'codespell'. Signed-off-by: Aleksandar Markovic <aleksandar.markovic.sa@gmail.com>
This commit is contained in:
parent
83169f51af
commit
8a32b05905
23 changed files with 27 additions and 27 deletions
|
@ -247,7 +247,7 @@ Then build and flash an application. Here is an example for the
|
|||
|
||||
Run a serial host program to connect with your board:
|
||||
Per default the console on ``usart1`` is available on the USB Type C connector
|
||||
via the build-in USB to UART converter.
|
||||
via the built-in USB to UART converter.
|
||||
|
||||
.. code-block:: console
|
||||
|
||||
|
|
|
@ -401,7 +401,7 @@ Flashing
|
|||
:alt: SPI DONGLE ASSY 6791 Connected
|
||||
|
||||
|
||||
.. note:: If you dont't want to press Reset button every time, you can disconnect
|
||||
.. note:: If you don't want to press Reset button every time, you can disconnect
|
||||
SPI Dongle ASSY 6791 from the EVB during the west flash programming.
|
||||
Then connect it back to the ``J44`` header and apply power to the EVB.
|
||||
Result will be the same.
|
||||
|
|
|
@ -405,7 +405,7 @@ Flashing
|
|||
:align: center
|
||||
:alt: Reset Button
|
||||
|
||||
.. note:: If you dont't want to press Reset button every time, you can disconnect
|
||||
.. note:: If you don't want to press Reset button every time, you can disconnect
|
||||
SPI Dongle ASSY 6791 from the EVB during the west flash programming.
|
||||
Then connect it back to the ``J34`` header and apply power to the EVB.
|
||||
Result will be the same.
|
||||
|
|
|
@ -18,7 +18,7 @@ Ethernet series MCU with ARM® -Cortex®-M4F core.
|
|||
Features:
|
||||
=========
|
||||
- 32-bit Arm Cortex®-M4 M487JIDAE MCU
|
||||
- Core clock upto 192 MHz
|
||||
- Core clock up to 192 MHz
|
||||
- 512 KB embedded Dual Bank Flash and 160 KB SRAM
|
||||
- Audio codec (NAU88L25) with Microphone In and Headphone Out
|
||||
- Ethernet (IP101GR) for network application
|
||||
|
|
|
@ -328,7 +328,7 @@ Power supply testpoint
|
|||
| TP13 | testpoint | testpoint boost converter input voltage |
|
||||
+-------+-----------------------+-------------------------------------------+
|
||||
|
||||
Build-in Debug Adapter
|
||||
Built-in Debug Adapter
|
||||
======================
|
||||
|
||||
The debug adapter is based on the DAPLink interface firmware and
|
||||
|
|
|
@ -44,7 +44,7 @@ SensorTile.box provides the following hardware components:
|
|||
- 1 x USB OTG FS (SoC) with micro-B connector
|
||||
(USB device role only)
|
||||
|
||||
- Internal Busses
|
||||
- Internal Buses
|
||||
|
||||
- 3 x SPI bus
|
||||
- 3 x I2C bus
|
||||
|
@ -104,7 +104,7 @@ SensorTile.box System Clock could be driven by internal or external
|
|||
oscillator, as well as main PLL clock. By default, the System clock is
|
||||
driven by the PLL clock at 80MHz, driven by the 16MHz external oscillator.
|
||||
The system clock can be boosted to 120MHz.
|
||||
The internal AHB/APB1/APB2 AMBA busses are all clocked at 80MHz.
|
||||
The internal AHB/APB1/APB2 AMBA buses are all clocked at 80MHz.
|
||||
|
||||
Serial Port
|
||||
===========
|
||||
|
|
|
@ -59,7 +59,7 @@ Mode 1: Standard Mode
|
|||
=====================
|
||||
|
||||
In standard I2C mode the two buses are connected together. As a consequence, all devices on the shield
|
||||
reside on the same I2C bus and are accessible from the main board thru I2C bus.
|
||||
reside on the same I2C bus and are accessible from the main board through I2C bus.
|
||||
|
||||
The jumper configuration to activate this mode is:
|
||||
|
||||
|
@ -71,7 +71,7 @@ Mode 2: SensorHub Mode
|
|||
======================
|
||||
|
||||
In SensorHub mode LSM6DSL is connected to I2C2 and is accessible from the main board.
|
||||
All the other devices are connected to LSM6DSL master thru I2C1.
|
||||
All the other devices are connected to LSM6DSL master through I2C1.
|
||||
|
||||
The jumper configuration to activate this mode is:
|
||||
|
||||
|
|
|
@ -57,7 +57,7 @@ Mode 1: Standard Mode
|
|||
=====================
|
||||
|
||||
In standard I2C mode the two buses are connected together. As a consequence, all devices on the shield
|
||||
reside on the same I2C bus and are accessible from the main board thru I2C bus.
|
||||
reside on the same I2C bus and are accessible from the main board through I2C bus.
|
||||
|
||||
The jumper configuration to activate this mode is:
|
||||
|
||||
|
@ -69,7 +69,7 @@ Mode 2: SensorHub Mode
|
|||
======================
|
||||
|
||||
In SensorHub mode LSM6DSO and LIS2DW12 are connected to I2C2 and are accessible from the main board.
|
||||
All the other devices are connected to LSM6DSO master thru I2C1.
|
||||
All the other devices are connected to LSM6DSO master through I2C1.
|
||||
|
||||
The jumper configuration to activate this mode is:
|
||||
|
||||
|
|
|
@ -69,7 +69,7 @@ Mode 2: SensorHub Mode
|
|||
======================
|
||||
|
||||
In SensorHub mode ISM330DHCX and IIS2DLPC are connected to I2C2 and are accessible from the main board mcu.
|
||||
Instead, the IIS2MDC device is connected only to ISM330DHCX sensor thru its SCx/SDX (I2Cx) pins.
|
||||
Instead, the IIS2MDC device is connected only to ISM330DHCX sensor through its SCx/SDX (I2Cx) pins.
|
||||
|
||||
The jumper configuration to activate this mode is:
|
||||
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue