Milind Dumbare wrote:
> Look at these lines in dmesg
> eth0: Setting MAC address to 00:04:9f:22:22:22
> I guess this is causing problem.
>
> -Miline
I removed that configuration from rc.sysinit
The following is the ouput.
eth0: Link now 100-FullDuplex
eth0: AT91 ethernet at 0xfefbc000 int=24 100-FullDuplex (14:f0:9f:e5:14:f0)
eth0: Davicom 9161 PHY (Copper)
kgdboe: local port 6442
kgdboe: local IP 192.168.0.201
kgdboe: interface eth0
kgdboe: remote port 6443
kgdboe: remote IP 192.168.0.169
kgdboe: remote ethernet address 00:16:76:b4:16:30
kgdboe: device eth0 not up yet, forcing it
eth0: Link now 100-FullDuplex
kgdboe: carrier detect appears untrustworthy, waiting 4 seconds
kgdboe: debugging over ethernet enabled
ifconfig outputs the following
eth0 Link encap:Ethernet HWaddr 14:F0:9F:E5:14:F0
inet addr:192.168.0.201 Bcast:192.168.0.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:67 errors:0 dropped:0 overruns:0 frame:0
TX packets:23 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:6497 (6.3 KiB) TX bytes:2098 (2.0 KiB)
Interrupt:24 Base address:0xc000
Still I have problems connecting to the target.
As discussed here:
http://www.mail-archive.com/[email protected]/msg01255.html
Mr. Matt says
"
Hmmm, 6443 != 6433 (typo?) and 32785 != 6442 (config problem).
"
which config problem? Kernel configuration or the cross-gdb configuration?
Regards
--Himanshu
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Kgdb-bugreport mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/kgdb-bugreport
