cancel
Showing results for 
Search instead for 
Did you mean: 

How to make the right connection for using DDR Test Suite?

porter.chen
Associate II

0693W00000QMwtvQAD.jpg0693W00000QMx0DQAT.jpgThe board is installed with the system( stm32mp1-openstlinux-5.15-yocto-kirkstone-mp1-v22.06.15) by following the Getting started .

0693W00000QMx03QAD.jpgAll drivers are installed.

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

16 REPLIES 16
porter.chen
Associate II

Hi @Semer CHERNI​ 

Thank you for the information.

The the listed projects are gray and cannot be selected. "Finish" can not be selected. Could you help?

  • Go to File > Import
    • Select "Existing Projects into Workspace" > Next
      • 0693W00000SvJStQAN.jpg
    • Browse to your project location (In the STM32DDRFW-UTIL package, the projects are stored in DDR_Tool directory)
      • 0693W00000SvJTDQA3.jpg
    • Select one of the listed project > Finish
      • the listed projects are gray and cannot be selected
      • => cannot "finish"

0693W00000SvJThQAN.jpg 

​Thank you

Hi @Semer CHERNI (ST Employee)​

Any chance to help on this issue?

Thanks

Helle @porter.chen​ 

First sorry for my late response.

To be able to import correctly the project, you have to select the folder containing the ".project" file.

In you case you go another level lower to select the folder "STM32MP135C-DK_DDR_UTILITIES_A7"

Doing this will let you import the project successfully.

Kind regards,

Semer.

To give better visibility on the answered topics, please click on Accept as Solution on the reply which solved your issue or answered your question.

porter.chen
Associate II

Hi @Semer CHERNI​ ​

Thank you for the information.

"This Port Com Is Not Responding" is still happened. Could you help?

The details are listed below.

the main operation is to achieve(2.3.2 Using STM32CubeMX

)

  • STM32CubeIDE: Launch the debug session as indicated in §2.2.3 Launch project+ STM32CubeMX DDR Test Suite run DDR Tests

After choosing another workspace location and restarting the import process, the files were successfully imported.

0693W00000WIMdEQAX.jpg

  • In Main tab:
    • Make sure binary file .elf is correctly set
    • 0693W00000WIMRSQA5.jpg
  • In Debugger tab:
    • Make sure JTAG/SWD link (Engineering mode) is selected for "Load Mode"
    • Debug probe uses ST-LINK
    • 0693W00000WIMT9QAP.jpg
  • Disable "Enable live expressions"
    • 0693W00000WIMc6QAH.jpg
  • On your board, make sure the boot pins are set in Engineering mode (See §2.1 Hardware connections)

0693W00000WIMYiQAP.jpg

  • Then launch the Debug session

=> Shows a lot red info; gdb port disable

  • 0693W00000WIMaZQAX.jpg

Red info:

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 V3J10M3B5S1 (API v3) VID:PID 0483:3753

Info : Target voltage: 3.306809

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 : 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: 0x0000a978

MMU: disabled, D-Cache: disabled, I-Cache: disabled

  •  try C/C++ Application debug
  • 0693W00000WIMvDQAX.jpg

=>Error with command: gdb -- version

=>cannot run program "gdb": Launching failed

0693W00000WIMw6QAH.jpg 

4.Open CubeMX and follow the steps described in 2.2

3.2.3 DDR configuration

  • Once the project is opened, configure the DDR settings in “Pinout and configuration�? tab

0693W00000WIMxsQAH.jpg

  • Once the DDR configuration is set, you can then run DDR Test Suite in “Tools�? tab (See §3.2.5 DDR Test Suite).

0693W00000WINADQA5.jpgSelect the correct port com then connect the board. Target information is displayed when the tool is running properly

=> The Port Com is Not Responding

​---------------------------------------------------------------------------------

Thank you

Alex - APMemory
Senior II

@Semer CHERNI​ 

Hi Semer,

Appreciate your support to get set up done and be able to run all memory validation

Thanks

Alex

Alex - APMemory
Senior II

@Semer CHERNI (ST Employee)

Let us know if any further advice or local contact in Taiwan who could help ?

Thanks

Alex

porter.chen
Associate II

@[Semer CHERNI]​ @[Alex - APMemory]​ 

Hi Semer and Alex,

Thank you for your support .

The connection of using DDR test suite is complete by using the operation steps listed below.

Please let me know if any steps need to be modified.

 Flash the MP135 with the "STM32MP135C-DK_DDR_UTILITIES_A7_signed.stm32" file found under this https://github.com/STMicroelectronics/STM32DDRFW-UTIL/tree/main/Binaries/STM32MP135C-DK_DDR_UTILITIES_A7 with the Cube programmer in CLI using this cmd "Cubeprogrammer install path\STM32_Programmer_CLI.exe -c port=usb1 -w the file path\STM32MP157C-DK2_DDR_UTILITIES_A7_signed.stm32 0x01 --start 0x01"

=> download STM32MP135C-DK_DDR_UTILITIES_A7.stm32 to C:\Program Files\STMicroelectronics\STM32Cube\STM32CubeProgrammer\bin

1 . connect cables as the picture shown below.(left: microUSB for ST-Link; right: USB typeC for power supply) the boot mode is set to "Force USB boot for flashing SW1[0 0 0 0]"

 
_legacyfs_online_stmicro_images_0693W00000biDAKQA2.png 
_legacyfs_online_stmicro_images_0693W00000biD5pQAE.png
_legacyfs_online_stmicro_images_0693W00000biDF0QAM.png2 . open cmd, follow the below steps. (by referring to 3.1.3 SYSRAM loading from

https://github.com/STMicroelectronics/STM32DDRFW-UTIL/blob/main/README.md#11-package-overview or Hub - STMicroelectronics/STM32DDRFW-UTIL: DDRFW-UTIL tool repository) (the same)

in cmd: path in C:\Program Files\STMicroelectronics\STM32Cube\STM32CubeProgrammer\bin>

type in and run:

STM32_Programmer_CLI.exe -c port=COM30 -w STM32MP135C-DK_DDR_UTILITIES_A7_signed.stm32 0x01 –-start 0x01

then open STM32CubeMX, choose COM30 in DDR interactive, connect , run DDR test suite

 
_legacyfs_online_stmicro_images_0693W00000biHDhQAM.png 

thank you