I am trying to boot up an OMAP4 blaze board into Android and I am encountering some issues. I am following the video tutorials available at http://omappedia.org/wiki/Blaze_Video_Tutorials. In summary this is the procedure I am following:
1- Set Switch2: OFF ON OFF OFF ON OFF OFF OFF
2- Set Switch3: OFF ON ON ON
3- Configure SD card using the script available at http://git.openembedded.org/openembedded/tree/contrib/angstrom/omap3-mkcard.sh (I do change the Angstrom partition to rootfs)
4- Copy Android (L27.4 RC0 ) pre-built files into SD card (taken from http://omappedia.org/wiki/Android:_Working_with_pre-built_binaries)
5- insert USB cable, insert SD card, and finally the power cord
This is the output that I get on my host PC:
OMAP44XX SDP # Texas Instruments X-Loader 1.41 (Jul 23 2010 - 15:35:03)mmc read: Invalid sizeStarting OS Bootloader from MMC/SD1 ...U-Boot 1.1.4-L24.6 (Jul 23 2010 - 15:33:44)Load address: 0x80e80000DRAM: 512 MBFlash: 0 kBIn: serialOut: serialErr: serialNet: KS8851SNLOMAP44XX SDP #
Could you please point me to what I am not doing correctly or what else I need to do in order to boot the board into Android?
about the switch configuration i usually look in next page
one point that could affect is if your Blaze is 4460 or 4430, if you are running 4430 then actual work is ok with L27.4, if it is 4460 try to move to latest 4AI release
if you move to 4AI remember to format the sdcard's partitions and copy respective release files to it, when using eMMC fastboot tool is different from L27.4 to 4AI.
you are in the point that xloader and uboot are running, that is a good point, what you need next is to set bootargs and bootcmd, then kernel and AFS will be started.
you can find them in next locations, i think it is Eclair and first link shows the instruction to follow,
other releases are available, one for GiungerBread is
and the latest for Icecream Sandwich is
yo can find more information about Android and Blaze in next links
A startup guides are in next 2 links
Android Pre-built Binaries Startup Guide
Building Android Startup Guide
another route to follow from the actual point is to use eMMC it requires to boot using SD Card done
for questions about OMAP4 Forum you can go to
Thanks a lot. I did follow the instructions for bootargs and bootcmd. And then I've got the following error message (sorry, I could not copy the test so I attached it as an image):
actually I have the whole log of kernel boot here:
Load address: 0x80e80000DRAM: 512 MBFlash: 0 kBIn: serialOut: serialErr: serialNet: KS8851SNLOMAP44XX SDP # setenv bootargs console=ttyO2,115200n8 root=/dev/mmcblk0p2 rw rootdelay=2 mem 463M init=/init OMAP44XX SDP # setenv bootcmd 'mmcinit 0; fatload mmc 0 0x80000000 uImage; bootm 0x80000000'OMAP44XX SDP # bootmmc read: Invalid size2474244 bytes read## Booting image at 80000000 ... Image Name: Linux-184.108.40.206 Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 2474180 Bytes = 2.4 MB Load Address: 80008000 Entry Point: 80008000 Verifying Checksum ... OKOKStarting kernel ... Uncompressing Linux.........................
I checked the bootargs against other configurations in omapedia.org and they looks ok, it could be related to the way you SD card is formated.
This release may not be supporting many features that are supported in latests 4AI releases, and it's difficult to provide full technical support for such old releases.
You could consider moving to the latest 4AI release to get more features enabled and use Icecream Sandwich release: http://omapedia.org/wiki/4AI.1.3_OMAP4_Icecream_Sandwich_Release_Notes
You can find formatting instructions in 4AI link (previously post shared link) and it mentions about a script to use instead of manual formatting omap3-mkcard.sh and full instructions on how to compile and use this release, check that some command lines includes #(..) to indicate configuration to use for each device.
No experience with this platform but I do think that the bootargs have a syntax error. There should be a '=' between "mem" and "463M". It is incorrect on the webpage
The other pages have the properly formatted mem bootargs, eg.
mem=458M@0x80000000 mem=512M@0xA0000000mem=456M@0x80000000 mem=512M@0xA0000000
Odd inconsistency in memory size and noncontiguous.
Right, I didn't saw it, thanks;
final bootargs to try must looks like:
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'
Thanks a lot for your help. I managed to build icecream sandwitch and put on the board. I will tey your suggestion ASAP too. Cheers!
All content and materials on this site are provided "as is". TI and its respective suppliers and providers of content make no representations about the suitability of these materials for any purpose and disclaim all warranties and conditions with regard to these materials, including but not limited to all implied warranties and conditions of merchantability, fitness for a particular purpose, title and non-infringement of any third party intellectual property right. TI and its respective suppliers and providers of content make no representations about the suitability of these materials for any purpose and disclaim all warranties and conditions with respect to these materials. No license, either express or implied, by estoppel or otherwise, is granted by TI. Use of the information on this site may require a license from a third party, or a license from TI.
TI is a global semiconductor design and manufacturing company. Innovate with 100,000+ analog ICs andembedded processors, along with software, tools and the industry’s largest sales/support staff.