Re: Arndale support

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Tue, Dec 4, 2012 at 6:18 AM, James White
<james.white.2012@xxxxxxxxxxx> wrote:
>
>
>
> ----------------------------------------
>> Date: Mon, 3 Dec 2012 10:39:05 -0500
>> Subject: Re:  Arndale support
>> From: cdall@xxxxxxxxxxxxxxx
>> To: james.white.2012@xxxxxxxxxxx
>> CC: kvmarm@xxxxxxxxxxxxxxxxxxxxx
>>
>> On Mon, Dec 3, 2012 at 10:28 AM, James White
>> <james.white.2012@xxxxxxxxxxx> wrote:
>> >
>> >> Subject: Re:  Arndale support
>> >>
>> >>
>> >>
>> >> On Tue, Nov 20, 2012 at 9:35 AM, Christoffer Dall
>> >> <cdall@xxxxxxxxxxxxxxx<mailto:cdall@xxxxxxxxxxxxxxx>> wrote:
>> >> Hi there,
>> >>
>> >> For those of you with an Arndale board who would like to boot KVM on
>> >> it, I have a hack for u-boot and the kernel that makes things work.
>> >>
>> >> Take a look here:
>> >>
>> >> https://github.com/columbia/linux-kvm-arm/tree/lue_arndale-kvm
>> >> branch: lue_arndale-kvm
>> >> (use the arndale_kvm_defconfig if you like)
>> >>
>> >> And the u-boot code here:
>> >> https://github.com/columbia/u-boot-arndale
>> >> branch: lue_arndale-kvm
>> >>
>> >>
>> >> oh, and here's some instructions for how to flash.
>> >>
>> >> Use this as a starting
>> >> point: https://wiki.linaro.org/Boards/Arndale/Setup/EnterpriseUbuntuServer
>> >>
>> >> Make sure you flash the bl1 and the dt and such, and set up the right
>> >> u-boot environment.
>> >>
>> >> To flash this u-boot, do:
>> >>
>> >> $ export ARCH=arm
>> >> $ export CROSS_COMPILE=<whatever you use>
>> >> $ cd u-boot-arndlae
>> >> $ make arndale5250 #builds both SPL and u-boot proper
>> >> $ sudo dd if=spl/smdk5250-spl.bin of=/dev/sdX bs=512 seek=17
>> >> $ sudo dd if=u-boot.bin of=/dev/sdX bs=512 seek=49
>> >>
>> >> $ cd ../linux-kvm-arm
>> >> $ git checkout lue_arndale-kvm
>> >> $ make arndale_kvm_defconfig
>> >> $ make -j8 uImage
>> >> $ sudo dd if=arch/arm/boot/uImage of=/dev/sdX bs=512 seek=1105
>> >>
>> >> and that's it.
>> >
>> > I have built u-boot and linux-kvm-arm from your trees, but when I try to boot the board I get the following error:
>> >
>> > MMC read: dev # 0, block # 1105, count 8192 ... 8192 blocks read: OK
>> > ## Booting kernel from Legacy Image at 40007000 ...
>> > Image Name: Linux-3.7.0-rc4
>> > Image Type: ARM Linux Kernel Image (uncompressed)
>> > Data Size: 2640608 Bytes = 2.5 MiB
>> > Load Address: 40008000
>> > Entry Point: 40008000
>> > Verifying Checksum ... OK
>> > Loading Kernel Image ... OK
>> > OK
>> >
>> > Starting kernel ...
>> >
>> > Uncompressing Linux... done, booting the kernel.
>> >
>> > Error: unrecognized/unsupported machine ID (r1 = 0x00000ebe).
>> >
>> > Available machine support:
>> >
>> > ID (hex) NAME
>> > ffffffff SAMSUNG EXYNOS5 (Flattened Device Tree)
>> >
>> > Please check your kernel config and/or bootloader.
>> >
>> >
>> > I have built a DTB as described here https://wiki.linaro.org/Boards/Arndale/Setup/EnterpriseUbuntuServer and it is the last binary on the SD card. ( I dd'ed it onto the card as described in that documentation. )
>> >
>> > However, I think the kernel fails to find the DTB and so it complains.
>> >
>> > Looking through the u-boot code, in particular lowlevel_init.S I do not see where u-boot hands the address of the DTB to the kernel? Shouldn't that be placed in register r3 as described in Documentation/arm/Booting, or am I missing something?
>> >
>> > Thanks for your help.
>> >
>> I had this one too, but I don't remember what I did wrong. Perhaps not
>> setting the right u-boot params. Try following this guide *carefully*:
>> https://wiki.linaro.org/Boards/Arndale/Setup/EnterpriseUbuntuServer
>
> I think it comes from the bootcmd environment variable.
> bootcmd=mmc read 40007000 451 2000;mmc read 42000000 2451 20;bootm 40007000 - 42000000
>
> Can you explain where the offset 451 comes from? I assume that is the starting point of the kernel binary, and then 2451 is the starting point of the DTB?
> Can you confirm that this is this case and how it is meant to be? Or is 2451 actually the starting point of the ramdisk?
>
This relates to your dd commands, 451 is actually hex, 0x451 :)

-Christoffer
_______________________________________________
kvmarm mailing list
kvmarm@xxxxxxxxxxxxxxxxxxxxx
https://lists.cs.columbia.edu/cucslists/listinfo/kvmarm


[Index of Archives]     [Linux KVM]     [Spice Development]     [Libvirt]     [Libvirt Users]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux