S32 Debug Probe can't connect S32G274

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

S32 Debug Probe can't connect S32G274

155 Views
lany
Contributor I

Hi,

    S32 DS for S32 V3.6.2 , and RTD V5.0.0 for S32 G2 M7 Core.

    Import RTD example Project into S32 DS V3.6.2 and compiled , connect S32 Debug probe through Ethernet. before debug, I try 'Test connection' in Debug Configuration and get the infomation back successfully. But when I try Debug,  the S32-DP can't connect to the S32G274.s32ds.png

Here is the full log of the gdb traces.

405,868 2-gdb-version
405,875 ~"GNU gdb (GDB src=ga98a3c7ad40 bld=ga98a3c7ad40 ) 15.1\n"
405,875 ~"Copyright (C) 2024 Free Software Foundation, Inc.\n"
405,875 ~"License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>\nThis is fre\
e software: you are free to change and redistribute it.\nThere is NO WARRANTY, to the extent permitt\
ed by law."
405,875 ~"\nType \"show copying\" and \"show warranty\" for details.\n"
405,875 ~"This GDB was configured as \"--host=x86_64-w64-mingw32 --target=arm-none-eabi\".\n"
405,875 ~"Type \"show configuration\" for configuration details.\n"
405,875 ~"For bug reporting instructions, please see:\n"
405,876 ~"<https://www.gnu.org/software/gdb/bugs/>.\n"
405,876 ~"Find the GDB manual and other documentation resources online at:\n <"
405,876 ~"http://www.gnu.org/software/gdb/documentation/>.\n\n"
405,876 ~"For help, type \"help\".\n"
405,876 ~"Type \"apropos word\" to search for commands related to \"word\".\n"
405,876 2^done
405,876 (gdb)
405,876 3-environment-cd E:/Users/Lenovo/workspaceS32DS.3.6.2/test_lany/test_lany_M7_0
405,887 3^done
405,887 (gdb)
405,887 4-gdb-set breakpoint pending on
405,898 4^done
405,898 (gdb)
405,898 5-gdb-set detach-on-fork on
405,909 5^done
405,909 (gdb)
405,909 6-enable-pretty-printing
405,920 6^done
405,920 (gdb)
405,920 7-gdb-set python print-stack none
405,931 7^done
405,931 (gdb)
405,931 8-gdb-set print object on
405,942 8^done
405,942 (gdb)
405,942 9-gdb-set print sevenbit-strings on
405,952 9^done
405,952 (gdb)
405,952 10-gdb-set host-charset UTF-8
405,963 10^done
405,963 (gdb)
405,963 11-gdb-set target-charset GBK
405,973 11^done
405,973 (gdb)
405,973 12-gdb-set target-wide-charset UTF-16
405,984 12^done
405,984 (gdb)
405,984 13-gdb-set dprintf-style call
405,995 13^done
405,995 (gdb)
405,995 14source .gdbinit
406,006 &"source .gdbinit\n"
406,010 &".gdbinit: No such file or directory.\n"
406,010 14^error,msg=".gdbinit: No such file or directory."
406,010 (gdb)
406,010 15-gdb-set mi-async off
406,017 15^done
406,017 (gdb)
406,017 16-gdb-set record full stop-at-limit off
406,027 16^done
406,027 (gdb)
406,027 17-gdb-set auto-solib-add on
406,038 17^done
406,038 (gdb)
406,041 18py _IS_LOGGING_ENABLED = False
406,041 19py _REMOTE_TIMEOUT = 30
406,041 20py _CORE_NAME = "M7_0"
406,041 21py _SOC_NAME = "S32G274A"
406,041 22py _SOC_REVISION = "Rev2"
406,041 23py _GDB_SERVER_PORT = 45000
406,042 24py _JTAG_SPEED = 24000
406,042 25py _RESET_DELAY = 0
406,042 26py _PROBE_IP = "s32dbg:192.168.3.103"
406,042 27py _CCS_IP = "127.0.0.1"
406,042 28py _CCS_PORT = 41475
406,042 29source E:\NXP\S32DS.3.6.2\S32DS\tools\S32Debugger\Debugger\scripts\s32g2xx\s32g2xx_attach.\
py
406,049 &"py _IS_LOGGING_ENABLED = False\n"
406,049 18^done
406,049 (gdb)
406,049 &"py _REMOTE_TIMEOUT = 30\n"
406,049 19^done
406,049 (gdb)
406,049 &"py _CORE_NAME = \"M7_0\"\n"
406,049 20^done
406,049 (gdb)
406,049 &"py _SOC_NAME = \"S32G274A\"\n"
406,049 21^done
406,049 (gdb)
406,049 &"py _SOC_REVISION = \"Rev2\"\n"
406,050 22^done
406,050 (gdb)
406,050 &"py _GDB_SERVER_PORT = 45000\n"
406,050 23^done
406,050 (gdb)
406,050 &"py _JTAG_SPEED = 24000\n"
406,050 24^done
406,050 (gdb)
406,050 &"py _RESET_DELAY = 0\n"
406,051 25^done
406,051 (gdb)
406,051 &"py _PROBE_IP = \"s32dbg:192.168.3.103\"\n"
406,051 26^done
406,051 (gdb)
406,051 &"py _CCS_IP = \"127.0.0.1\"\n"
406,051 27^done
406,051 (gdb)
406,051 &"py _CCS_PORT = 41475\n"
406,051 28^done
406,051 (gdb)
406,051 &"source E:\\NXP\\S32DS.3.6.2\\S32DS\\tools\\S32Debugger\\Debugger\\scripts\\s32g2xx\\s32g2x\
x_attach.py\n"
406,189 =cmd-param-changed,param="pagination",value="off"
406,206 29^done
406,206 (gdb)
406,206 30py board_init()
406,216 &"py board_init()\n"
406,216 ~"... board_init() skipped.\n"
406,216 30^done
406,216 (gdb)
406,216 31py core_init()
406,227 &"py core_init()\n"
406,227 ~"Selected CORE=M7_0\n"
406,283 ~"Primary session connecting...\n"
406,310 =cmd-param-changed,param="remotetimeout",value="30"
410,319 ~"^Error:Target connection failed. Please re-check the settings."
410,319 ~"Processor: S32G2XX"
410,319 ~"Probe: S32 Debugger TAP (192.168.3.103)"
410,319 ~"[CCS: Error in part definition]"
410,319 ~"//"
410,319 ~"Additional error details:"
410,319 ~"[GTA: target access error]"
410,319 ~":GtaTaErr(1303)"
410,319 ~" File \"<string>\", line 1, in <module>"
410,319 ~" File \"E:\\NXP\\S32DS.3.6.2\\S32DS\\tools\\S32Debugger\\Debugger\\scripts\\s32g2xx\\s32g\
2xx_attach.py\", line 83, in core_init"
410,319 ~" connect()"
410,319 ~" File \"E:\\NXP\\S32DS.3.6.2\\S32DS\\tools\\S32Debugger\\Debugger\\scripts\\s32g2xx\\s32g\
2xx_attach.py\", line 54, in connect"
410,319 ~" gta_lib.establish_connection("
410,319 ~" File \"E:\\NXP\\S32DS.3.6.2\\S32DS\\tools\\S32Debugger\\Debugger\\scripts\\s32g2xx//../u\
tils\\gta_lib.py\", line 89, in establish_connection"
410,319 ~" return connect("
410,320 ~" File \"E:\\NXP\\S32DS.3.6.2\\S32DS\\tools\\S32Debugger\\Debugger\\scripts\\s32g2xx//../u\
tils\\errors.py\", line 275, in wrapper"
410,320 ~" v = func(*args, **kwargs)"
410,320 ~" File \"E:\\NXP\\S32DS.3.6.2\\S32DS\\tools\\S32Debugger\\Debugger\\scripts\\s32g2xx//../u\
tils\\gta_lib.py\", line 153, in connect"
410,320 ~" gdb_exec(\"monitor ctx connect\", from_tty=True, errcode=ErrorCode.ConnectError).unwra\
p()"
410,320 ~" File \"E:\\NXP\\S32DS.3.6.2\\S32DS\\tools\\S32Debugger\\Debugger\\scripts\\s32g2xx//../u\
tils\\mem_reg_utils.py\", line 65, in wrapper"
410,320 ~" result = Result(Error(value, str(error_msg)))"

Tags (2)
0 Kudos
Reply
5 Replies

101 Views
Joey_z
NXP Employee
NXP Employee

hi,lany

Thank you for contacting us.

I can find you use the project of test_lany_M7_0 in your log. Could you try to test the S32 debug Probe for using the RTD demo?

BR

Joey

0 Kudos
Reply

90 Views
lany
Contributor I

Hi, Joey

Thank for your reply.

I tried the demo from S32G AUTOSAR 4.4 RTD.

demo.png

And my debugger configurature is blow.

config_debugger.pngconfig_main.png

When I try the "test connection",  the infomation back like this:

info.png

But still, the same failure came,  this is the traces infomation.SO, it confused me a lot. I get the Soc infomation successfully above, but here looks like connection failure.What should I do next?traces.png

 

BR

Lany

0 Kudos
Reply

84 Views
Joey_z
NXP Employee
NXP Employee

hi,lany

Thank you for your information.

Do you use the RDB2 board or customer board? The S32 Debug prober function is normal on our development board?

BR

Joey

0 Kudos
Reply

80 Views
lany
Contributor I

Hi, Joey

I use customer board and have no development board.

But I have an oscilloscope, is there any possibility to figure this issue out with the oscilloscope.

of course, any other method is welcome.

BR

Lany

0 Kudos
Reply

60 Views
Joey_z
NXP Employee
NXP Employee

hi,lany

Thank you for your reply.

It is recommended to check whether there are any problems with the hardware JTAG circuit.

In addition, an oscilloscope can also be used to capture the debug signal and compare it with the standard ARM debug process signal.

BR

Joey

0 Kudos
Reply