Thanks Kevin. I dont have anything else plugged to USB on my laptop apart from HiKey usb cable. Moreover, i have tried this with 3 different Linux machine and still have the same issue. 

On 9 September 2015 at 00:06, Kevin Hilman <khilman@kernel.org> wrote:
I saw something similar when I had something plugged into the USB host
connector as well as the OTG connector. Be sure have nothing plugged
into the USB host connector when trying to (re)flash or use fastboot.

Kevin


On Mon, Sep 7, 2015 at 11:34 PM, Guodong Xu <guodong.xu@linaro.org> wrote:
> Amit,
>
> So it's steadily repeatable on your HiKey. ...
> That's a phenomena I never heard before. I have 3 boards, and other LT
> members have at least 4. Also Huawei's team, they have several.
>
> That behavior at this stage in board side is controlled by HiKey Hi6220's
> ROM code. I am checking with Huawei for what kind of issue this could be.
>
> Or CircuitCo has an explanation for that?
>
> -Guodong
>
> On 8 September 2015 at 14:17, Amit Khare <amit.khare@linaro.org> wrote:
>>
>> Hi George, Here's the full log and it seems usbserial support is getting
>> registered.
>>
>> [33949.970976] usb 1-1.1: new full-speed USB device number 6 using
>> ehci-pci
>> [33950.064568] usb 1-1.1: New USB device found, idVendor=12d1,
>> idProduct=3609
>> [33950.064583] usb 1-1.1: New USB device strings: Mfr=1, Product=4,
>> SerialNumber=0
>> [33950.064592] usb 1-1.1: Product:
>> \xffffffe3\xffffff84\xffffffb0\xffffff84\xffffffb0\xffffffe3\xffffff8c\xffffffb2\xffffff8c\xffffffb2\xffffffe3\xffffff94\xffffffb4\xffffff94\xffffffb4\xffffffe3\xffffff9c\xffffffb6\xffffff9c\xffffffb6\xffffffe3\xffffffa4\xffffffb8\xffffffa4\xffffffb8
>> [33950.064599] usb 1-1.1: Manufacturer:
>> \xffffffe4\xffffff95\xffffff87\xffffff95\xffffff87\xffffffe4\xffffff95\xffffff8e\xffffff95\xffffff8e\xffffffe4\xffffffa5\xffffff8e\xffffffa5\xffffff8e
>> [33950.129406] usbcore: registered new interface driver usbserial
>> [33950.129429] usbcore: registered new interface driver usbserial_generic
>> [33950.129447] usbserial: USB Serial support registered for generic
>> [33950.144501] usbcore: registered new interface driver option
>> [33950.144551] usbserial: USB Serial support registered for GSM modem
>> (1-port)
>> [33950.144690] option 1-1.1:1.0: GSM modem (1-port) converter detected
>> [33950.144787] usb 1-1.1: GSM modem (1-port) converter now attached to
>> ttyUSB0
>> [33950.541308] usb 1-1.1: USB disconnect, device number 6
>> [33950.541773] option1 ttyUSB0: usb_wwan_indat_callback: resubmit read urb
>> failed. (-19)
>> [33950.541783] option1 ttyUSB0: usb_wwan_indat_callback: resubmit read urb
>> failed. (-19)
>> [33950.541789] option1 ttyUSB0: usb_wwan_indat_callback: resubmit read urb
>> failed. (-19)
>> [33950.541795] option1 ttyUSB0: usb_wwan_indat_callback: resubmit read urb
>> failed. (-19)
>> [33950.542051] option1 ttyUSB0: GSM modem (1-port) converter now
>> disconnected from ttyUSB0
>> [33950.542091] option 1-1.1:1.0: device disconnected
>> amit@linaro:~$
>>
>>
>> On 7 September 2015 at 13:54, George Grey <george.grey@linaro.org> wrote:
>>>
>>> One other possibility - I don’t see the usbserial support being
>>> registered in Amit’s log.
>>> Could it be that you have got the relevant usbserial detection support
>>> enabled on your Linux box ….
>>> George
>>>
>>>
>>> > On Sep 7, 2015, at 9:20 AM, Daniel Thompson
>>> > <daniel.thompson@linaro.org> wrote:
>>> >
>>> > On 06/09/15 04:05, Guodong Xu wrote:
>>> >> Amit,
>>> >>
>>> >> The 90 seconds delay is key here. In "install bootloader" mode, you
>>> >> must
>>> >> make sure to start the USB download process within 90 seconds of
>>> >> powering up hikey.
>>> >>
>>> >> The log you attached makes sense to me. Everything are reasonable.
>>> >> Here
>>> >> for your reference, is on mine board and PC. In this case, I should
>>> >> run
>>> >> 'hisi-idt.py' before [14495.204951].
>>> >
>>> > On Amit's board the logs do look very similar but the disconnect
>>> > happens after half a second (rather than 90 seconds). I think that is what
>>> > leads to a guess conclusion there is a hardware fault.
>>> >
>>> >
>>> > Daniel.
>>> > _______________________________________________
>>> > Dev mailing list
>>> > Dev@lists.96boards.org
>>> > https://lists.96boards.org/mailman/listinfo/dev
>>>
>>
>>
>>
>> --
>> Regards,
>> Amit Khare
>>
>> _______________________________________________
>> Dev mailing list
>> Dev@lists.96boards.org
>> https://lists.96boards.org/mailman/listinfo/dev
>>
>
>
> _______________________________________________
> Dev mailing list
> Dev@lists.96boards.org
> https://lists.96boards.org/mailman/listinfo/dev
>



--
Regards,
Amit Khare