[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: [partial-reconfig] crc error writing partial bitstreams to icap
Mati,
Thanks for the information. I have currently given up using their
HW_ICAP driver/ip and am working on my own. I will definitely keep that
in mind as I try and get it to accept my bitstreams.
-Brian
-----Original Message-----
From: owner-partial-reconfig@xxxxxxxxxxxxxx
[mailto:owner-partial-reconfig@xxxxxxxxxxxxxx] On Behalf Of Mati Nahshon
Sent: Wednesday, December 19, 2007 1:15 PM
To: partial-reconfig@xxxxxxxxxxxxxx
Subject: RE: [partial-reconfig] crc error writing partial bitstreams to
icap
Hi,
I am not sure this info will help you...
The ICAP has both I and O ports as appose to select map that uses
bidirectional port for both. The documentation (which I looked at last a
few
months ago...) does not say what the O port reads when something other
then
a read sequence is performed. But during my debug I have noticed that
the
abort status word is presented on the O port if read is not preformed.
This
is not documented but this is what I saw. [I was not using HW_ICAP
rather
my own wrapper with direct view into the ICAP signals.]
Mati
-----Original Message-----
From: owner-partial-reconfig@xxxxxxxxxxxxxx
[mailto:owner-partial-reconfig@xxxxxxxxxxxxxx] On Behalf Of Brian Sutton
Sent: Friday, December 14, 2007 4:40 PM
To: partial-reconfig@xxxxxxxxxxxxxx
Subject: RE: [partial-reconfig] crc error writing partial bitstreams to
icap
Justin,
Thanks for the reply. I have spent a while looking at the abort
sequence and don't think it is possible to reach via the ICAP port. The
abort status word is sent out when the RDWR status changes while
SelectMAP CS is active. I looked at the hwicap statemachine and believe
that this is an impossible condition to reach for the icap. It looks
like the only way to change the rw signal is when ce is deasserted.
That being said, I can't rule out that it is sending out the abort
status word for whatever reason. I'll continue to look into it more.
Thanks.
-Brian
-----Original Message-----
From: owner-partial-reconfig@xxxxxxxxxxxxxx
[mailto:owner-partial-reconfig@xxxxxxxxxxxxxx] On Behalf Of Justin Braun
Sent: Thursday, December 13, 2007 1:11 PM
To: partial-reconfig@xxxxxxxxxxxxxx
Subject: Re: [partial-reconfig] crc error writing partial bitstreams to
icap
Brian,
0x000000DF looks like an abort status word, pg 50-51 in the Virtex-4
configuration guide. I'm not familiar with the hwicap, but it seems like
this might have to do with switching from write to read.
Justin
On Thu, 2007-12-13 at 10:51 -0500, Brian Sutton wrote:
> Hi,
>
>
>
> I am writing in regard to the following thread (just joined the list):
>
>
>
>
http://www.itee.uq.edu.au/~listarch/partial-reconfig/archive/2007/10/msg
00006.html
>
>
>
> I have a very similar situation - iMPACT programming of the device
> works whereas if I use the ICAP port I get CRC errors.
>
>
>
> I am using EDK 9.2.01i with opb_hwicap v1.10a. I can read the
> register space successfully but as soon as I try and load the partial
> bitstreams through ICAP I get CRC errors. I tried disabling the CRC
> check in the bit files but this still did make partial reconfig
> through ICAP work.
>
>
>
> The one thing that I have noticed when using the hwicap driver is that
> each time I fill the BRAM with bitstream data and do a
> deviceWrite/readback the first word is not the expected value. I have
> performed the same experiment with very simple command register
> accesses:
>
>
>
> Packet = XHwIcap_Type1Write(XHI_AXSS_IDCODE) | 1; // just picked a
> register I could r/w to, this is not done during reconfiguration
>
> XHwIcap_StorageBufferWrite(&myICAP, 0, XHI_DUMMY_PACKET);
>
> XHwIcap_StorageBufferWrite(&myICAP, 1, XHI_SYNC_PACKET);
>
> XHwIcap_StorageBufferWrite(&myICAP, 2, XHI_NOOP_PACKET);
>
> XHwIcap_StorageBufferWrite(&myICAP, 3, Packet);
>
> XHwIcap_StorageBufferWrite(&myICAP, 4, 0xF0F0F0F0);
>
> XHwIcap_StorageBufferWrite(&myICAP, 5, XHI_NOOP_PACKET);
>
> XHwIcap_StorageBufferWrite(&myICAP, 6, XHI_NOOP_PACKET);
>
>
>
> Status = XHwIcap_DeviceWrite(&myICAP, 0, 7);
>
>
>
> //sent
>
> 40200000 : FFFFFFFF
>
> 40200004 : AA995566
>
> 40200008 : 20000000
>
> 4020000C : 3001A001
>
> 40200010 : F0F0F0F0
>
> 40200014 : 20000000
>
> 40200018 : 20000000
>
>
>
> Status = XHwIcap_DeviceRead(&myICAP, 0, 7);
>
>
>
> //read
>
> 40200000 : 000000DF
>
> 40200004 : AA995566
>
> 40200008 : 20000000
>
> 4020000C : 3001A001
>
> 40200010 : F0F0F0F0
>
> 40200014 : 20000000
>
> 40200018 : 20000000
>
>
>
> The returned buffer is identical except for the XHI_DUMMY_PACKET. The
> 0x000000DF is what I always get for the very first write out to the
> device through the ICAP.
>
>
>
> Is this normal or can anyone shed insight into the problem?
>
>
>
> Thanks,
>
> Brian Sutton
>
>
>
>
___________________________
partial-reconfig mailing list
partial-reconfig@xxxxxxxxxxxxxx
Mailing List Archive :
http://www.itee.uq.edu.au/~listarch/partial-reconfig/
___________________________
partial-reconfig mailing list
partial-reconfig@xxxxxxxxxxxxxx
Mailing List Archive :
http://www.itee.uq.edu.au/~listarch/partial-reconfig/
___________________________
partial-reconfig mailing list
partial-reconfig@xxxxxxxxxxxxxx
Mailing List Archive :
http://www.itee.uq.edu.au/~listarch/partial-reconfig/
___________________________
partial-reconfig mailing list
partial-reconfig@xxxxxxxxxxxxxx
Mailing List Archive : http://www.itee.uq.edu.au/~listarch/partial-reconfig/