Horstbox DVA-G3342SB with FreeBSD
Sam Leffler
sam at freebsd.org
Thu May 15 16:59:24 UTC 2008
Michael Fuckner wrote:
> Hi,
>
> I am trying to boot FreeBSD on a Horstbox Professional made by Dlink.
>
> I used the instructions from http://wiki.freebsd.org/FreeBSDAvila
>
>
> - Do I still need npe-firmware or does FreeBSD simply use the one
> uuencoded in the source tree?
The firmware image in the src tree should work.
> - where do I get information about the memory regions used in kernel
> configuration
>
> options PHYSADDR=0x10000000
> options KERNPHYSADDR=0x10200000
> options KERNVIRTADDR=0xc0200000 # Used in ldscript.arm
> options FLASHADDR=0x50000000
> options LOADERRAMADDR=0x00000000
Not sure what you asking. The memory layout for the board should be
documented by the vendor. Much is standardized by the IXP42xx but
others are board-specific. Many memory locations are defined relative
to the base address of IXP memory boundaries in arm/xscale/ixp*/*.h.
Some bits that have been found to vary between boards are already
settable as hints (e.g. look in AVILA.hints).
>
> Long version with all details is at
> http://michael.fuckner.net/me/blog/index.php?/archives/420-Horstbox-DVA-G3342SB-with-FreeBSD.html#extended
>
>
> TIA,
> Michael!
>
> PS: This is what happenes right now:
> The Kernel boots, but in the middle, the system simply hangs.
>
> RedBoot> load -b 0x200000 kernel-horst.nfs
> Using default protocol (TFTP)
> Address offset = 0x40000000
> Entry point: 0x00200100, address range: 0x00200000-0x0054e330
> RedBoot> go
> KDB: debugger backends: ddb
> KDB: current backend: ddb
> Copyright (c) 1992-2008 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 7.0-STABLE #1: Wed May 14 07:24:11 CEST 2008
> root at g33.rebootking.de:/usr/obj/arm/samba/freebsd7-arm/src/sys/HORST
> CPU: IXP425 533MHz rev 1 (ARMv5TE) (XScale core)
> DC enabled IC enabled WB enabled LABT branch prediction enabled
> 32KB/32B 32-way Instruction cache
> 32KB/32B 32-way write-back-locking Data cache
> real memory = 67108864 (64 MB)
> avail memory = 58355712 (55 MB)
> ixp0: <Intel IXP425> on motherboard
> pcib0: <IXP425 PCI Bus> on ixp0
> pci0: <PCI bus> on pcib0
> ixppcib: no mapping for 0/12/0
> ixppcib: no mapping for 0/13/0
> ixppcib: no mapping for 0/14/0
> ixppcib: no mapping for 0/14/1
> ixppcib: no mapping for 0/14/2
This indicates the mapping isn't recognized/handled. Not sure if this
is because your hardware is different or the system is reading
information from the wrong memory locations.
> pci0: <network> at device 12.0 (no driver attached)
> pci0: <network> at device 13.0 (no driver attached)
> ohci0: <NEC uPD 9210 USB controller> irq -1 at device 14.0 on pci0
> ixppcib: no mapping for 0/14/0
> ohci0: Could not allocate irq
> pcib0: ohci0 called release_resource
> device_attach: ohci0 attach returned 6
> ohci1: <NEC uPD 9210 USB controller> irq -1 at device 14.1 on pci0
> ixppcib: no mapping for 0/14/1
> ohci1: Could not allocate irq
> pcib0: ohci1 called release_resource
> device_attach: ohci1 attach returned 6
> ehci0: <NEC uPD 720100 USB 2.0 controller> mem 0x48002200-0x480022ff irq
> -1 at device 14.2 on pci0
> pcib0: ehci0 called activate_resource
> ehci0: Could not map memory
> device_attach: ehci0 attach returned 6
> ixpclk0: <IXP425 Timer> on ixp0
> ixpiic0: <IXP425 GPIO-Based I2C Interface> on ixp0
> iicbb0: <I2C bit-banging driver> on ixpiic0
> iicbus0: <Philips I2C bus> on iicbb0 master-only
> iicbus0: <unknown card> at addr 0
> iic0: <I2C generic I/O> on iicbus0
> ad74180: <Analog Devices AD7418 ADC> at addr 0x50 on iicbus0
> ds16720: <Dallas Semiconductor DS1672 RTC> at addr 0xd0 on iicbus0
> ixpwdog0: <IXP425 Watchdog Timer> on ixp0
> uart0: <Non-standard ns8250 class UART with FIFOs> on ixp0
> uart0: [FILTER]
> uart0: console (115200,n,8,1)
> uart1: <Non-standard ns8250 class UART with FIFOs> on ixp0
> uart1: [FILTER]
Looks like most of your issues stem from the PCI support not being setup
as expected.
Sam
More information about the freebsd-arm
mailing list