public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: "Harsha D" <harshad@sanyo.co.in>
To: "Andrew Lunn" <andrew@lunn.ch>
Cc: <ecos-discuss@sources.redhat.com>
Subject: RE: [ECOS]  Redboot :: __startup_stack
Date: Fri, 01 Jul 2005 12:37:00 -0000	[thread overview]
Message-ID: <C03A3C267DDF184EA523BBAB577BF92405B12C@blrexsr1.slti.sanyo.co.in> (raw)


Hi 

I was able to get the redboot working by disabling the gdb stubs. (which
effectively makes initialize_stub not be called).
Now redboot prompt appears.. although some junk characters are taken as
input and the program seems to be in infinite loop.

But i am unable to understand what is that in the gdb stubs which is
making the redboot to crash.  If you can throw some light on some of the
possibilities it would be great !!

Thanking you
harsha



-----Original Message-----
From: Andrew Lunn [mailto:andrew@lunn.ch]
Sent: 01 July 2005 13:16
To: Harsha D
Cc: ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] Redboot :: __startup_stack


On Fri, Jul 01, 2005 at 10:09:49AM +0530, Harsha D wrote:
> Hi
>  
>  ===============================================================
>  Porting 		:	Redboot	
>  Platform	:	ARM922T based board
>  source base	:	based on Excalibur package
>  
>  ===============================================================
>  Memory layout is 
>  --------------------------
>  SRAM(32KB)	 0x00000000 - 0x00008000	
>  RAM(32MB)	 0x20000000 - 0x02000000
>  
>  ===============================================================
>  My ram ldi file
>  ---------------------
>  MEMORY
>  {
>      ram : ORIGIN = 0x20000000, LENGTH = 0x02000000
>  }
>  
>  SECTIONS
>  {
>      SECTIONS_BEGIN
>      SECTION_fixed_vectors (ram, 0x20000020, LMA_EQ_VMA)
>      SECTION_rom_vectors (ram, 0x20300000, 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
>  }

....
  
>  [ I am loading redboot at 0x20300000]
> Googling told me that 
>  fixed_vectors should be at 0x20(???) which is not the case for me.  
>  Will it cause any problems ?  If yes then how should i have my memory
layout.

      SECTION_fixed_vectors (ram, 0x20000020, LMA_EQ_VMA)

Add an sram memory region and change this to 0x20 and the fixed
vectors will move.

        Andrew

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

             reply	other threads:[~2005-07-01 12:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-01 12:37 Harsha D [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-07-05  4:20 Harsha D
2005-07-01  8:34 Harsha D
2005-07-01  4:36 Harsha D
2005-07-01  7:46 ` Andrew Lunn

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=C03A3C267DDF184EA523BBAB577BF92405B12C@blrexsr1.slti.sanyo.co.in \
    --to=harshad@sanyo.co.in \
    --cc=andrew@lunn.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).