OMAP4 blaze tablet2 is not booting

Hi Senthil,

Please ensure that you are following the exact S2 Switch settings as mentioned under "First time flashing on eMMC " at http://omapedia.org/wiki/4AI.1.4_OMAP4_Icecream_Sandwich_Release_Notes before powering the Blaze Tablet 2. You can connect using cutecom or minicom.

Use the /dev/ttyUSB2 port to connect which works for me using Cutecom.

You only need to have GP MLO and u-boot.bin in the boot partition of SD Card for first time booting and then enter fastboot to flash the pre-built binaries as per the steps outlined in Release Notes at http://omapedia.org/wiki/4AI.1.4_OMAP4_Icecream_Sandwich_Release_Notes.

Please let me know if you need any further help.

Thanks & Best Regards,

Venkat

Hi Venkat,

  Thank you for quick reply.I have doubt about power up procdure too.Please correct me if i am wrong.

1. Connect mini USB to HOST pc  - observed USB LED is ON

2. Connect micro USB to HOST pc. - observed No difference

3. Connect 5V DC power to charge connector. - observed No difference

4.  Power switch on right side with USB/OFF/AC options.I changed it to USB. - observed Status   LED (TOP of USB LED) is ON there is one more status LED (Next to CPU module) is OFF.(Sorry i dont remember the LED names).

5. Open minicom ttyUSB1-4 at 115200 8N1 configuration no log messages.

I have question about S3 POwer switch at center of the board.DO we need to switch it ON?However i tried that too.What about RESET switch near HDMI connector.

Regards

Senthilkumar R

Hi Venkat,

   Thanks.It is working with ttyUSB2 now.Previously i was using prebuilt MLO from Anroid for Tablet.Now i am using another prebuilt MLO file from Android on Blaze column(4A.1.4) releases.I am able to boot from eMMC now.But u-boot is breaking with fastboot entered all the time.Is there any method to bypass the script in uboot.Or whether we have any u-boot with default hit key option.If i want to rebuilt myself,please let me know.

Regards

Senthilkumar R

Hi Senthil,

I also faced similar issue while using the pre-built binaries of 4AI.1.3 release. Even if you you use the your own built u-boot.bin, you will face the same issue. Basically the problem is with the u-boot.bin binary. Can you reflash the u-boot.bin from the earlier releases of ICS such as L27.IS.2-P1 instead of 4AI.1.4 u-boot binary.

This option works for me with Tablet 2 flashed with 4AI.1.3 pre-built binaries except the u-boot.bin from L27.IS.2-P1 release. Otherwise, you can use the u-boot.bin from your earlier pre-built binary which was working for you.

Thanks and Best Regards,

Venkat

Hi Venkat,

  It is working fine.I am able to boot from eMMC with prebuilt binaries.Now i have to configure NFS/TFTP boot for Blaze tablet 2.Is there any link which provides information about the setup,Can you please share it?.If possible share the boorargs to be saved while booting.Thanks

Regards

Senthilkumar R

Normally we do not use NFS/TFTP boot for Android releases. However it can be done. There is some information available in the link provided below. It might help you.

http://www.omappedia.org/wiki/Android_Getting_Started#Installing_Android

Also I suggest you to post another question as original question is already answered and this is different question.

Hello,

        When I boot up from the sd card,the ttyUSB(0-3) puts out nothing.And the three buttons at the buttom of the screen are flashing all the time.

         I use the tablet firstly. Please help me!

 Thank you !

Zhang,

Please include what HW are you using? What version of SW you are trying to boot? Did you try eMMC boot? Add any debug pointer you can provide.

Regards,

Chintan 

Hi Chintan,

 1. My hardware is  TEVM4460 blaze tablet.

 2.I have tried with the  pre-built binaries version 4AI1.4, 4AI1.7 on the android on blaze and on the tablet column ,but all failed.

3. I recevied  the the tablet a few days ago. I  am the first time to boot it up from the sd card.

Thanks!

,

Zhang,

If you are flashing it for first time you need to boot up with SD card first. Please create the SD card using instructions given in the below link:

http://omappedia.org/wiki/Android_Build_SD_Configuration

Download the prebult binaries from the below link:

http://www.omappedia.com/wiki/Android:_Working_with_pre-built_binaries

- Copy the MLO, u-bbot in the boot partion

- Put the SDCard in the EVM and select /dev/ttyUSB2

Please let us know if this gets you any message on terminal.

Regards,

Chintan

Hi Chintan,

   All you mention above ,I have tried  step by step as

http://omappedia.org/wiki/Android_Pre-built_Binaries_Guide

There is nothing from the /dev/ttyUSB2.,except the three buttons at the buttom of  the screen are flashing all the time.

Please help! Thank you!

I think the MLO you are using is not correct. Please make sure you are using the right MLO. It depends on the silicon version. Please let us know the silicon revision.

Regards,

Chintan

Chintan,

  Thank you for your reply.

  And how can I get the  silicon revision? What does it look like?

Best regards.

Hi

 I think the u-boot.bin what I am used is not the right one,because when I rename the u-boot.bin like myuboot.bin,the three buttons will be not flashing.

But I try some different version u-boot.bin, the three buttons are still flashing and the terminal is nothing out..

Zhang,

I think you need change the DIP switch setting. Change the switch 1 and 3 to OFF. You may need to open the back cover. When you open the board silicon revision will be written on the silicon eg "ES1.0". You can select the MLO accordingly.

Regards,

Chintan

Chintan，

              I am sure the MLO revision and  switch setting I use are correct. I have tried with different MLO and /or u-boot.bin version,but the  phenomenon is the same that the the three buttons are flashing greenly.

              The  silicon revision of my tablet is 4460ES1.1(A) 1.5Ghz GP.

   Best regards.

Zhang,

The fact that the 3 LEDs are blinking is a good thing.  That means that your system has entered into Fastboot mode.  That means that your MLO and u-boot.bin are running successfully.  The system will automatically enter into Fastboot mode at the u-boot if it cannot find the boot.img on your eMMC, since the default bootargs are set to boot from eMMC.  When you tried using the wrong u-boot.bin (or u-boot.bin file named incorrectly), the u-boot didn't run and you didn't enter Fastboot, which is why the LEDs weren't flashing.

The issue is why you don't see any output in your serial terminal, as you should see output prints as the x-loader and u-boot are running and as you enter into Fastboot mode.  Which serial terminal program are you using?  There are many options, but personally I use cutecom, and it works out-of-the-box.  Ensure that the mini-USB cable is connected from the Blaze Tablet to your PC for serial console access.  On the Blaze Tablet, this is the port labeled "USB debug."  The other USB port (micro-USB) is labeled "USB OTG" and is used for Fastboot flashing and ADB, but not serial console access.  In your terminal program, make sure to select /dev/ttyUSB2 as the device, 115200 as the baudrate, 8 data bits, 1 stop bit, and parity none.

Since you have entered Fastboot, you can also connect the micro-USB cable to the PC and run the "fastboot.sh" script to flash the software to the eMMC.  You can download a package of eMMC files here http://www.omappedia.com/wiki/Android:_Working_with_pre-built_binaries, which already includes fastboot.sh.  (Make sure to download a package for Blaze Tablet, not Blaze.)  Then upon the next bootup, you should see Android running on your Blaze Tablet.  However, ultimately you will need console access for debug purposes.

Regards,
Gina 

Hi Gina ,

             Thanks for your help.

             The former problem resulted  from my  serial terminal program  Now, the tablet can setup with Android system  normallly.

              But , I have another problem that the command 'adb devices' can't find the tablet device. I can't use the adb for debugging.

Best regards.

Do you have the micro USB cable connected?  It is needed for ADB.  (The mini USB cable is needed for serial console.)  Make sure that you are running the ADB commands as sudo.

Regards,
Gina