AnsweredAssumed Answered

s32 debug probe with S32DS 3.2 latest update

Question asked by Js Ha Employee on Apr 4, 2020
Latest reply on Apr 9, 2020 by mccoin

Hello,

 

I updated S32DS with latest S32G SDK EAR 0.9 SDK, s32 debug probe is not working any more.

Target PCB is S32G-PROCEVB.

 

Till S32G SDK EAR 0.8 SDK, I could debug S32G EVB diag sw package with s32 debug probe, but after update with latest SDK, I have below error when I try debugging SW on S32G EVB with S32 debug probe. 

 

S32DS s32 debug probe failed

 

gta is listening on port 45000.
ccs_open
ipaddr = 127.0.0.1
port = 41475
timeout = 100
serverh = 0
ccs_open; ccs_error = 0
ccs_get_cc_config
serverh = 0
cc = 0
config_string =
ccs_get_cc_config; ccs_error = 23
Error message: CC not present
ccs_config_cc
serverh = 0
config_string = s32dbg:169.254.140.240
ccs_config_cc; ccs_error = 0
ccs_set_connection_timeout
serverh = 0
timeout = 100
ccs_set_connection_timeout; ccs_error = 0
ccs_config_server
serverh = 0
cc = 0
server_config = 0
value = 16000
ccs_config_server; ccs_error = 0
ccs_get_config_chain
serverh = 0
device_list: (size = 0)
ccs_get_config_chain; ccs_error = 0
ccs_config_chain
serverh = 0
cc = 0
device_list: (size = 2)
device[0]:: core_type=S32G(324)
device[1]:: core_type=DAP(232)
ccs_config_chain; ccs_error = 39
Error message: S32G: Initialization sequence is not found
ccs_get_subcore_error
serverh = 0
cc = 0
error = 73
chain_pos = 0
ccs_get_subcore_error; ccs_error = 0
ccs_config_chain
serverh = 0
cc = 0
device_list: (size = 2)
device[0]:: core_type=S32G(324)
device[1]:: core_type=DAP(232)
ccs_config_chain; ccs_error = 268435458
Error message: Initialization sequence error in command 0x2
ccs:Initialization sequence error in command 0x2

 

To be sure, I tried debugging on same S32DS version with S32V234 evb, it worked as like below

S32 debug probe working on S32V234 evb

 

Is there any hints of debugging board_init() script?

 

Thank you,

Best Regards

JS Ha

Outcomes