[bootlin/training-materials updates] master: labs/*beagleplay*: standard capitalization of mikroBUS (9c2f2500)

Michael Opdenacker michael.opdenacker at bootlin.com
Mon Aug 7 16:25:55 CEST 2023


Repository : https://github.com/bootlin/training-materials
On branch  : master
Link       : https://github.com/bootlin/training-materials/commit/9c2f2500d3c0cd3e84b8f578f22966dca922a996

>---------------------------------------------------------------

commit 9c2f2500d3c0cd3e84b8f578f22966dca922a996
Author: Michael Opdenacker <michael.opdenacker at bootlin.com>
Date:   Mon Aug 7 15:31:15 2023 +0200

    labs/*beagleplay*: standard capitalization of mikroBUS
    
    According to https://www.mikroe.com/mikrobus
    
    Signed-off-by: Michael Opdenacker <michael.opdenacker at bootlin.com>


>---------------------------------------------------------------

9c2f2500d3c0cd3e84b8f578f22966dca922a996
 .../sysdev-accessing-hardware-beagleplay.tex         | 20 ++++++++++----------
 .../sysdev-thirdparty-beagleplay.tex                 |  4 ++--
 2 files changed, 12 insertions(+), 12 deletions(-)

diff --git a/labs/sysdev-accessing-hardware-beagleplay/sysdev-accessing-hardware-beagleplay.tex b/labs/sysdev-accessing-hardware-beagleplay/sysdev-accessing-hardware-beagleplay.tex
index 837d9791..9dad543e 100644
--- a/labs/sysdev-accessing-hardware-beagleplay/sysdev-accessing-hardware-beagleplay.tex
+++ b/labs/sysdev-accessing-hardware-beagleplay/sysdev-accessing-hardware-beagleplay.tex
@@ -121,12 +121,12 @@ GPIOs are already in use:
 # cat /sys/kernel/debug/gpio
 \end{bashinput}
 
-We are going to use one of the MIKROBUS connector of the board,
+We are going to use one of the mikroBUS connector of the board,
 
 Take one of the M-M breadboard wires provided by your instructor and:
 \begin{itemize}
-  \item Connect one end to the \code{INT} pin of the \code{MIKROBUS} connector
-  \item Connect the other end to the \code{GND} pin of the \code{MIKROBUS} connector
+  \item Connect one end to the \code{INT} pin of the \code{mikroBUS} connector
+  \item Connect the other end to the \code{GND} pin of the \code{mikroBUS} connector
 \end{itemize}
 
 \includegraphics[width=\textwidth]{labs/sysdev-accessing-hardware-beagleplay/System-Block-Diagram.png}
@@ -141,7 +141,7 @@ or \code{RST} pin to do this lab, because there are all GPIOs.
 
 Now that we've selected our pin on the board, we need to know where it
 is connected on the SoC. To do so BeagleBoard.org provides us with the schematics
-of the Mikrobus header we are using:
+of the mikroBUS header we are using:
 
 \includegraphics[width=\textwidth]{labs/sysdev-accessing-hardware-beagleplay/mikroBUS1.png}
 {\small Source: \url{https://docs.beagleboard.org/latest/boards/beagleplay/03-design.html}}
@@ -266,7 +266,7 @@ it here.
 As shown on the earlier picture the BeaglePlay has 3 I2C
 busses available through different connectors:
 \begin{itemize}
-\item I2C3: available on the MIKROBUS connector
+\item I2C3: available on the mikroBUS connector
 \item I2C1: available on the Groove connector
 \item I2C2: available on the Qwic connector
 \end{itemize}
@@ -326,7 +326,7 @@ So, we are lucky that the first 4 Linux I2C names corresponds to the first 4
 datasheet names.
 
 In this lab we will be using the I2C3 bus to connect the nunchuk
-because it is located on the MIKROBUS connector and is easily
+because it is located on the mikroBUS connector and is easily
 accessible.
 
 However because this I2C controller is already enabled, we will
@@ -460,10 +460,10 @@ to the \busname\ bus on the board, using breadboard wires:
 \includegraphics[width=0.7\textwidth]{common/beagleplay-connect-nunchuk.jpg}
 
 \begin{itemize}
-\item Connect the Nunchuk PWR pin to \code{+3.3V} pin of MIKROBUS connector
-\item Connect the Nunchuk GND pin to \code{GND} pin of MIKROBUS connector
-\item Connect the Nunchuk SCL pin to \code{SCL} pin of MIKROBUS connector
-\item Connect the Nunchuk SDA pin to \code{SDA} pin of MIKROBUS connector
+\item Connect the Nunchuk PWR pin to \code{+3.3V} pin of mikroBUS connector
+\item Connect the Nunchuk GND pin to \code{GND} pin of mikroBUS connector
+\item Connect the Nunchuk SCL pin to \code{SCL} pin of mikroBUS connector
+\item Connect the Nunchuk SDA pin to \code{SDA} pin of mikroBUS connector
 \end{itemize}
 
 If you didn't do any mistake, your new device should be detected at
diff --git a/labs/sysdev-thirdparty-beagleplay/sysdev-thirdparty-beagleplay.tex b/labs/sysdev-thirdparty-beagleplay/sysdev-thirdparty-beagleplay.tex
index bf9e5f1a..a58d2745 100644
--- a/labs/sysdev-thirdparty-beagleplay/sysdev-thirdparty-beagleplay.tex
+++ b/labs/sysdev-thirdparty-beagleplay/sysdev-thirdparty-beagleplay.tex
@@ -678,8 +678,8 @@ $ aarch64-linux-strip target/usr/bin/gpio*
 
 \subsection{Testing libgpiod}
 
-First, connect \code{GPIO1_9} (\code{INT} pin of \code{MiCKROBUS} connector)
-connected to ground (\code{GND} pin of \code{MiCKROBUS} connector), as in the
+First, connect \code{GPIO1_9} (\code{INT} pin of \code{mikroBUS} connector)
+connected to ground (\code{GND} pin of \code{mikroBUS} connector), as in the
 {\em Accessing Hardware Devices} lab.
 
 Now, let's run the \code{gpiodetect} command on the target, and check that




More information about the training-materials-updates mailing list