Project TouchGFX, HardFault_Handler in IAR

Hosting · ‎2019-06-03

Hey.

When starting the debugger in IAR, fall in HardFault_Handler.

__HAL_RC_CRC_CLK_ENABLE(); did not help.

attach log file.

Martin KJELDSEN · ‎2019-06-06

Hi @Hosting,

Maybe V1.0 supported a flashloader for the QSPI directly in the EWARM project. But this is definitely not something that we'll be doing going forward - It's too much work because we sometimes have to make them ourselves.

Using ST-Link, could you try the following?

1) Upgrade the firmware on the chip (ST-Link -> Firmware update)

2) Make sure you've specified the flashloader for the STM32F746G-DISCO under "External Loader"-> "Add External Loader". And find "N25Q128A_STM32F746G-DISCO"

/Martin

View solution in original post

Martin KJELDSEN · ‎2019-06-03

Hi,

How did you create this project? I see it's STM32F746G-DISCO which is what we call the "dream board" here because it's been so stable for us. If you created the project from Touchgfx designer, the CRC should already be enabled.

/Martin

Hosting · ‎2019-06-04

First generated in the designer touchgfx, then in IAR via the tab "open workspace" from the folder EWARM.

Martin KJELDSEN · ‎2019-06-04

Which version of IAR?

/Martin

Hosting · ‎2019-06-04

IAR Embedded Workbench for ARM v. 8.30

Hosting · ‎2019-06-04

I did not understand what has changed, maybe the guys from ST updated something, but the folder structure changed when generating code in the TouchGFX designer. The main.cpp file has also changed. Now the debugger successfully starts and works. I apply screenshots of the project folder structure generated before and after some changes.

Martin, can you tell me how it happened?😊

Martin KJELDSEN · ‎2019-06-04

Looks like you're using the latest version of the Application template for STM32F746G-DISCO (v2.0+) which is CubeMX enabled (has an .ioc file). The previous one (v1.0.0) did not. In any case, the folder structure between those versions of the Application template has changed. Does that make sense to you?

Hosting · ‎2019-06-04

Verified. Indeed, STM32F746G-DISCO (v2.0+) has error while debugging, and V 1.1.0 version works good.

And how to use version 2.0 correctly? Or is it Bug?

Martin KJELDSEN · ‎2019-06-05

Hi again,

I'll try to very this here at the lab. Stay tuned!

Martin KJELDSEN · ‎2019-06-06

Okay, AT v2.0.0 is working for me without hardfault. This is interesting.

Can you tell how far you get before entering HardFault handler?

/Martin