cancel
Showing results for 
Search instead for 
Did you mean: 

TouchGFX taget MDK-ARM debug fault (Automatic run without clicking run )

ggyy426
Associate II

Hi all

I try to use MDK-ARM Keil to debug TouchGFX project?

But it hang on Debug mode.

When enter debug it directly run and hang like photo below

0690X000008vxo3QAA.png

This happen after I add new algorithm for STM32H7

0690X000008vxoNQAQ.png

After adding this for QSPI setting for insufficient flash

Because I code and photo are more than 2MBs so I need add .flm file to use QSPI

Here is my file

Thanks

13 REPLIES 13
Martin KJELDSEN
Chief III

Hi,

Are you saying that you were able to debug prior to adding the Flash Algorithm for QSPI?

/Martin

Hi Martin

Yes if code and photo in flash below 2MBs it will work but in my case code and photo more than 2MBs will cause error like flash insufficient.

So I need external flash to store photo just remove Flash Algorithm won't work

Could you please try to program the external flash using ST-Link or STCubeProgrammer instead of the Keil flashloader? Then debug in Keil as usual.

/Martin

I use stlink to connect my keil.

0690X000008vzgVQAQ.jpg

0690X000008vzhJQAQ.jpg

You mean ST-Link Utility like photo show? I try it later.

Yes i mean the ST-Link Utility, sorry.

Hi Martin

I tried but I still have problem

0690X000008w17tQAA.png

0690X000008w188QAA.png

Keil still need download external flash

If just download STM32H7X_2048 it will have error like photo below.

0690X000008w18DQAQ.png

I also have some problems where should I use QSPI function

 https://community.st.com/s/question/0D50X0000AqALvpSQG/stm32h743-qspi-function

If you just remove the external flashloader configuration from your Keil project, enable the project to convert the axf to hex, then use ST-Link to program the entire range (even internal) - Just use "target->program" instead of "External Loader->Program".

/Martin

Hi Martin

I already entered debug

I still have problems with QSPI

So far when I hang at BitmapsBase

I can't enter 0x90000000 where should I call QSPI read() function

to solve this issue?

0690X000008w5kkQAA.jpg

And one more question

Is here any future plan STM32CubeMX will update STM32H7 to support TouchGFX like stm32f7 series photo below?

0690X000008w5lOQAQ.png

There is no executable code in QSPI, only asset data.

I don't know about the current CubeMX roadmap re: H7. But the general goal is to have TouchGFX be enabled for all relevant MCUs.

/Martin