However, in the DDR test suite, I cannot connect to the device.
How to make the right connection for using DDR Test Suite?
Do I need a DDR utilities binary file for the connection?
thank you
@Erwan SZYMANSKI @Semer CHERNI
Thank you for the support.
- I modified SW1 [0 0 0 0] and followed the steps from 1 to 2. Then followed step 3 and 4 with SW1[1010], but it shows errors in activating device and no responding
- Will it cause the connection problem when applying STM32MP135C-DK_DDR_UTILITIES_A7_signed.stm32 to the board STM32MP135F-DK?
Could you help?
@Erwan SZYMANSKI (ST Employee) @Semer CHERNI (ST Employee)
Thank you for the support.
- I used SW1 [0 0 0 0] and followed 3.1.3 SYSRAM loading to 3.2.5 DDR Test Suite https://github.com/STMicroelectronics/STM32DDRFW-UTIL/blob/main/README.md#11-package-overview but it shows "This Port Com Is Not Responding".
- After that, I used SW1[1 0 1 0] by following "3.2.5.1.2 Serial boot"., but it shows "This Port Com Is Not Responding" and "Error: Activating device: KO. Please, verify the boot mode configuration and check the serial port configuration. Reset your device then try again…"
Then I tried SW1 [0 0 1 0] and repeat "3.2.5.1.2 Serial boot"; and tried SW1[0 0 0 0] and repeat "3.2.5.1.2 Serial boot". It shows the same "This Port Com Is Not Responding" and "Error: Activating device: KO. Please, verify the boot mode configuration and check the serial port configuration. Reset your device then try again…"
- The com port information is shown in the attached picture. How to check the serial port is properly connected?
- Will it cause the connection problem when applying STM32MP135C-DK_DDR_UTILITIES_A7_signed.stm32 to the board STM32MP135F-DK?
Could you help?
Thank you
Adding the information I got from SW1 operating instruction
Force USB boot for flashing SW1[0 0 0 0]
Engineering boot SW1[0 0 1 0]
Boot from microSD card SW1[1 0 1 0]
Hello @porter.chen
First sorry because my response took time.
About how to connect the board and run the DDR test Suite I found a roughly simple way:
- Start by downloading this repo GitHub - STMicroelectronics/STM32DDRFW-UTIL: DDRFW-UTIL tool repository
- Put the board in engineering mode
- Using STM32CubeIDE import the project "STM32MP135C-DK" I used this project on STM32MP135F because I couldn't find an other one(you can follow the steps described in 2.2 How to compile and launch DDR Tool project)
- Build the imported project and run it
- Open CubeMX and follow the steps described in 2.2 How to compile and launch DDR Tool project
Kind regards,
Semer.
Hi @Semer CHERNI ,
Thank you for the information.
It does not work properly, details of the operation are listed below.
Could you help?
2.2.2 Build project
The project can contain several build configurations. In that case, you should firstly select the configuration corresponding to your hardware version:
- Right click on the project in the Project Explorer
- Go to Build configurations > Set Active
- Select your configuration
To build the project in STM32CubeIDE:
- Right click on the project in the Project Explorer
- And click on "Build Project"
To launch the project:
- Right click on the project in the Project Explorer
- Select "Debug As / Debug Configurations�?
- In STM32 Cortex-M C/C++ Application / Select your debug configuration (if not present, double-click on "STM32 Cortex-M C/C++ Application")
- In Main tab:
- Make sure binary file .elf is correctly set
- In Debugger tab:
- Make sure JTAG/SWD link (Engineering mode) is selected for "Load Mode"
- Debug probe uses ST-LINK
- On your board, make sure the boot pins are set in Engineering mode (See §2.1 Hardware connections)
- Then launch the Debug session
failure information:
Open On-Chip Debugger 0.11.0+dev-00449-g53fa0f7 (2022-06-09-09:42) [https://github.com/STMicroelectronics/OpenOCD]
Licensed under GNU GPL v2
For bug reports, read
http://openocd.org/doc/doxygen/bugs.html
srst_only srst_pulls_trst srst_gates_jtag srst_open_drain connect_deassert_srst
Info : Listening on port 6666 for tcl connections
Info : Listening on port 4444 for telnet connections
Info : STLINK V3J8M3B5S1 (API v3) VID:PID 0483:3753
Info : Target voltage: 3.310621
Info : Unable to match requested speed 5000 kHz, using 3300 kHz
Info : Unable to match requested speed 5000 kHz, using 3300 kHz
Info : clock speed 3300 kHz
Info : stlink_dap_op_connect(connect)
Info : SWD DPIDR 0x6ba02477
Info : stlink_dap_op_connect(connect)
Info : SWD DPIDR 0x6ba02477
Info : STM32MP135FAFx.cpu: hardware has 6 breakpoints, 4 watchpoints
Info : STM32MP135FAFx.cpu: MPIDR level2 0, cluster 0, core 0, multi core, no SMT
Info : gdb port disabled
Info : gdb port disabled
Info : starting gdb server for STM32MP135FAFx.cpu on 3333
Info : Listening on port 3333 for gdb connections
Info : accepting 'gdb' connection on tcp/3333
Info : New GDB Connection: 1, Target STM32MP135FAFx.cpu, state: halted
Info : rejected 'gdb' connection, no more connections allowed
Info : stlink_dap_op_connect(connect)
Info : SWD DPIDR 0x6ba02477
Info : stlink_dap_op_connect(connect)
Info : stlink_dap_op_connect(reconnect)
Info : SWD DPIDR 0x6ba02477
target halted in ARM state due to debug-request, current mode: Supervisor
cpsr: 0x200001d3 pc: 0x0000a97c
MMU: disabled, D-Cache: disabled, I-Cache: disabled
3.Build the imported project and run it
Open On-Chip Debugger 0.11.0+dev-00449-g53fa0f7 (2022-06-09-09:42) [https://github.com/STMicroelectronics/OpenOCD]
Licensed under GNU GPL v2
For bug reports, read
http://openocd.org/doc/doxygen/bugs.html
srst_only srst_pulls_trst srst_gates_jtag srst_open_drain connect_deassert_srst
Info : Listening on port 6666 for tcl connections
Info : Listening on port 4444 for telnet connections
Info : STLINK V3J8M3B5S1 (API v3) VID:PID 0483:3753
Info : Target voltage: 3.313828
Info : Unable to match requested speed 5000 kHz, using 3300 kHz
Info : Unable to match requested speed 5000 kHz, using 3300 kHz
Info : clock speed 3300 kHz
Info : stlink_dap_op_connect(connect)
Info : SWD DPIDR 0x6ba02477
Info : stlink_dap_op_connect(connect)
Info : SWD DPIDR 0x6ba02477
Info : STM32MP135FAFx.cpu: hardware has 6 breakpoints, 4 watchpoints
Info : STM32MP135FAFx.cpu: MPIDR level2 0, cluster 0, core 0, multi core, no SMT
Info : gdb port disabled
Info : gdb port disabled
Info : starting gdb server for STM32MP135FAFx.cpu on 3333
Info : Listening on port 3333 for gdb connections
Info : accepting 'gdb' connection on tcp/3333
Info : New GDB Connection: 1, Target STM32MP135FAFx.cpu, state: halted
Info : rejected 'gdb' connection, no more connections allowed
Info : stlink_dap_op_connect(connect)
Info : SWD DPIDR 0x6ba02477
Info : stlink_dap_op_connect(connect)
Info : stlink_dap_op_connect(reconnect)
Info : SWD DPIDR 0x6ba02477
target halted in Thumb state due to debug-request, current mode: Supervisor
cpsr: 0x200001f3 pc: 0x000060a4
MMU: disabled, D-Cache: disabled, I-Cache: disabled
shutdown command invoked
4.Open CubeMX and follow the steps described in 2.2 How to compile and launch DDR Tool project
=> The port com is not responding
Thank you
Hello @porter.chen
Thanks for your feedback.
I think that there are 2 main reasons for the failure:
- The project structure in the screenshots you posted is a little different that the one I have:
==> Make sure you imported the project this way :
- Go to File > Import
- Select "Existing Projects into Workspace" > Next
- Browse to your project location (In the STM32DDRFW-UTIL package, the projects are stored in DDR_Tool directory)
- Select one of the listed project > Finish
- When debugging I see that you get an error about a failure in activating the live expressions
==> When the "Enable live expressions" is selected I get the same error message when debugging
==> Make sure that this option is disabled in the debug configuration
Kind regards,
Semer.
