Squashed commit of the following:

commit 4ab3ff82
Author: Jason Kridner <jkridner@beagleboard.org>
Date:   Tue Oct 25 21:38:16 2022 -0400

    More spelling fixes

commit fce576ba
Author: Jason Kridner <jkridner@beagleboard.org>
Date:   Tue Oct 25 13:52:28 2022 -0400

    Fixed a bunch of spelling and linking errors

commit 185218ee
Merge: 39c2dd78 c3b7fb7f
Author: Jason Kridner <jkridner@beagleboard.org>
Date:   Mon Oct 24 13:58:46 2022 -0400

    Merge branch 'main' of git.beagleboard.org:docs/docs.beagleboard.io

commit 39c2dd78
Author: Jason Kridner <jkridner@beagleboard.org>
Date:   Mon Oct 24 13:54:54 2022 -0400

    books/pru-cookbook/code: fix some spelling issues

commit c3de7ef6
Author: Jason Kridner <jkridner@beagleboard.org>
Date:   Mon Oct 24 13:44:15 2022 -0400

    books/pru-cookbook: fix references to code

commit c4a51c22
Author: Jason Kridner <jkridner@beagleboard.org>
Date:   Mon Oct 24 12:18:03 2022 -0400

    books/pru-cookbook: move code to submodule

.gitmodules

 [submodule "books/beaglebone-cookbook/code"]
 	path = books/beaglebone-cookbook/code
 	url = https://git.beagleboard.org/beagleboard/beaglebone-cookbook-code.git
+[submodule "books/pru-cookbook/code"]
+	path = books/pru-cookbook/code
+	url = https://git.beagleboard.org/beagleboard/pru-cookbook-code

boards/beaglebone/ai-64/ch04.rst

@@ -27,7 +27,7 @@ BeagleBone AI-64 is manufactured and warranted by partners listed at https://bea
 * Mark Yoder, professor at Rose-Hulman Institute of Technology
 * Kathy Giori, product engineer at ZEDEDA
 
-See `bbb.io/about <bbb.io/about>`_
+See `bbb.io/about <https://beagleboard.org/about>`_
 
 BeagleBone AI-64 has been designed by Seeed Studio (Seeed Development Limited) under guidance from BeagleBoard.org Foundation.
 

boards/beaglebone/ai-64/ch07.rst

@@ -35,7 +35,7 @@ The **GPIO** row is the expected gpio identifier number in the Linux
 kernel. 
 
 Each row includes the gpiochipX and pinY in the format of 
-`X Y`. You can use these values to direcly control the GPIO pins with the 
+`X Y`. You can use these values to directly control the GPIO pins with the 
 commands shown below.
 
 .. code::

boards/beaglebone/ai-64/ch11.rst

@@ -11,7 +11,7 @@ All support for this design is through BeagleBoard.org community at: link: `Beag
 Hardware Design
 ------------------
 
-You can find all BeagleBone AI-64 hardware files `here <https://git.beagleboard.org/beagleboard/beaglebone-ai-64/-/tree/master/hw>`_ .
+You can find all BeagleBone AI-64 hardware files `here <https://git.beagleboard.org/beagleboard/beaglebone-ai-64>`_ under the `hw` folder.
 
 
 .. _software-updates:

boards/beaglebone/ai/ch12.rst

@@ -30,6 +30,7 @@ the equipment.
 This Class A or B digital apparatus complies with Canadian ICES-003.
 Changes or modifications not expressly approved by the party responsible
 for compliance could void the user’s authority to operate the equipment.
+
 Cet appareil numérique de la classe A ou B est conforme à la norme
 NMB-003 du Canada. Les changements ou les modifications pas expressément
 approuvés par la partie responsible de la conformité ont pu vider

boards/beaglebone/black/ch07.rst

@@ -1175,7 +1175,11 @@ Serial cable is recommended as shown in *Figure 55* below.
 
 The cable can be purchased from several different places and must be the
 3.3V version TTL-232R-3V3. Information on the cable itself can be found
-direct from FTDI at: `pdf <http://www.ftdichip.com/Support/Documents/DataSheets/Cables/DS_TTL232R_CABLES.pdf>`_
+direct from FTDI at: `pdf <https://ftdichip.com/wp-content/uploads/2020/07/DS_USB_RS232_CABLES.pdf>`_
+
+.. note:
+
+   #TODO#: move accessory links to a single common document for all boards.
 
 Pin 1 of the cable is the black wire. That must align with the pin 1 on
 the board which is designated by the white dot next to the connector on
@@ -1183,7 +1187,7 @@ the board.
 
 Refer to the support WIKI `http://elinux.org/BeagleBoneBlack <http://elinux.org/BeagleBoneBlack>`_ for more sources of this cable and other options that will work.
 
-Table is the pinout of the connector as reflected in the schematic. It is the same as the FTDI cable which can be found at `http://www.ftdichip.com/Support/Documents/DataSheets/Cables/DS_TTL-232R_CABLES.pdf <http://www.ftdichip.com/Support/Documents/DataSheets/Cables/DS_TTL-232R_CABLES.pdf>`_ with the exception that only three pins are used on the board. The pin numbers are defined in *Table 14*. The signals are from the perspective of the board.
+Table is the pinout of the connector as reflected in the schematic. It is the same as the FTDI cable which can be found at `https://ftdichip.com/wp-content/uploads/2020/07/DS_USB_RS232_CABLES.pdf <https://ftdichip.com/wp-content/uploads/2020/07/DS_USB_RS232_CABLES.pdf>`_ with the exception that only three pins are used on the board. The pin numbers are defined in *Table 14*. The signals are from the perspective of the board.
 
 .. list-table:: J1 Serial Header Pins
    :header-rows: 1

boards/beaglebone/blue/accessories.rst

@@ -3,6 +3,10 @@
 Accessories 
 ###############
 
+.. note::
+
+   #TODO#: We are going to work on a unified accessories page for all the boards and it should replace this.
+
 .. _chassis_and_kits:
 
 Chassis and kits
@@ -251,7 +255,8 @@ I2C devices
 ==============
 
 -  See
-   `One-Liner-Module-Tests#Grove_I2C_modules <One-Liner-Module-Tests#Grove_I2C_modules>`__
+   :ref:`One-Liner-Module-Tests#i2c <beaglebone-blue-one-liner-tests>`__
+-  See :ref:`bone101_i2c`.
 
 .. _uart_devices:
 

boards/beaglebone/blue/tests.rst

@@ -9,7 +9,7 @@ ADC
 -  `Grove Rotary Angle
    Sensor <http://wiki.seeed.cc/Grove-Rotary_Angle_Sensor/>`__
    See output on adc_1
-   `source <https://github.com/StrawsonDesign/Robotics_Cape_Installer/blob/master/examples/rc_test_adc/rc_test_adc.c>`__
+   `source <https://git.beagleboard.org/beagleboard/librobotcontrol/-/blob/v1.1/examples/src/rc_test_adc.c>`__
 
 .. code:: bash
 

boards/beagleconnect/freedom/zephyr.rst

@@ -127,7 +127,7 @@ Other systems
 Log into BeagleBone Green Gateway
 =================================
 
-These instructions assume an x86_64 computer runing Ubuntu 20.04.3 LTS, but any
+These instructions assume an x86_64 computer running Ubuntu 20.04.3 LTS, but any
 computer can be used to connect to your BeagleBone Green Gateway.
 
 #. Log onto the Seeed BeagleBone® Green Gateway using :code:`ssh`.

boards/pocketbeagle/original/ch06.rst

@@ -195,8 +195,7 @@ Additional documentation is located on the Texas Instruments website at
 and also located at
 `http://github.com/beagleboard/am335x_pru_package. <http://github.com/beagleboard/am335x_pru_package>`__
 
-Example projects using the PRU-ICSS can be found at
-`processors.wiki.ti.com/index.php/PRU_Projects <http://processors.wiki.ti.com/index.php/PRU_Projects>`__.
+Example projects using the PRU-ICSS can be found in :ref:`pru-cookbook-home`.
 
 .. _pru_icss_features:
 
@@ -313,4 +312,4 @@ chart separately.
     | P2.34       | PRU0_5      | C13             | B3        |                              |                           | pr1_pru0_pru_r30_5 (Output)  | pr1_pru0_pru_r31_5 (Input)    |                                              |
     +-------------+-------------+-----------------+-----------+------------------------------+---------------------------+------------------------------+-------------------------------+----------------------------------------------+
     | P2.35       | A5/86       | U5              | F3        |                              |                           | pr1_pru1_pru_r30_8 (Output)  | pr1_pru1_pru_r31_8 (Input)    |                                              |
-    +-------------+-------------+-----------------+-----------+------------------------------+---------------------------+------------------------------+-------------------------------+----------------------------------------------+
\ No newline at end of file
+    +-------------+-------------+-----------------+-----------+------------------------------+---------------------------+------------------------------+-------------------------------+----------------------------------------------+

books/beaglebone-cookbook/01basics/basics.rst

@@ -313,7 +313,7 @@ This shows you a list of dates of the most recent Debian images (:ref:`basics_de
    Latest Debian images
 
 At the time of writing, we are using the *Bullseye* image.  
-Click on it's link. Scrolling up you'll find :ref:`basics_deb2`. 
+Click on its link. Scrolling up you'll find :ref:`basics_deb2`. 
 There are three types of snapshots, Minimal, IoT and Xfce Desktop. 
 IoT is the one we are running.
 

books/beaglebone-cookbook/02sensors/sensors.rst

@@ -684,7 +684,7 @@ tools to test the device. Because these are Linux command-line tools,
 you have to use *2* as the bus number. *i2cdetect*, shown in :ref:`js_i2cTools`, 
 shows which |I2C|  devices are on the bus. The *-r* flag indicates which bus to use. 
 Our TMP101 is appearing at address *0x498*. You can use the *i2cget* command to read 
-the value. It returns the temperature in hexidecimal and degrees C. 
+the value. It returns the temperature in hexadecimal and degrees C. 
 In this example, 0x18 = 24{deg}C, which is 75.2{deg}F. (Hmmm, the office is a bit warm today.) 
 Try warming up the TMP101 with your finger and running *i2cget* again.
 

books/beaglebone-cookbook/09capes/capes.rst

@@ -796,7 +796,7 @@ and PCB shown in :ref:`capes_miniDisplay_pcb`.
     PCB for MiniDisplay cape
 
 .. note::
-   #TODO#: The MiniDisplay cape is not currently available, so this example should be udpated.
+   #TODO#: The MiniDisplay cape is not currently available, so this example should be updated.
 
 A good starting point is to take the PCB layout for the MiniDisplay and edit it for your project. 
 The connectors for +P8+ and +P9+ are already in place and ready to go.
@@ -1153,10 +1153,14 @@ Solution
 ---------
 
 Complete capes have an |I2C| EEPROM on board that contains configuration information that is read at boot time. 
-`Adventures in BeagleBone Cape EEPROMs <http://bit.ly/1Fb64uF>`_ gives a helpful description of two methods for 
-programming the EEPROM.  `How to Roll your own BeagleBone Capes <http://bit.ly/1E5M7RJ>`_ is a good four-part 
+`Adventures in BeagleBone Cape EEPROMs <https://web.archive.org/web/20190108195421/http://azkeller.com:80/blog/?p=62>`_ gives a helpful description of two methods for 
+programming the EEPROM.  `How to Roll your own BeagleBone Capes <https://web.archive.org/web/20200222204651/http://papermint-designs.com/community/taxonomy/term/68>`_ is a good four-part 
 series on creating a cape, including how to wire and program the EEPROM.
 
+.. note::
+
+   The current effort to document how to enable software for a cape is ongoing at https://docs.beagleboard.org/latest/boards/capes.
+
 .. _capes_production:
 
 Putting Your Cape Design into Production
@@ -1172,7 +1176,7 @@ Solution
 ---------
 
 `CircuitHub <https://circuithub.com/>`_ offers a great tool to get a quick quote on assembled PCBs. 
-To make things simple, I downloaded the `CircuitCo MiniDisplay Cape Eagle design materials <https://elinux.org/Special:Badtitle/NS500:MiniDisplay_Cape>`_
+To make things simple, I downloaded the `CircuitCo MiniDisplay Cape Eagle design materials <https://elinux.org/MiniDisplay_Cape>`_
 and uploaded them to CircuitHub.
 
 After the design is uploaded, you'll need to review the parts to verify that CircuitHub has or 

books/beaglebone-cookbook/10parts/parts.rst

@@ -52,8 +52,6 @@ with jumper wires, and <<parts_breadboard>> shows where you can get breadboards.
     +-------------+--------------------------------------------------------------------------------------------+
     | Digikey     | http://www.digikey.com/product-detail/en/TW-E012-000/438-1049-ND/643115                    |
     +-------------+--------------------------------------------------------------------------------------------+
-    | RadioShack  | http://www.radioshack.com/solderless-breadboard-jumper-wire-kit/2760173.html#.VG5i1PnF8fA  |
-    +-------------+--------------------------------------------------------------------------------------------+
     | SparkFun    | https://www.sparkfun.com/products/124                                                      |
     +-------------+--------------------------------------------------------------------------------------------+
 
@@ -73,7 +71,7 @@ with jumper wires, and <<parts_breadboard>> shows where you can get breadboards.
     +-------------+---------------------------------------------------------------------------------------------------------------------------------------------+
     | SparkFun    | https://www.sparkfun.com/search/results?term=breadboard                                                                                     |
     +-------------+---------------------------------------------------------------------------------------------------------------------------------------------+
-    | CircuitCo   | http://elinux.org/CircuitCo:BeagleBone_Breadboard                                                                                           |
+    | CircuitCo   | https://elinux.org/BeagleBoneBreadboard (no longer manufactured, but design available)                                                      |
     +-------------+---------------------------------------------------------------------------------------------------------------------------------------------+
 
 If you want something more permanent, try `Adafruit's Perma-Proto Breadboard <https://www.adafruit.com/product/1609>`_, laid out like a breadboard.
@@ -234,7 +232,3 @@ Here are some things that don't fit in the other categories.
     | Nokia 5110 LCD                                      | `Adafruit 5110 LCD <http://bit.ly/1Ag6LgG>`_,                                         |
     |                                                     | `SparkFun 5110 LCD <http://bit.ly/19cizdu>`_                                          |
     +-----------------------------------------------------+---------------------------------------------------------------------------------------+
-    | BeagleBone LCD7                                     | `eLinux LCD7 <http://elinux.org/CircuitCo:BeagleBone_LCD7#Distributors>`_             |
-    +-----------------------------------------------------+---------------------------------------------------------------------------------------+
-    | MiniDisplay Cape                                    | `eLinux minidisplay <http://elinux.org/CircuitCo:MiniDisplay_Cape>`_                  |
-    +-----------------------------------------------------+---------------------------------------------------------------------------------------+

code @ e103135d

-Subproject commit 269209bc64423a06e8caf11b91c7468805b287b2
+Subproject commit e103135d4cd1387e0bfa37b468e3137b9a34e60f

books/pru-cookbook/01case/case.rst

@@ -113,14 +113,14 @@ via the PRU that can be used out of the box.
 
 Just run:
 
-.. code-block:: bash
+.. code-block:: shell-session
 
    bone$ sudo rc_test_servos -f 10 -p 1.5
 
 The ``-f 10`` says to use a frequency of 10 Hz and the ``-p 1.5`` says to set the position to ``1.5``.  The range of positions is
 ``-1.5`` to ``1.5``.   Run ``rc_test_servos -h`` to see all the options.
 
-.. code-block:: bash
+.. code-block:: shell-session
 
    bone$ rc_test_servos -h
 
@@ -229,9 +229,9 @@ Solution
 The forth encoder can be implemented on the PRU. If you run ``rc_test_encoders_eqep`` 
 on the Blue, you will see the output of encoders E1-E3 which are connected to the eEQP hardware.
 
-.. code-block:: bash
+.. code-block:: shell-session
 
-   bone$ *rc_test_encoders_eqep* 
+   bone$ rc_test_encoders_eqep
 
    Raw encoder positions
          E1   |      E2   |      E3   | 
@@ -288,13 +288,13 @@ Solution
 The forth encoder is implemented on the PRU and accessed with `sudo rc_test_encoders_pru`  
 
 .. note::
-   This command needs root permission, so the `sudo` is needed.  
+   This command needs root permission, so the `sudo` is needed.  The default password is `temppwd`.
 
 Here's what you will see
 
-.. code-block:: bash
+.. code-block:: shell-session
 
-   bone$ *sudo rc_test_encoders_pru*
+   bone$ sudo rc_test_encoders_pru
    [sudo] password for debian: 
 
    Raw encoder position
@@ -343,17 +343,17 @@ If you want to be running a newer image, there are instructions on the site for
 
 .. _case_installing_beaglelogic:
 
-.. code-block:: bash
+.. code-block:: shell-session
    :caption: Installing BeagleLogic
       
-   bone$ *git clone https://github.com/abhishek-kakkar/BeagleLogic*
-   bone$ *cd BeagleLogic/kernel*
-   bone$ *mv beaglelogic-00A0.dts beaglelogic-00A0.dts.orig*
-   bone$ *wget https://gist.githubusercontent.com/abhishek-kakkar/0761ef7b10822cff4b3efd194837f49c/raw/eb2cf6cfb59ff5ccb1710dcd7d4a40cc01cfc050/beaglelogic-00A0.dts*
-   bone$ *make overlay*
-   bone$ *sudo cp beaglelogic-00A0.dtbo /lib/firmware/*
-   bone$ *sudo update-initramfs -u -k \`uname -r`*
-   bone$ *sudo reboot*
+   bone$ git clone https://github.com/abhishek-kakkar/BeagleLogic
+   bone$ cd BeagleLogic/kernel
+   bone$ mv beaglelogic-00A0.dts beaglelogic-00A0.dts.orig
+   bone$ wget https://gist.githubusercontent.com/abhishek-kakkar/0761ef7b10822cff4b3efd194837f49c/raw/eb2cf6cfb59ff5ccb1710dcd7d4a40cc01cfc050/beaglelogic-00A0.dts
+   bone$ make overlay
+   bone$ sudo cp beaglelogic-00A0.dtbo /lib/firmware/
+   bone$ sudo update-initramfs -u -k \`uname -r`
+   bone$ sudo reboot
 
 Once the Bone has rebooted, browse to 192.168.7.2:4000 where you'll see
 :ref:`case_beaglelogic_capture`.  Here you can easily select the sample
@@ -386,17 +386,17 @@ logic analyzer on the Bone with no additional hardware needed.
 The kernel interface makes it easy to control the PRUs through the
 command line.  For example
 
-.. code-block:: bash
+.. code-block:: shell-session
       
-   bone$ *dd if=/dev/beaglelogic of=mydump bs=1M count=1*
+   bone$ dd if=/dev/beaglelogic of=mydump bs=1M count=1
 
 will capture a binary dump from the PRUs. The sample rate and number of 
 bits per sample can be controlled through ``/sys/``.
 
-.. code-block:: bash
+.. code-block:: shell-session
 
-   bone$ *cd /sys/devices/virtual/misc/beaglelogic*
-   bone$ *ls*
+   bone$ cd /sys/devices/virtual/misc/beaglelogic
+   bone$ ls
    buffers      filltestpattern  power       state         uevent
    bufunitsize  lasterror        samplerate  subsystem
    dev          memalloc         sampleunit  triggerflags
@@ -407,9 +407,9 @@ bits per sample can be controlled through ``/sys/``.
 
 You can set the sample rate by simply writing to ``samplerate``.
 
-.. code-block:: bash
+.. code-block:: shell-session
 
-   bone$ *echo 100000000 > samplerate*
+   bone$ echo 100000000 > samplerate
 
 `sysfs attributes Reference <https://beaglelogic.readthedocs.io/en/latest/sysfs_attributes.html>`_
 has more details on configuring via sysfs.
@@ -417,9 +417,9 @@ has more details on configuring via sysfs.
 If you run ``dmesg -Hw`` in another window you can see when a capture 
 is started and stopped.
 
-.. code-block:: bash
+.. code-block:: shell-session
 
-   bone$ *dmesg -Hw*
+   bone$ dmesg -Hw
    [Jul25 08:46] misc beaglelogic: capture started with sample rate=100000000 Hz, sampleunit=1, triggerflags=0
    [  +0.086261] misc beaglelogic: capture session ended
 
@@ -583,11 +583,11 @@ explaining how the PRUs get this type of performance.
 
   .. _case_e1.31_example:
 
-  .. literalinclude:: code/e1.31-test.py
+  .. literalinclude:: ../code/01start/e1.31-test.py
      :caption: e1.31-test.py -Example of generating packets to control the NeoPixels
      :linenos:
 
-  :download:`e1.31-test.py <code/e1.31-test.py>` 
+  :download:`e1.31-test.py <../code/01start/e1.31-test.py>` 
 
   .. TODO document the code
 
@@ -748,10 +748,10 @@ following instructions at https://xlights.org/releases/.
 
 Run xLights and you'll see :ref:`case_xlights_setup`.
 
-.. code-block:: bash
+.. code-block:: shell-session
 
-   host$ *chmod +x xLights-2021.18-x86_64.AppImage*
-   host$ *./xLights-2021.18-x86_64.AppImage*
+   host$ chmod +x xLights-2021.18-x86_64.AppImage
+   host$ ./xLights-2021.18-x86_64.AppImage
 
 .. TODO update the figures.
 
@@ -985,7 +985,7 @@ You can `build simpPRU <https://simppru.readthedocs.io/en/latest/install/build/>
 source, more easily just `install it <https://simppru.readthedocs.io/en/latest/install/install/>`_. 
 On the Beagle run:
 
-.. code-block:: bash
+.. code-block:: shell-session
 
    bone$ wget https://github.com/VedantParanjape/simpPRU/releases/download/1.4/simppru-1.4-armhf.deb
    bone$ sudo dpkg -i simppru-1.4-armhf.deb
@@ -996,15 +996,15 @@ Now, suppose you wanted to run the
 `LED blink <https://simppru.readthedocs.io/en/latest/examples/led_blink/>`_
 example which is reproduced here.
 
-.. literalinclude:: code/blink.sim
+.. literalinclude:: ../code/01start/blink.sim
    :caption: LED Blink (blink.sim)
    :linenos:
 
-:download:`blink.sim <code/blink.sim>`
+:download:`blink.sim <../code/01start/blink.sim>`
 
 Just run simppru
 
-.. code-block:: bash
+.. code-block:: shell-session
 
    bone$ simppru blink.sim --load 
    Detected TI AM335x PocketBeagle
@@ -1019,7 +1019,7 @@ Detected TI AM335x PocketBeagle
 The +--load+ flag caused the compiled code to be copied to +/lib/firmware+.
 To start just do:
 
-.. code-block:: bash
+.. code-block:: shell-session
 
    bone$ cd /dev/remoteproc/pruss-core0/
    bone$ ls

books/pru-cookbook/01case/code/blink.sim

-/* From: https://simppru.readthedocs.io/en/latest/examples/led_blink/ */
-while : 1 == 1 {
-    digital_write(P1_31, true);
-    delay(250);     /* Delay 250 ms */
-    digital_write(P1_31, false);
-    delay(250);
-}

books/pru-cookbook/01case/code/circle.py

-#!/usr/bin/env python3
-
-"""A demo client for Open Pixel Control
-http://github.com/zestyping/openpixelcontrol
-
-Runs an LED around in a circle
-
-"""
-
-import time
-import opc
-
-ADDRESS = 'localhost:7890'
-
-# Create a client object
-client = opc.Client(ADDRESS)
-
-# Test if it can connect
-if client.can_connect():
-    print('connected to %s' % ADDRESS)
-else:
-    # We could exit here, but instead let's just print a warning
-    # and then keep trying to send pixels in case the server
-    # appears later
-    print('WARNING: could not connect to %s' % ADDRESS)
-
-# Send pixels forever
-STR_LEN=16
-for i in range(STR_LEN):
-    leds = [(0, 0, 0)] * STR_LEN
-leds[0] = (0, 127, 0)
-
-while True:
-    tmp = leds[0]
-    for i in range(STR_LEN-1):
-        leds[i] = leds[i+1]
-    leds[-1] = tmp
-    if client.put_pixels(leds, channel=0):
-        print('sent')
-    else:
-        print('not connected')
-    time.sleep(0.1)
-

books/pru-cookbook/01case/code/e1.31-test.py

-#!/usr/bin/env python3
-# Controls a NeoPixel (WS2812) string via E1.31 and FPP
-# https://pypi.org/project/sacn/
-# https://github.com/FalconChristmas/fpp/releases
-import sacn
-import time
-
-# provide an IP-Address to bind to if you are using Windows and want to use multicast
-sender = sacn.sACNsender("192.168.7.1")
-sender.start()							# start the sending thread
-sender.activate_output(1)		# start sending out data in the 1st universe
-sender[1].multicast = False # set multicast to True
-sender[1].destination = "192.168.7.2"  # or provide unicast information.
-sender.manual_flush = True # turning off the automatic sending of packets
-# Keep in mind that if multicast is on, unicast is not used
-LEDcount = 24
-# Have green fade is as it goes
-data = []
-for i in range(LEDcount):
-	data.append(0)		# Red
-	data.append(i)		# Green
-	data.append(0)		# Blue
-sender[1].dmx_data = data
-sender.flush()
-time.sleep(0.5)
-
-# Turn off all LEDs
-data=[]
-for i in range(3*LEDcount):
-	data.append(0)
-sender.flush()
-sender[1].dmx_data = data
-time.sleep(0.5)
-
-# Have red fade in
-data = []
-for i in range(LEDcount):
-	data.append(i)
-	data.append(0)
-	data.append(0)
-sender[1].dmx_data = data
-sender.flush()
-time.sleep(0.25)
-
-# Make LED circle 5 times
-for j in range(15):
-	for i in range(LEDcount-1):
-		data[3*i+0] = 0
-		data[3*i+1] = 0
-		data[3*i+2] = 0
-		data[3*i+3] = 0
-		data[3*i+4] = 64
-		data[3*i+5] = 0
-		sender[1].dmx_data = data
-		sender.flush()
-		time.sleep(0.02)
-# Wrap around
-	i = LEDcount-1
-	data[0] = 0
-	data[1] = 64
-	data[2] = 0
-	data[3*i+0] = 0
-	data[3*i+1] = 0
-	data[3*i+2] = 0
-	sender[1].dmx_data = data
-	sender.flush()
-	time.sleep(0.02)
-    
-time.sleep(2)  # send the data for 10 seconds
-sender.stop()  # do not forget to stop the sender

books/pru-cookbook/01case/code/encoder_setup.sh

-#!/bin/bash
-# Configure the pins based on which Beagle is running
-machine=$(awk '{print $NF}' /proc/device-tree/model)
-echo -n $machine
-
-# Configure eQEP pins
-if [ $machine = "Black" ]; then
-    echo " Found"
-    pins="P9_92 P9_27 P8_35 P8_33 P8_12 P8_11 P8_41 P8_42"
-elif [ $machine = "Blue" ]; then
-    echo " Found"
-    pins=""
-elif [ $machine = "PocketBeagle" ]; then
-    echo " Found"
-    pins="P1_31 P2_34 P2_10 P2_24 P2_33"
-else
-    echo " Not Found"
-    pins=""
-fi
-
-for pin in $pins
-do
-    echo $pin
-    config-pin $pin qep
-    config-pin -q $pin
-done
-
-##########################################
-# Configure PRU pins
-if [ $machine = "Black" ]; then
-    echo " Found"
-    pins="P8_16 P8_15"
-elif [ $machine = "Blue" ]; then
-    echo " Found"
-    pins=""
-elif [ $machine = "PocketBeagle" ]; then
-    echo " Found"
-    pins="P2_09 P2_18"
-else
-    echo " Not Found"
-    pins=""
-fi
-
-for pin in $pins
-do
-    echo $pin
-    config-pin $pin pruin
-    config-pin -q $pin
-done