[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
[cdt-debug-dev] ARM JTAG hardware debugger setup working
|
After much mucking about, I finally managed to figure out a
way to get Eclipse CDT and JTAG hardware debugging working.
I use the "GDB server" in CDT and the gdb init script below.
The main problem when trying to get this to work is the number
of pieces to the puzzle and the wanting error messages/progress
info.
Insight scores slightly over CDT here, because I'm "closer to the metal"
and it is easier to see whats going wrong. arm-elf-gdb
in text mode is invaluable when debugging the setup.
It will be interesting to see how well this fares,
as the debug environment is quite different from the Redboot GDB stubs
that
I've been using previously.
##### Debug via Abatron BDI 2000
#
# Reset CPU
# erase flash
# program app to flash
# reset CPU
# jump to app
target remote 192.168.222.200:2001
# We need to have a really long timeout, or we get
# funky error messages
set remotetimeout 60
# It would be nice if I could program the flash in
# this startup script, but it does not work and
# I don't really understand why. Besides its
# kinda flaky and it if done interactively via telnet
# I get error messages/progress info.
#
# monitor erase
# shell sleep 2
# monitor prog
# shell sleep 2
monitor reset
shell sleep 2
set $pc=0x1020000
