FAQs
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 

Upgraded the STM32Cube IDE from 1.5.1 to 1.7.0 causes problems in debugging session

Go to solution
KF
Associate

‎2021-08-11 02:20 AM

Hello, i have just upgraded the IDE and now when I am starting a debug session, the external QSPI Flash is completly ignored, there is no compare/write operation on the external flash. Before the update, everything worked fine. I have a STM32F746NG chip on an personal board, with an personal loader for the external flash. When i upgraded the IDE bevore i just had to overwrite the ST_STM32F746G_Disco_QSPI.elf file in the STM32CubeIDE\plugins\com.st.stm32cube.ide.mcu.externaltools.jlink.win32_1.5.0.202011040924\tools\bin\Devices\ST\STM32F7 directory, but in the new "Devices" directory there is no STM32F7 directory?

Labels:
0 Kudos
1 ACCEPTED SOLUTION

Accepted Solutions
Go to solution
Markus GIRDLAND
ST Employee
In response to Markus GIRDLAND

‎2021-08-16 04:55 AM

This is the answer I got from SEGGER:

"The STM32F7 QSPI support has been moved from the JLinkDevices.xml / Device folder into the J-Link DLL.

The algorithm itself has not been changed. If *no* custom flash loader is required (default pin config), everything is working out-of-the-box.

If a custom flash loader is required, the default one needs to be overwritten via the JLinkDevices.xml. Actually in the same way as

it has been done in older versions."

Useful links:

https://wiki.segger.com/STM32F7#QSPI_support

https://wiki.segger.com/Open_Flashloader#Extending_an_Existing_Device

https://wiki.segger.com/Open_Flashloader#Using_a_Precompiled_Flashloader

View solution in original post

0 Kudos
3 REPLIES 3
Go to solution
Markus GIRDLAND
ST Employee

‎2021-08-16 02:58 AM

Hello there!

STM32CubeIDE packages whatever SEGGER J-Link provides. We will contact SEGGER to see if we can find out the reasoning behind the removal of the STM32F7 directory.

I'll update this thread once I know more.

0 Kudos
Go to solution
Markus GIRDLAND
ST Employee
In response to Markus GIRDLAND

‎2021-08-16 04:55 AM

This is the answer I got from SEGGER:

"The STM32F7 QSPI support has been moved from the JLinkDevices.xml / Device folder into the J-Link DLL.

The algorithm itself has not been changed. If *no* custom flash loader is required (default pin config), everything is working out-of-the-box.

If a custom flash loader is required, the default one needs to be overwritten via the JLinkDevices.xml. Actually in the same way as

it has been done in older versions."

Useful links:

https://wiki.segger.com/STM32F7#QSPI_support

https://wiki.segger.com/Open_Flashloader#Extending_an_Existing_Device

https://wiki.segger.com/Open_Flashloader#Using_a_Precompiled_Flashloader

0 Kudos
Go to solution
KF
Associate
In response to Markus GIRDLAND

‎2021-08-18 12:39 AM

Hello, thank you for the answer, just adding the device to the xml file and adding a directory for the elf file does not solve all problems in my case. Also the RAM settings were not correct, but they could be added in the xml. (In the older versions the RAM settings were not provided in the xml). Now i have the problem that the first 16MB seems to be read/write correct, (i have a 32MB external flash) but the next 16MB are not read/write correct...

0 Kudos
Top