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.

Boot Mistral OMAP3EVM from SD with Rowboat Code



Hello,

I'm trying to load Android (rowboat project) on to the OMAP3EVM from SD card, with no luck. I am able to boot the Mistral Android SD image, but not having any luck with the prebuilt kernel and FS from the rowboat repo. Here are some things I tried:

Boot Mistral Android SD card image. Created SD card using DD. - This works

Leaving mistral MLO & u-boot.bin on SD card, replacing kernel and filesystems with Rowboat prebuilt. <- get "Bad magic number"

Replacing MLO & u-boot.bin with prebuilt from the PSP 02.01.03.11 Release from Mistral, no kernel or FS. Just tryin to get to the u-boot prompt via Serial <-get error "x-loader hangs"

What am I doing wrong?

TIA,

Brian

  • Hello Brian,

    Please use the MLO/u-boot for the Mistral EVM available from the Rowboat website. You are correct to use the kernel and filesystem from Rowboat. I have tried x-loader 1.41/u-boot 2008.10 in NAND with kernel on FAT SD partition and file system on ext3 partition with success.

    Can you please post your query along with your bootargs and which prebuilt version of rowboat you are using to the rowboat mailing list (rowboat@googlegroups.com)? There might be better ideas there.

    Thanks,

    Katie

  • Not that this is much help, but I tried the same sequence starting with an old Mistral Android SD card I had lying around and trying to copy in the kernel and FS and than the MLO and U-Boot from the Rowboat site, and I got the same results.

    The bad magic number seems to stem from customizations Mistral put into their U-Boot image that is running on the SD card, in essence it does not load the uImage file from the SD card so when it tries to run the kernel image all U-Boot sees is empty RAM space. I tried using a normal SD card loading command in U-Boot but it failed as well, and without saveenv working on their U-Boot image it is not very practical to use in my opinion.

    The X-Loader hangs message in the past has meant there was some boot switch setting incorrect (amongst other things), but now I am not sure why it is happening, since when I switch back to the MLO and U-Boot from Mistral it still does not work anymore for me, I fear that the physical placement in the SD card may be impacting the way X-Loader functions, but I am not certain.

    At the moment the only way I have booted the Rowboat successfully was from NFS as described here, in that case I just had some arbitrary old X-Loader and U-Boot in NAND, I think from SDK 1.02 though it may have been from the newer SDK.

  • Bernie/Katie,

    I edited the boot settings to potentially boot from both SD and NFS using the flash X-Loader/U-boot. These settings seem to get me a bit further. I get the following before it hangs:

    OMAP3EVM # run boot_sd

    2299212 bytes read
    ## Booting image at 80000000 ...
       Image Name:   Linux-2.6.29-rc3-omap1
       Image Type:   ARM Linux Kernel Image (uncompressed)
       Data Size:    2299148 Bytes =  2.2 MB
       Load Address: 80008000
       Entry Point:  80008000
       Verifying Checksum ... OK
    OK

    Starting kernel ...

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

     Here is the specific setup:

    -Host is Ubuntu 8.04
    -Mistral EVM Main board REV C
    -OMAP 35xx REV B
    -SW4 set to boot from flash/UART in that order (10010100)
    -TI X-Loader 1.41
    -U-Boot 1.1.4 (07/01/08)
    -Rowboat version: omap3evm-donut-2009-11-03 (prebuilt)

    SD & TFTP/NFS Boot  Commands
    baudrate=115200
    stdin=serial
    stdout=serial
    stderr=serial
    ethaddr=00:50:C2:7E:86:21
    bootdelay=10
    myip=172.16.0.219:172.16.0.1:255.255.255.0::::off
    gatewayip=172.16.0.1
    bootcmd=dhcp; bootm
    bootfile=uImage
    netmask=255.255.255.0
    ipaddr=172.16.0.219
    serverip=172.16.0.144
    bootargs_sd=mem=128M console=ttyS0,115200n8 root=/dev/mmcblk0p2 rw rootdelay=2
    boot_nfs=setenv bootargs $(bootargs_nfs);dhcp;bootm 0x80000000
    load_sd_kernel=mmcinit;fatload mmc 0 0x80000000 uImage
    boot_sd=setenv bootargs $(bootargs_sd);run load_sd_kernel;bootm 0x80000000

    bootargs_nfs=console=ttyS0,115200n8 androidboot.console=ttyS0 noinitrd rw ip=dhcp root=/dev/nfs nfsroot=172.16.0.144:/android,nolock,proto=tcp init=/init rootwait mem=128
    bootargs=console=ttyS0,115200n8 androidboot.console=ttyS0 noinitrd rw ip=dhcp root=/dev/nfs nfsroot=172.16.0.144:/android,nolock,proto=tcp init=/init rootwait mem=128

    The default boot method is NFS. Halting the boot and typing run boot_sd boots from the SD card. Both methods yield the same result: Hanging at "booting the kernel"

    Any thoughts?
    Thanks!

    Brian

  • Katie,

    I updated the last post with both an SD and NFS setup, and sent my new question over to the rowboat ML. Thanks!

    Thanks!

    Brian