From mboxrd@z Thu Jan  1 00:00:00 1970
From: Chetan Nanda <chetannanda@gmail.com>
Date: Fri, 21 Aug 2009 18:35:24 +0530
Subject: [U-Boot] Mips: start.S Questions
In-Reply-To: <574bb010908210553v7dd8570cnfa6d85978b531e10@mail.gmail.com>
References: <574bb010908210434j5e3bcc4cqb96604c345f01046@mail.gmail.com>
	<m21vn59w6s.fsf@ohwell.denx.de>
	<574bb010908210553v7dd8570cnfa6d85978b531e10@mail.gmail.com>
Message-ID: <7f245da80908210605q2b78dc9dtf39559feaa9af224@mail.gmail.com>
List-Id: <u-boot.lists.denx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: u-boot@lists.denx.de

On Fri, Aug 21, 2009 at 6:23 PM, Peter Belm <peterbelm@gmail.com> wrote:

> >
> > This is not quite correct.  "romReserved" is only used for the, well,
> > reserved entries.  There are other parameters passed, these two are
> > pretty important for example:
>
>
> The thing I don't get is if you expand the RVECENT macro into the code
> wouldn't you get this:
>
> _start:
>    b reset; nop    /* U-boot entry point */


On power on, first instruction that will get executed is  'b reset, nop'. So
code will Jump to reset label
from where actual booting sequence start.


>
>    b reset; nop    /* software reboot */
>
>    b romReserved
>    b romReserved
>
> ....
>
> romReserved:
>    b romReserved
>
> So wouldn't it get stuck in an infinite loop straight away, calling
> romReserved recursively? I'm obviously overlooking something I think.


So romReserved will not get called in normal booting-sequence as code will
jump to 'reset' label.
 In case of some exception 'romReserved' will be called and then board will
struck in while loop.


Thanks,
Chetan  Nanda

>
>
> And what's the point of passing the second parameter (0-127) to RVECENT
> when
> it's not used?
>
> --
> Regards,
> Peter Belm
>
> _______________________________________________
> U-Boot mailing list
> U-Boot at lists.denx.de
> http://lists.denx.de/mailman/listinfo/u-boot
>
>