public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Jonathan Larmour <jlarmour@redhat.com>
To: Jing Luo <Jing@vicom.com>
Cc: 'Charles-Henri Balet' <charles-henri@bluewin.ch>,
	eCos Discuss <ecos-discuss@sources.redhat.com>
Subject: Re: [ECOS] Insight 5.1.1 with Angel /serial debugger
Date: Fri, 01 Mar 2002 11:42:00 -0000	[thread overview]
Message-ID: <3C7FD8F9.A3DB46D8@redhat.com> (raw)
In-Reply-To: <B26EACBBAF91D411BD8500508BF7D695051D87@earth.vicom.com>

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

  parent reply	other threads:[~2002-03-01 19:39 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-28 20:20 Jing Luo
2002-02-28 22:49 ` Charles-Henri Balet
2002-03-01 11:42 ` Jonathan Larmour [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-02-26 21:55 Jing Luo
2002-02-28  0:27 ` Jesper Skov
2002-02-26 14:39 Charles-Henri Balet

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3C7FD8F9.A3DB46D8@redhat.com \
    --to=jlarmour@redhat.com \
    --cc=Jing@vicom.com \
    --cc=charles-henri@bluewin.ch \
    --cc=ecos-discuss@sources.redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).