[meta-xilinx] Bitstream/Boot.bin/etc - Providers/Virtual targets

[Michal Simek]

On 02/13/2014 03:54 PM, Philip Balister wrote:
> On 02/13/2014 08:53 AM, Mike Looijmans wrote:
>> On 02/13/2014 02:27 PM, Philip Balister wrote:
>>> On 02/13/2014 07:16 AM, Mike Looijmans wrote:
>>>> On 02/13/2014 01:05 PM, Michal Simek wrote:
>>>>> Hi guys,
>>>>>
>>>>> nice discussing and maybe good time to jump into.
>>>>>
>>>>> On 02/13/2014 08:15 AM, Cjw X wrote:
>>>>>> We should unequivocally throw the FSBL into the fires of Mount Doom.
>>>>>>
>>>>>> I've been working with u-boot-spl running on my microzed for about a
>>>>>> month
>>>>>> now, and I'm already considerably happier with it.
>>>>>
>>>>> spl is nice and it will be supported in mainline u-boot soon.
>>>>> My patches have been already reviewed and waiting for adding to arm
>>>>> custodian
>>>>> tree.
>>>>> It means u-boot spl will be available for everybody.
>>>>
>>>> I took a peek at master-next of u-boot-xlnx, and it builds just fine. I
>>>> can't get the "spl" part working though. The u-boot.bin it generates
>>>> will boot fine when paired with an fsbl, but the "boot.bin" it creates
>>>> just doesn't boot at all.
>>>>
>>>> What's the step to really activate the SPL part, because currently it
>>>> just generates something that doesn't boot at all.
>>>
>>> The boot.bin file from an spl build loads the u-boot.img file. You need
>>> both now.
>>
>> On the FAT partition of the SD card then?
> 
> Yes.
> 
>>
>> What if I boot from flash? (usually I run the bootloader from flash and
>> the image from either flash or SD)
> 
> I'm not sure. Michal?

Just look at the code and you will see.
For SD there is a mode which I am using which is loading u-boot.img from
FAT partition on SD. There is also mode where images doesn't need to be
on FAT but RAW mode can be used.

Regarding flashes.
QSPI - I didn't try to add boon.bin to QSPI but I have tried to load u-boot-spl
on zc702 which loads images stored in qspi. Location on that images
is fully configurable in zynq-common.h config and you can change it.
NOR - I don't have any zynq board with NOR that's why I didn't test it
but from the code I have seen it is the same case as qspi - just need to setup
offsets.
NAND - we have nand driver in our tree and all SPL infrastructure for nand
is in place that's why it will just work too.

In general for all modes it is working in 2 stages which is spl -> load full u-boot
Or in boot os mode spl just boot Linux or another OS without full u-boot.
Full u-boot can be added to filesystem or not and can be the part of spl or not.

Just check configuration.
But if you need any help you have to provide better information about your configuration
because it is hard to suggest what exactly you are using.

Thanks,
Michal

-- 
Michal Simek, Ing. (M.Eng), OpenPGP -> KeyID: FE3D1F91
w: www.monstr.eu p: +42-0-721842854
Maintainer of Linux kernel - Microblaze cpu - http://www.monstr.eu/fdt/
Maintainer of Linux kernel - Xilinx Zynq ARM architecture
Microblaze U-BOOT custodian and responsible for u-boot arm zynq platform


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 263 bytes
Desc: OpenPGP digital signature
URL: <http://lists.yoctoproject.org/pipermail/meta-xilinx/attachments/20140214/3f60d0d7/attachment.pgp>