public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Pink Boy <dasfoo@yahoo.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Building u-boot for the AT91RM9200-EK circa 2008
Date: Fri, 31 Oct 2008 17:34:28 -0700 (PDT)	[thread overview]
Message-ID: <579033.94714.qm@web31811.mail.mud.yahoo.com> (raw)
In-Reply-To: <20081031214037.GA4178@ld0162-tx32.am.freescale.net>


Hi, first post here.

vis: Building u-boot for the AT91RM9200-EK circa 2008

Is this still possible all things considered? It appears that 
this board is left behind in a backwater sometime around 2006.

Problem is I need to compile a new version of u-boot for my 
new board based on the AT91RM9200 and I'm having a lot of trouble. 
My board is very closely based on the AT91RM9200-EK, pretty much 
the same except the flash has changed. So I need to modify u-boot 
to handle the new flash (AT49BV642D). I'm running into real 
problems, at least for a noob.

On my board I can get two versions of u-boot to run, the 1.1.5 
version that comes with the AT91RM9200 development kit. And an 
ancient u-boot 1.1.1 that I got off Atmel's website which 
surprisingly enough will write to the new flash chip I have 
installed, even though it thinks there is only 2M installed 
instead of 8M And I can use it to do setenv, etc and load 
uboot 1.1.5 into flash and boot linux over the network connection.

So far so good. So my hardware works, I just need a version of 
u-boot that supports the AT49BV642D. Patching the source seems 
easy enough. However. Problem is that the official distribution 
of u-boot has no support for the AT91RM9200-EK. Which is sad. 
Very very sad.

I tried compiling u-boot from scratch using the instructions 
on this page.

http://www.linux4sam.org/twiki/bin/view ... _x_sources

Namely,
wget ftp://ftp.denx.de/pub/u-boot/u-boot-1.1.5.tar.bz2
tar xvjf u-boot-1.1.5.tar.bz2
cd u-boot-1.1.5

wget ftp://www.linux4sam.org/pub/uboot/u-boo ... 5.diff.bz2
bzcat u-boot-1.1.5_atmel_1.5.diff.bz2 | patch -p1

Then

I fixed up two lines in the examples make file adding an .o 
at the end in order to make the 3.81 linker happy.

Line 147 :
  $(obj)%.srec: $(obj)%.o
Line 150
  $(obj)%.bin: $(obj)%.o

Then

make distclean
make at91sam9263ek_config
make CROSS_COMPILE=<path_to_cross-compiler/cross-compiler-prefix->

Where my compiler is 
   gcc version 3.4.3 (release) (CodeSourcery ARM Q1B 2005)

I've also tried 
   gcc version 4.1.1 (CodeSourcery ARM Sourcery G++ 2006q3-26)

and 
   gcc 4.1.1 from timesys.

In each case I get a built version of u-boot.bin. However when 
I download it the same way I use the other two wokring binaries
of u-boot that I have it just hangs with no output.

I've also tried gzipping it and trying to have boot.bin load it
from flash, but it hangs as well.

I also tried compiling with an old version of gcc 3.4.1 but it 
wouldn't compile the source due to a compiler bug/issue.  Google
indicates the error is due to the compiler assuming a hard fpu.

Anyone have advice on how to proceed from here?

  reply	other threads:[~2008-11-01  0:34 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-31 21:40 [U-Boot] Pull request: nand flash Scott Wood
2008-11-01  0:34 ` Pink Boy [this message]
2008-11-01  9:44   ` [U-Boot] Building u-boot for the AT91RM9200-EK circa 2008 Jean-Christophe PLAGNIOL-VILLARD
2008-11-01 14:34     ` Ulf Samuelsson
2008-11-02  0:34     ` Pink Boy
2008-11-03  7:26   ` Martin Hejnfelt
2008-11-03 11:11     ` Wolfgang Denk
2008-11-03 12:07       ` Martin Hejnfelt
2008-11-03 20:11         ` Wolfgang Denk
2008-11-03 21:40           ` Pink Boy
2008-11-03 22:51             ` James Black
2008-11-03 23:02             ` Wolfgang Denk
2008-11-06  1:48           ` Pink Boy
2008-11-06  8:15             ` Wolfgang Denk
2008-11-01 15:21 ` [U-Boot] Pull request: nand flash 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=579033.94714.qm@web31811.mail.mud.yahoo.com \
    --to=dasfoo@yahoo.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