boards/beagleplay/05-demos.rst

@@ -178,6 +178,7 @@ Demos and tutorials
     demos-and-tutorials/using-grove
     demos-and-tutorials/using-mikrobus
     demos-and-tutorials/using-qwiic
+    demos-and-tutorials/using-nodered
     demos-and-tutorials/using-rtc
     demos-and-tutorials/using-oldi
     demos-and-tutorials/using-csi
@@ -185,4 +186,4 @@ Demos and tutorials
     demos-and-tutorials/beagleplay-kernel-development
     demos-and-tutorials/greybus-host
     demos-and-tutorials/understanding-boot
-    demos-and-tutorials/using-nodered
+    demos-and-tutorials/low-power-video-doorbell

boards/beaglev/ahead/02-quick-start.rst

@@ -111,6 +111,7 @@ Flashing eMMC
 **************
 
 .. note:: To flash your BeagleV Ahead you need either a super-speed micro-B or high-speed micro-B cable as shown in section above.
+    This cable is not included in the box and must be purchased separately.
 
 Download latest software image
 ===============================
@@ -204,8 +205,9 @@ Access UART debug console
 **************************
 
 .. note:: It has been noticed that 6pin FTDI cables like `this <https://www.adafruit.com/product/70>`_ 
-    doesn't seem work with BeagleV Ahead debug port and there might be other cables/modules that will 
-    show garbage when connected to the board. 
+    doesn't seem work with BeagleV Ahead debug port and there might be other cables/modules based on PL2303
+    which give garbage values in the serial port. It is recommended to use the below listed modules for
+    accessing the UART debug console.
     
     Some tested devices that are working good includes:
 

boards/beagley/ai/01-introduction.rst

@@ -96,7 +96,7 @@ Board components location
 Front components
 =================
 
-.. figure:: images/components-location/front.*
+.. figure:: images/components-location/beagley-ai-board-front-annotated.*
     :width: 1400
     :align: center
     :alt: BeagleY-AI board front components location 
@@ -143,7 +143,7 @@ Front components
 Back components
 ================
 
-.. figure:: images/components-location/back.*
+.. figure:: images/components-location/beagley-ai-board-back-annotated.*
     :width: 1400
     :align: center
     :alt: BeagleY-AI board back components location 

boards/beagley/ai/03-design.rst

@@ -110,13 +110,17 @@ USB-C Power/Data Port
 
     BeagleY-AI USB-C
 
-The board is primarily intended to be powered via USB-C. PD Power negotiation is not done dynamically but rather
-by tying the CC lines to GND via 5.1KΩ resistors to indicate to the PD Source that the device requires 5V 3A. 
-Using USB-PD power supplies rated for higher wattages is safe as they will always negotiate to the 5V 3A requested by the board. 
 
-The USB-C port is configured by default to also show up as a USB2.0 Device which exposes a serial console, ethernet gadget (for connection sharing) as well as MTP (Flash Drive)
-so that only one cable is required to use the board. A Type-C to Type-C cable and avoiding un-powered USB hubs is recommended due to
-the board's power consumption requirements. Inadequate behavior may result in brownouts/resets or other unexpected behavior. 
+The board is powered via USB-C, using 5.1 kΩ resistors to signal itself as a power sink (UFP) and enable 5V output.
+It assumes 500 mA by default (per USB-C’s "Power Sinking Device" rules) but requires 5V @ 3A for stable operation. 
+The USB-C source dictates available current (via CC-line signaling), which the board does not validate. Users must 
+ensure their charger explicitly supports 3A. While USB-PD supplies default to 5V, they may not deliver 3A unless the 
+source advertises it, risking instability or port damage if undersourced.
+
+The USB-C port also functions as a USB 2.0 device, providing serial console access, Ethernet gadget connectivity, 
+and USB Mass Storage (UMS) emulation. A Type-C to Type-C cable is recommended to avoid power limitations, and 
+unpowered hubs should be avoided. single-cable design simplifies connectivity but relies on proper power sourcing.
+Inadequate behavior may result in brownouts/resets or other unexpected behavior. 
 
 PMIC
 ----------------

boards/beagley/ai/05-demos.rst

@@ -6,8 +6,6 @@ Demos and tutorials
 .. toctree::
    :maxdepth: 1
 
-.. todo:: Isn't including "beagley-ai" in the filename superfluous?
-
    demos/beagley-ai-using-gpio
    demos/beagley-ai-using-pwm
    demos/beagley-ai-using-rtc

boards/capes/index.rst

@@ -49,7 +49,8 @@ Find the instructions below on using each cape:
    :maxdepth: 2
    :hidden:
 
-   /boards/capes/cape-interface-spec
-   /boards/capes/relay
-   /boards/capes/comms
+   cape-interface-spec
+   relay
+   comms
+   motor_cape
 

boards/pocketbeagle-2/01-introduction.rst

@@ -67,7 +67,7 @@ description of the major components and interfaces that make up the board.
    +=========================+=========================================================================================================================================+
    | **Processor**           | `Texas Instruments AM6232 <https://www.ti.com/product/AM623>`_                                                                          |
    +-------------------------+-----------------------------------------------------------------------------------------------------------------------------------------+
-   | **SDRAM Memory**        | LPDDR4 3200MHz (512MB) Kingston D2516AN9EXGXN-TU                                                                                        |
+   | **SDRAM Memory**        | 512MB DDR4 (Kingston D2516AN9EXGXN-TU)                                                                                                  |
    +-------------------------+-----------------------------------------------------------------------------------------------------------------------------------------+
    | **PMIC**                | TPS6521903                                                                                                                              |
    +-------------------------+-----------------------------------------------------------------------------------------------------------------------------------------+

boards/pocketbeagle-2/02-quick-start.rst

@@ -92,26 +92,193 @@ Once the flashing is done, you will see the following screen.
 
 Your microSD card is now ready to boot PocketBeagle 2.
 
-Methods of operation
-*********************
-
-1.  Directly tethered to a PC via USB-C port.
-2.  With TechLab Cape for sesors, USB host, LEDs and Buttons.
-
-.. todo:: add link to TechLab Cape
-
 .. _pocketbeagle-2-main-connection-scenarios:
 
 Main Connection Scenarios
-============================
+*************************
 
 This section describes how to connect and power the board and serves as a slightly more detailed 
-description of the Quick Start Guide included in the box. The board can be configured in several 
+description of the quick start guide included in the box. The board can be configured in several 
 different ways, but we will discuss the two most common scenarios.
 
-* Tethered to a PC via the USB cable  
-* Attached to a cape like TechLab Cape
+1.  Directly tethered to a PC via pocketbeagle 2 USB-C port.
+2.  With `TechLab Cape <https://www.beagleboard.org/boards/techlab>`_ or `GamePup Cape <https://www.beagleboard.org/boards/pocketbeagle-gamepup-cape>`_  for sensors, USB host, LEDs and Buttons.
+
+.. _pocketbeagle-2-tethered-scenario:
+
+Tethered Connection
+====================
+
+In this scenario, the board is directly connected to a PC via USB-C port. This is the simplest way to get started with the board.
+Optionally you can connect rpi debug probe to 3-pin JST-SH connector to see boot log, board console access and for general debugging.
+
+
+.. figure:: images/connection-diagrams/tethered-connection.*
+   :align: center
+   :alt: Tethered Connection
+
+   Tethered Connection
+
+USB connection
+---------------
+
+1. Connect the USB-C cable to the PocketBeagle 2 and the other end to the PC.
+2. The board will power up and boot from the microSD card.
+3. The board will show up as a USB device on the PC.
+4. You can access the board via ``SSH`` or board ``serial`` connection or though ``Visial Studio Code Server`` web interface.
+
+.. tab-set::
+   .. tab-item:: Visial Studio Code Server
+
+      After connecting the board to the PC, you can access the board via a web browser by entering the IP address of the board in the address bar.
+
+      .. code-block:: text
+
+         https://192.168.7.2:3000/
+
+      .. figure:: images/misc/vscode-server.png
+         :align: center
+         :alt: Visual Studio Code Server
+
+         Visual Studio Code Server
+
+   .. tab-item:: SSH
+
+      After connecting the board to the PC, you can access the board via SSH executing the following command in your terminal.
+
+      .. code-block:: bash
+
+         ssh <username>@192.168.7.2
+
+      Where ``<username>`` is the username you selected during the microSD card flashing process.
+
+      .. figure:: images/misc/ssh-connection.png
+         :align: center
+         :alt: SSH connection
+
+         SSH connection
+
+   .. tab-item:: Serial
+
+      PocketBeagle 2 has a built-in UART debug connection. You can connect to the board console using a serial 
+      console application (e.g. Putty) on the PC just like your would connection using any external UART debug probe
+
+      If PocketBeagle 2 is the old device connected with UART, on linux you can use `tio` utility, replace ``ttyACMx`` with the actual device name.
+
+      .. code-block:: bash
+
+         tio /dev/ttyACMx
+
+      .. figure:: images/misc/serial-connection.png
+         :align: center
+         :alt: Serial connection
+
+         Serial connection
+
+Once you have access to the console using any of the methods above, you might want to share interne connection with the board.
+You can do this by running ``pb2-internet.sh`` file on your PocketBeagle 2 board. and the follow OS specific steps to share internet connection.
+
+First you have to create ``pb2-internet.sh`` file on PocketBeagle 2 with the following content,
+
+.. code-block:: bash
+
+   #!/bin/sh -e
+   #
+
+   if ! id | grep -q root; then
+           echo "must be run as root"
+           exit
+   fi
+
+   if [ -f /etc/default/bb-boot ] ; then
+           . /etc/default/bb-boot
+   fi
+
+   if [ "x${USB_CONFIGURATION}" = "x" ] ; then
+           USB0_SUBNET=192.168.7
+           DNS_NAMESERVER=8.8.8.8
+   fi
+
+   /sbin/route add default gw ${USB0_SUBNET}.1 || true
+
+   ping -c1 ${DNS_NAMESERVER}
+   echo "nameserver ${DNS_NAMESERVER}" >> /etc/resolv.conf
+
+   #
+
+then execute following commands,
+
+.. code-block:: bash
+
+   chmod +x pb2-internet.sh
+   sudo ./pb2-internet.sh
+
+On PC you have to follow OS specific steps to share internet connection with the board.
+
+.. tab-set::
+
+   .. tab-item:: Linux
+
+      First you have to identify your WiFi interface name and PocketBeagle 2 Ethernet interface name using following command,
+
+      .. code-block:: bash
+
+         ip a
+
+      If you have your WiFi connected to router and PB2 connected to one of the USB the you should see four interfaces listed
+
+      - 1: lo
+      - 2: wlp0s20f3
+      - 3: enp0s20f0u2
+      - 4: enp0s20f0u2i2
+
+      Out of which ``wlp0s20f3`` is the WiFi interface and ``enp0s20f0u2`` is the PocketBeagle 2 Ethernet interface. 
+      
+      Once you know the interface names, you have to create ``pc-internet.sh`` file on PC with the following content,
+
+      .. code-block:: bash
+
+         sudo sysctl net.ipv4.ip_forward=1
+         sudo iptables --table nat --append POSTROUTING --out-interface wlp0s20f3 -j MASQUERADE
+         sudo iptables --append FORWARD --in-interface enp0s20f0u1 -j ACCEPT
+
+      make sure to update line 2 and 3 with your WiFi and PocketBeagle 2 Ethernet interface names. Then execute following commands,
+
+      .. code-block:: bash
+
+         chmod +x pc-internet.sh
+         sudo ./pc-internet.sh
+
+   .. tab-item:: Windows
+
+      .. todo:: Add steps to share internet connection on Windows
+
+   .. tab-item:: MacOS
+
+      .. todo:: Add steps to share internet connection on MacOS
+
+UART serial debug connection
+----------------------------
+
+1. Connect the rpi debug probe to the 3-pin JST-SH connector on the board.
+2. Connect the other end of the probe to the PC.
+3. Use command line utility like `tio` with default setting or a serial console application (e.g. Putty) to accress your board.
+4. You will see the boot log and can access the board console.
+
+.. figure:: images/misc/serial-debug.png
+   :align: center
+   :alt: Serial debug
+
+   Serial debug
+
+.. _pocketbeagle-2-cape-scenario:
+
+Cape Connection
+================
 
-.. todo:: Add connection information in detail
+In this scenario, the board is connected to a cape like `TechLab Cape <https://www.beagleboard.org/boards/techlab>`_ 
+or `GamePup Cape <https://www.beagleboard.org/boards/pocketbeagle-gamepup-cape>`_. This is the most common way to 
+use the board for sensor interfacing, USB host, LEDs and Buttons. 
 
+.. todo:: Add cape connection diagram and steps to use examples.