From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21020 invoked by alias); 1 Mar 2002 06:35:28 -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 20931 invoked from network); 1 Mar 2002 06:35:22 -0000 Received: from unknown (HELO mta3n.bluewin.ch) (195.186.1.212) by sources.redhat.com with SMTP; 1 Mar 2002 06:35:22 -0000 Received: from CHARLESHENRI (213.3.84.151) by mta3n.bluewin.ch (Bluewin AG 6.0.040) id 3C58FCB7007187E9; Fri, 1 Mar 2002 07:33:59 +0100 Message-ID: <002501c1c0ea$e62d1900$0401a8c0@CHARLESHENRI> From: "Charles-Henri Balet" To: "Jing Luo" , Cc: References: Date: Thu, 28 Feb 2002 22:49:00 -0000 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Subject: Re: [ECOS] Insight 5.1.1 with Angel /serial debugger X-SW-Source: 2002-02/txt/msg00589.txt.bz2 Hi, same for me, I want to use this redboot debugger, any litlle question, work this with insight too, or redboot in an complete and independent debugger ? I find the insight user interface nice. many thanks balet charles-henri ----- Original Message ----- From: "Jing Luo" To: "'Jesper Skov'" ; "Jing Luo" Cc: "'Charles-Henri Balet'" ; "eCos Discuss" Sent: Friday, March 01, 2002 4:37 AM Subject: RE: [ECOS] Insight 5.1.1 with Angel /serial debugger > Hi, > Thanks Jesper. Now I know porting eCos is no t that easy. > > I choose the second option you suggested - port Redboot. > > I changed the hal-platform-setup.h for hardware initialization. > > I want to start Redboot from RAM, but the problem is the memory layout came > out is not the way I wanted as the following. > [mlt_arm_mytarget_ram.ldi] > // eCos memory layout - Thu Feb 28 18:55:04 2002 > > // This is a generated file - do not edit > > #include > > MEMORY > { > ram : ORIGIN = 0xc0000000, LENGTH = 0x2000000 > } > > SECTIONS > { > SECTIONS_BEGIN > SECTION_fixed_vectors (ram, 0xc0000000, LMA_EQ_VMA) > SECTION_rom_vectors (ram, 0xc0020000, LMA_EQ_VMA) > SECTION_text (ram, ALIGN (0x4), LMA_EQ_VMA) > SECTION_fini (ram, ALIGN (0x4), LMA_EQ_VMA) > SECTION_rodata (ram, ALIGN (0x4), LMA_EQ_VMA) > SECTION_rodata1 (ram, ALIGN (0x4), LMA_EQ_VMA) > SECTION_fixup (ram, ALIGN (0x4), LMA_EQ_VMA) > SECTION_gcc_except_table (ram, ALIGN (0x4), LMA_EQ_VMA) > SECTION_data (ram, ALIGN (0x4), LMA_EQ_VMA) > SECTION_bss (ram, ALIGN (0x4), LMA_EQ_VMA) > CYG_LABEL_DEFN(__heap1) = ALIGN (0x8); > SECTIONS_END > } > > After build library and look in the map, __exception_handlers start from > address 0x20000 which is in the ROM. > I am confused about that. How can I make it run from RAM? > > Have anyone had experience to run Redboot from RAM? > > Another question about the linker file: > what LMA_EQ_VMA mean? > > Thanks, > > -----Original Message----- > From: Jesper Skov [mailto:jskov@redhat.com] > Sent: Thursday, February 28, 2002 12:24 AM > To: Jing Luo > Cc: 'Charles-Henri Balet'; eCos Discuss > Subject: RE: [ECOS] Insight 5.1.1 with Angel /serial debugger > > > On Wed, 2002-02-27 at 03:45, Jing Luo wrote: > > The same problem with me when I am trying to port eCos to 80200EVB. > > But my configuration is disable of CYGIMP_HAL_PROCESS_ALL_EXCEPTIONS and > > enable of of CYGSEM_HAL_USE_ROM_MONITOR. > > > > If this one doesn't work, how I can do to debug eCos? > > and > > > I use Insight 5.1.1 on an ARM processor on a board with Angel 1.20, the > > link, download, debugger work fine, > > my problem, the ecos startup code in the Vectors.s file, this startup > > replace vectors in the vector table and when the > > vector of the undefined instruction is replaced, insight freeze, I'm have > to > > start step by step and the problem is > > on the line "str r2,[r0,#0x24]" > > The problem is that Angel is using the CPU exception to do the > single-stepping. When the eCos HAL executes and takes over that > exception, Angel essentially dies. > > What you want to do is either (a) comment out that code to debug the > application with Angel or (b) port RedBoot and make it the primary > monitor and debug agent of the system. > > RedBoot knows how to debug eCos applications, Angel does not. > > Jesper > > -- > Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos > and search the list archive: http://sources.redhat.com/ml/ecos-discuss > > -- Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos and search the list archive: http://sources.redhat.com/ml/ecos-discuss