cancel
Showing results for 
Search instead for 
Did you mean: 

General Discussions

Lord_Petunio
Journeyman III

Problem with the bus AXI on Kria KV260

Hi,

I have a problem with the signals that i received on my slave for the PS. The problem its when I declared not cacheable the memory spaced asigned to the interfaces of the M_AXI_XX (XX its LPD or FPD depends of the core) the behavior changes.

The three write channels works at expected but when you ask for a reading the signals change. 

Am example its:

memcpy(0xA0000000 , datos,8);

memcpy(datos_read,0xA0000000,8);

The axi_width its 4 bytes and the memory is aligned with 8 bytes. The core of the APU its a cortexa_53 with a bus width of 16 bytes.

On this case the values of the signals on the write channel are AWSIZE = 2 and AWLEN = 1 which its interpreted as a writing of 8 bytes and the values of the signals on the read channel are AWSIZE = 2 and AWLEN = 3 which its interpreted as a reading of 16 bytes.

When I change the axi_width to 16 bytes.

On this case the values of the signals on the write channel are AWSIZE = 4 and AWLEN = 0 which its interpreted as a writing of 16 bytes and the values of the signals on the read channel are AWSIZE = 3 and AWLEN = 0 which its interpreted as a reading of 16 bytes but in this case the Write Strobes signals are enabled with a value of FF00 therefore the reading should be 8 bytes.

If anyone has any idea what might be going on. I'd appreciate it.

PD: The AXI its declared as a full AXI transfer.

 

0 Likes
1 Reply

Probably better to ask at https://www.xilinx.com/support.html

My PC- Ryzen 5 5600x, B550 aorus pro ac, Hyper 212 black, 2 x 16gb F4-3600c16dgtzn kit, NM790 2TB, Nitro+RX6900XT, RM850, Win.10 Pro., LC27G55T.
0 Likes