From owner-freebsd-embedded@FreeBSD.ORG Wed May 23 06:48:36 2007 Return-Path: X-Original-To: freebsd-embedded@FreeBSD.org Delivered-To: freebsd-embedded@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id BADCA16A400 for ; Wed, 23 May 2007 06:48:36 +0000 (UTC) (envelope-from krassi@bulinfo.net) Received: from mx.bulinfo.net (mx.bulinfo.net [193.194.156.1]) by mx1.freebsd.org (Postfix) with ESMTP id 3EBDF13C45A for ; Wed, 23 May 2007 06:48:35 +0000 (UTC) (envelope-from krassi@bulinfo.net) Received: from localhost (localhost [127.0.0.1]) by mx.bulinfo.net (Postfix) with ESMTP id 66BE164624; Wed, 23 May 2007 09:18:52 +0300 (EEST) Received: from mx.bulinfo.net ([127.0.0.1]) by localhost (mx.bulinfo.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 70596-01; Wed, 23 May 2007 09:18:49 +0300 (EEST) Received: from [192.168.2.188] (pythia.bulinfo.net [212.72.195.5]) by mx.bulinfo.net (Postfix) with ESMTP id 4606164620; Wed, 23 May 2007 09:18:49 +0300 (EEST) Message-ID: <4653DCC9.5060108@bulinfo.net> Date: Wed, 23 May 2007 09:18:49 +0300 From: Krassimir Slavchev User-Agent: Thunderbird 1.5 (X11/20060201) MIME-Version: 1.0 To: Warner Losh References: <465233FF.8060100@miralink.com> <20070522.094257.74690293.imp@bsdimp.com> In-Reply-To: <20070522.094257.74690293.imp@bsdimp.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: amavisd-new at mx.bulinfo.net Cc: freebsd-embedded@FreeBSD.org Subject: Re: [nanobsd] Calculation of new flash image size X-BeenThere: freebsd-embedded@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Dedicated and Embedded Systems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 May 2007 06:48:36 -0000 What about diskinfo? I always use output from diskinfo -v without any problems. Warner Losh wrote: > From: Sean Bruno > Subject: [nanobsd] Calculation of new flash image size > Date: Mon, 21 May 2007 17:06:23 -0700 > > >> If the manufacturer doesn't provide me with the specific values for >> NANO_SECTS, NANO_HEADS and NANO_MEDIASIZE, I assume that I would be able >> to use the output of fdisk to calculate it for me: >> >> fmybox# fdisk /dev/ad0 >> ******* Working on device /dev/ad0 ******* >> parameters extracted from in-core disklabel are: >> cylinders=993 heads=16 sectors/track=63 (1008 blks/cyl) >> >> parameters to be used for BIOS calculations are: >> cylinders=993 heads=16 sectors/track=63 (1008 blks/cyl) >> >> >> So in this case, NANO_SECTS=63, NANO_HEADS=16 and NANO_MEDIASIZE=(993 * >> 16 * 63)=1000944? >> >> I added the following to Flashdevices.sub: >> >> dom512m) >> # Source: sbruno@miralink.com >> NANO_MEDIASIZE=`expr 512483328 / 512` >> NANO_HEADS=16 >> NANO_SECTS=63 >> ;; >> > > The flashdevices.sub database is lame. It is a misfeature to require > it. > > >> If I do this for my new Transcend module, the system won't boot properly >> and freezes on the BTX boot loader startup. >> >> What am I doing wrong here? >> > > There's a fundamental flaw in nanobsd. That is that it requires one > to know the geometry of the target device. fdisk won't tell you this > when you are using a scsi card reader, so you can't find it out > automatically. This is because the scsi layer uses a fake geometry > here (I can't recall if it is FreeBSD software, or the card reader). > Nanobsd is supposed to use 'packet mode' so that geometry doesn't > matter. You should make sure that the CF/disk created is in packet > mode. > > If you have a card that you've re-fdisked since you bought it, dd > about 30k of zeros to the front of it from /dev/zero. Then insert it > into a camera that can do the formatting of flash cards. Put that > back into your freebsd box and run fdisk again and see what the > partitions look like. > > You'll see something that looks like: > > fdisk da0 > > ******* Working on device /dev/da0 ******* > parameters extracted from in-core disklabel are: > cylinders=CCC heads=HHH sectors/track=SSS (SSS * HHH blks/cyl) > > Figures below won't work with BIOS for partitions not in cyl 1 > parameters to be used for BIOS calculations are: > cylinders=CCC heads=HHH sectors/track=SSS (SSS * HHH blks/cyl) > > Media sector size is 512 > Warning: BIOS sector numbering starts with sector 1 > Information from DOS bootblock is: > The data for partition 1 is: > sysid 6 (0x6),(Primary 'big' DOS (>= 32MB) > start SSS, size XXX (YYY Meg), flag 80 (active) > beg: cyl 0/ head 1/ sector 1; > end: cyl CCC/ head HHH/ sector SSS > The data for partition 2 is: > > The data for partition 3 is: > > The data for partition 4 is: > > > CCC, HHH and SSS are the numbers you need. > > Also, you can put this card in your target device and look at the BIOS > in that target device. It will tell you what it thinks it is. > > Warner > _______________________________________________ > freebsd-embedded@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-embedded > To unsubscribe, send any mail to "freebsd-embedded-unsubscribe@freebsd.org" > >