From: Z.N. <zoldnap@freemail.hu>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] porting to custom at 91 board
Date: Sat, 20 Nov 2004 23:23:39 +0000 [thread overview]
Message-ID: <1100993019.6511.10.camel@localhost> (raw)
Dear developers!
As some advised, instead of trying to write a boot loader for a custom
AT91 board, I wanted to use the loader.bin and u-boot.bin from ATMEL.
However, after transferring loader.bin, the 'C'-s appear, however, I
cannot transfer u-boot.bin, because Hyper terminal displays some "Error
limit exceeded" message. (I've also tried with minicom, it gives a
couple of NAK messages when transferring u-boot.bin).
What can be the error?
My board is more or less the same as at19rm9200dk, however it has only 1
chip of 16 bit SDRAM connected instead of 2 chips (so the data bus is
only 16 bits wide, and memory timings are different). Can this cause a
problem?
My alternate question is, how to port u-boot, so that I can start it in
RAM with the above configuration (I've got a small boot loader done in
assembly, which is loaded from SPI on startup. So I could store u-boot
in the SPI flash, and load it to RAM from there on startup by my small
boot loader. how to do this? eg. where to load the u-boot image in RAM?
I guess I have to also adjust the SDRAM setup and timings which are
differing from the atmel DK.). have anyone ported u-boot to such a
configuration?
I'd be grateful if you could give me any pointers on this problem.
Best Regards,
Zo
next reply other threads:[~2004-11-20 23:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-20 23:23 Z.N. [this message]
2004-11-21 0:06 ` [U-Boot-Users] porting to custom at 91 board Wolfgang Denk
2004-11-21 9:52 ` Z.N.
2004-11-21 10:03 ` Wolfgang Denk
2004-11-22 9:56 ` Steven Scholz
2004-11-22 11:09 ` Wolfgang Denk
2004-11-22 11:12 ` Steven Scholz
2004-11-22 16:46 ` 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=1100993019.6511.10.camel@localhost \
--to=zoldnap@freemail.hu \
--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.