2008-03-19 04:50:44 The kgdb can't debug with adeos
new kernel (CHINA)
Message: 52745 I can debug driver in uClinuxR1-RC2 without adeos using kgdb normally .But I patch adeos in uclinux-RC2, i can 't debug by kgdb.
This is gdb :
(gdb) target remote udp:172.26.10.234:6443
Remote debugging using udp:172.26.10.234:6443
Ignoring packet error, continuing...
warning: unrecognized item "timeout" in "qSupported" response
Ignoring packet error, continuing...
Ignoring packet error, continuing...
Ignoring packet error, continuing...
Malformed response to offset query, timeout
This is booting information:
Starting Kernel at = 19c000
Linux version 2.6.22.16-ADI-2008R1-svn (josh@josh-laptop) (gcc version 4.1.2 (ADI svn)) #99 PREEMPT Wed Mar 19 16:18:59 CST 2008
Hardware Trace Off and Disabled
Warning: limiting memory to 15MB due to hardware anomaly 05000263
Blackfin support (C) 2004-2007 Analog Devices, Inc.
Compiled for ADSP-BF537 Rev 0.2
Blackfin Linux support by http://blackfin.uclinux.org/
Processor Speed: 300 MHz core clock and 100 MHz System Clock
Board Memory: 16MB
Kernel Managed Memory: 16MB
Memory map:
text = 0x00001000-0x0013ecf0
rodata = 0x0013f000-0x00188b60
data = 0x00189000-0x0019c000
stack = 0x0018a000-0x0018c000
init = 0x0019c000-0x001ac000
bss = 0x001ac000-0x001ce640
available = 0x001ce640-0x00eff000
DMA Zone = 0x00f00000-0x01000000
Instruction Cache Enabled
Data Cache Enabled (write-through)
Built 1 zonelists. Total pages: 3802
Kernel command line: root=/dev/mtdblock2 rw rootfstype=jffs2 console=ttyBF0,115200 mtdparts=BF5xx-Flash:512k(uboot),1024k(kernel),15104k(jffs2) kgdboe=@172.26.10.234/,@172.26.10.115/
kgdboe: local port 6443
kgdboe: local IP 172.26.10.234
kgdboe: interface eth0
kgdboe: remote port 6442
kgdboe: remote IP 172.26.10.115
kgdboe: remote ethernet address ff:ff:ff:ff:ff:ff
Configuring Blackfin Priority Driven Interrupts
PID hash table entries: 64 (order: 6, 256 bytes)
I-pipe 1.7-00: pipeline enabled.
Dentry cache hash table entries: 2048 (order: 1, 8192 bytes)
Inode-cache hash table entries: 1024 (order: 0, 4096 bytes)
Memory available: 13156k/16384k RAM, (64k init code, 1271k kernel code, 510k data, 1024k dma, 360k reserved)
Blackfin Scratchpad data SRAM: 4 KB
Blackfin Data A SRAM: 16 KB (16 KB free)
Blackfin Data B SRAM: 16 KB (16 KB free)
Blackfin Instruction SRAM: 48 KB (42 KB free)
Security Framework v1.0.0 initialized
Mount-cache hash table entries: 512
NET: Registered protocol family 16
Blackfin GPIO Controller
Blackfin DMA Controller
stamp_init(): registering device resources
Generic PHY: Registered new driver
NET: Registered protocol family 2
�IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
TCP established hash table entries: 512 (order: 0, 4096 bytes)
TCP bind hash table entries: 512 (order: -1, 2048 bytes)
TCP: Hash tables configured (established 512 bind 512)
TCP reno registered
I-pipe: Domain Xenomai registered.
Xenomai: hal/blackfin started.
Xenomai: real-time nucleus v2.4.0 (Bells Of Lal) loaded.
Xenomai: starting native API services.
Xenomai: starting RTDM services.
JFFS2 version 2.2. 2001-2006 Red Hat, Inc.
io scheduler noop registered (default)
FPGALoader Init major:250
fpgaregio Init
Serial: Blackfin serial driver
bfin-uart.1: ttyBF0 at MMIO 0xffc00400 (irq = 18) is a BFIN-UART
bfin-uart.1: ttyBF1 at MMIO 0xffc02000 (irq = 20) is a BFIN-UART
RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize
SMSC LAN83C185: Registered new driver
bfin_mac_mdio: probed
bfin_mac: attached PHY driver [Generic PHY] (mii_bus:phy_addr=0:00, irq=-1, mdc_clk=2500000Hz(mdc_div=19)@sclk=100MHz)
bfin_mac: Version 1.1, Blackfin BF53[67] BF527 on-chip Ethernet MAC driver
kgdboe: device eth0 not up yet, forcing it
kgdboe: carrier detect appears untrustworthy, waiting 4 seconds
PHY: 0:00 - Link is Up - 100/Full
kgdb: debugging over ethernet enabled
BF5xx flash: probing 16-bit flash bus
BF5xx-Flash: Found 1 x16 devices at 0x0 in 16-bit bank
Amd/Fujitsu Extended Query Table at 0x0040
BF5xx-Flash: CFI does not contain boot bank location. Assuming top.
number of CFI chips: 1
cfi_cmdset_0002: Disabling erase-suspend-program due to code brokenness.
GHS FLASH was initalized already
Using static partition definition
Creating 3 MTD partitions on "BF5xx-Flash":
0x00000000-0x00080000 : "Bootloader"
0x00080000-0x00180000 : "Kernel1"
0x00180000-0x00e80000 : "JFFS2"
TCP cubic registered
NET: Registered protocol family 1
NET: Registered protocol family 17
jffs2_scan_inode_node(): CRC failed on node at 0x0079b220: Read 0xffffffff, calculated 0xecbaa51a
VFS: Mounted root (jffs2 filesystem).
Freeing unused kernel memory: 64k freed
dma_alloc_init: dma_page @ 0x00294000 - 256 pages at 0x00f00000
_____________________________________
a8888b. / Welcome to the uClinux distribution \
d888888b. / _ _ \
8P"YP"Y88 / | | |_| __ __ (TM) |
8|o||o|88 _____/ | | _ ____ _ _ \ \/ / |
8' .88 \ | | | | _ \| | | | \ / |
8`._.' Y8. \ | |__ | | | | | |_| | / \ |
d/ `8b. \ \____||_|_| |_|\____|/_/\_\ |
dP . Y8b. \ For embedded processors including |
d8:' " `::88b \ the Analog Devices Blackfin /
d8" 'Y88b \___________________________________/
:8P ' :888
8a. : _a88P For further information, check out:
._/"Yaa_: .| 88P| - http://blackfin.uclinux.org/
\ YP" `| 8P `. - http://docs.blackfin.uclinux.org/
/ \.___.d| .' - http://www.uclinux.org/
`--..__)8888P`._.' jgs/a:f - http://www.analog.com/blackfin
Have a lot of fun...
BusyBox v1.4.1 (2008-03-05 15:03:31 CST) Built-in shell (msh)
Enter 'help' for a list of built-in commands.
root:/> ifconfig eth0 172.26.10.234
QuoteReplyEditDelete
2008-03-19 05:44:21 Re: The kgdb can't debug with adeos
Sonic Zhang (CHINA)
Message: 52749
Adeos takes over all event entries from kernel. The kgdb exception may be ignored by ADEOS code. Changes are necessary to keep ADESO event entry code to work well with kgdb exception code.
QuoteReplyEditDelete
2008-03-26 08:21:54 Re: The kgdb can't debug with adeos
Paul Lau (UNITED STATES)
Message: 53050 Does it mean that once you patch the Kernel with ADEOS, you can no longer debug Kernel with KGDB. If that is the case, what are the alternatives to Kernel debugging. Would the Changes you mentioned be completed in the near future?
QuoteReplyEditDelete
2008-03-26 11:03:34 Re: The kgdb can't debug with adeos
Mike Frysinger (UNITED STATES)
Message: 53062 if you cant use the software solution of kgdb, then you need to use a jtag hardware solution in the meantime
QuoteReplyEditDelete
2008-03-27 03:48:16 Re: The kgdb can't debug with adeos
Yi Li (CHINA)
Message: 53100 Currently you may not debug adeos using KGDB. I am hoping this could be solved when kgdb is merged into mainline linux kernel (see: http://lwn.net/Articles/269378/) and upstream adeos will be updated accordingly.
For now, I think JTAG/gdbproxy could be used.