cancel
Showing results for 
Search instead for 
Did you mean: 

The stm32cubeide v1.1.0 hasn't load image option on macos

SChen.11
Associate III

Hi supporter,

I use STM32Cube v1.10 on macos(Mojave) and linux(debian 9). The debug dialog has load mode option to choose production or engineering mode in stm32cubeide on linux system. But that dialog hasn't the load mode on macos.

Below picture is debug dialog on macos.

0690X00000BvtBbQAJ.pngDoes any thing I am missing to setup for stm32cubeide?

1 ACCEPTED SOLUTION

Accepted Solutions
Olivier GALLIEN
ST Employee

Hi @Community member​ 

I confirm that MP1 is not supported in MacOS CubeIDE version.

Sorry for inconvenience.

Olivier

Olivier GALLIEN
In order 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.

View solution in original post

10 REPLIES 10
Cartu38 OpenDev
Lead II

Sounds STM32MP1* targets debug are not supported by STM32CubeIDE if MacOS. Please have a look at your IDE install. If Linux or MacOS some OS related plugins are lacking.

This is the correct answer.

Did you import the project from Linux to mac? Because if you try to create a new MP1 project through macOS then you should receive a dialogue telling you that there's no support for MP1 in macOS yet.

I am import these projects of stm32cubemp1 package into stm32cubeide on MacOS. On the import progress, the stm32cubeide show me some convert dialog and success tips. These converted projects can be build successful. I also confirm the "unsupported target selection" dialog when I select the stm32mp157 chip in new stm32 project process.

Well, that can be confusing for sure. The converter still converts the project successfully and it's the same builder so there shouldn't be any issues with that either. However, I believe it's the MP1 specific debug that hasn't been implemented yet.

Olivier GALLIEN
ST Employee

Hi @Community member​ 

I confirm that MP1 is not supported in MacOS CubeIDE version.

Sorry for inconvenience.

Olivier

Olivier GALLIEN
In order 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.

Thanks again. Does it will be add in the next version?

ACapo.1
Senior

This is a little bit mad!

I can build and debug the linux A7 side from OS X, I can build the M4 side from OSX but I cannot debug it.

I must admit after getting the A7 side working I thought the stmcube32ide side would just work!

OKoko.1
Associate II

hello All.

Olivier is not exactly correct about absence of MP1 support.

here is what you have to do to make MacOS CubeIDE working for M4 onboard core:

  1. switch to the (whatever it's been named) boot mode Boot0 = 0, Boot2 = 1
  2. copy over from the linux CubeIDE whole plugin folder: plugins/com.st.stm32cube.ide.mpu.debug.openocd_1.5.0.202011161118 into /Applications/STMicroelectronics/STM32CubeIDE.app/Contents/Eclipse
  3. copy over missing target/stm32mp1x.cfg file from plugins/com.st.stm32cube.ide.mpu.debug.openocd_1.5.0.202011161118/resources/openocd/st_scripts/target/stm32mp1x.cfg to plugins/com.st.stm32cube.ide.mcu.debug.openocd_1.5.0.202011091203/resources/openocd/st_scripts/target
  4. fix the /Applications/STMicroelectronics/STM32CubeIDE.app/Contents/Eclipse/artifacts.xml with the following lines:

   <artifact classifier='osgi.bundle' id='com.st.stm32cube.ide.mpu.debug.openocd' version='1.5.0.202011161118'>

     <properties size='1'>

       <property name='download.size' value='16850'/>

     </properties>

     <repositoryProperties size='1'>

       <property name='artifact.folder' value='true'/>

     </repositoryProperties>

   </artifact>

(this could be inserted right after the following block:

   <artifact classifier='osgi.bundle' id='com.st.stm32cube.ide.common.ui' version='1.5.0.202011040924'>

     <properties size='1'>

       <property name='download.size' value='17176'/>

     </properties>

   </artifact>

in result there will be OpenOCD working just fine:

Open On-Chip Debugger 0.10.0+dev-01288-g7491fb4 (2020-10-27-17:40)

Licensed under GNU GPL v2

For bug reports, read

   http://openocd.org/doc/doxygen/bugs.html

Info : Listening on port 6666 for tcl connections

Info : Listening on port 4444 for telnet connections

Warn : 'srst_nogate' reset_config option is required

Info : STLINK V2J37M26 (API v2) VID:PID 0483:3752

Info : Target voltage: 3.247706

Info : Unable to match requested speed 8000 kHz, using 4000 kHz

Info : Unable to match requested speed 8000 kHz, using 4000 kHz

Info : clock speed 4000 kHz

Warn : 'srst_nogate' reset_config option is required

Info : stlink_dap_op_connect(connect)

Warn : 'srst_nogate' reset_config option is required

Info : SWD DPIDR 0x6ba02477

Info : stlink_dap_op_connect(connect)

Warn : 'srst_nogate' reset_config option is required

Info : SWD DPIDR 0x6ba02477

Info : STM32MP157CACx.cm4: hardware has 6 breakpoints, 4 watchpoints

Info : STM32MP157CACx.cpu0: hardware has 6 breakpoints, 4 watchpoints

Info : STM32MP157CACx.cpu1: hardware has 6 breakpoints, 4 watchpoints

Info : starting gdb server for STM32MP157CACx.cpu0 on 3334

Info : Listening on port 3334 for gdb connections

Info : starting gdb server for STM32MP157CACx.cm4 on 3333

Info : Listening on port 3333 for gdb connections

Info : accepting 'gdb' connection on tcp/3333

target halted due to debug-request, current mode: Handler HardFault

xPSR: 0x21000003 pc: 0x10000446 msp: 0x1003fea4

Info : New GDB Connection: 1, Target STM32MP157CACx.cm4, state: halted

Info : accepting 'gdb' connection on tcp/3333

Info : New GDB Connection: 2, Target STM32MP157CACx.cm4, state: halted

Hi @OKoko.1​ , your way is right for me. The stm32cubeide 1.5 can debug cm4 on macos 10.14. But I had another issue when debugging on first time. The openocd can not reset core. So I need debug cm4 at first time on linux system then using it on macos.

Below is log message when debugging issue on macos 10.14 with stm32cubeide 1.5.

Open On-Chip Debugger 0.10.0+dev-01288-g7491fb4 (2020-10-27-17:40)
Licensed under GNU GPL v2
For bug reports, read
	http://openocd.org/doc/doxygen/bugs.html
Info : Listening on port 6666 for tcl connections
Info : Listening on port 4444 for telnet connections
Warn : 'srst_nogate' reset_config option is required
Info : STLINK V2J37S7 (API v2) VID:PID 0483:3748
Info : Target voltage: 3.261214
Info : Unable to match requested speed 8000 kHz, using 4000 kHz
Info : Unable to match requested speed 8000 kHz, using 4000 kHz
Info : clock speed 4000 kHz
Warn : 'srst_nogate' reset_config option is required
Info : stlink_dap_op_connect(connect)
Warn : 'srst_nogate' reset_config option is required
Info : SWD DPIDR 0x6ba02477
Info : stlink_dap_op_connect(connect)
Warn : 'srst_nogate' reset_config option is required
Info : SWD DPIDR 0x6ba02477
Info : STM32MP157AAAx.cm4: hardware has 6 breakpoints, 4 watchpoints
Info : STM32MP157AAAx.cpu0: hardware has 6 breakpoints, 4 watchpoints
Info : STM32MP157AAAx.cpu1: hardware has 6 breakpoints, 4 watchpoints
Info : STM32MP157AAAx.cm4: external reset detected
Info : starting gdb server for STM32MP157AAAx.cpu0 on 3334
Info : Listening on port 3334 for gdb connections
Info : starting gdb server for STM32MP157AAAx.cm4 on 3333
Info : Listening on port 3333 for gdb connections
Info : accepting 'gdb' connection on tcp/3333
Info : Halt timed out, wake up GDB.
Error: timed out while waiting for target halted
Error executing event gdb-attach on target STM32MP157AAAx.cm4:
 
Info : New GDB Connection: 1, Target STM32MP157AAAx.cm4, state: reset
Warn : negative reply, retrying
Warn : negative reply, retrying
Info : accepting 'gdb' connection on tcp/3333
Info : Halt timed out, wake up GDB.
Error: timed out while waiting for target halted
Error executing event gdb-attach on target STM32MP157AAAx.cm4:
 
Info : New GDB Connection: 2, Target STM32MP157AAAx.cm4, state: reset
Warn : negative reply, retrying
Warn : negative reply, retrying
Warn : target STM32MP157AAAx.cm4 is not halted (add breakpoint)
Error: can't add breakpoint: target running
Warn : target STM32MP157AAAx.cm4 is not halted (add breakpoint)
Error: can't add breakpoint: target running