tl,dr: No boot log or root term via ST-LINK connector on STM32MP157F-EV1. Haven't tried UART 4 yet.
This is related to:
https://community.st.com/t5/stm32-mpus-products/i-get-output-via-uart4-but-not-via-st-link-and-i-cannot-input/m-p/135067
Reference:
https://wiki.st.com/stm32mpu/wiki/How_to_get_Terminal
The board: STM32MP157F-EV1
My host: Dell XPS, USB puck with two USB ports, running Ubuntu 22.04.4 LTS using Minicom 2.8.
Following
https://wiki.st.com/stm32mpu/wiki/Getting_started/STM32MP1_boards/STM32MP157x-EV1/Let%27s_start/Populate_the_target_and_boot_the_image
I have:
* successfully prog'd the microSD with the STM32MP1257F (note the "eff") firmware
ie: FlashLayout_sdcard_stm32mp157F-ev1-optee.tsv
* the eval board boots to OpenSTLinux launcher
* all the demo apps will run
Just no log or root command line using the ST-LINK connector via USB. I cannot execute basic commands in
https://wiki.st.com/stm32mpu/wiki/Getting_started/STM32MP1_boards/STM32MP157x-EV1/Let%27s_start/Execute_basic_commands
My terminal command line is: sudo minicom -D /dev/ttyACM0.
Hardware flow control is off and UART settings are 115200 8N1.
Minicom does connect to ttyACM0.
I've ensured the Linux user is a part of the dialout group.
J1, J4, and J5 are set correctly.
I am respecting the power up and connection sequence described in user manual 6.7 Embedded ST-LINK/V2-1. The LEDs are lit as described by the manual.
As the 'F' part is intended for secure device, as opposed to the 'C':
Does that 'F' load suppress terminal access? Shoud I try 'C'?
Or is something else going on?
