OMAP 4460GP Blaze Flashing/Booting Android Problem

Ducati binary is located in /system/vendor/firmware/ducati-m3.bin for 4AI1.7. You may need to copy the file using adb push and it will require to set device in rw mode, you can use the commands in next post to set rw mode, or root mode.

http://e2e.ti.com/support/omap/f/849/p/210782/746879.aspx#746879

Check that Ducati binary is for Blaze or Blaze tablet, I can't remember if there was an issue with 4AI.1.7 Ducati binary the one from eMMC package, but it  should be needed to load it for Blaze, any way check if it is being loaded of it is not then follow the procedure to replace it.

If you are using prebuild binaries for eMMC, then the process requires to rename the MLO that you build to a fixed name that depends on what device you are using, for Blaze Tablet I have next example,

user@user:/media/f7117f61/omap4_emmc_files_blaze$ sudo ./fastboot.sh
Fastboot: ./fastboot
Image location: ./
Fastboot - device detected: 0000000000000000
Missing ./Blaze_Tablet_GP_MLO

by reading attached document, next step is wrong,

cp -Rfp 4AI.1.7_Blaze_emmc_files.tar.bz2/* /media/rootfs

if you are booting from SDCard then you need to extract the rootfs and system image, I followed next steps for recent issue,

from

http://omapedia.org/wiki/Android_eMMC_Booting

look for " Modifying .IMG Files" section, and follow "RAMDISK" and "SYSTEM.IMG" instructions to extract the binaries, for example

(remove # from the command)

# cd omap4_emmc_files_blaze

# mkdir ramdisk

# cd ramdisk

# gunzip -c ../ramdisk.img | cpio -i

# cd ..

# mkdir mnt-point

you need to have simg2img in emmc-same directory, if it is not then it can be found in ./mydroid/out/host/linux-x86/bin/simg2img directory after compiling AFS, other possible issue is that in earlier releases it was needed to add +x flag using chmod for this binary, if it is not in the emmc folder then you can search for recent prebuild emmc files and check if it is there.

# ./simg2img system.img system.img.raw

# sudo mount -t ext4 -o loop system.img.raw mnt-point/

this will mount the files inside mnt-point, the only thing left is to copy the file to the SDCard,

# cd ramdisk

# sudo cp -rdfv * /media/rootfs/

# cd ../mnt-point/

# sudo cp -rdfv * /media/rootfs/

and wait for files to be copied

# sync

that should to the trick,

just do a clean up,

# cd ..

# sudo umount mnt-point

# rm -rdfv ramdisk

if you don't have anything to add you can unmount it, or this is a good chance to copy Ducati binary into /media/rootfs/system/vendor/firmware/ducati-m3.bin

# umount /media/rootfs

rootfs label\directory could be different depending how you formated the SDCard.

I am not sure a 8GB would work in Tablet try 4GB, but if it does please share the information.

Check to use FAT32 for Boot partition and set boot flag, minimum size is 32MB by FAT specification, this partition is used by default to store photos, videos and other files.

4544.OMAP 4460 GP Flash Android issue2.docx

I didn't really understand the process of checking whether i have the right ducati binary for the Blaze. It is located in the /vendor/firmware folder. I’m not sure if I have to do anything with it. Do i have to copy it to somewhere?  Can you please clarify?

On the other hand, the minicom output definitely changed after following the RAMDISK and SYSTEM.IMG instructions. I still get the "efi partition table not found" and theres some files that can't be found apparently. I have attached the new output.

*side note* the output suddenly stops and it doesn't seem to continue processing the whole thing. I think there is a problem.

I am still using a 8GB for now. It may be that this is the problem. I will try to work with a 1GB once I get a hold of one.

Also, can you clarify how to fastboot.

If you get the device to boot and load Android, and you are able to play a file check if next OMX.TI.DUCATI1.VIDEO.DECODER prints are present, it means that HW codecs are loaded.

I/OMXCodec(  126): [OMX.TI.DUCATI1.VIDEO.DECODER] video dimensions are 896 x 576
I/OMXCodec(  126): [OMX.TI.DUCATI1.VIDEO.DECODER] Crop rect is 800 x 464 @ (0, 0)
I/OMXCodec(  126): [OMX.TI.DUCATI1.VIDEO.DECODER] video dimensions are 896 x 576
I/OMXCodec(  126): [OMX.TI.DUCATI1.VIDEO.DECODER] Crop rect is 800 x 464 @ (0, 0)
I/OMXCodec(  126): [OMX.TI.DUCATI1.VIDEO.DECODER] video dimensions are 896 x 576
I/OMXCodec(  126): [OMX.TI.DUCATI1.VIDEO.DECODER] Crop rect is 800 x 450 @ (32, 24)

if you see next prints when playing the file it means SW codecs were loaded, the SW codecs are used in JellyBean to create thumbnails, you are using ICS then it should be both actions using HW codecs, just check the you see HW prints when you press play in gallery.

I/OMXCodec(  125): [OMX.google.h264.decoder] video dimensions are 320 x 240
I/OMXCodec(  125): [OMX.google.h264.decoder] Crop rect is 320 x 240 @ (0, 0)
I/OMXCodec(  125): [OMX.google.h264.decoder] video dimensions are 800 x 464
I/OMXCodec(  125): [OMX.google.h264.decoder] Crop rect is 800 x 450 @ (0, 0)
I/OMXCodec(  125): [OMX.google.h264.decoder] video dimensions are 800 x 464
I/OMXCodec(  125): [OMX.google.h264.decoder] Crop rect is 800 x 450 @ (0, 0)

for the EFI and SDCard boot, check procedure in next link, past Friday when I answered your post I didn't noted it in SDCard, using the procedure in this link I was able to boot ok from SDCard, during last week I tried to boot copying files to the SDCard and all tries were unsuccessful, I just shared the information on how to extract the files from eMMC packages but not focusing in running from SDCard.

http://e2e.ti.com/support/omap/f/849/p/269068/953200.aspx#953200

You are using 4AI1.7 then it should be possible to run by just copying the files to the SDCard, what path are you going to follow?

possibly from the other post the used command to select :SD is a different than the one used in 4AJ1.7.

3480.OMAP 4460 GP Flash Android issue3.docx

So this is what I have so far and I am still unsuccessful with getting Android 4AI1.7 to work & I am now using a 4GB.

Here are the steps I took to get here:

1. Downloaded the 4AI1.7 pre-built binaries except for ducati-binary

2. Configured my 4GB SD Card

• I set my boot partition to have a size of +2048M (I'm not sure if this is right)

3. Flashing to SD

• Followed instructions for RAMDISK AND SYSTEM.IMG
• my pre-built files are located in /Downloads/two
• did not copy the ducati-binary since there's one already
• copied the files  onto /media/rootfs
• copied MLO (renamed), u-boot.bin, uImage to /tmp/mmc1 (works)
• copied the rest to /media/rootfs
• --> check the picture for details

4.Connecting to Blaze

• I only have the power supply cord and the regular USB cable plugged in with the 4GB SD Card loaded
• the dip switches are all correct

5. Minicom

• stopped the boot countdown
• setenv bootargs console=ttyS3,115200n8 root=/dev/mmcblk1p2 rw rootdelay=1 init=/init
  setenv bootcmd 'mmcinit 0; fatload mmc 0 0x81c00000 uImage; bootm 0x81c00000'
  boot
• results pop up (in the attached document)

PROBLEMS:

1) I tried following the link you sent me but reading the posts, I keep having to go to a different post which really confuses me. Would you be able to show me the steps on here if possible. Please show me the commands you'd use as well.

2) Do I need to make changes in the u-boot?? if so, how do I go about doing that?

3) i tried to "cd omap4_emmc_files_blaze/" and do a "./fastboot oem set_flash_slot:SD but it just shows <waiting for device> and nothing ever happens

4) rm -rdfv ramdisk -> seems to be wrong

5) i still get "efi partition table not found"

6)you showed me this (figuring out if you have the right MLO)

user@user:/media/f7117f61/omap4_emmc_files_blaze$ sudo ./fastboot.sh
Fastboot: ./fastboot
Image location: ./
Fastboot - device detected: 0000000000000000
Missing ./Blaze_Tablet_GP_MLO

how do I do this?

Regards,

Seimon Arcinue

I am checking it tomorrow, maybe keeping separated procedures, that means not to follow the other link I mentioned, but it has some information has bootargs and others.

I tried 5 different times to load using formatting SDCard procedure described in the other post, but it is not working for 4AI1.7, and formating it in different ways too.

I tried too to boot the normal way but after trying 4 different bootargs and I cannot make it boot.

It could require some more work, do you need to boot 4AI.a.7 using SDCard? did you make some progress?

Sorry for the late reply.

I still have not made progress.

In regards to your question, I don't necessarily need to boot 4AI.1.7. It can be any release. Also, if there is another way to boot without using the SD card, then I am open to such alternatives. I will just need help on how to do so.

Regards,

Seimon Arcinue.

If you are planning to use 4AJ releases you will need to check next set of patches from 4AJ2.3 and for 4AJ2.5 and 4AJ2.5P1.

for 4AJ2.3 check

http://e2e.ti.com/support/omap/f/849/p/253953/888544.aspx#888544

for latest 4AJ2.5

http://e2e.ti.com/support/omap/f/849/p/269664/942046.aspx#942046

The process to flash eMMC is present in almost all the release pages in "Flashing_the_OMAP4_Hardware" section.

There are some consideration to make.

1. If the Ducati image is not working, you see a a print mentioning that "AudioPolicyService not published, waiting..." then you need to use the Ducati binary located in Prebuild binaries link for used release.

2. If you need to patch the kernel then you need to recreate the boot.img, there are 2 methods,

    a) is to use umulti.sh script in the eMMC instructions or compressed file, this script recreates the boot.img using zImage for new changes.

    b) uncompress the boot.img and recreate it using procedure in http://omapedia.org/wiki/Android_eMMC_Booting.

3. for #2 when recompiling Kernel you need to update GPX and WLAN drivers in /system/lib/modules (if not some PID errors could appear), WLAN procedure is in release notes, and not sure about Graphics drivers but they should be copied too from this directory, then it requires to build mydroid AFS too. If you are using 4AI1.7 eMMC files from prebuild link then compile kernel is not needed and using the eMMC package should be ok.

4.

The steps to follow,

1) Compile  AFS and boot files from release notes up to "Flashing_the_OMAP4_Hardware" or download prebuild eMMC package from Prebuild binaries link.

2) You need to create a FAT32 partition in SDCard and set it active(boot flag) and maybe name it "BOOT" for easy access, this partition I have used it at most 55MB, it is suppose that it can be any side if it is FAT32 and proper flags are set, but I have never check it. By now it is not needed to create other partition in SDCard since it will be loaded to eMMC memory.

3) download Xloaded (MLO) and U-boot (u-boot.bin) files from Prebuild binaries, and copy them to SDCard boot partition, you need to check that files are for Blaze or Blaze Tablet, upper section of prebuild binary page is for Blaze and lower is for Tablet.

4) use SYSBOOT configuration as indicated in release notes.

5) Insert the SDCard in the Blaze and wait to stop countdown, then type "fastboot", then in Computer side open a terminal and follow the steps to flash eMMC, it is basically sudo ./fastboot.sh from Terminal PC.

6) when process finishes it is needed to modify SYSBOOT switch configuration as indicated in release notes to boot from eMMC.

7) then it is ok to remove the SDCard and restart the device, it should boot ok.

I followed the steps from memory if I missed some step it should be in the release notes.

I will definitely try this when I have the time.

By any chance, do you know anyone who has successfully booted Android (any release) from a SD Card? If so, I would like to know the complete details of how they did it. I would like to continue trying to boot from a SD Card.

Best Regards,

Seimon

I found 2 posts, one of them is mentioned in the other thread running in parallel to this one about SDCard,

http://e2e.ti.com/support/omap/f/849/p/256063/898093.aspx

this is the one that is mentioned in http://e2e.ti.com/support/omap/f/849/p/269068/945872.aspx#945872

the other post,

http://e2e.ti.com/support/omap/f/849/t/215322.aspx?pi239031349=2

Actually reading the release notes ... Do i need to do this one? If so..

How do I go about doing this??

export BOARD_TYPE="blaze_tablet" #or "blaze" depending on your board type

cd ${MYDROID}/out/target/product/${BOARD_TYPE}
mkdir -p system/lib/modules
cp ${MYDROID}/hardware/ti/wlan/mac80211/compat_wl12xx/compat/compat.ko system/lib/modules/
cp ${MYDROID}/hardware/ti/wlan/mac80211/compat_wl12xx/net/wireless/cfg80211.ko system/lib/modules/
cp ${MYDROID}/hardware/ti/wlan/mac80211/compat_wl12xx/net/mac80211/mac80211.ko system/lib/modules/
cp ${MYDROID}/hardware/ti/wlan/mac80211/compat_wl12xx/drivers/net/wireless/wl12xx/wl12xx.ko system/lib/modules/
cp ${MYDROID}/hardware/ti/wlan/mac80211/compat_wl12xx/drivers/net/wireless/wl12xx/wl12xx_sdio.ko system/lib/modules/


cd ${YOUR_PATH}
mkdir myfs_${BOARD_TYPE}
cd myfs_${BOARD_TYPE}
cp -Rfp ${MYDROID}/out/target/product/${BOARD_TYPE}/root/* .
cp -Rfp ${MYDROID}/out/target/product/${BOARD_TYPE}/system/ .
cp -Rfp ${MYDROID}/out/target/product/${BOARD_TYPE}/data/ .

I actually don't get what to remove from the commands and what to insert.  Please show example.

If you are using Blaze use

export BOARD_TYPE="blaze"

and if it is Blaze Tablet use

export BOARD_TYPE="blaze_tablet"

I'm currently still having problems. I don't know what i'm doing wrong. I'm still doing 4AI.1.7 with a 4GB using a Blaze OMAP4460 GP and Im using the SD card to flash Android.

Do you know anyone that has an Android configuration that works on 4460 Blaze using any prebuilt binary that is willing to sh
I've been reading the release notes to see what to do but I am not entirely familiar with the codes. are their codes or a complete detail with me?

GOOD NEWS:

I was able to boot Android L27.5.2 on my OMAP. However i had to use a different card to load the U-boot and then once I stopped the autoboot, I replaced the card with the on that had  L27.5.2 files. After setting the setenv commands and the boot command, it successfully worked.

HOWEVER

What do I do so that it loads automatically from the SD Card? I want it so that once I reinsert the card, I can just turn on the OMAP and Android will load automatically.

Thank you!

For what I remember L27.x releases booted using instructions from release notes and using mentioned bootargs, even it was not supported, there is an extra change that is required in recent 4Ai and 4AJ releases that SDCard is not booting.

About your question, what is the release for the first U-boot you are using to boot? and I think the second one is from L27.5.2, right?

You could try to boot L27.13.inc1.1 or L27.G5 too.

I must mention that those releases are not being supported now.

UPDATE:

I replaced the old MLO and u-boot with newer ones. Now, the bootloader works fine now using the SD card with the L27.5.2. However, is there a way to change the contents in the u-boot bin so that I wont have to insert the bootargs so that the Blaze will boot Android automatically once you turn it on OR how do i compile my own u-boot.bin??

U-Boot 1.1.4-g83ec135f (Aug  8 2012 - 08:36:56)

Load address: 0x80e80000
DRAM:  1024 MB
Flash:  0 kB
Using default environment

In:    serial
Out:   serial
Err:   serial
Initializing SD(0) Slot.
ptbl slot: SD:(0).
efi partition table not found
efi partition table:
ptbl slot: EMMC:(1).
efi partition table not found
Net:   KS8851SNL
Hit any key to stop autoboot:  0
OMAP44XX SDP # setenv bootargs console=ttyO2,115200n8 root=/dev/mmcblk0p2 rw rootdelay=2 mem=463M int
OMAP44XX SDP # setenv bootcmd 'mmcinit 0; fatload mmc 0 0x80000000 uImage; bootm 0x80000000'
OMAP44XX SDP # boot

I think if you configure Kernel to use bootargs configuration you need to change the values in

./u-boot/include/configs/omap44xxtablet.h

or modify the kernel value in ./kernel/android-3.0/arch/arm/config/blaze_defconfig

the values to check to use bootargs from defconfig are mentioned in next post:

http://e2e.ti.com/support/omap/f/849/p/269068/946189.aspx#946189

I'm sorry but how do you go about doing this? Do you mind showing it to me step by step?

I think if you configure Kernel to use bootargs configuration you need to change the values in

./u-boot/include/configs/omap44xxtablet.h

You can modify the values used and recompile,

#ifdef NFS_BOOT_DEFAULTS
#define CONFIG_BOOTARGS "mem=64M console=ttyS0,115200n8 noinitrd \
    root=/dev/nfs rw nfsroot=128.247.77.158:/home/a0384864/wtbu/rootfs \
    ip=dhcp"
#else

#define CONFIG_BOOTARGS "console=ttyO2,115200n8 mem=456M@0x80000000 mem=512M@0xA0000000" \
            " init=/init vram=10M omapfb.vram=0:4M androidboot.console=ttyO2"

#define CONFIG_BOOTCOMMAND "booti mmc1"

#endif

or modify the kernel value in ./kernel/android-3.0/arch/arm/config/omap_4430sdp_defconfig ( one correction filename was different).

You can modify next like to add your bootargs

CONFIG_CMDLINE="root=/dev/ram0 rw mem=128M console=ttyS2,115200n8 initrd=0x81600000,20M ramdisk_size=20480"

the other 2 mentioned changes are to change the behavior of how the bootargs are copied and what values to use if Kernel ones, u-boot ones or a concatenation.

Read code in function init setup_arch inside next file for the use of CONFIG_CMDLINE_OVERWRITE and CONFIG_CMDLINE_EXTEND.

/27.13.1/kernel/android-2.6.35/arch/sh/kernel/setup.c

where do i find the file ./u-boot/include/configs/omap44xxtablet.h and ./kernel/android-3.0/arch/arm/config/omap_4430sdp_defconfig ?? I cant find these files. I would like to do this onto L27.5.2.

I haven't downloaded this exact release, but could you try to find blaze_defconfig and for u-boot depending on your configuration could be one of next files,

./L27IS1/u-boot/include/configs/omap44XXtablet.h

./L27IS1/u-boot/include/configs/omap4430sdp.h.

/L27IS1/u-boot/include/configs/omap4430panda.h

I must say that I don't have the exact release you mention then names could change.

I noticed that these files are obtained by downloading the release software from the release notes. Was I supposed to download these? Like I said, I had the pre-built binaries.

The one I found was /u-boot/include/configs/omap4430sdp.h

What should I do once I open the file? Should I entirely remove:

#define CONFIG_BOOTARGS "mem=64M console=ttyS0,115200n8 noinitrd \
    root=/dev/nfs rw nfsroot=128.247.77.158:/home/a0384864/wtbu/rootfs \
    ip=dhcp"
#else

AND replace

#define CONFIG_BOOTARGS "console=ttyO2,115200n8 mem=456M@0x80000000 mem=512M@0xA0000000" \
            " init=/init vram=10M omapfb.vram=0:4M androidboot.console=ttyO2"

#define CONFIG_BOOTCOMMAND "booti mmc1"

with...

#define CONFIG_BOOTARGS "console=ttyO2,115200n8 root=/dev/mmcblk0p2 rw rootdelay=2 mem=463M init=/init" \
      
#define CONFIG_BOOTCOMMAND "mmcinit 0; fatload mmc 0 0x80000000 uImage; bootm 0x80000000"

????

The changes I made were from:

setenv bootargs console=ttyO2,115200n8 root=/dev/mmcblk0p2 rw rootdelay=2 mem=463M init=/init
setenv bootcmd 'mmcinit 0; fatload mmc 0 0x80000000 uImage; bootm 0x80000000'
boot

IS THIS RIGHT?

---------------------------------

So assuming that I modified the values accurately, how do I go about recompiling the file?? Please show me.

Lastly, once we recompiled this file, where do I put this file to?

Thank you for being patient with me,

Seimon Arcinue

You need to replace the value of bootargs in the mentioned line, then you need to compile the Uboot as explained in the release notes, try to find the release you are using in next link

http://omapedia.org/wiki/Release_Notes

the instructions usually contains both Ubuntu instructions for environment setup  and from where to download the source code and compile it.

What release are you using? is it present in release notes link?

http://omapedia.org/wiki/L27.INC1.5.2_Froyo_ES2_Community_Release_Notes

This is the release that I am using. When I got the AFS, it did not come with the u-boot folder nor the x-loader folder as mentioned in the instructions. I had to take it out from the other release (4AI.1.7). 

I edited the omap4430sdp.h that i found under /u-boot/include/configs

#ifdef NFS_BOOT_DEFAULTS
/*#define CONFIG_BOOTARGS "mem=64M console=ttyS0,115200n8 noinitrd     \
    root=/dev/nfs rw nfsroot=128.247.77.158:/home/a0384864/wtbu/rootfs \
    ip=dhcp"
#else*/
/*#define CONFIG_BOOTARGS "console=ttyO2,115200n8 mem=456M@0x80000000 mem=512M@0xA0000000" \
" init=/init vram=10M omapfb.vram=0:4M androidboot.console=ttyO2" */        
#define CONFIG_BOOTARGS "console=ttyO2,115200n8 root=/dev/mmcblk0p2 rw rootdelay=2 mem=463M init=/init"
/*#define CONFIG_BOOTCOMMAND "booti mmc1"*/
#define CONFIG_BOOTCOMMAND "mmcinit 0; fatload mmc 0 0x80000000 uImage; bootm 0x80000000"

However, I get the result where it doesnt load Android automatically:

Texas Instruments Inc X-Loader 1.41.0-g28b5a696-dirty (Jul 29 2013 - 15:54:05)
OMAP4460: 1.5 GHz capable SOM
Starting OS Bootloader from MMC/SD1 ...

U-Boot 1.1.4-g83ec135f-dirty (Jul 31 2013 - 15:04:20)

Load address: 0x80e80000
DRAM:  1024 MB
Flash:  0 kB
Using default environment

In:    serial
Out:   serial
Err:   serial
Initializing SD(0) Slot.
ptbl slot: SD:(0).
efi partition table not found
efi partition table:
ptbl slot: EMMC:(1).
efi partition table not found
Net:   KS8851SNL
Hit any key to stop autoboot:  0
OMAP44XX SDP #

ALSO: I did #printenvbootdelay=3

baudrate=115200
ipaddr=128.247.77.90
serverip=128.247.77.158
netmask=255.255.254.0
bootfile="uImage"
stdin=serial
stdout=serial
stderr=serial
bootcmd=booti mmc0
ethact=KS8851SNL and this is what I got:

_______

Did i change the values right? Or no?

From the release notes, I must note that this release is very old and it possibly only supports OMAP4430.

From the release notes this release boots from SDCard then following the instructions in next link and clicking next button at the end of each page you should reach the page were the bootargs are mentioned.

http://omappedia.org/wiki/Android_SD_Configuration

http://omappedia.org/wiki/Flashing_Android#Flashing_to_SD

http://omappedia.org/wiki/Booting_Android

in the third link there are instructions to write the bootargs into memory and it is not needed to modify the u-boot.

Since you mentioned that the release is very old and might only support OMAP 4430, I dedided to use 4AI.1.7 Release Notes. By the way I am now using CentOS 6.4 instead of Ubuntu so bear with me.

I had to start all over and follow the instructions to build from step one. The only problem that I could find is when i got to "Preparing Android Binaries":

cd ${YOUR_PATH}
mkdir myfs_${BOARD_TYPE}
cd myfs_${BOARD_TYPE}
cp -Rfp ${MYDROID}/out/target/product/${BOARD_TYPE}/root/* .
cp -Rfp ${MYDROID}/out/target/product/${BOARD_TYPE}/system/ .
cp -Rfp ${MYDROID}/out/target/product/${BOARD_TYPE}/data/ .

The folder doesnt actually have a root folder and a data folder. I dont know why this is so.

ALSO

When i did [root@ohm mydroid]# make -j4 2>&1 |tee ${MYDROID}/logs/android_make.out, I got this output:

============================================
PLATFORM_VERSION_CODENAME=REL
PLATFORM_VERSION=4.0.4
TARGET_PRODUCT=full_blaze
TARGET_BUILD_VARIANT=userdebug
TARGET_BUILD_TYPE=release
TARGET_BUILD_APPS=
TARGET_ARCH=arm
TARGET_ARCH_VARIANT=armv7-a-neon
HOST_ARCH=x86
HOST_OS=linux
HOST_BUILD_TYPE=release
BUILD_ID=IMM76L
============================================
Checking build tools versions...
build/core/main.mk:324: implicitly installing apns-conf_sdk.xml
ln: creating symbolic link `out/target/product/blaze/system/lib/../vendor/lib/libbltsville_gc2d.so': No such file or directory
ln: creating symbolic link `out/target/product/blaze/system/lib/../vendor/lib/libbltsville_hw2d.so': No such file or directory
cp: target `out/target/product/blaze/system/vendor/lib' is not a directory
No private recovery resources for TARGET_DEVICE blaze
host Java: jsr305lib (out/host/common/obj/JAVA_LIBRARIES/jsr305lib_intermediates/classes)
Header: out/host/linux-x86/obj/include/libexpat/expat.h
Header: out/host/linux-x86/obj/include/libexpat/expat_external.h
Header: out/target/product/blaze/obj/include/libexpat/expat.h
Header: out/target/product/blaze/obj/include/libexpat/expat_external.h
Header: out/host/linux-x86/obj/include/libpng/png.h
Header: out/host/linux-x86/obj/include/libpng/pngconf.h
Header: out/host/linux-x86/obj/include/libpng/pngusr.h
Header: out/target/product/blaze/obj/include/libpng/png.h
Header: out/target/product/blaze/obj/include/libpng/pngconf.h
Header: out/target/product/blaze/obj/include/libpng/pngusr.h
Header: out/target/product/blaze/obj/include/libsonivox/eas.h
Header: out/target/product/blaze/obj/include/libsonivox/eas_types.h
Header: out/target/product/blaze/obj/include/libsonivox/eas_reverb.h
Header: out/target/product/blaze/obj/include/libsonivox/jet.h
Header: out/target/product/blaze/obj/include/libsonivox/ARM_synth_constants_gnu.inc
Header: out/target/product/blaze/obj/include/libwpa_client/wpa_ctrl.h
Notice file: external/guava/NOTICE -- out/host/linux-x86/obj/NOTICE_FILES/src//framework/guavalib.jar.txt
host Java: antlr (out/host/common/obj/JAVA_LIBRARIES/antlr_intermediates/classes)
Notice file: external/doclava/NOTICE -- out/host/linux-x86/obj/NOTICE_FILES/src//framework/doclava.jar.txt
target Java: core (out/target/common/obj/JAVA_LIBRARIES/core_intermediates/classes)
host Java: dx (out/host/common/obj/JAVA_LIBRARIES/dx_intermediates/classes)
Notice file: dalvik/dx/NOTICE -- out/host/linux-x86/obj/NOTICE_FILES/src//bin/dx.txt
Notice file: frameworks/base/tools/aapt/NOTICE -- out/host/linux-x86/obj/NOTICE_FILES/src//bin/aapt.txt
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
Notice file: frameworks/base/libs/utils/NOTICE -- out/host/linux-x86/obj/NOTICE_FILES/src//lib/libutils.a.txt
Notice file: system/core/liblog/NOTICE -- out/host/linux-x86/obj/NOTICE_FILES/src//lib/liblog.a.txt
Notice file: system/core/libcutils/NOTICE -- out/host/linux-x86/obj/NOTICE_FILES/src//lib/libcutils.a.txt
Notice file: external/expat/NOTICE -- out/host/linux-x86/obj/NOTICE_FILES/src//lib/libexpat.a.txt
Notice file: external/libpng/NOTICE -- out/host/linux-x86/obj/NOTICE_FILES/src//lib/libpng.a.txt
Yacc: aidl <= frameworks/base/tools/aidl/aidl_language_y.y
bison -d  -o out/host/linux-x86/obj/EXECUTABLES/aidl_intermediates/aidl_language_y.cpp frameworks/base/tools/aidl/aidl_language_y.y
Lex: aidl <= frameworks/base/tools/aidl/aidl_language_l.l
frameworks/base/tools/aidl/aidl_language_l.l:54: warning, rule cannot be matched
Notice file: frameworks/base/tools/aidl/NOTICE -- out/host/linux-x86/obj/NOTICE_FILES/src//bin/aidl.txt
touch out/host/linux-x86/obj/EXECUTABLES/aidl_intermediates/aidl_language_y.hpp
echo '#ifndef 'aidl_language_y_h > out/host/linux-x86/obj/EXECUTABLES/aidl_intermediates/aidl_language_y.h
echo '#define 'aidl_language_y_h >> out/host/linux-x86/obj/EXECUTABLES/aidl_intermediates/aidl_language_y.h
cat out/host/linux-x86/obj/EXECUTABLES/aidl_intermediates/aidl_language_y.hpp >> out/host/linux-x86/obj/EXECUTABLES/aidl_intermediates/aidl_language_y.h
echo '#endif' >> out/host/linux-x86/obj/EXECUTABLES/aidl_intermediates/aidl_language_y.h
rm -f out/host/linux-x86/obj/EXECUTABLES/aidl_intermediates/aidl_language_y.hpp
Notice file: external/tinyxml/NOTICE -- out/host/linux-x86/obj/NOTICE_FILES/src//lib/libtinyxml.a.txt
prebuilt/linux-x86/toolchain/arm-linux-androideabi-4.4.x/bin/arm-linux-androideabi-gcc -mthumb-interwork -Ibionic/libc/private -DCRT_LEGACY_WORKAROUND -Ibionic/libc/private -o out/target/product/blaze/obj/lib/crtbegin_so.o -c bionic/libc/arch-arm/bionic/crtbegin_so.S
build/tools/merge-event-log-tags.py:29: DeprecationWarning: the md5 module is deprecated; use hashlib instead
  import md5
prebuilt/linux-x86/toolchain/arm-linux-androideabi-4.4.x/bin/arm-linux-androideabi-gcc -mthumb-interwork -Ibionic/libc/private -DCRT_LEGACY_WORKAROUND -Ibionic/libc/private -o out/target/product/blaze/obj/lib/crtend_so.o -c bionic/libc/arch-arm/bionic/crtend_so.S
prebuilt/linux-x86/toolchain/arm-linux-androideabi-4.4.x/bin/../lib/gcc/arm-linux-androideabi/4.4.3/../../../../arm-linux-androideabi/bin/as: error while loading shared libraries: libz.so.1: cannot open shared object file: No such file or directory
prebuilt/linux-x86/toolchain/arm-linux-androideabi-4.4.x/bin/../lib/gcc/arm-linux-androideabi/4.4.3/../../../../arm-linux-androideabi/bin/as: error while loading shared libraries: libz.so.1: cannot open shared object file: No such file or directory
make: *** [out/target/product/blaze/obj/lib/crtbegin_so.o] Error 1
make: *** Waiting for unfinished jobs....
make: *** [out/target/product/blaze/obj/lib/crtend_so.o] Error 1
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.

How do I fix this?? This output might be related to why I don't have the missing folders.

Verify that MYDROID code is downloaded at 100%, try doing

cd $MYDROID

repo sync

then you should see a 100% downloaded message if it is ok, if not it will continue downloading the source code. The root folder should appear when all Android FS in MYDROID is completed.

I actually was able to get around this problem. The problem was that I did not have all the required Tools and Dependency packages. I had to download the 32-bit versions as well.

However, my problem is now this:

1 error
target Java: DisabledTestApp (out/target/common/obj/APPS/DisabledTestApp_intermediates/classes)
target Java: frameworks-core-util-lib (out/target/common/obj/JAVA_LIBRARIES/frameworks-core-util-lib_intermediates/classes)
make: *** [out/target/common/obj/APPS/CtsVerifier_intermediates/classes-full-debug.jar] Error 41
make: *** Waiting for unfinished jobs....

-------

Apparently the problem is the version of java that I have..

java version "1.6.0_24"
OpenJDK Runtime Environment (IcedTea6 1.11.11.90) (rhel-1.62.1.11.11.90.el6_4-x86_64)
OpenJDK 64-Bit Server VM (build 20.0-b12, mixed mode)
------

How do I fix this?

I fixed this problem myself. I needed to locate where the downloaded java went and set my PATH accordingly.

I was also able to build everything from scratch. YAY! So now I'm back to my original problem:

How do I boot Android onto OMAP4460 Blaze using the files from the release notes using my 4GB SD memory card?

Also, I would like to boot Android USB automatically whenever I turn on my Blaze, how do I do that?

I stopped after

sed -i 's/${FASTBOOT-".\/..\/..\/..\/..\/out\/host\/linux-x86\/bin\/fastboot"}/.\/fastboot/g' fastboot.sh
sed -i 's/${PRODUCT_OUT-".\/"}/.\//g' fastboot.sh 

I wasnt sure what to do after..

Could you try this link?

http://e2e.ti.com/support/embedded/android/f/509/p/202090/718395.aspx#718395

I was able to get pass the Java problem.

Now I have all the files and everything. I just need to know what to do after that. How do I boot Android onto OMAP4460 Blaze using the files from the release notes using my 4GB SD memory card?

I want to solely use the SDCard to flash Android on OMAP4460.

I stopped after [http://omapedia.org/wiki/4AI.1.7_OMAP4_Icecream_Sandwich_Release_Notes#Building_Kernel]

sed -i 's/${FASTBOOT-".\/..\/..\/..\/..\/out\/host\/linux-x86\/bin\/fastboot"}/.\/fastboot/g' fastboot.sh
sed -i 's/${PRODUCT_OUT-".\/"}/.\//g' fastboot.sh 

I read that I have to change the scripts in some files. I'm using 4AI.1.7 with 4GB Card. Do I have to fastboot if im trying to use a SD Card.

*So far I have the MLO and u-boot.bin in my boot partition. Im not sure where to get the uImage

Thanks you for your patience!

About Android USB do you meant something like the information in next link?

http://omappedia.org/wiki/Omapboot#USBBOOT

We are trying to boot from SDCard using fastboot but we are facing some issues, read next post for more information,

http://e2e.ti.com/support/omap/f/849/p/269068/981426.aspx#981426

I mean, the procedure of using fastboot for SDCard is described in this thread, we followed it but there are some issues with it and 4AJ releases.

You can find references to this procedure along all the thread, and one of the main posts is

http://e2e.ti.com/support/omap/f/849/p/269068/953200.aspx#953200

I haven't used USBBOOT utility, there are some other references in omapedia.org about it but they are for OMAP4 PandaBoard, just search for USBBOOT.

Sorry, the USB was a typo.

Anyway, so I have all the compiled files from the release notes of 4AI.1.7. I currently have the MLO and unmodified u-boot.bin in the boot partition. I have a couple questions

1) in the --- board/omap4430sdp/mmc.c --- I changed the mmc_slot from 1 to 0 twice. AND the bootargs in ---omap4430sdp.h--- || QUESTION: would i have to rebuild u-boot again using "make 2>&1 |tee ${MYDROID}/logs/u-boot_make.out"??

2) Which folder do I copy into rootfs partition?

3) Just to clarify, is the SYSBOOT referring to the dip switches

4) Do I also make the change in the init.omap4blazeboard.rc from mmc1 to mmc0?

5) Is the third partition required? I only have the boot and the rootfs

6) where do I find the uImage? Should I just get the pre-built uImage?

7) what does it mean to comment out all lines with yaffs (init.rc) ? Do i just add # before each line?

That's all I have for now. Let me know once you are able to fully boot from SDcard.

Thank you for your efforts!

THANK YOU!

I was finally able to get it working! I definitely would like to try it with the recent release considering that I used a Froyo release.

Thanks to you!, your question about why it is not booting directly into the FS was one of the key question while debugging the issue, it helped to solve the last part when modifying u-boot to boot without interrupting the boot sequence countdown.

BTW, is there really no way to boot from a 8GB SD Card?

I don't have a 8GB SDCard right now, but let me see if I can find one during next days to check it.

Have you tried it to boot using 8GB SDCard? try to make first partition like 52MB or less with boot flags enabled.

I have tried to boot using a 8GB SD Card. I set it to 52MB and nothing happened.

Anyway, I'm going to try and build the 4AJ2.2 Release.

There wasn't a lot of changes that I made when I got the Gingerbread version to work on the the blaze with the SD Card. It was really just the U-boot. But what changes do I need to make for this version? I saw the post with Michael Sogo (http://e2e.ti.com/support/omap/f/849/t/269068.aspx?pi239031349=4) but I wanted to be sure which changes are really necessary.

Also, I'm having a problem with uImage. How do I go about doing this:

Note: If you are building for a GP device it is recommended not to build the SMC kernel driver.
To create kernel uImage you need to add "mkimage" directory path to your "PATH" environment variable:

I was getting this error:

"mkimage" command not found - U-Boot images will not be built
make[1]: *** [arch/arm/boot/uImage] Error 1
make: *** [uImage] Error 2

In addition:

This release supports WiLink8 by default. If you have Tablet/Blaze with WiLink7 you can enable Wi-Fi by running a small script which is part of the build.

# su
# wilink7.sh

--- when do I do this part??

Thank you!

Following next 2 post should be ok to make it work copying the files into the SDCard.

http://e2e.ti.com/support/omap/f/849/p/269068/990490.aspx#990490

http://e2e.ti.com/support/omap/f/849/p/269068/992123.aspx#992123

The mkimage is created by the u-boot, then following the release notes compiling from top to bottom.

That is why it is added next export in order to find it, but you have to define all the paths and variables in the release notes. If the mkImage is not present then there should be an error in the u-boot compilation. Like a note, check the compilation commands for Blaze and Tablet, some of them have a # you need to copy the command line and modify it to what device you are using.

for example:

make ARCH=arm omap44XXtablet_config #(for Blaze_Tablet)

becomes

make ARCH=arm omap44XXtablet_config

If the # is added then the configuration doesn't have effect. The same applies to other components in the release notes that differentiates between Blaze and Blaze Tablet compilation.

export PATH=${YOUR_PATH}/u-boot/tools:$PATH

And I didn't found anything about your question about WiLink8, the script is located in

./4AJ22/mydroid/hardware/ti/wlan/mac80211/config/Switch_To_WiLink7.sh

then copied and renamed inside the Android FS in

./4AJ22/mydroid/out/target/product/blaze_tablet/system/bin/wilink7.sh

by the file content it should be run from the device terminal one time it is flashed and running, it contains

MODULES_PATH=/system/lib/modules

I'm still having a problem loading 4AJ.2.2 using the 4GB SD card.

I'm still getting garbage characters as output when I open up minicom. For now, I have to switch to a different card with the working bootloader files and I would switch to the SD card that has 4AJ.2.2 files.

From the output of minicom, these were the last output.

[    9.232360] Freeing init memory: 288K
[    9.255889] init: skipping insecure file '/default.prop'
[    9.263031] init: skipping insecure file '/init.rc'
[   14.013336] init: Timed out waiting for /dev/.coldboot_done
[   14.022705] init: skipping insecure file '/system/build.prop'
[   62.005065] HDCP: failed to load keys
[   62.009643] omap-rproc omap-rproc.1: rproc_loader_cont: failed to load ducati-m3.bin
[   62.018737] omap-rproc omap-rproc.0: rproc_loader_cont: failed to load tesla-dsp.bin

How do I fix these problems.

These are the patches, check tablet and blaze in the file name for correct version, and shared too the binary files I am using. In this way using the binaries it should be matter to check the SDCard format and that SYSBOOT configuration were correct.

u-boot

http://review.omapzoom.org/33670

Kernel

8750.0001-Kernel-Modification-to-boot-from-SDCard-using-4AJ2.2.patch.txt

device/ti/blaze_tablet

http://review.omapzoom.org/33671

device/ti/blaze

http://review.omapzoom.org/33672

8308.boot_files.tar

Added later,

The patch are the changes for init.rc.

http://review.omapzoom.org/33748

I will check this again on Friday.

Just an update:
[I tried to rebuild the 4AJ.2.2 thinking that the modified files were creating the garbage but I still got the garbage on minicom without modifying anything. I followed the build instructions as best as I could. So I don't really know where the problem is coming from.]

Hopefully I can give you good news on Friday when I check out these instructions

Seimon,

I forgot one patch, while doing the fastboot method in the other post I found it out.

The patch are the changes for init.rc.

http://review.omapzoom.org/33748

Excuse me for this missed patch if it caused some inconvenience.

You can find the instructions to boot from SDCard using fastboot method in next post,

http://e2e.ti.com/support/omap/f/849/p/269068/1012981.aspx#1012981

I just encountered problems with the whole insecure files init.rc files and Ive already tried changing permissions and there's just more problems that come up and now I see init: untracked pid ### exited.

Would you mind doing a step by step process after changing all of the values in the rc files etc.??

I don't really know how to do the fastboot process and i'm really not sure how it's done. By any chance, could you do a video demonstration? That would really help me out a lot.