public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Hebbar <gururajakr@sanyo.co.in>
To: u-boot@lists.denx.de
Subject: [U-Boot] U-Boot on ARM9
Date: Mon, 22 Sep 2008 02:46:59 -0700 (PDT)	[thread overview]
Message-ID: <19604726.post@talk.nabble.com> (raw)
In-Reply-To: <40a670230809220012j1bab5602gdd07eeab9e8db482@mail.gmail.com>


Hi,

>>
>>I have a few questions on arm926 initialization code, located in
>>${U_BOOT}/cpu/arm926ejs/start.S:
>>1) what is the point of deliberately setting up SVC mode, as it's
>>already in this mode right upon the reset?
What if the target board has a custom bootmonitor & you use U-Boot as
secondary bootloader. This is a precautionary measure.

>>2) I can't quite understand what 'CONFIG_USE_IRQ' is used for. It is
>>defined on just a few targets.
Generally bootloader doesnt use IRQ for running. But if u need to use
IRQ/FIQ u need to setup stacks for the Same. And also When Interrupt occurs
you need to set sp to pint to proper stacks, save registers & then jump to
irq handler. U_Boot provides a common envelope for all interrupt related
functions. 


>>3) The stack set up -- commonly startup code initializes stacks for
>>all modes, but it's not clear how it's done in 'start.S'. Seems like
>>somehow stacks are run-time configured, but I didn't perceive  how.
U-boot Initially sets up Stack for SVC Mode. 

Upon Interrupt Triggers, Stacks are setup for the IRQ/FIQ Modes. 

This is done in the ${U_BOOT}/cpu/arm926ejs/start.S

for SVC Mode ---> @ line 173
for IRQ Mode --->  @ line 327
for FIQ Mode --->  @ line 331

Hope this would clear your doubts.

Regards
Gururaja
-- 
View this message in context: http://www.nabble.com/-U-Boot--U-Boot-on-ARM9-tp19602930p19604726.html
Sent from the Uboot - Users mailing list archive at Nabble.com.

  reply	other threads:[~2008-09-22  9:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-22  7:12 [U-Boot] U-Boot on ARM9 Roman Mashak
2008-09-22  9:46 ` Hebbar [this message]
2008-09-23 12:17   ` Roman Mashak

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=19604726.post@talk.nabble.com \
    --to=gururajakr@sanyo.co.in \
    --cc=u-boot@lists.denx.de \
    /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