On Wed, Nov 04, 2015 at 07:12:36PM +0000, Dietmar Eggemann wrote:
On 04/11/15 03:47, Leo Yan wrote:
On Tue, Nov 03, 2015 at 08:33:33PM +0000, Dietmar Eggemann wrote:
Hi Leo,
On 30/10/15 03:12, Leo Yan wrote:
Hi Dietmar,
On Thu, Oct 29, 2015 at 04:30:00PM +0000, Dietmar Eggemann wrote:
On 29/10/15 14:36, Dietmar Eggemann wrote:
On 21/10/15 02:56, Leo Yan wrote:
[...]
After burn image 'l-loader.bin', you can check PC side if dump below info:
leoy@leoy-linaro:~$ sudo dmesg -c [52045.180850] usb 1-1.1.3: USB disconnect, device number 46 [52045.181032] option1 ttyUSB1: GSM modem (1-port) converter now disconnected from ttyUSB1 [52045.181048] option 1-1.1.3:1.0: device disconnected [52045.393983] usb 1-1.1.3: new high-speed USB device number 47 using ehci-pci [52045.499062] usb 1-1.1.3: New USB device found, idVendor=18d1, idProduct=d00d [52045.499067] usb 1-1.1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [52045.499069] usb 1-1.1.3: Product: Android 2.0 [52045.499071] usb 1-1.1.3: Manufacturer: Androi [52045.499072] usb 1-1.1.3: SerialNumber: 0123456789ABCDEF
Yeah, there is no dmesg output for the board in question but I can see this output using a fresh hikey board so I guess the l-loader.bin I built is OK.
leoy@leoy-linaro:~/Work/hisi/boot/l-loader$ sudo fastboot devices 0123456789ABCDEF fastboot
So that means it has prepared successfully for "fastboot", otherwise we can get to know 'l-loader.bin' has not successfully initialized protocol for "fastboot".
Yes, 'fastboot devices' is not working for the board in question where as it works fine for the fresh hikey board.
So for fresh hikey board, can burn fip.bin image successfully? And in normal mode, can boot successfully into UEFI?
[...]
Thanks, Leo Yan