s32k146 jlink connect error

取消
显示结果 
显示  仅  | 搜索替代 
您的意思是: 
已解决

s32k146 jlink connect error

跳至解决方案
4,170 次查看
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,156 次查看
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,233 次查看
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,157 次查看
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 项奖励
回复