Frequent hardfault on startup

キャンセル
次の結果を表示 
表示  限定  | 次の代わりに検索 
もしかして: 

Frequent hardfault on startup

ソリューションへジャンプ
2,819件の閲覧回数
Daan
Contributor III

Hello,

 

On an RT1064 I run a FreeRTOS based project. Quite frequent the application will not startup from the debugger because of a hardfault, if I reflash the application, it works properly (I didn't change the application nor do I need to recompile it). If I inspect the call stack, it is very random where the error originated, it can be USB, ethernet, File system, but it's always some FreeRTOS sourcefile, but I assume the FreeRTOS sources are quite well debugged.

Now and then I notice that there is no call stack at all, it just stops at an interrupt.

I work with SDK 2.10.0.

Any ideas?

0 件の賞賛
返信
1 解決策
2,730件の閲覧回数
Daan
Contributor III

Thanks for the reply.

I switched to the Segger driver for the debugger, this resolved my problem, I don't get the hardfaults on power-up any more.

Regards,

Danny

元の投稿で解決策を見る

0 件の賞賛
返信
5 返答(返信)
2,640件の閲覧回数
Daan
Contributor III

It seems that the hardfaults are caused by an incorrectly written flash, as mentioned before, I need to reflash the application, if I then inspect the console output, I noticed that 1 sector (of 12) is rewritten, that's odd, since the code has not changed. Is there some way to verify the flash during or after programming?

0 件の賞賛
返信
2,731件の閲覧回数
Daan
Contributor III

Thanks for the reply.

I switched to the Segger driver for the debugger, this resolved my problem, I don't get the hardfaults on power-up any more.

Regards,

Danny

0 件の賞賛
返信
2,803件の閲覧回数
Daan
Contributor III

Okay thank you, I'll install the latest SDK.

Regards,

Daan

0 件の賞賛
返信
2,804件の閲覧回数
Daan
Contributor III

Okay thank you, I'll install the latest SDK.

0 件の賞賛
返信
2,806件の閲覧回数
EdwinHz
NXP TechSupport
NXP TechSupport

Hi @Daan,

The random nature of the issue that you are describing makes it difficult to pinpoint the error to something specific. However, many bug fixes come with each release of our SDKs, so the first recommendation would definitely be to update the SDK to the latest release (2.12.0 as of now). Let me know if the problem persists after this.

 

BR,

Edwin.

0 件の賞賛
返信