- Austin, TX
- (512) 861-3400
- Austin, TX
- 512-861-3400
Published On: July, 30, 2025 By: Neeraj Kumar Reddy Dantu | Updated: November 18, 2025 by Greg Sheridan
The OSD62-PM-BRK is a flexible prototyping platform for the OSD62x-PM System-in-Package (SiP) module. It features the OSD6254-1G-IPM built around the AM6254 SoC from Texas Instruments. In addition to enabling multimedia features of OSD62x-PM, the platform provides access to 145 IOs of the OSD62x-PM device. This allows you to prototype custom applications with ease, offering maximum flexibility for customizing your prototypes based on OSD62-PM-BRK.
This application note will give you a brief overview of the OSD62-PM-BRK, its features, and how to get started on using it to prototype your application.
The OSD62-PM-BRK package comes with the OSD62-PM-BRK board in an anti-static bag (shown below).
The OSD62-PM-BRK is an Open-source prototyping platform for the OSD62x-PM SiP module. The schematics and layout files for the OSD62-PM-BRK can be found here:
https://octavosystems.com/octavo_products/osd62-pm-brk/#Design%20Files
The following image shows a block diagram of OSD62-PM-BRK:
The following are the main features of OSD62-PM-BRK:
The figure below shows the physical locations of the main features of the OSD62-PM-BRK:
While serving as a prototyping platform for the OSD62x-PM, the OSD62-PM-BRK showcases the advantages of using the OSD62x-PM in a custom design.
The OSD62-PM-BRK is compatible with all software for the AM62x SoC. This includes TI’s Linux BSP as well as MCU+ SDK for the M4 core of AM62x SoC and popular community supported software.
This image is built on TI’s Linux distribution to support the AM62x SoC. Details on the generation of this image can be found here.
You can download the complete image here:
This image is built on the Beagleboard.org® Beagleplay® Debian Linux distribution. The Debian distribution allows you to dynamically customize packages for easy prototyping. Details on how this image was created can be found here.
You can download the complete image here:
Below you can find an image of the that outlines the default pinout for the 100mil headers of the OSD62-PM-BRK.
An Excel spreadsheet with the pinout and corresponding alternate functions for each pin can be downloaded from here:
Getting started with OSD62-PM-BRK involves the following steps:
To get started with the OSD62-PM-BRK, you will need:
A picture of the setup items is shown below:
For this Getting Started Guide, we will use the BeagleBoard.org® Debian Linux image customized for OSD62-PM-BRK. The TI SDK image will follow a similar procedure. Once you download the image from the
Software section, use Etcher to flash the image to the SD card as described in the following steps:
NOTE: If you are using a Linux based distribution, such as Ubuntu, on your host PC, you can use other programs like “dd” to program the SD card.
Now that you have a microSD card with a Linux image on it, you can boot the OSD62-PM-BRK board and begin communicating with it. This section is broken into two. The first consists of the required steps to boot the OSD62-PM-BRK and communicate with it via USB. The second contains extra optional steps that can be added if you would like to use a UART terminal to interface with the OSD62-PM-BRK.
Once the Linux kernel starts booting LED 0 will show a “heartbeat” pattern and LED 1 will show “cpu activity”.
Windows: https://192.168.7.2:3000/?folder=/home/debian
MAC / Linux: https://192.168.6.2:3000/?folder=/home/debian
Note: You may need to bypass the browser security warnings due to certificate issues.
echo 1 > /sys/class/leds/led-2/brightness
We highly recommend using a UART connection as it provides better visibility into boot and provides direct access to the console. The following steps should be done before the OSD62-PM-BRK is powered on in Step 2 of the previous section.
NOTE: If you are using a Linux based distribution, such as Ubuntu, on your host PC, you can use a terminal program like “minicom” or “picocom” for serial communication. For example, the picocom command to initialize the serial terminal is:
sudo picocom -b 115200 /dev/ttyUSBx
where /dev/ttyUSBx (x will be a number such as 0, 1, 2, etc.) is the virtual device in /dev that is created when the USB to UART adapter is connected to the PC’s USB port.
Username | debian |
Password | temppwd |
After you input the above details, you will be prompted to change the password. Choose a new password.
Note: When typing passwords, there will be no feedback from the terminal.
Per the Mikroe Click Board™ standard linked here: https://cdn.mikroe.com/cms/click-boards/click-board-standard-guidelines-april-2019.pdf, the following diagram shows the pinout and dimensions of the three (3) different sizes of Click boards:
Click Board™ compatible interfaces are available on each end of the OSD62-PM-BRK board. The following figure shows the position of the click boards installations for the OSD62-PM-BRK.
TFor this guide, we will use the Accel Click to demonstrate working with Click Boards™. The Accel Click contains the ADXL345 Digital Accelerometer sensor with SPI or I2C slave interfaces for communication:
The Click Board™ draws 3.3V from the Click Board™ Interface to power the ADXL345 sensor. We will use the I2C interface of the Click Board™ to communicate with the sensor. The following figure shows the specific pins used for using the Accel Click with the OSD62-PM-BRK.
For this demonstration, you will need the following items:
The following image shows the items needed:
As described in Figure 22, there are 2 positions you can use to interface OSD62-PM-BRK with the Accel Click™ board. They are shown below:
For this demonstration, we will use the I2C1 Interface position above the microSD card slot. The rest of the hardware setup is the same as described in Section 5.3.
A Python program that uses i2c_tools to communicate with the ADXL345 chip on the Accel Click is provided in /home/debian/osd62-pm-brk-demos/ folder:
To execute the script, use the following command:
$ python3 osd62-pm-brk-demos/accel_click_demo.py
Here is an example output for this script:
debian@BeagleBone:~$ python3 osd62-pm-brk-demos/accel_click_demo.py
Read ADXL345 via i2c_tools
Setup time: 54.0 ms
Acceleration: (12, -7, 217) Time: 23.1 ms
Acceleration: (2, 10, 224) Time: 23.1 ms
^CReading ADXL345 Complete
If you want to change the position of the Click Board™ from over the microSD card (I2C1) to over the USB-C UFP (I2C3), you will need to change the variable ADXL345_I2C_BUS in accel_click_demo.py to “3”.
In this demo, we show how to control the on-board LEDs via a web browser. The following items are needed:
The hardware setup is the same as described in Section 5.3.
The Python program that initializes the web server is located in
/home/debian/osd62-pm-brk-demos/LEDWebDemo/:
To execute the script, use the following two commands:
$cd osd62-pm-brk-demos/LEDWebDemo/
$python3 LEDWebServer.py
The output on the console should look like this:
debian@BeagleBone:~/osd62-pm-brk-demos/LEDWebDemo$ python3 LEDWebServer.py
Server Starts - :8080
192.168.7.1 - - [04/Sep/2024 08:58:55] "GET / HTTP/1.1" 200 -
192.168.7.1 - - [04/Sep/2024 08:58:55] "GET /favicon.ico HTTP/1.1" 200 –
You can now browse to the web page hosted by OSD62-PM-BRK by visiting the URL: http://192.168.7.2:8080/. The following figure shows the web page with buttons for various actions:
Select the button for the corresponding action for each LED: D1, D2 and D3.
You will see the corresponding LED change based on the selection.
The OSD62-PM-BRK has a USB-C DFP (Downstream Facing Port) that advertises 500mA current output. This port, which is configured as a USB Host port by default in the Linux Device Tree, can be used to connect USB devices such as mice, keyboards, and USB adapters. Please note that the current requirements for both the OSD62-PM-BRK and any USB devices attached to the USB-C DFP must be satisfied by the USB-C UFP and / or the VIN-5P0 pins of the 100mil expansion headers.
In this section adding a WiFi USB adapter is demonstrated.
In addition to the items described in Section 5.1, the following items are needed:
Table 8‑1: Items Needed to Add WiFi Networking to OSD52-PM-BRK
| Product | Description | Where to Buy |
|---|---|---|
| TP-Link TL-WN725N | USB WiFi adapter (or equivalent) | https://www.amazon.com/wifi-adapter-usb-pc-network/dp/B008IFXQFU |
| USB-C to USB-A adapter | USB-C Male to USB-A Female (or equivalent) | https://www.amazon.com/10Gbps-USB-Adapter-Smartphone-Keyboard/dp/B0DYS9YH3K/ |
Other USB WiFi adapters and USB-C to USB-A adapters can also work.
The following image shows the items:
To connect the WiFi adapter to the USB-C DFP port, plug the WiFi adapter into the USB-A female port of the USB-C adapter and plug the USB-C adapter’s USB-C male port into the USB-C DFP port of OSD62-PM-BRK. This arrangement is shown below:
The rest of the hardware setup is the same as described in Section 5.3
Once the OSD62-PM-BRK has booted and the WiFi adapter has been inserted, you can check whether the adapter was detected with the “lsusb” command:
debian@BeagleBone:~$ lsusb
Bus 001 Device 002: ID 0bda:8179 Realtek Semiconductor Corp. RTL8188EUS 802.11n Wireless Network Adapter
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
The output of the “ifconfig” command should show a “wlanX” interface, where “X” is a number:
debian@BeagleBone:~$ ifconfig
wlan0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
ether b4:b0:24:69:8b:b9 txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
The following steps are needed to connect to a WiFi network:
Command:
nmcli dev status
Ouput:
debian@BeagleBone:~$ nmcli dev status
DEVICE TYPE STATE CONNECTION
lo loopback connected (externally) lo
docker0 bridge connected (externally) docker0
wlan0 wifi disconnected ——
Command:
sudo nmcli dev wifi rescan
Command:
nmcli dev wifi list
Output:
debian@BeagleBone:~$ nmcli dev wifi list
IN-USE BSSID SSID MODE CHAN RATE SIGNAL BARS SECURITY
xx:xx:xx:xx:xx:xx Network1 Infra 2 65 Mbit/s 72 ▂▄▆_ WPA2
xx:xx:xx:xx:xx:xx Network2 Infra 2 65 Mbit/s 55 ▂▄__ WPA2
xx:xx:xx:xx:xx:xx Network3 Infra 2 65 Mbit/s 37 ▂▄__ WPA2
Command:
sudo nmcli dev wifi connect "YOUR_SSID" password "YOUR_PASSWORD" ifname wlan0
Output:
debian@BeagleBone:/home/debian# sudo nmcli dev wifi connect “NETWORK_NAME” password “PASSWORD” ifname wlan0
Device ‘wlan0’ successfully activated with ‘xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx’
Command:
nmcli con show --active
Output:
root@BeagleBone:/home/debian# nmcli con show —active
NAME UUID TYPE DEVICE
NETWORK_NAME xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxx wifi wlan0
The OSD62-PM-BRK comes with a 40 pin FPC connector for connecting to touchscreen displays using the OLDI0 and I2C0 interfaces. In addition to the hardware listed in the previous sections, you will need a compatible display and FPC connector. The FPC connector pinout was designed specifically for the TI SK-LDC1 touchscreen. Please check the FPC connector pinout for your touchscreen before connecting it to the OSD62-PM-BRK. Please note that the FPC Type B cable that comes with the TI SK-LCD1 is not compatible with the OSD62-PM-BRK. Specifics of a display configuration that is supported out of the box are provided below.
In addition to the items described in Section 5.1, the following items are needed:
Table 9‑1: OSD62-PM-BRK Display Configuration
| Product | Description | Where to Buy |
|---|---|---|
| TI SK-LCD1 | Microtips Technology USA # 13-101HIEB0HF0-S 10.1” WUXGA 1920x1200 TFT | https://www.ti.com/tool/SK-LCD1 |
| FPC 20624 | Type A 40 pin 0.5mm pitch | https://www.amazon.com/uxcell-Flexible-Ribbon-Player-Laptop/dp/B00W8WAICI/ |
| SLE48S1203N01 | 12V power supply with Barrel Plug, 2.5mm I.D. x 5.5mm O.D. x 9.5mm | https://www.digikey.com/en/products/detail/sl-power-advanced-energy/SLE48S1203N01/13424842 |
These items are shown below:
The rest of the hardware setup is the same as described in Section 5.3.
The TI-SK-LCD1 panel is supported by the OSD62-PM-BRK out of the box. However, the panel needs to be enabled via its Linux Device Tree Overlay. The device tree overlay for the TI-SK-LCD1: k3-am625-osd625-brk-microtips-mf101hie-panel.dtbo is located in /boot/firmware/overlays.
To enable the device tree overlay, the “microSD (default)” label in /boot/firmware/extlinux/extlinux.conf must be changed to add the variable “fdtoverlays” and set it to the device tree overlay for the TI-SK-LCD1. You can make this change by using a text editor like nano:
$ nano /boot/firmware/extlinux/extlinux.conf
Set the “fdtoverlays” variable under “microSD (default)” label to “/overlays/k3-am625-osd625-brk-microtips-mf101hie-panel.dtbo”. The following figure shows the edited extlinux.conf file with the setting for the “fdtoverlays” variable:
The next time the OSD62-PM-BRK boots, it will load the device tree overlay for the LCD panel on top of the default device tree it loads for the OSD62-PM-BRK board. To reboot the board, you can issue a reboot command to see the desktop environment loaded on the LCD screen:
$ sudo reboot
The OSD62-PM-BRK comes with a 15 pin FPC connector for communicating with camera modules over the CSIRX0 and WKUP_I2C0 interfaces. In addition to the hardware listed in the previous sections, you will need a compatible camera module and FPC connector. The FPC connector itself follows the Raspberry PI 15 pin FPC camera connector specification. However, not all cameras are supported by the current distribution of Linux. To understand if a particular camera is supported, please check the manufacturer driver installation instructions to see if they are compatible. Specifics of a camera module that is supported out of the box are provided below.
In addition to the items described in Section 5.1, the following items are needed:
Table 10‑1: OSD62-PM-BRK Camera Configuration
| Product | Description | Where to buy |
|---|---|---|
| 410-358 (Digilent Pcam 5C) | With OV5640 5MP camera | https://www.digikey.com/en/products/detail/digilent-inc/410-358/8111762 |
| FPC 20624 | Type B 15 pin 1mm pitch | https://www.amazon.com/dp/B0F1N7K82K/ |
These items are shown below:
The following steps describe the procedure to connect the camera module to the OSD62-PM-BRK:
The rest of the hardware setup is the same as described in Section 5.3.
The Pcam 5C camera module is supported by the OSD62-PM-BRK out of the box. However, the camera needs to be enabled via its Linux Device Tree Overlay. The device tree overlay for the Pcam 5C: k3-am625-osd625-brk-csi2-ov5640.dtbo is located in /boot/firmware/overlays.
To enable the device tree overlay, the “microSD (default)” label in /boot/firmware/extlinux/extlinux.conf must be changed to add the variable “fdtoverlays” and set it to the device tree overlay for the Pcam 5C. You can make this change by using a text editor like nano:
$ nano /boot/firmware/extlinux/extlinux.conf
Set the “fdtoverlays” variable under the “microSD (default)” label to “/overlays/ k3-am625-osd625-brk-csi2-ov5640.dtbo”. The following figure shows the edited extlinux.conf file with the setting for the “fdtoverlays” variable:
The next time the board boots, it will load the device tree overlay for the camera module on top of the default device tree it loads for the OSD62-PM-BRK board. To reboot the board, you can issue a reboot command to set up the camera module:
$ sudo reboot
The bash shell script that captures a frame from the camera module is located in the /home/debian/osd62-pm-brk-demos/ folder:
To execute the script, use the following commands:
cd osd62-pm-brk-demos/
./pcam_frame_capture.sh
A new image file named “pcam_frame.jpg” should appear in the osd62-pm-demos folder.
The following figure shows the mechanical diagram of OSD62-PM-BRK.
This app note shows how to power up and interact with the OSD62-PM-BRK. For the BeagleBoard.org® based Debian image, you can install packages and update software as you would with a standard Debian release. For the TI SDK image, if you want to customize the software running on the board to develop a prototype or change the configuration of the Linux image running on the board, please make sure to check out this repository:
https://github.com/octavosystems/osd62-pm-brk-tisdk.
The README guides you through generating custom TI SDK images for the OSD62-PM-BRK.
Yocto compatible meta-octavo-osd62 layer that integrates with TI’s Arago distro is available here:
https://github.com/octavosystems/meta-octavo-osd62
The README guides you through using the meta layer to generate images for OSD62-PM-BRK.
| Revision Number | Revision Date | Changes | Author |
|---|---|---|---|
| 1 | 08/04/2025 | Initial Revision | Neeraj Dantu, Erik Welsh |
| 2 | 10/16/2025 | Modify section 5.3 for clarity. Added Sections 6 through 10 to support more features. | Neeraj Dantu |
There has been multiple revisions to the OSDZU3-REF and some of the documentation is for specific revisions.
The revision of your OSDZU3-REF is printed under the fan next to the Octavo Systems logo. See the image below.
If there are multiple versions of a document make sure you select the one that matches your revision.
