I'm attempting to connect GDB to the GDB Server on the CodeWarrior Tap and debug a Linux Kernel remotely.
I'm able to do it using the CodeWarrior IDE. See the following:
Attach debugger to elf file in u-boot.
Debugging Linux Kernel with CodeWarrior for PA
(Thanks again yipingwang).
Now I'm attempting to do the same thing with GDB. I've edited the p1020_init.gdb file that allowed me to connect to the GDB server and debug with GDB through the CodeWarrior Tap. The file is attached.
I've created my own version of that file attempting minimize the amount of hardware initialized in the script since U-BOOT has initialized what I need. Also without resetting the system.
When I source my_gdb.init.gdb in GDB without a "mon reset system" or a flushregs on line 63:
mon jtag_chain info
0: mpc8572 in Invalid mode 0xBEAAFADA
1: Draco/m HIP8 in Execute Mode
2: Draco/m HIP8 in Execute Mode
mon get_probe_status
Connected to gdbserver FSL04CBEE:2345
Connected to CCS 10.1.1.90:41475
Connected to probe fpga
Connected to target mpc8572
and with a mon reset system I get and a flughregs on line 63:
mon jtag_chain info
mpc8572 in Debug Mode
1: Draco/m HIP8 in Debug Mode
2: Draco/m HIP8 in Debug Mode
mon get_probe_status
Connected to gdbserver FSL04CBEE:2345
Connected to CCS 10.1.1.90:41475
Connected to probe fpga
Connected to target mpc8572
How can I attach GDB with out resetting the System or deleting the memory?
Thanks :smileyhappy:
Zach
