BeagleBone Series - BBAI Getting Started

Initialization

First, connect the 12V power supply input to the Cape, and use a USB to serial module to connect the on-board serial port (J3 port for debugging):

BeagleBone Initialization

Make sure the USB to serial module has the necessary drivers (I used an FTDI module, and the driver can be downloaded from this link).

Use a command-line tool to connect to the serial port (I used MobaXterm), and set the baud rate to 115200.

Installing Patch Files

wget https://github.com/linyuxuanlin/File-host/blob/main/stash/k3-j721e-beagleboneai64.dtb?raw=true

Rename it to k3-j721e-beagleboneai64.dtb, move it to the /boot directory, and overwrite the original file. (I uploaded the file to a GitHub repository and used the wget command to retrieve it. You may need to modify the GitHub host to download it successfully.)

You can also transfer the file directly using SFTP.

evtest

The evtest tool is used for printing evdev kernel events. It reads and prints events with values and symbolic names directly from kernel devices. It can be used to debug input devices such as mice, keyboards, touchpads, and more.

Download the evtest tool:

sudo apt install evtest

Use the tool as follows:

sudo evtest /dev/input/eventｘ (where ｘ is the event number)

Key Input

debian@BeagleBone:~$ evtest
No device specified, trying to scan all of /dev/input/event*
Available devices:
/dev/input/event0: gpio-keys
Select the device event number [0-0]: 0
Input driver version is 1.0.1
Input device ID: bus 0x19 vendor 0x1 product 0x1 version 0x100
Input device name: "gpio-keys"
Supported events:
  Event type 0 (EV_SYN)
  Event type 1 (EV_KEY)
    Event code 256 (BTN_0)
    Event code 257 (BTN_1)
    Event code 258 (BTN_2)
Key repeat handling:
  Repeat type 20 (EV_REP)
    Repeat code 0 (REP_DELAY)
      Value    250
    Repeat code 1 (REP_PERIOD)
      Value     33
Properties:
Testing ... (interrupt to exit)
Event: time 1634868166.060258, type 1 (EV_KEY), code 257 (BTN_1), value 1
Event: time 1634868166.060258, -------------- SYN_REPORT ------------
Event: time 1634868166.284257, type 1 (EV_KEY), code 257 (BTN_1), value 0
Event: time 1634868166.284257, -------------- SYN_REPORT ------------

Devices on the SPI Bus

Barometer - BMP280
6-DOF - LSM6DS3TR
Compass - BMM150

# Change directory and list the contents
cd /sys/bus/iio/devices && ls -l

# Display the names of IIO devices
cat iio:device0/name
cat iio:device1/name
cat iio:device2/name
cat iio:device3/name
cat iio:device4/name
cat iio:device5/name

BeagleConnect Communication

# BC_RST
cd /sys/class/gpio
echo 326 > export
echo out > gpio326/direction
echo 0 > gpio326/value
echo 1 > gpio326/value

# Uart2
root@BeagleBone:/sys/class/tty# ls -l
lrwxrwxrwx 1 root root 0 Jul 13 17:29 ttyS4 -> ../../devices/platform/bus@100000/2820000.serial/tty/ttyS4

# Install minicom (if not already installed)
sudo apt-get install minicom

# Connect to /dev/ttyS4 using minicom
sudo minicom -D /dev/ttyS4

Welcome to minicom 2.8
OPTIONS: I18n
Port /dev/ttyS4, 10:57:41
Press CTRL-A Z for help on special keys

hello

The test was unsuccessful; no data was sent or received.

LEDs

# Change directory and list LED information
cd /sys/class/leds && ls -l

# Turn on the specified LEDs
echo 255 > beaglebone:green:cape0/brightness
echo 255 > beaglebone:green:cape3/brightness

# Turn off the specified LED
echo 0 > beaglebone:green:cape1/brightness

Laser Radar

If you encounter permission issues, please refer to Enabling SSH for the Root Account and execute the following commands with root privileges.

First, control GPIO to activate the laser radar:

cd /sys/class/gpio
echo 306 > export
echo 374 > export
echo out > gpio306/direction
echo out > gpio374/direction
echo 0 > gpio374/value
echo 1 > gpio306/value

Ensure the interface is recognized:

ls -l /sys/class/tty/

lrwxrwxrwx 1 root root 0 Jul 13 17:29 ttyS0 -> ../../devices/platform/bus@100000/2880000.serial/tty/ttyS0

Download the latest SDK from https://github.com/Slamtec/rplidar_sdk/releases.

Modify the /sdk/sdk/src/hal/event.h file for proper compilation:

enum
{
    EVENT_OK = 1,
    EVENT_TIMEOUT = 2, // Changed from -1
    EVENT_FAILED = 0,
};

Switch to the /sdk directory and use the make command to compile. The compiled files will be located in the /sdk/output directory.

Navigate to the /sdk/output/Linux/Release directory and execute the following command to run the test routine:

./ultra_simple /dev/ttyS0

References and Acknowledgments

Original: https://wiki-power.com/ This post is protected by CC BY-NC-SA 4.0 agreement, should be reproduced with attribution.

This post is translated using ChatGPT, please feedback if any omissions.