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.
If I boot in 'normal' mode (pin1-pin2 set) I get the following output on UART0:
debug EMMC boot: print init OK debug EMMC boot: send RST_N . debug EMMC boot: start eMMC boot...... load fastboot1!
Switch to aarch64 mode. CPU0 executes at 0xf9801000! NOTICE: Booting Trusted Firmware NOTICE: BL1: v1.1(release):1b9a4b277314 NOTICE: BL1: Built : 13:43:57, Nov 3 2015 NOTICE: syspll frequency:1190494208Hz INFO: rdet ds fail INFO: rdet ds fail INFO: rdet ds fail ...
"INFO: rdet ds fail", it's related with DDR's initialization; below log info is when bl1 has initailized DDR successfully.
Switch to aarch64 mode. CPU0 executes at 0xf9801000! NOTICE: Booting Trusted Firmware NOTICE: BL1: v1.1(release):ca9f7ed NOTICE: BL1: Built : 11:05:40, Nov 4 2015 NOTICE: syspll frequency:1190494208Hz NOTICE: succeed to init lpddr3 rank0 dram phy INFO: lpddr3_freq_init, set ddrc 533mhz INFO: init ddr3 rank0 INFO: ddr3 rank1 init pass INFO: lpddr3_freq_init, set ddrc 800mhz INFO: init ddr3 rank0 INFO: ddr3 rank1 init pass INFO: Elpida DDR NOTICE: Enter fastboot mode...
I don't see the output related to the DDR initialization, instead I see the 'INFO: rdet ds fail'.
At least below things are deserved to get a quick try:
- Could you directly try below images: http://people.linaro.org/~leo.yan/hi6220_dev/output/l-loader_DDR_533MHz.bin
No change in case I load l-loader_DDR_533MHz.bin. Same behaviour on both hikey boards.
http://people.linaro.org/~leo.yan/hi6220_dev/output/fip_DDR_533MHz.bin
We can use this way to confirm DDR can work well;
If it's lucky with upper images, can continue to try 800MHz DRR: http://people.linaro.org/~leo.yan/hi6220_dev/output/l-loader_DDR_800MHz.bin http://people.linaro.org/~leo.yan/hi6220_dev/output/fip_DDR_800MHz.bin
If all of them can work well, then we can check if build enviornment is same b/t both sides. Before we found some toolchain will introduce DDR initialization failed.
Since the l-loader.bin is working as expected on the fresh hikey board and was working on the board in question till yesterday afternoon I'm quite sure I'm building something sane here.
Thanks,
-- Dietmar
[...]