arm discussion forum thread list

My problem is I can not make Android work provided, describe below exactly
all the steps and hope that you can help me in finding out where I"m wrong:

_Format  a 4G sd card, creating two FAT partitions, a 500M and 3.5G, using
software for Windows Active @ Partition Manager
_Another PC with Linux Fedora, formatted the partition as ext3 3.5G.
_The steps of the 32 page user"s manual DevKit800:
_copy  _4.3 files with extension to the FAT partition, removing _4.3
in the order specified: MLO, u-boot and uImage.
_In Ext3 partition, unzip the file RFS.tar.bz2.
By connecting the DevKit8000 with the sd card into the socket and the user
pressed botton, appeared in the terminal
the following messages:

Texas Instruments X-Loader 1:41
Starting OS Bootloader ...

U-Boot 1.3.3-svn333 (Sep 10 2009 - 16:49:01)

OMAP3530-GP rev 2, CPU-165MHz L3-OPP2
OMAP3 DevKit8000 Board LPDDR + / NAND
DRAM: 128 MB
NAND: 128 MiB
In: serial
Out: serial
Err: serial
Hit any key to stop autoboot: 0
reading uImage

1877828 bytes read
reading ramdisk.gz

** Unable to read "ramdisk.gz" from mmc 0:1 **
# # Booting kernel from Legacy Image at 80300000 ...
   Image Name: Linux-2.6.27-omap1-svn302-dirty2
   Image Type: ARM Linux Kernel Image (uncompressed)
   Data Size: 1877764 Bytes = 1.8 MB
   Load Address: 80008000
   Entry Point: 80008000
   Verifying checksum ... OK
   Loading Kernel Image ... OK
OK

Starting kernel ...

Uncompressing Linux ................................................ .............
.................................................. .......... done, booting the k
Ernel.

There appears nothing in the terminal or the LCD display or DVI output
The previous commands to the u-boot were these:

setenv console = bootargs ttyS2, 115200n8 root = / dev / ram initrd =
0x81600000, 40M video = omapfb: mode: 4.3inch_LCD
setenv bootcmd "mmcinit; fatload mmc 0 80300000 uImage; fatload mmc 0
81600000 ramdisk.gz; bootm 80300000"
saveenv

I changed to these:

setenv bootargs "console = ttyS2, 115200n8 root = / rw dev/mmcblk0p2
rootwait video = omapfb: mode: 4.3inch_LCD"
setenv bootcmd "mmcinit; fatload mmc 0 80300000 uImage; bootm
80300000"
saveenv

The terminal during the boot process is as follows:

Texas Instruments X-Loader 1:41
Starting OS Bootloader ...

U-Boot 1.3.3-svn333 (Sep 10 2009 - 16:49:01)

OMAP3530-GP rev 2, CPU-165MHz L3-OPP2
OMAP3 DevKit8000 Board LPDDR + / NAND
DRAM: 128 MB
NAND: 128 MiB
In: serial
Out: serial
Err: serial
Hit any key to stop autoboot: 0
reading uImage

1877828 bytes read
# # Booting kernel from Legacy Image at 80300000 ...
   Image Name: Linux-2.6.27-omap1-svn302-dirty2
   Image Type: ARM Linux Kernel Image (uncompressed)
   Data Size: 1877764 Bytes = 1.8 MB
   Load Address: 80008000
   Entry Point: 80008000
   Verifying checksum ... OK
   Loading Kernel Image ... OK
OK

Starting kernel ...

Uncompressing Linux ................................................ .............
.................................................. .......... done, booting the k
Ernel.

Again without display or serial terminal
Windows CE and Linux provided in the cd image \ 1G +1 G are functioning
normally, so I think my problem is the setup of the u-boot

You can help me?
Thanks in advance

* Posted by: Gabriel 2010-5-1 1:47:04 *

One detail that I consider important: <--- 〖Reply to this〗

One detail that I consider important:
The same procedure with the Angstrom functioned normally.
Does the Android files that came on the cd can be wrong?
Where can I find them to download?

* Posted by: Gabriel 2010-5-4 0:29:33 *

One detail that I consider important: <--- 〖Reply to this〗

Dear Gabriel.

You had to use the image( mlo, u-boot ) on the directory of
disk/linux/demo/android/.
Please change it.

* Posted by: James Li 2010-5-19 9:37:10 *

Problems of boot DevKit8000 <--- 〖Reply to this〗

Unfortunately must take up this subject, because if this boot problem is not
resolved, I will have to adopt other hardware, not Devkit8000.
The problem described in the first post also occurs with the latest version of
Angstrom, but only if I use uImage, Angstrom, if I use uImage Devkit800 the cd, it
boots normally, but unable to use Gnome, and other minor problems, explaining better:
_MLO, U-boot uImage and rootfs"s website Angstrom = no boot
_MLO, U-boot, and the site of Angstrom rootfs and uImage cd = dvkit8000 of the boot,
but with serious problems in Gnome, and others

* Posted by: Gabriel 2010-8-24 3:22:46 *

Re:Problems of boot DevKit8000 <--- 〖Reply to this〗

Dear Gabriel,

The Angstrom is demo for the devkit8000, we can provide you bottom image,
but we can not provide the Gnome, please refer to the
http://www.angstrom-distribution.org/
http://www.angstrom-distribution.org/demo/beagleboard/

Thanks.
Best regards.

* Posted by: James Li 2010-8-25 15:28:51 *

Someone could run on 2.6.32 Angstrom DevKit8000? <--- 〖Reply to this〗

If yes, please post here what are the secrets, especially the setup of the u-boot
and what are the files used.
Ex.:
setenv bootargs .....
setenv bootcmd ....

* Posted by: Gabriel 2010-8-26 0:11:10 *

Report any problems to the webmaster.