Comment 6 for bug 1189457

On 08/27/2013 02:51 PM, Tixy (Jon Medhurst) wrote:
> On Tue, 2013-08-27 at 12:44 +0000, Julien Grall wrote:
>> Yes, I have add the device tree diff in attachment.
>>
>>> Generally, removing all entries for one cluster should work, I did this
>>> on the Linux 3.10 based LSK build last week and dtb's modified like this
>>> are also used successfully with the workload automation tests.
>>
>> I just tried again the latest Linaro tree (ll_20130821.0) and the
>> platform still hangs.
>
> I've just tried the same and it works for me, perhaps your bootloader is
> starting the kernel on the A7 cluster and not the A15?
>
> Tip, to check which CPU the system is booting on, look for a line in
> kernel boot for 'CPU0:' like
>
> CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
>
> or
>
> CPU0: thread -1, cpu 0, socket 1, mpidr 80000100
>
> On TC2, the mpidr value is 80000000 for the first A15 cpu and 80000100
> for the first A7.
>
> If you are using bootmon, or UEFI started from bootmon, then the boot
> CPU is changed by editing the file SITE1/HBI0249A/board.txt on the
> vexpress internal micro-SD card, and clearing bit 28 of the SCC: 0x700
> value, e.g. to boot on A15 I used the line:
>
> SCC: 0x700 0x0032F003
>
> Our standard config in the files on the Linaro release pages has it set
> for A7 booting with:
>
> SCC: 0x700 0x1032F003
>
> I this isn't the problem, can you provide a log of the serial output
> during a failed boot, including all bootmonitor and bootloader output
> from before the kernel is started.

Unfortunately, I still can't boot Linux on the versatile express.
board.txt is correctly modified
(http://releases.linaro.org/13.07/ubuntu/vexpress/).

You can find in attachment the serial output.

Cheers,

--
Julien Grall