From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 5939 invoked by alias); 21 Aug 2004 20:23:40 -0000 Mailing-List: contact ecos-maintainers-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Post: List-Help: , Sender: ecos-maintainers-owner@sources.redhat.com Received: (qmail 5931 invoked from network); 21 Aug 2004 20:23:39 -0000 Message-ID: <4127AF49.4020403@eCosCentric.com> Date: Sat, 21 Aug 2004 20:23:00 -0000 From: Jonathan Larmour User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-GB; rv:1.4) Gecko/20030703 X-Accept-Language: en-gb, en, en-us MIME-Version: 1.0 To: Udo van den Heuvel Cc: ecos-maintainers@ecos.sourceware.org Subject: Re: Hardware support References: <001a01c4875c$fba0fff0$450aa8c0@hierzo> In-Reply-To: <001a01c4875c$fba0fff0$450aa8c0@hierzo> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2004-08/txt/msg00020.txt.bz2 Udo van den Heuvel wrote: > Hello, > > I tried to build a toolchain for the CalmRISC16 (calm16_ceb) target using > the info at http://ecos.sourceware.org/ecos/build-toolchain.html but found > that the calm16 target is not supported. (errormessages, no references in > sources, responses on the eCos mailinglist, etc) > > Could you please let me know what is additionally needed to build a CalmRISC > toolchain for eCos? You're right in that I can't find any trace of a GNU toolchain made available by Samsung or publically. Note, as described at , the port was only even ever for core emulation hardware, not the real CPU. Also note that CalmRISC16 support is RedBoot-only, not eCos. Mark Salter would know more authoratitively, but your only route may be to approach Samsung directly asking for it. It does exist, but was done under contract for Samsung so they're the ones to ask. Jifl -- eCosCentric http://www.eCosCentric.com/ The eCos and RedBoot experts --["No sense being pessimistic, it wouldn't work anyway"]-- Opinions==mine