Date: Tue, 12 Nov 2013 08:09:30 +0100 From: Hans Petter Selasky <hps@bitfrost.no> To: Boris Astardzhiev <boris.astardzhiev@gmail.com>, freebsd-arm@freebsd.org, freebsd-hackers@freebsd.org Subject: Re: ARM kgdb remote debugging over USB serial Message-ID: <5281D42A.6050904@bitfrost.no> In-Reply-To: <CAP=KkTwhPyPazTq1uW1qrM6fHeO7Gyrzjc-Pk4Y1Us-e7J4_oQ@mail.gmail.com> References: <CAP=KkTwhPyPazTq1uW1qrM6fHeO7Gyrzjc-Pk4Y1Us-e7J4_oQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 11/09/13 19:05, Boris Astardzhiev wrote: > Hi, > > I have a question regarding the FreeBSD kernel debugging facilities. > Has anyone succeeded in using kgdb with a target ARM machine over a USB > serial. > I've managed to build kgdb-arm > > http://bsdimp.blogspot.com/2007/10/cross-debugger.html > (This tutorial also applies to building kgdb-arm in binutils) > > So on the arm machine I enter kdb: > db> gdb > db> s > .. > > On the debugging machine I easily get into kgdb: > kgdb-arm ${KERNEL_PATH}/kernel.debug > kgdb> set remotebaud 115200 > kgdb> target remote /dev/cuaU0 (the USB interface) > > So far so good but.. It seems to connect to the ARM device but it stops on > an address kgdb has no > reference about. I thought I was missing some symbols and.. > kgdb> set solib-search-path ${KERNEL_PATH} > > This seems to load lots of symbols but still I can't backtrace or do > anything. Attempting to do a 'bt' it tells me I got a SIGTRAP. I don't seem > to understand. > > Any ideas or materials? > > Greetings, > Boris Hi, Maybe there are some bits missing in the USB serial glue part? You can try making the USB serial port the console by setting the sysctls listed below correctly. Will also work in the panic prompt: hw.usb.ucom.cons_baud: 9600 hw.usb.ucom.cons_subunit: 0 hw.usb.ucom.cons_unit: -1 --HPS
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5281D42A.6050904>