Date: Thu, 24 Aug 2006 17:52:08 +0200 From: Bernd Walter <ticso@cicely12.cicely.de> To: freebsd-arm@freebsd.org Cc: Bernd Walter <ticso@cicely12.cicely.de> Subject: Re: AT91RM9200 problem Message-ID: <20060824155207.GM49178@cicely12.cicely.de> In-Reply-To: <20060823175736.GE47093@cicely12.cicely.de> References: <20060823175736.GE47093@cicely12.cicely.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Aug 23, 2006 at 07:57:37PM +0200, Bernd Walter wrote:
> >e 0x20000000
> KDB: debugger backends: ddb
> KDB: current backend: ddb
> Copyright (c) 1992-2006 The FreeBSD Project.
> Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
> The Regents of the University of California. All rights reserved.
> FreeBSD 7.0-CURRENT #4: Wed Aug 23 19:47:16 CEST 2006
> ticso@cicely7.cicely.de:/FreeBSD-arm-src/src/sys/arm/compile/BWCT
> CPU: ARM920T rev 0 (ARM9TDMI core)
> DC enabled IC enabled WB enabled LABT
> 16KB/32B 64-way Instruction cache
> 16KB/32B 64-way write-back-locking-A Data cache
> real memory = 67108864 (64 MB)
> avail memory = 62603264 (59 MB)
> panic: Cannot allocate L1 KVM
> KDB: enter: panic
>
> This is a prototype board, so hardware problems are not impossible.
It was a hardware problem with power distribution to the SDRAM chips.
My next problem ist ethernet.
>e 0x20000000
KDB: debugger backends: ddb
KDB: current backend: ddb
Copyright (c) 1992-2006 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
The Regents of the University of California. All rights reserved.
FreeBSD 7.0-CURRENT #6: Thu Aug 24 06:06:58 CEST 2006
ticso@cicely7.cicely.de:/FreeBSD-arm-src/src/sys/arm/compile/BWCT
CPU: ARM920T rev 0 (ARM9TDMI core)
DC enabled IC enabled WB enabled LABT
16KB/32B 64-way Instruction cache
16KB/32B 64-way write-back-locking-A Data cache
real memory = 67108864 (64 MB)
avail memory = 62586880 (59 MB)
CONFIG: invalid hint 'hint.ohci.at=apb'
CONFIG: invalid hint 'hint.ohci.maddr=0x00300000'
atmelarm0: <AT91RM9200 device bus> on motherboard
at91_st0: <ST> mem 0xfffffd00-0xfffffdff irq 1 on atmelarm0
at91_st0: watchdog registered, timeout intervall max. 64 sec
at91_pio0: <PIOA> mem 0xfffff400-0xfffff5ff irq 1 on atmelarm0
at91_pio0: ABSR: 0x60 OSR: 0 PSR:0x3f380010 ODSR: 0
at91_pio0: [FAST]
at91_pio1: <PIOB> mem 0xfffff600-0xfffff7ff irq 1 on atmelarm0
at91_pio1: ABSR: 0xff300 OSR: 0 PSR:0x3fc00cff ODSR: 0
at91_pio1: [FAST]
at91_pio2: <PIOC> mem 0xfffff800-0xfffff9ff irq 1 on atmelarm0
at91_pio2: ABSR: 0 OSR: 0x400 PSR:0xc47f ODSR: 0
at91_pio2: [FAST]
at91_pio3: <PIOD> mem 0xfffffa00-0xfffffbff irq 1 on atmelarm0
at91_pio3: ABSR: 0 OSR: 0 PSR:0xfffffff ODSR: 0
at91_pio3: [FAST]
at91_pmc0: <PMC> mem 0xfffffc00-0xfffffcff irq 1 on atmelarm0
at91_pmc0: main clock: 10000000 Hz PLLA: 112 MHz CPU: 112 MHz main 37 MHz
at91_rtc0: <RTC> mem 0xfffffe00-0xfffffeff irq 1 on atmelarm0
at91_rtc0: [FAST]
at91_twi0: <TWI> mem 0xfffb8000-0xfffbbfff irq 12 on atmelarm0
iicbus0: <Philips I2C bus> on at91_twi0
iicsmb0: <SMBus over I2C bridge> on iicbus0
smbus0: <System Management Bus> on iicsmb0
smb0: <SMBus generic I/O> on smbus0
ate0: <EMAC> mem 0xfffbc000-0xfffbffff irq 24 on atmelarm0
miibus0: <MII bus> on ate0
ukphy0: <Generic IEEE 802.3u media interface> on miibus0
ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
ate0: Ethernet address: 00:0e:42:02:00:1f
uart0: <DBGU> mem 0xfffff200-0xfffff3ff irq 1 on atmelarm0
uart0: [FAST]Ķuart0: console (115200,n,8,1)
uart1: <USART0> mem 0xfffc0000-0xfffc3fff irq 6 on atmelarm0
uart1: [FAST]
uart2: <USART1> mem 0xfffc4000-0xfffc7fff irq 7 on atmelarm0
uart2: [FAST]
uart3: <USART2> mem 0xfffc8000-0xfffcbfff irq 8 on atmelarm0
uart3: [FAST]
uart4: <USART3> mem 0xfffcc000-0xfffcffff irq 9 on atmelarm0
uart4: [FAST]
at91_spi0: <SPI> mem 0xfffe0000-0xfffe3fff irq 13 on atmelarm0
spibus0: <spibus bus> on at91_spi0
Cannot get 100 Hz clock; using 128Hz
at91_st0: [FAST]
Timecounter "AT91RM9200 timer" frequency 32768 Hz quality 1000
Timecounters tick every 7.812 msec
Sending DHCP Discover packet from interface ate0 (00:0e:42:02:00:1f)
ate0: link state changed to DOWN
ate0: link state changed to UP
DHCP/BOOTP timeout for server 255.255.255.255
DHCP/BOOTP timeout for server 255.255.255.255
I see the packets on the DHCP-server:
17:48:24.996668 IP (tos 0x0, ttl 1, id 30, offset 0, flags [none], proto: UDP (17), length: 1488) 0.0.0.0.68 > 255.255.255.255.67: [udp sum ok] BOOTP/DHCP, Request from 00:0e:42:02:00:1f, length: 1460, xid:0xffff0001, secs:137, flags: [Broadcast] (0x8000)
Client Ethernet Address: 00:0e:42:02:00:1f
Vendor-rfc1048:
MSZ:1460
VC:"FreeBSD:arm:7.0-CURRENT"
DHCP:DISCOVER
17:48:25.001473 IP (tos 0x10, ttl 16, id 0, offset 0, flags [none], proto: UDP (17), length: 391) 85.159.14.49.67 > 255.255.255.255.68: [udp sum ok] BOOTP/DHCP, Reply, length: 363, xid:0xffff0001, secs:137, flags: [Broadcast] (0x8000)
Your IP: 85.159.14.54
Server IP: 85.159.14.49
Client Ethernet Address: 00:0e:42:02:00:1f
sname "cicely11.cicely.de"
Vendor-rfc1048:
DHCP:OFFER
SID:85.159.14.49
LT:86400
SM:255.255.255.248
DG:85.159.14.49
NS:10.1.1.8,10.1.1.7
HN:"test-54.bwct.de^@"
RP:"85.159.14.49:/var/d6/arm-boot/"
RN:43200
RB:75600
BR:85.159.14.55
NTP:10.1.1.10
DN:"cicely.de"
And I can see via scope that packets are transfered via MII
to the MAC, nevertheless the kernel complains about timeouts.
bootspi shows the same: ARP requests are send out repeatetly as if
nothing was received.
--
B.Walter http://www.bwct.de http://www.fizon.de
bernd@bwct.de info@bwct.de support@fizon.de
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060824155207.GM49178>