From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 13468 invoked by alias); 16 Aug 2005 14:27:41 -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 13445 invoked by uid 22791); 16 Aug 2005 14:27:37 -0000 Received: from smarthost3.mail.uk.easynet.net (HELO smarthost3.mail.uk.easynet.net) (212.135.6.13) by sourceware.org (qpsmtpd/0.30-dev) with ESMTP; Tue, 16 Aug 2005 14:27:37 +0000 Received: from [217.207.210.179] (helo=mail.hanoverdisplays.com) by smarthost3.mail.uk.easynet.net with esmtp (Exim 4.10) id 1E52Pe-000MpO-00; Tue, 16 Aug 2005 15:27:34 +0100 Content-Class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Tue, 16 Aug 2005 14:27:00 -0000 Message-ID: From: "Matt Sartori" To: "Gary Thomas" CC: "Andrew Lunn" ,"eCos Discussion" Subject: RE: [ECOS] interrupt/virtual vectors confusion X-SW-Source: 2005-08/txt/msg00171.txt.bz2 Eeek! But that would mean that Redboot can only properly work as a bootloader for Redboot "enabled" programs. It was my understanding (and basis for advocating it as a viable alternative to writing our own custom bootloader) that Redboot is able to run any application and only re-appear when the board is reset. -----Original Message----- From: Gary Thomas [mailto:gary@mlbassoc.com]=20 Sent: 16 August 2005 15:18 To: Matt Sartori Cc: Andrew Lunn; eCos Discussion Subject: RE: [ECOS] interrupt/virtual vectors confusion On Tue, 2005-08-16 at 15:06 +0100, Matt Sartori wrote: > >Is Blinky an eCos RAM program? If so it should of taken over the > >interrupt vectors from Redboot. Redboot should no longer be active > >unless blinky actually calls into Redboot via the virtual vectors. >=20 > Blinky is just a standalone program I decided to use as a test. The only > change I've made to it to make it run is to link it directly into free > ram so that I can run it after having loaded it from Redboot (with a > load -r -m ymodem -b 0x20005b68).=20 > The reason I know that Redboot is handling (or at least that Redboot > code is being called) the IRQ is that I put while(1){flash an led every > second} at the top of hal_IRQ_handler and that it gets stuck there when > I run Blinky. Then, this is just as it should be :-) Unless you make Blinky into an eCos program, which uses the HAL interrupt mechanisms, RedBoot is quite happily going to try and handle the interrupt, etc. --=20 ------------------------------------------------------------ Gary Thomas | Consulting for the MLB Associates | Embedded world ------------------------------------------------------------ ---------------------------------------------------------------------------= ----- The information transmitted is intended only for the person or entity to wh= ich it is addressed and may contain confidential and/or privileged material= . Any review, retransmission, dissemination or other use of, or taking of a= ny action in reliance upon, this information by persons or entities other t= han the intended recipient is prohibited. If you received this in error, please contact the sender or postmaster (pos= tmaster@hanoverdisplays.com) and delete the material from any computer. Although we routinely screen for viruses, addressees should check this e-ma= il and any attachment for viruses. We make no warranty as to absence of vir= uses in this e-mail or any attachments. Our Company's email policy is to permit incidental personal use. If this em= ail is of a personal nature, it must not be relied upon as expressing the v= iews or opinions of the company. Visit out website at www.hanoverdisplays.com -- Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss