Hi,
I was program a boot.img in hieky board. Now it cannot do fastboot. So I want to program I-loader again.
But ubuntu cannot recongize hikey’s usb, when I closed auto power up and boot select jumper.
picture:
And do ls /dev/ttyUSB* or lsusb, cannot have hikey’s usb.
Could you help me? Thanks!
HiKey Board (LeMaker)
Board based on HiSilicon Kirin 6220 processor
More Info: http://www.96boards.org/product/hikey/
Buy now: http://linaro.co/hikey-lenovator-buy
It’s very difficult to do hikey recovery using a windows hosted linux machine. Go to Window’s Device Settings and look for the COM port for the usb connection. If there’s an error (an ! or ? or x sign) next to the icon then your linux machine (terminal) won’t see the usb connection even if it shows up in the VM’s menu. If you can replace (update) the driver for the COM port with one that works (i.e. without ! or ? or x sign next to the icon) then it might just work. Try one from http://www.ftdichip.com/Drivers/VCP.htm. If you get still a ! or ? or x sign, then it’s best to just get a native linux pc and save yourself a lot of time and trouble. If it’s really too difficult to get a linux pc, then your other options are to boot up the pc using a linux live usb/cd, or configure dual boot and boot into linux.
WARNING: Sometimes upgrading the usb serial driver CAN break other COM ports that you use on Windows for regular console/terminal, so please make sure you BACK UP your working driver files and proceed very carefully!
Assuming you have a driver that works, you also need to note that the hikey usb connection will only be visible for 90 seconds, so if you don’t attach it to your linux guest and run hisi-idt.py within 90 seconds, then the recovery process will fail also.
Sometimes even after 90 seconds, the linux guest will still list the usb connection in the menu, even though it’s not really there anymore. You should note this as well.
hi vchong,
I was download the driver for windows 7 from http://www.ftdichip.com/Drivers/VCP.htm. The device also cannot recoginze by windows.
Yes driver name is right. As mentioned above, if you cannot get the driver to work, then your options are 1 use linux pc 2 use linux live cd/usb 3 configure windows-linux dual boot for your pc. Or you can keep on trying different windows pc until you find one that works. Sorry but I don’t know of any other way around it. Again, it really requires a lot of time and effort to try to get it to work in windows and really really not worth it!
