2019-07-26 08:11 AM
I'm trying to build an image for the STM32MP157C-DK2 board using the standard unmodified OpenSTLinux yocto build.
The build is successful and the image boots fine, but Bluetooth does not work with the basic image (it works with the trusted image).
Using a scope, I noticed that BT_REG_ON (on TP29) is driven low, which turns off the bluetooth part of the chip.
I suspect that the device tree is parsed differently depending on the bootloader used (the device tree itself is identical to the one that is preloaded on the provided SDCard).
Build Configuration:
BB_VERSION = "1.40.0"
BUILD_SYS = "x86_64-linux"
NATIVELSBSTRING = "ubuntu-19.04"
TARGET_SYS = "arm-openstlinux_weston-linux-gnueabi"
MACHINE = "stm32mp1"
DISTRO = "openstlinux-weston"
DISTRO_VERSION = "2.6-snapshot-20190726"
TUNE_FEATURES = "arm armv7ve vfp thumb neon vfpv4 callconvention-hard cortexa7"
TARGET_FPU = "hard"
DISTRO_CODENAME = "thud"
ACCEPT_EULA_stm32mp1 = "1"
GCCVERSION = "8.%"
PREFERRED_PROVIDER_virtual/kernel = "linux-stm32mp"
meta-oe
meta-gnome
meta-xfce
meta-initramfs
meta-multimedia
meta-networking
meta-webserver
meta-filesystems
meta-perl
meta-python = "HEAD:f1511d254632a34c1deb51f4bf8b8c21e7423f51"
meta-st-stm32mp = "HEAD:dcc955d6992cc46ce07440caaa5a17942776bbe6"
meta-qt5 = "HEAD:fd1f0f47312e7ee80e5ca65b8b2992cb068b1656"
meta-st-openstlinux = "HEAD:4e36cf0c7c7bdb24700a990f73afcda84cdcf0cf"
meta = "HEAD:f0394e80a37f1da47042a1aa0487594f390603f9"
2019-07-26 08:38 AM
Hello,
we recommend to use 'trusted boot' chain, which provide you full feature availability.
see https://wiki.st.com/stm32mpu/wiki/Boot_chains_overview#Overview
Note: The basic boot chain is not promoted by STMicroelectronics to make products, it is only provided to support the DDR Tuning Tool and the U-Boot developments.