vexpress-tc2 target boards need a change in firmware to boot on to A7

[Naresh Kamboju]

vexpress-tc2 target boards need a change in firmware to boot on to A7.

FILE: SITE1/HBI0249A/board.txt

SCC: 0x700 0x0032F003 ;CFGRW48 - [25:24]Boot CPU [28]Boot Cluster (default CA7_0)

Replace it with: 0x1032F003 (which boots on to A7 cluster now)

something like this:
-SCC: 0x700 0x0032F003 ;CFGRW48 - [25:24]Boot CPU [28]Boot Cluster (default CA7_0)
+SCC: 0x700 0x1032F003 ;CFGRW48 - [25:24]Boot CPU [28]Boot Cluster (default CA7_0)

[Ryan Harkin (ryanharkin)]

UEFI will need to be upgraded when this change happens, because the UEFI currently installed does not boot on A7, only on A15.

The UEFI binaries from the release (13.04 or CI [1]) will boot on A7, but not on A15.

I am hoping that ARM will soon release the patches needed so that UEFI can boot on A7 or A15.

[1] https://snapshots.linaro.org/components/kernel/uefi/15

[Naresh Kamboju (naresh-kamboju)]

Following lava jobs effected
http://validation.linaro.org/lava-server/scheduler/job/53302
http://validation.linaro.org/lava-server/scheduler/job/53378

Switcher initialized cpu 0 only instead of both cpu 0 and cpu 1 because of old UEFI configuration.
As Ryan comment, UEFI needs to be upgraded as per 13.04 release.

[Ryan Harkin (ryanharkin)]

OK, so if jobs are failing because we need the latest UEFI, then I might have to go ahead and do the upgrade, the UEFI feature I was hoping for has not landed yet and might not be available by 2013.05 either...

[Naresh Kamboju (naresh-kamboju)]

LAVA job effected

http://validation.linaro.org/lava-server/scheduler/job/53635/log_file

[Naresh Kamboju (naresh-kamboju)]

I can see you have update the firmware, but lava failed to boot image reporting issues that kernel image is not found.
I request you to revisit this issue, the jobs failed today

1.
[a] Boot Manager
[b] Shell
Start: 3
MciReadBlockData(): TIMEOUT! Response:0xA404012 Status:0x48
ERROR: Did not find Linux kernel.
ASSERT /mnt/ci_build/workspace/uefi/uefi/MdeModulePkg/Core/Dxe/Mem/Pool.c(424): CR has Bad Signature

LAVA jobs Falied:
- http://validation.linaro.org/lava-server/scheduler/job/53963
- http://validation.linaro.org/lava-server/scheduler/job/53803

2.
[a] Boot Manager
[b] Shell
Start: ASSERT /mnt/ci_build/workspace/uefi/uefi/MdeModulePkg/Core/Dxe/Mem/Page.c(697): End > Start
<LAVA_DISPATCHER>2013-05-09 03:45:58 PM WARNING: Sending newline in case of corruption.
....
<LAVA_DISPATCHER>2013-05-09 03:57:59 PM ERROR: boot_linaro_android_image failed: booting into android test image failed
Traceback (most recent call last):
  File "/srv/lava/.cache<email address hidden>/lava_dispatcher/actions/boot_control.py", line 55, in run
    adb_check=adb_check)
  File "/srv/lava/.cache<email address hidden>/lava_dispatcher/client/base.py", line 458, in boot_linaro_android_image
    raise OperationFailed("booting into android test image failed")
OperationFailed: booting into android test image failed

LAVA job failed:
http://validation.linaro.org/lava-server/scheduler/job/53860/log_file

[Ryan Harkin (ryanharkin)]

Of course, what you are seeing, Naresh, is a *different* problem to the one this bug describes :-O

LAVA was upgraded to boot via the A7 cluster, it just happens that booting from the A7 cluster is buggier than booting from the A15 cluster. That's a UEFI problem, not a LAVA problem, so it's down to me.

So this bug should stay closed and a new bug (that I'll raise tomorrow) will be needed to track the new problem.