HOWTO: Compiling and Flashing U-Boot onto Mini2440

By Bill » Saturday, January 16 2010, 13:41

The bootloader that comes factory installed on the Micro2440 and the Mini2440 board is called Supervivi. I don't personally like it. It has very limited support and requires a YAFFS filesystem for the root filesystem. So when I bought my board I began to immediately search out an alternative. The bootloader by choice, it seems, is a modified version of U-Boot with modifications for the Mini2440 board's hardware

The code is maintained by a guy named buserror. I'll provide his information at the end of this howto.

At the time of writing this, I had some issues with getting Buserror's U-Boot working correctly.

The code that is in his git repository, doesn't run from RAM without a modification to the source. So here are the instructions that I gathered for altering and compiling it, and getting it going on the Mini2440 and Micro2440 board.

For this to work, I'm going to assume that you have a crosscompiler set up. Later on, I will probably write an entry here about setting that up, but not now. I'm also assuming you have git installed.

Step 1: Get the source

mkdir uboot ; cd uboot
git clone git://repo.or.cz/u-boot-openmoko/mini2440.git

Step 2: Set your cross compiler prefix so you don't end up compiling this for x86.

export CROSS_COMPILE=arm-none-linux-gnueabi-

Step 3: Modify the source to disable CONFIG_USE_IRQ. Open include/configs/mini2440.h.

#define USE_920T_MMU
//#define CONFIG_USE_IRQ                    1       /* Needed for USB device! */

Disabling this obviously disables the use of USB During boot. You can fix this by reflashing a normal copy of u-boot from within u-boot once this is up and running. In the above example, I commented it out but you can probably just change the 1 to a 0.

Step 4: Make and compile.

 cd ../../
 make mini2440_config
 make

Assuming this all compiles correctly, you will have a u-boot.bin file in your directory now as well as a 2k and 16k block size bin file. Those two are for flashing inside of U-Boot. The normal .bin is for flashing from ram from within supervivi.

Step 5: Flashing u-boot to the mini2440. In this example, we'll be using DMW for Windows to transfer the binary over to the board with the supplied USB cable.

5a. Set boot switch to NOR.

5b. When supervivi pops up, hit q for supervivi shell.

5c. Load the image in to ram at 0x32000000 (6 zeros) memory location.

 shell> load ram 0x32000000 <uboot bin size in bytes> u-boot

5d. Use DNW to transfer the u-boot.bin from your computer to the board.

5e. Execute the loaded bin file you loaded in to RAM.

shell> go 0x32000000

5f. You should now be inside u-boot at a MINI24440# prompt. Now we prepare the NAND.

MINI2440# nand scrub

5g. Create the bad block table.

MINI2440# nand createbbt

5h. Write the u-boot that we're running at 0x32000000, to the NAND.

MINI2440# nand write.e 0x32000000 0x0 <u-boot bin size in hex>

5i. Partition the NAND.

MINI2440# dynpart

5j Create the dynamic environment space for u-boot.

MINI2440# dynenv set u-boot_env

5k. Save the environment to NAND.

MINI2440# saveenv

You can now set the boot switch back to NAND and reboot the system. It should pop up with U-Boot and give you a MINI2440# uboot prompt. From this point on you can do all your work inside U-boot for loading images for the kernel and for the filesystem. I would like to note though, that in the above examples, you need to know your u-boot bin file size in both bytes and in hex. You can use google to convert the file size in bytes to hex. (i.e. "233907 to hex" in the google search box). I recommend trying to run u-boot without the source modification first before disabling IRQ because I'm guessing at some point, buserror or someone else will figure out why it won't run from RAM with that enabled. If it fails, and you can always modify the source and recompile.

I'd like to note that I collected these instructions from various sites and I've re-worded and explained them some to help. I hope that this helps you.

Here are some useful links for u-boot and other things:

http://bliterness.blogspot.com/ - Busseror's blog

http://code.google.com/p/mini2440/ ... - Buserror's Google code page.

http://repo.or.cz/w/openembedded/mi... - Git repository for the modified Openembedded

http://repo.or.cz/w/u-boot-openmoko... - Git repository for u-boot

UPDATE: MAY 8th, 2010: As of writing this update, the code in the git repository already has the above modification to the code. If you for any reason require USB support on your bootloader, you will need to uncomment the line that is commented out above and recompile.

UPDATE MAY 31st, 2010: There have been some problems with the current repository code and it won't run from RAM for some devices. So here's a quick workaround.

1. Switch the system to NOR and boot with supervivi.
2. hit v in supervivi
3. i uploaded the u-boot.bin file
4. switch the system to NAND and boot up with u-boot. You'll get some errors.
5. Run nand scrubs and createbbt
6. switch back to NOR
7. hit v again and upload U-boot since you just erased it.
8. switch back to nand and it should boot up with minimal errors using u-boot.
9. run the dynpart and dynenv and saveenv as mentioned above.

You should have a working u-boot... I'm currently getting an error about it not seeing my nand but it seems to be able to access it. Maybe you guys can let me know if you see anything wrong. I am suspecting there is a problem with the new u-boot code. Maybe buserror can shed some light on this.

//Bill Sargent

Questions? Comments? Need Help? Go to my forum and ask there.

« Welcome to my FriendlyARM Mini2440 - Micro2440 - Openembedded and Bitbake Stupidity and Odd results »

Comments

1. On Sunday, January 17 2010, 19:48 by regnirps

Bill, where are you getting your information? I'm puzzled by your choices of where to start and what to use. Why not Angstrom, or the Chinese 2.6.32? Are you using the mainstream sources? www.bliternes.blogspot.com? Email me and I'll send you some stuff.

2. On Monday, February 1 2010, 05:11 by Amit

Hi
Are there any changes required to build u-boot for 128MB boards.

regards
Amit

3. On Monday, February 1 2010, 07:42 by Bill

No, it should work with the instructions I've given above without special modifications for 128MB Boards. The new code for u-boot from Buserror has auto-detection for 128MB. The only alteration is the disabling of IRQ mentioned above but thats for both 64 and 128MB.

4. On Wednesday, February 10 2010, 11:02 by Amit

Hi
I have a 128Mb board. I was successful in compiling & installing u-boot to the and as suggested in you blog. I also loaded up the the kernel and the root fs as generated by openembedded. On reset u-boot loads the kernel but is not able to execute it .

Any pointers is as to what is happening ???

regards
--Amit
Listed is the capture of boot sequence also listed are
capture of mtdparts & printenv
===============================================================
MINI2440 # resetþ
U-Boot 1.3.2-mini2440 (Feb 8 2010 - 10:59:13)
I2C: ready
DRAM: 64 MB
Flash: 2 MB
NAND: 128 MiB
Found Environment offset in OOB..
USB: S3C2410 USB Deviced
In: serial
Out: serial
Err: serial
MAC: 08:08:11:18:12:27
Hit any key to stop autoboot: 0

Loading from NAND 128MiB 3,3V 8-bit, offset 0x60000
Image Name:
Created: 2010-02-09 12:25:48 UTC
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 2041256 Bytes = 1.9 MB
Load Address: 30008000
Entry Point: 30008000
## Booting kernel from Legacy Image at 32000000 ...
Image Name:
Created: 2010-02-09 12:25:48 UTC
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 2041256 Bytes = 1.9 MB
Load Address: 30008000
Entry Point: 30008000
Verifying Checksum ... OK
Loading Kernel Image ... OK
OK
===============================================================

Capture of mtdparts & printenv
===============================================================
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 0x07aa0000 0x00560000 0

active partition: nand0,0 - (u-boot) 0x00040000 @ 0x00000000
defaults:
mtdids : nand0=mini2440-nand
mtdparts: <NULL>

===============================================================
===============================================================
MINI2440 # printenv
baudrate=115200
ethaddr=08:08:11:18:12:27
usbtty=cdc_acm
mtdparts=mtdparts=mini2440-nand:256k@0(u-boot),128k(env),5m(kernel),-(root)
mini2440=mini2440=0tb
bootargs_base=console=ttySAC0,115200 noinitrd
bootargs_init=init=/sbin/init
root_nand=root=/dev/mtdblock3 rootfstype=jffs2
root_mmc=root=/dev/mmcblk0p2 rootdelay=2
root_nfs=/mnt/nfs
set_root_nfs=setenv root_nfs root=/dev/nfs rw nfsroot=${serverip}:${root_nfs}
ifconfig_static=run setenv ifconfig ip=${ipaddr}:${serverip}::${netmask}:mini2440:eth0
ifconfig_dhcp=run setenv ifconfig ip=dhcp
ifconfig=ip=dhcp
set_bootargs_mmc=setenv bootargs ${bootargs_base} ${bootargs_init} ${mini2440} ${root_mmc}
set_bootargs_nand=setenv bootargs ${bootargs_base} ${bootargs_init} ${mini2440} ${root_nand}
set_bootargs_nfs=run set_root_nfs; setenv bootargs ${bootargs_base} ${bootargs_init} ${mini2440} ${root_nfs} ${ifconfig}
mtdids=nand0=mini2440-nand
autostart=no
autoload=no
dnsip=10.0.0.1
filesize=980000
fileaddr=31000000
gatewayip=10.0.0.10
netmask=255.255.0.0
ipaddr=10.0.243.222
serverip=10.0.0.1
bootcmd=nboot.e kernel ; bootm
bootargs=console=ttySAC0,115200 mini2440=3tb root=/dev/mtdblock3 rootfstype=jffs2

bootdelay=0
partition=nand0,0
mtddevnum=0
mtddevname=u-boot
Environment size: 1271/131068 bytes

===============================================================

5. On Monday, February 15 2010, 11:21 by Bill

Well Amit, to begin with your bootargs is wrong. Your root device shouldnt be mtdBLOCK3.... it should be mtdblk0p3

Please try to correct that and see what happens. It should work per my instructions. I've just now following my own instructions using the latest uboot from the mini2440 git repository and it's working fine.

My apologies for not responding sooner, I just didn't see this comment.

6. On Monday, March 1 2010, 15:08 by say2paul

You have not specified the OS you are using to compile and flash u-boot to mini2440

Also certain information is unclear like where to set cross comiler prefix, etc.

7. On Monday, March 1 2010, 15:17 by Bill

Hello say2paul... I didn't mention those things because it's a given. Not to be like every other linux dork out there, but if you don't know some of this stuff already, this particular tutorial is already out of your ability and learning some basic stuff about Linux is necessary. Teaching people to use linux goes beyond the scope of this documentation. I used Debian Linux for this, 64bit. And the cross compiler prefix setting is done at the command prompt. Please let me know if you have any further questions :)

8. On Sunday, April 25 2010, 10:15 by max2440

Hi Bill
Am new to linux , i bought micro2440 too and i want to port Uboot to it , The source code that i got with DVD does not have "mini2440.h" in "configs " folder am having problem in porting . Could you please send me the Source code and the U-boot image for Micro2440 my id is muthuk03@gmail.com.
thank U

Max2440

9. On Sunday, April 25 2010, 11:53 by Bill

@max2440 : I'm sending you an email but I really don't recommend you use the source from the DVD. It's old. You should instead follow my directions above for obtaining the newest source and compiling it.

10. On Monday, April 26 2010, 10:14 by Max2440

Hi Bill

thanks a lot for your support . i can not access internet on my linux pc coz i use my phone to connect to internet that's why i asked for Uboot source code.

Let me see if i have any other option

11. On Monday, May 10 2010, 21:08 by Bloggins666

Bill,

I've been posting on the FriendlyArm Forum under the "Linux" topic and have added a sub-topic "Linux, u-boot, 256M NAND and rootfs".

I just wanted to see if you could look it over please. I was able to flash u-boot into NAND using your instructions and using u-boot that was the git repository at the time. As you can see with my post I suspect that something has changed in the repository. In fact my friend did a diff between what I had and what is current and there are some changes. Bottom line, the repository does not seem to work.

Do you have time to check this out? For selfish reasons I would like to find out if I'm insane or not.

Cheers!!

12. On Monday, May 10 2010, 22:06 by Bill

Hi,

I replied over there. I'll repeat my request here too. I'd like to see the log of what the kernel is doing and your environment variables as well. :)

Thanks,
Bill

13. On Tuesday, May 11 2010, 18:16 by flux000

Hello All,

How do i use u-boot with zImage_T35 and root_qtopia-64M.img (i.e. i loaded zImage_T35 and root_qtopia-64M.img but when i reboot, i got error msg "bootcmd: wrong image").

1. fatload mmc 0:1 0x31000000 zImage_T35
2. nand write 0x31000000 kernel
3. nand erase root
4. fatload mmc 0:1 0x31000000 root_qtopia-64M.img
5. nand write 0x31000000 root ${filesize}
6. setenv bootcmd nboot.e kernel \; bootm
7. saveenv

Thanks,

flux000

14. On Tuesday, May 11 2010, 18:21 by Bill

Hi flux000,

U-Boot uses uImage files, not zImage. You'll need to use the utility that comes with u-boot called mkimage to convert it. You'll need to google for how to use mkimage. I don't have the exact usage of it on hand right now.

Also you don't need to cross-post your questions in multiple entries on the blog here :) This isn't a public forum, it's just me.

15. On Tuesday, May 11 2010, 22:18 by flux000

Hi Bill,

Thanks for the rapid reply. I will google the tool and test it out... I will post my findings...

My apology for the multiple entries.

Thanks,

flux000

16. On Wednesday, May 12 2010, 03:25 by flux000

Hello All,

1. To install mkimage type "apt-get install uboot-mkimage" in Ubuntu terminal.
2. To convert zImage to uImage type "mkimage -A arm -O linux -T kernel -C none -a 0x30008000 -e 0x30008000 -d zImage uImage" at the terminal or "mkimage --help" to see what argument to pass to mkimage

After the conversion, i loaded uImage and root_qtopia-64M.img and the environment variables are set as followed:

bootdelay=3
baudrate=115200
ethaddr=08:08:11:18:12:27
ipaddr=10.0.0.111
serverip=10.0.0.4
netmask=255.255.255.0
usbtty=cdc_acm
mtdparts=mtdparts=mini2440-nand:256k@0(u-boot),128k(env),5m(kernel),-(root)
mini2440=mini2440=0tb
bootargs_base=console=ttySAC0,115200 noinitrd
bootargs_init=init=/sbin/init
root_mmc=root=/dev/mmcblk0p2 rootdelay=2
root_nfs=/mnt/nfs
set_root_nfs=setenv root_nfs root=/dev/nfs rw nfsroot=${serverip}:${root_nfs}
ifconfig_static=run setenv ifconfig ip=${ipaddr}:${serverip}::${netmask}:mini2440:eth0
ifconfig_dhcp=run setenv ifconfig ip=dhcp
ifconfig=ip=dhcp
set_bootargs_mmc=setenv bootargs ${bootargs_base} ${bootargs_init} ${mini2440} ${root_mmc}
set_bootargs_nand=setenv bootargs ${bootargs_base} ${bootargs_init} ${mini2440} ${root_nand}
set_bootargs_nfs=run set_root_nfs; setenv bootargs ${bootargs_base} ${bootargs_init} ${mini2440} ${root_nfs} ${ifconfig}
mtdids=nand0=mini2440-nand
filesize=3477000
bootcmd=nboot.e kernel ; bootm
root_nand=root=/dev/mtdblock3 rootfstype=yaffs
partition=nand0,0
mtddevnum=0
mtddevname=u-boot
bootargs=root=/dev/mtdblock3 rootfstype=yaffs console=ttySAC0,115200 mini2440=0tb

However after reset, i got the following msges.
....
.....
s3c2410-rtc s3c2410-rtc: setting system clock to 2010-09-09 01:31:53 UTC (1283995913)
yaffs: dev is 32505859 name is "mtdblock3"
yaffs: passed flags ""
yaffs: Attempting MTD mount on 31.3, "mtdblock3"
yaffs_read_super: isCheckpointed 0
VFS: Mounted root (yaffs filesystem) on device 31:3.
Freeing init memory: 160K
Warning: unable to open an initial console.
Kernel panic - not syncing: No init found. Try passing init= option to kernel.
Backtrace:
<c0035270> (dump_backtrace+0x0/0x10c) from <c03958f0> (dump_stack+0x18/0x1c)

r7:00000000 r6:c0503ed0 r5:c0503660 r4:c04c61a0

<c03958d8> (dump_stack+0x0/0x1c) from <c0395940> (panic+0x4c/0x134)
<c03958f4> (panic+0x0/0x134) from <c00305a4> (init_post+0xec/0x178)

r3:00000000 r2:c3949200 r1:c0539000 r0:c045348c

<c00304b8> (init_post+0x0/0x178) from <c00084c4> (kernel_init+0xf4/0x124)

r5:c00205d4 r4:c00205d4

Any possible solution?

Thanks,

flux000

17. On Friday, May 14 2010, 19:47 by stereo_m

Hello! Do I need to make any changes for building u-boot for the 1GB NAND mini2440 board? I can't get u-boot to work when I load it into ram, only if I load it into nand flash. I have compiled u-boot myself and also tried the bianry on this page, with the exact same results.

If I load the u-boot.bin with "load ram 0x32000000 239636 u" and then "go 0x32000000". Then I
get the following output:

Supervivi> go 0x32000000
go to 0x32000000

 argument 0 = 0x00000000
 argument 1 = 0x00000000
 argument 2 = 0x00000000
 argument 3 = 0x00000000

and it just stops there until I reset the board. I don't get the "MINI2440#" prompt like in the guide.

I have also tried the guide at http://wiki.linuxmce.org/index.php/...
Using the "load flash 0 239636 u" works, but I need to switch the NOR-switch to off-position (away from the edge of the board) to get to the MINI2440# prompt. In NOR-mode I get to the supervivi-prompt. That would be okay, but if I try to do the nand scrub and nand createbbt, I think it erases itself from NAND, because it doesn't work after reset after doing scrub and createbbt.

Is there any solution? What could I be doing wrong?

18. On Friday, May 14 2010, 19:52 by Bill

Hi Stereo_m,

I don't have a 1gB NAND board to try it on, but other people have been telling me that they're getting the same issue with the 256MB board as well. So I can only assume theres a problem with u-boot on those boards right now. I don't really have a solution for you at this point. If someone is willing to send me a 1GB NAND board, I'd be happy to try and diagnose it ;-)

And yes, you are flashing it to the NAND and then erasing it by scrubbing the NAND and creating the bbt.. It needs to be able to run from RAM, so you can create the bad block table, and THEN write it to the NAND.

Thanks,
Bill

19. On Friday, May 14 2010, 20:01 by Bill

Hi flux000,

Try changing

bootargs_init=init=/sbin/init

bootargs_init=init=/linuxrc

Let me know if that works :)

Bill

20. On Friday, May 14 2010, 20:03 by flux000

Bill,

Any solution to my problem posted on May 12 2010, 03:25:

Warning: unable to open an initial console.
Kernel panic - not syncing: No init found. Try passing init= option to kernel.

flux0000

21. On Friday, May 14 2010, 20:04 by Bill

Yes flux000,

See above :)

Thakns

22. On Friday, May 14 2010, 20:44 by flux000

Bill,

I set bootargs_init=init=/linuxrc however i still get the same msg

yaffs: dev is 32505859 name is "mtdblock3"
yaffs: passed flags ""
yaffs: Attempting MTD mount on 31.3, "mtdblock3"
yaffs_read_super: isCheckpointed 0
VFS: Mounted root (yaffs filesystem) on device 31:3.
Freeing init memory: 128K
Warning: unable to open an initial console.
Kernel panic - not syncing: No init found. Try passing init= option to kernel.

Previous post was 2 min apart :)

Thanks,

flux000

23. On Friday, May 14 2010, 20:47 by Bill

Hi flux000,

Well I'm out of ideas. Why do you want to run u-boot if you're going to use the yaffs image of qtopia? Supervivi does that just fine. I use u-boot because I don't want to use yaffs, and because I was to boot from SD card. If I didn't need to do those things, I'd just keep supervivi on there.

Thanks

24. On Friday, May 14 2010, 21:02 by stereo_m

Hi Bill,
How important is it to create the bbt if I run everything from a SD card? I mean, if I put the kernel and debian on a SD card, could I get it running well without the scrub and bbt? It's actually easier for me if I could have everything on a SD card.
Can u-boot be used from the NAND without the scrub+bbt, or would it be too unreliable? If that would work I would be really happy. Like you have done here: http://bill.station51.net/index.php...

25. On Friday, May 14 2010, 21:42 by Bill

Hi Stereo_m,

I'm pretty sure you need to run createbbt for u-boot to reliably save it's environment variables. but you can try to do it without. It is worth a try :)

Let me know how it turns out.
Thanks,
Bill

26. On Sunday, May 16 2010, 11:44 by bob

Scrubbing a nandflash is a VERY risky thing to do.

If U-Boot does not save the manufacturers bad block data before scrubbing
and if it does not replace it correctly

Then you are setting yourself up for all sorts of random errors later.

27. On Sunday, May 16 2010, 17:47 by flux000

Bill,

You have a valid point. So i have decided to install u-boot and GPE. Now i am facing a different issue.

When a Qt application (e.g fluidlauncher) is started and i touch the screen, sometimes application in the background or desktop is activated. Is there a way to prevent the background apps from activating when running Qt application?

My environment variables are shown below.

export TSLIB_TSEVENTTYPE=INPUT
export TSLIB_CONSOLEDEVICE=none
export TSLIB_FBDEVICE=/dev/fb0
export TSLIB_TSDEVICE=/dev/input/touchscreen0
export TSLIB_CALIBFILE=/usr/local/tslib/etc/pointercal
export TSLIB_CONFFILE=/usr/local/tslib/etc/ts.conf
export TSLIB_PLUGINDIR=/usr/local/tslib/lib/ts
export QWS_MOUSE_PROTO=tslib:/dev/input/touchscreen0

Thanks,

flux000

28. On Monday, May 17 2010, 13:12 by Bill

Hi "Bob",

Actually, instructions all over the net tell you to do this. I think you're misinformed. I'm nearly positive you are. While I'm not an expert with NAND, I do tend to follow the masses on this and when everything says its fine, and only you say it's not.... If you can provide proof, or a link suggesting what you say is true, I'd be happy to look at it...

Bill

29. On Monday, May 17 2010, 13:14 by Bill

Hi flux000,

I don't know. I've not messed with Qt very much. Might be a question for the mailing list. :) I plan to mess with Qt more this summer if I can get things in order here.

Thanks,
Bill

30. On Tuesday, May 18 2010, 21:52 by Tara

Hi stereo_m,

I'm having the same problem with my 256 MB mini2440. I compiled the latest uboot source and after I load it to RAM, I do not get beyond:
Supervivi> go 0x32000000
go to 0x32000000

 argument 0 = 0x00000000
 argument 1 = 0x00000000
 argument 2 = 0x00000000
 argument 3 = 0x00000000

Do you or anybody have any solution/workaround to this?

Thanks,
Tara

31. On Thursday, May 20 2010, 19:21 by stereo_m

hi Tara,
I think I got it working with the u-boot-nand2k.bin file posted in this thread at 18.5.2010: http://www.friendlyarm.net/forum/to...

Starting u-boot from ram still gave the "argument 0 = 0x00....." errors, but after that it continued normally, and I was able to do the nand scrub and nand createbbt, and save it to flash. It also starts from NAND as it should. You could try that and report if it works.

32. On Saturday, May 22 2010, 10:38 by Bill

Hello everyone,

After finally getting around to testing this myself, I'm getting the same errors you are.

Bill

33. On Saturday, May 22 2010, 11:36 by Bill

Alright everyone, here's what I did to fix it.

1. Switch the system to NOR and boot with supervivi.
2. hit v in supervivi
3. i uploaded the u-boot.bin file
4. switch the system to NAND and boot up with u-boot. You'll get some errors.
5. Run nand scrubs and createbbt
6. switch back to NOR
7. hit v again and upload U-boot since you just erased it.
8. switch back to nand and it should boot up with minimal errors using u-boot.
9. run the dynpart and dynenv and saveenv as mentioned above.

Bill

34. On Wednesday, May 26 2010, 16:05 by flux000

Info for anothers: Answer to May 16 2010 post.

I had to commented out "/bin/qtopia" in the file "rcS" located here
"/etc/init.d/rcS" and i was able to start my app without touchscreen
issues.

It turns out that we cannot run qtopia desktop with our apps otherwise we
will get touchscreen interference with qtopia desktop.

Credit: Paolo @ http://www.sereno-online.com/site/2...

flux000

35. On Wednesday, May 26 2010, 23:39 by Belina76

I have also made a guide for installing android in the Mini2440. I was able, after some effort, to install in the 1gb version. I have published it to help others who could not.

If you think it will help, please send this link to others.

https://sites.google.com/site/belin...

Thanks

36. On Tuesday, June 1 2010, 01:31 by digital wiz

Hi Bill,

You seem to have one of the most active Mini2440 forums out there on the web. Thanks for doing this.

I have a Mini2440 with 128 MB of flash. I have two problems:
1. When I build u-boot from buserror's git repository, it hangs as some others have reported here. The pre-built binary works fine so that's what I'm using and I can defer this problem until later.
2. Mounting the root file system from flash is not working under any of several circumstances that I've tried. Trying to mount a JFFS2 file image reports that it can't open root device "mtdblock3". The root_qtopia-128M.img YAFFS image mounts but then reports that it can't open the console and can't find /sbin/init. I get essentially the same result from the yaffs file system image that I built. Here is the relevant boot up output:

yaffs: dev is 32505859 name is "mtdblock3"
yaffs: passed flags ""
yaffs: Attempting MTD mount on 31.3, "mtdblock3"
yaffs: auto selecting yaffs2
block 575 is bad
yaffs_read_super: isCheckpointed 0
VFS: Mounted root (yaffs filesystem) on device 31:3.
Freeing init memory: 128K
Warning: unable to open an initial console.
Failed to execute /sbin/init. Attempting defaults...
Kernel panic - not syncing: No init found. Try passing init= option to kernel.

Any words of wisdom? TIA

37. On Tuesday, June 1 2010, 01:53 by Bill

Hi Everyone,

If you could all move over to the forums and register, I'd like to answer questions there from now on. It's too hard to follow the questions here. Please visit http://billforums.station51.net and you will find all of these HOWTO posts on the forum and can ask your questions there. Thanks

Bill

38. On Tuesday, June 8 2010, 02:26 by jalal

hi bill and thank you very much. your weblog is very useful for me.

i have a problem making uboot. i get buserror uboot from git repository and set PATH and CROSS_COMPILE i make mini2440_config successfully but when i run "make all" i get this error

for dir in tools examples api_examples ; do make -C $dir _depend ; done
make1: Entering directory `/home/jalal/uboot/mini2440/tools'
make1: Nothing to be done for `_depend'.
make1: Leaving directory `/home/jalal/uboot/mini2440/tools'
make1: Entering directory `/home/jalal/uboot/mini2440/examples'
make1: Nothing to be done for `_depend'.
make1: Leaving directory `/home/jalal/uboot/mini2440/examples'
make1: Entering directory `/home/jalal/uboot/mini2440/api_examples'
make1: Nothing to be done for `_depend'.
make1: Leaving directory `/home/jalal/uboot/mini2440/api_examples'
Generating include/autoconf.mk
make -C tools all
make1: Entering directory `/home/jalal/uboot/mini2440/tools'
ln -s ../libfdt/libfdt_internal.h libfdt_internal.h
make1: execvp: ln: Too many levels of symbolic links
make1: *** libfdt_internal.h Error 127
make1: Leaving directory `/home/jalal/uboot/mini2440/tools'
make: *** tools Error 2

could you help me please?
thanks and sorry for my poor english!!

39. On Tuesday, June 8 2010, 22:46 by Bill

Hi Jalal,

I will need to know more about your environment before I can answer. What distro are you using, and are you running as root or as a regular user (like you should)?

I would recommend erasing the stuff you downloaded and starting over, without being able to see it, it sounds like something has gotten screwed up when you grabbed the files from the git repository. There shouldn't be that many levels of sym links.

Thanks,
Bill

40. On Saturday, June 19 2010, 11:47 by alex

Can we run u-boot from Nor flash in mini2440(friendly arm)

41. On Saturday, June 19 2010, 11:50 by alex

Hi
if we want to run u-boot-1.1.6 from NOR falsh in mini2440,what chages are required?
could you please help me?

Thanks
Alex

42. On Saturday, June 19 2010, 21:25 by Bill

Hi Alex, please ask your question in the forum. The top of the page has a link to it.

They posted on the same topic

Trackback URL : http://bill.station51.net/index.php?trackback/910

This post's comments feed