Skip to content

stm32mp135f-dk

Directory actions

More options

Directory actions

More options

Latest commit

 

History

History

stm32mp135f-dk

README.md

STM32MP135F-DK QuickStart

Purchase the STM32MP135F-DK

Tip

To set up and connect this device using the AWS Greengrass Lite SDK, refer to this QuickStart Guide

  1. Introduction
  2. Requirements
  3. Hardware Setup
  4. Device Setup
  5. Onboard Device
  6. Using the Demo
  7. Troubleshooting
  8. Resources

1. Introduction

This guide is designed to walk through the steps to connect the STM32MP135F-DK to the Avnet /IOTCONNECT platform and periodically send general telemetry data.

The STM32MP135 Discovery kit (STM32MP135F-DK) leverages the capabilities of the 1 GHz STM32MP135 microprocessors to allow users to develop easily applications using STM32 MPU OpenSTLinux Distribution software. It includes an ST-LINK embedded debug tool, LEDs, push-buttons, two 10/100 Mbit/s Ethernet (RMII) connectors, one USB Type-C® connector, four USB Host Type-A connectors, and one microSD™ connector. To expand the functionality of the STM32MP135 Discovery kit, one GPIO expansion connector is also available for third-party shields. Additionally, the STM32MP135 Discovery kit features an LCD display with a touch panel, Wi-Fi® and Bluetooth® Low Energy capability, and a 2-megapixel CMOS camera module. It also provides secure boot and cryptography features.

2. Requirements

This guide has been written and tested to work on a Windows 10/11 PC. However, there is no reason this can't be replicated in other environments.

Hardware

Software

Note

The demos for this device have been tested with the Scarthgap version 6.0 Yocto image release from ST. Older or newer versions may have significant incompatibilities, so it is recommended to use the 6.0 release. Follow this flashing guide to download and flash this image to your board.

3. Hardware Setup

See the reference image below for cable connections.

Reference Image with Connections

Using the above image as reference, make the following connections:

  1. (OPTIONAL) Connect an Ethernet cable from your LAN (router/switch) to the Ethernet connector labeled #1. If you instead wish to use Wi-Fi, after booting your board refer to the WIFI guide.
  2. Connect the USB-C cable from a 5V/2.4A (up to 3A) power supply to the PWR USB-C connector on the board, labeled **#2 **.
  3. Connect the Micro-USB cable from your PC to the Micro-USB connector labeled #3 on the reference image.

4. Device Setup

  1. Open a serial terminal emulator program such as TeraTerm.
  2. Ensure that your serial settings in your terminal emulator are set to:
  • Baud Rate: 115200
  • Data Bits: 8
  • Stop Bits: 1
  • Parity: None
  1. Noting the COM port value for "STMicroelectronics STLink Virtual COM Port" in the Device Manager list, attempt to connect to your board via the terminal emulator

Note

A successful connection may result in just a blank terminal box. If you see a blank terminal box, press the ENTER key to get a login prompt. An unsuccessful connection attempt will usually result in an error window popping up.

  1. When prompted for a login, type root followed by the ENTER key.
  2. Run these commands to update the core board packages and install necessary /IOTCONNECT packages:
su

apt-get update && apt-get install python3-pip -y && python3 -m pip install iotconnect-sdk-lite requests
  1. Run this command to create and move into a directory for your demo files:
mkdir -p /opt/demo && cd /opt/demo

Tip

To gain access to "copy" and "paste" functions inside of a PuTTY terminal window, you can CTRL+RIGHTCLICK within the window to utilize a dropdown menu with these commands. This is very helpful for copying/pasting between your browser and the terminal.

5. Onboard Device

Important

If users plan to deploy a KVS expansion demo, the device needs to be originally created in /IOTCONNECT with the plitekvs template (available here). During the device creation steps, the Stream Type should be set to "USB Based" and the Stream Resource should be set as either "Video Stream" (for the PutMedia demo) or "WebRTC" (for the WebRTC demo). The AWS backend will not register the device for KVS if it is created with a different template and then later switched to plitekvs, it needs to be set at device creation.

The next step is to onboard your device into /IOTCONNECT. This will be done via the online /IOTCONNECT user interface.

Follow this guide to walk you through the process.

Tip

If you have obtained a solution key for your /IOTCONNECT account from Softweb Solutions, you can utilize the /IOTCONNECT REST API to automate the device onboarding process via shell scripts. Check out this guide for more info on that.

6. Using the Demo

Run the basic demo with this command:

python3 app.py

Note

Always make sure you are in the /opt/demo directory before running the demo. You can move to this directory with the command: cd /opt/demo

View the random-integer telemetry data under the "Live Data" tab for your device on /IOTCONNECT.

7. Troubleshooting

To return the board to an out-of-box state, refer to the FLASHING.md guide.

8. Resources