u-boot

Recently I bought the mini2440 board with 128MB.
I've downloaded u-boo from git repository
(git://repo.or.cz/u-boot-openmoko/mini2440.git) and compiled it.
I've tried to install it:

##### FriendlyARM BIOS 2.0 for 2440 #####
[x] format NAND FLASH for Linux
[v] Download vivi
[k] Download linux kernel
[y] Download root_yaffs image
[a] Absolute User Application
[n] Download Nboot for WinCE
[l] Download WinCE boot-logo
[w] Download WinCE NK.bin
[d] Download & Run
[z] Download zImage into RAM
[g] Boot linux from RAM
[f] Format the nand flash
[b] Boot the system
[s] Set the boot parameters
[u] Backup NAND Flash to HOST through USB(upload)
[r] Restore NAND Flash from HOST through USB
[q] Goto shell of vivi

Supervivi> load flash 0 233472 u
USB host is connected. Waiting a download.

Now, Downloading [ADDRESS:30000000h,TOTAL:233482]
RECEIVED FILE SIZE:  233482 (76KB/S, 3S)
Downloaded file at 0x30000000, size = 233472 bytes
Found block size = 0x00040000
Erasing...    ... done
Writing...    ... done
Written 233472 bytes

Supervivi> go 0x30000000
go to 0x30000000
  argument 0 = 0x00000000
  argument 1 = 0x00000000
  argument 2 = 0x00000000
á argument 3 = 0x00000000

U-Boot 1.3.2-mini2440 (Sep 12 2009 - 16:17:01)

I2C:   ready
DRAM:  64 MB
Flash:  2 MB
NAND:  Bad block table not found for chip 0
Bad block table not found for chip 0
128 MiB
*** Warning - bad CRC or NAND, using default environment

USB:   S3C2410 USB Deviced
In:    serial
Out:   serial
Err:   serial
MAC: 08:08:11:18:12:27
Hit any key to stop autoboot:  0  

MINI2440 # nand scrub

NAND scrub: device 0 whole chip
Warning: scrub option will erase all factory set bad blocks!
         There is no reliable way to recover them.
         Use this command only for testing purposes if you
         are sure of what you are doing!

Really scrub this NAND flash? <y/N>
Erasing at 0x3c0000 --   3% complete.
NAND 128MiB 3,3V 8-bit: MTD Erase failure: -5
Erasing at 0x3fe0000 --  50% complete.
NAND 128MiB 3,3V 8-bit: MTD Erase failure: -5
Erasing at 0x7fe0000 -- 100% complete.
Bad block table not found for chip 0
Bad block table not found for chip 0
OK

MINI2440 # nand createbbt
Create BBT and erase everything ? <y/N>
Skipping bad block at  0x00440000
Skipping bad block at  0x04100000
Skipping bad block at  0x07f80000
Skipping bad block at  0x07fa0000
Skipping bad block at  0x07fc0000
Skipping bad block at  0x07fe0000

Creating BBT. Please wait ...Bad block table not found for chip 0
Bad block table not found for chip 0
Bad block table written to 0x07fe0000, version 0x01
Bad block table written to 0x07fc0000, version 0x01 

MINI2440 # nand write 0x30000000 u-boot

NAND write: device 0 offset 0x0, size 0x40000
 262144 bytes written: OK

MINI2440 # saveenv


Now if I turn off the board, switch to nand boot and turn it on again
u-boot doesn't start.

I've also tried different methods to install u-boot but no one of them work
for me.

Loading u-boot directly with "v" option from vivi I can boot just one time
u-boot (the second time looks likes it disappears) with the following
error:

U-Boot 1.3.2-mini2440 (Sep 12 2009 - 16:17:01)

I2C:   ready
DRAM:  64 MB
Flash:  2 MB
NAND:  nand_scan(): Cannot allocate oob_buf
0 MiB


Anybody can help me?
Thanks
Renzo

Hi 
i was also facing the same problem as you are facing. but after getting the
solution from the following link it has been solved.
Please refer the following link .
very useful 
http://code.google.com/p/mini2440/wiki/MiniBringup

Thanks &  Regards
Dhaval

So what was the solution?  I've tried everything described at the URLs
above and still get the oob error.  Can you go into a little more detail?

Thanks!

It is quit possible that you should use 'nand write.e' instead of 'nand
write' as write.e "will write the error-correction bytes, and skip any bad
blocks" (http://code.google.com/p/mini2440/wiki/MiniBringup).

Here are my algorithm for flashing u-boot (please note that my u-boot size
is equal to 242332 bytes or 0x3b29c in hex):

0. Set NOR switch to NOR and power on your board

1. picocom -b 115200 /dev/ttyUSB0 --send-cmd "sx -vv"

2. param set xmodem_timeout 100000000

3. load ram 0x32000000 242332 x

4. ctrl-a, ctrl-s and type path to your u-boot.bin for example
'/tftpboot/u-boot.bin'

5. go 0x32000000

6. nand scrub

7. nand createbbt

8. nand write.e 0x32000000 0x0 0x3b29c

9. dynpart

10. dynenv set u-boot_env

11. saveenv

12. reset


I hope this example will be useful. Thanks.

P.S. I can't understand, you want to load 233472 bytes of u-boot.bin, but
you loaded 233482 bytes.

Hi can you email me the u-boot image you used for successfully bootloading
the 128MB Flash .My email is maheshkuruganti@gmail.com Thanks.

Hi Mahesh,

Check your mail.

Hi mgalemin

I have the same problem with u-boot and almost give-up. Would you mind to
share with me also your u-boot image to my email: hecsanhk@hotmail.com.

Thanks,
Puma

Hi Puma, 

Done.

Hi mgalemin,

I got it. It's great! Thanks a lot.

Puma

hi 
i have also a 128 MB board having the same problem. can you please send me
the u-boot.bin file

thank you
Ethem

sory
my e mail is ethemtug@gmail.com
 thanks again
Ethem

Same problem here with 128M NAND. Can you send me the binary file?

Thanks in advance.

Ooopppps! I forgot the email... cm_ortiz@msn.com

Hello,

i've also had the same problem. I've downloaded the u-boot source at the
git tree and compiled it. But it happens the same as renzo.

Can you please e-mail me the u-boot source for the 128Mb Flash?


Best regards,

Luís Silva

Sorry forgot my e-mail is lds@sapo.pt


Thank you,

Luís Silva

Please use next link to download u-boot.bin:

http://depositfiles.com/files/xeayrz0hm

Thanks.

Plz refer to link:-
http://narnia.cs.ttu.edu/drupal/node/131

It worked perfectly for me.

mgalemin,

Thank you for the file, the board now boots u-boot. But it still gives the
nand warning ".... Bad CRC or NAND using default environment"

Would it be too much to ask for the source code?

Neo,

Thank you for your help, but it didn't worked. Does files are for the 64MB
flash.

Luís, 

Did you scrub your flash? Try to use next commands in u-boot command line:

nand scrub
nand createbbt
dynpart
dynenv set u-boot_env
saveenv
reset

And please post a traces dump from your console with the "Bad CRC or NAND
using default environment" error with traces before and after it. Thanks.

Yes, i did the scrub. The problem was i didn't do the "dynenv set
u-boot_env" part. 

Now, following this tutorial http://narnia.cs.ttu.edu/drupal/node/131 i
wrote in the flash both a kernel and a filesystem (the ones here
http://labs.kernelconcepts.de/Projects/Micro2440/#Downloads), then booted
the board, after the kernel starts to load the modules, a whole bunch of
errors starts to appear saying "uncorrectable error: <4>mtd->read(xxx bytes
from xxx) returned ECC error. After all the errors it goes into "kernel
panic - not syncing: Attempted to kill init!".

Do you have any idea what this might be? Could it be from the images that
are made for a 64mb flash? In the cd that came with the board, there are no
files uImage and filesystem.jffs2, only zImage_T35 file and filesystem in a
img format. How can i load this into the board using the sdcard?

Thank you for your help.
Best Regards,
Luís Silva

"... returned ECC error" - this error can appear because of invalid
settings for mounting your rootfs (u-boot settings, image format etc.). Try
to flash some verified rootfs (for example try to compile your own).

In the cd that came with the mini2440, there are only images in .img
format. I cannot load these with u-boot. How can i convert them to jffs2 to
work in my 128MB NAND? Yes, that is probably the best idea. I'll try that
right away. As soon as i make some progress i'll post it.

About the u-boot source code, is it possible for you to make the source
available? I already tried to compile it, but it didn't worked.

Best regards,
Luís Silva

Well, to build your own rootfs is a not so big issue. Just use buildroot
from here http://buildroot.uclibc.org and make a couple of things:

1. Untar it and execute 'make menuconfig'

2. Change these settings:

Target Architecture
    [*] arm

Target Architecture Variant
    [*] arm920t

Target ABI: 
    [*] EABI

Toolchain
    [*] Enable RPC // need for NFS support in busybox
    [*] Use software floating point // need for for busybox 

Package Selection for the target 
    [*] <choose software you want to use in your system>

Target filesystem options
    [ ] ext2
    [*] jffs2

        Flash Type
            (x) NAND flash with 2kB Page and 128 kB erasesize

3. Save these settings and execute 'make'. You'll find ready to flash
rootfs.arm.jffs2 rootfs image in ./binaries/uclibc/ folder. Buildroot will
download and build all necessary packages (toolchain, binutils, uclibc,
busybox etc.)

For building u-boot I used sources from Buserror repo, you can download it
from this git repo http://repo.or.cz/w/u-boot-openmoko/mini2440.git.

Hi,

yes, i've already done that and it worked, but thank you for your tips
anyway.
Now i need to compile a kernel otherwise it will be impossible for me to
try the filesystem.

About the u-boot, yesterday i downloaded  the latest version from the git
tree, and compiled it by typing "make". After a while i got the
"u-boot.bin" file, but when i rebooted the board, it froze. I don't know
what it might be.

Please tell me if i could be of any assistance to you.

Best regards,

Luís Silva

Luís, 

Have you executed 'make mini2440_config' command before 'make'? You also
need to export CROSS_COMPILE env variable before compiling u-boot, for
example 'export CROSS_COMPILE=arm-linux-'. It is quit possible that you got
u-boot.bin for i386 platform.

What about the kernel - you may try kernel from Buserror repo. Try these
commands:

1. git clone git://repo.or.cz/linux-2.6/mini2440.git

2. mkdir -p ../kernel-bin

3. CROSS_COMPILE=arm-linux- ARCH=arm make O=../kernel-bin/
mini2440_defconfig

4. CROSS_COMPILE=arm-linux- ARCH=arm make O=../kernel-bin/

5. Export path to the 'mkimage' binary (it should be in your u-boot sources
directory in ./tools/ folder) or type full path in the next command.

6. mkimage -A arm -O linux -T kernel -C none -a 0x30008000 -e 0x30008000 -d
../kernel-bin/arch/arm/boot/zImage ../kernel-bin/uImage

You'll find uImage in ../kernel-bin/ folder. Of course you should export
path to your toolchain in your PATH variable or just use full path in
'CROSS_COMPILE=' part. If you want to add some extra modules to the kernel
try this command:

CROSS_COMPILE=arm-linux- ARCH=arm make O=../kernel-bin/ menuconfig

Sincerely, 
Maksim.

Hi,

this is what i've done.

"luis@luis-desktop:~/Desktop/mini2440-u-boot$ make clean
luis@luis-desktop:~/Desktop/mini2440-u-boot$ make mini2440_config 
Configuring for mini2440 board...
luis@luis-desktop:~/Desktop/mini2440-u-boot$ echo $CROSS_COMPILE

luis@luis-desktop:~/Desktop/mini2440-u-boot$ export
CROSS_COMPILE=arm-linux-
luis@luis-desktop:~/Desktop/mini2440-u-boot$ echo $CROSS_COMPILE
arm-linux-
luis@luis-desktop:~/Desktop/mini2440-u-boot$ make
for dir in tools examples api_examples ; do make -C $dir _depend ; done
make[1]: Entering directory `/home/luis/Desktop/mini2440-u-boot/tools'
make[1]: Nothing to be done for `_depend'.
make[1]: Leaving directory `/home/luis/Desktop/mini2440-u-boot/tools'
make[1]: Entering directory `/home/luis/Desktop/mini2440-u-boot/examples'
make[1]: Nothing to be done for `_depend'.
make[1]: Leaving directory `/home/luis/Desktop/mini2440-u-boot/examples'
make[1]: Entering directory
`/home/luis/Desktop/mini2440-u-boot/api_examples'
make[1]: Nothing to be done for `_depend'.
make[1]: Leaving directory
`/home/luis/Desktop/mini2440-u-boot/api_examples'
Generating include/autoconf.mk
make -C tools all
make[1]: Entering directory `/home/luis/Desktop/mini2440-u-boot/tools'
gcc -Wall -pedantic -idirafter /home/luis/Desktop/mini2440-u-boot/include
-idirafter /home/luis/Desktop/mini2440-u-boot/include2 -idirafter
/home/luis/Desktop/mini2440-u-boot/include -DTEXT_BASE=0x33F80000
-DUSE_HOSTCC -O -c -o img2srec.o img2srec.c
gcc -Wall -pedantic -idirafter /home/luis/Desktop/mini2440-u-boot/include
-idirafter /home/luis/Desktop/mini2440-u-boot/include2 -idirafter
/home/luis/Desktop/mini2440-u-boot/include -DTEXT_BASE=0x33F80000
-DUSE_HOSTCC -O  -o img2srec img2srec.o
strip img2srec
make[1]: *** No rule to make target
`/home/luis/Desktop/mini2440/include/sha1.h', needed by `mkimage.o'.  Stop.
make[1]: Leaving directory `/home/luis/Desktop/mini2440-u-boot/tools'
make: *** [tools] Error 2
luis@luis-desktop:~/Desktop/mini2440-u-boot$"

This is the error i get. Bit strange isn't it?

Still working on the kernel.

Best regards,
Luís Silva

As I can see you have sources with old object files:

make[1]: Entering directory `/home/luis/Desktop/mini2440-u-boot/tools'
make[1]: Nothing to be done for `_depend'.
make[1]: Leaving directory `/home/luis/Desktop/mini2440-u-boot/tools'

Please try to download clean sources from the repo and compile it again.

Sincerely, 
Maksim.

Hello again.


I still haven't had the time to compile the new u-boot from the git tree.
I'll do it this weekend, and report to you as soon as i can.

I've compiled the kernel, just like you told me. Created a uImage file,
loaded it to the Mini2440's 128MB NAND flash, but as soon as is starting
the kernel is freezes.
Do you have any idea what it might be?


"Hit any key to stop autoboot:  0

Loading from NAND 128MiB 3,3V 8-bit, offset 0x60000
   Image Name:   Linux-2.6.31
   Created:      2009-11-05  11:50:49 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2833752 Bytes =  2.7 MB
   Load Address: 30008000
   Entry Point:  30008000
## Booting kernel from Legacy Image at 32000000 ...
   Image Name:   Linux-2.6.31
   Created:      2009-11-05  11:50:49 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2833752 Bytes =  2.7 MB
   Load Address: 30008000
   Entry Point:  30008000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK
OK

Starting kernel ..."

Yours sincerely, 

Luís Silva

The only thing I can note is that your uImage file has strange size. I have
next traces:

Loading from NAND 128MiB 3,3V 8-bit, offset 0x60000
   Image Name:   
   Created:      2009-10-28  18:56:50 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2027436 Bytes =  1.9 MB
   Load Address: 30008000
   Entry Point:  30008000

I have built my kernel from the repo without any additional modules (with
sound patch only). Please check your cross toolchain.

Sincerely, 
Maksim.

Hi,

I just got a 128M version to work with. i'm a newbie and i flashed the nand
to load other kernel and rootfs provided in the cd. now the problem is that
those files are for 64M as pointed out and are not working at all..i've got
all sorts of problems as discussed before - kernel freexing in the end.
original problem on this thread (renzo's prob) where can i get the
bootloader for 128M and the kernel images for the same.shoud the procedure
on kernelconcepts be followed with the new bootloader? which toolchain
would work? is there a need to modify the toolchain? can anybody point out
a link which demonstrated how to compile the same if the source is
provided. 

@mgalemin : kindly send me the uboot 128M file. depositfiles is blocked in
my college.

i'll definitely create a manual if m able to revive my board...

Thanks

btw, my mail is suchakra[at]gmail.com

Hello,

i've built the kernel exacty as you told me. the reason the kernel is so
big probably has to do with the fact that when i made the mini2424_config
the program asked me for the options i wanted in the kernel, driver
support, the board, etc. So the kernel grew. The thing that may be in the
way is the compiler. Which toolchain do you use? One of those that came
with the board? Which version?

I'm still working on the u-boot porting to ARM.




Thank you for your attention.

Luís Silva

Hi Luís, 

I use cross toolchain from buildroot after compiling rootfs. I have already
told how to build everything using buildroot.

When you configure kernel using mini2424_config config file program can't
ask you anything. Try to compile clean kernel from the repo, you shouldn't
execute 'menuconfig' command.

Actually u-boot have already been ported to ARM by Buserror so you just
need to compile it. It is an _extremely_ easy operation just get normal
cross toolchain.

Sincerely, 
Maksim.

Hello,

sorry for the absence but i didn't wanted to come talk to you without doing
something.

Still haven't tried the new u-boot but it compiled. I'm using your bin
file.

I was able to compile the kernel successfully. :)

By mistake i deleted the Buildroot with the already built filesystem. It
had problems, so i wasn't very worried. But the problem is now i can't
build it again. It keeps giving me a fakeroot error.
I make exactly like you said, and it worked the first time. Now it doesn't
even compile correctly.
Well i'll keep trying and when i have progress i will show you.

Also, i've made a guide on how to compile u-boot for the mini2440 with 128
MB. If possible, i'd like you to take a look at it later and correct any
errors you find. I'll make it available either here or in my blog.

What's your opinion on this? (Or any one else's opinion?)


Best regards,
Luís Silva

I have same problem here with 128M NAND. Can you send me the binary file?

my email ananyot_dd(at)hotmail.com

thanks very much.

Hi Luís,

I got a mini2440 with 128MB flash and the "Cannot allocate oob_buf
" problem as other people for the u-boot.bin compiled the code from
git://repo.or.cz/u-boot-openmoko/mini2440.git .

although the u-boot.bin provided by mgalemin at
http://depositfiles.com/files/xeayrz0hm (on the above post) solved that
problem, but could you please show us the code and guide on how to compile
u-boot ?


Thanks a million,
Paul,

Hi,
I have big problem with mini2440 cards.
It doesn't star the linux.
So I have installed the u-boot(version 1.3.2-mini2440 (Oct  6 2009 -
12:51:09)) and it seems to work.
But when I instakked uImage and try to start it then next error:
'VFS: Cannot open root device "mtdblock3" or unknown-block(31,3)
Please append a correct "root=" boot option; here are the available
partitions:
1f00             256 mtdblock0 (driver?)
1f01             128 mtdblock1 (driver?)
1f02            5120 mtdblock2 (driver?)
1f03          125568 mtdblock3 (driver?)
b300          123008 mmcblk0 driver: mmcblk
  b301          122959 mmcblk0p1
Kernel panic - not syncing: VFS: Unable to mount root fs on
unknown-block(31,3)'

What this mean and what I will be able to try?

Hi,
I have solved some problems.  I built
git://repo.or.cz/linux-2.6/mini2440.git package and converted zImage to the
uImage.  I installed the uImage and after that I installed
gpe-image-micro2440.jffs2( http://narnia.cs.ttu.edu/drupal/node/131).
So now it seems to work but I don't know what is correct login/password.
Does anyone know what it correct login and password?
(And why this is so complicated?).
And how I can install the root_qtopia?  Now I have image file and source
code but it not include any makefile.  How I can build it?

@paul 
follow the instruction here to build u-boot from git repository
http://wiki.linuxmce.org/index.php/Mini2440
if you do not have ARM cross-tools then yet then it is not bad idea to
start with compiling openembedded first because you will get all those
cross-tools you will ever need, good description is here
http://www.electronics.diycinema.co.uk/?p=109

For recent mini2440 with 128MB Flash/2K you should use generated image
called u-boot-nand2k.bin
regards ufon

Hello,

I've got a couple of problems. I've got a working u-boot.bin from this
thread and it works fine. None of the others I've compiled following any
directions above have worked. they start loading, I see it showing the RAM
and flash, and  then there are a couple of odd characters and it crashes
and I get thrown back to vivi. Thats using buserrors code and compiling is
exactly that way his wiki page says. I'm using my openembedded arm
toolchain as well which I know works because I've compiled several things
for this already which have all worked.

I'm trying to find a NEWER version of u-boot because I think the one
buserror has used has some problems with the SD reader on my Micro2440. I
always get mmc_block_read: err SDIDSTA=0x00000020, after a bunch of Time
Outs. Other people have had the same problem, yet nobody seems to address
it. If buserror's version of u-boot cannot handle SD/SDHC then I cant boot
from SD. 

Any help would be appreciated.

Thanks
Bill

Just struggling with a similar problem.  Did you read the blogger comments
on buserror's site.

You have to go through some juggling to get his u-boot image to work.  Best
to read his comments.

Well I fixed my own problem.I got tired of following all these directions.
So I just went in to supervivi and hit [v] Download vivi, and I uploaded
u-boot that I compiled myself to that. And I switched back to Nand and
reset the board. The U-Boot I compiled dated Jan 7, 22:31:01, popped right
up. No more weird errors. When i followed the directions from buserrors
page, when I would "go" to the address and run u-boot, it would load twice
and then crash back to supervivi spitting out a few weird characters and
saying something about oob_buf... 

For me, this seems so far, to have worked. SD cards work now too

Nevermind, I realised how stupid that was after I wrote it. If you write it
to nand and then boot it up and scrub the nand, and create a bad block
table, you end up wiping out u-boot which is why it need sto be running
from ram first ... lol... 

So much for my quick answer... Now back to finding out why I cant load it
the correct way. :D

I ended up using the u-boot that Forrest Bao used in his tutorial, which
uses the download package off KernelKoncepts.

Possibly the same u-boot as you can get off the Downloads page on this
site.

Well if anyone has any information on compiling u-boot to work with the
128MB board, I'd be very interested. The u-boot.bin that mgalemin posted
does work, however the SD card reader does not work with it. I think the
u-boot ssource that mgalemin used is older. 

I need the SD card to work. And I need a compilable u-boot that is made to
work for the device I have, and not the 64MB one. And so far, everyone's
got all these instructions, apparently nobody who is writing these
instructions actually own a modern mini2440. 

On Buserror's google code page, he even has a script that downloads a
toolchain, and uboot from the repository, and compiles it for the mini2440
and even the uboot code produced from that doesnt work corretly for me. I
don't know if its the fact that I'm using a 64bit system to compile but im
beginning to suspect it. 

Does anyone have any ideas? 

Bill

Did you sign in to look at his blog comments?

***
The new u-boot doesn't work in RAM. Somehow the interupt code that I added
to get USB working makes it crash when launched at an arbitrary address.

To make it work anyway, edit include/configs/mini2440.h and disable the
interupt #define. That will build you a u-boot that works in ram, but
without usb. Once that is in RAM and runs, build another u-boot to flash to
NAND...
***

I don't know how I missed that. I'll try it out. Thanks dave.

Bill, when you have compiled both versions, can you please post them here
for download? I have a new board with 256 MB. U-Boot from the link above
stops with:

U-Boot 1.3.2-mini2440 (Oct  6 2009 - 12:51:09)

I2C:   ready
DRAM:  64 MB
Flash:  2 MB
NAND:  nand_scan(): Cannot allocate oob_buf
0 MiB

Try my blog for now. Try to follow the directions for compiling U-Boot that
I give which shows how to alter the u-boot source to run from RAM.

http://bill.station51.net

please feel free, anyone, to comment if you see something rediculously
stupid that I might be doing. This is all just my notes and rants but I'm
also trying to be helpful. So please be sure to pass on corrections.

Hm, I don't to get it working on 256 MB NAND.

It probably won't work until Buserror adds support for that to it. He
supposedly has autodetect support for 64 and 128, but I dont know about
256.

Hi Maksim,

I am using u-boot128MB.bin downloaded from friendlyarm.net's download page.

I am confused with dynpart.  after dynapart it shows:

0x00040000 u-boot
0x00020000 u-boot_env
0x00500000 kernel
0x07aa0000 rootfs

I guess 0x00040000 is the end of u-boot.

Also dynenv set command needs address.  So which address i should use ??  I
tried dynenv set u-boot_env, and it did not work.  It requires some address
there.


TIA

Vikas

In this tutorial

http://narnia.cs.ttu.edu/drupal/node/131

he uses

dynenv set 40000

Haven't heard that uboot has grown sufficiently to cause this to change. 
You'll soon find out!

Good luck

Shame to say, it changes nothing.

MINI2440 # mtdparts                    

device nand0 <mini2440-nand>, # parts = 4
 #: name                        size            offset          mask_flags
 0: u-boot              0x00040000      0x00000000      0
 1: env                 0x00020000      0x00040000      0
 2: kernel              0x00500000      0x00060000      0
 3: root                0x03aa0000      0x00560000      0

(For the 64M version)

env offset is 0x00040000, it's size is 0x00020000

So, the end of u-boot env is 0x00060000

Don't know what dynparts is . . . I use mtdparts.

Now, you got me worried as the tutorial I mentioned says to:
dynenv set 40000 before putting the kernel and rootfs in.  At the end you
set up the environment variables.

Now, if you go back in and erase from 40000 it appears to me that you would
lose the environment variables.

This doesn't seem to happen.

***
Now, if you go back in and erase from 40000 it appears to me that you would
lose the environment variables.
***

Ignore this comment.  I imagine if I did say to erase from the start of
u-boot env then you would have to put the environment variables back in!

The next line in the tutorial says to:
nand erase kernel, which starts at 0x00060000 not 0x00040000

Sorry, for any confusion

Thanks Dave,

Yesterday night i found this, but was lazy to update the status here.

Thanks once again.

Vikas

Hi This is Babu, I am using MINI2440 with 128Mb RAM, i need u-boot for this
configuration.

Thanks 
-----

Hi,
   I brought mini s3c2440 recently. I need to flash U-Boot on NOR flash
instead of NAND, (so that I can leave my current setting with out
disturbing). Then I need to boot OS from SD Card. So that I can create
different images on SD card & I can insert according to my need, When I 
change the boot switch on NOR.

Any one tried this or any one know how to do this. 

Any help is appreciated

Hi folks,

I've been struggling with U-boot on the Mini2440 for several days now,
going through the various forums and lists that have any info on it.  I can
download buserror's original binary, uboot.bin, and it works.  I haven't
tried loading that to flash because I suspect it will fail since I have the
128 MB flash.

But when I build U-boot from the GIT source, it just hangs.  The IRQ line
in mini2440.h is commented out.  I've tried two different tool chains.  I
sure hope someone may have some insight into this.

Thanks,

Doug

Have you read through all these?

https://www.blogger.com/comment.g?blogID=11320970&postID=41189769619...

Hi can you email me the u-boot image you used for successfully bootloading
the 128MB Flash .My email is kirti.patil2386@gmail.com 

Thanks & Regards

http://www.friendlyarm.net/downloads#software

hi,
    Do u have u-boot image for the following specification.
         I am using freebsd.
            Board:smdk2410
            processor:ARM920T, s3c2410
        If not binaty image, source code for the same will be helpful.
Either send the link on this forum or mail me.
        My email is kirti.patil2386@gmail.com      
       
Thanks & regards
kirti