Issue in debug envirement

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

Issue in debug envirement

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

I have a very annoying issue. When I (re)start the debug environment.

If I have this line in the expression window:

CAN2->MB[5].CS

 I got this error message:

pastedImage_1.png

It basically stops working. I have to power cycle the device, remove this line form the expression window And restart the debugger and that is really frustrating when you try to figure out why the canbus still doesn't work.

タグ(1)
0 件の賞賛
返信
1 解決策
2,188件の閲覧回数
jingpan
NXP TechSupport
NXP TechSupport

Hi Ernst,

This is because the FlexCAN module is not initialized at that time. The register in FlexCAN is not readable.

Regards,

Jing

元の投稿で解決策を見る

0 件の賞賛
返信
5 返答(返信)
2,188件の閲覧回数
ZhangJennie
NXP TechSupport
NXP TechSupport

Hi Ernst van Spronsen 

Please add your chip part number, thus we can have the right support for your issue. Thanks

Jun Zhang

0 件の賞賛
返信
2,188件の閲覧回数
e_v_spronsen
Contributor III

RT1060

0 件の賞賛
返信
2,189件の閲覧回数
jingpan
NXP TechSupport
NXP TechSupport

Hi Ernst,

This is because the FlexCAN module is not initialized at that time. The register in FlexCAN is not readable.

Regards,

Jing

0 件の賞賛
返信
2,188件の閲覧回数
e_v_spronsen
Contributor III

Jing,

I understand, but throwing a fatal exception and terminate the program  is really annoying and not necessary.

So every time I have to remove the parameters for debug. Start the program rewrite the parameters and remove them again when I'm terminate or restart the session.  When I forgot to remove the parameter on time. The program terminate and I have to restart over again. That is not really a workable situation.

Some error handling should be nice.

0 件の賞賛
返信
2,188件の閲覧回数
jingpan
NXP TechSupport
NXP TechSupport

Hi Ernst,

Yes, this is a bit boring. But read unaccessable address will cause hardfault. To avoid this problem, you can right click CAN2->MB[5].CS in Expressions window and select "disable". 

Regards,

Jing

0 件の賞賛
返信