Date: Tue, 04 Oct 2011 18:40:44 +1100 From: Mattia Rossi <mrossi@swin.edu.au> To: freebsd-arm@freebsd.org Cc: Matthieu Kraus <matthieu.kraus@s2008.tu-chemnitz.de> Subject: Re: freebsd-arm Digest, Vol 286, Issue 5 Message-ID: <4E8AB87C.7080202@swin.edu.au> In-Reply-To: <20111001122747.20873v82axd8cq3n@mail.tu-chemnitz.de> References: <20110930120022.4ABAA10656A7@hub.freebsd.org> <20110930173253.55166lqso9c8zvad@mail.tu-chemnitz.de> <op.v2mv1onei1oka3@ntai.abinitio.com> <4E86DBCD.6020909@swin.edu.au> <20111001122747.20873v82axd8cq3n@mail.tu-chemnitz.de>
next in thread | previous in thread | raw e-mail | index | archive | help
Ok, at least I got the kernel to start, but now it hangs.
I'm using the DREAMPLUG kernconf and the dreamplug.dts file (Again,
thanks Matthieu!) and include std.db88f6xxx
This is where I got to:
--- output start ---
Marvell>> tftpboot 0x900000 kernel.bin
No link on egiga0
Using egiga1 device
TFTP from server 192.168.12.81; our IP address is 192.168.12.80
Filename 'kernel.bin'.
Load address: 0x900000
Loading: #################################################################
#################################################################
#################################################################
#################################################################
##############################
done
Bytes transferred = 4248696 (40d478 hex)
Marvell>> go 0x900000
## Starting application at 0x00900000 ...
dtbp = 0xc0cd8708
KDB: debugger backends: ddb
KDB: current backend: ddb
Copyright (c) 1992-2011 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 is a registered trademark of The FreeBSD Foundation.
FreeBSD 10.0-CURRENT #10 r225870: Tue Oct 4 17:40:25 EST 2011
root@freebsd82fresh.matnina:/usr/obj/arm.arm/usr/devel/sys/DREAMPLUG arm
module mvs already present!
CPU: Feroceon 88FR131 rev 1 (Marvell core)
DC enabled IC enabled WB enabled EABT branch prediction enabled
16KB/32B 4-way Instruction cache
16KB/32B 4-way write-back-locking-C Data cache
real memory = 536870912 (512 MB)
avail memory = 518946816 (494 MB)
SOC: Marvell 88F6281 rev A1, TClock 200MHz
simplebus0: <Flattened device tree simple bus> on fdtbus0
ic0: <Marvell Integrated Interrupt Controller> mem 0xf1020200-0xf102023b
on sim0
timer0: <Marvell CPU Timer> mem 0xf1020300-0xf102032f irq 1 on simplebus0
Event timer "CPUTimer0" frequency 200000000 Hz quality 1000
Timecounter "CPUTimer1" frequency 200000000 Hz quality 1000
gpio0: <Marvell Integrated GPIO Controller> mem 0xf1010100-0xf101011f
irq 35,360
device_attach: gpio0 attach returned 6
rtc0: <Marvell Integrated RTC> mem 0xf1010300-0xf1010307 on simplebus0
twsi0: <Marvell Integrated I2C Bus Controller> mem 0xf1011000-0xf101101f
irq 430
iicbus0: <Philips I2C bus> on twsi0
iic0: <I2C generic I/O> on iicbus0
mge0: <Marvell Gigabit Ethernet controller> mem 0xf1072000-0xf1073fff
irq 12,130
mge0: Ethernet address: f0:ad:4e:00:84:c7
miibus0: <MII bus> on mge0
e1000phy0: <Marvell 88E1116R Gigabit PHY> PHY 0 on miibus0
e1000phy0: none, 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX,
1000baseT, 10o
mge1: <Marvell Gigabit Ethernet controller> mem 0xf1074000-0xf1075fff
irq 16,170
miibus1: <MII bus> on mge1
e1000phy1: <Marvell 88E1116R Gigabit PHY> PHY 1 on miibus1
e1000phy1: none, 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX,
1000baseT, 10o
uart0: <16550 or compatible> mem 0xf1012000-0xf101201f irq 33 on simplebus0
uart0: console (1056,n,8,1)
uart1: <16550 or compatible> mem 0xf1012100-0xf101211f irq 34 on simplebus0
ehci0: <Marvell Integrated USB 2.0 controller> mem 0xf1050000-0xf1050fff
irq 480
usbus0: EHCI version 1.0
usbus0: stop timeout
usbus0: set host controller mode
--- output end ---
What should come next after loading the USB drivers? I suspect it's the
SATA bits.. can anyone confirm that?
In the .dts file, after the statements for the USB stuff there are the
xor, sata and sdio bits, which haven't been loaded. I believe there's a
mismatch somewhere.
Can anyone tell me where the hell I can find the documentation with the
specifications of the dreamplug? That would help to fix these issues I
believe..
Mat
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4E8AB87C.7080202>