s32k146 jlink connect error

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

s32k146 jlink connect error

ソリューションへジャンプ
4,045件の閲覧回数
frank-li2021
Contributor III

frankli2021_0-1636612537972.png

each time it'll be ok if re-connect the jlink usb again, before start a new debug session with s32 design studio.

 

it show in IDE:

Checking target voltage...
Target voltage: 3.31 V
Listening on TCP/IP port 2331
Connecting to target...WARNING: CPU could not be halted
WARNING: CPU could not be halted
WARNING: CPU could not be halted
WARNING: CPU could not be halted
WARNING: CPU could not be halted
WARNING: CPU could not be halted
Halting target device failed. Trying again with reset
WARNING: CPU could not be halted
WARNING: CPU could not be halted
WARNING: CPU could not be halted
WARNING: CPU could not be halted
WARNING: CPU could not be halted
Failed to halt target device on connect
ERROR: Could not connect to target.
Target connection failed. GDBServer will be closed...Restoring target state and closing J-Link connection...
Shutting down...
Could not connect to target.
Please check power, connection and settings.

 

0 件の賞賛
返信
1 解決策
4,031件の閲覧回数
danielmartynek
NXP TechSupport
NXP TechSupport

Hello @frank-li2021,

Can you please contact SEGGER support?

It seems like an issue with the j-link probe if it needs to reset every time.

 

BR, Daniel

元の投稿で解決策を見る

0 件の賞賛
返信
2 返答(返信)
3,108件の閲覧回数
dongni
Contributor II

hello, how about this problem? I have the same problem as you, can you share me how to solve it, thank you@frank-li2021

0 件の賞賛
返信
4,032件の閲覧回数
danielmartynek
NXP TechSupport
NXP TechSupport

Hello @frank-li2021,

Can you please contact SEGGER support?

It seems like an issue with the j-link probe if it needs to reset every time.

 

BR, Daniel

0 件の賞賛
返信