• State Resolved
  • Locked Locked
  • Replies 6 replies
  • Subscribers 98 subscribers
  • Views 963 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.

Jelly bean 4AJ.2.2 fails to boot up on Blaze board through SD card

Prakash Divate
Intellectual 755 points

Hi,

I am trying to boot Blaze board using Android Jelly bean 4AJ.2.2 using SD card. I followed the instructions given in http://www.omappedia.com/wiki/4AJ.2.2_OMAP4_Jelly_Bean_Release_Notes and was successful in building the x-loader, u-boot,  kernel and the android file system.

I followed 2 methods to flash the sd card.

Method 1:

Followed the instructions given in the release notes (i.e to use fastboot)

Method 2:

Manually copied MLO u-boot and kernel to the boot partition and android file system to the rootfs partition.

After making the appropriate switch settings and booting the board using SD card, android comes up on Blaze display for a brief time but it freezes and i cannot access the board touchscreen.

I have attached the log for your reference.

Any help would be greatly appreciated.

Thanks

Prakash

  • 0
    TI__Prodigy 235 points

    Hi Prakash,

    Are you trying to run Android from SD card or to use SD card only to boot into flashboot mode. It seems from your log that Android is running from both the SD card and the emmc. There is another thread that discusses similar issue: http://e2e.ti.com/support/omap/f/849/t/215322.aspx.

    In order to run from Android from SD card you will have to change the following things:

    * create two partitions on your SD card and copy MLO, u-boot.bin and uImage to the first one. On the second one copy your root fs that you have build already. I think you have to copy the content of the root/ folder from mydroid/out/target/product/blaze/ and the system/ folder into root/system/.

    * boot from SD card and change the following params:

     setenv bootargs 'console=ttyO2,115200n8 mem=456M@0x80000000 mem=512M@0xA0000000 root=/dev/mmcblk1p2 init=/init vram=10M omapfb.vram=0:4M androidboot.console=ttyO2'
     mmcinit 0; fatload mmc 0 0x80000000 uImage;bootm 80000000'

    * you will have to change all init.rc scripts to use the device names pointing to the SD card.

    I was able to get it so far. It is possible that you will have to change other things as well. If you are not sure whether you use images from the EMMC or the SD card you can erase the relevand partitions with fastboot erase <partname>.

    Regards,

    Ivaylo

  • 0 in reply to Ivaylo Todorov-XID
    Intellectual 755 points

    Hi Ivaylo,

    Thanks and appreciate for your quick reply .

    I am trying to run Android from SD card. I am successful in running Android from eMMC. But not so lucky with the sd-card.

    I have followed all the instructions as suggested by you in order to run Android from SD card, however i have a few doubts here,

    1. U said "I think you have to copy the content of the root/ folder from mydroid/out/target/product/blaze/ and the system/ folder into root/system/."     Which system folder and root/system are you refering here?

    2.U said "you will have to change all init.rc scripts to use the device names pointing to the SD card" .    what changes should i make in the init.rc files? Could you point me to the exact locations in each file? Because i have already made the changes which i thought i should in the init.rc files.

    3.U said " It is possible that you will have to change other things as well"   What changes are you referring to ? Could you be specific?

    Thank You

    Prakash

  • 0 in reply to Prakash Divate
    TI__Prodigy 235 points

    Hi Prakash,

    the answer I gave you before is based on some tests I have done so far. It is by no means the right way of doing this. Those are some hacks I have tried myself and possibly will get you an unstable system.

    Now for your first question. When you format your emmc with the fastboot tool you get a bunch of partitions that are lately at boot time used to create the root file system. Because on you SD car you have only two partitions you will have to create the rootfs differently. I copied the content from mydroid/out/target/product/blaze/root/ folder to the second partition. After this step you will have several folders on your second partition one of which being system/. You have to fill this folder with the files from mydroid/out/target/product/blaze/system/ folder.

    I changed the following init files:

    In init.rc

    * comment out all lines starting with 'mount yaffs2'. They are used to mount partitions that you dont have on the SD card.

    * Mount rootfs as rw. That is definitely not a good thing (the right way) but it helped me a step further. To do that change the line 'mount rootfs rootfs / ro remount' with 'mount rootfs rootfs / rw remount'

    in init.omap4blazeboard.rc

    * delete this line 'mount_all /fstab.blaze'. That is also used to mount partition you dont have.

    By other changes I meant that there are probably some apps/services that might complain of something missing or not being done right.

    I managed to boot Android this way. I hope it will help you as well.

    Regards,

    Ivaylo

  • 0 in reply to Ivaylo Todorov-XID
    Intellectual 755 points

    Hi Ivaylo,

    I followed the steps you suggested but the result is same.

    Android comes up on the Blaze display but it freezes i.e i cannot access anything. In the debug console the kernel gets stuck at this point ' [   15.202484] omapdss DISPC error: OCP_ERR '  for a while and the log continues and the Android on the Blaze display disappears. I have attached the log file for your reference.

    Thank You

    Prakash

  • 0 in reply to Prakash Divate
    TI__Prodigy 235 points

    Hi Prakash,

    I think your problem is not related to booting from SD card but caused from this error: "EMIF: Access error from EMIF0 SYS port - 1". I spent some time researching it and my assumption is that your kernel reports more memory than you have on your board. On this thread there is a discussion related to this problem: http://e2e.ti.com/support/omap/f/849/t/178611.aspx.

    Regards,

    Ivaylo

  • 0 in reply to Ivaylo Todorov-XID
    Intellectual 755 points

    Hi Ivaylo,

    I got the board booting from SD card. Thanks a ton.

    Regards

    Prakash