Re: [android-building] Re: Android fastboot eom format never returns

2,909 views
Skip to first unread message

Max Chu

unread,
Jul 4, 2012, 1:47:42 PM7/4/12
to android-...@googlegroups.com
I'm very frustrated.  One week passed and no progress. 

There is something wrong with my system, obviously, because no one seems to experience this problem.  However, I'm new to build and flashing and don't know how to investigate further.  I hope someone would kindly makes some suggestions.  May be I have to follow the linaro build process instead, but using fastboot to flash should work, right?

On Thu, Jun 28, 2012 at 10:04 AM, max chu <chaom...@gmail.com> wrote:
More info:

I think the fastboot is not working as it should. But it showed as in fastboot mode.  How can I indentify the problem at this point?  Could it be some configuration issues (i.e. USB connection)? 

================================
0. in /device/ti/panda:
-rw-rw-r-- 1 androidgroup androidgroup  165012 Jun 26 01:17 bootloader.bin
-rwxrwxr-x 1 androidgroup androidgroup   50164 Jun 26 01:17 usbboot
-rw-rw-r-- 1 androidgroup androidgroup   23824 Jun 26 01:17 xloader.bin

1. plug in USB cable then power-on the pandaboard.  Use lsusb to list USB devices:
...
Bus 001 Device 084: ID 0451:d010 Texas Instruments, Inc.  <- detect the pandaboard

2. load fastboot over USB:
androidgroup@gimli:~/android$ sudo device/ti/panda/usbboot device/ti/panda/bootloader.bin
[sudo] password for androidgroup:
using built-in 2ndstage.bin
reading ASIC ID
CHIP: 4440
IDEN: 0000000000000000000000000000000000000000
MPKH: 0000000000000000000000000000000000000000000000000000000000000000
CRC0: 229e85ba
CRC1: 00000000
sending 2ndstage to target... f0030002
waiting for 2ndstage response...
sending image to target...

3. load completed, check USB device again
androidgroup@gimli:~/android$ lsusb
...
Bus 001 Device 100: ID 0451:d022 Texas Instruments, Inc. <- this indicates the board is in fastboot mode "d022"

4. use fastboot to list devices:
androidgroup@gimli:~/android$ fastboot devices
1732000200000001    fastboot

5. try fastboot command:
androidgroup@gimli:~/android$ fastboot getvar version-bootloader
(no response, unplug USB cable to force command exit)

getvar:version-bootloader FAILED (status read failed (No such device))
finished. total time: 154.489s
============================

Any suggestion is appreciated!

/max


On Wednesday, June 27, 2012 11:24:34 AM UTC-7, max chu wrote:
Yes, SD card is in pandaboard.

A little more info; I unplug the USB cable after long wait (several hours later) and the fastboot response following

FAILED (status read failed (No such device)) 
finished. total time: 249390.445s

When I checked the SD card, it has 7 partitions:

Partition    File System    Size
/dev/sdc1    unknown       128KB
/dev/sdc2    unknown       256KB
/dev/sdc3    unknown       8MB
/dev/sdc4    unknown       8MB
/dev/sdc5    unknown       512MB
/dev/sdc6    unknown       256B
/dev/sdc7    unknown       6.6GB



On Wednesday, June 27, 2012 9:57:24 AM UTC-7, Anthony Russello wrote:
Hi,

Do you have an sdcard inserted when you run fastboot oem format?

Thanks,
Anthony

On Tuesday, 26 June 2012 18:45:39 UTC-4, max chu wrote:
Hi All,

Can someone help?

I have built ICS 4.0.4 on Ubuntu 12.04 for Pandaboard ES (full_panda-userdebug).  My problem is when I tried flashing to SD card, the format command never return.  I think the usbboot is fine.

The last two commands:
==========================
androidgroup@gimli:~/ics_source$ sudo ./out/host/linux-x86/bin/fastboot devices
1732000200000001    fastboot

androidgroup@gimli:~/ics_source$ sudo ./out/host/linux-x86/bin/fastboot oem format
...   <- never return
=================

Thx.

--
You received this message because you are subscribed to the "Android Building" mailing list.
To post to this group, send email to android-...@googlegroups.com
To unsubscribe from this group, send email to
android-buildi...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-building?hl=en

Jean-Baptiste Queru

unread,
Jul 4, 2012, 2:59:05 PM7/4/12
to android-...@googlegroups.com
Bummer. I understand the frustration, but I have really no idea where
to look. I've never had that problem, but I also haven't tested with a
wide variety of SD cards (and that's the only variation I can think
of).

JBQ
--
Jean-Baptiste M. "JBQ" Queru
Technical Lead, Android Open Source Project, Google.

Questions sent directly to me that have no reason for being private
will likely get ignored or forwarded to a public forum with no further
warning.

Jean-Baptiste Queru

unread,
Jul 9, 2012, 12:05:21 PM7/9/12
to android-...@googlegroups.com
FWIW, I do all my testing on 10.04. I've never used 12.04 myself.

"fastboot devices" is essentially the simplest fastboot command you can run.

JBQ

On Sun, Jul 8, 2012 at 12:38 AM, max chu <chaom...@gmail.com> wrote:
> Thanks for the response, at least I know someone is reading the post.
>
> I have a couple questions regarding how the fastboot works, may be you can
> help?
>
> 1. I used Ubuntu 12.04 and Panda ES, is this configuration been verified? I
> think it is from some people's posting but just checking.
>
> 2. After I load bootloader.bin using usbboot, is there any fastboot command
> that I can use to verify the connection between host and the board? I
> tried:
> =================
>
> androidgroup@gimli:~/android$ fastboot getvar version-bootloader
> (no response, unplug USB cable to force command exit)
>
> getvar:version-bootloader FAILED (status read failed (No such device))
> finished. total time: 154.489s
> =================
> I don't have SD card in the slot yet, so I don't think it's the SD card
> problem.
>
> 3. In other attempts, I did run fastboot oem format with the SD card. Even
> though the command hang, but when I force the fastboot exit I can see there
> are partitions created in the SD card (but no labels or file system for the
> partition).
>
> So from the above cases, I think the commands are issued and possibly being
> executed but the fastboot on the board failed to write back to the host. Is
> there permission issue? I tried running with "sudo" or running as root but
> no difference.
>
> Thx!!
Reply all
Reply to author
Forward
0 new messages