Hello Matthew Davis,
If you are using QorIQ PowerPC processors, please download and install CodeWarrior for PowerPC 10.5.1 from CodeWarrior Dev Tools for Networked Apps|NXP, CCS is in C:\Freescale\CW_PA_v10.5.1\PA\ccs\bin.
If you are using QorIQ Layerscape ARMv8 processors, please download and install CodeWarrior for ARMv8 from CodeWarrior Dev Tools for Networked Apps|NXP, CCS is in C:\Freescale\CW4NET_v2017.03\Common\CCS\bin.
If you are using LS102x processor, please download and install CodeWarrior for ARMv7 from CodeWarrior Dev Tools for Networked Apps|NXP, CCS is located in C:\Freescale\CW4NET_v2017.03\Common\CCS\bin.
We provided boards bringing up support with GDB and CodeWarrior TAP several days ago when we just started to use
CodeWarrior TAP to replace USB TAP. The document and gdb test tar ball containing boards initialization and configuration files released at that time are old, only can be used on PowerPC platforms. Then we didn't provide any
update release to customers, so we don't have gdb configuration demos for Layerscape(ARM core) processors, because we recommend customers to purchase CodeWarrior license.
For documents, you could refer to
CWTAP_GDB_GSG.pdf provided by Pavel Chubakov in https://community.nxp.com/thread/468025,
We have GDB configuration demos tar ball working with CodeWarrior TAP for PowerPC platforms, please refer to gdb_test_ccs_365 provided in the above link. If users still want to use GDB and CodeWarrior TAP to do QorIQ Layerscape brining up, they could create their own initialization and configuration files based on the existing demos for PowerPC referring to CodeWarrior initialization file.
Please refer to the video provided in http://www.nxp.com/video/board-level-bringup-using-codewarrior-tap-and-gdb:BOARDLVL_CWTAPGDB_VID.
GDB proxy setting up section is provided in the script bin/<platform>_init.gdb, after setting up gdb console, you could run the following command to connect to the target board.(gdb) source p4080_init.gdb
Please refer to the following commands to connect to gdb proxy.
(gdb) set logging off
(gdb) set debug frame 0
(gdb) set debug remote 0
(gdb) set remotetimeout 100
(gdb) set tdesc filename ../xml/power-core.xml
(gdb) target remote 10.193.20.72:2345
Remote debugging using 10.193.20.72:2345
0x00000000 in ?? ()
(gdb) mon get_probe_status
Connected to gdbserver FSL039B85:2345
Have a great day,
TIC
-----------------------------------------------------------------------------------------------------------------------
Note: If this post answers your question, please click the Correct Answer button. Thank you!
-----------------------------------------------------------------------------------------------------------------------
