DHSBC STM32MP13: Difference between revisions
From Wiki-DB
Jump to navigationJump to search
Ageisreiter (talk | contribs) |
Ageisreiter (talk | contribs) |
||
(24 intermediate revisions by the same user not shown) | |||
Line 32: | Line 32: | ||
*'''PMIC''' STPMIC1D | *'''PMIC''' STPMIC1D | ||
*'''DDR3 DRAM''' 512 Mbyte @ 533 MHz | *'''DDR3 DRAM''' 512 Mbyte @ 533 MHz | ||
*'''eMMC Flash''' | *'''eMMC Flash''' 4 Gbyte | ||
*'''NOR Flash''' 4 Mbyte, Quad SPI interface | *'''NOR Flash''' 4 Mbyte, Quad SPI interface | ||
*'''EEPROM''' 4 kbyte | *'''EEPROM''' 4 kbyte | ||
Line 51: | Line 51: | ||
*'''Supply (SYS_DCIN)''' 8 - 18 VDC | *'''Supply (SYS_DCIN)''' 8 - 18 VDC | ||
*'''Temperature Range''' 0 - 40 °C | *'''Temperature Range''' 0 - 40 °C | ||
*'''Dimensions ''' | *'''Dimensions ''' 85 x 56 mm | ||
*'''Raspberry Pi 40-pin Expansion''' | *'''Raspberry Pi 40-pin Expansion''' | ||
**2 x UART | **2 x UART | ||
Line 64: | Line 64: | ||
== Product Change Notifications (PCN) == | == Product Change Notifications (PCN) == | ||
==== DHCOR STM32MP13==== | ==== DHCOR STM32MP13==== | ||
== Downloads == | |||
* [https://www.dropbox.com/scl/fi/1g9t0m3q1oramkm3orskx/STM32-linux6_6_scarthgap_dh-stm32mp13-dhcor-dhsbc_meta-dhsom-extras_meta-dhsom-extras-qt6_meta-dhsom-extras-wpe.tar?rlkey=uqveic9wwu89jjd7zf6zv7yo5&st=fawr2ytc&dl=0 DH Mainline based starter image 2024-07-03 (based on 6.6 Linux Kernel)] | |||
== Documentation == | |||
* [[media:DOC_DHSBC-STM32MP13-Quick-Start-Guide_R02_2024-08-05.pdf|Getting-Started with DHSBC STM32MP13 (R02)]] | |||
* [[media:USM DHCOR-STM32MP13 R01 2024-07-12.pdf|DHCOR STM32MP13 User Manual R01 <span style="color:#FF0000">'''IMPORTANT: Please have a look at chapter 26. Hardware design checklist'''</span>]] | |||
== Design Files == | |||
* [[media:SCH_719-100-HS00035-customer_R06_2023-11-16.pdf|DHSBC STM32MP13 Schematic]] | |||
* [https://www.dropbox.com/scl/fi/xfo9dyfflo3fn08u2h3t2/DHSBC-STM32MP13-3D-STEP-719-100_R01_2024-03-07.zip?rlkey=7s00f73wh2cxb48g4n7v8ca2s&st=sll9kjbr&dl=0 DHSBC STM32MP13 3D STEP file] | |||
* [https://www.dropbox.com/scl/fi/qw4w8y4mwyztalvotos1v/DHCOR-STM32MP13-Symbol-Footprint.zip?rlkey=9twtzutrerlw61a3zel3gl720&st=3c9ibw89&dl=0 DHCOR STM32MP13 Allegro/layout symbol] | |||
* [https://www.dropbox.com/scl/fi/jje7b8vn9tllsu96smpjr/DHCOR-STM32MP13-3D-STEP-718-100_R01_2024-03-06.zip?rlkey=8yjki1zvhzqoo0a76znuki0vn&st=pwcz7b8y&dl=0 DHCOR STM32MP13 3D STEP file] | |||
== Software == | |||
=== DH Mainline based Linux === | |||
* [https://github.com/dh-electronics/kas-dhsom Build your own Yocto Scarthgap LTS via kas (GitHub)] | |||
* [https://github.com/dh-electronics/meta-dhsom-stm32-bsp Yocto BSP meta layer (Github)] | |||
== Useful instructions == | |||
==== Setup new board and install image files via USB (dfu and ums mode) / U-Boot recovery via DFU ==== | |||
*[[DHSBC STM32MP13 DFU and UMS usage|DHSBC STM32MP13 DFU and UMS usage]] | |||
==== How to connect to WiFi network with WPA2 PSK? ==== | |||
:'''Establish connection''' | |||
:{| class="wikitable" | |||
|<tt>$ wpa_passphrase "SSID" > /etc/wpa_supplicant.conf</tt> | |||
|} | |||
:-> In the next step, please enter the password | |||
:{| class="wikitable" | |||
|<tt>$ rfkill unblock all</tt> | |||
|- | |||
|<tt>$ ip link set wlansom0 up</tt> | |||
|- | |||
|<tt>$ wpa_supplicant -B -i wlansom0 -c /etc/wpa_supplicant.conf</tt> | |||
|- | |||
|<tt>$ udhcpc -i wlansom0 </tt> | |||
|} | |||
:'''Disconnect''' | |||
:{| class="wikitable" | |||
|<tt>$ ip link set wlansom0 down</tt> | |||
|} | |||
==== Simple Bluetooth test ==== | |||
:Bring up bluetooth on the STM32MP13xx DHCOR SoM / DHSBC: | |||
:{| class="wikitable" | |||
|<tt>$ hciconfig hci0 up</tt> | |||
|} | |||
:Make the STM32MP13xx DHCOR SoM / DHSBC discoverable to other BT devices: | |||
:{| class="wikitable" | |||
|<tt>$ hciconfig hci0 piscan</tt> | |||
|} | |||
:Scan for other discoverable devices: | |||
:{| class="wikitable" | |||
|<tt>$ hcitool scan</tt> | |||
|} Scanning ... | |||
:When the scan is now performed on a HostPC, the STM32MP13xx DHCOR SoM / DHSBC should be visible: | |||
:{| class="wikitable" | |||
|<tt>$ hciconfig hci0 up</tt> | |||
|- | |||
|<tt>$ hcitool scan</tt> | |||
|} | |||
:Scanning ... | |||
DC:FE:23:12:34:56 dh-stm32mp13-dhcor-dhsbc | |||
:To generate some traffic on the BT UART between SoC and BT chip, try e.g. L2 ping from hostpc: | |||
:{| class="wikitable" | |||
|<tt> l2ping DC:FE:23:12:34:56</tt> | |||
|} | |||
Ping: DC:FE:23:12:34:56 from E8:48:B8:11:22:33 (data size 44) ... | |||
44 bytes from DC:FE:23:12:34:56 id 0 time 11.44ms | |||
44 bytes from DC:FE:23:12:34:56 id 1 time 39.83ms | |||
44 bytes from DC:FE:23:12:34:56 id 2 time 39.25ms ... | |||
:An interesting option to l2ping is -f, flood ping, which sends a lot of packets, that means a lot more traffic too: | |||
:{| class="wikitable" | |||
|<tt> l2ping -f DC:FE:23:12:34:56</tt> | |||
|} | |||
==== Add support for joy-it RB-TFT3.2V2 SPI display==== | |||
:[[Image:DHSBC-STM32MP13-with-SPI-Display.png|300px]] | |||
:Add Device Tree oeverlay to u-boot. | |||
:{| class="wikitable" | |||
|<tt>=> setenv loaddtos '#conf-stm32mp135f-dhcor-dhsbc.dtb#conf-stm32mp13xx-dhcor-dhsbc-overlay-rb-tft32-v2.dtbo'</tt> | |||
|- | |||
|<tt>=> saveenv </tt> | |||
|- | |||
|<tt>=> saveenv </tt> | |||
|} | |||
* [https://joy-it.net/en/products/RB-TFT3.2V2 Link: joy-it RB-TFT3.2V2] | |||
== Links == | |||
* [https://www.dh-electronics.com/embedded-produkte/dhsom/detail/dhcor-stm32mp13 DH DHCOR STM32MP13] | |||
* [https://www.dh-electronics.com/embedded-produkte/development-carrier-boards/detail/dhsbc-stm32mp13 DH DHSBC STM32MP13] | |||
* [https://wiki.st.com/stm32mpu/wiki/Main_Page STM32 MPU wiki] | |||
* [https://wiki.st.com/stm32mpu/wiki/Category:Device_tree_configuration STM32 MPU wiki - Device tree configuration] | |||
* [https://wiki.st.com/stm32mpu/wiki/STM32MP13_resources STM32MP13 resources] |
Latest revision as of 12:30, 13 September 2024
The DHSBC STM32MP13x board is the official DHCOR STM32MP13 reference design!
Introduction
Reference design for secure industrial IoT devices based on STM32MP13x
- Single Board Computer based on the solderable DHCOR STM32MP13
- Compatible with accessories from the Raspberry Pi© community
- Highlights: Bluetooth / WiFi, Dual GB Ethernet, Secure Boot, OP-TEE support
- Trusted Platform Module 2.0 available on request
- Mainline Linux support and active software maintenance
- Industrial product design with CE certification
- Guaranteed long-term availability of 10+ years
Technical Details
|
|
Product Change Notifications (PCN)
DHCOR STM32MP13
Downloads
Documentation
- Getting-Started with DHSBC STM32MP13 (R02)
- DHCOR STM32MP13 User Manual R01 IMPORTANT: Please have a look at chapter 26. Hardware design checklist
Design Files
- DHSBC STM32MP13 Schematic
- DHSBC STM32MP13 3D STEP file
- DHCOR STM32MP13 Allegro/layout symbol
- DHCOR STM32MP13 3D STEP file
Software
DH Mainline based Linux
Useful instructions
Setup new board and install image files via USB (dfu and ums mode) / U-Boot recovery via DFU
How to connect to WiFi network with WPA2 PSK?
- Establish connection
$ wpa_passphrase "SSID" > /etc/wpa_supplicant.conf
- -> In the next step, please enter the password
$ rfkill unblock all $ ip link set wlansom0 up $ wpa_supplicant -B -i wlansom0 -c /etc/wpa_supplicant.conf $ udhcpc -i wlansom0
- Disconnect
$ ip link set wlansom0 down
Simple Bluetooth test
- Bring up bluetooth on the STM32MP13xx DHCOR SoM / DHSBC:
$ hciconfig hci0 up
- Make the STM32MP13xx DHCOR SoM / DHSBC discoverable to other BT devices:
$ hciconfig hci0 piscan
- Scan for other discoverable devices:
$ hcitool scan
- When the scan is now performed on a HostPC, the STM32MP13xx DHCOR SoM / DHSBC should be visible:
$ hciconfig hci0 up $ hcitool scan
- Scanning ...
DC:FE:23:12:34:56 dh-stm32mp13-dhcor-dhsbc
- To generate some traffic on the BT UART between SoC and BT chip, try e.g. L2 ping from hostpc:
l2ping DC:FE:23:12:34:56
Ping: DC:FE:23:12:34:56 from E8:48:B8:11:22:33 (data size 44) ... 44 bytes from DC:FE:23:12:34:56 id 0 time 11.44ms 44 bytes from DC:FE:23:12:34:56 id 1 time 39.83ms 44 bytes from DC:FE:23:12:34:56 id 2 time 39.25ms ...
- An interesting option to l2ping is -f, flood ping, which sends a lot of packets, that means a lot more traffic too:
l2ping -f DC:FE:23:12:34:56
Add support for joy-it RB-TFT3.2V2 SPI display
=> setenv loaddtos '#conf-stm32mp135f-dhcor-dhsbc.dtb#conf-stm32mp13xx-dhcor-dhsbc-overlay-rb-tft32-v2.dtbo' => saveenv => saveenv