From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 20946 invoked by alias); 2 Jul 2002 13:29:40 -0000 Mailing-List: contact ecos-discuss-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: ecos-discuss-owner@sources.redhat.com Received: (qmail 20934 invoked from network); 2 Jul 2002 13:29:35 -0000 Received: from unknown (HELO tchip.ch) (209.102.28.129) by sources.redhat.com with SMTP; 2 Jul 2002 13:29:35 -0000 Received: from tchip.com ([195.190.161.174]) by tchip.ch (8.9.3) with ESMTP id GAA01245 sender joel.brenner@tchip.com; Tue, 2 Jul 2002 06:29:26 -0700 Message-ID: <3D21C70C.4060902@tchip.com> Date: Tue, 02 Jul 2002 06:29:00 -0000 From: brenner joel User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.2.1) Gecko/20010901 X-Accept-Language: en-us MIME-Version: 1.0 To: Gary Thomas CC: ecos-discuss@sources.redhat.com References: <3D21BE28.1070203@tchip.com> <1025615113.31919.1397.camel@hermes.chez-thomas.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [ECOS] EB40 standalone application X-SW-Source: 2002-07/txt/msg00013.txt.bz2 Gary Thomas wrote: >On Tue, 2002-07-02 at 08:52, brenner joel wrote: > >>Hello all, >> I'm trying to use eCos on a Atmel EB40 board without any monitor. >>I need to use eCos without any debug features so I've modified a little >>the ld script for ROM version. >>(no space left for debug monitor, place rom_vectors directly at remapped >>address 0x0of SRAM and place the program >> in RAM at address 0x02000000). >>I've configured eCos to run in ROM, without debug features and without >>virtual vector calling. >>The compilation and the test works fine, but when I download the binary >>to the target it hangs always somewhere in "hal_if_diag". >> >>What I've made wrong ? >>Are there maybe some things to add for running eCos as a stand alone >>application, or some initializations are missed? (twothreads, hello and >>serial examples hangs always). >> > >Look at how RedBoot is configured for that platform. It is a stand >alone program, built from the eCos sources. > >I'd guess that the problem lies with your turning off of the virtual >vector stuff. This doesn't cost you anything and for a stand alone >program, your program will provide the actual I/O (again, look at >RedBoot since it uses virtual vector support). > > > Tanks for the help. I've seen that in "hal_if_diag" there is a mov pc, r2, where r2 contains the address 0x64. But at this address isn't any valid code. Contents of section .rom_vectors: 0000 feff7fea 18f09fe5 18f09fe5 18f09fe5 ................ 0010 18f09fe5 00000000 18f09fe5 18f09fe5 ................ 0020 00000002 8c010002 f4010002 2c020002 ............,... 0030 8c020002 00000000 78030002 40030002 ........x...@... Contents of section .text: 2000000 80a59fe5 2f0ab0e1 0aa6a001 2aa6a001 ..../.......*... Is the virtual vector calling interface placed at these address ? Regards jobre -- Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos and search the list archive: http://sources.redhat.com/ml/ecos-discuss