public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: "G.Muruganandam" <gmuruga@gdatech.com>
To: Gary Thomas <gary@mlbassoc.com>
Cc: eCos Discussion <ecos-discuss@sources.redhat.com>
Subject: Re: [ECOS] Issue in boot script
Date: Fri, 03 Oct 2003 19:45:00 -0000	[thread overview]
Message-ID: <5.2.1.1.0.20031003124545.047812b8@mail.gdatech.com> (raw)
In-Reply-To: <1065209434.18201.517.camel@hermes>

Hi Gary,

Even though the the time displayed in seconds shows 100 ( looks like, it is 
multiplied by 10) .

So it is effectively waiting for 10 seconds only before displaying the 
redboot prompt. I did verify
elapsed time using the system clock.

Here is the screen shot.


SDRAM(768M): 0x00000000 - 0x30000000, 0x00200000 - 0x2ffdf000 available
SRAM Channel 0(16M): 0x80000000 - 0x81000000
SRAM Channel 1(16M): 0x90000000 - 0x91000000
SRAM Channel 2(16M): 0xa0000000 - 0xa1000000
SRAM Channel 3(16M): 0xb0000000 - 0xb1000000
FLASH(16M): 0xc4000000 - 0xc5000000, 128 blocks of 0x00020000 bytes each.
CPLD Rev. is 9.4
== Executing boot script in 100.000 seconds - enter ^C to abort
RedBoot_2800>

Thanks
G.Muruganandam


At 01:30 PM 10/3/2003 -0600, Gary Thomas wrote:
>On Fri, 2003-10-03 at 13:30, G.Muruganandam wrote:
> > Hi,
> >
> > I am working on the IXP2xxx platform to boot linux using the boot script.
> >
> > The linux image is in the flash.
> > I am able to use the following command at the redboot prompt to boot
> > the linux. Its working fine.
> >
> > Redboot> fis load zImage
> > Redboot>exec 0x10008000
> >
> >
> > But when I include the same command under the boot script and allows 
> the system
> > to boot using the script, it is not working. I could see the system 
> waiting
> > for the Ctrl +c
> > from user to abort the booting. But it is not reading the boot script and
> > executing it .
> >
> > I can see the boot script residing in the flash using the following 
> command.
> >
> > RedBoot> fconfig -li
> > Run script at boot: true
> > Boot script:
> > .. fis load zImage
> > .. exec 0x10008000
> >
> > Boot script timeout (1000ms resolution): 100
> > Use BOOTP for network configuration: true
> > GDB connection port: 9000
> > Network debug at boot time: false
> > RedBoot>
> >
> >
> > Please let me know  what I am missing and do let me know if you need more
> > details.
> >
>
>How long did you wait?  You've told it not to run the script until
>*100* seconds have passed :-), so unless you waited for nearly two
>minutes, you won't see the script execute.
>
>This value (Boot script timeout) is typically something like 5 seconds.
>
>
>--
>Gary Thomas <gary@mlbassoc.com>
>MLB Associates


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

  reply	other threads:[~2003-10-03 19:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-03 19:25 G.Muruganandam
2003-10-03 19:30 ` Gary Thomas
2003-10-03 19:45   ` G.Muruganandam [this message]
2003-10-07 19:00 G.Muruganandam

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=5.2.1.1.0.20031003124545.047812b8@mail.gdatech.com \
    --to=gmuruga@gdatech.com \
    --cc=ecos-discuss@sources.redhat.com \
    --cc=gary@mlbassoc.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).