ICAP attached to Microblaze on Virtex 2-pro..

X

Xesium

Guest
Hi everybody,
I'm trying to partially reconfigure my device (XC2VP30 on ML310 board)
through ICAP. I have my ICAP attached to OPB which is attached to
Microblaze. In bitgen.ut file I have set the value of mode pins
(M2M1M0) to 1 (PULLUP). So it is not set on 101 which is JTAG mode. As
well the base address and high address of my HWICAP is 0x42000000 and
0x42000fff as mentioned in the datasheet of HWICAP. Initially my OPB
clock frequency was 100 MHz but now I have reduced it to 25MHz. The
system contains a timer, a SysAce, a hwicap, a uartlite and an opb-mdm
(for debugging) all attached to the opb. The microblaze has some local
memory too. I'm also using EDK, ISE 8.2. That's the whole setting
about my system. Now here is the problem:

I just need to measure the delay of reconfiguration through ICAP. The
following is a very simple C code I have implemented to read a frame
and print the content on the screen. Later I want to write something
to a frame and again read it back just to make sure that in fact it
changed the reconfiguration. Firstly I initialize the ICAP module and
then invoke XHwIcap_DeviceReadFrame() and then I read the
configuration through XHwIcap_StorageBufferRead().

XHwIcap my_icap;

XStatus icap_stat;

icap_stat = XHwIcap_Initialize(&my_icap,
XPAR_OPB_HWICAP_0_DEVICE_ID, XHI_READ_DEVICEID_FROM_ICAP);

if(icap_stat != XST_SUCCESS)
print("\n There is something wrong in initializing the ICAP!!
\n");

Xuint32 frame_content;

icap_stat = XHwIcap_DeviceReadFrame(&my_icap, XHI_FAR_CLB_BLOCK,
32, 32);

if(icap_stat != XST_SUCCESS)
print("\n There is something working in reading a frame with col
= 5 and lut_bit = 3!!!!!\n");

for(i = 0; i < my_icap.WordsPerFrame; i++)
{
print("word number");
putnum(i+1);
print(" is equal to: ");
frame_content = XHwIcap_StorageBufferRead(&my_icap, i);
putnum(frame_content);
putchar('\n');
}

The problem is when I read back the frame except for the first 7 words
everything is 0, no matter what frame it is.
I have carefully studied ICAP's driver's functions and their
implementation. I know that the driver writes the first 7 words in the
storage buffer but even the 7 words that I read from the storage
buffer is not the same as the ones that the driver's deviceRead
function writes to the storage buffer. So I don't get what the problem
is.
The seven words that I read are as follows:

30008001
0000000d
ffffffff
ffffffff
30002001
00404000
2800619c

However for example based on the driver's implementation the first
word should be 0xFFFFFFFF which is an XHI_DUMMY_PACKET.

So as I mentioned, my problem is I can't basically read a frame of
configuration correctly. Do you have any idea where I'm doing wrong or
what the problem is?

As well I have some doubts and questions. Firstly why should we first
read a frame, modify it and then write it back to the configuration?
Can't we just write something to the device? I haven't still worked
with difference-based reconfiguration and it might have something to
do with that. But if I just want to write configuration to one frame
that doesn't implement any other part of any other circuit, can't I
just write something to that frame without first reading it and
modifying it?

The second question that I have is about the storage buffer of the
HWICAP module. Firstly I thought that I have to set an opb_bram so
that HWICAP can use it. However later through studying the driver I
realized that the base address for HWICAP is the same as storage
buffer (which is the BRAM) so I concluded that when I use a HWICAP I
implicitly assign a BRAM to it. Is this so? If not please let me know.

The third question is the clock frequency that ICAP operates! I have
read somewhere that the highest is 66MHz. Is it correct or we can set
the clock higher than that?

This message became very long, but I really appreciate it if you could
kindly help me out with it. I have read many of the previous posts
about ICAP but couldn't find enough information to solve my problems.
So perhaps this post can be a complement to them.

Thanks a lot beforehand,

Amir
 
Hi Amir,

What you do is quite interesting! We have gone through a similar
process and i must say that
although it is a painful one it is a fun work as well!

On Feb 27, 10:54 pm, Xesium <amirhossein.gholamip...@gmail.com> wrote:
Hi everybody,
I'm trying to partially reconfigure my device (XC2VP30 on ML310 board)
through ICAP. I have my ICAP attached to OPB which is attached to
Microblaze. In bitgen.ut file I have set the value of mode pins
(M2M1M0) to 1 (PULLUP). So it is not set on 101 which is JTAG mode. As
Click to expand...
This is correct. Also be aware that the Persist bit shouldn't be set;
otherwise ICAP
will be disabled.

well the base address and high address of my HWICAP is 0x42000000 and
0x42000fff as mentioned in the datasheet of HWICAP. Initially my OPB
clock frequency was 100 MHz but now I have reduced it to 25MHz. The
system contains a timer, a SysAce, a hwicap, a uartlite and an opb-mdm
(for debugging) all attached to the opb. The microblaze has some local
memory too. I'm also using EDK, ISE 8.2. That's the whole setting
Click to expand...
I would suggest you to transit to the EDK, ISE 9.1+SP2. Moreover, EAPR
tools
would help you boosting your design. Check the link
http://www.xilinx.com/support/prealounge/protected/index.htm


about my system. Now here is the problem:

I just need to measure the delay of reconfiguration through ICAP. The
following is a very simple C code I have implemented to read a frame
and print the content on the screen. Later I want to write something
to a frame and again read it back just to make sure that in fact it
changed the reconfiguration. Firstly I initialize the ICAP module and
then invoke XHwIcap_DeviceReadFrame() and then I read the
configuration through XHwIcap_StorageBufferRead().


XHwIcap my_icap;

XStatus icap_stat;

icap_stat = XHwIcap_Initialize(&my_icap,
XPAR_OPB_HWICAP_0_DEVICE_ID, XHI_READ_DEVICEID_FROM_ICAP);

if(icap_stat != XST_SUCCESS)
print("\n There is something wrong in initializing the ICAP!!
\n");

Xuint32 frame_content;

icap_stat = XHwIcap_DeviceReadFrame(&my_icap, XHI_FAR_CLB_BLOCK,
32, 32);

if(icap_stat != XST_SUCCESS)
print("\n There is something working in reading a frame with col
= 5 and lut_bit = 3!!!!!\n");

for(i = 0; i < my_icap.WordsPerFrame; i++)
{
print("word number");
putnum(i+1);
print(" is equal to: ");
frame_content = XHwIcap_StorageBufferRead(&my_icap, i);
putnum(frame_content);
putchar('\n');
}

The problem is when I read back the frame except for the first 7 words
everything is 0, no matter what frame it is.
I have carefully studied ICAP's driver's functions and their
implementation. I know that the driver writes the first 7 words in the
storage buffer but even the 7 words that I read from the storage
buffer is not the same as the ones that the driver's deviceRead
function writes to the storage buffer. So I don't get what the problem
is.
The seven words that I read are as follows:

30008001
0000000d
ffffffff
ffffffff
30002001
00404000
2800619c

However for example based on the driver's implementation the first
word should be 0xFFFFFFFF which is an XHI_DUMMY_PACKET.

So as I mentioned, my problem is I can't basically read a frame of
configuration correctly. Do you have any idea where I'm doing wrong or
what the problem is?
Click to expand...
We have not tried the readback operation but...are you sure that you
read the correct address
the XHI_DUMMY_PACKET is stored in?
Why don't you first try to write and then read what you wrote?
Use the functions XHwIcap_StorageBufferWrite() and
XHwIcap_DeviceWrite().

Also notice that if you use JTAG to initially program the device, and
then ICAP you can use them on the same design but, between each mode
the configuration logic has to be desynchronized. In order to use the
ICAP port you should use the XhwIcap_CommandDesync() function.


As well I have some doubts and questions. Firstly why should we first
read a frame, modify it and then write it back to the configuration?
Can't we just write something to the device? I haven't still worked
with difference-based reconfiguration and it might have something to
do with that. But if I just want to write configuration to one frame
that doesn't implement any other part of any other circuit, can't I
just write something to that frame without first reading it and
modifying it?
Click to expand...
The on-chip reconfiguration operates in a read-modify-write manner.
The date frame
is read back from the ICAP port and stored in the BRAM of the HWICAP
(see below)
in which the processor modifies the data. Afterwards, the HWICAP
downloads
the new data back to the configuration memory through the ICAP port.

The second question that I have is about the storage buffer of the
HWICAP module. Firstly I thought that I have to set an opb_bram so
that HWICAP can use it. However later through studying the driver I
realized that the base address for HWICAP is the same as storage
buffer (which is the BRAM) so I concluded that when I use a HWICAP I
implicitly assign a BRAM to it. Is this so? If not please let me know.
Click to expand...
The "xhwicap_i.h" header file contains the XHI_MAX_BUFFER_INTS
constant which defines the size of the ICAP BRAM . The HWICAP BRAM,
i.e. storage buffer,
is implemented with a BRAM of which the 512 words at maximum are used
(at least the above
stands for EDK 7.1.i in which we conducted the experiments).

The third question is the clock frequency that ICAP operates! I have
read somewhere that the highest is 66MHz. Is it correct or we can set
the clock higher than that?
Click to expand...
Yes, this is the ICAP's frequency for the Virtex-2 when BUSY signal is
checked
(50 MHz when not checked). New devices like Virtex-4 embed an 100 Mhz
ICAP.

This message became very long, but I really appreciate it if you could
kindly help me out with it. I have read many of the previous posts
about ICAP but couldn't find enough information to solve my problems.
So perhaps this post can be a complement to them.

Thanks a lot beforehand,

Amir
Click to expand...
I hope this helps. Keep up the good work and let me know about the
result.
Besides PR entails a hell of details!:)

Take care,
Kyprianos
 
Microblaze. In bitgen.ut file I have set the value of mode pins
(M2M1M0) to 1 (PULLUP). So it is not set on 101 which is JTAG mode. As
well the base address and high address of my HWICAP is 0x42000000 and
0x42000fff as mentioned in the datasheet of HWICAP. Initially my OPB
Click to expand...

Amir,

In which way to you load the initial configuration? Do you load it
through the ICAP and you don't use
ICAP at all?Did you check the Persist option?
As a second thought check the ICAP configuration. Has it been
configured appropriately? Have the base address and the high address
been added in the xparameters.h file?

Take care,
Kyprianos
 
Hi Kyprianos,
Thanks a lot for your comments. I checked to make sure that persist
bit is also not set. I also checked the base and high address in
xparameters.h file and they are as I had set them before. I'm actually
configuring my device using parallel cable 4 and through JTAG (I
guess!). I wasn't desynchronizing before using ICAP but now I tried
doing that to make sure that I'm not doing anything wrong. I'm not
sure how I can verify ICAP's correct configuration, but I actually
print ICAP's base address (using putnum(my_icap.BaseAddress);
statement) to make sure that it is the same as what I'd set before and
it is actually the same! However the result for me is still the same!
I tried changing the Major and Minor address that I'm writing to.
Nothing really changes if I just read it. But when I try writing to it
(just writing an arbitrary value (0xFFFFFFFF) to some address in the
storage buffer!) and then reading it exactly as the following code,
sometimes the output of DeviceReadFrame method is that the device is
busy and just then it gives me some numbers that some of them actually
are not 0. However it never happens that I actually read the same
value that I'm writing! I'm wondering, for example in your case, how
is the content of the storage buffer when you read back the
configuration? Is it mostly 0 and a few of them are non-zero?
Should I be reading words or bytes? Because I realized that when I'm
reading from compact flash I'm actually reading in bytes not words! So
when I'm writing to the storage buffer of ICAP should I be writing in
bytes or in words? If it should be in words then it means that I have
manipulate the data I'm reading from Compact Flash!
Well that's another problem but for now I can't get the ICAP work and
appreciate any suggestion and comment!
For now I'll try installing ISE and EDK 9.2 instead of 8.2 and am
keeping my fingers crossed that may work!

Thanks a lot,

Amir

My code is as follows:

XHwIcap my_icap;

XStatus icap_stat;

icap_stat = XHwIcap_Initialize(&my_icap,
XPAR_OPB_HWICAP_0_DEVICE_ID, XHI_READ_DEVICEID_FROM_ICAP);

if(icap_stat != XST_SUCCESS)
print("\n There is something wrong in initializing the ICAP!!
\n");

icap_stat = XHwIcap_CommandDesync(&my_icap);

if(icap_stat != XST_SUCCESS)
print("\n Desynchronization was not successful!\n");

XHwIcap_StorageBufferWrite(&my_icap, 25, 0xffffffff);

icap_stat = XHwIcap_DeviceWriteFrame(&my_icap, XHI_FAR_CLB_BLOCK,
20, 32);

print("A frame has been written to the device\n");


if(icap_stat != XST_SUCCESS)
print("There is something wrong in writing to the device!");

Xuint32 frame_content;

icap_stat = XHwIcap_DeviceReadFrame(&my_icap, XHI_FAR_CLB_BLOCK,
20, 32);

print("The same frame is read from the configuration\n");

if(icap_stat != XST_SUCCESS)
print("\n There is something wrong in reading a frame with col =
5 and lut_bit = 3!!!!!\n");

if(icap_stat == XST_DEVICE_BUSY)
print("\n Device is busy right now!\n");

if(icap_stat == XST_BUFFER_TOO_SMALL)
print("BUFFER is TOO SMULL!\n");

if(icap_stat == XST_INVALID_PARAM)
print("XST_INVALID_PARAM!\n");

for(i = 0; i < my_icap.WordsPerFrame; i++)
{
print("word number");
putnum(i+1);
print(" is equal to: ");
frame_content = XHwIcap_StorageBufferRead(&my_icap, i);
putnum(frame_content);
putchar('\n');
}



On Feb 29, 8:29 pm, kyprianos <kpapa...@mhl.tuc.gr> wrote:
Microblaze. In bitgen.ut file I have set the value of mode pins
(M2M1M0) to 1 (PULLUP). So it is not set on 101 which is JTAG mode. As
well the base address and high address of my HWICAP is 0x42000000 and
0x42000fff as mentioned in the datasheet of HWICAP. Initially my OPB

Amir,

In which way to you load the initial configuration? Do you load it
through the ICAP and you don't use
ICAP at all?Did you check the Persist option?
As a second thought check the ICAP configuration. Has it been
configured appropriately? Have the base address and the high address
been added in the xparameters.h file?

Take care,
Kyprianos
Click to expand...
 
On Mar 2, 4:24 am, Xesium <amirhossein.gholamip...@gmail.com> wrote:
Hi Kyprianos,
Thanks a lot for your comments. I checked to make sure that persist
bit is also not set. I also checked the base and high address in
xparameters.h file and they are as I had set them before. I'm actually
configuring my device using parallel cable 4 and through JTAG (I
guess!). I wasn't desynchronizing before using ICAP but now I tried
doing that to make sure that I'm not doing anything wrong.
Click to expand...
Let me clear this. You load the initial configuration through the
JTAG.
As you first load the data from JTAG you should set up the
configuration
mode pins as M2M1M0=101. Then XHwIcap_CommandDesync() allows you
to transit to the ICAP.
Also try the function XHwIcap_DeviceWrite() instead of
XHwIcap_DeviceWriteFrame().
The same stands for read, i.e. use XHwIcap_Device instead of
XHwIcap_DeviceReadFrame().

Did you also do assign OPB_Clk to sys_clk_s?

I'm not
sure how I can verify ICAP's correct configuration, but I actually
print ICAP's base address (using putnum(my_icap.BaseAddress);
statement) to make sure that it is the same as what I'd set before and
it is actually the same! However the result for me is still the same!
I tried changing the Major and Minor address that I'm writing to.
Nothing really changes if I just read it. But when I try writing to it
(just writing an arbitrary value (0xFFFFFFFF) to some address in the
storage buffer!) and then reading it exactly as the following code,
sometimes the output of DeviceReadFrame method is that the device is
busy and just then it gives me some numbers that some of them actually
are not 0. However it never happens that I actually read the same
value that I'm writing! I'm wondering, for example in your case, how
is the content of the storage buffer when you read back the
configuration? Is it mostly 0 and a few of them are non-zero?
Should I be reading words or bytes? Because I realized that when I'm
reading from compact flash I'm actually reading in bytes not words!
when I'm writing to the storage buffer of ICAP should I be writing in
bytes or in words? If it should be in words then it means that I have
manipulate the data I'm reading from Compact Flash!
Click to expand...
The writing to the storage buffer is executed in a word by word
fashion. When the buffer is full it sends the data to the ICAP port,
all with one function
call, and then continues copying. When it is finished copying and
there is still data in the
buffer, it writes it to ICAP and the function finishes.
This is due to the API provided with the opb_hwicap (at least for the
EDK 7.1i with
which we conducted the experiments)
Therefore, yes! you should manipulate the data you transfer from the
Compact Flash.
This depends on the API provided with the compact
flash driver which can only read ASCII character data types from a
file. This fact
introduces extra programming effort: The characters that compose a 32
bit
word have to be read and combined to form the 32 bit word-number.
A typical configuration with bitsreams from the compact flash consists
of the
following steps:
-Open the bitstream file stored in the compact flash, identify and
read the header information,
-Read a data chunk equal to a multiple of a compact flash sector i.e.
x 512 bytes,
-Synthesize a 32-bit ICAP word from every 4 bytes of the data chunk,
-Load the synthesized word into the ICAP BRAM storage buffer
......

Well that's another problem but for now I can't get the ICAP work and
appreciate any suggestion and comment!
For now I'll try installing ISE and EDK 9.2 instead of 8.2 and am
keeping my fingers crossed that may work!
Click to expand...
I can't say anything about ISE+EDK 9.2. We have conducted experiments
only
using ISE+EDK 7.1i (for difference-based performance evaluation) and
ISE 9.1i.02 (for module-based application development)

I hope this help. Let me know about the progress

Good luck,
Kyprianos

Thanks a lot,

Amir

My code is as follows:

XHwIcap my_icap;

XStatus icap_stat;

icap_stat = XHwIcap_Initialize(&my_icap,
XPAR_OPB_HWICAP_0_DEVICE_ID, XHI_READ_DEVICEID_FROM_ICAP);

if(icap_stat != XST_SUCCESS)
print("\n There is something wrong in initializing the ICAP!!
\n");

icap_stat = XHwIcap_CommandDesync(&my_icap);

if(icap_stat != XST_SUCCESS)
print("\n Desynchronization was not successful!\n");

XHwIcap_StorageBufferWrite(&my_icap, 25, 0xffffffff);

icap_stat = XHwIcap_DeviceWriteFrame(&my_icap, XHI_FAR_CLB_BLOCK,
20, 32);

print("A frame has been written to the device\n");

if(icap_stat != XST_SUCCESS)
print("There is something wrong in writing to the device!");

Xuint32 frame_content;

icap_stat = XHwIcap_DeviceReadFrame(&my_icap, XHI_FAR_CLB_BLOCK,
20, 32);

print("The same frame is read from the configuration\n");

if(icap_stat != XST_SUCCESS)
print("\n There is something wrong in reading a frame with col =
5 and lut_bit = 3!!!!!\n");

if(icap_stat == XST_DEVICE_BUSY)
print("\n Device is busy right now!\n");

if(icap_stat == XST_BUFFER_TOO_SMALL)
print("BUFFER is TOO SMULL!\n");

if(icap_stat == XST_INVALID_PARAM)
print("XST_INVALID_PARAM!\n");

for(i = 0; i < my_icap.WordsPerFrame; i++)
{
print("word number");
putnum(i+1);
print(" is equal to: ");
frame_content = XHwIcap_StorageBufferRead(&my_icap, i);
putnum(frame_content);
putchar('\n');
}

On Feb 29, 8:29 pm, kyprianos <kpapa...@mhl.tuc.gr> wrote:

Microblaze. In bitgen.ut file I have set the value of mode pins
(M2M1M0) to 1 (PULLUP). So it is not set on 101 which is JTAG mode. As
well the base address and high address of my HWICAP is 0x42000000 and
0x42000fff as mentioned in the datasheet of HWICAP. Initially my OPB

Amir,

In which way to you load the initial configuration? Do you load it
through the ICAP and you don't use
ICAP at all?Did you check the Persist option?
As a second thought check the ICAP configuration. Has it been
configured appropriately? Have the base address and the high address
been added in the xparameters.h file?

Take care,
Kyprianos
Click to expand...
 
Hi Kyprianos,
Thank you so much for your invaluable suggestions and help. It
actually worked. Now I can use ICAP and I'm reading data from CF and
load it to ICAP.

I'm planning to put a complete kind of tutorial for those who want to
do the same thing and pass on the favor I've been given by people like
you. I'm also recommending everyone who is trying to do the same to
read your paper "Methodology and Experimental Setup for the
Determination of System-level Dynamic Reconfiguration Overhead" if
they want to do dynamic reconfiguration through ICAP.

Best wishes,

Amir

On Mar 2, 5:13 pm, kyprianos <kpapa...@mhl.tuc.gr> wrote:
On Mar 2, 4:24 am, Xesium <amirhossein.gholamip...@gmail.com> wrote:

Hi Kyprianos,
Thanks a lot for your comments. I checked to make sure that persist
bit is also not set. I also checked the base and high address in
xparameters.h file and they are as I had set them before. I'm actually
configuring my device using parallel cable 4 and through JTAG (I
guess!). I wasn't desynchronizing before using ICAP but now I tried
doing that to make sure that I'm not doing anything wrong.

Let me clear this. You load the initial configuration through the
JTAG.
As you first load the data from JTAG you should set up the
configuration
mode pins as M2M1M0=101. Then XHwIcap_CommandDesync() allows you
to transit to the ICAP.
Also try the function XHwIcap_DeviceWrite() instead of
XHwIcap_DeviceWriteFrame().
The same stands for read, i.e. use XHwIcap_Device instead of
XHwIcap_DeviceReadFrame().

Did you also do assign OPB_Clk to sys_clk_s?



I'm not
sure how I can verify ICAP's correct configuration, but I actually
print ICAP's base address (using putnum(my_icap.BaseAddress);
statement) to make sure that it is the same as what I'd set before and
it is actually the same! However the result for me is still the same!
I tried changing the Major and Minor address that I'm writing to.
Nothing really changes if I just read it. But when I try writing to it
(just writing an arbitrary value (0xFFFFFFFF) to some address in the
storage buffer!) and then reading it exactly as the following code,
sometimes the output of DeviceReadFrame method is that the device is
busy and just then it gives me some numbers that some of them actually
are not 0. However it never happens that I actually read the same
value that I'm writing! I'm wondering, for example in your case, how
is the content of the storage buffer when you read back the
configuration? Is it mostly 0 and a few of them are non-zero?
Should I be reading words or bytes? Because I realized that when I'm
reading from compact flash I'm actually reading in bytes not words!
when I'm writing to the storage buffer of ICAP should I be writing in
bytes or in words? If it should be in words then it means that I have
manipulate the data I'm reading from Compact Flash!

The writing to the storage buffer is executed in a word by word
fashion. When the buffer is full it sends the data to the ICAP port,
all with one function
call, and then continues copying. When it is finished copying and
there is still data in the
buffer, it writes it to ICAP and the function finishes.
This is due to the API provided with the opb_hwicap (at least for the
EDK 7.1i with
which we conducted the experiments)
Therefore, yes! you should manipulate the data you transfer from the
Compact Flash.
This depends on the API provided with the compact
flash driver which can only read ASCII character data types from a
file. This fact
introduces extra programming effort: The characters that compose a 32
bit
word have to be read and combined to form the 32 bit word-number.
A typical configuration with bitsreams from the compact flash consists
of the
following steps:
-Open the bitstream file stored in the compact flash, identify and
read the header information,
-Read a data chunk equal to a multiple of a compact flash sector i.e.
x 512 bytes,
-Synthesize a 32-bit ICAP word from every 4 bytes of the data chunk,
-Load the synthesized word into the ICAP BRAM storage buffer
.....

Well that's another problem but for now I can't get the ICAP work and
appreciate any suggestion and comment!
For now I'll try installing ISE and EDK 9.2 instead of 8.2 and am
keeping my fingers crossed that may work!

I can't say anything about ISE+EDK 9.2. We have conducted experiments
only
using ISE+EDK 7.1i (for difference-based performance evaluation) and
ISE 9.1i.02 (for module-based application development)

I hope this help. Let me know about the progress

Good luck,
Kyprianos

Thanks a lot,

Amir

My code is as follows:

XHwIcap my_icap;

XStatus icap_stat;

icap_stat = XHwIcap_Initialize(&my_icap,
XPAR_OPB_HWICAP_0_DEVICE_ID, XHI_READ_DEVICEID_FROM_ICAP);

if(icap_stat != XST_SUCCESS)
print("\n There is something wrong in initializing the ICAP!!
\n");

icap_stat = XHwIcap_CommandDesync(&my_icap);

if(icap_stat != XST_SUCCESS)
print("\n Desynchronization was not successful!\n");

XHwIcap_StorageBufferWrite(&my_icap, 25, 0xffffffff);

icap_stat = XHwIcap_DeviceWriteFrame(&my_icap, XHI_FAR_CLB_BLOCK,
20, 32);

print("A frame has been written to the device\n");

if(icap_stat != XST_SUCCESS)
print("There is something wrong in writing to the device!");

Xuint32 frame_content;

icap_stat = XHwIcap_DeviceReadFrame(&my_icap, XHI_FAR_CLB_BLOCK,
20, 32);

print("The same frame is read from the configuration\n");

if(icap_stat != XST_SUCCESS)
print("\n There is something wrong in reading a frame with col =
5 and lut_bit = 3!!!!!\n");

if(icap_stat == XST_DEVICE_BUSY)
print("\n Device is busy right now!\n");

if(icap_stat == XST_BUFFER_TOO_SMALL)
print("BUFFER is TOO SMULL!\n");

if(icap_stat == XST_INVALID_PARAM)
print("XST_INVALID_PARAM!\n");

for(i = 0; i < my_icap.WordsPerFrame; i++)
{
print("word number");
putnum(i+1);
print(" is equal to: ");
frame_content = XHwIcap_StorageBufferRead(&my_icap, i);
putnum(frame_content);
putchar('\n');
}

On Feb 29, 8:29 pm, kyprianos <kpapa...@mhl.tuc.gr> wrote:

Microblaze. In bitgen.ut file I have set the value of mode pins
(M2M1M0) to 1 (PULLUP). So it is not set on 101 which is JTAG mode. As
well the base address and high address of my HWICAP is 0x42000000 and
0x42000fff as mentioned in the datasheet of HWICAP. Initially my OPB

Amir,

In which way to you load the initial configuration? Do you load it
through the ICAP and you don't use
ICAP at all?Did you check the Persist option?
As a second thought check the ICAP configuration. Has it been
configured appropriately? Have the base address and the high address
been added in the xparameters.h file?

Take care,
Kyprianos
Click to expand...
 
Hi Amir,
Please, can you put a complete kind of tutorial?
Thank you
 
You must log in or register to reply here.

Welcome to EDABoard.com

Sponsor

Back
Top