BeagleBoar​d xm - Froyo Prebuild image problem

It is most likely the sd card issue.

Please check the table in the link below to see if the sd card you use is known not good.

http://processors.wiki.ti.com/index.php/TI-Android-FroYo-DevKit-V2.2_UserGuide#SD_Card_Recommendations

As I wrote at the beginning of my post I have tried 5 SD card (SanDisk 4GB Class 4)

I have downloaded Ubuntu image and was able to run it on beagleboard worked great

(Same SD card) so it doesn’t seems to be neither an SD card problem nor the socket.

Any Ideas?

Maybe it's Rev A Issue?

OMAP34xx/35xx-GP ES2.0, CPU-OPP2 L3-165MHz

OMAP3 Beagle board + LPDDR/NAND

I2C:   ready

DRAM:  384 MiB

NAND:  0 MiB

*** Warning - bad CRC or NAND, using default environment

In:    serial

Out:   serial

Err:   serial

Beagle xM Rev A

Die ID #577000019ff80000015eeaa101019023

Hit any key to stop autoboot:  0

mmc1 is available

reading boot.scr

415 bytes read

Running bootscript from mmc ...

## Executing script at 82000000

reading uImage

2618432 bytes read

***** Kernel: /dev/mmcblk0p1/uImage *****

***** RootFS: /dev/mmcblk0p2 *****

## Booting kernel from Legacy Image at 80200000 ...

   Image Name:   Linux-2.6.32

   Image Type:   ARM Linux Kernel Image (uncompressed)

   Data Size:    2618368 Bytes = 2.5 MiB

   Load Address: 80008000

   Entry Point:  80008000

   Verifying Checksum ... OK

   Loading Kernel Image ... OK

OK

Starting kernel ...

Uncompressing Linux................................................................................................................................................................... done, booting the kernel.

Linux version 2.6.32 (a0393957@swubn01) (gcc version 4.4.0 (GCC) ) #4 Wed Jan 19 15:12:38 IST 2011

CPU: ARMv7 Processor [413fc082] revision 2 (ARMv7), cr=10c53c7f

CPU: VIPT nonaliasing data cache, VIPT nonaliasing instruction cache

I saw the similar log when used some sd cards, for example, Transcend or Kingston, but not on SanDisk cards. (I do have ONE SanDisk card which has the problem.)

Android use much higher throughputs than Linux, so you might not see the issue in Ubuntu.

Is it possible to try Android in the SD cards on other boards (xM or EVM) to make sure you dont have a defect xM board?

I dont think it is revA problem. I have a revA, which has no issue w/ SanDisk cards.

Hi

Thanks for the reply Bin Liu.

I was able to run Ubuintu image (http://www.angstrom-distribution.org/demo/beagleboard/) And Everything worked. (So it's not SD card problem)

the error i see is related to the USB traffic while try to read/write from the SD card. 

If you say you have beagle board rev .A which run Froyo can you post the link of the pre-build image so i can download  and try it.

Can you send me a link so i can download you kernel (via http://uploading.com/) 

Better can you Attach you kernel configuration file to one of your messages

I can recompile the the kernel, anyone know which SD card driver i need to add to the kernel

Regards,

Micki

http://software-dl.ti.com/dsps/dsps_public_sw/sdo_tii/TI_Android_DevKit/02_02_00/index_FDS.html

The link above has the prebuilt package for xM, and here is the user guide: http://processors.wiki.ti.com/index.php/TI-Android-FroYo-DevKit-V2.2_UserGuide

Please download the prebuilt, untar it, and do 'sudo ./mkmmc-android.sh /dev/sdX' to flush everything (bootloader, kernel, filesystem, and media files) to the sd card.

The source code is in the download page too, or go to https://gitorious.org/rowboat 

Hi

Again thanks for the reply, As i mentioned in my first post i have downloaded TI-Android-FroYo-DevkitV2.2

And  i have used mkmmc-android.sh script to create the SD card. 

The error i posted are with the pre build image used. (Android don't start)

I have tried another SD card and got the same result.

Any other suggestion?

Regards

The devkit prebuilt is the image I tried on xM, I don't have anything else for you.

The only suggestion I have is to try other xM or EVM board, to check if you have a defect xM board.