NTM88_LIB.mem issue while trying to erase/flash the device

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

NTM88_LIB.mem issue while trying to erase/flash the device

ソリューションへジャンプ
1,021件の閲覧回数
shai_b
Senior Contributor II

Hello Team,

My customer is using NTM88 EVK and he was able to erase/flash the device in the past but suddenly he got the following error message:  

NTM88_lib_err.png

Can you please advise what is wrong?, BTW the $(ProjDirPath) seems to be fine and the project successfully builds and compiled.

Waiting for your kind feedback, attached extra Dianosticinfo if needed.

Regards,

Shai

 

ラベル(2)
タグ(1)
0 件の賞賛
返信
1 解決策
997件の閲覧回数
TomasVaverka
NXP TechSupport
NXP TechSupport

Hello Shai,

Here is something to try:

From what I understand, the error occurs when the target task named “NTM88_LIB” is launched.

Each task is linked to a Run Configuration. In below screenshot, the linked configuration is “Active Debug Context”, corresponding to the active Debug configuration in the workspace.

1.png

My guess is that the path to the .mem file (including $(ProjDirPath) variable) is configured in the Run configuration linked to the task. But the $(ProjDirPath) variable may not be visible in the context the task is launched.

Since configuring a path to the .mem file is not necessary, I propose to remove it. So, edit the Run Configuration, go to the Target Properties panel and untick the “Memory configuration” box.

With the box unticked as shown below, no path to the .mem file is configured.

2.png

Could you try this and let us know if it works?

Best regards,

Tomas

元の投稿で解決策を見る

0 件の賞賛
返信
2 返答(返信)
984件の閲覧回数
shai_b
Senior Contributor II

@TomasVaverka, thanks it's was very helpful.

KR,

Shai

0 件の賞賛
返信
998件の閲覧回数
TomasVaverka
NXP TechSupport
NXP TechSupport

Hello Shai,

Here is something to try:

From what I understand, the error occurs when the target task named “NTM88_LIB” is launched.

Each task is linked to a Run Configuration. In below screenshot, the linked configuration is “Active Debug Context”, corresponding to the active Debug configuration in the workspace.

1.png

My guess is that the path to the .mem file (including $(ProjDirPath) variable) is configured in the Run configuration linked to the task. But the $(ProjDirPath) variable may not be visible in the context the task is launched.

Since configuring a path to the .mem file is not necessary, I propose to remove it. So, edit the Run Configuration, go to the Target Properties panel and untick the “Memory configuration” box.

With the box unticked as shown below, no path to the .mem file is configured.

2.png

Could you try this and let us know if it works?

Best regards,

Tomas

0 件の賞賛
返信