Date: Wed, 15 Jan 2014 23:05:28 -0700 (MST) From: Warren Block <wblock@wonkity.com> To: =?ISO-8859-15?Q?Olivier_Cochard-Labb=E9?= <olivier@cochard.me> Cc: Ian Smith <smithi@nimnet.asn.au>, "freebsd-embedded@freebsd.org" <freebsd-embedded@freebsd.org> Subject: Re: Creating code slice before disk image in nanobsd Message-ID: <alpine.BSF.2.00.1401152227170.86525@wonkity.com> In-Reply-To: <CA%2Bq%2BTcqw%2BFbVtGbg_6%2B-j55R4HPGzMvhmkTktrZnyWucmpDrkA@mail.gmail.com> References: <20120629133759.GA19373@snail.casa> <20140114161533.GB19601@snail.casa> <CAJ-VmonKFEvPRimEmA8vnAbXVCYQ16yOftYhq03VJBYB5knotA@mail.gmail.com> <6027B660-1D2E-4058-B87F-83D8225F0DC3@bsdimp.com> <20140116034220.B43023@sola.nimnet.asn.au> <alpine.BSF.2.00.1401151214480.83038@wonkity.com> <CA%2Bq%2BTcqw%2BFbVtGbg_6%2B-j55R4HPGzMvhmkTktrZnyWucmpDrkA@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 16 Jan 2014, Olivier Cochard-Labbé wrote:
> On Wed, Jan 15, 2014 at 8:50 PM, Warren Block <wblock@wonkity.com> wrote:
>
>
> To create the initial MBR, probably already done before the code above:
> gpart create -s mbr ${MD}
> gpart bootcode -b ${NANO_WORLDDIR}/boot/boot ${MD}
>
>
> Regarding the remplacement of boot0cfg by gpart, the exact command that nanobsd uses is:
It was about using gpart instead of fdisk and bsdlabel. boot0cfg is
another matter.
> NANO_BOOT0CFG="-o packet -s 1 -m 3"
> NANO_BOOTLOADER="boot/boot0sio"
> boot0cfg -B -b ${NANO_WORLDDIR}/${NANO_BOOTLOADER} ${NANO_BOOT0CFG} ${MD}
>
> A PC Engines WRAP need the NANO_BOOT0CFG="-o nopacket" for booting.
>
> Does gpart bootcode support all these boot0cfg options too ? (I didn't find it in the man page).
I don't think so, at present anyway.
From owner-freebsd-embedded@FreeBSD.ORG Fri Jan 17 20:38:35 2014
Return-Path: <owner-freebsd-embedded@FreeBSD.ORG>
Delivered-To: freebsd-embedded@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
(using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
(No client certificate requested)
by hub.freebsd.org (Postfix) with ESMTPS id 554C6927;
Fri, 17 Jan 2014 20:38:35 +0000 (UTC)
Received: from onlyone.friendlyhosting.spb.ru (onlyone.friendlyhosting.spb.ru
[IPv6:2a01:4f8:131:60a2::2])
by mx1.freebsd.org (Postfix) with ESMTP id 1B2FB183D;
Fri, 17 Jan 2014 20:38:35 +0000 (UTC)
Received: from lion.home.serebryakov.spb.ru (unknown
[IPv6:2001:470:923f:1:396f:111a:890d:cdd5])
(Authenticated sender: lev@serebryakov.spb.ru)
by onlyone.friendlyhosting.spb.ru (Postfix) with ESMTPSA id EF7AC4AC2D;
Sat, 18 Jan 2014 00:38:26 +0400 (MSK)
Date: Sat, 18 Jan 2014 00:38:17 +0400
From: Lev Serebryakov <lev@FreeBSD.org>
Organization: FreeBSD
X-Priority: 3 (Normal)
Message-ID: <632415116.20140118003817@serebryakov.spb.ru>
To: freebsd-embedded@freebsd.org
Subject: True embedded developing under FreeBSD -- how to install
gcc-arm-embedded properly?
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Cc: kientzle@FreeBSD.org
X-BeenThere: freebsd-embedded@freebsd.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: lev@FreeBSD.org
List-Id: Dedicated and Embedded Systems <freebsd-embedded.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-embedded>,
<mailto:freebsd-embedded-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-embedded/>;
List-Post: <mailto:freebsd-embedded@freebsd.org>
List-Help: <mailto:freebsd-embedded-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-embedded>,
<mailto:freebsd-embedded-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 17 Jan 2014 20:38:35 -0000
Hello, Freebsd-embedded.
I want to program Coretx-M devices (STM32 and Tiva C ones) under FreeBSD.
Is here any proper way to install gcc-arm-embedded ()? It is
"arm-none-eabi" in theory, but all Linux guides suggest to install it from
https://launchpad.net/gcc-arm-embedded and not from "vanilla" binutils/gcc
source. And all guided has instructions how to install these tools from
sources, but it includes compiling gcc TWICE (!), with building newlib
in-between. I cannot see these two compilations in "devel/cross-gcc" port.
So, my questions are:
(1) Is `devel/arm-eabi-gcc' (effectivly `devel/cross-gcc') is Ok?
(2) Is here any plans to update cross-gcc to latest 4.8.x?
(3) Is here any proper way to packetize/portify gcc-arm-embedded toolchain
by receipts from gcc-arm-embedded project? I don't see any obious way to
build gcc twice in one port (wth newlib / dietlibc in between), for example.
(4) Is here any interest to have "proper embedded toolchain" port? By
"proper embedded toolchain" I mean package which will include binutils + gcc
+ libc in ONE package, as it is conventional in embedded world, where it is
not common to update separate parts of ooolchain separately.
--
// Black Lion AKA Lev Serebryakov <lev@FreeBSD.org>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.00.1401152227170.86525>