From: Scott Wood <scottwood@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] P2020rdb :- process hangs while invalidate_tlb's
Date: Mon, 22 Oct 2012 18:58:57 -0500 [thread overview]
Message-ID: <1350950337.30970.12@snotra> (raw)
In-Reply-To: <34572303.post@talk.nabble.com> (from diya8off@gmail.com on Thu Oct 18 05:50:23 2012)
On 10/18/2012 05:50:23 AM, diyaa wrote:
>
> Hi
>
> I am working on a custom board (VPX Based P2020 board) and trying to
> port
> u-boot-2011.09 (supports P2020 RDB) in it . Our board is similar to
> P2020RDB
> board and the technical specification is shown below ,
You should always try with the latest version when asking for help
(even if you will eventually need to use an older version for some
other (usually not very good) reason).
> ->Processor
>
> Freescale QorIQ P2020 processor
> Dual PowerPC e500v2 cores at up to 1.2 GHz
> 512 kB of shared L2 cache
>
> ->Memory
>
> 1 GB of DDR3-600 SDRAM
> 128 MB of NOR flash (16-bit)
>
> Through Codewarroier Emulator Tool, We checked the DDR,FLASH,Uart
> console
> and its working fine without any issue.
>
> when we ported u-boot (u-boot-2011.09) at boot rom location
> 0xFFF80000, it
> fails at invalidate_tlbs in cpu_init_early_f and cannot proceed to
> get
> serial console .we probed the flash CS while poweron boot , processor
> is
> keeping bunch of CS( confirms processor able to access flash)
>
>
> Why its getting held up while invalidating tlb's
Are you sure that's where it's failing? It could be that you just
can't single step through that boot phase. There were recently applied
patches to shrink the "undebuggable" window somewhat.
If that's not it, probably there's no IPROT TLB entry covering the
address you're running out of, or covering the initial RAM area. Have
you tried dumping the TLB?
-Scott
next prev parent reply other threads:[~2012-10-22 23:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-18 10:50 [U-Boot] P2020rdb :- process hangs while invalidate_tlb's diyaa
2012-10-22 23:58 ` Scott Wood [this message]
2012-11-15 7:09 ` vidya Krishnamoorthy
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=1350950337.30970.12@snotra \
--to=scottwood@freescale.com \
--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