From: Felix Radensky <felix@embedded-sol.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] PPC440GX: DDR ECC init time.
Date: Tue, 08 Sep 2009 12:19:41 +0300 [thread overview]
Message-ID: <4AA621AD.3020902@embedded-sol.com> (raw)
In-Reply-To: <200909071623.22541.sr@denx.de>
Hi, Stefan
Stefan Roese wrote:
> On Monday 07 September 2009 15:57:19 Wouter Eckhardt wrote:
>
>> Well, I've been trying to work this into my U-Boot. I haven't succeeded
>> so far. Basically, the cache stuff in 4xx_spd_ddr2.c consists of setting
>> up a TLB without the CACHE_INHIBITED bit and then using some cache
>> instructions to fill up memory. That's what I've been trying to do, but
>> my call to change_tlb() hangs because of the invalidate_dcache() call
>> (bad trap exceptions). What could be going on here?
>>
>> I'll try and set up the DDR TLB dynamically instead of statically (in
>> init.S) and see if I can get that working.
>>
>
> Yes. That's what I would do as well.
>
>
>> By the way, I've also stumbled upon some other VERY strange behavior. If
>> I leave the ecc_init() in its original state and just add in a puts(" ")
>> call at the beginning of the function, ECC generation is finished VERY
>> quickly. What influence could adding the puts() call possibly have on
>> the speed of generating ECC values in DDR?
>>
>
> That's strange indeed. I suspect a problem in the code then. Try looking at
> the generated assembler code and/or debug with an BDI2000/3000.
>
Not exactly related to the subject under discussion, but I thought I'd
mention it.
I had problems with ecc_init() on a custom 460EX board with soldered DDR2.
Right after ecc_init() u-boot was crashing on PLB access. I've modified
the code
to use program_ecc_addr() instead of ecc_init(), and problem was solved.
I was
wandering why use two different ECC initialization routines for SPD and
soldered
cases, when program_ecc_addr() can do the job in both cases, while
ecc_init()
apparently has issues ?
Thanks.
Felix.
> Cheers,
> Stefan
>
> --
> DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
> HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
> Phone: (+49)-8142-66989-0 Fax: (+49)-8142-66989-80 Email: office at denx.de
> _______________________________________________
> U-Boot mailing list
> U-Boot at lists.denx.de
> http://lists.denx.de/mailman/listinfo/u-boot
>
next prev parent reply other threads:[~2009-09-08 9:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-04 12:34 [U-Boot] PPC440GX: DDR ECC init time Wouter Eckhardt
2009-09-04 12:50 ` Stefan Roese
2009-09-04 13:06 ` Wouter Eckhardt
2009-09-04 13:13 ` Stefan Roese
2009-09-07 13:57 ` Wouter Eckhardt
2009-09-07 14:23 ` Stefan Roese
2009-09-08 9:19 ` Felix Radensky [this message]
2009-09-08 9:49 ` Stefan Roese
2009-09-08 10:05 ` Felix Radensky
2009-09-08 11:04 ` Stefan Roese
2009-09-08 15:19 ` Grant Erickson
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=4AA621AD.3020902@embedded-sol.com \
--to=felix@embedded-sol.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.