From: Wolfgang Wegner <wolfgang@leila.ping.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] Solved: U-Boot (porting) problem on MCF5445x board
Date: Tue, 19 Jan 2010 14:17:16 +0100 [thread overview]
Message-ID: <20100119131716.GC23389@leila.ping.de> (raw)
In-Reply-To: <20100114165307.GE4092@leila.ping.de>
Hi list,
sorry for the noise!
The problem turned out to be a simple SDRAM setup problem.
I had set "burst read to read/precharge delay" and "burst write
to read/write/precharge delay" by 1 too low.
Don't know how I messed these values up, but these lead to all
memory accesses in single-step mode and via BDM to work correctly
but gave erroneous results in real program execution.
[note to self: in case of strange errors, always check memory
interface. If triple-checked: check again...]
Sorry again,
Wolfgang
PS: just in case anybody is interested, I am using two pieces of
MT47H32M16HR-3IT on an MCF54455 with this setup:
; SDRAM init
; SDCS0:
mem write 0xFC0B8110 0x40000019
; SDCS1:
mem write 0xFC0B8114 0x44000019
; SDCFG1:
mem write 0xFC0B8008 0x66311720
; SDCFG2:
mem write 0xFC0B800C 0x6A670000
; SDCR (PALL):
mem write 0xFC0B8004 0xE9062002
; SDMR (EMode2):
mem write 0xFC0B8000 0x80010000
; SDMR (EMode3):
mem write 0xFC0B8000 0xC0010000
; SDMR (EMode)
mem write 0xFC0B8000 0x40010412
; SDMR (Mode)
mem write 0xFC0B8000 0x00010333
wait 10
; SDCR:
mem write 0xFC0B8004 0xE9062C02
mem write 0xFC0B8004 0xE9062C04
mem write 0xFC0B8004 0xE9062C04
; SDMR (MODE)
mem write 0xFC0B8000 0x00010233
; SDMR (EMODE, OCD default)
mem write 0xFC0B8000 0x40010792
; SDMR (EMODE, OCD exit)
mem write 0xFC0B8000 0x40010412
; SDCR:
mem write 0xFC0B8004 0x79062C00
next prev parent reply other threads:[~2010-01-19 13:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-14 14:33 [U-Boot] U-Boot (porting) problem on MCF5445x board Wolfgang Wegner
2010-01-14 16:15 ` Wolfgang Wegner
2010-01-14 16:53 ` Wolfgang Wegner
2010-01-19 13:17 ` Wolfgang Wegner [this message]
2010-01-19 14:04 ` [U-Boot] Solved: " Wolfgang Denk
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=20100119131716.GC23389@leila.ping.de \
--to=wolfgang@leila.ping.de \
--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