[meta-xilinx] How to verify that BITSTREAM is loaded...???

[Mike Looijmans]

On 02/18/2014 08:56 AM, Alan DuBoff wrote:
> On Mon, February 17, 2014 10:35 pm, Mike Looijmans wrote:
>> You can check in a shell script:
>>       result=`cat /sys/devices/amba.[0123]/f8007000.devcfg/prog_done` if [
> $result -ne 1 ]; then
>>         echo "ERROR configuring FPGA, logic is not configured!"
>>         exit 1
>>       fi
>
> Thanks, I'll just remember to check the prog_done to see what it in it. I have
> 0 in mine at the moment, so it didn't load it.
>
>> I've been using /dev/xdevcfg from the beginning. The more natural place for
> the bitstream is the root filesystem. Loading the bitstream from a
> bootloader
>> seems like a hack to me.
>
> I agree that it seems more natural, I have only booted from flash in the past,
> and that just seemed like a cleaner solution.
>
> However, I agree with you in regard to being able to load logic at runtime. No
> question that is convenient. What about using PL during the second stage boot
> loader? You don't have that option with sysfs.

I'd only use an early stage PL load if really really needed. For example, if 
you want to implement an PCI-X slave interface in logic, the PL has to be up 
and running in about 100ms, so you'll have to do something smart probably in 
the FSBL to get this working.

Loading logic in the secondstage (usually u-boot) only makes sense if you 
always use the same image and need to have all drivers reside inside the 
kernel instead of using loadable modules for the drivers that require the PL 
to be active.

Loading PL from up-and-running linux allows you to let both CPU cores continue 
doing useful work while the FPGA is being programmed. So in effect, 
programming doesn't actually take any time away from other tasks.




Met vriendelijke groet / kind regards,

Mike Looijmans

TOPIC Embedded Systems
Eindhovenseweg 32-C, NL-5683 KH Best
Postbus 440, NL-5680 AK Best
Telefoon: (+31) – (0)499 - 33.69.79
Telefax: (+31) - (0)499 - 33.69.70
E-mail: mike.looijmans at topic.nl
Website: www.topic.nl

Dit e-mail bericht en de eventueel daarbij behorende bijlagen zijn uitsluitend bestemd voor de geadresseerde, zoals die blijkt uit het e-mail bericht en/of de bijlagen. Er kunnen gegevens met betrekking tot een derde instaan. Indien u als niet-geadresseerde dit bericht en de bijlagen ontvangt, terwijl u niet bevoegd of gemachtigd bent om dit bericht namens de geadresseerde te ontvangen, wordt u verzocht de afzender hierover direct te informeren en het e-mail bericht met de bijlagen te vernietigen. Ieder gebruik van de inhoud van het e-mail bericht, waaronder de daarbij behorende bijlagen, door een ander dan de geadresseerde is onrechtmatig jegens ons dan wel de eventueel in het e-mail bericht of de bijlagen voorkomende andere personen. TOPIC Embedded Systems is niet aansprakelijk voor enigerlei schade voortvloeiend uit het gebruik en/of acceptatie van dit e-mail bericht of de daarbij behorende bijlagen.

The contents of this message, as well as any enclosures, are addressed personally to, and thus solely intended for the addressee. They may contain information regarding a third party. A recipient who is neither the addressee, nor empowered to receive this message on behalf of the addressee, is kindly requested to immediately inform the sender of receipt, and to destroy the message and the enclosures. Any use of the contents of this message and/or the enclosures by any other person than the addressee or person who is empowered to receive this message, is illegal towards the sender and/or the aforementioned third party. TOPIC Embedded Systems is not  liable for any damage as a result of the use and/or acceptance of this message and as well as any enclosures.