S32Z2 Python script error issue

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

S32Z2 Python script error issue

930 Views
jack_huang1
Contributor IV

Dear;

       The customer uses NXP S32Z2 to design a real-time computing board, and the IDE uses NXP S32DS. 3.6.3. Currently, during debugging, occasional S32Z2 Python script error issues occur, with the specific phenomenon being "failure during execution of Python script", as shown in Figure 1. The relevant error log information is as follows:

        540,987 1-list-features
541,001 1^done,features=["frozen-varobjs","pending-breakpoints","thread-info","data-read-memory-byte\
s","breakpoint-notifications","ada-task-info","language-option","info-gdb-mi-command","undefined-com\
mand-error-code","exec-run-start-option","data-disassemble-a-option","simple-values-ref-types","pyth\
on"]
541,002 (gdb)
541,142 2-list-thread-groups
541,142 3-gdb-version
541,150 2^done,groups=[{id="i1",type="process"}]
541,150 (gdb)
541,151 ~"GNU gdb (GDB src=ga98a3c7ad40 bld=ga98a3c7ad40 ) 15.1\n"
541,151 ~"Copyright (C) 2024 Free Software Foundation, Inc.\n"
541,151 ~"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."
541,151 ~"\nType \"show copying\" and \"show warranty\" for details.\n"
541,151 ~"This GDB was configured as \"--host=x86_64-w64-mingw32 --target=arm-none-eabi\".\n"
541,151 ~"Type \"show configuration\" for configuration details.\n"
541,151 ~"For bug reporting instructions, please see:\n"
541,151 ~"<https://www.gnu.org/software/gdb/bugs/>.\n"
541,151 ~"Find the GDB manual and other documentation resources online at:\n <"
541,151 ~"http://www.gnu.org/software/gdb/documentation/>.\n\n"
541,151 ~"For help, type \"help\".\n"
541,151 ~"Type \"apropos word\" to search for commands related to \"word\".\n"
541,151 3^done
541,151 (gdb)
541,151 4-environment-cd C:/Users/developer/Desktop/MyWorkspace/modifiedPlatform/100713_PLT_COM_S32Z\
280_R52_Core
541,166 4^done
541,166 (gdb)
541,166 5-gdb-set breakpoint pending on
541,166 5^done
541,167 (gdb)
541,167 6-gdb-set detach-on-fork on
541,167 6^done
541,167 (gdb)
541,167 7-enable-pretty-printing
541,167 7^done
541,167 (gdb)
541,167 8-gdb-set python print-stack none
541,167 8^done
541,167 (gdb)
541,168 9-gdb-set print object on
541,168 9^done
541,168 (gdb)
541,168 10-gdb-set print sevenbit-strings on
541,169 10^done
541,169 (gdb)
541,169 11-gdb-set host-charset UTF-8
541,169 11^done
541,169 (gdb)
541,169 12-gdb-set target-charset GBK
541,170 12^done
541,170 (gdb)
541,170 13-gdb-set target-wide-charset UTF-16
541,170 13^done
541,170 (gdb)
541,170 14-gdb-set dprintf-style call
541,170 14^done
541,170 (gdb)
541,170 15source .gdbinit
541,171 &"source .gdbinit\n"
541,171 &".gdbinit: No such file or directory.\n"
541,171 15^error,msg=".gdbinit: No such file or directory."
541,171 (gdb)
541,171 16-gdb-set mi-async off
541,171 16^done
541,171 (gdb)
541,172 17-gdb-set record full stop-at-limit off
541,173 17^done
541,173 (gdb)
541,173 18-gdb-set auto-solib-add on
541,173 18^done
541,173 (gdb)
541,174 19-gdb-set substitute-path C:\\Users\\tgp\\Documents\\Platform_SW_git\\COM_Lane\\COM_PFCC_S3\
2Z280_Platform_SW_Core_R52\\Debug_RAM/../Project_Settings/Startup_Code/ C:\\Users\\developer\\Deskto\
p\\MyWorkspace\\modifiedPlatform\\100713_PLT_COM_S32Z280_R52_Core\\Project_Settings\\Startup_Code\\
541,174 20-gdb-set substitute-path C:\\Users\\tgp\\Documents\\Platform_SW_git\\COM_Lane\\COM_PFCC_S3\
2Z280_Platform_SW_Core_R52\\Debug_RAM/../include/ C:\\Users\\developer\\Desktop\\MyWorkspace\\modifi\
edPlatform\\100713_PLT_COM_S32Z280_R52_Core\\include\\
541,204 21-gdb-set substitute-path C:\\Users\\tgp\\Documents\\Platform_SW_git\\COM_Lane\\COM_PFCC_S3\
541,204 19^done
541,204 (gdb)
2Z280_Platform_SW_Core_R52\\Debug_RAM/../src/ C:\\Users\\developer\\Desktop\\MyWorkspace\\modifiedPl\
atform\\100713_PLT_COM_S32Z280_R52_Core\\src\\
541,205 20^done
541,205 (gdb)
541,206 21^done
541,206 (gdb)
541,207 22py _IS_LOGGING_ENABLED = True
541,207 23py _REMOTE_TIMEOUT = 30
541,207 24py _CORE_NAME = "S32Z280_R52_0_0"
541,207 25py _SOC_NAME = "S32Z280"
541,207 26py _GDB_SERVER_PORT = 45000
541,207 27py _JTAG_SPEED = 16000
541,207 28py _RESET_DELAY = 0
541,207 29py _PROBE_IP = "s32dbg:usb#00:04:9f:08:bc:b1"
541,207 30py _CCS_IP = "127.0.0.1"
541,207 31py _CCS_PORT = 41475
541,207 32source C:\NXP\S32DS.3.6.3\eclipse\../S32DS/tools/S32Debugger/Debugger/scripts/s32z2e2/s32z\
2e2_attach.py
541,234 &"py _IS_LOGGING_ENABLED = True\n"
541,234 22^done
541,234 (gdb)
541,235 &"py _REMOTE_TIMEOUT = 30\n"
541,235 23^done
541,235 (gdb)
541,235 &"py _CORE_NAME = \"S32Z280_R52_0_0\"\n"
541,235 24^done
541,235 (gdb)
541,235 &"py _SOC_NAME = \"S32Z280\"\n"
541,235 25^done
541,235 (gdb)
541,236 &"py _GDB_SERVER_PORT = 45000\n"
541,236 26^done
541,236 (gdb)
541,236 &"py _JTAG_SPEED = 16000\n"
541,236 27^done
541,236 (gdb)
541,236 &"py _RESET_DELAY = 0\n"
541,236 28^done
541,236 (gdb)
541,237 &"py _PROBE_IP = \"s32dbg:usb#00:04:9f:08:bc:b1\"\n"
541,237 29^done
541,237 (gdb)
541,237 &"py _CCS_IP = \"127.0.0.1\"\n"
541,238 30^done
541,238 (gdb)
541,238 &"py _CCS_PORT = 41475\n"
541,238 31^done
541,238 (gdb)
541,238 &"source C:\\NXP\\S32DS.3.6.3\\eclipse\\../S32DS/tools/S32Debugger/Debugger/scripts/s32z2e2/\
s32z2e2_attach.py\n"
541,300 =cmd-param-changed,param="pagination",value="off"
541,306 32^done
541,306 (gdb)
541,306 33py board_init()
541,306 &"py board_init()\n"
541,307 ~"... board_init() skipped.\n"
541,307 33^done
541,307 (gdb)
541,307 34py core_init()
541,331 &"py core_init()\n"
541,331 ~"Selected CORE=S32Z280_R52_0_0\n"
541,347 ~"Primary session connecting...\n"
541,360 =cmd-param-changed,param="remotetimeout",value="30"
545,535 ~"^Error:Target connection failed. Please re-check the settings."
545,535 ~"Processor: S32S250"
545,535 ~"Probe: S32 Debugger TAP (usb#00:04:9f:08:bc:b1)"
545,535 ~"[CCS: Bus error]"
545,535 ~"//"
545,535 ~"Additional error details:"
545,535 ~"[GTA: target access error]"
545,535 ~":GtaTaErr(1303)"
545,535 ~" File \"<string>\", line 1, in <module>"
545,535 ~" File \"C:\\NXP\\S32DS.3.6.3\\eclipse\\../S32DS/tools/S32Debugger/Debugger/scripts/s32z2e\
2/s32z2e2_attach.py\", line 80, in core_init"
545,536 ~" connect()"
545,536 ~" File \"C:\\NXP\\S32DS.3.6.3\\eclipse\\../S32DS/tools/S32Debugger/Debugger/scripts/s32z2e\
2/s32z2e2_attach.py\", line 52, in connect"
545,536 ~" gta_lib.establish_connection("
545,536 ~" File \"C:\\NXP\\S32DS.3.6.3\\S32DS\\tools\\S32Debugger\\Debugger\\scripts\\s32z2e2//../u\
tils\\gta_lib.py\", line 89, in establish_connection"
545,536 ~" return connect("
545,536 ~" File \"C:\\NXP\\S32DS.3.6.3\\S32DS\\tools\\S32Debugger\\Debugger\\scripts\\s32z2e2//../u\
tils\\errors.py\", line 275, in wrapper"
545,537 ~" v = func(*args, **kwargs)"
545,537 ~" File \"C:\\NXP\\S32DS.3.6.3\\S32DS\\tools\\S32Debugger\\Debugger\\scripts\\s32z2e2//../u\
tils\\gta_lib.py\", line 152, in connect"
545,537 ~" gdb_exec(\"monitor ctx connect\", from_tty=True, errcode=ErrorCode.ConnectError).unwra\
p()"
545,537 ~" File \"C:\\NXP\\S32DS.3.6.3\\S32DS\\tools\\S32Debugger\\Debugger\\scripts\\s32z2e2//../u\
tils\\mem_reg_utils.py\", line 65, in wrapper"
545,538 ~" result = Result(Error(value, str(error_msg)))"
     The red part shows an error in the debugging tool link. Is this Python script a configuration issue or a problem with the GDB tool? Please help analyze it. If there is a configuration error, is there a script file updated with Python? Thank you!

0 Kudos
Reply
3 Replies

845 Views
chenyin_h
NXP Employee
NXP Employee

Hello, @jack_huang1 

Thanks for your reply.

1. Error code 1303 sometimes is seen when debugging in S32DS, and may be solved by re-running the debug session or rebooting the board, may I know if the customer meeting this issue every time? would you please have a try after rebooting the board?

2. I understand that the customer met such issue when debugging their own code, have they seen such issue when debugging with the official demos provisioned by NXP? 

Also, I suggest retesting it with the following steps:

1. Connect the board to the S32 Debug Probe via JTAG, then connect the USB connector of the S32 Debug Probe.
2. Wait for the S32 Debug Probe TX/RX LED to start flashing green.
3. Start GDB Server. (C:\NXP\S32DS.3.6.3\S32DS\tools\S32Debugger\Debugger\Server\gta\gta.exe)
4. Power on the board and start command prompt
 
BR
Chenyin
0 Kudos
Reply

893 Views
chenyin_h
NXP Employee
NXP Employee

Hello, @jack_huang1 

Thanks for your post.

1. May I know if the customer is debugging with a custom board or some kind of EVB?

2. From the log, customer was using S32 debug probe?

3. They met this issue with specific examples/demos provided? or their own applications?

4. The script used is the default one or with any custom modifications upon it?  

 

BR

Chenyin

0 Kudos
Reply

869 Views
jack_huang1
Contributor IV

Dear Chenyin;

           The specific response is as follows:

  1. May I know if the customer is debugging with a custom board or some kind of EVB? [Tony]: Custom board(can be considered as EVB with FPGA only)
  2. From the log, customer was using S32 debug probe? [Tony]: Yes, S32 debug probe
  3. They met this issue with specific examples/demos provided? or their own applications? [Tony]:own app
  4. The script used is the default one or with any custom modifications upon it?  [Tony]: Yes, s32z2e2_attach.py

          Please CHeck.  Thank you!

          Best Regards!

           Jack

  

0 Kudos
Reply