On Thu, Nov 05, 2015 at 11:12:52AM +0000, Dietmar Eggemann wrote:
On 05/11/15 01:38, Leo Yan wrote:
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:
[...]
So for fresh hikey board, can burn fip.bin image successfully? And in normal mode, can boot successfully into UEFI?
Yes. I can run your burn_boot_images.sh on it and it finishes successfully (like it did with the other board until Tuesday afternoon).
I don't have the Debug Uart on the fresh hikey board but I noticed that User LED switched from 0 to 1 & 3 being on.
Looks like the fresh board can work well, could you firstly use this one and solder pins for Debug UART?
BTW, it's interesting for turning on LED 1 & 3, in ATF it will report panic with LED. In ATF, LED 1 & 3 (0xa) means a FIQ is triggered in ATF. This is not likely happend. Later kernel will enable it as CPU running indicators. But i don't know if UEFI will use it or not.
Just give more info at here, it's better you can check log after solder pins for Debug UART.
I was able to boot UEFI on the other board successfully until I ran into this DDR issue.
So far have no idea for this error; Looks like a hardware issue. Will loop in Guodong and Amit for further check in another mail.
Thanks, Leo Yan