Problems of Android in DevKit8000 (BeagleBoard clone)

[do interior]

My steps:
_Format a 4G sd card, creating two FAT partitions, a 500M and 3.5G, using software
for Windows Active @ Partition Manager
_Usando Another PC with Linux Fedora, formatted the partition as ext3 3.5G.
_The steps of the 32 page user's manual DevKit8000:
_copy _4.3 files with extension to the FAT partition, removing _4.3
in the order specified: MLO, u-boot and uImage.
_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

 

[jammulak]

Hi,
I am using DEVKIT8000 with Android Up and running. PM me with details of kernel and Android you are using I can share you the code.

Kiran Jammula

 

[do interior]

I use Android from cd Devkit8000

 

[do interior]

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

Use this to 2, will be that because the current is greater uImage should I change something in the setup of the u-boot?

setenv bootargs 'console=ttyS2,115200n8 console=tty0 root=/dev/mmcblk0p2 rootwait video=omapfb:vram:2M,vram:4M nohz=off'
setenv bootcmd 'mmcinit;fatload mmc 0 84000000 uImage;bootm 84000000'
saveenv

jammulak, please put here the links to the programs that you are using

 

[yhaddad]

Hi,

I have exactly the same problem, Could you please specify what you did exactly to fix the problem?

Which parameters you put in the u-boot ?

Thanks

 

[TomTang]

haha, i have had the same problem, when i debug the omap 3730 board, but now i forgot how to fix it.