From owner-freebsd-arm@FreeBSD.ORG Tue Feb 20 19:27:03 2007 Return-Path: X-Original-To: freebsd-arm@freebsd.org Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id BBFEF16C006 for ; Tue, 20 Feb 2007 19:27:03 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (vc4-2-0-87.dsl.netrack.net [199.45.160.85]) by mx1.freebsd.org (Postfix) with ESMTP id 5952F13C481 for ; Tue, 20 Feb 2007 19:27:03 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from localhost (localhost [127.0.0.1]) by harmony.bsdimp.com (8.13.4/8.13.4) with ESMTP id l1KJN9gS083014; Tue, 20 Feb 2007 12:23:09 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Tue, 20 Feb 2007 12:23:51 -0700 (MST) Message-Id: <20070220.122351.-432837306.imp@bsdimp.com> To: krassi@bulinfo.net From: "M. Warner Losh" In-Reply-To: <45DADFCD.7000209@bulinfo.net> References: <20070220075204.GI66059@x12.dk> <45DADFCD.7000209@bulinfo.net> X-Mailer: Mew version 4.2 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0 (harmony.bsdimp.com [127.0.0.1]); Tue, 20 Feb 2007 12:23:10 -0700 (MST) Cc: freebsd-arm@freebsd.org Subject: Re: What goes wrong? 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: Tue, 20 Feb 2007 19:27:03 -0000 In message: <45DADFCD.7000209@bulinfo.net> Krassimir Slavchev writes: : Try to change the BOOT_FLAVOR in the /usr/src/sys/boot/arm/at91/Makefile : : Soeren Straarup wrote: : > Hi : > : > What goes wrong when i send via serial xmodem the bootspi to the arm board : > and all i get back is some unreadable chars? : > I'm doing this from windows via teraterm at 115200 The root cause of 'unreadable' characters usually is that your board uses a different base oscillator than the board you've compiled the defaults for. The second cause can be bad memory parameters, but that's less common (it usually manifests itself in the kernel failing to print the right amount of memory). Since the PLLs that run the serial port are derived from the base christal frequency, bad things happen downstream. We should likely document these failings and how to work around them. Better yet would be to 'bloat' the boot loader a little and have it use the atmel facilities for discovering the base frequency. Bloating it to cope with different SDRAM would be a much harder task... Warner