linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Misbah khan <misbah_khan@engineer.com>
To: linuxppc-embedded@ozlabs.org
Subject: Re: Control not branching to the instruction present at resetvec i.e 0xfffffffc
Date: Sat, 5 Jan 2008 06:19:05 -0800 (PST)	[thread overview]
Message-ID: <14633599.post@talk.nabble.com> (raw)
In-Reply-To: <OFD408300E.ACB35FD3-ON852573C6.0072065E-852573C6.007337FA@RFLELECT.COM>


Hi Mr Ravi ...
I suggest you to post a new concern in a new thread ....

----Misbah 

ravi.rao wrote:
> 
> Hi All,
>     We have a custom target board based on PPC-EP405. We just got the 
> board from the hardware team .I connected the board to BDI200 and powered 
> it on. 
> The control came to the resetvec address which is 0xfffffffc. I was able 
> to read and write to flash. So I erased the flash and burnt the bootloader 
> into flash from 0xfffc0000.
> I verified that the instruction at 0xfffffffc is 4bfc2104 whicis actually 
> a branch to 0xfffc2100. Also a memory dump of 0xfffc2100 shows the correct 
> code. This proved that
> the uboot bootloader was burnt properly.
> Now when I reset the board the control never reaches 0xfffc2100 i.e for 
> some reason the code at the resetvec is not getting executed. Any help or 
> pointers to resolve this is greatly appreciated.
> Thanks,
> Ravishankar Govindarao
> RFL Electronics Inc.
> E-mail : Ravi.Rao@rflelect.com
> Voice: 973.334.3100 Ext. 233
> Fax: 973.334.3863
>  
> CONFIDENTIALITY NOTE
> This e-mail, including any attachments, may contain confidential and/or 
> legally privileged information.  The Information is intended only for the 
> use of the individual or entity named on this e-mail .  If you are not the 
> intended recipient, you are hereby notified that any disclosure, copying, 
> distribution, or the taking of any action in reliance on the contents of 
> this transmitted Information is strictly prohibited.  Further, if you are 
> not the intended recipient, please notify us by return e-mail and delete 
> the Information promptly.
>  
>  
>  
> _______________________________________________
> Linuxppc-embedded mailing list
> Linuxppc-embedded@ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-embedded
> 

-- 
View this message in context: http://www.nabble.com/Reading-a-config-file-in-a-driver-....-tp14591717p14633599.html
Sent from the linuxppc-embedded mailing list archive at Nabble.com.

  reply	other threads:[~2008-01-05 14:19 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-03  5:03 Reading a config file in a driver Misbah khan
2008-01-03 16:30 ` Olof Johansson
2008-01-03 18:43   ` Carlos Munoz
2008-01-04  8:32     ` Misbah khan
2008-01-04 20:58       ` Control not branching to the instruction present at resetvec i.e 0xfffffffc ravi.rao
2008-01-05 14:19         ` Misbah khan [this message]
2008-01-04  8:36   ` Reading a config file in a driver Misbah khan
     [not found] <mailman.1.1199581203.5432.linuxppc-embedded@ozlabs.org>
2008-01-09 18:28 ` Control not branching to the instruction present at resetvec i.e 0xfffffffc Siva Prasad

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=14633599.post@talk.nabble.com \
    --to=misbah_khan@engineer.com \
    --cc=linuxppc-embedded@ozlabs.org \
    /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 NNTP newsgroup(s).