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

[Mike Looijmans]

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

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.

With the bitstream in the rootfs, the bitstream can be compressed (on an ubifs 
root in flash, the 4MB bitstream only takes up about 500k of flash because of 
the LZO compression), and you can have multiple alternative bitstreams on a 
single device. I regularly test out new bitstreams by simply unloading modules 
using them, sending a new stream over ssh, and restarting the drivers. The 
system is up and running a new bitstream in about 0.2 seconds.

And besides that, xdevcfg is the way to go to use partial configuration.

Mike.


On 02/18/2014 12:54 AM, Alan DuBoff wrote:
>
> On Mon, February 17, 2014 3:50 pm, Alan DuBoff wrote:
>> I have been trying to figure out the difference between booting off the sd
>> card or flash. Specificially I was thinking that the bitstream could only be
>> loaded from flash, but with the newer /dev/xdevcfg style of updating the
>> bitstream, I guess it's less important for such...
>>
>> I'm not crazy about using /dev/xdevcfg, it seems kinda like a hack to me.
>>
>> I included the bitstream on an image I built recently which I'm booting off
>> the sd card, but is it possible to list with one of the utilities to verify it
>> is loaded?
>
> Hah, fat fingered that one, changing subject to reflect BITSTREAM and not
> bitmap...<duh!>
>



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.