This is the mail archive of the mailing list for the eCos project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

RE: Insight 5.1.1 with Angel /serial debugger

Thanks Jesper. Now I know porting eCos is not 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.
// eCos memory layout - Thu Feb 28 18:55:04 2002

// This is a generated file - do not edit

#include <cyg/infra/>

    ram : ORIGIN = 0xc0000000, LENGTH = 0x2000000

    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);

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?


-----Original Message-----
From: Jesper Skov []
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
> If this one doesn't work, how I can do to debug eCos?


> 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
> 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.


Before posting, please read the FAQ:
and search the list archive:

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]