From: Anton F. <AD....@gm...> - 2010-04-05 09:27:40
|
Hello, Please see logs of OpenOCD and GDB in attached files. Anton Fedotov 2010/4/3 Anton Fedotov <AD....@gm...>: > Hello, > > Thanks for your replies. Let me tell a few words about debugging emvironment > I've used Devkit8000: http://www.armkits.com/Product/devkit8000.asp > It came with Linux preinstalled. From user guide I've taken an example > program that makes leds blink and cross-compiled it with debug symbols > included. I didn't recompile Linux kernel, but I think everything will be the > same. > > I've launched the system this way: > 1) Powered on Devkit8000 > 2) On my linux host launched OpenOCD: > sudo openocd -s /usr/local/share/openocd/ -f > interface/olimex-jtag-tiny.cfg -f target/omap3530.cfg -d 3 > 3) On cross-GDB (arm-linux-gnueabi-gdb) entered commands: > target remote localhost:3333 > monitor gdb_breakpoint_override hard > monitor omap3_dbginit omap3530.cpu > monitor halt > > Two last commands can be substituted with "monitor reset halt". Command > "monitor gdb_breakpoint_override hard" is critical. It tells gdb to use hardware > breakpoints. > > Now GDB is connected to the device and device is stoped and ready to > be debugged. > You can use usual GDB commands like: backtrace, break, step, stepi, > print, x, ... > And also Openocd commands in GDB like: monitor virt2phys, monitor mww, ... > > I'll attach some logs of debugging session on Monday. > > Anton > > 2010/4/3 Dirk Behme <dir...@go...>: >> Hi Anton, >> >> On 03.04.2010 09:16, Øyvind Harboe wrote: >>> >>> Hi Anton, >>> >>> I can't look until after easter, but it is great to see some work >>> done in this area! >> >> Yes, great! :) >> >>> Hopefully you'll get some good feedback before then and it will >>> be ready to merge soon, so we can get it tested more widely! >> >> It would be nice if you could give some short examples how you tested it. >> E.g. how to load U-Boot and Linux debugging symbols, how you initialized >> OpenOCD, where you set breakpoints etc. Maybe you like to just copy & paste >> the log of an example debugging session? >> >> Many thanks for the great work and best regards >> >> Dirk >> >> >> > |