Date: Sat, 28 Mar 2015 17:39:32 +0100 From: =?windows-1252?Q?Manuel_St=FChn?= <freebsdnewbie@freenet.de> To: freebsd-arm@freebsd.org Cc: ticso@cicely.de Subject: Re: remote kernel debugging Message-ID: <5516D944.80602@freenet.de> In-Reply-To: <20150322011054.GA81780@cicely7.cicely.de> References: <550DD740.2070608@freenet.de> <20150322011054.GA81780@cicely7.cicely.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 22 Mar 2015 02:10:54 +0100, Bernd Walter wrote > The flags are documented in the uart manpage. > 0x10 flag sets the console uart and 0x80 the gdb uart. > 0x90 sets both. > But it assumes /boot/device.hints to be used, which to my knowledge isn't > true on the BBB. > The console is setup via stdin/stdout in > sys/boot/fdt/dts/arm/beaglebone.dts > No idea how gdb or any of the other flags can be entered in the DTS files. > After further investigation I found this flag for loader(8): set hw.uart.dbgport="mm:0x48022000,br:115200" # uart1 on BBB (more info in sys/dev/uart/uart_subr.c), which seems to be able to inform the debug-system about the desired uart-port. Unfortunately, when I'm setting this variable like shown above the systems stops right here: Hit [Enter] to boot immediately, or any other key for command prompt. Booting [/boot/kernel/kernel]... Using DTB provided by U-Boot at address 0x80000100. Kernel entry at 0x80200100... Kernel args: (null) GDB: debug ports: uart No further output appears, it seems that the whole system stopped at this point. Any hints? Thanks, Manuel
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5516D944.80602>