From owner-freebsd-arm@FreeBSD.ORG Thu May 15 16:59:24 2008 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 82D82106564A for ; Thu, 15 May 2008 16:59:24 +0000 (UTC) (envelope-from sam@freebsd.org) Received: from ebb.errno.com (ebb.errno.com [69.12.149.25]) by mx1.freebsd.org (Postfix) with ESMTP id 3FE358FC18 for ; Thu, 15 May 2008 16:59:24 +0000 (UTC) (envelope-from sam@freebsd.org) Received: from Macintosh-3.local (039sub223.uottawa.ca [137.122.39.151]) (authenticated bits=0) by ebb.errno.com (8.13.6/8.12.6) with ESMTP id m4FGU2oX078037 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 15 May 2008 09:30:04 -0700 (PDT) (envelope-from sam@freebsd.org) Message-ID: <482C6504.1010209@freebsd.org> Date: Thu, 15 May 2008 12:29:56 -0400 From: Sam Leffler Organization: FreeBSD Project User-Agent: Thunderbird 2.0.0.14 (Macintosh/20080421) MIME-Version: 1.0 To: Michael Fuckner References: <482A9E8E.5050407@fuckner.net> In-Reply-To: <482A9E8E.5050407@fuckner.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-DCC-Rhyolite-Metrics: ebb.errno.com; whitelist Cc: freebsd-arm@freebsd.org Subject: Re: Horstbox DVA-G3342SB with FreeBSD X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the StrongARM Processor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 May 2008 16:59:24 -0000 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@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: on motherboard > pcib0: on ixp0 > pci0: 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: at device 12.0 (no driver attached) > pci0: at device 13.0 (no driver attached) > ohci0: 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: 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: 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: on ixp0 > ixpiic0: on ixp0 > iicbb0: on ixpiic0 > iicbus0: on iicbb0 master-only > iicbus0: at addr 0 > iic0: on iicbus0 > ad74180: at addr 0x50 on iicbus0 > ds16720: at addr 0xd0 on iicbus0 > ixpwdog0: on ixp0 > uart0: on ixp0 > uart0: [FILTER] > uart0: console (115200,n,8,1) > uart1: on ixp0 > uart1: [FILTER] Looks like most of your issues stem from the PCI support not being setup as expected. Sam