Hi,
I followed the steps in the link below, minus "populate target," but I was able to successfully compile, transfer, and run the C example.
https://wiki.st.com/stm32mpu/wiki/Getting_started/STM32MP1_boards/STM32MP135x-DK
I also managed to create and compile an OpenSTLinux C project for the STM32MP135F-DK board using STM32CubeIDE.
Now I'm having trouble debugging the code.
My STM32MP135F-DK board has Ethernet working, and I can communicate with it using SSH. The STLINK interface of the Ubuntu host PC is working. I can use it to load MCU firmware onto a Nucleo board. The STlink serial port is also working, as I can connect to the board using the Minicon terminal and execute commands as shown in the link below:
https://wiki.st.com/stm32mpu/wiki/Getting_started/STM32MP1_boards/STM32MP135x-DK/Let%27s_start/Execute_basic_commands
The difference in relation to the link is in the item: "Printing distribution specific information", which for my board shows:
BB_VERSION = 2.0.0
BUILD_SYS = x86_64-linux
NATIVELSBSTRING = universal
TARGET_SYS = arm-ostl-linux-gnueabi
MACHINE = stm32mp1
DISTRO = openstlinux-weston
DISTRO_VERSION = 4.0.1-openstlinux-5.15-yocto-kirkstone-mp1-v22.06.15.1
TUNE_FEATURES = arm vfp cortexa7 neon vfpv4 thumb callconvention-hard
TARGET_FPU = hard
DISTRO_CODENAME = kirkstone
ACCEPT_EULA_stm32mp1 = 1
GCCVERSION = 11.%
PREFERRED_PROVIDER_virtual/kernel = linux-stm32mp
The problem is that the "Status Target Widget" in the lower right corner of the STM32CubeIDE shows "Busy Status," but during boot, it doesn't show the other statuses, as shown in the link below:
https://wiki.st.com/stm32mpu/wiki/How_to_use_the_Target_Status_widget_in_STM32CubeIDE
Could someone tell me why the Status Target Widget only shows "Busy Status" for my board? Could it be that the STM32MP135F-DK doesn't allow remote debugging, or does the factory image installed on the SD card not support communication with the STM32CubeIDE?
Ari
