> Hello,No, sysace_fread() only load bitstream from flash to the buffer you point
>
> Another question, dose the sysace_fread() has relation with ICAP?
> I use HWICAP 1.00.b, dirver 1.00c
>
to. Checke the codes of XHwIcap_CF2Icap(), you will know how the process
works.
>> http://www.itee.uq.edu.au/~listarch/partial-reconfig/archive/2008/09/msg00006.html<http://www.itee.uq.edu.au/%7Elistarch/partial-reconfig/archive/2008/09/msg00006.html>
> Thanks for your help.
>
> Best Regards,
> Shih-Shen
>
> 2008/11/26 Lu Yi <yilu@xxxxxxxxxxxxxxxxxxxxx>
>
>> Hello,
>>
>> As far as I know, at least the ICAP module 1.00.b and drive 1.00.c works
>> for V4 board when you use the sysace_fread().
>> check the follwing link and database of Sept.
>>
>>
>> regards,
>> luyi
>> > Hello,
>> >
>> > Can I ask a question? Can you use sysace_fread() to read your
>> bitstream
>> ?
>> > I meet the same problem that sysace_fread() dosen't work. I do not
>> make
>> > sure
>> > that I use ICAP_X0Y1, but I run the ICAP example that show the same
>> output
>> > with yours.
>> > These are the result of the test:
>> >
>> --------------------------------------------------------------------------
>> > Status: 447
>> > HWICAP Status Register:
>> > cfgerr_n: 1
>> > dalign: 1
>> > rip: 0
>> > in_abort_n: 1
>> > Always 1: 1
>> > Always 1: 1
>> > Always 1: 1
>> > Always 1: 1
>> > Done: 1
>> > -- Reading Device IDCODE through ICAP:
>> > Creating cmd bitstream...
>> > Sending cmd bitstream to ICAP...
>> > Reading from ICAP...
>> > Device IDCODE is: 9321EB40
>> > -- Reading Device IDCODE through ICAP:
>> > Creating cmd bitstream...
>> > Sending cmd bitstream to ICAP...
>> > Reading from ICAP...
>> > Device IDCODE is: 9321EB40