• State
  • Locked Locked
  • Replies 4 replies
  • Subscribers 98 subscribers
  • Views 414 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Unable to boot TI-Android-GingerBread-2.3.4-DevKit-2.1 in a Beagleboard XM Rev C (USING THE DEMO IMAGES)

carlos pardo
Prodigy 130 points

After a bunch of tries I am stuck here:

EXT3-fs (mmcblk0p2): mounted filesystem with ordered data mode                  
VFS: Mounted root (ext3 filesystem) on device 179:2.                            
Freeing init memory: 204K                                                       
init (1): /proc/1/oom_adj is deprecated, please use /proc/1/oom_score_adj inste.
Texas Instruments X-Loader 1.51 (Jul 11 2011 - 21:11:32)                        
Unsupported Chip!                                                               
Beagle xM Rev C                                                                 
Starting X-loader on MMC                                                        
Reading boot sector                                                             
213256 Bytes Read from MMC                                                      
Starting OS Bootloader from MMC...                                              
Starting OS Bootloader...                                                       
U-Boot 2010.06 (Jul 08 2011 - 04:37:45)                                         
OMAP34xx/35xx-GP ES2.1, CPU-OPP2 L3-165MHz                                      
OMAP3 Beagle board + LPDDR/NAND                                                 
I2C:   ready                                                                    
DRAM:  384 MiB                                                                  
NAND:  HW ECC [Kernel/FS layout] selected                                       
0 MiB                                                                           
*** Warning - bad CRC or NAND, using default environment                        
In:    serial
Out:   serial
Err:   serial                                                                   
Beagle xM Rev A/C                                                               
Die ID #778800029ff800000163810c1300601f                                        
Hit any key to stop autoboot:  0                                                
OMAP3 beagleboard.org #

 

I always does the same. the last boot script I tried was:

if fatload mmc 0 82000000 uImage
then
echo ***** Kernel: /dev/mmcblk0p1/uImage *****
fi
echo ***** RootFS: /dev/mmcblk0p2 *****

setenv bootargs 'console=ttyO2,115200n8 androidboot.console=ttyO2 mem=256M root=/dev/mmcblk0p2 rw rootfstype=ext3 rootdelay=1 init=/init ip=off omapdss.def_disp=lcd buddy=bbtoys-ulcd omap_vout.vid1_static_vrfb_alloc=y vram=8M omapfb.vram=0:8M'

Can someone at TI knows this? Where can I get a SD card that works ?

Thank you.

  • 0
    TI__Expert 4390 points

    Hi Carlos,

    1. This question in answered in one of the post in e2e. http://e2e.ti.com/support/embedded/f/509/p/110013/479751.aspx

    2. However with the new devkit release 2.1, this sould work fine. Are you using all prebuilt including u-boot and x-loader from the latest release ?

    3. Could you give complete log details for the further analysis.

    BR,

    satish

     

  • 0 in reply to Satish Patel
    Prodigy 130 points

    Satish,

    I am using the pre-built images. Can I get a SD image such that I can do DD  (dd if=bootable.img of=/dev/sdb bs=2048)

     

    root@opersys-embedded-android:/media/sf_U_DRIVE/OPERSYS/TI_Android_GingerBread_2_3_4_DevKit_2_1/Prebuilt_Images/beagleboard-xm# ls
    Boot_Images  Media_Clips       mkmmc-android.sh.ori  README.txt
    Filesystem   mkmmc-android.sh  pwd                   START_HERE
    root@opersys-embedded-android:/media/sf_U_DRIVE/OPERSYS/TI_Android_GingerBread_2_3_4_DevKit_2_1/Prebuilt_Images/beagleboard-xm# cd Boot_Images/
    root@opersys-embedded-android:/media/sf_U_DRIVE/OPERSYS/TI_Android_GingerBread_2_3_4_DevKit_2_1/Prebuilt_Images/beagleboard-xm/Boot_Images# ls -al
    total 2916
    drwxrwx--- 1 root vboxsf       0 2011-07-11 11:41 .
    drwxrwx--- 1 root vboxsf    4096 2011-10-12 17:04 ..
    -rwxrwx--- 1 root vboxsf     460 2011-07-07 19:10 boot.scr
    -rwxrwx--- 1 root vboxsf   21728 2011-07-11 11:41 MLO
    -rwxrwx--- 1 root vboxsf  213256 2011-07-07 19:09 u-boot.bin
    -rwxrwx--- 1 root vboxsf 2745172 2011-07-07 18:58 uImage

     

     

  • 0 in reply to carlos pardo
    Prodigy 130 points

    mkmmc-android.sh has a bug.   In my system I have to add delays so that it works.

    mkfs.vfat -F 32 -n boot "$1"1 &> /dev/null
    sleep 1
    mkfs.ext3 -L rootfs "$1"2 &> /dev/null
    sleep 1
    mkfs.vfat -F 32 -n data "$1"3 &> /dev/null
    sleep 1
    I took a look at the patches and they are already  there. I will try again later. I really would like to have a FULL IMAGE THAT I CAN FLASH and WORKS. I can take it from there. 

  • 0 in reply to carlos pardo
    TI__Expert 4390 points

    Hi Carlos,

    1. Prebuilt images has been validated by flashing a sdcard with ubuntu OS.

    2. It may be the case where with some configuration it may give the problem. To understand further could you give your system configuration in details.

    3. Prebuilt is also working with VM ware ubuntu images.

    BR,

    satish