public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Fabian Cenedese <Cenedese@indel.ch>
To: u-boot@lists.denx.de
Subject: [U-Boot] P2020 L2 cache as SRAM
Date: Thu, 20 Jan 2011 10:21:49 +0100	[thread overview]
Message-ID: <5.2.0.9.1.20110120101552.05b50b38@localhost> (raw)
In-Reply-To: <20110119140221.083392bf@udp111988uds.am.freescale.net>


>> >We're trying to configure the PPC P2020 cpu to use the L2 cache
>> >as SRAM so we can load the U-Boot code in there. However we
>> >stumble into problems. Sometimes the cpu goes on trap when
>> >trying to access this area. Sometimes there's no trap but we
>> >seem to access a different area. That's probably a problem with
>> >setting up a TLB/LAW.
>> >
>> >Has anybody already done this and could share some code with
>> >us?
>> >
>> >I've seen that there's a mpc85xx branch with quite some work
>> >going on. Where should we base our work on? Should we use
>> >the master or is it better to use this branch? I'm used to svn,
>> >not git, so there may be other options I don't know about yet.
>> 
>> I know you're busy with patches and releasing, I just wanted
>> to ask again if anybody has already done this.
>
>Yes, it's been done.  P1_P2_RDB does this when configured for NAND boot.
>
>Look for CONFIG_SYS_INIT_L2_ADDR.

Thanks for the hint. We have seen this and compared it to our
implementation which was based on the AN3646.pdf (chapter 4).
It seems that disabling the errors as done in cpu_init_nand.c
helps quite a bit. We've seen this code before but for some
reason that register got lost in the conversion to assembler.
So now it works fine.

Thanks.

bye  Fabi

  reply	other threads:[~2011-01-20  9:21 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-17  8:07 [U-Boot] P2020 L2 cache as SRAM Fabian Cenedese
2011-01-19  7:50 ` Fabian Cenedese
2011-01-19 20:02   ` Scott Wood
2011-01-20  9:21     ` Fabian Cenedese [this message]
2011-10-19 11:53     ` DarkKhan
2011-10-19 12:12       ` Aggrwal Poonam-B10812

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.0.9.1.20110120101552.05b50b38@localhost \
    --to=cenedese@indel.ch \
    --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