After trying using different setups, I would like to know what I'm doing wrong.
Probably something right before my nose...
I tried to use the DDR Test Suite for a MP157D/F-DK2. Just generated a project Xm using the defaults settings of the -DK2 board. Generate code. Not really needed at this point, but at least with the project I get to the DDR Test Suite Tool Button in STM32CubeMX (12.x).
Next thing reading the wiki, I needed the U-Boot SPL file. After searching I did not find anything that would be suitable using any of the packages provided.
Searching through the community.st.com revealed that the use of U-Boot SPL file is depreciated. You need to use the DDRFW-UTIL Package. So grabbed it from GitHub and looked for the file in the Binaries directory. Low and behold there was a ..MP157C-DK2_DDR_UTILITY_A7.stm32 file.
I tried also to compile the project using STM32CubeIDE and it did not compile without errors. The problem was the post processing using a python script. I have had more problems building the system and besides some mention of adding an alias python=python3 in .basrc to solve some quirks, installing `python-is-python3` solved the above problem.
So I used my VMware machine with Ubuntu 22.04 that works OK with USB on my Mac and followed the procedure to start the test suite. Set the loading in system to USB, and have a USB-serial converter connected to UART4.
Selecting STM32_Programmer_CLI was not possible. I could select the program in the bin directory, but it repeated in explaining it could not be found and the USB port was reported being busy.
So I moved over to a genuine PC (i3) running the same setup natively using Ubuntu 22.04 and repeated the procedure. Same problem and the USB port was reported being busy.
Last resort, dusted off a PC WIN10 machine and installed latest CubeMX, CubeProgrammer. Repeated the procedure and now I see the system being loaded with the ..MP157C-DK2_DDR_UTILITY_A7.stm32 file. The STM32_Programmer_CLI is found and does work. Then it stops, error that the port cannot be found.
Setup is micro-usb cable to STLink for console, USB2 port for downloading, USB1 port for power supply (3A).
There seems to be an incompatibility or misconfiguration on the linux side.
Windows seems to work, however, in all situations the console port cannot be used.
** Update the detection/acceptance of STM32_Programmer_CLI using DDR Test Suite in CubeMX is depending on teh used programmer version. The latest 2.17.x will not work. I noticed the same problem using windows after updating to the latest version. So I downgraded to make it work again. But this no solution for the problem of the DDR Test Suite.
