From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 24914 invoked by alias); 9 Aug 2005 15:21:40 -0000 Mailing-List: contact ecos-discuss-help@ecos.sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: ecos-discuss-owner@ecos.sourceware.org Received: (qmail 24900 invoked by uid 22791); 9 Aug 2005 15:21:33 -0000 Received: from anchor-post-34.mail.demon.net (HELO anchor-post-34.mail.demon.net) (194.217.242.92) by sourceware.org (qpsmtpd/0.30-dev) with ESMTP; Tue, 09 Aug 2005 15:21:33 +0000 Received: from calivar.demon.co.uk ([83.104.54.243] helo=xl5.calivar.com) by anchor-post-34.mail.demon.net with esmtp (Exim 4.42) id 1E2Vv0-0009S7-Fy; Tue, 09 Aug 2005 15:21:31 +0000 Received: from xl5.calivar.com (localhost [127.0.0.1]) by xl5.calivar.com (Postfix) with ESMTP id 53DB4110CA; Tue, 9 Aug 2005 16:21:30 +0100 (BST) To: R Vamshi Krishna Cc: raghavendra pai g , ecos-discuss@ecos.sourceware.org References: <20050809102804.17214.qmail@webmail28.rediffmail.com> From: Nick Garnett Original-Sender: nickg@ecoscentric.com Date: Tue, 09 Aug 2005 15:21:00 -0000 In-Reply-To: Message-ID: User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Subject: Re: [ECOS] Re: eCos Grub Problem X-SW-Source: 2005-08/txt/msg00099.txt.bz2 R Vamshi Krishna writes: > > To my knowledge, on Fedora Core which Ragavendra has, > /etc/grub.conf is a link to /boot/grub/grub.conf > > So any changes in /etc/grub.conf are reflected properly in > /root/grub/grub.conf See my other response, on SuSE they appear to be different files. > > So the problem is that : > > 1. We have Redboot.elf in /boot directory > 2. We have the above mentioned menu.lst > 3. When we boot we get the afore mentioned output. > > > So far we have executed a few applications by putting redboot on the > floppy, then booting the i386 PC, using TFTP to retrieve the > application > and the execute it from redboot. > > No when we use grub, do we have to boot redboot from grub and then > execute the application. > > Can I not have the setup such that the application directly starts > running without a ROM Monitor. > > In that case my menu.lst will be > Title eCos Application (Hello) > kernel (hd0,1)/boot/Hello > > ...... > Yes, you can do this, and in fact this is the recommended way of running eCos application over GRUB. There is often not much point in using a bootloader to load a bootloader to load the application. The GRUB version of RedBoot is most useful as a development tool. See the documentation at: http://ecos.sourceware.org/docs-latest/user-guide/setup-i386-pc.html The only thing to be aware of is that without RedBoot, applications will default to doing IO only via the serial lines, they will not use the screen and keyboard. I have just tried booting a GRUB version of RedBoot from a floppy-resident GRUB here, and it all works as expected. So, I think the problems are that somehow the right partition and file name are not being suppled to GRUB. -- Nick Garnett eCos Kernel Architect http://www.ecoscentric.com The eCos and RedBoot experts -- Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss