RE: [ECOS] Insight 5.1.1 with Angel /serial debugger

RE: [ECOS] Insight 5.1.1 with Angel /serial debugger

[Jing Luo]

Hi,
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.
[mlt_arm_mytarget_ram.ldi]
// eCos memory layout - Thu Feb 28 18:55:04 2002

// This is a generated file - do not edit

#include <cyg/infra/cyg_type.inc>

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

Re: [ECOS] Insight 5.1.1 with Angel /serial debugger

[Charles-Henri Balet]

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" <Jing@vicom.com>
To: "'Jesper Skov'" <jskov@redhat.com>; "Jing Luo" <Jing@vicom.com>
Cc: "'Charles-Henri Balet'" <charles-henri@bluewin.ch>; "eCos Discuss"
<ecos-discuss@sources.redhat.com>
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 <cyg/infra/cyg_type.inc>
>
> 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

Re: [ECOS] Insight 5.1.1 with Angel /serial debugger

[Jonathan Larmour]

Jing Luo wrote:
> 
> Hi,
> Thanks Jesper. Now I know porting eCos is not that easy.

Porting eCos to work with proprietary ROM monitors may not be as easy, no.

> 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 <cyg/infra/cyg_type.inc>
> 
> 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?

Compare with other ports and look at their .ldi files. For example, you'll
see that fixed_vectors should be at 0x20 generally.

> Have anyone had experience to run Redboot from RAM?
> 
> Another question about the linker file:
> what LMA_EQ_VMA mean?

Load address is the same as the address the program is expected to run at.
This is correct for RAM startup.

Jifl
-- 
Red Hat, Rustat House, Clifton Road, Cambridge, UK. Tel: +44 (1223) 271062
Maybe this world is another planet's Hell -Aldous Huxley || Opinions==mine

-- 
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss

RE: [ECOS] Insight 5.1.1 with Angel /serial debugger

[Jesper Skov]

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

RE: [ECOS] Insight 5.1.1 with Angel /serial debugger

[Jing Luo]

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?

Thanks,
-----Original Message-----
From: Charles-Henri Balet [mailto:charles-henri@bluewin.ch]
Sent: Tuesday, February 26, 2002 9:58 AM
To: ecos-discuss@sources.redhat.com
Subject: [ECOS] Insight 5.1.1 with Angel /serial debugger


Hi,
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]"

this is the part of the warm_reset where the problem appear :

        mov     r0,#0           // move vectors
        ldr     r1,=__exception_handlers
#ifndef CYGDBG_HAL_DEBUG_GDB_INCLUDE_STUBS
        // Wait with this if stubs are included (see further down).
        ldr     r2,[r1,#0x04]   // undefined instruction
        str     r2,[r0,#0x04]
        ldr     r2,[r1,#0x24]
        str     r2,[r0,#0x24]
#endif
        ldr     r2,[r1,#0x08]   // software interrupt
        str     r2,[r0,#0x08]

I have built an "RAM" startup, with enable of
CYGIMP_HAL_PROCESS_ALL_EXCEPTIONS
and disable of CYGSEM_HAL_USE_ROM_MONITOR.

any has any idea, can we modify the vectors table with an Angel debugger ?

many thanks

balet charles-henri







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

[ECOS] Insight 5.1.1 with Angel /serial debugger

[Charles-Henri Balet]

Hi,
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]"

this is the part of the warm_reset where the problem appear :

        mov     r0,#0           // move vectors
        ldr     r1,=__exception_handlers
#ifndef CYGDBG_HAL_DEBUG_GDB_INCLUDE_STUBS
        // Wait with this if stubs are included (see further down).
        ldr     r2,[r1,#0x04]   // undefined instruction
        str     r2,[r0,#0x04]
        ldr     r2,[r1,#0x24]
        str     r2,[r0,#0x24]
#endif
        ldr     r2,[r1,#0x08]   // software interrupt
        str     r2,[r0,#0x08]

I have built an "RAM" startup, with enable of
CYGIMP_HAL_PROCESS_ALL_EXCEPTIONS
and disable of CYGSEM_HAL_USE_ROM_MONITOR.

any has any idea, can we modify the vectors table with an Angel debugger ?

many thanks

balet charles-henri







-- 
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss